RTN 900 V100R009C00 Configuration Guide 01

OptiX RTN 900 Radio Transmission System
V100R009C00
Configuration Guide
Issue
01
Date
2016-04-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2016. 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 01 (2016-04-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

Configuration Guide
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX RTN 900
V100R009C00
iManager U2000
V200R016C50
Intended Audience
This document describes how to configure various services on the OptiX RTN 900 series.
This document describes the basic information and configuration process, and uses
configuration examples to show how to set specific parameters.
NOTE
This manual is for the entire OptiX RTN 900 series. The configuration examples for services in the manual
are based on a specific product, but are applicable to other OptiX RTN 900 products that support the services.
For example, the configuration example for CES services is based on OptiX RTN 980, but is applicable to
OptiX RTN 905, 910A, 950, 950A.
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.
Issue 01 (2016-04-30)

ii

Configuration Guide
About This Document
Symbol
Description
Indicates a potentially hazardous situation
which, if not avoided, could result in death
or serious injury.
which, if not avoided, may result in minor
or moderate injury.
which, if not avoided, could result in
equipment damage, data loss, performance
deterioration, or unanticipated results.
NOTICE is used to address practices not
related to personal injury.
Calls attention to important information,
best practices and tips.
NOTE is used to address information not
related to personal injury, equipment
damage, and environment deterioration.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

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

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Updates in Issue 01 (2016-04-30) Based on Product Version V100R009C00

This is the first document issue for the V100R009C00 product version.
Issue 01 (2016-04-30)

iii

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

5 Configuring the Network Topology........................................................................................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 Logical Board............................................................................................................................................................ 20
5.1.5 Fiber/Cable Types......................................................................................................................................................22
5.1.6 Subnet........................................................................................................................................................................ 23
5.2 Configuration Process...................................................................................................................................................23
5.3 Configuration Example (Network Topology of a Hybrid Microwave Chain Network).............................................. 28
5.3.1 Networking Diagram................................................................................................................................................. 28
5.3.2 Configuration Procedure............................................................................................................................................29
5.4 Configuration Example (Network Topology of a Hybrid Microwave Ring Network)................................................ 37
5.5 Configuration Example (Network Topology for a Packet Network)............................................................................46
6 Configuring Microwave Links..................................................................................................55

6.1 Basic Concepts............................................................................................................................................................. 56
6.1.1 RF Configuration Modes........................................................................................................................................... 56
6.1.2 Microwave Link Aggregation................................................................................................................................... 57
6.2 Configuration Process...................................................................................................................................................58
Issue 01 (2016-04-30)

iv

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

7.1 Basic Concepts............................................................................................................................................................. 84
7.1.1 Protection Modes for TDM Services.........................................................................................................................84
7.1.2 Timeslots for TDM Services on IF Boards................................................................................................................87
7.1.3 MSP Subnet............................................................................................................................................................... 88
7.1.4 SDH Trails................................................................................................................................................................. 88
7.1.5 Numbering Schemes for SDH Timeslots ..................................................................................................................88
7.1.6 TDM Timeslot Planning Schemes.............................................................................................................................90
7.1.7 Transmitting Native T1 Services Through E1 Channels........................................................................................... 92
7.2 End-to-End Configuration Process............................................................................................................................... 92
7.3 Configuration Process on a Per-NE Basis.................................................................................................................... 95
7.4 Configuration Example (TDM Services on a Hybrid Microwave Chain Network).....................................................99
7.4.2 End-to-end Configuration........................................................................................................................................100
7.4.3 Configuration on a Per-NE Basis............................................................................................................................ 105
7.5 Configuration Example (TDM Services on a Hybrid Microwave Ring Network).................................................... 107
7.5.1 Networking Diagram............................................................................................................................................... 107
7.5.3 Configuration on a Per-NE Basis.............................................................................................................................113
8 Configuring Native Ethernet Services...................................................................................116

8.1 Basic Concepts............................................................................................................................................................117
8.1.1 Native Ethernet Services..........................................................................................................................................117
8.1.2 Ethernet Port ID....................................................................................................................................................... 117
8.1.3 Auto-negotiation...................................................................................................................................................... 118
8.1.4 Flow Control............................................................................................................................................................120
8.1.5 Typical Mobile Backhaul Network Topologies for Ethernet Services.................................................................... 121
8.1.5.1 Networking of VLAN-based E-Line Services......................................................................................................121
8.1.5.2 Networking of IEEE 802.1d bridge-based E-LAN services.................................................................................122
8.1.5.3 Networking of IEEE 802.1q Bridge-based E-LAN Services............................................................................... 123
8.1.5.4 Comparison Between the Three Networking Modes........................................................................................... 124
8.1.6 Protection for Native Ethernet Services.................................................................................................................. 127
8.2 End-to-end Configuration Process (Native Ethernet E-Line).....................................................................................132
8.3 End-to-end Configuration Process (Native Ethernet E-LAN)....................................................................................136
Issue 01 (2016-04-30)


Configuration Guide
Contents
8.4 Process of Configuration on a Per-NE Basis (Native Ethernet E-Line)..................................................................... 138

8.5 Process of Configuration on a Per-NE Basis (Native Ethernet E-LAN).................................................................... 141
8.6 Configuration Example (Configuring Point-to-Point Transparently Transmitted E-Line Services)..........................146
8.6.2 Configuration Procedure..........................................................................................................................................147
8.6.2.1 Configuring Ethernet Ports................................................................................................................................... 147
8.6.2.2 Configuring Service Information..........................................................................................................................149
8.6.2.3 Configuring QoS...................................................................................................................................................150
8.6.2.4 Verifying Ethernet Services.................................................................................................................................. 153
8.7 Configuration Example (VLAN-based E-Line Services)...........................................................................................156
8.7.2 End-to-End Configuration Procedure...................................................................................................................... 156
8.7.2.2 Configuring QoS...................................................................................................................................................160
8.7.3 Per-NE Configuration Process.................................................................................................................................165
8.7.3.3 Configuring QoS...................................................................................................................................................170
8.8 Configuration Example (QinQ-based E-Line Services)............................................................................................. 175
8.8.2.2 Configuring QoS...................................................................................................................................................180
8.8.3.3 Configuring QoS...................................................................................................................................................189
8.9 Configuration Example (IEEE 802.1d Bridge-based E-LAN Services).................................................................... 195
8.9.2.2 Configuring QoS...................................................................................................................................................201
8.9.3.2 Configuring ERPS................................................................................................................................................ 210
8.9.3.4 Configuring QoS...................................................................................................................................................214
Issue 01 (2016-04-30)

vi

Configuration Guide
Contents

8.10 Configuration Example (IEEE 802.1q Bridge-based E-LAN Services).................................................................. 218
8.10.1 Networking Diagram............................................................................................................................................. 218
8.10.2 End-to-end Configuration......................................................................................................................................219
8.10.2.1 Configuring Service Information........................................................................................................................219
8.10.2.2 Configuring QoS.................................................................................................................................................221
8.10.2.3 Verifying Ethernet Services................................................................................................................................ 223
8.10.3 Configuration on a Per-NE Basis.......................................................................................................................... 225
8.10.3.1 Configuring Ethernet Ports................................................................................................................................. 225
8.10.3.3 Configuring QoS.................................................................................................................................................231
8.11 Configuration Example (IEEE 802.1ad Bridge-based E-LAN Services).................................................................235
8.11.2 End-to-End Configuration Procedure.................................................................................................................... 236
8.11.2.2 Configuring QoS.................................................................................................................................................241
8.11.3 Configuration on a Per-NE Basis...........................................................................................................................247
8.11.3.1 Configuring Ethernet Ports................................................................................................................................. 247
8.11.3.2 Configuring ERPS.............................................................................................................................................. 251
8.11.3.4 Configuring QoS.................................................................................................................................................256
9 Configuring Ethernet Services on EoS/EoPDH Boards..................................................... 262

9.1 Basic Concepts........................................................................................................................................................... 263
9.1.1 EoS/EoPDH............................................................................................................................................................. 263
9.1.2 VCTRUNK.............................................................................................................................................................. 264
9.2 Configuration Procedure (EPL/EVPL Services)........................................................................................................ 264
9.3 Configuration Procedure (EPLAN/EVPLAN Services).............................................................................................268
9.4 Configuration Example (Ethernet Services Based on TDM Radio) ..........................................................................273
9.4.2 Configuration Process..............................................................................................................................................274
9.4.2.1 Configuration Procedure (Ethernet Ports)............................................................................................................ 274
9.4.2.2 Configuring ERPS Protection...............................................................................................................................280
9.4.2.3 Configuring Ethernet Services..............................................................................................................................281
9.4.2.4 Configuring Cross-connections............................................................................................................................ 283
9.5 Configuration Example (Ethernet Services Traversing a TDM Network)................................................................. 287
9.5.2 Configuration Procedure..........................................................................................................................................289
9.5.2.1 Configuring Native Ethernet Ports....................................................................................................................... 289
Issue 01 (2016-04-30)

vii

Configuration Guide
Contents
9.5.2.2 Configuring Native Ethernet Service Information............................................................................................... 290

9.5.2.3 Configuring QoS Information for Native Ethernet Services................................................................................ 291
9.5.2.4 Configuring EoS/EoPDH Ethernet Ports..............................................................................................................294
9.5.2.5 Configuring EoS/EoPDH Ethernet Protection..................................................................................................... 297
9.5.2.6 Configuring EoS/EoPDH-based Ethernet Services.............................................................................................. 298
9.5.2.7 Configuring Cross-connections............................................................................................................................ 299
9.5.2.8 Configuring QoS for EoS/EoPDH-based Ethernet Services................................................................................ 301
10 Configuring MPLS Tunnels.................................................................................................. 307

10.1 End-to-End Configuration Process........................................................................................................................... 308
10.2 Configuration Process on a Per-NE Basis................................................................................................................ 314
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)................................................................... 322
10.3.2.1 Configuring MPLS Port......................................................................................................................................323
10.3.2.2 Configuring MPLS Tunnel................................................................................................................................. 325
10.3.2.3 Configuring QoS ................................................................................................................................................332
10.3.2.4 Verifying MPLS Tunnels.................................................................................................................................... 333
10.3.3 Procedure of Configuration on a Per-NE Basis..................................................................................................... 334
10.3.3.3 MPLS APS......................................................................................................................................................... 342
10.3.3.4 Configuring QoS ................................................................................................................................................345
10.3.3.5 Configuration Procedure (Verifying Configured MPLS Tunnels)..................................................................... 346
10.4 Configuration Example (MPLS Tunnels with No Protection)................................................................................. 347
10.4.2.3 Configuring QoS.................................................................................................................................................355
10.4.3 Procedure of Configuration on a Per-NE Basis..................................................................................................... 357
10.4.3.3 Configuring QoS.................................................................................................................................................364
10.5 Configuration Example (MPLS Tunnels Traversing L2 Networks).........................................................................366
10.5.2.3 Configuring QoS ................................................................................................................................................375
Issue 01 (2016-04-30)

viii

Configuration Guide
Contents

10.5.3 Per-NE Configuration Process...............................................................................................................................377
10.5.3.3 Configuring QoS ................................................................................................................................................385
10.6 Configuration Example (MPLS Tunnels Traversing a TDM Network)...................................................................387
10.6.2.3 Configuring QoS.................................................................................................................................................397
10.6.3.3 Configuring QoS.................................................................................................................................................409
10.6.3.4 Configuration Procedure (Verifying Configured MPLS Tunnels)......................................................................411
11 Configuring ETH PWE3 Services......................................................................................... 412

11.1 End-to-End Configuration Process (E-Line Services Carried by PWs)................................................................... 414
11.2 End-to-End Configuration Process (Hybrid Configuration of PW-Carried E-Line Services and E-LAN Services)
.......................................................................................................................................................................................... 417
11.3 Per-NE Configuration Process (E-Line Services Carried by PWs).......................................................................... 421
11.4 Per-NE Configuration Process (E-Aggr Services Carried by PWs)......................................................................... 425
11.5 Per-NE Configuration Process (E-LAN Services Carried by PWs)......................................................................... 427
11.6 Configuration Example (E-Line Services Carried by SS-PW).................................................................................431
11.6.2.1 Configuring LAG................................................................................................................................................432
11.6.2.3 Configuring QoS ................................................................................................................................................435
11.6.2.4 Verifying Services Carried by PWs.................................................................................................................... 437
11.6.3 Per-NE Configuration Procedure...........................................................................................................................438
11.6.3.1 Configuring UNIs............................................................................................................................................... 438
11.6.3.2 Configuring LAG................................................................................................................................................439
11.6.3.4 Configuring QoS ................................................................................................................................................442
11.7 Configuration Example (E-Line Services Carried by MS-PWs)..............................................................................444
11.7.2.1 Configuring LAG................................................................................................................................................446
Issue 01 (2016-04-30)

ix

Configuration Guide
Contents

11.7.2.3 Configuring QoS ................................................................................................................................................449
11.7.3.2 Configuring LAG................................................................................................................................................453
11.7.3.4 Configuring QoS ................................................................................................................................................457
11.8 Configuration Example (Hybrid Configuration of PW-Carried E-Line Services and E-LAN Services).................460
11.8.2.3 Configuring QoS ................................................................................................................................................464
11.8.3.3 Configuring QoS ................................................................................................................................................474
11.9 Configuration Example (E-Aggr Services Carried by PWs).................................................................................... 476
11.9.2.3 Configuring QoS ................................................................................................................................................483
12 Configuring CES Services......................................................................................................486

12.1 End-to-End Configuration Process........................................................................................................................... 487
12.2 Per-NE Configuration Process..................................................................................................................................489
12.3 Configuration Example (CES Services Based on CESoPSN Encapsulation).......................................................... 492
12.4 Configuration Example (CES Services Based on SAToP Encapsulation)................................................................500
Issue 01 (2016-04-30)


Configuration Guide
Contents

12.5 Configuration Example (Configuring CES Services Transparently Transmitting STM-1s)....................................509
12.5.2.3 Configuring Information About CES Services Transmitting SDH Overhead Bytes..........................................512
12.5.3.2 Configuring Information About CES Services Carrying E1 Payload................................................................ 515
12.5.3.3 Configuring Information About CES Services Transmitting SDH Overhead Bytes..........................................517
13 Configuring ATM Services....................................................................................................520

13.1 End-to-End Configuration Process (ATM Services)................................................................................................ 521
13.2 Per-NE Configuration Process (ATM Services)....................................................................................................... 525
13.3 Configuration Example (ATM Connection-based ATM Services)...........................................................................529
13.3.2.2 Configuring ATM/IMA Information.................................................................................................................. 532
13.3.2.3 Configuring QoS ................................................................................................................................................534
13.3.3.3 Configuring QoS ................................................................................................................................................544
13.4 Configuration Example (Transparently Transmitted ATM Services).......................................................................550
Issue 01 (2016-04-30)

xi

Configuration Guide
Contents

13.4.2.3 Configuring QoS ................................................................................................................................................554
13.4.3.3 Configuring QoS ................................................................................................................................................561
14 Configuring the Clock............................................................................................................ 566

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

15.1 Auxiliary Ports and Functions.................................................................................................................................. 584
15.2 Environment Monitoring Functions......................................................................................................................... 586
15.3 Configuration Process (Monitoring the Outdoor Cabinet)....................................................................................... 589
15.4 Configuration Example (Orderwire)........................................................................................................................ 591
15.5 Configuration Example (Synchronous Data Services)............................................................................................. 595
15.6 Configuration Example (Asynchronous Data Services)...........................................................................................597
15.7 Configuration Example (Wayside E1 Services)....................................................................................................... 599
15.8 Configuration Example (External Alarms)...............................................................................................................601
15.9 Configuration Example (Monitoring of an Outdoor Cabinet)..................................................................................603
Issue 01 (2016-04-30)

xii

Configuration Guide
Contents
16 Adding and Modifying Configuration Data......................................................................607

16.1 Common Task Collection (Network Topology)....................................................................................................... 608
16.2 Common Task Collection (Radio Links)..................................................................................................................609
16.3 Common Task Collection (TDM Services).............................................................................................................. 613
16.4 Common Task Collection (Native Ethernet Services)..............................................................................................614
16.5 Common Task Collection (Ethernet Services on the EoS/EoPDH Plane)............................................................... 616
16.6 Common Task Collection (MPLS/PWE3 Services)................................................................................................. 619
A Task Collection......................................................................................................................... 627

A.1 U2000 Quick Start..................................................................................................................................................... 629
A.1.1 Logging in to a U2000 Client................................................................................................................................. 629
A.1.2 Shutting Down a U2000 Client...............................................................................................................................629
A.1.3 Using Online Help.................................................................................................................................................. 630
A.1.4 Navigating to Common Views................................................................................................................................631
A.1.4.1 Navigating to the Main Topology........................................................................................................................631
A.1.4.2 Navigating to the NE Explorer............................................................................................................................ 631
A.1.4.3 Navigating to the NE Panel................................................................................................................................. 632
A.2 Web LCT Quick Start................................................................................................................................................ 632
A.2.1 Using Online Help.................................................................................................................................................. 633
A.2.2 Navigating to the NE Explorer............................................................................................................................... 633
A.3 Network Management............................................................................................................................................... 634
A.3.1 Managing NEs........................................................................................................................................................ 634
A.3.1.1 Creating NEs by Using the Search Method (U2000).......................................................................................... 634
A.3.1.2 Creating NEs by Using the Search Method (Web LCT)..................................................................................... 636
A.3.1.3 Creating NEs by Using the Manual Method (U2000)......................................................................................... 638
A.3.1.4 Creating NEs by Using the Manual Method (Web LCT).................................................................................... 640
A.3.1.5 Logging In to an NE (Web LCT).........................................................................................................................641
A.3.1.6 Configuring the Logical Board............................................................................................................................ 642
A.3.1.7 Configuring an SFP Port......................................................................................................................................643
A.3.1.8 Configuring the Backplane Bus Rate.................................................................................................................. 647
A.3.1.9 Changing the NE ID............................................................................................................................................ 647
A.3.1.10 Changing the NE Name..................................................................................................................................... 648
A.3.1.11 Enabling NE Automatic Reporting....................................................................................................................649
A.3.1.12 Synchronizing the NE Time (U2000)................................................................................................................ 650
A.3.1.13 Synchronizing the NE Time (Web LCT)........................................................................................................... 653
A.3.1.14 Localizing the NE Time.....................................................................................................................................654
A.3.1.15 Configuring Standard NTP Keys.......................................................................................................................655
A.3.2 Configuring the NE Data........................................................................................................................................ 656
A.3.2.1 Uploading the NE Data (U2000)......................................................................................................................... 656
A.3.2.2 Synchronizing NE Data (U2000).........................................................................................................................657
A.3.3 Configuring the Performance Monitoring Status of NEs....................................................................................... 658
A.3.4 Suppressing Alarms for Monitored Objects........................................................................................................... 659
Issue 01 (2016-04-30)

xiii

Configuration Guide
Contents
A.3.5 Connecting Fibers or Cables...................................................................................................................................660

A.3.5.1 Creating Optical Fibers by Using the Search Method......................................................................................... 660
A.3.5.2 Creating Fibers Manually.................................................................................................................................... 661
A.3.5.3 Searching for Ethernet Links............................................................................................................................... 662
A.3.5.4 Creating an Extended ECC.................................................................................................................................. 664
A.3.5.5 Creating a Back-to-Back Radio Connection........................................................................................................665
A.3.6 Managing Subnets.................................................................................................................................................. 665
A.3.6.1 Creating a Subnet.................................................................................................................................................666
A.3.6.2 Copying Topology Objects.................................................................................................................................. 667
A.3.6.3 Moving Topology Objects................................................................................................................................... 668
A.3.7 Managing Communication..................................................................................................................................... 668
A.3.7.1 Setting NE IP Communication Parameters..........................................................................................................668
A.3.7.2 Configuring DCCs............................................................................................................................................... 669
A.3.7.3 Configuring DCC Transparent Transmission...................................................................................................... 671
A.3.7.4 Configuring the VLAN ID and Bandwidth Used by an Inband DCN.................................................................672
A.3.7.5 Configuring the Priority of Inband DCN Packets................................................................................................673
A.3.7.6 Configuring Inband DCN Ports........................................................................................................................... 673
A.3.7.7 Configuring Access Control................................................................................................................................ 674
A.3.7.8 Configuring Extended ECC Communication...................................................................................................... 675
A.3.7.9 Creating a Static IP Route....................................................................................................................................677
A.3.7.10 Creating Static Route Entries in Kernel Route Tables.......................................................................................677
A.3.7.11 Setting OSPF Protocol Parameters.................................................................................................................... 678
A.3.7.12 Creating an OSPF Area..................................................................................................................................... 679
A.3.7.13 Configuring the Network Information of an ABR............................................................................................ 680
A.3.7.14 Creating a Manual Route Aggregation Group...................................................................................................681
A.3.7.15 Configuring the OSPF Authentication Type......................................................................................................682
A.3.7.16 Enabling the Proxy ARP....................................................................................................................................683
A.3.7.17 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used.................................................. 684
A.3.7.18 Querying ECC Routes....................................................................................................................................... 684
A.3.7.19 Querying IP Routes............................................................................................................................................685
A.3.7.20 Querying Core Routing Table Entries............................................................................................................... 686
A.3.7.21 Querying OSPF Neighbor Information............................................................................................................. 686
A.3.7.22 Verifying Connectivity of an ECC Network......................................................................................................687
A.3.7.23 Verifying Connectivity of an IP DCN Network................................................................................................ 688
A.3.7.24 Setting SNMP Communications Parameters..................................................................................................... 689
A.3.7.25 Configuring the Active and Standby Gateway NEs.......................................................................................... 690
A.3.8 Configuring the NMS Port......................................................................................................................................691
A.3.8.1 Configuring Basic Parameters for the NMS Port................................................................................................ 691
A.3.8.2 Setting the VLAN ID for Huawei NMS.............................................................................................................. 692
A.3.8.3 Changing the Encapsulation Type and QinQ Type Domain for the Ethernet NMS Port.................................... 693
A.3.8.4 Configuring the Network Management Serial Port on an NE............................................................................. 694
A.3.8.5 Configuring the Mini USB Port...........................................................................................................................695
Issue 01 (2016-04-30)

xiv

Configuration Guide
Contents
A.4 Security Management................................................................................................................................................ 695

A.4.1 Configuring an NE User......................................................................................................................................... 695
A.4.1.1 Creating an NE User............................................................................................................................................ 696
A.4.1.2 Changing the Password of an NE User................................................................................................................697
A.4.1.3 Configuring Additional User Information........................................................................................................... 698
A.4.1.4 Setting Warning Screen Parameters.....................................................................................................................699
A.4.1.5 Querying NE User Groups...................................................................................................................................700
A.4.1.6 Managing Online NE Users.................................................................................................................................701
A.4.1.7 Switching NE Users.............................................................................................................................................702
A.4.2 Configuring USB Access Status............................................................................................................................. 703
A.4.3 Configuring LCT Access to NEs............................................................................................................................ 703
A.4.4 Configuring SSL Protocol Communication............................................................................................................704
A.4.4.1 Configuring SSL Protocol Communication Between a U2000 Server and its Clients........................................704
A.4.4.2 Configuring the Connection Mode Between a U2000 Client and Its Gateway NE............................................ 705
A.4.5 Configuring RADIUS Authentication.................................................................................................................... 707
A.4.5.1 Enabling/Disabling the RADIUS Function......................................................................................................... 707
A.4.5.2 Creating a RADIUS Server or a RADIUS Proxy Server.................................................................................... 708
A.4.5.3 Configuring RADIUS Server Parameters............................................................................................................710
A.4.6 Configuring LLDP.................................................................................................................................................. 711
A.4.6.1 Configuring the Transmit Parameters for LLDP Packets.................................................................................... 711
A.4.6.2 Configuring LLDP for an Ethernet Port.............................................................................................................. 712
A.4.6.3 Querying LLDP Neighbor Relationship.............................................................................................................. 712
A.5 Managing Radio Links.............................................................................................................................................. 713
A.5.1 Configuring a Single-Hop Radio Link................................................................................................................... 713
A.5.2 Creating an IF 1+1 Protection Group..................................................................................................................... 716
A.5.3 Modifying the Parameters of IF 1+1 Protection..................................................................................................... 718
A.5.4 Creating an N+1 Protection Group......................................................................................................................... 720
A.5.5 Querying the IF 1+1 Protection Status................................................................................................................... 722
A.5.6 Querying the IF N+1 Protection Status.................................................................................................................. 723
A.5.7 IF 1+1 Protection Switching...................................................................................................................................723
A.5.8 IF N+1 Protection Switching.................................................................................................................................. 724
A.5.9 Starting/Stopping the N+1 Protection Protocol...................................................................................................... 725
A.5.10 Creating a PLA/EPLA/EPLA+/Super EPLA Group............................................................................................ 726
A.5.11 Querying the Status of a PLA/EPLA/EPLA+/Super EPLA Group...................................................................... 733
A.5.12 Configuring Ethernet Frame Header Compression over Air Interfaces............................................................... 733
A.5.13 Configuring Enhanced Ethernet Frame Compression.......................................................................................... 734
A.5.14 Setting AES-based Encryption at Air Interfaces.................................................................................................. 735
A.6 Managing the MSP.................................................................................................................................................... 736
A.6.1 Configuring Linear MSP........................................................................................................................................ 736
A.6.2 Querying the Status of the Linear MSP.................................................................................................................. 738
A.6.3 Performing Linear MSP Switching........................................................................................................................ 738
A.6.4 Starting/Stopping the Linear MSP Protocol........................................................................................................... 739
Issue 01 (2016-04-30)

xv

Configuration Guide
Contents
A.6.5 Configuring Ring MSP........................................................................................................................................... 740

A.6.6 Querying Ring MSP Status.....................................................................................................................................741
A.6.7 TriggeMSP ring Ring Switching............................................................................................................................ 742
A.6.8 Starting/Stopping the MSP Ring Protocol.............................................................................................................. 743
A.6.9 Creating a Packet-based Linear MSP Group.......................................................................................................... 743
A.6.10 Querying the Status of a Packet-based Linear MSP Group..................................................................................745
A.6.11 Performing Packet-based Linear MSP Switching.................................................................................................745
A.6.12 Enabling/Disabling the Linear MSP Protocol...................................................................................................... 746
A.7 Managing TDM Services...........................................................................................................................................747
A.7.1 Creating the Cross-Connections of Point-to-Point Services...................................................................................747
A.7.2 Creating Cross-Connections of SNCP Services..................................................................................................... 748
A.7.3 Modifying the Priorities of E1 Services................................................................................................................. 749
A.7.4 Inserting E1_AIS upon a TU_AIS Condition.........................................................................................................751
A.7.5 Configuring the Automatic Switching of SNCP Services...................................................................................... 752
A.7.6 Deleting Cross-Connections................................................................................................................................... 753
A.7.7 Converting a Normal Service into an SNCP Service............................................................................................. 754
A.7.8 Converting an SNCP Service to a Normal Service................................................................................................ 756
A.7.9 Querying TDM Services.........................................................................................................................................757
A.7.10 Switching SNCP Services.....................................................................................................................................757
A.7.11 Querying the Protection Status of SNCP Services............................................................................................... 758
A.8 Managing Ports.......................................................................................................................................................... 758
A.8.1 Setting the Parameters of SDH Ports......................................................................................................................759
A.8.2 Setting Working Modes of E1 Ports....................................................................................................................... 759
A.8.3 Setting the Parameters of PDH Ports......................................................................................................................760
A.8.4 Configuring Overhead Bytes.................................................................................................................................. 761
A.8.4.1 Configuring RSOHs.............................................................................................................................................761
A.8.4.2 Configuring VC-4 POHs..................................................................................................................................... 762
A.8.4.3 Configuring VC-12 POHs................................................................................................................................... 764
A.8.5 Changing the E1 Frame Format and Frame Mode for a Channelized STM-1....................................................... 766
A.8.6 Setting Smart E1 Port Parameters...........................................................................................................................766
A.8.6.1 Setting Basic Attributes of Smart E1 Ports..........................................................................................................766
A.8.6.2 Setting Advanced Attributes of Smart E1 Ports.................................................................................................. 767
A.8.7 Setting Serial Port Parameters................................................................................................................................ 768
A.8.7.1 Creating Serial Ports............................................................................................................................................ 768
A.8.7.2 Setting Basic Attributes of Serial Ports............................................................................................................... 769
A.8.8 Setting Ethernet Port Parameters............................................................................................................................ 770
A.8.8.1 Setting the Basic Attributes of Ethernet Ports..................................................................................................... 770
A.8.8.2 Configuring the Traffic Control of Ethernet Ports...............................................................................................771
A.8.8.3 Setting the Layer 2 Attributes of Ethernet Ports..................................................................................................772
A.8.8.4 Setting Layer 3 Attributes of Ethernet Ports........................................................................................................773
A.8.8.5 Setting the Advanced Attributes of Ethernet Ports..............................................................................................774
A.8.9 Setting Microwave Port Parameters....................................................................................................................... 775
Issue 01 (2016-04-30)

xvi

Configuration Guide
Contents
A.8.9.1 Setting the Basic Attributes of IF_ETH Ports..................................................................................................... 775

A.8.9.2 Setting the Layer 2 Attributes of IF_ETH Ports.................................................................................................. 776
A.8.9.3 Setting Layer 3 Attributes of IF_ETH Ports........................................................................................................776
A.8.9.4 Setting the Advanced Attributes of IF_ETH Ports.............................................................................................. 777
A.8.10 Setting IF Port Parameters.................................................................................................................................... 778
A.8.10.1 Setting IF Attributes.......................................................................................................................................... 778
A.8.10.2 Configuring ATPC Attributes............................................................................................................................ 780
A.8.10.3 Setting Advanced AM Attributes...................................................................................................................... 781
A.8.10.4 Querying the AM Status.................................................................................................................................... 782
A.8.10.5 Querying ATPC Adjustment Records................................................................................................................782
A.8.10.6 Changing the IF Service Type........................................................................................................................... 783
A.8.10.7 Changing the Running Mode of an IF Port....................................................................................................... 784
A.8.10.8 Enabling or Disabling the AM Booster Function.............................................................................................. 785
A.8.10.9 Modifying the Hybrid/AM Attributes............................................................................................................... 785
A.8.11 Setting RFU/RFU-SD/ODU Port Parameters.......................................................................................................787
A.8.11.1 Setting ODU Transmit Frequency Attributes.................................................................................................... 788
A.8.11.2 Querying ODU Information...............................................................................................................................788
A.8.11.3 Setting ODU Power Attributes.......................................................................................................................... 789
A.8.11.4 Setting ODU Advanced Attributes.................................................................................................................... 790
A.8.12 Creating VLAN Sub-Interfaces............................................................................................................................ 791
A.9 Configuring Native Ethernet Services and Features..................................................................................................792
A.9.1 Managing ERPS......................................................................................................................................................792
A.9.1.1 Creating Ethernet Ring Protection Instances....................................................................................................... 792
A.9.1.2 Setting Global ERPS Protocol Parameters.......................................................................................................... 794
A.9.1.3 Setting Protocol Parameters for an ERPS Instance............................................................................................. 794
A.9.1.4 Creating a Virtual Channel VLAN Forwarding Table.........................................................................................795
A.9.1.5 Setting Parameters for Switching Upon Multiple Failures..................................................................................796
A.9.1.6 Performing an External ERPS Switchover.......................................................................................................... 797
A.9.1.7 Querying the Status of the Ethernet Ring Protocol............................................................................................. 798
A.9.2 Managing the LAG................................................................................................................................................. 798
A.9.2.1 Creating a LAG....................................................................................................................................................799
A.9.2.2 Setting LAG Parameters...................................................................................................................................... 801
A.9.2.3 Querying the Protocol Information of the LAG.................................................................................................. 802
A.9.3 Configuring Ethernet Services................................................................................................................................803
A.9.3.1 Configuring the QinQ Link................................................................................................................................. 804
A.9.3.2 Configuring the Forwarding Mode for Ethernet Services................................................................................... 804
A.9.3.3 Configuring UNI-UNI E-Line Services (U2000)................................................................................................ 805
A.9.3.4 Configuring UNI-UNI E-Line Services(Web LCT)............................................................................................ 806
A.9.3.5 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(U2000)........................................................ 808
A.9.3.6 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)................................................... 809
A.9.3.7 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(U2000)........................................................ 810
A.9.3.8 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)....................................................811
Issue 01 (2016-04-30)

xvii

Configuration Guide
Contents
A.9.3.9 Configuring UNI-NNI E-Line Services (Carried by PWs)(U2000)....................................................................814

A.9.3.10 Configuring UNI-NNI E-Line Services (Carried by PWs)(Web LCT)............................................................. 816
A.9.3.11 Creating E-AGGR Services............................................................................................................................... 818
A.9.3.12 Creating a VLAN Forwarding Table for an E-Line Service..............................................................................820
A.9.3.13 Configuring TPID for a Request VLAN........................................................................................................... 821
A.9.3.14 Configuring IEEE 802.1d Bridge-Based E-LAN Services(U2000).................................................................. 822
A.9.3.15 Configuring IEEE 802.1d Bridge-Based E-LAN Services(Web LCT)............................................................. 823
A.9.3.16 Configuring IEEE 802.1q Bridge-Based E-LAN Services(U2000).................................................................. 824
A.9.3.17 Configuring IEEE 802.1q Bridge-Based E-LAN Services(Web LCT)............................................................. 826
A.9.3.18 Configuring IEEE 802.1ad Bridge-Based E-LAN Services(U2000)................................................................ 827
A.9.3.19 Configuring IEEE 802.1ad Bridge-Based E-LAN Services(Web LCT)........................................................... 829
A.9.3.20 Configuring PW-Carried E-LAN Services (U2000)..........................................................................................830
A.9.3.21 Configuring Global Attributes of VPLS Services............................................................................................. 833
A.9.3.22 Changing Logical Ports Connected to a VB......................................................................................................834
A.9.3.23 Deleting an E-Line Service................................................................................................................................835
A.9.3.24 Deleting E-LAN Services.................................................................................................................................. 836
A.9.4 Managing the MAC Address Table........................................................................................................................ 836
A.9.4.1 Creating a Static MAC Address Entry.................................................................................................................836
A.9.4.2 Creating a Blacklist Entry of MAC Addresses....................................................................................................837
A.9.4.3 Configuring the MAC Address Learning Parameters......................................................................................... 838
A.9.4.4 Querying or Deleting a Dynamic MAC Address................................................................................................ 839
A.9.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service........................................................839
A.9.6 Managing the MSTP...............................................................................................................................................840
A.9.6.1 Creating the MSTP Port Group........................................................................................................................... 840
A.9.6.2 Setting the Bridge Parameters of the MSTP........................................................................................................841
A.9.6.3 Setting the Parameters of the CIST..................................................................................................................... 842
A.9.6.4 Querying the CIST Running Information............................................................................................................843
A.9.6.5 Changing the Spanning Tree Protocol Used by the Port Group.......................................................................... 844
A.9.6.6 Enabling/Disabling the MSTP Protocol.............................................................................................................. 844
A.9.6.7 Modifying the Configuration Data of the MSTP Port Group..............................................................................845
A.9.7 Managing the IGMP Snooping............................................................................................................................... 846
A.9.7.1 Configuring the IGMP Snooping Protocol.......................................................................................................... 846
A.9.7.2 Querying the Port Information of the Routers..................................................................................................... 847
A.9.7.3 Querying the Information About the Multicast Groups...................................................................................... 848
A.9.7.4 Creating Static Router Ports................................................................................................................................ 848
A.9.7.5 Creating a Member of a Static Multicast Group..................................................................................................849
A.9.7.6 Adding a Quickly Deleted Port............................................................................................................................850
A.9.7.7 Calculating IGMP Packets...................................................................................................................................851
A.9.8 Managing the QoS.................................................................................................................................................. 851
A.9.8.1 Creating a DS Domain.........................................................................................................................................851
A.9.8.2 Modifying the Mapping Relationships for the DS Domain.................................................................................853
A.9.8.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types.................................................. 854
Issue 01 (2016-04-30)

xviii

Configuration Guide
Contents
A.9.8.4 Enabling/Disabling DSCP Demapping at the Egress Port of a DiffServ Domain...............................................856

A.9.8.5 Enabling/Disabling Outbound Demapping at the Egress Port of a DiffServ Domain.........................................857
A.9.8.6 Creating a Port Policy.......................................................................................................................................... 858
A.9.8.7 Modifying the Port Policy................................................................................................................................... 859
A.9.8.8 Creating Traffic....................................................................................................................................................860
A.9.8.9 Creating a Port WRED Policy............................................................................................................................. 862
A.9.8.10 Creating a Service WRED Policy......................................................................................................................863
A.9.8.11 Creating a WRR Policy......................................................................................................................................864
A.9.8.12 Setting the Port That Uses the Port Policy.........................................................................................................865
A.9.8.13 Creating a V-UNI Egress Policy........................................................................................................................ 866
A.9.8.14 Creating a V-UNI Group....................................................................................................................................867
A.9.8.15 Creating a PW Policy.........................................................................................................................................868
A.9.8.16 Creating a QinQ Policy......................................................................................................................................869
A.9.8.17 Applying policies for Ethernet services.............................................................................................................871
A.9.8.18 Configuring Port Shaping.................................................................................................................................. 871
A.9.8.19 Configuring Bandwidth Limitation for MPLS Tunnels.....................................................................................872
A.9.8.20 Configuring Bandwidth Limitation for PWs..................................................................................................... 873
A.9.8.21 Configuring Bandwidth Limitation for QinQ Links..........................................................................................874
A.9.9 Using the ethernet service OAM............................................................................................................................ 875
A.9.9.1 Creating an MD................................................................................................................................................... 875
A.9.9.2 Creating an MA................................................................................................................................................... 876
A.9.9.3 Creating MEPs.....................................................................................................................................................877
A.9.9.4 Creating Remote MEPs in an MA....................................................................................................................... 878
A.9.9.5 Creating MIPs...................................................................................................................................................... 879
A.9.9.6 Performing a CC Test.......................................................................................................................................... 880
A.9.9.7 Performing an LB Test.........................................................................................................................................881
A.9.9.8 Performing an LT Test......................................................................................................................................... 882
A.9.9.9 Activating the AIS............................................................................................................................................... 883
A.9.9.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services............................................... 884
A.9.9.11 E-LAN Service Loopback Detection................................................................................................................. 885
A.9.9.12 Reactivating E-LAN Services............................................................................................................................886
A.9.9.13 Enabling/Disabling Automatic Service Loop Detection................................................................................... 887
A.9.10 Using the ethernet port OAM............................................................................................................................... 888
A.9.10.1 Enabling the OAM Auto-Discovery Function...................................................................................................888
A.9.10.2 Enabling the Link Event Notification ...............................................................................................................889
A.9.10.3 Modifying the OAM Error Frame Monitoring Threshold ................................................................................ 889
A.9.10.4 Performing Remote Loopbacks......................................................................................................................... 890
A.9.10.5 Enabling Self-Loop Detection........................................................................................................................... 891
A.9.11 LPT Configuration................................................................................................................................................ 892
A.9.11.1 Configuring Point-to-Point LPT Traversing an L2 Network.............................................................................892
A.9.11.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network..............................................................893
A.9.11.3 Configuring Point-to-Multipoint LPT................................................................................................................894
Issue 01 (2016-04-30)

xix

Configuration Guide
Contents
A.9.11.4 Configuring Simple LPT....................................................................................................................................895

A.9.12 Configuring IP Packet Coloring and Statistics Collection................................................................................... 896
A.10 Configuring Ethernet Services and Features on the EoS/EoPDH Boards............................................................... 898
A.10.1 Managing ERPS....................................................................................................................................................898
A.10.1.1 Creating ERPS Instances................................................................................................................................... 898
A.10.1.2 Setting the Parameters of the ERPS Protocol.................................................................................................... 899
A.10.1.3 Querying the Status of the ERPS Protocol........................................................................................................ 900
A.10.2 Managing LAGs .................................................................................................................................................. 900
A.10.2.1 Creating a LAG..................................................................................................................................................900
A.10.2.2 Setting Parameters for LAGs.............................................................................................................................902
A.10.2.3 Querying the Protocol Information of LAGs.....................................................................................................902
A.10.3 Configuring Ethernet Services..............................................................................................................................903
A.10.3.1 Creating Ethernet Private Line Services............................................................................................................903
A.10.3.2 Creating Ethernet LAN Services....................................................................................................................... 905
A.10.3.3 Changing the Ports Connected to a VB............................................................................................................. 909
A.10.3.4 Creating the VLAN Filtering Table................................................................................................................... 909
A.10.3.5 Creating QinQ-Based EVPL Services............................................................................................................... 910
A.10.3.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services................................................................................912
A.10.3.7 Deleting an Ethernet Private Line Service.........................................................................................................915
A.10.3.8 Deleting an Ethernet LAN Service.................................................................................................................... 916
A.10.4 Managing the MAC Address Table...................................................................................................................... 917
A.10.4.1 Creating a Static MAC Address Entry...............................................................................................................917
A.10.4.2 Creating a Blacklist Entry of a MAC Address.................................................................................................. 918
A.10.4.3 Setting the Aging Time of a MAC Address Table Entry ..................................................................................918
A.10.4.4 Querying or Deleting a Dynamic MAC Address.............................................................................................. 919
A.10.4.5 Querying the Actual Capacity of a MAC Address Table.................................................................................. 919
A.10.5 Configuring Ethernet Ports................................................................................................................................... 920
A.10.5.1 Configuring External Ethernet Ports................................................................................................................. 920
A.10.5.2 Configuring VCTRUNKs on an Ethernet Board...............................................................................................922
A.10.5.3 Modifying the Type Field of QinQ Frames....................................................................................................... 924
A.10.5.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth..................................................................... 924
A.10.6 Managing the Spanning Tree Protocol................................................................................................................. 926
A.10.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol........................................................ 926
A.10.6.2 Setting the Parameters of Spanning Tree Protocol............................................................................................ 926
A.10.6.3 Querying the Running Information About the Spanning Tree Protocol............................................................927
A.10.7 Managing the IGMP Snooping Protocol.............................................................................................................. 928
A.10.7.1 Configuring the IGMP Snooping Protocol........................................................................................................ 928
A.10.7.2 Configuring Static Multicast Entries................................................................................................................. 929
A.10.7.3 Modifying the Aging Time of a Multicast Table Entry..................................................................................... 930
A.10.7.4 Querying the Running Information of the IGMP Snooping Protocol............................................................... 931
A.10.8 Managing the QoS................................................................................................................................................ 931
A.10.8.1 Creating a Flow..................................................................................................................................................931
Issue 01 (2016-04-30)

xx

Configuration Guide
Contents
A.10.8.2 Creating the CAR.............................................................................................................................................. 932

A.10.8.3 Creating the CoS................................................................................................................................................933
A.10.8.4 Binding the CAR/CoS....................................................................................................................................... 935
A.10.8.5 Configuring Traffic Shaping for Egress Queues............................................................................................... 936
A.10.8.6 Configuring Port Shaping.................................................................................................................................. 936
A.10.8.7 Setting Egress Queue Scheduling Policies........................................................................................................ 937
A.10.9 Using the Ethernet service OAM..........................................................................................................................937
A.10.9.1 Creating MDs.....................................................................................................................................................938
A.10.9.2 Creating MAs.....................................................................................................................................................939
A.10.9.3 Creating MPs..................................................................................................................................................... 939
A.10.9.4 Performing a CC Test........................................................................................................................................ 941
A.10.9.5 Performing an LB Test.......................................................................................................................................942
A.10.9.6 Performing an LT Test....................................................................................................................................... 943
A.10.9.7 Activating the AIS............................................................................................................................................. 944
A.10.9.8 Performing a Ping Test ..................................................................................................................................... 944
A.10.9.9 Performing Performance Check........................................................................................................................ 945
A.10.10 Using the Ethernet port OAM.............................................................................................................................946
A.10.10.1 Enabling the OAM Auto-Discovery Function.................................................................................................946
A.10.10.2 Enabling the Link Event Notification..............................................................................................................947
A.10.10.3 Modifying the OAM Error Frame Monitoring Threshold............................................................................... 948
A.10.10.4 Performing the Remote Loopback...................................................................................................................949
A.10.11 Configuring LPT.................................................................................................................................................950
A.10.11.1 Configuring LPT for Point-to-Point Services.................................................................................................. 950
A.10.11.2 Configuring LPT for Point-to-Multipoint Services......................................................................................... 951
A.11 Managing MPLS/PWE3 Services and Features...................................................................................................... 952
A.11.1 Managing Address Resolution..............................................................................................................................952
A.11.1.1 Creating ARP Static Entries...............................................................................................................................953
A.11.1.2 Querying ARP Entries....................................................................................................................................... 953
A.11.1.3 Converting Dynamic ARP Entries to Static ARP Entries................................................................................. 954
A.11.1.4 Deleting Static ARP Entries...............................................................................................................................954
A.11.1.5 Setting ARP Aging Time................................................................................................................................... 955
A.11.2 Managing MPLS Tunnels..................................................................................................................................... 956
A.11.2.1 Setting Basic MPLS Attributes..........................................................................................................................956
A.11.2.2 Configuring Global OAM Parameters............................................................................................................... 957
A.11.2.3 Changing the MPLS Tunnel/PW OAM Standard..............................................................................................957
A.11.2.4 Creating a Unidirectional MPLS Tunnel........................................................................................................... 958
A.11.2.5 Creating a Bidirectional MPLS Tunnel............................................................................................................. 960
A.11.2.6 Querying MPLS Tunnel Information.................................................................................................................961
A.11.2.7 Changing MPLS Tunnel Information................................................................................................................ 962
A.11.2.8 Deleting MPLS Tunnels.....................................................................................................................................963
A.11.2.9 Setting MPLS OAM (Y.1711) Parameters.........................................................................................................964
A.11.2.10 Enabling/Disabling FDI................................................................................................................................... 964
Issue 01 (2016-04-30)

xxi

Configuration Guide
Contents
A.11.2.11 Starting/Stopping CV/FFD Detection for MPLS Tunnels............................................................................... 965

A.11.2.12 Querying LSP Running Status......................................................................................................................... 966
A.11.2.13 Clearing OAM Configuration Data for MPLS Tunnel OAM (Y.1711)...........................................................967
A.11.2.14 Performing an LSP Ping Test...........................................................................................................................968
A.11.2.15 Performing an LSP Traceroute Test.................................................................................................................969
A.11.2.16 Configuring MEP Parameters for MPLS-TP Tunnel OAM............................................................................ 969
A.11.2.17 Creating MIPs of MPLS-TP Tunnel OAM......................................................................................................970
A.11.2.18 Starting a CC Test of MPLS-TP Tunnel OAM................................................................................................971
A.11.2.19 Starting an LB Test of MPLS-TP Tunnel OAM.............................................................................................. 972
A.11.2.20 Starting an LT Test Provided by MPLS-TP Tunnel OAM...............................................................................973
A.11.2.21 Testing the Delay and Delay Variation of an MPLS Tunnel............................................................................974
A.11.2.22 Setting the LCK Status of MPLS-TP Tunnel OAM........................................................................................ 975
A.11.2.23 Starting a TST Test Provided by MPLS-TP Tunnel OAM.............................................................................. 976
A.11.3 Managing MPLS APS Protection Groups............................................................................................................ 977
A.11.3.1 Creating an MPLS APS Protection Group.........................................................................................................977
A.11.3.2 Querying MPLS APS Status..............................................................................................................................979
A.11.3.3 Triggering MPLS APS Switching......................................................................................................................980
A.11.3.4 Enabling/Disabling MPLS APS Protection....................................................................................................... 981
A.11.4 Managing PWs......................................................................................................................................................982
A.11.4.1 Querying Information and Running Status of PWs........................................................................................... 982
A.11.4.2 Creating an MS-PW...........................................................................................................................................983
A.11.4.3 Setting PW OAM (Y.1711) Parameters............................................................................................................. 984
A.11.4.4 Performing a PW Ping Test................................................................................................................................985
A.11.4.5 Performing a PW Traceroute Test......................................................................................................................986
A.11.4.6 Configuring MEP Parameters for MPLS-TP PW OAM....................................................................................987
A.11.4.7 Creating MIPs of MPLS-TP PW OAM............................................................................................................. 988
A.11.4.8 Starting a CC Test of MPLS-TP PW OAM....................................................................................................... 989
A.11.4.9 Starting an LB Test of MPLS-TP PW OAM..................................................................................................... 989
A.11.4.10 Starting an LT Test Provided by MPLS-TP PW OAM....................................................................................991
A.11.4.11 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW...............................................................991
A.11.4.12 Setting the LCK Status of MPLS-TP PW OAM............................................................................................. 992
A.11.4.13 Starting a TST Test of MPLS-TP PW OAM................................................................................................... 993
A.11.5 Managing a PW APS/PW FPS Protection Group.................................................................................................994
A.11.5.1 Creating a PW APS Protection Group............................................................................................................... 995
A.11.5.2 Creating a PW FPS Protection Group................................................................................................................997
A.11.5.3 Configuring Slave Protection Pairs of PW APS................................................................................................ 999
A.11.5.4 Querying PW APS Status................................................................................................................................ 1001
A.11.5.5 Triggering PW APS Switching........................................................................................................................ 1001
A.11.5.6 Enabling/Disabling PW APS Protection..........................................................................................................1002
A.11.6 Managing CES Services..................................................................................................................................... 1003
A.11.6.1 Creating CES Services.....................................................................................................................................1003
A.11.6.2 Modifying CES Service Parameters................................................................................................................ 1006
Issue 01 (2016-04-30)

xxii

Configuration Guide
Contents
A.11.6.3 Querying CES Service Information................................................................................................................. 1006

A.11.6.4 Deleting a CES Service....................................................................................................................................1007
A.11.6.5 Calculating the Maximum Number of CES Services That an MPLS Tunnel Can Transmit...........................1008
A.11.7 Managing ATM/IMA Ports.................................................................................................................................1009
A.11.7.1 Binding ATM TRUNKs...................................................................................................................................1009
A.11.7.2 Configuring an IMA group ............................................................................................................................. 1011
A.11.7.3 Setting ATM Port Parameters.......................................................................................................................... 1011
A.11.7.4 Querying Running Status of an IMA Group....................................................................................................1012
A.11.7.5 Querying Link Running Status of an IMA Group........................................................................................... 1013
A.11.8 Managing ATM Services.................................................................................................................................... 1014
A.11.8.1 Creating ATM Services....................................................................................................................................1014
A.11.8.2 Modifying ATM Service Parameters............................................................................................................... 1016
A.11.8.3 Querying ATM Services.................................................................................................................................. 1017
A.11.8.4 Deleting an ATM Service.................................................................................................................................1017
A.11.9 ATM Traffic Management.................................................................................................................................. 1018
A.11.9.1 Creating an ATM-DiffServ Domain................................................................................................................ 1018
A.11.9.2 Modifying an ATM-Diffserv Domain..............................................................................................................1019
A.11.9.3 Creating an ATM Policy.................................................................................................................................. 1021
A.11.9.4 Modifying an ATM Policy............................................................................................................................... 1022
A.11.10 Using ATM OAM............................................................................................................................................. 1023
A.11.10.1 Enabling/Disabling the AIS/RDI Insertion Status......................................................................................... 1023
A.11.10.2 Setting Segment and End Attributes of AIS/RDI.......................................................................................... 1023
A.11.10.3 Performing a Continuity Check Test..............................................................................................................1024
A.11.10.4 Querying or Setting LLIDs............................................................................................................................ 1025
A.11.10.5 Performing an LB Test...................................................................................................................................1026
A.11.11 Managing MP Groups.......................................................................................................................................1026
A.11.11.1 Creating MP Groups...................................................................................................................................... 1026
A.11.11.2 Querying the MP Group Protocol Information.............................................................................................. 1028
A.12 Managing the Clock...............................................................................................................................................1029
A.12.1 Managing Clocks at the Physical Layer............................................................................................................. 1029
A.12.1.1 Setting the SDH Retiming Function................................................................................................................ 1029
A.12.1.2 Setting the E1 Clock Source for a Channelized STM-1 Interface Board........................................................ 1030
A.12.1.3 Configuring the Clock Sources........................................................................................................................1030
A.12.1.4 Configuring Clock Subnets..............................................................................................................................1032
A.12.1.5 User-Defined Clock Quality............................................................................................................................ 1032
A.12.1.6 Configuring the SSM Output Status................................................................................................................ 1033
A.12.1.7 Configuring the Clock ID Output Status......................................................................................................... 1034
A.12.1.8 Modifying the Parameters of the Clock Output...............................................................................................1035
A.12.1.9 Configuring Clock Sources for External Clock Output...................................................................................1035
A.12.1.10 Changing the Conditions for Clock Source Switching..................................................................................1037
A.12.1.11 Modifying the Recovery Parameter of the Clock Source.............................................................................. 1037
A.12.1.12 Querying the Clock Synchronization Status..................................................................................................1038
Issue 01 (2016-04-30)

xxiii

Configuration Guide
Contents
A.12.2 Managing CES ACR Clocks.............................................................................................................................. 1038

A.12.2.1 Configuring a CES Transmit Clock.................................................................................................................1038
A.12.2.2 Configuring the Primary Clock for an ACR Clock Domain........................................................................... 1041
A.12.2.3 Configuring Ports Using the Clock Domain....................................................................................................1042
A.12.2.4 Querying the CES ACR Clock Status............................................................................................................. 1043
A.12.3 Managing the IEEE 1588v2 Clock..................................................................................................................... 1044
A.12.3.1 Changing the Mode for Selecting the Frequency Source................................................................................ 1044
A.12.3.2 Querying or Modifying the PTP System Time................................................................................................ 1044
A.12.3.3 Setting the PTP NE Attributes......................................................................................................................... 1045
A.12.3.4 Creating PTP Clock Ports................................................................................................................................ 1046
A.12.3.5 Setting PTP Clock Port Attributes................................................................................................................... 1047
A.12.3.6 Setting Parameters for IEEE 1588v2 Clock Packets....................................................................................... 1048
A.12.3.7 Configuring the Cable Transmission Offset Between NEs............................................................................. 1048
A.12.3.8 Configuring a PTP Clock Subnet.................................................................................................................... 1049
A.12.3.9 Modifying the BMC Algorithm Parameters for NE Clocks............................................................................ 1049
A.12.3.10 Setting Basic Attributes of External Time Ports............................................................................................1050
A.12.3.11 Setting BMC Algorithm Parameters for External Time Ports....................................................................... 1051
A.12.3.12 Setting the Cable Transmission Offset for External Time Ports....................................................................1051
A.13 Ethernet Performance Query................................................................................................................................. 1052
A.13.1 Browsing Current Ethernet Performance............................................................................................................1052
A.13.2 Configuring Ethernet Performance Threshold-Crossing Parameters................................................................. 1055
A.13.3 Setting Parameters for Monitoring Historical Ethernet Performance.................................................................1058
A.13.4 Browsing Historical Ethernet Performance Data................................................................................................1059
A.14 Configuring Auxiliary Ports and Functions...........................................................................................................1062
A.14.1 Configuring Orderwire....................................................................................................................................... 1062
A.14.2 Configuring the Synchronous Data Service....................................................................................................... 1063
A.14.3 Configuring the Asynchronous Data Service..................................................................................................... 1064
A.14.4 Configuring the Wayside E1 Service..................................................................................................................1065
A.14.5 Configure External Alarms.................................................................................................................................1066
A.14.6 Monitoring the Outdoor Cabinet........................................................................................................................ 1067
A.14.6.1 Configuring the Function for an Auxiliary Port.............................................................................................. 1067
A.14.6.2 Setting the Type of the Outdoor Cabinet......................................................................................................... 1068
A.14.6.3 Querying and Setting the Temperature and Fan Information of the Outdoor Cabinet.................................... 1069
A.14.6.4 Querying and Setting the Information About the Power System of the Outdoor Cabinet.............................. 1070
A.14.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet................................................... 1071
A.14.6.6 Setting the Temperature and Humidity Alarm Thresholds for the PMU.........................................................1072
A.15 End-to-End Configuration Task Collection........................................................................................................... 1073
A.15.1 Configuring a Protection Subnet........................................................................................................................ 1073
A.15.1.1 Searching for Protection Subnets.....................................................................................................................1073
A.15.1.2 Creating a Linear MSP Protection Subnet.......................................................................................................1073
A.15.1.3 Creating a Ring MSP Protection Subnet......................................................................................................... 1074
A.15.1.4 Managing Protection Subnets.......................................................................................................................... 1075
Issue 01 (2016-04-30)

xxiv

Configuration Guide
Contents
A.15.2 Configuring TDM Services in E2E Mode.......................................................................................................... 1075

A.15.2.1 Searching for SDH Trails.................................................................................................................................1075
A.15.2.2 Creating Server Trails...................................................................................................................................... 1076
A.15.2.3 Creating Point-to-Point Service Trails.............................................................................................................1078
A.15.2.4 Creating SNCP Service Trails......................................................................................................................... 1079
A.15.2.5 Copying Service Trails.................................................................................................................................... 1081
A.15.2.6 Managing SDH Trails...................................................................................................................................... 1082
A.15.2.7 Managing Discrete TDM Services.................................................................................................................. 1083
A.15.3 Configuring Native Ethernet Services (in an End-to-End Mode).......................................................................1083
A.15.3.1 Searching for Native Ethernet Services........................................................................................................... 1084
A.15.3.2 Creating E-Line Services over Native Ethernet...............................................................................................1086
A.15.3.3 Creating an ERP Ring......................................................................................................................................1089
A.15.3.4 Creating E-LAN Services over Native Ethernet..............................................................................................1091
A.15.3.5 Verifying Native Ethernet Services................................................................................................................. 1095
A.15.3.6 Managing Native Ethernet Services................................................................................................................ 1097
A.15.3.7 Testing the Packet Loss Rate, Delay, or Delay Jitter of a Native Ethernet Service.........................................1098
A.15.3.8 Managing Discrete Services Transmitted in Native Ethernet Mode............................................................... 1099
A.15.3.9 Adjusting an E-LAN Service Network............................................................................................................ 1100
A.15.4 Searching for MPLS Tunnels and PWE3 Services.............................................................................................1102
A.15.5 Configuring MPLS Tunnels in an End-to-End Mode.........................................................................................1104
A.15.5.1 Configuring Port IP Address Resources.......................................................................................................... 1105
A.15.5.2 Creating L2 Links............................................................................................................................................ 1105
A.15.5.3 Creating Non-Protection MPLS Tunnels (in an End-to-End Mode)............................................................... 1106
A.15.5.4 Creating MPLS Tunnels Configured with MPLS APS Protection in an End-to-End Mode........................... 1111
A.15.5.5 Verifying MPLS Tunnels in an End-to-End Mode.......................................................................................... 1118
A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode......................................................................................... 1119
A.15.5.7 Managing Discrete MPLS Tunnels.................................................................................................................. 1119
A.15.5.8 Searching for MPLS APS Protection Groups..................................................................................................1120
A.15.5.9 Managing MPLS APS Protection Groups in an End-to-End Mode................................................................ 1120
A.15.5.10 Testing the Delay and Delay Variation of an MPLS Tunnel..........................................................................1121
A.15.5.11 Starting a TST Test Provided by MPLS-TP Tunnel OAM............................................................................ 1122
A.15.6 Configuring PWE3 Services in an End-to-End Mode........................................................................................ 1123
A.15.6.1 Creating PWE3 Service Templates.................................................................................................................. 1123
A.15.6.2 Configuring CES Services in an End-to-End Mode........................................................................................ 1124
A.15.6.3 Configuring an ATM Policy Profile.................................................................................................................1127
A.15.6.4 Configuring an ATM CoS Mapping Profile.....................................................................................................1128
A.15.6.5 Configuring ATM Services in an End-to-End Mode....................................................................................... 1130
A.15.6.6 Configuring PW-Based E-Line Services (in an End-to-End Mode)................................................................1132
A.15.6.7 Hybird Configuration of E-Line and E-LAN services based on PWE3.......................................................... 1134
A.15.6.8 Verifying PW Configurations in an End-to-End Mode....................................................................................1137
A.15.6.9 Verifying ATM Services in an End-to-End Mode............................................................................................1139
A.15.6.10 Verifying PW-Based Ethernet Service Configurations (in an End-to-End Mode)........................................ 1140
Issue 01 (2016-04-30)

xxv

Configuration Guide
Contents
A.15.6.11 Managing and Maintaining PWE3 Services.................................................................................................. 1143

A.15.6.12 Managing Discrete PWE3 Services............................................................................................................... 1143
A.15.6.13 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW.............................................................1144
A.15.6.14 Starting a TST Test of MPLS-TP PW OAM................................................................................................. 1145
A.15.7 Managing Ethernet Services Based on the Service Path View........................................................................... 1146
A.15.7.1 Searching for Service Paths Based on VLANs................................................................................................1146
A.15.7.2 Searching for Service Paths Based on MAC Addresses..................................................................................1148
A.15.7.3 Checking the Layer 2 Protocols Used by Ethernet Services............................................................................1149
A.15.7.4 Performing Intelligent Service Fault Diagnosis for Ethernet Services............................................................1150
A.15.7.5 Performing E-LAN Service Loopback Detection............................................................................................1152
A.15.7.6 Monitoring Ethernet Service Performance and Traffic Volume Based on Service Paths................................1153
A.15.8 Querying the Clock Tracing Relationship.......................................................................................................... 1155
B Parameters Description..........................................................................................................1158
B.1 Parameters for Network Management..................................................................................................................... 1159
B.1.1 Parameters for NE Management........................................................................................................................... 1159
B.1.1.1 Parameter Description: NE Searching (U2000).................................................................................................1159
B.1.1.2 Parameter Description: NE Searching (Web LCT)............................................................................................ 1163
B.1.1.3 Parameter Description: NE Creation (U2000)................................................................................................... 1164
B.1.1.4 Parameter Description: NE Creation (Web LCT).............................................................................................. 1168
B.1.1.5 Parameter Description: Login to an NE (Web LCT)..........................................................................................1169
B.1.1.6 Parameter Description:Changing NE IDs.......................................................................................................... 1170
B.1.1.7 Parameter Description: NE Time Synchronization (U2000)............................................................................. 1171
B.1.1.8 Parameter Description: NE Time Synchronization (Web LCT)........................................................................ 1174
B.1.1.9 Parameter Description: Localization Management of the NE Time.................................................................. 1179
B.1.1.10 Parameter Description: Standard NTP Key Management............................................................................... 1180
B.1.1.11 Parameter Description: License Management..................................................................................................1182
B.1.1.12 Parameter Description: Automatic Disabling of the Functions of NEs........................................................... 1183
B.1.2 Parameters for Communications Management..................................................................................................... 1184
B.1.2.1 Parameter Description: NE Communication Parameter Setting........................................................................ 1184
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration..............................................................1185
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management............................. 1187
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC........................................................ 1189
B.1.2.5 Parameter Description: NE ECC Link Management......................................................................................... 1191
B.1.2.6 Parameter Description: ECC Link Management_Availability Test................................................................... 1192
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management..............................................1193
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route Management Creation............................... 1194
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test....................................................... 1195
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings....................................... 1196
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP................................................................................... 1202
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas.......................................................................1202
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas....................................1203
Issue 01 (2016-04-30)

xxvi

Configuration Guide
Contents
B.1.2.14 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be Manually Aggregated
........................................................................................................................................................................................ 1205
B.1.2.15 Parameter Description: Port OSPF Setting...................................................................................................... 1205
B.1.2.16 Parameter Description: Static Route Entries in a Kernel Route Table_Creation.............................................1206
B.1.2.17 Parameter Description: DCN Management_Bandwidth Management............................................................1206
B.1.2.18 Parameter Description: DCN Management_Port Setting................................................................................ 1208
B.1.2.19 Parameter Description: DCN Management_Access Control...........................................................................1210
B.1.2.20 Parameter Description: DCN Management_Packet Control............................................................................1211
B.1.2.21 Parameter Description: L2 DCN Management................................................................................................ 1211
B.1.2.22 Parameter Description: Access Control........................................................................................................... 1212
B.1.2.23 Parameter Description: SNMP Communication.............................................................................................. 1214
B.1.2.24 Parameter Description: LLDP..........................................................................................................................1216
B.1.3 Parameters for Network Security Management.................................................................................................... 1217
B.1.3.1 Parameter Description: RADIUS Configuration_Creation............................................................................... 1217
B.1.3.2 Parameter Description: RADIUS Configuration_RADIUS Server................................................................... 1219
B.1.3.3 Parameter Description: Enabling/Disabling the RADIUS Function................................................................. 1220
B.2 Radio Link Parameters.............................................................................................................................................1221
B.2.1 Parameter Description: N+1 Protection_Create....................................................................................................1221
B.2.2 Parameter Description: N+1 Protection................................................................................................................ 1223
B.2.3 Parameter Description: IF 1+1 Protection_Create................................................................................................ 1225
B.2.4 Parameter Description: IF 1+1 Protection............................................................................................................ 1229
B.2.5 Parameter Description: Link Configuration_Creating a PLA/EPLA/EPLA+/Super EPLA Group..................... 1233
B.2.6 Parameter Description: Link Configuration_PLA/EPLA/EPLA+/Super EPLA.................................................. 1237
B.2.7 Parameter Description: Radio Link Management.................................................................................................1241
B.3 Multiplex Section Protection Parameters.................................................................................................................1247
B.3.1 Parameter Description: Linear MSP_Creation..................................................................................................... 1247
B.3.2 Parameter Description: Linear MSP..................................................................................................................... 1250
B.3.3 Parameter Description: Packet-based Linear MSP_Creation............................................................................... 1253
B.3.4 Parameter Description: Packet-based Linear MSP............................................................................................... 1255
B.3.5 Parameter Description: Ring MSP_Creation........................................................................................................ 1258
B.3.6 Parameter Description: Ring MSP........................................................................................................................1260
B.4 TDM Service Parameters......................................................................................................................................... 1261
B.4.1 Parameter Description: SDH/PDH Service Configuration_Creation................................................................... 1262
B.4.2 Parameter Description: SDH/PDH Service Configuration_SNCP Service Creation........................................... 1264
B.4.3 Parameter Description: SDH/PDH Service Configuration_Converting Normal Services Into SNCP Services.. 1268
B.4.4 Parameter Description: SDH/PDH Service Configuration................................................................................... 1271
B.4.5 Parameter Description: SNCP Service Control.................................................................................................... 1273
B.4.6 Parameter Description: TU_AIS Insertion............................................................................................................1277
B.5 Parameters for Board Interfaces...............................................................................................................................1278
B.5.1 Parameter Description: Working Modes of Ports................................................................................................. 1279
B.5.2 PDH Port Parameters............................................................................................................................................ 1279
B.5.2.1 Parameter Description: PDH Ports_Basic Attributes........................................................................................ 1279
B.5.2.2 Parameter Description: PDH Ports_Advanced Attributes................................................................................. 1281
Issue 01 (2016-04-30)

xxvii

Configuration Guide
Contents
B.5.3 Parameters for the Ports on Ethernet Boards........................................................................................................ 1284

B.5.3.1 Parameter Description: Ethernet Interface_Basic Attributes............................................................................. 1285
B.5.3.2 Parameter Description: Ethernet Interface_Flow Control................................................................................. 1289
B.5.3.3 Parameter Description: Ethernet Interface_Layer 2 Attributes..........................................................................1291
B.5.3.4 Parameter Description: Ethernet Port_Layer 3 Attributes................................................................................. 1292
B.5.3.5 Parameter Description: Ethernet Interface_Advanced Attributes......................................................................1293
B.5.4 Serial Port Parameters...........................................................................................................................................1299
B.5.4.1 Parameter Description: Serial Port_Basic Attributes.........................................................................................1299
B.5.4.2 Parameter Description: Serial Port_Creation of Serial Ports............................................................................. 1301
B.5.5 Channelized STM-1 Port Parameters....................................................................................................................1302
B.5.5.1 Parameter Description: Clock Transparent Transmission..................................................................................1302
B.5.5.2 Parameter Description: Path Configuration....................................................................................................... 1303
B.5.6 Microwave Interface Parameters.......................................................................................................................... 1306
B.5.6.1 Parameter Description: Microwave Interface_Basic Attributes........................................................................ 1306
B.5.6.2 Parameter Description: Microwave Interface_Layer 2 Attributes.....................................................................1308
B.5.6.3 Parameter Description: Microwave Interface_Layer 3 Attributes.....................................................................1310
B.5.6.4 Parameter Description: Microwave Interface_Advanced Attributes................................................................. 1311
B.5.7 IF Board Parameters............................................................................................................................................. 1313
B.5.7.1 Parameter Description: IF Interface_IF Attribute..............................................................................................1313
B.5.7.2 Parameter Description: IF Interface_ATPC Attribute........................................................................................1320
B.5.7.3 Parameter Description: IF Port_Advanced Attributes....................................................................................... 1321
B.5.7.4 Parameter Description: ATPC Adjustment Records.......................................................................................... 1322
B.5.8 RFU/ODU Parameters.......................................................................................................................................... 1323
B.5.8.1 Parameter Description: RFU/RFU-SD/ODU Interface_Radio Frequency Attribute.........................................1323
B.5.8.2 Parameter Description: RFU/RFU-SD/ODU Interface_Power Attributes........................................................ 1326
B.5.8.3 Parameter Description: RFU/RFU-SD/ODU Interface_Equipment Information..............................................1330
B.5.8.4 Parameter Description: ODU Interface_Advanced Attributes...........................................................................1332
B.5.9 Parameters for SDH Interface Boards...................................................................................................................1333
B.5.9.1 Parameter Description: SDH Interfaces.............................................................................................................1333
B.5.9.2 Parameter Description: Automatic Laser Shutdown..........................................................................................1335
B.5.10 Parameters for PDH Interface Boards.................................................................................................................1335
B.5.10.1 Parameter Description: PDH Ports.................................................................................................................. 1335
B.5.11 Parameters for Overhead.....................................................................................................................................1339
B.5.11.1 Parameter Description: Regenerator Section Overhead...................................................................................1339
B.5.11.2 Parameter Description: VC-4 POHs................................................................................................................ 1340
B.5.11.3 Parameter Description: VC-12 POHs.............................................................................................................. 1342
B.5.12 Parameter Description: Ethernet Virtual Interfaces............................................................................................ 1343
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane.........................................................1347
B.6.1 Parameters for Ethernet Services.......................................................................................................................... 1347
B.6.1.1 Parameter Description: E-Line Service_Creation (U2000)............................................................................... 1347
B.6.1.2 Parameter Description: E-Line Service_Creation(Web LCT)........................................................................... 1368
B.6.1.3 Parameter Description: E-Line Service..............................................................................................................1392
Issue 01 (2016-04-30)

xxviii

Configuration Guide
Contents
B.6.1.4 Parameter Description: VLAN Forwarding Table Items for E-Line Services_Creation................................... 1403
B.6.1.5 Parameter Description: E-LAN Service_Creation (U2000).............................................................................. 1404
B.6.1.6 Parameter Description: E-LAN Service_Creation(Web LCT).......................................................................... 1414
B.6.1.7 Parameter Description: E-LAN Service(U2000)............................................................................................... 1425
B.6.1.8 Parameter Description: E-LAN Service(Web LCT).......................................................................................... 1439
B.6.1.9 Parameter Description: QinQ Link_Creation.................................................................................................... 1453
B.6.1.10 Parameter Description: E-AGGR Services_Creation...................................................................................... 1454
B.6.1.11 Parameter Description: E-AGGR Services...................................................................................................... 1461
B.6.2 Parameters for Ethernet Protocols........................................................................................................................ 1467
B.6.2.1 Parameter Description: ERPS Management_Creation...................................................................................... 1467
B.6.2.2 Parameter Description: ERPS Management...................................................................................................... 1470
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation................................................................. 1483
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration........................................................ 1484
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters................................................................... 1485
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters...................................................................... 1490
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST..................................... 1492
B.6.2.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration.............................................1500
B.6.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted......................... 1504
B.6.2.10 Parameter Description: IGMP Snooping Configuration_Route Management................................................ 1505
B.6.2.11 Parameter Description: IGMP Snooping Configuration_Static Router Port Creation.....................................1506
B.6.2.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management.......................... 1507
B.6.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation.............. 1508
B.6.2.14 Parameter Description: IGMP Snooping Configuration_Data Count............................................................. 1509
B.6.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation..........................................1511
B.6.2.16 Parameter Description: Ethernet Link Aggregation_Link Aggregation.......................................................... 1518
B.6.2.17 Parameter Description: LPT Management_Creating Simple LPT.................................................................. 1519
B.6.2.18 Parameter Description: LPT Management_Point-to-Point LPT......................................................................1520
B.6.2.19 Parameter Description: LPT Management_Creating Point-to-Point LPT....................................................... 1522
B.6.2.20 Parameter Description: LPT Management_Point-to-Multipoint LPT............................................................. 1523
B.6.2.21 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT.............................................. 1526
B.6.3 Parameters for the Ethernet OAM........................................................................................................................ 1530
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation........................1530
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation..................1531
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation..................................................1532
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation.................................... 1533
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation................................................... 1534
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling.................................................... 1535
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling.....................................................1536
B.6.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback Detection..................................1538
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter....................................................1539
B.6.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring........................... 1542
B.6.4 QoS Parameters.....................................................................................................................................................1543
Issue 01 (2016-04-30)

xxix

Configuration Guide
Contents
B.6.4.1 Parameter Description: DiffServ Domain Management.................................................................................... 1543

B.6.4.2 Parameter Description: DiffServ Domain Management_Create....................................................................... 1549
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification............................................................. 1555
B.6.4.4 Parameter Description: Policy Management..................................................................................................... 1556
B.6.4.5 Parameter Description: Port Policy....................................................................................................................1560
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration........................................................ 1568
B.6.4.7 Parameter Description: Port Shaping Management_Creation........................................................................... 1578
B.6.4.8 Parameter Description: Port WRED Policy_Create.......................................................................................... 1579
B.6.4.9 Parameter Description: Service WRED Policy_Create..................................................................................... 1580
B.6.4.10 Parameter Description: WRR Scheduling Policy_Create................................................................................1582
B.6.4.11 Parameter Description: V-UNI Egress Policy..................................................................................................1583
B.6.4.12 Parameter Description: PW Policy.................................................................................................................. 1591
B.6.4.13 Parameter Description: QinQ Policy............................................................................................................... 1599
B.6.5 Parameter Description: IP Packet Marking and Statistics Collection...................................................................1607
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane............................................... 1612
B.7.1 Parameters for Ethernet Services.......................................................................................................................... 1612
B.7.1.1 Parameter Description: Ethernet Line Service_Creation................................................................................... 1612
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services.........................1616
B.7.1.3 Parameter Description: Ethernet Line Service...................................................................................................1627
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/
802.1q Bridge................................................................................................................................................................. 1630
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service
........................................................................................................................................................................................ 1633
B.7.1.6 Parameter Description: Ethernet LAN Service..................................................................................................1638
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation.................................................................................. 1645
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries................................................................1646
B.7.2 Parameters for Ethernet Protocols........................................................................................................................ 1646
B.7.2.1 Parameter Description: ERPS Management_Creation...................................................................................... 1646
B.7.2.2 Parameter Description: ERPS Management...................................................................................................... 1649
B.7.2.3 Parameter Description: Spanning Tree_Protocol Enabling............................................................................... 1658
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters...............................................................................1659
B.7.2.5 Parameter Description: Spanning Tree_Port Parameters...................................................................................1660
B.7.2.6 Parameter Description: Spanning Tree_Bridge Running Information...............................................................1662
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information...................................................................1663
B.7.2.8 Parameter Description: Spanning Tree_Point-to-Point Attribute...................................................................... 1664
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling............................................................................ 1665
B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries...................... 1666
B.7.2.11 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries........................... 1667
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs..........................................................1668
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation.......................................................... 1670
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT......................................1671
B.7.2.15 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT............................. 1673
B.7.2.16 Parameter Description: Port Mirroring_Creation............................................................................................ 1674
Issue 01 (2016-04-30)

xxx

Configuration Guide
Contents
B.7.3 Parameters for the Ethernet OAM........................................................................................................................ 1675

B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs....................................................................1675
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs....................................................................1676
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs.................................................................... 1676
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB.......................................................................... 1679
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT...........................................................................1680
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter..........................................................................1681
B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring...................................................1682
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter............................................................ 1683
B.7.4 QoS Parameters.....................................................................................................................................................1684
B.7.4.1 Parameter Description: QoS Management_Creation of Flows..........................................................................1684
B.7.4.2 Parameter Description: QoS Management_Creation of CAR........................................................................... 1686
B.7.4.3 Parameter Description: QoS Management_Creation of CoS.............................................................................1688
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS................................................................... 1690
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues.......................................1691
B.7.4.6 Parameter Description: QoS Management_Port Shaping..................................................................................1693
B.7.5 Parameters for the Ports on Ethernet Boards........................................................................................................ 1694
B.7.5.1 Parameter Description: Ethernet Port_External Port......................................................................................... 1694
B.7.5.2 Parameter Description: Ethernet Port_Internal Port.......................................................................................... 1701
B.7.5.3 Parameter Description: Type Field of QinQ Frames......................................................................................... 1707
B.8 Parameters for MPLS/PWE3 Services.....................................................................................................................1708
B.8.1 MPLS Tunnel Parameters..................................................................................................................................... 1708
B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels...................................................................... 1708
B.8.1.2 Parameter Description: MPLS Basic Configuration_Global OAM Parameters................................................1710
B.8.1.3 Parameter Description: Unicast Tunnel Management_Static Tunnel................................................................ 1711
B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels............................. 1716
B.8.1.5 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels................................1721
B.8.1.6 Parameter Description: Unicast Tunnel Management_OAM Parameters......................................................... 1726
B.8.1.7 Parameter Description: Unicast Tunnel Management_FDI...............................................................................1732
B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Ping...................................................................... 1732
B.8.1.9 Parameter Description: Unicast Tunnel Management_LSP Traceroute............................................................ 1735
B.8.1.10 Parameter Description: Unicast Tunnel Management_MEP Management..................................................... 1738
B.8.1.11 Parameter Description: Unicast Tunnel Management_Creating Tunnel MIPs................................................1743
B.8.1.12 Parameter Description: Unicast Tunnel Management_Enabling an LB Test.................................................. 1744
B.8.1.13 Parameter Description: PW Management_PW Management..........................................................................1746
B.8.1.14 Parameter Description: PW Management_MS-PW Creation..........................................................................1752
B.8.1.15 Parameter Description: PW Management_PW OAM..................................................................................... 1763
B.8.1.16 Parameter Description: PW Management_PW Ping....................................................................................... 1768
B.8.1.17 Parameter Description: PW Management_PW Traceroute..............................................................................1771
B.8.1.18 Parameter Description: PW Management_MEP Management........................................................................1773
B.8.1.19 Parameter Description: PW Management_Creating MIPs.............................................................................. 1777
B.8.1.20 Parameter Description: PW Management_Enabling an LB............................................................................ 1778
Issue 01 (2016-04-30)

xxxi

Configuration Guide
Contents
B.8.1.21 Parameter Description: MPLS APS Protection Management......................................................................... 1780

B.8.1.22 Parameter Description: Tunnel Protection Group_Creation............................................................................ 1784
B.8.1.23 Parameter Description: PW APS Protection Group_Creation.........................................................................1789
B.8.1.24 Parameter Description: PW FPS Protection Group_Creation......................................................................... 1800
B.8.1.25 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation............................... 1808
B.8.2 Parameter Description: VPLS Management......................................................................................................... 1814
B.8.3 CES Parameters.................................................................................................................................................... 1815
B.8.3.1 Parameter Description: CES Service Management........................................................................................... 1815
B.8.3.2 Parameter Description: CES Service Management_Creation............................................................................1825
B.8.4 ATM Parameters................................................................................................................................................... 1842
B.8.4.1 Parameter Description: ATM IMA Management_IMA Group Management....................................................1842
B.8.4.2 Parameter Description: ATM IMA Management_Bound Path Configuration.................................................. 1846
B.8.4.3 Parameter Description: ATM IMA Management_IMA Group Status...............................................................1848
B.8.4.4 Parameter Description: ATM IMA Management_IMA Link Status................................................................. 1849
B.8.4.5 Parameter Description: ATM IMA Management_ATM Interface Management............................................... 1850
B.8.4.6 Parameter Description: Configuration of ATM Service Class Mapping Table................................................. 1852
B.8.4.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation..................................1853
B.8.4.8 Parameter Description: ATM Policy Management............................................................................................ 1855
B.8.4.9 Parameter Description: ATM Policy Management_Creation............................................................................ 1859
B.8.4.10 Parameter Description: ATM Service Management........................................................................................ 1864
B.8.4.11 Parameter Description: ATM Service Management_Creation.........................................................................1874
B.8.4.12 Parameter Description: ATM OAM Management_Segment and End Attributes............................................1886
B.8.4.13 Parameter Description: ATM OMA Management_CC Activation Status....................................................... 1890
B.8.4.14 Parameter Description: ATM OAM Management_Remote End Loopback Status......................................... 1894
B.8.4.15 Parameter Description: ATM OAM Management_LLID................................................................................1897
B.8.4.16 Parameter Description: ATM OAM_ATM Cell Insertion Status.....................................................................1898
B.8.5 MP Group Parameters...........................................................................................................................................1899
B.8.5.1 Parameter Description: MP Group Management_Creation............................................................................... 1899
B.8.5.2 Parameter Description: MP Group Management_Basic Attributes...................................................................1902
B.9 Clock Parameters..................................................................................................................................................... 1906
B.9.1 Parameter Description: Frequency Selection Mode..............................................................................................1906
B.9.2 Physical Clock Parameters....................................................................................................................................1906
B.9.2.1 Parameter Description: Clock Source Priority Table.........................................................................................1906
B.9.2.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port.......................... 1910
B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet............................................................................ 1912
B.9.2.4 Parameter Description: Clock Subnet Setting_Clock Quality........................................................................... 1915
B.9.2.5 Parameter Description: Clock Subset Setting_SSM Output Control.................................................................1918
B.9.2.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status......................................................... 1919
B.9.2.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters.................................1920
B.9.2.8 Parameter Description: Clock Source Switching_Clock Source Switching......................................................1922
B.9.2.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions................................... 1923
B.9.2.10 Parameter Description: Output Phase-Locked Source of the External Clock Source..................................... 1925
Issue 01 (2016-04-30)

xxxii

Configuration Guide
Contents
B.9.2.11 Parameter Description: Clock Synchronization Status.................................................................................... 1927

B.9.3 CES ACR Clock Parameters.................................................................................................................................1930
B.9.3.1 Parameter Description: ACR Clock Source.......................................................................................................1930
B.9.3.2 Parameter Description: Clock Domain.............................................................................................................. 1930
B.9.3.3 Parameter Description: Clock Domain_Creation.............................................................................................. 1931
B.9.4 PTP Clock Parameters.......................................................................................................................................... 1932
B.9.4.1 Parameter Description: Clock Synchronization Attribute................................................................................. 1932
B.9.4.2 Parameter Description: Clock Synchronization Attribute_Creation of PTP Clock Ports..................................1945
B.9.4.3 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet............................................................. 1945
B.9.4.4 Parameter Description: Setting of a PTP Clock Subnet_BMC..........................................................................1946
B.9.4.5 Parameter Description: External Time Port_Basic Attributes........................................................................... 1947
B.9.4.6 Parameter Description: External Time Port_BMC............................................................................................ 1949
B.9.4.7 Parameter Description: External Time Port_Cable Transmission Distance...................................................... 1950
B.9.5 Parameter Description: Auxiliary Ports................................................................................................................ 1951
B.10 Parameters for the Orderwire and Auxiliary Interfaces......................................................................................... 1952
B.10.1 Parameter Description: Orderwire_General........................................................................................................1953
B.10.2 Parameter Description: Orderwire_Advanced.................................................................................................... 1954
B.10.3 Parameter Description: Orderwire_F1 Data Port................................................................................................1955
B.10.4 Parameter Description: Orderwire_Broadcast Data Port.................................................................................... 1956
B.10.5 Parameter Description: Environment Monitoring Interface............................................................................... 1956
C Glossary.................................................................................................................................... 1960
Issue 01 (2016-04-30)

xxxiii

Configuration Guide
1 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 01 (2016-04-30)


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


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

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

functions
End
Required
Optional
Issue 01 (2016-04-30)


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

l EoS and EoPDH services are not supported.
l MPLS packet services can only be ETH PWE3 services and CES services carried over MPLS tunnels.
l The auxiliary port supports only asynchronous data services and external alarms.
For OptiX RTN 910A, there are the following exceptions:
l EoS and EoPDH services are not supported.
Table 2-1 describes the procedure in the configuration flowchart.

Table 2-1 Initial configuration
Operation
Description
5 Configuring the Network Topology
Required.
6 Configuring Microwave Links
Required.
7 Configuring TDM Services
Required when TDM services need to be

transmitted.
8 Configuring Native Ethernet Services
Required when Native Ethernet services need

to be transmitted.
9 Configuring Ethernet Services on

EoS/EoPDH Boards
Required when Ethernet services on the EoS/

EoPDH boards need to be transmitted.
Configuring MPLS
packet services
Required when MPLS packet services need to

be transmitted.
10 Configuring
MPLS Tunnels
11 Configuring
ETH PWE3
Services
12 Configuring
CES Services
13 Configuring
ATM Services
14 Configuring the Clock
Required.
15 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 2-1 is for reference only and needs to be adjusted as required
in actual application scenarios.
Issue 01 (2016-04-30)


Configuration Guide
Network Adjustment
Network adjustment involves adding and adjusting configuration data in the equipment
commissioning and operation phases. You can find the corresponding configuration
operations according to the actual network adjustment requirements in Table 2-2.
Table 2-2 Network adjustment
Issue 01 (2016-04-30)
Operation
Description
16.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.
16.2 Common Task Collection (Radio

Links)

configuration operations associated with radio
links, including changing the working mode of
a TDM radio link and changing the number of
E1s on a Hybrid radio link.
16.3 Common Task Collection (TDM

Services)

configuration operations associated with TDM
services, including deleting TDM services and
upgrading a normal service to an SNCP
service.
16.4 Common Task Collection (Native

Ethernet Services)

configuration operations associated with
Native Ethernet services, including setting or
modifying Ethernet port parameters and
deleting Ethernet services.
16.5 Common Task Collection

(Ethernet Services on the EoS/EoPDH
Plane)

Ethernet services on the EoS/EoPDH boards,
including setting or modifying Ethernet port
parameters and deleting Ethernet services.
16.6 Common Task Collection (MPLS/

PWE3 Services)

packet services, including setting or modifying
packet service parameters and deleting packet
services.


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

Examples
About This Chapter

To better describe the initial configuration method for OptiX RTN 900, most configuration
examples in this document are based on the following three networking scenarios. The other
configuration examples are based on special networking scenarios and are for special
application scenarios.
3.1 Hybrid Microwave Chain Network
A Hybrid microwave chain network can receive various base station services and directly
transmits the services to packet GE rings on a packet network.
3.2 Hybrid Microwave Ring Network
A Hybrid microwave ring network can receive various base station services and directly
3.3 Packet Network
The packet network receives base station services through a packet microwave chain and
various base stations services through a packet ring network.
Issue 01 (2016-04-30)


Configuration Guide
3.1 Hybrid Microwave Chain Network

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


Configuration Guide
Figure 3-2 Board configuration of NEs on a Hybrid microwave chain network

NE13
CSHO
ISV3
NE6
ISV3
FE
NE14
R4
BTS12
RTN 905 2E
E1
GE+E1
ISV3
ISV3
NE11
PIU
RTN 950A
RTN 950A
R99
BTS13
NE12
CSHO
ISV3
NE6
ISV3
FE
PIU
CSHN
R4
BTS11
ISV3
ISV3
RTN 980
SP3S
E1 GE
NE15
CSHO
NE16
NE6
ISV3
RTN 905 1E
FE
RNC
ISV3
ISV3
RTN 950A
E1
R99
BTS14
R4
BTS15
3.2 Hybrid Microwave Ring Network

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


Configuration Guide
Figure 3-3 Hybrid microwave ring network
U2000
E1
LAN switch
BSC
GE
RNC
NE21
RTN 950A
R4 FE
BTS21
E1
BTS22
FE
NE25
NE22
RTN 905 2E
R4
BTS24
RTN 910A
NE23
RTN 905 1E
NE24
RTN 905 1E
FE
R4
BTS23
Figure 3-4 shows the board configurations for each NE.
Issue 01 (2016-04-30)


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

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

10

Configuration Guide
Figure 3-5 Topology of the packet network

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

11

Configuration Guide
Figure 3-6 Board configuration on the packet network

BTS32
NE35
RTN 950A
NE36
FE FE
CSHO
ISV3
ISV3
NE6
ISV3
RTN 905 1E
R4
NE32
RTN 980
PIU
NE33
RTN 980
PIU
PIU
GE
PIU
CSHN
ISV3
ISV3
EG4
NE31
RTN 950
CSH
NE34
RTN 980
CSHN
ML1
PIU
PIU
CSH
NE6
EG4
ML1
GE
E1
RNC
CSHN
BSC
ML1
NOTE
l On the network, NE32, NE33, and NE34 use OptiX RTN 980, NE31 uses OptiX RTN 950, NE35 uses
OptiX RTN 950A, and NE36 uses OptiX RTN 905 1E. To provide the complete configurations of packet
services, this document describes the configurations of all NEs.
l A LAG in configured for the GE port connected to the RNC for protection.
Issue 01 (2016-04-30)

12

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

and Scenarios
Configuration examples in this manual cover all initial configuration operations mentioned in
Networking Scenarios of Configuration Examples, as well as the special configuration
examples, which are based on special configuration scenarios.
This table lists the configuration examples related to each scenario, to facilitate querying of
the mapping between configuration examples and scenarios in this manual.
Issue 01 (2016-04-30)
Initial
Configuration
Hybrid
Microwave
Chain
Network
Hybrid
Microwave
Ring Network
Packet
Network
Special
Scenario
Configuring the
network
topology
Configuring
the network
topology
Configuring
the network
topology
Configuring
the network
topology
Configuring
microwave
links
Configuring
microwave
links
Configuring
microwave
links
Configuring
microwave
links
Configuring
TDM services
Configuring
TDM services
Configuring
TDM services
Configuring
Native Ethernet
services
Configuring
point-to-point
transparently
transmitted ELine services
Configuring
VLAN-based
E-Line services
Configuring
QinQ-based ELine services

13

Configuration Guide
Initial
Configuration
Configuring
Ethernet
services on the
EoS/EoPDH
boards
NOTE
OptiX RTN
905/910A does
not support this
configuration.
Configuring
MPLS tunnels
Issue 01 (2016-04-30)
Hybrid
Microwave
Chain
Network
Hybrid
Microwave
Ring Network
Packet
Network
Special
Scenario
Configuring
IEEE 802.1D
bridge-based
E-LAN
services
Configuring
IEEE 802.1q
bridge-based
E-LAN
services
Configuring
802.1ad
bridge-based
E-LAN
services
Configuring
Ethernet
services
transmitted
over TDM
microwave
Configuring
Ethernet
Services
Traversing a
TDM Network
Configuring
MPLS tunnels
with MPLS AP
protection
Configuring
unprotected
MPLS tunnels
Configuring
MPLS tunnels
traversing a
Layer 2
network
Configuring
MPLS tunnels
traversing a
TDM network

14

Configuration Guide
Initial
Configuration
Hybrid
Microwave
Chain
Network
Hybrid
Microwave
Ring Network
Packet
Network
Special
Scenario
Configuring
ETH PWE3
services
Configuring ELine services

carried by SSPWs
Configuring ELine services

carried by MSPWs
Configuring ELine and ELAN services

carried by
PWs
Configuring EAggr services

carried by
PWs
Configuring
CES services
based on
CESoPSN
encapsulation
Configuring
CES services
based on
SAToP
encapsulation
Configuring
CES services
that
transparently
transmit
STM-1s
Configuring
ATM services
based on ATM
connections
Configuring
ATM ports to
transparently
transmit
services
Configuring
CES services
Configuring
ATM services
NOTE
OptiX RTN 905
does not support
this
configuration.
Issue 01 (2016-04-30)

15

Configuration Guide
Initial
Configuration
Hybrid
Microwave
Chain
Network
Hybrid
Microwave
Ring Network
Packet
Network
Special
Scenario
Configuring the
clock
Configuring
clock for a
Hybrid
microwave
chain network
Configuring
clock for a
Hybrid
microwave
ring network
Configuring
clock for a
packet
network
Configuring
orderwire
Configuring
auxiliary ports
and
environment
monitoring
functions
NOTE
OptiX RTN 905
does not support
this
configuration.
Configuring
synchronous
data services
NOTE
OptiX RTN 905
does not support
this
configuration.
Issue 01 (2016-04-30)
Configuring
asynchronous
data services
Configuring
bypass E1
services
Configuring
external
alarms
Configuring
the monitoring
of outdoor
cabinets

16

Configuration Guide
Configuring the Network Topology
About This Chapter

You can manage a transport network by using the U2000 only after configuring the network
topology on the network.
5.1 Basic Concepts
Before configuring the network topology, you need to be familiar with the basic concepts.
5.2 Configuration Process
This section provides the process for configuring NEs, DCN channels, fibers/cables, and
subnets.
5.3 Configuration Example (Network Topology of a Hybrid Microwave Chain Network)
This example assumes that DCN communication is normal on the Hybrid microwave chain
network.
5.4 Configuration Example (Network Topology of a Hybrid Microwave Ring Network)
This example assumes that DCN communication is normal on the Hybrid microwave ring
network.
5.5 Configuration Example (Network Topology for a Packet Network)
This example assumes that DCN communication is normal on the packet network.
Issue 01 (2016-04-30)

17

Configuration Guide
5.1 Basic Concepts

Before configuring the network topology, you need to be familiar with the basic concepts.
5.1.1 DCN
To manage and maintain an NE, the U2000 needs to communicate with the NE through the
data communication network (DCN).
On a DCN, the NMS and all the NEs are considered as nodes. The DCN between the NMS
and all the NEs is considered as the external DCN, and the DCN between the NEs is
considered as the internal DCN. The OptiX RTN 900 supports the HWECC and IP DCN
solutions. IP DCN is the commonest DCN solution.
IP DCN is a DCN solution provided by Huawei. In this solution, DCN packets are
encapsulated using the standard IP protocol stack and transmitted over DCN channels
between NEs as IP packets, so that the NMS can manage the NEs.
Figure 5-1 shows how DCN packets are transmitted in the IP DCN solution. Different
vendors' DCN packets can be transmitted over the following DCN channels:
l
DCCs over SDH lines/SDH microwave/Integrated IP microwave
Ethernet service channels over Integrated IP microwave or FE/GE links
Ethernet NMS ports or NE cascade ports
DCCs over IF/TDM cascade ports
Figure 5-1 IP DCN solution
3rd-party Msg
IP stack
NM-ETH
Third-party NMS
OptiX Msg
IP stack
DCC
3rd-party Msg
IP stack
NM-ETH
3rd-party Msg
IP stack
DCC
NM
NM
NM
OptiX NMS
OptiX Msg
IP stack
NM-ETH
OptiX equipment
Ethernet link
Issue 01 (2016-04-30)
OptiX Msg
IP stack
Inband DCN
GE
GE
OptiX Msg
IP stack
Inband DCN
OptiX Msg
IP stack
Inband DCN
Third-party equipment
Radio link

18

Configuration Guide
5.1.2 GNE and Non-GNE

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

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

19

Configuration Guide
5.1.4 Logical Board

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

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

5 + ISM6 in slot 7 + EG6 in
slot 8 + MP1 in slot 9
RTN 950A
CSHO
PIU in slot 9 + CSHO in slot

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

in slot 16 + EG2D in slot
17
l CSHN in slot 20 +SL4D
in slot 21 + EG2D in slot
22
RTN 980
CSHNA
l CSHNA in slot 15
+SL4D in slot 16 + EG4
in slot 17
l CSHNA in slot 20
+SL4D in slot 21 + EG4
in slot 22
Issue 01 (2016-04-30)

20

Configuration Guide
NE Type
Physical Board
ODU
Logical Board
For single-IF boards:
l The logical slot ID of an
OptiX RTN 910A/
950/950A ODU is the
logical slot ID of the IF
board that is connected
to the ODU plus 20.
l The logical slot ID of an
OptiX RTN 980 ODU is
the logical slot ID of the
IF board that is
connected to the ODU
plus 50.
For dual-IF boards:
l The logical slot ID of the
OptiX RTN 910A/
950/950A ODU
connected to the first IF
port is the logical slot ID
of the IF board plus 20.
The logical slot ID of the
OptiX RTN 980 ODU
port is the logical slot ID
of the IF board plus 50.
l The logical slot ID of the
OptiX RTN 910A, 950,
950A, or 980 ODU
connected to the second
IF port is the logical slot
ID of the ODU
port plus 20.
NOTE
On RTN 950A, a logical board SL1D can be switched to a logical board CD1, and a logical board SP3S can
be switched to a logical board MP1.
On RTN 950A, an MN1 board must be installed before CES services are configured on a logical board MP1
or CD1.
Logical Board of OptiX RTN 905

OptiX RTN 905 IDU is an integrated chassis with only one system board, as shown in the
following figure.
Issue 01 (2016-04-30)

21

Configuration Guide
Figure 5-2 Logical board layout of the OptiX RTN 905 IDU
IDU 905 1E
PIU
ISV3
CSHP
AUX
EG6
Slot 5
Slot 3
Slot 1
Slot 10
Slot 7
VS2/
EG2
Slot 8
MP1
Slot 9
CD1
MN1
FAN
Slot 15 Slot 16 Slot 6
IDU 905 2E
PIU
ISV3
ISV3
CSHP
AUX
EG6
Slot 5
Slot 4
Slot 3
Slot 1
Slot 10
Slot 7
VS2/
EG2
Slot 8
MP1
Slot 9
CD1
MN1
FAN
Slot 15 Slot 16 Slot 6
The slot ID for the logical board of an ODU equals 20 plus the slot ID of the IF board
connected to the ODU.
By default, slot 8 of an OptiX RTN 905 IDU is configured with a VS2 logical board. If the
COMBO interface functions as a GE interface, the VS2 board must be changed into an EG2
board.
Logical Board of an Outdoor Cabinet

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

You can obtain the clear fiber/cable connection relations between NEs by using the fiber
management function of the U2000. You can manage the fibers and cables by using the
U2000, including SDH fibers, radio links, Ethernet fibers/cables, extended ECC cables, and
back-to-back radio connections.
l
SDH fibers
SDH fibers refer to the fiber connections between different sets of equipment. That is,
SDH fibers indicate the connection relations between different SDH optical ports.
For the OptiX RTN 905, connection between TDM cascading ports is also indicated by
SDH fibers.
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.
Issue 01 (2016-04-30)

22

Configuration Guide
NOTE
Fibers and cables are topological objects on the U2000. Hence, operations on the fibers or cables do not affect
the normal running of the NEs.
5.1.6 Subnet
NEs in a same domain or with similar attributes can be allocated to a same subnet. In this
way, they can be displayed as a whole on the U2000, thus facilitating the NE management.
The subnets are topological objects on the U2000. Hence, operations on the subnets do not
affect the normal running of the NEs. In the case of a large number of topological objects,
subnets that contain multiple NEs simplify the topology view on the U2000.

This section provides the process for configuring NEs, DCN channels, fibers/cables, and
subnets.
Figure 5-3 shows the process for configuring the network topology.
Figure 5-3 Configuration flowchart (network topology)
Start
Creating NEs
Configuring NE attributes
Configuring DCCs
Synchronizing NE time
Setting the performance

monitoring status
Required
Optional
Issue 01 (2016-04-30)
Creating fibers/cables and

subnets
End

23

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

Table 5-2 Creating NEs
Step
Operation
Creating NEs
on the
integrated
NMS.
Remarks
Manually
Creating NEs
(U2000) or
Manually
Creating NEs
(Web LCT)
Recommended when one or more NEs need

to be added on a large-scale network.
If the NMS and the gateway NE
communicates using SSL, set Connection
Mode to Security SSL.
Creating NEs
by Using the
Search
Method
(U2000) or
Creating NEs
by Using the
Search
Method (Web
LCT)
Recommended in other cases.
A.3.2.1 Uploading the NE Data

(U2000)
If you select Upload after create during A.

3.1.1 Creating NEs by Using the Search
Method (U2000), skip this operation.
NOTE
The NE creation steps on the Web LCT are different from those on the U2000.
1. Operations in A.3.2.1 Uploading the NE Data (U2000) are not necessary.
2. If an NE is created but has not been logged in to, perform operations in A.3.1.5 Logging In to an NE
(Web LCT).
Issue 01 (2016-04-30)

24

Configuration Guide
Table 5-3 Configuring NE attributes

Step
Operation
Remarks
A.3.1.9
Changing
the NE ID
Required.
A.3.1.10
Changing
the NE
Name
Optional.
A.3.1.6
Configuring
the Logical
Board
Required. Set a logical board for the ODU based on the

ODU connections.
Configuring
an SFP Port
Required.
For OptiX RTN 980, manually set the SFP module type for
the SL4D board (a logical board) according to the actual
board.
It is recommended that you delete the SFP port for which

no SFP module is installed. If the type of the installed SFP
module differs from the default module type of the port,
delete the port, and add a new port for which the SFP
module type is set to the actual module type. The default
SFP module type for an Ethernet port is a Gigabit Ethernet
(GE) optical module and the default SFP module type for an
SDH port is a Synchronous Transport Module level 1
(STM-1) optical module.
Table 5-4 Configuring DCCs

Step
Operation
Remarks
A.3.7.1
Setting NE
IP
Communica
tion
Parameters
Required.
A.3.7.2
Configuring
DCCs
Optional.
Issue 01 (2016-04-30)
NOTE
If the IP address of an NE has not been 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-gateway NE does not
need to be changed manually.

25

Configuration Guide
Step
Operation
Remarks
A.3.7.4
Configuring
the VLAN
ID and
Bandwidth
Used by an
Inband
DCN
Perform this operation if the VLAN ID and bandwidth

planned for the inband DCN do not take their default
values. (The default VLAN ID is 4094 and the default
bandwidth is 512 kbit/s.)
A.3.7.6
Configuring
Inband
DCN Ports
If a few PPPoE packets sent by an Ethernet port connected

to a base station have impact on the base station, the inband
DCN function must be disabled on this Ethernet port.
NOTE
You can set the VLAN ID of the inband DCN based on NEs.
NOTE
l The inband DCN function is enabled on an RTN's Ethernet port
by default. Therefore, this port periodically sends a few PPPoE
packets that carry the inband DCN VLAN ID (default VLAN
ID: 4094) even if the interconnected base station cannot
recognize these packets. These packets have no impact on the
base station so long as the base station proactively discards the
packets.
l You can set the ports where inband DCN needs to be enabled
on ports.
Table 5-5 Synchronizing NE time
Issue 01 (2016-04-30)
Step
Operation
Synchroni
ze NE
time.
Remarks
Synchron
izing NE
Time
(U2000)
or
Synchron
izing NE
Time
(Web
LCT)
Required.
A.3.1.14
Localizin
g the NE
Time
Required if the DST scheme for the local area is

used.

26

Configuration Guide
Step
Operation
Remarks
A.3.1.15
Configuri
ng
Standard
NTP
Keys
Required if the NTP authentication is used to

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

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

functions are Disabled, start the functions manually.
Table 5-7 Creating fibers/cables and subnets

Step
Operation
Create
fibers/
cables.
Issue 01 (2016-04-30)
Remarks
A.3.5.1
Creating
Optical
Fibers by
Using the
Search
Method
It is recommended that you perform this operation

to create microwave links or SDH fibers on the
NMS when the physical microwave links or SDH
fibers exist.
A.3.5.2
Creating
Fibers
Manually
Perform this operation to create fibers/cables that

are not physically connected.
A.3.5.3
Searching
for
Ethernet
Links
Search for Ethernet links. You can create Ethernet

fiber/cable connections by searching for Ethernet
links.
A.3.5.4 Creating an
Extended ECC
Optional when NEs are connected through

extended ECCs.

27

Configuration Guide
Step
Operation
Remarks
A.3.5.5 Creating a
Back-to-Back Radio
Connection
Optional when there are cascading NEs on the

network.
Configure
subnets.
A.3.6.1
Creating
a Subnet
Optional.
A.3.6.2
Copying
Topology
Objects
Optional.
A.3.6.3
Moving
Topology
Objects
Optional.
5.3 Configuration Example (Network Topology of a

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

The network is a tree network comprising of four hops of microwave links.
Configure the network topology according to the following requirements:
l
In this example, the Hybrid microwave chain network comprises of only OptiX RTN
equipment which are connected to the packet network and managed by the U2000 in
unified manner.
NE11 is a gateway NE and the other NEs access the U2000 through NE11.
The Hybrid microwave chain receives various base station services and transmit them to
the RNC through NE11.
NE12 and NE13 are interconnected through GE ports.
Issue 01 (2016-04-30)

28

Configuration Guide
Figure 5-4 Networking diagram (Hybrid radio chain network)
BTS13
E1
FE
NE14
RTN 905 2E
BTS12
E1
GE+E1
NE13
RTN 950A
FE
NE12
RTN 950A
NE11
RTN 980
GE
RNC
BTS11
NE16
RTN 905 1E
NE15
FE
E1
RTN 950A
BTS14
BTS15
This figure shows the hardware configurations for each NE.

NE13
CSHO
ISV3
NE6
ISV3
FE
NE14
R4
BTS12
RTN 905 2E
E1
GE+E1
ISV3
ISV3
FE
NE15
CSHO
NE16
NE6
ISV3
RTN 905 1E
FE
NE11
PIU
RTN 950A
RTN 950A
R99
BTS13
NE12
CSHO
ISV3
NE6
ISV3
PIU
CSHN
R4
BTS11
ISV3
ISV3
RTN 980
SP3S
E1 GE
RNC
ISV3
ISV3
RTN 950A
E1
R99
BTS14
R4
BTS15
5.3.2 Configuration Procedure

During the configuration procedure, to facilitate interconnection between OptiX RTN 900 and
equipment that does not support HWECC, the network uses IP DCN solution.
Issue 01 (2016-04-30)

29

Configuration Guide
Data Preparation
Item
Value in This Example
Planning Principle
DCC
AUTO(default value)
DCN
1. All NEs use the default

inband DCN and
outband DCN functions
which are enabled for
microwave ports by
default.
2. When ports are

interconnected with
UNI-side base stations,
determine whether to
disable inband DCN for
the ports based on the
requirements of the base
stations. In this example,
inband DCN is enabled
for the ports.
Management VLAN ID and
bandwidth for inband DCN

bandwidth of inband DCN
for each NE:
l Management IDs and

service VLAN IDs must
be different.
l Retain the default value

4094 for the
management VLAN ID.
l Generally, the inband

DCN bandwidth takes
the default value. When
the inband DCN
channels are DCN
channels over a GE link
and the GE link is a
convergence link, you
can increase the inband
DCN bandwidth to 1
Mbit/s or higher.

512 kbit/s for the inband
DCN bandwidth.
Issue 01 (2016-04-30)

30

Configuration Guide
Item
Planning Principle
NE ID and NE IP address
See the following figure.
l Each NE must have a

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

network
NE time is synchronized
with the NMS time.
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
Extended ID-Basic ID
IP address
Gateway
Context
NOTE
In the case of NE commissioning, if the NE ID and the values of NE communication parameters have been
changed and the logical boards have been configured, skip the operations.
Issue 01 (2016-04-30)

31

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

32

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

Issue 01 (2016-04-30)

33

Configuration Guide
Step 4 Synchronize the NE time for NE11 to NE16.

Step 5 Create fibers/cables by using the search method.

Take the microwave link between NE11 and NE12 as an example.
Issue 01 (2016-04-30)

34

Configuration Guide
Normally, all Ethernet links involving NE11 to NE16 should be displayed on the main
topology.
Step 6 Search for Ethernet links.
Take the Ethernet link between NE12 and NE13 as an example.
1.
Issue 01 (2016-04-30)
Search for the link.

35

Configuration Guide
2.
Create the link.
topology.
----End
Issue 01 (2016-04-30)

36

Configuration Guide
5.4 Configuration Example (Network Topology of a

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

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

Issue 01 (2016-04-30)

37

Configuration Guide
BSC
CSHO
NE6
ISV3
ISV3
NE21
RTN 950A
RNC
FE
R4
BTS21
NE22
RTN 905 2E
BTS22
CSHR(ISM6)
NE25
RTN 910A
E1
FE
RTN 905 1E
RTN 905 1E
NE23
R4
BTS24
NE24
FE
R4
BTS23

Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
DCC
AUTO (default value)

38

Configuration Guide
Item
Planning Principle
DCN

inband DCN and
microwave ports by
default.
2. When ports are

interconnected with
for the ports.

for each NE:

be different.

4094 for the
management VLAN ID.

DCN bandwidth takes
the inband DCN
channels are DCN
DCN bandwidth to 1
Mbit/s or higher.

DCN bandwidth.
Issue 01 (2016-04-30)

39

Configuration Guide
Item
Planning Principle

unique NE ID and IP
address.
NE and the NMS must
segment and IP
NE automatically
after the NE ID is
129.9.0.22.)
Gateway NE
NE21
Non-gateway NE

network
with the NMS time.
9-21
129.9.0.21
0.0.0.0
NE21
9-22
129.9.0.22
0.0.0.0
9-25
129.9.0.25
0.0.0.0
NE25
NE22
9-23
129.9.0.23
0.0.0.0
NE23
9-24
129.9.0.24
0.0.0.0
NE24
IP address
Gateway
Issue 01 (2016-04-30)

40

Configuration Guide
Context
NOTE
Procedure
NOTE
commissioning.
Issue 01 (2016-04-30)

41

Configuration Guide

Issue 01 (2016-04-30)

42

Configuration Guide

Issue 01 (2016-04-30)

43

Configuration Guide

topology.
1.
Issue 01 (2016-04-30)

44

Configuration Guide
2.
Create the link.
topology.
----End
Issue 01 (2016-04-30)

45

Configuration Guide
5.5 Configuration Example (Network Topology for a

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

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

NE36
RTN 905 1E
NE35
RTN 950A
BTS32
FE
R4
FE
NE32
RTN 980
NE33
RTN 980
NE31
RTN 950
NE34
RTN 980
NMS
E1
E
+G
E1
E1
GE
BSC
RNC
Issue 01 (2016-04-30)

46

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

Data Preparation
Item
Planning Principle
DCC
AUTO (default value)
DCN

inband DCN and
microwave ports by
default.
2. When ports are

interconnected with
for the ports.
Issue 01 (2016-04-30)

47

Configuration Guide
Item
Planning Principle


for each NE:

be different.

4094 for the
management VLAN ID.

DCN bandwidth takes
the inband DCN
channels are DCN
DCN bandwidth to 1
Mbit/s or higher.

DCN bandwidth.

unique NE ID and IP
address.
NE and the NMS must
segment and IP
NE automatically
after the NE ID is
129.9.0.32.)
Issue 01 (2016-04-30)
Gateway NE
NE31
Non-gateway NE

network
with the NMS time.

48

Configuration Guide
Figure 5-10 Allocated IDs and IP addresses (packet network)
9-36
129.9.0.36
0.0.0.0
NE36
9-35
129.9.0.35
0.0.0.0
NE35
GE
9-32
129.9.0.32
0.0.0.0
GE
NE32
9-31
10.0.0.31
0.0.0.0
9-33
129.9.0.33
0.0.0.0
NE31
NE33
GE
9-34
129.9.0.34
0.0.0.0
GE
NE34
IP address
Gateway
Context
NOTE
Procedure
Issue 01 (2016-04-30)

49

Configuration Guide
NOTE
commissioning.

Issue 01 (2016-04-30)

50

Configuration Guide


Issue 01 (2016-04-30)

51

Configuration Guide
Normally, the microwave links between NE32 and NE35 and between NE35 and NE36
should be displayed on the main topology.
1.
Issue 01 (2016-04-30)

52

Configuration Guide
2.
Issue 01 (2016-04-30)
Create the link.

53

Configuration Guide
topology.
----End
Issue 01 (2016-04-30)

54

Configuration Guide
Configuring Microwave Links
About This Chapter

Before configuring services on a radio link, you need to configure the radio link.
6.1 Basic Concepts
This section provides links to concepts related to configuring microwave links.
The process for configuring microwave links is strongly related to the types of IF boards used.
6.3 Configuration Example (Radio Links on the Hybrid Radio Chain Network)
This section considers radio links on a Hybrid radio chain network as examples to describe
how to configure radio links according to the network planning information.
6.4 Configuration Example (Microwave Links on a Hybrid Microwave Ring Network)
This example assumes that the network topology has been configured.
6.5 Configuration Example (Microwave Links on a Packet Network)
Issue 01 (2016-04-30)

55

Configuration Guide
6.1 Basic Concepts

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

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

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

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

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

The N+1 protection mode indicates that a microwave link has more than N (N>1) working
channels and one protection channel.
Issue 01 (2016-04-30)

56

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

In microwave link aggregation, the Ethernet channels on multiple integrated IP microwave
links between two NEs are aggregated to form an Ethernet link of large bandwidth.
Microwave link aggregation is used to improve the Ethernet bandwidth and reliability of
microwave links.
Microwave link aggregation is implemented in either of the following ways:
l
PLA (also called L1 LAG). PLA can aggregate multiple integrated microwave links. To
implement the sharing of load and balance the Ethernet bandwidth utilization on the
microwave links, Ethernet traffic is allocated based on the Ethernet bandwidth of each
microwave link.
PLA is available in four modes, conventional mode, enhanced mode, super mode, and
Super Dual Band mode.
Conventional PLA has IF boards allocate traffic. Only two radio links share load.
Generally, conventional PLA is called PLA.
Enhanced PLA (EPLA) has packet switching units for allocating traffic. For OptiX
RTN 905 1E, EPLA supports load-sharing among a maximum of two microwave
links. For OptiX RTN 905 2E, 910A, 950, and 950A, EPLA supports load-sharing
among a maximum of four microwave links. For OptiX RTN 980, EPLA supports
load-sharing among a maximum of 12 microwave links.
NOTE
OptiX RTN 905 1E, OptiX RTN 905 2E, OptiX RTN 910A, OptiX RTN 950A, OptiX RTN 950
using CSHU/CSHUA boards and OptiX RTN 980 using CSHNA board support EPLA.
The PLA in super mode has the packet switching unit to distribute traffic to the
dual-IF board. Then, the dual-IF board distributes traffic to the IF ports. For OptiX
RTN 910A, this mode supports the load sharing of a maximum of six microwave
links. For OptiX RTN 950A and 950, this mode supports the load sharing of a
maximum of eight microwave links. Therefore, this super mode is called EPLA+.
NOTE
Only OptiX RTN 910A, OptiX RTN 950A and OptiX RTN 950 using CSHU/CSHUA boards
support EPLA+.
Issue 01 (2016-04-30)
The PLA in Super Dual Band mode binds links at common bands and E-Band links
to implement long-distance large-bandwidth transmission. The EM6D board is used
57

Configuration Guide
to distribute traffic to the two types of links according to service priorities. The PLA
in Super Dual Band Mode is called Super EPLA.
NOTE
Only OptiX RTN 950A and OptiX RTN 950 using CSHU/CSHUA boards support Super EPLA.
For more details about Super EPLA, see the Super Dual Band User Manual.
Air-interface LAG, also called L2 LAG. Air-interface LAG aggregates multiple

integrated microwave links based on IEEE 802.3ad. To implement the sharing of load,
Ethernet traffic is allocated based on the HASH algorithm which is based on packet
headers (IP addresses, MAC addresses, or MPLS labels).
Figure 6-1 Microwave link aggregation

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

The process for configuring microwave links is strongly related to the types of IF boards used.
This figure shows the process of configuring microwave links.
Issue 01 (2016-04-30)

58

Configuration Guide
Figure 6-2 Configuration flowchart (microwave links)

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

mode.
Create a microwave link

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

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

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

information for the
microwave link.
Configure link
aggregation over air
interfaces.
End

by using the search
method.
Modify the IF service type.
Configure the other

information for the
microwave link.
Required
End
Optional
NOTE
l OptiX RTN 905 is an integrated chassis device and does not support inserted boards.
l OptiX RTN 910A supports only ISV3 and ISM6 boards.
l OptiX RTN 950A does not support IF1/IFX2 boards.
l For OptiX RTN 910A/950/950A/980, when XPIC and IF 1+1 protection are coupled, IF 1+1 protection is
not configured on the Microwave Link Configuration tab.

Issue 01 (2016-04-30)

59

Configuration Guide
Process of Configuring Microwave Links

Table 6-1 Process of configuring microwave links
Operation
Remarks
A.8.10.7 Changing the Running Mode of

an IF Port
The working modes of IF ports at both ends

of a microwave link must be the same.
A.8.10.6 Changing the IF Service Type
Required if the IF service type is not Native

E1+Ethernet.
A.5.1 Configuring a Single-Hop Radio

Link
Required.
A.5.2 Creating an IF 1+1 Protection

Group
For OptiX RTN 910A/950/950A/980,

required when XPIC and IF 1+1 protection
are coupled.
Set related parameters according to the

network plan.

network plan. It is recommended to set
Alarm Report Mode to Only protection
group alarms.
Configuri
ng link
aggregatio
n over air
interfaces
Configurin
g PLA (L1
LAG)
A.5.10
Creating a
PLA/EPLA/
EPLA+/Super
EPLA Group
Required if the PLA/EPLA/EPLA+ function

needs to be used.
When PLA/EPLA/EPLA+ is implemented
over microwave links, load is shared at the
physical layer. Utilization of Ethernet
bandwidth is generally the same for each
microwave link.
NOTE
OptiX RTN 905 1E, OptiX RTN 905 2E, OptiX
RTN 910A, OptiX RTN 950A, OptiX RTN 950
using CSHU/CSHUA boards and OptiX RTN 980
using CSHNA board supports EPLA.
Only OptiX RTN 950 using CSHU/CSHUA
boards, OptiX RTN 950A and OptiX RTN 910A
support EPLA+.
Configurin
g a (L2)
LAG
Issue 01 (2016-04-30)
A.9.2.1
Creating a
LAG
Required if the LAG function needs to be

used.
A.9.2.2 Setting
LAG
Parameters
Optional.
When LAG is implemented over microwave

links, load is shared at the physical layer.
Utilization of Ethernet bandwidth might be
different between different microwave links.
It is recommended to retain the default value

Auto for Load Sharing Hash Algorithm.

60

Configuration Guide
Operation
Remarks
A.3.5.1 Creating Optical Fibers by Using

the Search Method
Required when microwave links needs to be

created on the U2000.
In normal cases, the main topology displays
the previously created microwave links.
NOTE
Skip this step if microwave links have been
created during per-NE commissioning or the
creation of network topology.
Configuring the other

information for the
microwave links
Modifying
parameters
for an IF 1+1
protection
group
Required if Alarm Report Mode needs to be

set to Only protection group alarms.
A.5.4 Creating
an N+1
Protection
Group
Required when the microwave links are

configured with N+1 protection.
A.8.11.3
Setting ODU
Power
Attributes
Main ODU parameters have been configured

in A.5.1 Configuring a Single-Hop Radio
Link. Required when the following
parameters need to be modified according to
the network plan.
Set attributes of the N+1 protection group to

the same values at both ends.
l Maximum Transmit Power(dBm)

l TX High Threshold(dBm)
l TX Low Threshold(dBm)
l RX High Threshold(dBm)
l RX Low Threshold(dBm)
Issue 01 (2016-04-30)
A.8.10.3
Setting
Advanced AM
Attributes
Optional.
Configuring
Ethernet
frame header
compression
and error
frame
discarding
over air
interfaces
Required when error Ethernet frames are not

discarded.
When E1 priority is enabled, you can

perform this operation to change the number
of E1s in intermediate modulation mode.

network plan.

61

Configuration Guide
Operation
Remarks
Configuring
enhanced
Ethernet
frame
compression
Optional.
If enhanced Ethernet frame compression is
enabled for a QoS queue at an IF port,
Ethernet frame header compression (L2+L3)
is automatically enabled for the IF port.
6.3 Configuration Example (Radio Links on the Hybrid

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

The network is a tree network comprising of four hops of microwave links.
The microwave links need to be configured based on 5.3 Configuration Example (Network
Topology of a Hybrid Microwave Chain Network) and the following requirements:
l
Each Hybrid microwave link transmits E1 services and Ethernet services. The AM
function is enabled on each link.
To improve transmission reliability of important services, the microwave links between

NE11 and NE12, between NE13 and NE14, and between NE13 and NE15 are configured
with 1+1 HSB protection.
This table provides the service capacity accessed by each BTS.

Table 6-2 Service capacity accessed by each BTS
Issue 01 (2016-04-30)
BTS
BTS11
BTS12
BTS13
BTS14
BTS15
Number of
highpriority E1s
Number of
low-priority
E1s
Capacity of
highpriority
Ethernet
services
(Mbit/s)
10

62

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

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

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

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

Low
Voice, signaling, and OM Ethernet

services
High
Streaming media, background, and

interactive Ethernet services, for
example, Internet services
Low

63

Configuration Guide
Figure 6-3 Networking diagram (Hybrid microwave chain network)
BTS13
E1
FE
NE14
RTN 905 2E
BTS12
E1
GE+E1
NE13
RTN 950A
FE
NE12
RTN 950A
NE11
RTN 980
GE
RNC
BTS11
NE16
RTN 905 1E
NE15
FE
E1
RTN 950A
BTS14
BTS15
The connections of microwave links is shown in the following figure.

NE13
CSHO
ISV3
NE6
ISV3
FE
NE14
R4
BTS12
RTN 905 2E
E1
GE+E1
ISV3
ISV3
FE
NE15
CSHO
NE16
NE6
ISV3
RTN 905 1E
FE
NE11
PIU
RTN 950A
RTN 950A
R99
BTS13
NE12
CSHO
ISV3
NE6
ISV3
PIU
CSHN
R4
BTS11
ISV3
ISV3
RTN 980
SP3S
E1 GE
RNC
ISV3
ISV3
RTN 950A
E1
R99
BTS14
R4
BTS15

This section describes the procedure for configuring data.
Issue 01 (2016-04-30)

64

Configuration Guide
Data Preparation
Item
Planning Principle
Basic information about

microwave links
See Figure 6-5. Singlepolarized antennas are used

on this network.
l On microwave networks,
TX high sites and TX
low sites are arranged
alternately.
l The polarization
directions of antennas on
one hop of microwave
link should be the same.
Hybrid/AM attribute
information
See Table 6-4.

The Hybrid microwave
capacity and the AM
function are available only if
the corresponding license
files are configured.
l Ensure that the air

interface bandwidth for a
microwave link in AM
guaranteed capacity
mode is larger than the
total bandwidth of highpriority services, and link
availability meets
availability requirements
of high-priority services.
interface bandwidth in
full capacity mode is
more than the total
bandwidth of all
services, and link
availability meets the
availability requirement
of low-priority services.
l When the E1 priority
function is enabled, full
E1 service bandwidth
Full service bandwidth Guaranteed service
bandwidth + Guaranteed
E1 service bandwidth.
Power information
Issue 01 (2016-04-30)
See Table 6-5.

65

Configuration Guide
Figure 6-5 Basic information about microwave links

102
14952M
14532M
420M
14M
1+1 HSB
H-polarization
101
14930M
14510M
420M
28M
1+1 HSB
V-polarzation
Tx high
NE14
RTN 905 2E
104
14930M
14510M
420M
7M
1+0
H-polarzation
Tx low
Tx low Tx high
Tx low
NE13
Tx high
RTN 950A RTN 950A

103
14967M
14547M
420M
14M
1+1 HSB
V-polarization
Tx high
NE15
RTN 950A
Tx low
NE11
RTN 980
NE12
NE16
RTN 905 1E
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
T/R Spacing
Channel spacing
RF configuarion
Polarization
Table 6-4 Hybrid/AM attribute information
Issue 01 (2016-04-30)
Parameter
Link 101
Link 102
Link 103
Link 104
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
Capacity of
high-priority
Ethernet
services
(Mbit/s)
113
39
39
19

66

Configuration Guide
Parameter
Link 101
Link 102
Link 103
Link 104
AM status
Enabled
Enabled
Enabled
Enabled
Modulation
mode of the
guaranteed AM
capacity
QPSK
QPSK
QPSK
QPSK
Modulation
mode of the full
AM capacity
128QAM
32QAM
64QAM
32QAM
E1 priority
status
Enabled
Disabled
Enabled
Disabled
Table 6-5 Power information

Parameter
Link 101
Link 102
Link 103
Link 104
TX Power
(dBm)
16.5 (NE11)
16.5 (NE13)
16 (NE13)
20 (NE15)
16.5 (NE12)
16.5 (NE14)
16 (NE15)
20 (NE16)
RX Power
(dBm)
-46 (NE11)
-44 (NE13)
-43 (NE13)
-48 (NE15)
-46 (NE12)
-44 (NE14)
-43 (NE15)
-48 (NE16)
ATPC
Disabled
Disabled
Disabled
Disabled
Automatic
ATPC threshold
setting
Upper threshold
of ATPC
adjustment
(dBm)
Lower
threshold of
ATPC
adjustment
(dBm)
Maximum
transmit power
(dBm)
Procedure
Step 1 Configure one hop of microwave link.
Link 101 between NE11 and NE12 is taken as an example. For details, see
Issue 01 (2016-04-30)

67

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

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

Microwave Ring Network)

The network contains four hops of microwave links configured with 1+0 protection. AM is
enabled for each hop of link.
Based on 5.4 Configuration Example (Network Topology of a Hybrid Microwave Ring
Network), the microwave links need to be configured according to the following
requirements:
l
Issue 01 (2016-04-30)
All the microwave links use 1+0 non-protection configuration.

68

Configuration Guide
AM is enabled for each hop of microwave link.
Table 6-6 shows the service capacity accessed by each BTS.

BTS
BTS21
BTS22
BTS23
BTS24
Number of
high-priority
E1s
Number of
low-priority
E1s
Capacity of
high-priority
Ethernet
services
(Mbit/s)
Capacity of
low-priority
Ethernet
services
(Mbit/s)
10
10
10
10
NOTE
transmission guarantees. Low-priority services can be discarded in modulation scheme shifts. The
common service priorities are provided in Table 6-7.
Table 6-7 Common service priorities
Issue 01 (2016-04-30)
Service Type
Priority
TDM E1s that carry 2G base station

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

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

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

Low
Voice, signaling, and OM Ethernet

services
High

69

Configuration Guide
Service Type
Priority
Streaming media, background, and

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

70

Configuration Guide
BSC
CSHO
NE6
ISV3
ISV3
NE21
RTN 950A
RNC
FE
R4
BTS21
NE22
RTN 905 2E
BTS22
NE25
CSHR(ISM6)
RTN 910A
E1
FE
RTN 905 1E
RTN 905 1E
NE23
R4
BTS24
NE24
FE
R4
BTS23

Data Preparation
Item
Planning Principle

microwave links
See Figure 6-8. Singlepolarized antennas are used

on this network.
l On microwave networks,
TX high sites and TX
low sites are arranged
alternately.
l The polarization
directions of antennas on
one hop of microwave
link should be the same.
Issue 01 (2016-04-30)

71

Configuration Guide
Item
Planning Principle
Hybrid/AM attribute
information
See Table 6-8.

guaranteed capacity
availability meets

capacity and the AM

more than the total
bandwidth of all
services, and link
Power information
Issue 01 (2016-04-30)
See Table 6-9.

72

Configuration Guide
201
14930M
14510M
420M
14M
1+0
V-polarization
Tx low
204
14958M
14538M
420M
14M
1+0
V-polarization
NE21
Tx high
Tx high
Tx low
Tx low
Tx low
NE22
Tx high
202
14958M
14538M
420M
14M
1+0
H-polarization
Tx high
203
14930M
14510M
420M
14M
1+0
H-polarization
NE24
NE23
NE25
Link ID
Tx high site Tx Freq.
Tx low site Tx Freq.
T/R spacing
Channel spacing
RF configuarion
Polarization
Issue 01 (2016-04-30)
Parameter
Link 201
Link 202
Link 203
Link 204
Number of E1s
in AM
guaranteed
capacity mode
Number of E1s
in AM full
capacity mode
Capacity of
high-priority
Ethernet
services
(Mbit/s)
28
28
28
28

73

Configuration Guide
Parameter
Link 201
Link 202
Link 203
Link 204
Capacity of
high-priority
Ethernet
services
(Mbit/s)
40
40
40
40
AM status
Enabled
Enabled
Enabled
Enabled
Modulation
mode of the
guaranteed AM
capacity
16QAM
16QAM
16QAM
16QAM
Modulation
mode of the full
AM capacity
128QAM
128QAM
128QAM
128QAM
E1 priority
status
Disabled
Disabled
Disabled
Disabled
Table 6-9 Power information
Issue 01 (2016-04-30)
Parameter
Link 201
Link 202
Link 203
Link 204
TX Power
(dBm)
16.5 (NE21)
16.5 (NE23)
16 (NE23)
15 (NE21)
16.5 (NE22)
16.5 (NE22)
16 (NE24)
15 (NE24)
RX Power
(dBm)
-42 (NE21)
-44 (NE23)
-43 (NE23)
-45 (NE21)
-42 (NE22)
-44 (NE22)
-43 (NE24)
-45 (NE24)
ATPC
Disabled
Disabled
Disabled
Disabled
Automatic
ATPC threshold
setting
Upper threshold
of ATPC
adjustment
(dBm)
Lower
threshold of
ATPC
adjustment
(dBm)
Maximum
transmit power
(dBm)

74

Configuration Guide
Procedure
Link 201 between NE21 and NE22 is taken as an example. For details, see
NOTE
Configure the running mode for the ISM6 board on NE25 to IS3 so that the ISM6 board can interconnect with
the ISV3 board.

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

Network)

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

bandwidth, the microwave links between NE32 and NE33 are enabled with XPIC and
configured with PLA protection.
75

Configuration Guide
This table provides the service capacity accessed by each BTS.

BTS
BTS32
Capacity of high-priority services

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

NE36
RTN 905 1E
NE35
RTN 950A
BTS32
FE
R4
FE
NE32
RTN 980
NE33
RTN 980
NE31
RTN 950
NE34
RTN 980
NMS
E1
E
+G
E1
E1
GE
BSC
RNC
This figure provides the board configuration of each NE on the packet network.
Issue 01 (2016-04-30)

76

Configuration Guide

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

Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle

microwave links
See Figure 6-11. The XPIC

link between NE32 and
NE35 uses dual-polarized
antennas and the
unprotected link between
NE35 and NE36 uses singlepolarized antennas.
On microwave networks,
TX high sites and TX low
sites are arranged
alternately.

77

Configuration Guide
Item
Planning Principle
Hybrid/AM attribute
information
See Table 6-11.

guaranteed capacity
availability meets

capacity and the AM

more than the total
bandwidth of all
services, and link
Power information
Issue 01 (2016-04-30)
See Table 6-12.

78

Configuration Guide
303
14930M
14510M
420M
7M
1+0
H- polarzation
NE36
RTN 905 1E
Tx high
301,302
14967M
14547M
420M
14M
XPIC
Dual - polarization
NE35
RTN 950A
PLA
Tx low
Tx low
Tx high
GE
NE32
RTN 980
NE33
RTN 980
NE31
RTN 950
NE34
RTN 980
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
T/R spacing
Channel spacing
RF configuarion
Polarization
Issue 01 (2016-04-30)
Parameter
Link 301
Link 302
Link 303
Capacity of highpriority services

(Mbit/s)

79

Configuration Guide
Parameter
Link 301
Link 302
Link 303
Capacity of lowpriority services

(Mbit/s)
24
24
24
AM status
Enabled
Enabled
Enabled
Modulation mode of
the guaranteed AM
capacity
QPSK
QPSK
QPSK
Modulation mode of
the full AM capacity
64QAM
64QAM
32QAM
Table 6-12 Power and ATPC information

Parameter
Link 301
Link 302
Link 303
TX Power (dBm)
6.0 (NE1)
6.0 (NE1)
20 (NE33)
6.0 (NE2)
6.0 (NE2)
20 (NE34)
-45.0 (NE1)
-45.0 (NE1)
-48 (NE33)
-45.0 (NE2)
-45.0 (NE2)
-48 (NE34)
ATPC
Disabled
Disabled
Disabled
Automatic ATPC
threshold setting
Upper threshold of
ATPC adjustment
(dBm)
Lower threshold of
ATPC adjustment
(dBm)
Maximum transmit
power (dBm)
RX Power (dBm)
Procedure
Take the XPIC link between NE32 and NE35 as an example.
Issue 01 (2016-04-30)

80

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

1.
Issue 01 (2016-04-30)
Build a new co-site.

81

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

On the network, two microwave links have been created in Configuring Network Topology
----End
Issue 01 (2016-04-30)

82

Configuration Guide
Configuring TDM Services
About This Chapter

The key to configuring TDM services is configuring the corresponding service crossconnections.
7.1 Basic Concepts
This section provides links to concepts related to configuring TDM services.
7.2 End-to-End Configuration Process
This section describes the process for configuring end-to-end SDH service trails, MSP
subnets, and SDH or PDH ports on a per-NE basis.
7.3 Configuration Process on a Per-NE Basis
The process of configuring services with SNCP is greatly different from the process of
configuring services without SNCP.
7.4 Configuration Example (TDM Services on a Hybrid Microwave Chain Network)
This example assumes that the network topology and microwave links have been configured.
7.5 Configuration Example (TDM Services on a Hybrid Microwave Ring Network)
Issue 01 (2016-04-30)

83

Configuration Guide
7.1 Basic Concepts

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

OptiX RTN 900 supports linear multiplex section protection (MSP) and subnet connection
protection (SNCP) for TDM services. OptiX RTN 980 also support two-fiber bidirectional
ring MSP.
Linear MSP
Linear MSP applies to point-to-point networks. MSP provides protection for the services
between two multiplex section termination (MST) modules. That is, when an MSP switching
occurs, the services are switched from the working section to the protection section. For
OptiX RTN 900, linear MSP provides protection for TDM services that are transmitted over
SDH fibers.
Linear MSP includes 1+1 linear MSP and 1:N linear MSP.
l
1+1 linear MSP

In the case of 1+1 linear MSP, one protection channel protects one working channel, and
the protection channel does not transmit extra services. When the working channel
becomes unavailable, services are switched to the protection channel for transmission, as
shown in Figure 7-1. 1+1 linear MSP is classified into dual-ended revertive, dual-ended
non-revertive, single-ended revertive, and single-ended non-revertive modes. The singleended 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 01 (2016-04-30)

84

Configuration Guide
1:N linear MSP

1:N linear MSP requires N working channels and one protection channel. The protection
channel may transmit extra services. When a working channel becomes unavailable, the
services on this channel are switched to the protection channel for transmission. As a
result, extra services are interrupted, as shown in Figure 7-2. 1:N linear MSP is available
only in dual-ended revertive mode.
Figure 7-2 1:N linear MSP
NE A
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
NOTE
OptiX RTN 910A supports only 1:1 protection for channelized STM-1 services. In 1:1 protection mode, one
working channel exclusively uses one protection channel, and the protection channel cannot carry extra
services. 1:1 protection for channelized STM-1 services is available only in dual-ended revertive mode.
SNCP
In the case of SNCP, the protection subnet connection takes over when the working subnet
connection fails or deteriorates. For OptiX RTN 900, SNCP provides protection for TDM
services on STM-1 fiber ring networks, TDM microwave ring networks, Hybrid microwave
ring networks, STM-1 fiber ring networks, or Hybrid ring networks.
SNCP is based on dual feed and selective receiving and requires a working subnet and a
protection subnet. When the working subnet fails or deteriorates, services are transmitted over
the protection subnet, as shown in Figure 7-3.
Issue 01 (2016-04-30)

85

Configuration Guide
Figure 7-3 SNCP

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

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

86

Configuration Guide
Figure 7-4 Two-fiber bidirectional MSP ring

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

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

87

Configuration Guide
STM-1
If an IF board transmits STM-1s and the STM-1 capacity is nxSTM-1, the first to nth VC-4
timeslots on the IF board are available and correspond to the first to nth STM-1s that are
transmitted over microwave. For example, if the STM-1 capacity is 2xSTM-1, VC4-1 and
VC4-2 on the IF board are available. If a cross-connection is configured between an E1 port
on a service board and the second VC-12 timeslot in VC4-2 on an IF board, the E1 services
that are accessed through the E1 port are sent to the second VC-12 in the second STM-1 that
is transmitted over microwave.
NOTE
An OptiX RTN 905 2E or an ISM6 board can transmit a maximum of two VC-4 TDM services.
7.1.3 MSP Subnet

The U2000 manages multiplex section protection (MSP) in end-to-end mode using MSP
subnets.
A protection subnet refers to a network structure that is capable of self-protection. It is a
network unit of the transport network and defines attributes including the signal protection
scheme, service direction, and rate level. On the U2000, a protection subnet is defined in a
broad sense. MSP subnets and two-fiber bidirectional MSP subnets (for OptiX RTN 980 only)
are used to provide end-to-end management of protection subnets of the OptiX RTN 900.
7.1.4 SDH Trails

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

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

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

88

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

TUG-2
TUG-3
{
{
{
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
Figure 7-6 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
63
45
48
51
54
57
60
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 crossconnections.
Issue 01 (2016-04-30)

89

Configuration Guide
7.1.6 TDM Timeslot Planning Schemes

Timeslot assignment diagrams illustrate TDM timeslot planning schemes.
Timeslot Assignment Diagram

A timeslot assignment diagram provides significant references for configuring TDM services.
Before planning TDM timeslots, you need to be familiar with the meanings shown in the
timeslot assignment diagram.
Figure 7-7 Timeslot assignment diagram
Site
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-7, the timeslot allocation diagram contains three areas, namely, site
area, timeslot area, and timeslot assignment area.
The site area contains the NE icons and interface boards that carry microwave links.
l
Each of the first NE and last NE has only one interface board and an intermediate NE
has two interface boards which are at both sides of the vertical line under the
intermediate NE icon.
The interface board on the left side of the vertical line under an intermediate NE icon is
connected to the interface board on the right side of the vertical line under its upstream
NE icon. The interface board on the right side of the vertical line under an intermediate
NE icon is connected to the interface board on the left side of the vertical line under its
downstream NE icon.
In the case of a ring link, before planning the site area, you need to break the ring link
into a chain link and ensure that the start and end NEs are the same one.
The timeslot area represents the VC-4 timeslot resources. For example, in the case of a
microwave link, timeslots occupied by an STM-1 service are all in the first VC-4.
In the timeslot assignment area, each straight line represents a service and the numeric above
the straight line represents the timeslot occupied by this service.
Issue 01 (2016-04-30)

90

Configuration Guide
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 same route, you only need to draw a
solid line to represent the working service. In the case of protection configuration (for
example, SNCP) wherein the working service and protection service have different
routes, you need to draw a solid line to represent the working service and a dotted line to
represent the protection service.
TDM Timeslot Planning Scheme for Chain Networks

On a backhaul network for a mobile base station, the services are accessed from different
nodes and then aggregated to the same node for transmission. In this case, assign the timeslots
on the chain microwave network as follows:
1.
Select the chain that contains the most hops as the main chain. Then, divide the chain
network into several sub-chains by taking the main chain as the reference. Consider the
E1 channels or fiber connections that are used for transferring services between NEs as
links.
2.
Assign the timeslots for the added, dropped, or pass-through services on the NEs of the
main chain one after another, in the descending order of distance. Assign the smallest
VC-12 timeslot number to the service on the farthest NE. The number of the timeslot
each service occupies does not change on the chain network.
3.
Repeat the previous step to configure timeslots for the services on all the sub-chains.
This timeslot assignment method ensures that only the numbers of timeslots that services on
the nodes of the aggregation sub-chain occupy may change.
The principles for obtaining the timeslot cross-connection configurations from the non-SNCP
service timeslot assignment diagram are as follows:
l
The vertical line under the NE name is considered as the reference.
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
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.
If there is a straight line with an arrow on both sides of the vertical line, it indicates that
cross-connections are configured between the two boards on both sides of the vertical
line. The corresponding cross-connected timeslots on each board are marked over the
straight line with an arrow on the side of this board.
For details, see 7.4 Configuration Example (TDM Services on a Hybrid Microwave
Chain Network).
Issue 01 (2016-04-30)

91

Configuration Guide
TDM Timeslot Planning Scheme for Ring Networks

On a backhaul network for a mobile base station, the services are accessed from different
nodes and then aggregated to the same node for transmission. In this case, assign the timeslots
on the SNCP microwave ring network as follows:
1.
Assign the timeslots to added or dropped services on the NEs in anti-clockwise order.
Assign the smallest VC-12 timeslot number to the service on the nearest NE. The
number of the timeslot each service occupies does not change on the ring network.
2.
Repeat the previous step to configure timeslots for the services on all the sub-chains.
This timeslot assignment method ensures that only the numbers of timeslots that services on
the nodes of the aggregation sub-chain occupy may change.
The principles for obtaining the timeslot cross-connection configurations from the SNCP
service timeslot assignment diagram are as follows:
l
The vertical line under the NE name is considered as the reference.
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 crossconnected timeslots are marked over the straight line with one dot.
For details, see 7.5 Configuration Example (TDM Services on a Hybrid Microwave Ring
Network).
7.1.7 Transmitting Native T1 Services Through E1 Channels

OptiX RTN 950A supports transmitting Native T1 services through E1 channels.
l
If the system control board is SLF2CSHO, the PDH ports of SP3S and SP3D boards and
the PDH port integrated on SLF2CSHO boards can work in T1 mode.
A T1 service occupies 24x64 kbit/s timeslots, an E1 service occupies 32x64 kbit/s

timeslots, and therefore a T1 service can be carried over an E1 channel with the
remaining 8x64 kbit/s timeslots stuffed.
When transmitting T1 services, each E1 channel corresponds to a T1 service.
When configuring T1 services, retain the original configurations of the TDM crossconnect mode and Hybrid microwave. Only the service types carried over PDH ports are
different.

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

92

Configuration Guide
Figure 7-8 Flowchart for configuring TDM services
Start
Configuring the TDM

service port working mode
Creating a Linear MSP
Protection Subnet
Creating Point-to-Point
Service Trails
Required
Creating SNCP Service

Trails
Copying Service Trails
Optional
End

Table 7-1 Process for configuring the TDM service port working mode
Step
Operation
Setting the
working
mode for a
TDM port
Description
A.8.2
Setting
Working
Modes of
E1 Ports
Required for an E1 port that supports various

service modes. Set Service Mode to PDH or
TDM.
NOTE
l For OptiX RTN 905 housing an MN1 board, you can
set Service Mode for ports on the logical board
MP1/VS2/CD1 to TDM or Packet.
l For OptiX RTN 950A housing an MN1 board, you
can set Service Mode for ports on the logical board
MP1/CD1 to TDM or Packet.
A.8.3
Setting
the
Paramete
rs of PDH
Ports
Issue 01 (2016-04-30)
Required if Native T1 services are transmitted

through E1 channels. Set Port Service Type to T1.
NOTE
The working mode of a PDH interface can be set to T1
for only OptiX RTN 950A.

93

Configuration Guide
Table 7-2 Process of creating an MSP subnet

Step
Operation
Remarks
A.3.5.1 Creating
Optical Fibers by
Using the Search
Method
Required to create SDH optical fiber connections

of service trails if they have not been created on
the U2000.
When creating optical fiber connections, set
Automatically Allocate Address to No.
A.15.1.2 Creating a
Linear MSP
Protection Subnet
Required.
The parameters need to be set according to the
service plan.
Table 7-3 Process of creating SDH trails

Step
Operation
Remarks
A.15.2.2 Creating
Server Trails
Optional. Create VC-4 service trails before

creating VC-3 or VC-12 service trails.
A.15.2.3 Creating
Point-to-Point Service
Trails
Required when point-to-point trails are created. By

performing this operation to specify the service
trail between the source and sink ends, you can
configure a point-to-point service in end-to-end
mode.
service plan.
Issue 01 (2016-04-30)

94

Configuration Guide
Step
Operation
Remarks
A.15.2.4 Creating
SNCP Service Trails
Required when SNCP trails are created. By

performing this operation to specify working and
protection trails between the dual-feed point and
the selective-receiving point, you can configure an
SNCP service in end-to-end mode.
service plan.
If the created SNCP service involves AM-enabled
links with E1 priorities or if E1 priorities of cross
connections need to be changed, modify the setting
of E1 Priority according to the service plan.
NOTE
When an AM-enabled microwave link is configured with
the E1 priority, configure E1 Priority for each crossconnection on the link as follows:
l If a cross-connection is configured for a point-topoint service, the E1 priority is configured when the
cross-connection is created.
l If a cross-connection is configured for an SNCP
service, the E1 priority is modified after the crossconnection is created.
l If the E1 priority is not specified for a crossconnection during creation, set E1 Priority to Low
or High for the cross-connection after it is created.
A.15.2.5 Copying
Service Trails
Optional. Perform this operation to copy service

trails. By copying service trails, you can quickly
create a service trail based on a created SDH trail.
service plan.

The process of configuring services with SNCP is greatly different from the process of
configuring services without SNCP.
Figure 7-9 shows the process of configuring TDM services.
Issue 01 (2016-04-30)

95

Configuration Guide
Figure 7-9 Flowchart for configuring TDM services
Process of configuring
added/dropped SNCP services
Process of configuring
common services or
SNCP pass-through services
Start
Start
Configuring the TDM service port

working mode
Configuring the TDM service port

working mode
Configuring MSP
Configuring MSP
Create cross-connections
for SNCP services
Create cross-connections
for point-to-point services
Configure automatic switching

conditions for SCNP services
Test E1 services using the PRBS
Change the
priority of E1 services
End
Test E1 services using the PRBS
Start
Required
Optional
Issue 01 (2016-04-30)

96

Configuration Guide
Table 7-4 Process for configuring TDM services (added/dropped SNCP services)
Step
Operation
Setting the
working
mode for a
TDM port
Remarks
A.8.2
Setting
Working
Modes of
E1 Ports
Required for an E1 port that supports various

service modes. Set Service Mode to PDH or
TDM.
NOTE
l For OptiX RTN 905 housing an MN1 board, you can
set Service Mode for ports on the logical board
l For OptiX RTN 950A housing an MN1 board, you
can set Service Mode for ports on the logical board
Issue 01 (2016-04-30)
Configuri
ng MSP
A.8.3
Setting
the
Paramete
rs of PDH
Ports
Required if Native T1 services are transmitted

through E1 channels. Set Port Service Type to T1.
A.6.1
Configuri
ng Linear
MSP
Required when linear MSP is configured for the

optical transmission line of OptiX RTN 900.
A.6.5
Configuri
ng Ring
MSP
Required when ring MSP is configured for the

NOTE
The working mode of a PDH interface can be set to T1
for only OptiX RTN 950A.

service plan.

service plan.
A.7.2 Creating CrossConnections of SNCP

Servicesa
Required when the TDM services are SNCP

services.
A.7.5 Configuring the

Automatic Switching
of SNCP Services
Optional when the TDM services are SNCP

services.

service plan.

97

Configuration Guide
Step
Operation
Remarks
A.7.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.
Modify E1 priority according to service plan.
NOTE
When an AM-enabled microwave link is configured with
the E1 priority, configure E1 Priority for each crossconnection on the link as follows:
l If a cross-connection is configured for a point-topoint service, the E1 priority is configured when the
cross-connection is created.
l If a cross-connection is configured for an SNCP
service, the E1 priority is modified after the crossconnection is created.
l If the E1 priority is not specified for a crossconnection during creation, set E1 Priority to Low
or High for the cross-connection after it is created.
Testing E1 Services
Using PRBS
The test results should show that each E1 service

contains no bit errors.
Table 7-5 Process of configuring TDM services (common services/SNCP pass-through

services)
Step
Operation
Remarks
A.8.2 Setting Working

Modes of E1 Ports
Required for OptiX RTN 905 and OptiX RTN

950A on which an MP1 or a CD1 board provides a
TDM port.
Set Port Working Mode to PDH or SDH.
Issue 01 (2016-04-30)
Configuri
ng MSP
A.6.1
Configuri
ng Linear
MSP
Required when linear MSP is configured for the

A.6.5
Configuri
ng Ring
MSP
Required when ring MSP is configured for the

A.7.1 Creating the

Cross-Connections of
Point-to-Point
Servicesa

service plan.

service plan.
Required when the TDM services are point-topoint services.
service plan.

98

Configuration Guide
Step
Operation
Remarks
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 TDM services on the
working channel only. In the case of N+1 protection configuration, two-fiber bidirectional ring MSP
configuration (for OptiX RTN 980 only) or 1:N linear MSP configuration, you also need to configure the
extra services on the protection channel if required.
7.4 Configuration Example (TDM Services on a Hybrid

Microwave Chain Network)

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

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

99

Configuration Guide
The connections of TDM links is shown in the following figure.

Figure 7-11 TDM link connections on a Hybrid microwave chain network
NE13
CSHO
ISV3
NE6
ISV3
NE14
RTN 905 2E
E1
E1
ISV3
ISV3
NE11
PIU
RTN 950A
RTN 950A
R99
BTS13
NE12
CSHO
ISV3
NE6
ISV3
CSHN
ISV3
ISV3
RTN 980
NE16
RTN 950 1E
NE15
CSHO
NE6
ISV3
PIU
SP3S
E1
RNC
ISV3
ISV3
RTN 950A
E1
R99
BTS14
7.4.2 End-to-end Configuration

The core of end-to-end configuration is to create or copy VC-12 paths corresponding to E1
services based on a timeslot assignment diagram.
Data Preparation
This figure shows timeslot assignment for TDM services on a network.
Issue 01 (2016-04-30)

100

Configuration Guide

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

101

Configuration Guide
2.
Issue 01 (2016-04-30)
Set the source and sink nodes for the service trail.

102

Configuration Guide
Step 2 Copy the SDH service trail.

The created SDH service trail is copied to create the high-priority E1 service trail between
port 2-SP3S-2 of NE11 and port 19-SP3S-2 of NE15.
1.
Issue 01 (2016-04-30)
Filter the created SDH service trail.

103

Configuration Guide
2.
Issue 01 (2016-04-30)
Copy the service trail.

104

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

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

105

Configuration Guide

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

106

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


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

107

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

Figure 7-15 TDM link connections on a Hybrid microwave ring network
E1
BSC
CSHO
NE6
ISV3
ISV3
NE21
RTN 950A
NE22
RTN 905 2E
BTS22
NE25
CSHR(ISM6)
E1
NE23
RTN 905 1E
RTN 905 1E
NE23
Issue 01 (2016-04-30)

108

Configuration Guide

In the case of end-to-end configuration, SNCP can be configured during VC-12 configuration.
Data Preparation
Station
Timeslot
NE22
NE21
3-ISV3 4-ISV3
3-ISV3
VC12: 1-2
19-SP3S:1-2
NE23
3-ISU3 8-TS2
NE24
NE25
8-TS2 3-ISU3
7-ISM6-1 7-ISM6-2
NE21
3-ISV3
VC12: 1-2
9-SP3S:1-2 9-SP3S:1-2
19-SP3S:1-2
Pass through (SNCP working path)

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

109

Configuration Guide
Step 2 Configure SNCP.
Issue 01 (2016-04-30)

110

Configuration Guide
Step 3 Copy the SDH service trail.

Copy the created SDH service trail to create E1 services between port 19-SP3S-2 of NE21
and port 9-SP3S-2 of NE22.
1.
Issue 01 (2016-04-30)
Filter the created SDH service trail.

111

Configuration Guide
2.
Issue 01 (2016-04-30)
Copy the service trail.

112

Configuration Guide
----End

In the case of configuration on a per-NE basis, SNCP can be configured during the
configuration of cross-connections for VC-12 timeslots.
Data Preparation
Station
Timeslot
NE22
NE21
3-ISV3 4-ISV3
3-ISV3
VC12: 1-2
19-SP3S:1-2
NE23
3-ISU3 8-TS2
NE24
NE25
8-TS2 3-ISU3
7-ISM6-1 7-ISM6-2
NE21
3-ISV3
VC12: 1-2
9-SP3S:1-2 9-SP3S:1-2
19-SP3S:1-2
Pass through (SNCP working path)

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

113

Configuration Guide
Step 2 On the same interface, configure SNCP.

Issue 01 (2016-04-30)

114

Configuration Guide
----End
Issue 01 (2016-04-30)

115

Configuration Guide
Configuring Native Ethernet Services
About This Chapter

Native Ethernet services are categorized into two types: E-Line and E-LAN.
8.1 Basic Concepts
This section provides links to concepts related to configuring Native Ethernet services.
8.2 End-to-end Configuration Process (Native Ethernet E-Line)
Port information and fiber/cable information needs to be configured before service
information.
8.3 End-to-end Configuration Process (Native Ethernet E-LAN)
Fiber/Cable information needs to be configured before service information.
8.4 Process of Configuration on a Per-NE Basis (Native Ethernet E-Line)
Port information needs to be configured before service information.
8.5 Process of Configuration on a Per-NE Basis (Native Ethernet E-LAN)
8.6 Configuration Example (Configuring Point-to-Point Transparently Transmitted E-Line
Services)
8.7 Configuration Example (VLAN-based E-Line Services)
8.8 Configuration Example (QinQ-based E-Line Services)
8.9 Configuration Example (IEEE 802.1d Bridge-based E-LAN Services)
8.10 Configuration Example (IEEE 802.1q Bridge-based E-LAN Services)
8.11 Configuration Example (IEEE 802.1ad Bridge-based E-LAN Services)
Issue 01 (2016-04-30)

116

Configuration Guide
8.1 Basic Concepts

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

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

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

PORT1 to PORT6
respectively.
EG2 (logical board)
GE1 and GE2 correspond to

PORT1 and PORT2
respectively.

117

Configuration Guide
Equipment Type
Board Name
Ethernet Port ID
RTN 910A
EG6 (logical board)

PORT1 to PORT6
respectively.
EG4/EG4P

PORT1 to PORT4
respectively.
EG4/EG4P

PORT1 to PORT4
respectively.
EM6T/EM6TA

PORT1 and PORT2
respectively; FE1 to FE4
correspond to PORT3 to
PORT6 respectively.
RTN 950
EM6F/EM6FA
RTN 950A
RTN 980
EG6 (logical board)

PORT1 to PORT6
respectively.
EG4/EG4P

PORT1 to PORT4
respectively.
EG2D (logical board)

PORT1 and PORT2
respectively.
EX1
GE1 corresponds to PORT1.
EG4 (logical board)

PORT1 to PORT4
respectively.
EG4/EG4P

PORT1 to PORT4
respectively.
EM6T/EM6TA

PORT1 and PORT2
respectively; FE1 to FE4
correspond to PORT3 to
PORT6 respectively.
EM6F/EM6FA
8.1.3 Auto-negotiation
The auto-negotiation function enables one network device to transmit information about its
supported working modes to the remote end on the network and to receive corresponding
information from the remote end on the network.
Issue 01 (2016-04-30)

118

Configuration Guide
NOTE
If auto-negotiating equipment does not support the half-duplex mode, the auto-negotiation result will be a
full-duplex mode at the corresponding rate level.
Auto-negotiation over FE Electrical Ports

FE electrical ports support four working modes, namely, 10M half-duplex, 10M full-duplex,
100M half-duplex, and 100M full-duplex. Two ports that work in different modes cannot
communicate with each other. If auto-negotiation is enabled, the two port can communicate
with each other. Auto-negotiation matches the working modes between the local port and the
remote port by transferring information about the negotiated working mode over fast link
pulses and normal link pulses.
Rules for auto-negotiation over FE ports are provided in Table 8-1.
Table 8-1 Auto-negotiation rules for FE electrical ports (when the local port works in the
auto-negotiation mode)
Working Mode of the Remote Port
Auto-negotiation Result
Auto-negotiation
100M full-duplex
10M half-duplex
10M half-duplex
10M full-duplex
10M half-duplex
100M half-duplex
100M half-duplex
100M full-duplex
100M half-duplex
NOTE
As provided in Table 8-1, when the remote port works in 10M full-duplex or 100M full-duplex mode, autonegotiation cannot match the working modes between the local port and the remote port; as a result, packets
may still be lost. Therefore, if the remote port works in 10M full-duplex or 100M full-duplex mode, configure
the local port to work in the same mode.
When both the local FE interface and the remote FE interface work in auto-negotiation mode,
they can auto-negotiate flow control.a
Auto-Negotiation Function for GE Electrical Ports

GE electrical ports support five working modes, namely, 10M half-duplex, 10M full-duplex,
100M half-duplex, 100M full-duplex, and 1000M full-duplex. As provided in Table 8-2, the
auto-negotiation rules for GE electrical ports are similar to the auto-negotiation rules for FE
electrical ports.
Table 8-2 Auto-negotiation rules for GE electrical ports (when the local port works in the
auto-negotiation mode)
Issue 01 (2016-04-30)
Auto-negotiation (GE electrical port)
1000M full-duplex

119

Configuration Guide
FE 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
1000M full-duplex
1000M full-duplex
NOTE
As provided in Table 8-2, when the remote port works in 10M full-duplex or 100M full-duplex mode, autonegotiation cannot match the working modes between the local port and the remote port; as a result, packets
may still be lost. Therefore, if the remote port works in 10M full-duplex or 100M full-duplex mode, configure
the local port to work in the same mode.
When the GE electrical ports on both ends are working in the auto-negotiation mode, the
equipment on both ends can negotiate the flow control function through the auto-negotiation
function.a
NOTE
a: OptiX RTN 950A supports the flow control function only for point-to-point transparently transmitted ELine services.
Auto-Negotiation Function for GE/FE Optical Ports

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

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

When an Ethernet port works in auto-negotiation mode, it can implement auto-negotiation
flow control. The auto-negotiation flow control modes include:
Issue 01 (2016-04-30)

120

Configuration Guide
Asymmetric PAUSE toward Link partner

In the case of congestion, the port can send PAUSE frames but cannot process received
PAUSE frames.
Symmetric PAUSE
The port can send and process PAUSE frames.
Both asymmetric and symmetric PAUSE

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

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

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

If a mobile backhaul network uses this networking mode, each base station needs to be
assigned with a unique VLAN ID.
Issue 01 (2016-04-30)

121

Configuration Guide
On the mobile backhaul network shown in Figure 8-2, the VLANs ID that are carried by base
station services are planned in a unified manner and are unique globally. The base station
services need to share the Ethernet service bandwidth on the Hybrid microwave network
(NE1 to NE5) and be isolated from each other using VLAN IDs. The base station services are
aggregated at NE1 and then transmitted through the regional backhaul network to the BSC.
Therefore, in this example, services on the Hybrid microwave network of the mobile backhaul
network are configured as VLAN-based E-Line services.
Figure 8-2 Networking diagram of VLAN-based E-Line services
FE
BTS
VLAN 1
NE3
FE
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.5.2 Networking of IEEE 802.1d bridge-based E-LAN services

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

122

Configuration Guide
Figure 8-3 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.5.3 Networking of IEEE 802.1q Bridge-based E-LAN Services

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

123

Configuration Guide
Figure 8-4 Networking diagram of IEEE 802.1q bridge-based E-LAN services
FE
BTS
VLAN 1
NE3
FE
NE2
BTS
VLAN 1
Domain 1
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.5.4 Comparison Between the Three Networking Modes

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

124

Configuration Guide
Table 8-3 Comparison between the three networking modes

Networkin
g Type
Application Scenario
Applicable
Network
Scale
Applicable VLAN ID
Allocation
Networking
of VLANbased E-Line
services
This
networking
mode is
applicable to
all network
scale.
l The VLAN IDs that

are carried by the
received base station
services are planned in
a unified manner and
are unique globally.
l Base station services
need to share physical
Ethernet service
bandwidths and need
to be isolated by
means of VLAN IDs.
Issue 01 (2016-04-30)
Servi
ce
Stabi
lity
Service
Security
OO&M
Capabilit
y
Network
Scalability
High
l Extre
mely
high
l Service
s with
a
certain
VLAN
ID are
transmi
tted
over a
fixed
service
trail.
l Network
expansion
is difficult.
l Servi
ces
from
differ
ent
base
statio
ns are
isolat
ed
from
each
other.

l The
OAM
capabil
ity is
strong
and
only
pointtopoint
config
uration
is
support
ed.
l When a
new base
station is
added to
the
network,
E-Line
services on
all NEs
that the
base
station
services
traverse
need to be
reconfigur
ed to add
the VLAN
ID of the
new base
station.
125

Configuration Guide
Networkin
g Type
Applicable
Network
Scale
Applicable VLAN ID
Allocation
Networking
of IEEE
802.1d
bridge-based
E-LAN
services
It is
recommended
that the
network
contains less
than 50 base
stations.
l The network does not

need to sense whether
the received base
station services carry
any VLAN IDs.
l Services between ports
mounted to one bridge
do not need to be
isolated.a
Servi
ce
Stabi
lity
Service
Security
OO&M
Capabilit
y
Network
Scalability
Medi
um
l Low
l A
service
trail is
set up
by
means
of
MAC
address
selflearnin
g, and
is
variabl
e.
l Network
expansion
is simple.
l The
servic
e
packe
ts can
be
broad
cast
on the
entire
netwo
rk.
l Pointtomultip
oint
config
uration
is
support
ed. The
OAM
capabil
ity is
relative
ly
weak.
Issue 01 (2016-04-30)

l Adding a
base
station
does not
require
changing
the
configurati
ons of the
other NEs
on the
network.
You only
need to
modify the
mounted
ports on
NEs that
are
connected
to the base
station.
126

Configuration Guide
Networkin
g Type
Applicable
Network
Scale
Applicable VLAN ID
Allocation
Networking
of IEEE
802.1q
bridge-based
E-LAN
services
This
networking
mode is
applicable to
all network
scale,
especially to a
network that is
divided into
several
domains.
l The VLAN IDs that

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

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

127

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

128

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

Ethernet service
direction
NE1
1
2 Topology 4
NE2
NE4
3
Ethernet service
direction
Blocked port
NE3
Protection
switching
NE1
Ethernet service
direction
1
2 Topology 4
NE2
NE4
Ethernet service
direction
Link down
NE3
Figure 8-6 shows a multi-ring Ethernet network using ERPS V2. NE1, NE2, NE3, and NE4
form a major ring with NE4 being the RPL owner node. NE2, NE6, NE5, and NE3 form a
sub-ring with NE6 being the RPL owner node.
l
Issue 01 (2016-04-30)
Normally, NE4 blocks the port connected to the neighbor node NE1, and NE1 also
blocks the port connected to NE4. NE6 blocks the port connected to the neighbor node
NE5, and NE5 also blocks the port connected to NE6. The blocking mechanism prevents
service loops on the major ring and sub-ring.
129

Configuration Guide
When the link between NE3 and NE5 on the sub-ring fails, NE5 and NE6 unblock their
ports so that services can be transmitted along the route NE2 -> NE6 -> NE5 on the subring. NE4 and NE1 on the major ring do not unblock their ports. The service route on the
major ring remains the same.
When the link between NE1 and NE2 on the major ring fails, NE4 and NE1 unblock
their ports so that services can be transmitted along the route NE2 -> NE3 -> NE4 ->
NE1 on the major ring. NE6 and NE5 on the sub-ring do not unblock their ports. The
service route on the sub-ring remains the same.
Figure 8-6 ERPS V2 protection switching (multi-ring network)

NE4
NE1
Major ring
topology
2
3
NE3
NE2
2
3
Sub-ring
topology
GE
6
GE
5
Ethernet service
direction
Blocked port
NE6
NE5
Major ring protection switching
Sub-ring protection switching
NE4
NE1
Major ring
topology
2
3
Major
ring
topology
2
NE3
NE2
2
NE3
3
Sub-ring
topology
GE
GE
Link down
Ethernet service
direction
NE2
3
Sub-ring
topology
GE
NE4
NE1
GE
5
Link down
NE6
Blocked port
NE5
Ethernet service
direction
NE6
NE5
Blocked port
LAG
Link aggregation enables one or multiple links that are connected to the same equipment to be
aggregated into a LAG. The aggregated links are considered as a single logical link by
customers.
As shown in Figure 8-7, the LAG provides the following functions:
l
Increasing bandwidth
A LAG provides users with a cost-effective method for increasing the link bandwidth.
Users obtain data links with higher bandwidths by combining multiple physical links
into one logical link without upgrading the existing equipment. The bandwidth of the
logical link is equal to the sum of the bandwidths of the physical links. The aggregation
Issue 01 (2016-04-30)

130

Configuration Guide
module distributes the traffic to different members by using the load sharing algorithm,
therefore achieving the load sharing function at the link level.
l
Improving link availability

The links in a LAG back up each other dynamically. When a link fails, another link in
the LAG takes it over immediately. The process of starting the backup link is only
related to the links in the same LAG.
Figure 8-7 LAG

Link 1
Link 2
Ethernet
packet
Ethernet
packet
Link aggregation
group
MSTP
OptiX RTN 900 supports only the MSTP protocol that uses the common and internal
spanning tree (CIST). The MSTP that uses the CIST can be used as a rapid spanning tree
protocol (RSTP). The RSTP is used in the network loop. This protocol adopts certain
algorithms to break a loop network into a loop-free tree network and therefore prevents
packets from increasing and cycling in an endless manner on the loop network.
For OptiX RTN 900, the MSTP is used to prevent a network loop on the access side.
As shown in Figure 8-8, when the user equipment accesses the OptiX RTN 900 through two
different trails, you can configure the ports on the OptiX RTN 900 that are connected to the
user network into a port group. This port group, together with the switch on the user network,
can run the MSTP. If an service access link becomes faulty, the MSTP enables a reconfiguration and therefore the spanning tree topology is generated to provide protection for
the user network that is configured with multiple access points.
Figure 8-8 Prevention of access network loops
Root
Root
Port group
CIST
Blocked Port
Issue 01 (2016-04-30)

131

Configuration Guide
8.2 End-to-end Configuration Process (Native Ethernet ELine)

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

Before configuring Native Ethernet E-Line services, you need to know the service model.
Model
References
Point-to-point transparently transmitted ELine services
Point-to-Point Transparently Transmitted ELine Service in Feature Description
VLAN-based E-Line services
VLAN-based E-Line Service Models in

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

Feature Description
Flowchart
Flowchart for configuring Native Ethernet E-Line services from end to end is shown in this
figure.
Issue 01 (2016-04-30)

132

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

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

configurations
End
Configuring Ethernet Ports

Table 8-4 Configuring Ethernet ports
Operation
Setting
parameters
of an
Ethernet port
Issue 01 (2016-04-30)
Remarks
A.8.8.1
Setting the
Basic
Attributes
of Ethernet
Ports
Required.

133

Configuration Guide
Operation
Remarks
A.8.8.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 parameters as follows:
l If the external equipment uses the non-auto-negotiation
flow control function, set Non-Autonegotiation Flow
Control Mode to Enable Symmetric Flow Control.
l If the external equipment uses the auto-negotiation flow
control function, set Auto-Negotiation Flow Control
Mode to Enable Symmetric Flow Control.
Setting the
parameters
of an
IF_ETH
porta
A.8.9.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
Set Port Mode to Layer 2 and set Encapsulation Type
according to the network plan of the E-Line service type.
Creating a LAG for Ethernet Ports

Table 8-5 Configuring a LAG
Operation
Remarks
A.9.2.1
Creating a
LAG
Required if the LAG function needs to be used for an FE/GE port.
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
For an Ethernet link for which a LAG is configured, configure parameters only for the main port. The
following operations described in this section are also applicable to the main port only.
Issue 01 (2016-04-30)

134

Configuration Guide
Configuring Native Ethernet E-Line Services

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

have not been created on the main topology of the U2000.
During the creation, do not use the automatically allocated IP addresses.
A.15.3.2
Creating ELine Services
over Native
Ethernet
Required.
A.9.3.12
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.
NOTE
Configure the VLAN forwarding table items separately for the source port and
sink port.
Configuring QoS
For details about the QoS configuration procedure, seeConfiguration Process (QoS/HQoS).
Verifying Ethernet Services

Table 8-7 Verifying Ethernet services
Issue 01 (2016-04-30)
Operation
Remarks
A.15.3.5
Verifying
Native
Ethernet
Services
Required.
The LB test result should show that no packet loss occurs.

135

Configuration Guide
8.3 End-to-end Configuration Process (Native Ethernet ELAN)

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

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

Models in Feature Description
IEEE 802.1q bridge-based E-LAN services
802.1Q Bridge-based E-LAN Service

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

Feature Description
NOTE
IEEE 802.1q and IEEE 802.1ad bridges are recommended. The two types of bridges can isolate broadcast
domains through VLANs, minimizing the possibility of loops. Do not use IEEE 802.1d bridges if possible.
Flowchart
Flowchart for configuring Native Ethernet E-LAN services from end to end is shown in this
figure.
Figure 8-10 Flowchart (Native Ethernet E-LAN services)
Required
Start
Optional
Configure LAGs.
Configure E-LAN services
Configure QoS
Verify Ethernet service

configurations.
End
Issue 01 (2016-04-30)

136

Configuration Guide

Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
Configuring Native Ethernet E-LAN Services

Table 8-9 Configuring Native Ethernet E-LAN services
Operation
Remarks
A.3.5.1 Creating Optical Fibers by Using

the Search Method
Perform this task to create microwave links

for the service trails if they have not been
created on the main topology of the U2000.
Creating a Fiber/Cable by Using the

Search Method
Required to create Ethernet fibers/cables for

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

Native Ethernet
Required.
A.9.9.13 Enabling/Disabling Automatic

Service Loop Detection
Optional.
Set the parameters according to the service

plan and parameter plan.
NOTE
If the network carries both E-LAN and E-Line services, configure end-to-end hybrid services instead of endto-end E-LAN services.
Issue 01 (2016-04-30)

137

Configuration Guide
Configuring QoS

Operation
Remarks
A.15.3.5
Verifying
Native
Ethernet
Services
Required.
8.4 Process of Configuration on a Per-NE Basis (Native

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

Before configuring Native Ethernet E-Line services, you need to know the service model.
Model
References
Point-to-point transparently transmitted ELine services
Point-to-Point Transparently Transmitted ELine Service in Feature Description
VLAN-based E-Line services
VLAN-based E-Line Service Models in

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

Feature Description
Flowchart
Flowchart for configuring Native Ethernet E-Line services is shown in this figure.
Issue 01 (2016-04-30)

138

Configuration Guide
Figure 8-11 Flowchart (Native Ethernet E-Line services)

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

configurations
End

Operation
Setting
parameters
of an
Ethernet port
Issue 01 (2016-04-30)
Remarks
A.8.8.1
Setting the
Basic
Attributes
of Ethernet
Ports
Required.
A.8.8.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.
l If the external equipment uses the non-auto-negotiation
flow control function, set Non-Autonegotiation Flow
Control Mode to Enable Symmetric Flow Control.
l If the external equipment uses the auto-negotiation flow
control function, set Auto-Negotiation Flow Control
Mode to Enable Symmetric Flow Control.

139

Configuration Guide
Operation
Remarks
Setting the
parameters
of an
IF_ETH port
A.8.8.3
Setting the
Layer 2
Attributes
of Ethernet
Ports
Required.
A.8.9.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
A.8.9.2
Setting the
Layer 2
Attributes
of IF_ETH
Ports
Required.

Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
Issue 01 (2016-04-30)

140

Configuration Guide
Configuring Native Ethernet E-Line Services

Table 8-13 Configuring Native Ethernet E-Line services
Operation
Remarks
A.9.3.3
Configuring
UNI-UNI ELine Services
(U2000) or A.
9.3.4
Configuring
UNI-UNI ELine
Services(Web
LCT)
Required.
A.9.3.12
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 parameters according to the network plan.
NOTE
Configure the VLAN forwarding table items separately for the source port and
sink port.
Configuring QoS

Operation
Remarks
A.15.3.5
Verifying
Native
Ethernet
Services
Required.
8.5 Process of Configuration on a Per-NE Basis (Native

Ethernet E-LAN)
Issue 01 (2016-04-30)

141

Configuration Guide
Getting to Know the Native Ethernet E-LAN Service Model

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

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

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

Feature Description
NOTE
IEEE 802.1q and IEEE 802.1ad bridges are recommended. The two types of bridges can isolate broadcast
domains through VLANs, minimizing the possibility of loops. Do not use IEEE 802.1d bridges if possible.
Flowchart
Flowchart for configuring Native Ethernet E-LAN services is shown in this figure.
Figure 8-12 Flowchart (Native Ethernet E-LAN services)
Required
Start
Optional
Configure Ethernet ports.
Configure IF_ETH ports.
Configure LAGs.
Configure ERPS protection.
Configure E-LAN services
Configure QoS

configurations.
End
Issue 01 (2016-04-30)

142

Configuration Guide

Remarks
Operation
Setting
parameters
of an
Ethernet port
Setting the
parameters
of an
IF_ETH port
Issue 01 (2016-04-30)
A.8.8.1
Setting the
Basic
Attributes
of Ethernet
Ports
Required.
A.8.8.3
Setting the
Layer 2
Attributes
of Ethernet
Ports
Required.
A.8.8.5
Setting the
Advanced
Attributes
of Ethernet
Ports
Required.
A.8.9.1
Setting the
Basic
Attributes
of IF_ETH
Ports
Required.
A.8.9.2
Setting the
Layer 2
Attributes
of IF_ETH
Ports
Required.
A.8.9.4
Setting the
Advanced
Attributes
of IF_ETH
Ports
Required.

143

Configuration Guide

Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
Configuring ERPS
Table 8-17 Configuring ERPS (OptiX RTN 950A)
Operation
Remarks
A.9.1.1
Creating
Ethernet Ring
Protection
Instances
Required when services on an Ethernet ring need to be protected.
A.9.1.2 Setting
Global ERPS
Protocol
Parameters
Required when the ERPS protocol parameters need to be modified

according to the network plan.
Table 8-18 Configuring ERPS (OptiX RTN 905, 950, 980)
Issue 01 (2016-04-30)
Step
Operation
Remarks
A.9.1.1
Creating
Ethernet Ring
Protection
Instances
Required.
A.9.1.3 Setting
Protocol
Parameters for
an ERPS
Instance
Required when ERPS V1 or a multi-ring network needs to be

configured.

144

Configuration Guide
Step
Operation
Remarks
A.9.1.2 Setting
Global ERPS
Protocol
Parameters
Required when the ERPS protocol parameters need to be

modified according to the network plan.
A.9.1.4
Creating a
Virtual
Channel VLAN
Forwarding
Table
Required when R-APS virtual channels are used.
Configuring Native Ethernet E-LAN Services

Table 8-19 Configuring Native Ethernet E-LAN services
Issue 01 (2016-04-30)
Operation
Remarks
A.9.3.16 Configuring
IEEE 802.1q Bridge-Based
E-LAN Services(U2000) or
IEEE 802.1q Bridge-Based
E-LAN Services(Web
LCT)
Required.
A.9.9.13 Enabling/
Disabling Automatic
Service Loop Detection
Optional.
Managing
the MAC
address table
A.9.4.2
Creating a
Blacklist
Entry of
MAC
Addresses
Required when you need to disable NEs with certain MAC

addresses from using E-LAN services.
A.9.4.1
Creating a
Static MAC
Address
Entry
Required if you need to enable certain MAC address entries

not to age.
A.9.4.3
Configuring
the MAC
Address
Learning
Parameters
Required if you need to disable the aging function or change

the aging time (5 minutes by default).

145

Configuration Guide
Configuring QoS

Operation
Remarks
A.15.3.5
Verifying
Native
Ethernet
Services
Required.
8.6 Configuration Example (Configuring Point-to-Point

Transparently Transmitted E-Line Services)

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

are configured and a QoS policy is configured for the services.
Issue 01 (2016-04-30)

146

Configuration Guide
Figure 8-13 Networking diagram (point-to-point transparently transmitted E-Line services)
Tranparent transmitted
E-Line service
Backhaul network
NE1
BSC
NE2
NodeB
NE1 (RTN 905 1E)
7-EG61 (to NodeB)
3-ISV3-1 (to NE2)

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

Set encapsulation type to null for all ports.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Encapsulation type
Null
For point-to-point
transparently transmitted
services, this parameter
takes the fixed value of
Null.

147

Configuration Guide
Item
Planning Principle
Port working mode
Auto-negotiation
l In this example, the GE

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

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

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

148

Configuration Guide
Step 2 Set the basic attributes of IF_ETH ports.
----End
8.6.2.2 Configuring Service Information

The source VLAN ID and sink VLAN ID does not need to be configured for services.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Service ID
Service name
BTStoNE2_Tline
Direction
UNI-UNI
BPDU
Not transparently
transmitted

149

Configuration Guide
Item
Planning Principle
Source port
7-EG6-1
Source VLAN ID
The source VLAN ID for a

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

transparently transmitted ELine service needs to be set
to empty.
Procedure
Step 1 Configure E-Line services.
----End
8.6.2.3 Configuring QoS

For point-to-point transparently transmitted E-Line services, a DiffServ domain based on CVLAN priorities is inapplicable. Therefore, the packet type must be DSCP.
Issue 01 (2016-04-30)

150

Configuration Guide
Data Preparation
Item
Planning Principle
Mapping between packet

priorities and PHB classes
l DiffServ configuration
should be the same for
each service port.
l The trusted packet types
of all services ports must
be base on DSCP values.
DSCP
Service type
Voice,signalling
OM,video
R99 data
HSPA data
40
24
16
0
Backhaul network
NE1
NE2
NodeB
DSCP
40
24
16
0
PHB
EF
AF3
AF2
BE
BSC
DSCP
40
24
16
0
DS mapping
Procedure
Step 1 Query the mapping in the DiffServ domain to ensure that the default setting is the same as the
planned setting.
This figure shows ingress mapping.
Issue 01 (2016-04-30)

151

Configuration Guide
This figure shows egress mapping.
Issue 01 (2016-04-30)

152

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

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

153

Configuration Guide
Step 2 Create an MA.
Step 3 Create MP.
Issue 01 (2016-04-30)

154

Configuration Guide
Step 4 Create remote MPs.
Step 5 Verify Ethernet services by using the LB function. For details, see A.9.9.7 Performing an LB
Test.
Perform an LB test by considering the MP whose ID is 101 as the source MP and the MP
whose ID is 102 as the sink MP.
Issue 01 (2016-04-30)

155

Configuration Guide
There should be no packet loss during the LB tests.

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


On the network, VLAN IDs are used to differentiate services from different base stations.
Network), 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 must carry VLAN IDs, and VLAN IDs on the entire
network must be planned in a unified manner.
VLAN priorities have been configured on each BTS according to service types.
To meet the preceding requirements, VLAN-based E-Line services are configured for each
NE; in addition, corresponding QoS policies are configured.
Figure 8-14 Networking diagram (VLAN-based E-Line services)
NE13 (RTN 950A)
17-EG61 (to NE12)
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15)
BTS12
VLAN 110
FE
NE12 (RTN 950A)

17-EG61 (to NE13)
3-ISV3-1 (to NE11)
17-EG62 (to BTS11)
R4
GE
NE14 (RTN 905 2E)

7-EG61 (to BTS12)
3-ISV3-1 (to NE13)
NE14
FE
NE13
FE
NE15
NE16
NE16 (RTN 905 1E)
7-EG61 (to BTS15)
3-ISV3-1 (to NE15)
R4
BTS15
VLAN 120
NE12
NE15 (RTN 950A)

3-ISV3-1 (to NE16)
4-ISV3-1 (to NE13)
R4
BTS11
VLAN 100
NE11
RNC
VLAN 100, 110, 120
NE11 (RTN 980)

17-EG2D1 (to RNC)
3-ISV3-1 (to NE12)
8.7.2 End-to-End Configuration Procedure

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

In this example, Ethernet ports are configured during configuration of service information.
Issue 01 (2016-04-30)

156

Configuration Guide
Data Preparation
Item
Planning Principle
Encapsulation type
802.1Q
For a port that carries

VLAN-based E-Line
802.1Q.
Port working mode
Auto-negotiation
l In this example, the

FE/GE port on all the
BTSs work in autonegotiation mode.
Therefore, Ethernet ports
on all the NEs that
receive the BTS services
must also work in autonegotiation mode. If a
peer Ethernet port work
in another mode, the
local Ethernet port must
work in the same mode.
auto-negotiation.
Max frame length
Issue 01 (2016-04-30)
1536


the equipment, the
157

Configuration Guide
Item
Planning Principle
Flow control
Disabled

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

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

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

158

Configuration Guide
1.
2.
Configure the source node for the service trail.
3.
Configure the sink node for the service trail.
Issue 01 (2016-04-30)

159

Configuration Guide
----End

In this example, the DS domain is deployed based on VLAN priorities for Native Ethernet
services.
Data Preparation
Item
Planning Principles

priorities and PHBs
l DiffServ configurations
each service port.
l The service ports trust
packets with VLAN
priorities (the default
setting).
Issue 01 (2016-04-30)

160

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

161

Configuration Guide
NOTE
AF3.
----End

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

162

Configuration Guide
2.
Issue 01 (2016-04-30)
Start an LB test.

163

Configuration Guide
3.
Issue 01 (2016-04-30)
View the test result.

164

Configuration Guide
----End
8.7.3 Per-NE Configuration Process

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

Set encapsulation type to 802.1Q for each port.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Encapsulation type
802.1Q
For a port that carries

VLAN-based E-Line
802.1Q.

165

Configuration Guide
Item
Planning Principle
Port working mode
Auto-negotiation

on all the NEs that
auto-negotiation.
Issue 01 (2016-04-30)
Max frame length
1536

the equipment, the
Flow control
Disabled

both ends.
Tag attribute
Tag Aware

services carry VLAN IDs.
Therefore, the tag attributes
of all the service ports are
Tag Aware.

166

Configuration Guide
Procedure
Step 2 Query the Layer 2 attributes of the Ethernet port and ensure that the Tag attribute is Tag
Aware.

Issue 01 (2016-04-30)

167

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

The source VLAN ID and sink VLAN ID need to be configured for each service.
Issue 01 (2016-04-30)

168

Configuration Guide
Data Preparation
Item
Planning Principle
Service information
Set IDs and names for

network-wide E-Line
services according to the
network plan.
BPDU
Not transparently
transmitted

NE11 (RTN 980)
NE12 (RTN 950A)
3-ISV3-1
RNC to BTS11
3-ISV3-1 17-EG6-1
17-EG6-1 4-ISV3-1
NE15 (RTN 950A)
NE16 (RTN
905 1E)
4-ISV3-1 3-ISV3-1
3-ISV3-1
C:100
17-EG2D-1(C:100)
7-EG6-1(C:100)
C:120
RNC to BTS15
RNC to BTS12
NE13 (RTN 950A)
C:120
17-EG2D-1(C:120)
C:110
C:120
C:120
7-EG6-1(C:120)
C:110
17-EG2D-1(C:110)
Links-2: NE13-NE14
NE13
NE14
17-EG6-1 3-ISV3-1
RNC to BTS12
C:110
3-ISV3-1
C:110
7-EG6-1(C:110)
S: S-VLAN
C: C-VLAN
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure VLAN-based E-Line services.
Issue 01 (2016-04-30)

169

Configuration Guide
----End

services.
Data Preparation
Item
Planning Principles

priorities and PHBs
each service port.
packets with VLAN
setting).
VLAN Pri.
PHB
5
3
2
0
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
PHB
5
3
2
0
DS mapping
VLAN Pri.
EF
AF3
AF2
BE
FE
5
3
2
0
DS mapping
R4
GE
BTS12
NE14
FE
NE13
VLAN Pri.
5
3
2
0
PHB
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
R4
FE
BTS11
NE15
NE16
R4
BTS15
DS mapping
Issue 01 (2016-04-30)
RNC
NE11
NE12
VLAN Pri.
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
5
3
2
0
PHB
EF
AF3
AF2
BE
VLAN Pri.
5
3
2
0
VLAN Pri.
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
DS mapping

170

Configuration Guide
Procedure
planned setting.
Issue 01 (2016-04-30)

171

Configuration Guide
NOTE
AF3.
----End

Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE12, NE14, and NE16.
Issue 01 (2016-04-30)

172

Configuration Guide
Step 2 Create a maintenance association (MA) for NE11, NE12, NE14, and NE16.
Step 3 Create maintenance points (MPs) for NE11, NE12, NE14, and NE16.
Issue 01 (2016-04-30)

173

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

174

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

l

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


On the network, QinQ tags are used to differentiate services from different base stations.
l
BTS11 to BTS15 provide FE ports whose port rate is 100 Mbit/s.
The VLAN ID of services from each BTS is allocated by the BTS. Services from
different BTSs may carry the same VLAN ID. To solve this problem, an RNC allocates a
unique S-VLAN ID for each BTS, and S-VLAN IDs on the entire network are planned in
a unified manner.
To meet the preceding requirements, QinQ-based E-Line services are configured for each NE;
in addition, corresponding QoS policies are configured.
Figure 8-15 Networking diagram (QinQ-based E-Line services)
NE13 (RTN 950A)
17-EG61 (to NE12)
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15)
BTS12
SVLAN 201
FE
NE12 (RTN 950A)

17-EG61 (to NE13)
3-ISV3-1 (to NE11)
17-EG62 (to BTS11)
R4
GE
NE14 (RTN 905 2E)

7-EG61 (to BTS12)
3-ISV3-1 (to NE13)
NE14
FE
NE13
FE
NE15
NE16
NE16 (RTN 905 1E)
7-EG61 (to BTS15)
3-ISV3-1 (to NE16)
R4
BTS15
SVLAN 202
NE15 (RTN 950A)

3-ISV3-1 (to NE16)
4-ISV3-1 (to NE13)
NE12
R4
BTS11
SVLAN 200
NE11
RNC
SVLAN 200, 201, 202
NE11 (RTN 980)

17-EG2D1 (to RNC)
3-ISV3-1 (to NE12)
NOTE
In this example, the BTS/RNC is capable of processing S-VLAN IDs.
Issue 01 (2016-04-30)

175

Configuration Guide


Data Preparation
Item
Planning Principle
Encapsulation type
QinQ
Because BTS services carry

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

on all the NEs that
auto-negotiation.
Issue 01 (2016-04-30)

176

Configuration Guide
Issue 01 (2016-04-30)
Item
Planning Principle
Max frame length
1536

the equipment, the
Flow control
Disabled

both ends.
QinQ type domain
0x88A8

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

177

Configuration Guide

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

178

Configuration Guide
2.
Configure the source node for the service trail.
3.
Configure the sink node for the service trail.
Issue 01 (2016-04-30)

179

Configuration Guide
----End

In this example, DS is deployed for UNIs base on C-VLAN priorities and for NNIs base on SVLAN priorities.
Data Preparation
Item
Planning Principle

each service port.
of all NNI ports must be
base on S-VLAN
priorities.
Issue 01 (2016-04-30)

180

Configuration Guide
CVLAN Pri.
PHB
5
3
2
0
SVLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
SVLAN Pri.
DS mapping
Service type
PHB
CVLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
PHB
5
3
2
0
SVLAN Pri.
EF
AF3
AF2
BE
FE
5
3
2
0
DS mapping
R4
GE
BTS12
NE14
FE
NE13
CVLAN Pri.
5
3
2
0
PHB
RNC
NE11
NE12
SVLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
SVLAN Pri.
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
R4
FE
BTS11
NE15
NE16
R4
BTS15
SVLAN Pri.
DS mapping
Service type
PHB
CVLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
5
3
2
0
PHB
EF
AF3
AF2
BE
SVLAN Pri.
5
3
2
0
CVLAN Pri.
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
DS mapping
Procedure
planned setting.
Issue 01 (2016-04-30)

181

Configuration Guide
NOTE
AF3.
Step 2 Change the packet type trusted by a port.

----End
Issue 01 (2016-04-30)

182

Configuration Guide

Procedure
1.
2.
Start an LB test.
Issue 01 (2016-04-30)

183

Configuration Guide
3.
Issue 01 (2016-04-30)

184

Configuration Guide
----End

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

This section describes the procedure for configuring Ethernet ports.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Encapsulation type
QinQ
Because BTS services carry

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

185

Configuration Guide
Item
Planning Principle
Port working mode
Auto-negotiation

on all the NEs that
auto-negotiation.
Issue 01 (2016-04-30)
Max frame length
1536

the equipment, the
Flow control
Disabled

both ends.

186

Configuration Guide
Item
Planning Principle
QinQ type domain
0x88A8

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

----End
Issue 01 (2016-04-30)

187

Configuration Guide

QinQ links between NNI ports need to be configured before service information.
Data Preparation
Item
Planning Principle
Service information
Set IDs and names for

network-wide E-Line
services according to the
network plan.
BPDU
Not transparently
transmitted

NE11 (RTN 980)
NE12 (RTN 950A)
3-ISV3-1
RNC to BTS11
3-ISV3-1 17-EG6-1
NE15 (RTN 950A)
17-EG6-1 4-ISV3-1
NE16 (RTN
905 1E)
4-ISV3-1 3-ISV3-1
3-ISV3-1
S: 200
17-EG2D-1(S: 200)
7-EG6-1(S: 200l)
S: 202
RNC to BTS15
RNC to BTS12
NE13 (RTN 950A)
S: 202
17-EG2D-1(S: 202)
S: 201
S: 202
S: 202
7-EG6-1(S: 202)
S: 201
17-EG2D-1(S: 201)
Links-2: NE13-NE14
NE13
NE14
17-EG6-1 3-ISV3-1
RNC to BTS12
S: 201
3-ISV3-1
S: 201
7-EG6-1(S: 201)
C: C-VLAN
S: S-VLAN
Pass through
Add/Drop
Foward
Procedure
Step 1 Configure a QinQ link.
Issue 01 (2016-04-30)

188

Configuration Guide

----End

In this example, DS is deployed for UNIs base on C-VLAN priorities and for NNIs base on SVLAN priorities.
Issue 01 (2016-04-30)

189

Configuration Guide
Data Preparation
Item
Planning Principle

each service port.
base on S-VLAN
priorities.
CVLAN Pri.
PHB
5
3
2
0
SVLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
SVLAN Pri.
Service type
PHB
CVLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
PHB
5
3
2
0
DS mapping
SVLAN Pri.
EF
AF3
AF2
BE
FE
5
3
2
0
DS mapping
R4
GE
BTS12
NE14
FE
NE13
CVLAN Pri.
5
3
2
0
PHB
RNC
NE11
NE12
SVLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
SVLAN Pri.
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
R4
FE
BTS11
NE15
NE16
R4
BTS15
SVLAN Pri.
DS mapping
Service type
PHB
CVLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
5
3
2
0
PHB
EF
AF3
AF2
BE
SVLAN Pri.
5
3
2
0
CVLAN Pri.
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
DS mapping
Procedure
planned setting.
Issue 01 (2016-04-30)

190

Configuration Guide
Issue 01 (2016-04-30)

191

Configuration Guide
NOTE
AF3.

----End

This section describes the procedure for verifying Ethernet service configurations.
Procedure
Issue 01 (2016-04-30)

192

Configuration Guide
Issue 01 (2016-04-30)

193

Configuration Guide
NOTE
NOTE
Issue 01 (2016-04-30)

194

Configuration Guide

l

----End
8.9 Configuration Example (IEEE 802.1d Bridge-based ELAN Services)


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

195

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

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

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
NE24
802.1d bridge
BTS24
NE25 (RTN 910A)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)


In this example, Ethernet ports and ERPS are configured during the configuration of service
information.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Tag type
Tag-Transparent
Set the tag type to TagTransparent for all IEEE

802.1d bridges.
Ports mounted to a bridge
Broadcast packet
suppression
Enabled

196

Configuration Guide
Item
Planning Principle
Max frame length
1536

the equipment, the
ERPS information
One ERPS ring:

l Has only one ERPS
owner node.
l The control VLAN ID
should be unique and
different from service
VLAN IDs.
Issue 01 (2016-04-30)

197

Configuration Guide
Figure 8-17 Ports mounted to a bridge

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

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
Issue 01 (2016-04-30)
NE24
802.1d bridge
BTS24
NE25 (RTN 910A)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)

198

Configuration Guide
Figure 8-18 ERPS information

3-ISV3-1 (East, RPL
neighbor port)
4-ISV3-1 (West)
Control VLAN: 4094
3-ISV3-1 (East, RPL port)
4-ISV3-1 (West)
Control VLAN: 4094
GE
NE21
RNC
FE
R4
BTS21
FE
R4
NE22
NE25
FE
R4
BTS23
7-EG61 (East)
3-ISV3-1 (West, RPL
neighbor port)
Control VLAN: 4094
NE24
NE23
BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
Control VLAN: 4094
3-ISV3-1 (East)
7-EG61 (West, RPL next
neighbor port)
Control VLAN: 4094
Procedure
Step 1 Configure ERPS.
Issue 01 (2016-04-30)

199

Configuration Guide
Step 2 Create 802.1d bridge-based E-LAN services.

1.
Issue 01 (2016-04-30)

200

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

In this example, the DiffServ domain is deployed based on C-VLAN priorities.
Issue 01 (2016-04-30)

201

Configuration Guide
Data Preparation
Item
Planning Principle

each service port.
packets with VLAN
setting).
VLAN Pri.
PHB
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
VLAN Pri.
RNC
PHB
5
3
2
0
GE
NE21
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
FE
R4
BTS21
NE22
NE25
R4
BTS24
VLAN Pri.
5
3
2
0
PHB
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
NE23
FE
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
NE24
R4
BTS23
DS mapping
VLAN Pri.
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
5
3
2
0
PHB
EF
AF3
AF2
BE
VLAN Pri.
5
3
2
0
DS mapping
Procedure
planned setting.
Issue 01 (2016-04-30)

202

Configuration Guide
Issue 01 (2016-04-30)

203

Configuration Guide
NOTE
AF3.
----End

Procedure
1.
Issue 01 (2016-04-30)

204

Configuration Guide
2.
Start an LB test.
3.
Issue 01 (2016-04-30)

205

Configuration Guide
----End

next NE.

Set encapsulation type to null for all ports.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Encapsulation type
Null
Set this parameter to Null

for ports mounted to an
IEEE 802.1d bridge.

206

Configuration Guide
Item
Planning Principle
Port working mode
Auto-negotiation

in auto-negotiation
same mode.
auto-negotiation.
Issue 01 (2016-04-30)
Max frame length
1536

the equipment, the
Flow control
Disabled

both ends.
Broadcast packet
suppression
Enabled

207

Configuration Guide

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

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

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
NE24
802.1d bridge
BTS24
NE25 (RTN 910A)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)
Procedure
Step 2 Set the advanced attributes of Ethernet ports.

Issue 01 (2016-04-30)

208

Configuration Guide

Step 4 Set the advanced attributes of IF_ETH ports.

Issue 01 (2016-04-30)

209

Configuration Guide
----End
8.9.3.2 Configuring ERPS

In this example, ERPS V2 NEs are used as RPL owner nodes for configuring ring network
protection.
Data Preparation
Item
Planning Principle
ERPS information
One ERPS ring:

l Has only one ERPS
owner node.
VLAN IDs.
Issue 01 (2016-04-30)

210

Configuration Guide

3-ISV3-1 (East, RPL
neighbor port)
4-ISV3-1 (West)
Control VLAN: 4094

4-ISV3-1 (West)
Control VLAN: 4094
GE
NE21
RNC
FE
R4
BTS21
FE
R4
NE22
NE25
FE
R4
BTS23
7-EG61 (East)
3-ISV3-1 (West, RPL
neighbor port)
Control VLAN: 4094
NE24
NE23
BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
Control VLAN: 4094
3-ISV3-1 (East)
neighbor port)
Control VLAN: 4094
Procedure
Issue 01 (2016-04-30)

211

Configuration Guide
----End

The tag type needs to be set to Tag-Transparent.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Tag type
Tag-Transparent
Set the tag type to TagTransparent for all IEEE

802.1d bridges.

212

Configuration Guide

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

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
NE24
802.1d bridge
BTS24
NE25 (RTN 910A)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)
Procedure
Step 1 Configure E-LAN services.
----End
Issue 01 (2016-04-30)

213

Configuration Guide

In this example, the DiffServ domain is deployed based on C-VLAN priorities.
Data Preparation
Item
Planning Principle

each service port.
packets with VLAN
setting).
VLAN Pri.
PHB
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
VLAN Pri.
RNC
PHB
5
3
2
0
GE
NE21
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
FE
R4
BTS21
NE22
NE25
R4
BTS24
VLAN Pri.
5
3
2
0
PHB
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
NE23
FE
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
NE24
R4
BTS23
DS mapping
VLAN Pri.
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
5
3
2
0
PHB
EF
AF3
AF2
BE
VLAN Pri.
5
3
2
0
DS mapping
Procedure
planned setting.
Issue 01 (2016-04-30)

214

Configuration Guide
Issue 01 (2016-04-30)

215

Configuration Guide
NOTE
AF3.
----End

Procedure
Issue 01 (2016-04-30)

216

Configuration Guide
NOTE
l On port 17-EG6-1 of NE21, create three MPs with the IDs of 102, 103, and 105 respectively.
Issue 01 (2016-04-30)

217

Configuration Guide
NOTE

l

----End
8.10 Configuration Example (IEEE 802.1q Bridge-based ELAN Services)


On the network, VLAN IDs are used to differentiate services from base stations in different
domains.
Issue 01 (2016-04-30)

218

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

7-EG61 (to BTS12)
3-ISV3-1 (to NE13)
NE14
NE13
FE
NE15
NE16
NE16 (RTN 905 1E)
7-EG61 (to BTS15)
3-ISV3-1 (to NE15)
R4
BTS15
VLAN 110
NE15 (RTN 950A)

3-ISV3-1 (to NE16)
4-ISV3-1 (to NE13)
NE11
NE12
NE12 (RTN 950A)

17-EG61 (to NE13)
3-ISV3-1 (to NE11)
17-EG62 (to BTS11)
RNC
VLAN 100, 110
NE11 (RTN 980)
17-EG2D1 (to RNC)
3-ISV3-1 (to NE12)

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

Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Tag type
C-Aware
Set the tag type to C-Aware

for all IEEE 802.1q bridges.

219

Configuration Guide
Item
Planning Principle
Max frame length
1536

the equipment, the
Broadcast packet
suppression
Enabled

NE13 (RTN 950A)
17-EG61 (to NE12)
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15)
BTS12
VLAN 100
FE
BTS11
R4 VLAN 100
FE
R4
GE
NE14 (RTN 905 2E)

7-EG61 (to BTS12)
3-ISV3-1 (to NE13)
NE14
NE13
FE
NE15
NE16
NE16 (RTN 905 1E)
7-EG61 (to BTS15)
3-ISV3-1 (to NE15)
R4
BTS15
VLAN 110
NE12
NE15 (RTN 950A)

3-ISV3-1 (to NE16)
4-ISV3-1 (to NE13)
NE11
NE12 (RTN 950A)

17-EG61 (to NE13)
3-ISV3-1 (to NE11)
17-EG62 (to BTS11)
RNC
VLAN 100, 110
NE11 (RTN 980)
17-EG2D1 (to RNC)
3-ISV3-1 (to NE12)
Procedure
Step 1 Create an IEEE 802.1q bridge-based E-LAN service.
1.
Issue 01 (2016-04-30)

220

Configuration Guide
2.
NOTE
----End

In this example, DiffServ is deployed based on C-VLAN priorities.
Procedure
planned setting.
Issue 01 (2016-04-30)

221

Configuration Guide
Issue 01 (2016-04-30)

222

Configuration Guide
NOTE
AF3.
----End

Procedure
Issue 01 (2016-04-30)

223

Configuration Guide
NOTE
Issue 01 (2016-04-30)

224

Configuration Guide
NOTE

l

----End

next NE.

Issue 01 (2016-04-30)

225

Configuration Guide
Data Preparation
Item
Planning Principle
Encapsulation type
802.1Q
Set this parameter to 802.1Q

for ports mounted to an
IEEE 802.1q bridge.
Port working mode
Auto-negotiation

in auto-negotiation
same mode.
auto-negotiation.
Issue 01 (2016-04-30)
Max frame length
1536

the equipment, the
Flow control
Disabled

both ends.

226

Configuration Guide
Item
Planning Principle
Tag attribute
Tag Aware
Because all base station

services carry VLAN IDs,
set this parameter to Tag
Aware.
Broadcast packet
suppression
Enabled
NE13 (RTN 950A)

17-EG61 (to NE12)
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15)
BTS12
VLAN 100
FE
BTS11
R4 VLAN 100
FE
R4
GE
NE14 (RTN 905 2E)

7-EG61 (to BTS12)
3-ISV3-1 (to NE13)
NE14
NE13
FE
NE15
NE16
NE16 (RTN 905 1E)
7-EG61 (to BTS15)
3-ISV3-1 (to NE15)
R4
BTS15
VLAN 110
NE15 (RTN 950A)

3-ISV3-1 (to NE16)
4-ISV3-1 (to NE13)
NE12
NE11
NE12 (RTN 950A)

17-EG61 (to NE13)
3-ISV3-1 (to NE11)
17-EG62 (to BTS11)
RNC
VLAN 100, 110
NE11 (RTN 980)
17-EG2D1 (to RNC)
3-ISV3-1 (to NE12)
Procedure
Step 2 Query the Layer 2 attributes of the Ethernet port and ensure that the Tag attribute is Tag
Aware.
Issue 01 (2016-04-30)

227

Configuration Guide

Issue 01 (2016-04-30)

228

Configuration Guide
Step 5 Query the Layer 2 attributes of the IF_ETH port and ensure that the Tag attribute is the default
value Tag Aware.
Issue 01 (2016-04-30)

229

Configuration Guide
----End

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

for all IEEE 802.1q bridges.

NE13 (RTN 950A)
17-EG61 (to NE12)
3-ISV3-1 (to NE14)
4-ISV3-1 (to NE15)
BTS12
VLAN 100
FE
BTS11
R4 VLAN 100
FE
R4
GE
NE14 (RTN 905 2E)

7-EG61 (to BTS12)
3-ISV3-1 (to NE13)
NE14
NE13
FE
NE15
NE16
NE16 (RTN 905 1E)
7-EG61 (to BTS15)
3-ISV3-1 (to NE15)
Issue 01 (2016-04-30)
R4
BTS15
VLAN 110
NE15 (RTN 950A)

3-ISV3-1 (to NE16)
4-ISV3-1 (to NE13)
NE12
NE11
NE12 (RTN 950A)

17-EG61 (to NE13)
3-ISV3-1 (to NE11)
17-EG62 (to BTS11)

RNC
VLAN 100, 110
NE11 (RTN 980)
17-EG2D1 (to RNC)
3-ISV3-1 (to NE12)
230

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

In this example, DiffServ is deployed based on C-VLAN priorities.
Procedure
planned setting.
Issue 01 (2016-04-30)

231

Configuration Guide
Issue 01 (2016-04-30)

232

Configuration Guide
NOTE
AF3.
----End

Procedure
Issue 01 (2016-04-30)

233

Configuration Guide
NOTE
Issue 01 (2016-04-30)

234

Configuration Guide
NOTE

l

----End
8.11 Configuration Example (IEEE 802.1ad Bridge-based ELAN Services)


Issue 01 (2016-04-30)

235

Configuration Guide
The RNC provides GE ports whose port rate is 1000 Mbit/s.
VLAN IDs are allocated by the RNC to its managed BTSs.
The VLAN IDs of services on BTSs that are managed by different RNCs may be the
same. Therefore, the transport network allocates an S-VLAN ID for services from each
BTSs, and the S-VLAN IDs on the entire network are planned in a unified manner.
The Ethernet services on the ring network need to be protected.
To meet the preceding requirements, IEEE 802.1ad bridge-based E-LAN services are
configured to transmit BTS services; in addition, broadcast packet suppression, ERPS
protection, and QoS policies are configured, as shown in the following figure.
Figure 8-23 Networking diagram (IEEE 802.1ad bridge-based E-LAN services)
RNC2
GE
NE21 (RTN 905 2E)
7-EG61 (to BTS21)
3-ISV3-1 (to NE23)
4-ISV3-1 (to NE21)
GE
RNC1
NE21 (RTN 950A)

17-EG61 (to RNC1)
17-EG62 (to RNC2)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21
802.1ad bridge
FE
R4
BTS21
CVLAN 100
SVLAN 200
FE
NE22
802.1ad bridge
NE25
802.1ad bridge
FE
BTS23
CVLAN 110
SVLAN 200
R4
NE24
802.1ad bridge
NE23
802.1ad bridge
NE23 (RTN 905 1E)

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
R4
BTS24
CVLAN 100
SVLAN 201
NE25 (RTN 905 2E)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)


In this example, Ethernet ports and ERPS are configured during the configuration of service
information.
Issue 01 (2016-04-30)

236

Configuration Guide
Data Preparation
Item
Planning Principle
Tag type
S-Aware
Set the tag type to S-Aware

for all IEEE 802.1ad
bridges.
In this example, base station

services carry C-VLAN IDs.
However, because the CVLAN IDs of BTS21 and
BTS24 conflict with each
other, S-VLAN IDs are
planned for the backhaul
network for distinguishing.
Therefore, the encapsulation
type is set to 802.1Q for
UNIs.
l The encapsulation type is

set to 802.1Q for UNIs.
set to QinQ for NNIs.
Max frame length
1536

the equipment, the
Broadcast packet
suppression
Enabled
ERPS information
One ERPS ring:

l Has only one ERPS
owner node.
VLAN IDs.
Issue 01 (2016-04-30)

237

Configuration Guide

RNC2
GE
NE21 (RTN 905 2E)
7-EG61 (to BTS21)
3-ISV3-1 (to NE23)
4-ISV3-1 (to NE21)
GE
RNC1
NE21 (RTN 950A)

17-EG61 (to RNC1)
17-EG62 (to RNC2)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21
802.1ad bridge
FE
FE
R4
BTS21
NE22
CVLAN 100
802.1ad bridge
SVLAN 200
NE25
802.1ad bridge
FE
BTS23
CVLAN 110
SVLAN 200
R4
NE23
802.1ad bridge
NE23 (RTN 905 1E)

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
Issue 01 (2016-04-30)
NE24
802.1ad bridge
R4
BTS24
CVLAN 100
SVLAN 201
NE25 (RTN 905 2E)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)

238

Configuration Guide
Figure 8-25 ERPS information

3-ISV3-1 (East, RPL
neighbor port)
4-ISV3-1 (West)
Control VLAN: 4094
4-ISV3-1 (West)
Control VLAN: 4094
GE
NE21
RNC
FE
R4
BTS21
FE
R4
NE22
NE25
FE
R4
BTS23
7-EG61 (East)
3-ISV3-1 (West, RPL
neighbor port)
Control VLAN: 4094
NE24
NE23
BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
Control VLAN: 4094
3-ISV3-1 (East)
neighbor port)
Control VLAN: 4094
Procedure
Issue 01 (2016-04-30)

239

Configuration Guide
Step 2 Create 802.1ad bridge-based E-LAN services.

1.
Issue 01 (2016-04-30)

240

Configuration Guide
2.
NOTE
----End

This topic describes the procedure for configuring QoS.
Issue 01 (2016-04-30)

241

Configuration Guide
Data Preparation
Item
Planning Principle

each service port.
base on S-VLAN
priorities.
VLAN Pri.
PHB
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
VLAN Pri.
RNC
PHB
5
3
2
0
GE
NE21
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
FE
R4
BTS21
NE22
NE25
R4
BTS24
VLAN Pri.
5
3
2
0
PHB
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
NE23
FE
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
NE24
R4
BTS23
DS mapping
VLAN Pri.
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
5
3
2
0
PHB
EF
AF3
AF2
BE
VLAN Pri.
5
3
2
0
DS mapping
Procedure
planned setting.
Issue 01 (2016-04-30)

242

Configuration Guide
Issue 01 (2016-04-30)

243

Configuration Guide
NOTE
AF3.

----End

Procedure
1.
Issue 01 (2016-04-30)

244

Configuration Guide
2.
Issue 01 (2016-04-30)
Start an LB test.

245

Configuration Guide
3.
Issue 01 (2016-04-30)

246

Configuration Guide
----End

next NE.

The encapsulation type needs to be set to 802.1Q for UNIs and to QinQ for NNIs.
Issue 01 (2016-04-30)

247

Configuration Guide
Data Preparation
Item
Planning Principle
l In this example, base

station services carry CVLAN IDs. However,
because the C-VLAN
IDs of BTS21 and
BTS24 conflict with
each other, S-VLAN IDs
are planned for the
backhaul network for
distinguishing.
Therefore, the
encapsulation type is set
to 802.1Q for UNIs.

Issue 01 (2016-04-30)
Max frame length
1536

the equipment, the
Broadcast packet
suppression
Enabled

248

Configuration Guide
RNC2
GE
NE21 (RTN 905 2E)
7-EG61 (to BTS21)
3-ISV3-1 (to NE23)
4-ISV3-1 (to NE21)
GE
RNC1
NE21 (RTN 950A)

17-EG61 (to RNC1)
17-EG62 (to RNC2)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21
802.1ad bridge
FE
FE
R4
BTS21
NE22
CVLAN 100
802.1ad bridge
SVLAN 200
NE25
802.1ad bridge
FE
BTS23
CVLAN 110
SVLAN 200
R4
NE23
802.1ad bridge
NE23 (RTN 905 1E)

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
NE24
802.1ad bridge
R4
BTS24
CVLAN 100
SVLAN 201
NE25 (RTN 905 2E)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)
Procedure

Issue 01 (2016-04-30)

249

Configuration Guide


Issue 01 (2016-04-30)

250

Configuration Guide
----End
8.11.3.2 Configuring ERPS

In this example, ERPS V2 NEs are used as RPL owner nodes for configuring ring network
protection.
Data Preparation
Item
Planning Principle
ERPS information
One ERPS ring:

l Has only one ERPS
owner node.
VLAN IDs.
Issue 01 (2016-04-30)

251

Configuration Guide

3-ISV3-1 (East, RPL
neighbor port)
4-ISV3-1 (West)
Control VLAN: 4094

4-ISV3-1 (West)
Control VLAN: 4094
GE
NE21
RNC
FE
R4
BTS21
FE
R4
NE22
NE25
FE
R4
BTS23
7-EG61 (East)
3-ISV3-1 (West, RPL
neighbor port)
Control VLAN: 4094
NE24
NE23
BTS24
7-ISM6-2 (East)
7-ISM6-1 (West)
Control VLAN: 4094
3-ISV3-1 (East)
neighbor port)
Control VLAN: 4094
Procedure
Issue 01 (2016-04-30)

252

Configuration Guide
----End

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

for all IEEE 802.1ad
bridges.
In this example, base station

services carry C-VLAN IDs.
However, because the CVLAN IDs of BTS21 and
BTS24 conflict with each
other, S-VLAN IDs are
planned for the backhaul
network for distinguishing.
Therefore, the encapsulation
type is set to 802.1Q for
UNIs.

Issue 01 (2016-04-30)

253

Configuration Guide

RNC2
GE
NE21 (RTN 905 2E)
7-EG61 (to BTS21)
3-ISV3-1 (to NE23)
4-ISV3-1 (to NE21)
GE
RNC1
NE21 (RTN 950A)

17-EG61 (to RNC1)
17-EG62 (to RNC2)
3-ISV3-1 (to NE22)
4-ISV3-1 (to NE24)
NE21
802.1ad bridge
FE
FE
R4
BTS21
NE22
CVLAN 100
802.1ad bridge
SVLAN 200
NE25
802.1ad bridge
FE
BTS23
CVLAN 110
SVLAN 200
R4
NE23
802.1ad bridge
NE23 (RTN 905 1E)

7-EG61 (to NE24)
7-EG62 (to BTS23)
3-ISV3-1 (to NE22)
NE24
802.1ad bridge
R4
BTS24
CVLAN 100
SVLAN 201
NE25 (RTN 905 2E)

8-EG61 (to BTS24)
7-ISM6-1 (to NE24)
7-ISM6-2 (to NE21)
NE24 (RTN 905 1E)

7-EG61 (to NE23)
3-ISV3-1 (to NE25)
Procedure
1.
Issue 01 (2016-04-30)
Configure the basic service information and ports mounted to UNIs.

254

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

255

Configuration Guide
----End

This topic describes the procedure for configuring QoS.
Data Preparation
Item
Planning Principle

each service port.
base on S-VLAN
priorities.
Issue 01 (2016-04-30)

256

Configuration Guide

VLAN Pri.
PHB
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
VLAN Pri.
RNC
PHB
5
3
2
0
GE
NE21
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
DS mapping
FE
R4
BTS21
NE22
NE25
R4
BTS24
VLAN Pri.
5
3
2
0
PHB
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
NE23
FE
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
NE24
R4
BTS23
DS mapping
VLAN Pri.
Service type
PHB
VLAN Pri.
Voice,signalling
OM,video
R99 data
HSPA data
EF
AF3
AF2
BE
5
3
2
0
VLAN Pri.
5
3
2
0
PHB
EF
AF3
AF2
BE
VLAN Pri.
5
3
2
0
DS mapping
Procedure
planned setting.
Issue 01 (2016-04-30)

257

Configuration Guide
NOTE
AF3.

----End
Issue 01 (2016-04-30)

258

Configuration Guide

Procedure
Issue 01 (2016-04-30)

259

Configuration Guide
NOTE
l On port 17-EG6-1 of NE21, create two MPs with the IDs of 102 and 103 respectively.
Issue 01 (2016-04-30)

260

Configuration Guide
NOTE

l

----End
Issue 01 (2016-04-30)

261

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

EoPDH Boards
About This Chapter

Ethernet services based on EoS/EoPDH boards are classified into EPL services, EVPL
services, EPLAN services, and EVPLAN services.
NOTE
OptiX RTN 905/910A does not support the configuration of Ethernet services on EoS/EoPDH boards.
9.1 Basic Concepts

This section provides hyperlinks to concepts related to EoS/EoPDH-based Ethernet services.
9.2 Configuration Procedure (EPL/EVPL Services)
When configuring EPL/EVPL services, you need to configure EPL/EVPL service information
and create cross-connections between VCTRUNKs and line timeslots.
9.3 Configuration Procedure (EPLAN/EVPLAN Services)
When configuring EPLAN/EVPLAN services, you need to configure EPLAN/EVPLAN
service information and create cross-connections between VCTRUNKs and line timeslots.
9.4 Configuration Example (Ethernet Services Based on TDM Radio)
9.5 Configuration Example (Ethernet Services Traversing a TDM Network)
Issue 01 (2016-04-30)

262

Configuration Guide
9.1 Basic Concepts

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

Figure 9-1 Transmitting Ethernet services on a TDM microwave network
L2 network
TDM microwave
network
L2 network
TDM Radio link
Ethernet frame
SDH/PDH container
Scenario 2: Transmitting Native Ethernet Services from a Hybrid Microwave

Network Across a Leased TDM Network
Figure 9-2 Scenario 2: transmitting Native Ethernet services from a Hybrid microwave
network across a leased TDM network
Hybrid microwave
network
TDM network
Hybrid microwave
network
TDM link
Ethernet frame
SDH/PDH container
Issue 01 (2016-04-30)

263

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

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

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

services
Point-to-Point Transparently Transmitted

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

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

Description
Flowchart
This figure shows the flowchart for configuring EPL/EVPL services.
Issue 01 (2016-04-30)

264

Configuration Guide
Figure 9-3 Configuration Procedure (EPL/EVPL Services)

Required
Start
Optional
Configuring LAGs
Configuring Ethernet Line

Services
Configuring QoS
Verifying Ethernet Service

Configurations
End

Issue 01 (2016-04-30)
Operation
Remarks
A.10.5.1
Configuring
External
Ethernet Ports
Required.
A.10.5.2
Configuring
VCTRUNKs
on an Ethernet
Board
Required.

265

Configuration Guide
Procedure for Configuring a LAG

Table 9-2 Procedure for configuring a LAG
Operation
Description
A.10.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.10.2.2
Setting
Parameters for
LAGs
Optional.
Configuring EVPL Services

Table 9-3 Configuring EVPL services
Issue 01 (2016-04-30)
Operation
Remarks
A.10.3.1
Creating
Ethernet
Private Line
Services
Required.

266

Configuration Guide
Procedure for Configuring QoS

Table 9-4 Procedure for configuring QoS
Operation
Description
A.10.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.10.8.2
Creating the
CAR
Required if you need to perform CAR or CoS operations for a specific

flow over a port.
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.10.8.3
Creating the
CoS
A.10.8.4
Binding the
CAR/CoS
A.10.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-5 Procedure for testing Ethernet services

Operation
Description
A.10.9.1 Creating
MDs
Required for NEs where the two Ethernet ports involved in the service test are located.
Set the parameters as follows:
l Set Maintenance Domain Name and Maintenance Domain Level to the same
values for the two NEs.
l For an Ethernet service between two edge nodes on the transport network, it is
recommended that Maintenance Domain Level take the default value 4. In the
test for an Ethernet service between two internal NEs on the transport network, set
Maintenance Domain Level to a value smaller than 4. In the test for an Ethernet
service between two Ethernet ports on the same NE, set Maintenance Domain
Level to a value smaller than the value that is set in the test for an Ethernet service
between two internal NEs on the transport network.
Issue 01 (2016-04-30)

267

Configuration Guide
Operation
Description
A.10.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.10.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.
Performing an LB
test to test the
Ethernet service
configurations
Required.
The LB test result should show that the test is successful.
9.3 Configuration Procedure (EPLAN/EVPLAN Services)

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

Before configuring EPLAN/EVPLAN services, you need to learn about their service models
in this table.
Issue 01 (2016-04-30)
Service Model
References
EPLAN services based on the 802.1d bridge
802.1D Bridge-based EPLAN Services in

the Feature Description
EVPLAN services based on the 802.1q

bridge
802.1Q Bridge-based EVPLAN Services in

EVPLAN services based on the 802.1ad

bridge
802.1ad Bridge-based EVPLAN Services in


268

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

Services
Configuring QoS
Verifying Ethernet Service

Configurations
End
The operations in the configuration flowchart are described as follows.

Issue 01 (2016-04-30)
Operation
Remarks
A.10.5.1
Configuring
External
Ethernet Ports
Required.
A.10.5.2
Configuring
VCTRUNKs
on an Ethernet
Board
Required.

269

Configuration Guide
Procedure for Configuring a LAG

Table 9-7 Procedure for configuring a LAG
Operation
Description
A.10.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.10.2.2
Setting
Parameters for
LAGs
Optional.
Configuring EVPLAN Services Based on the IEEE 802.1q Bridge

Table 9-8 Configuring EVPLAN services based on the IEEE 802.1q bridge
Issue 01 (2016-04-30)
Operation
Remarks
A.10.3.2 Creating Ethernet

LAN Services
Required.
A.10.3.4 Creating the

VLAN Filtering Table
Required.

270

Configuration Guide
Operation
Managing
the MAC
address table
Remarks
A.10.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.10.4.1
Creating a
Static MAC
Address
Entry
Required if you need to enable certain MAC address entries

not to age.
A.10.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.10.3.3 Changing the

Ports Connected to a VB
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.
Procedure for Configuring QoS

Table 9-9 Procedure for configuring QoS
Operation
Description
A.10.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.10.8.2
Creating the
CAR
Required if you need to perform CAR or CoS operations for a specific

flow over a port.
A.10.8.3
Creating the
CoS
Set CAR or CoS parameters and bind the configured CARs or CoSs to
the corresponding flows according to the network plan.
A.10.8.4
Binding the
CAR/CoS
Issue 01 (2016-04-30)

271

Configuration Guide
Operation
Description
A.10.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-10 Procedure for testing Ethernet services

Operation
Description
A.10.9.1 Creating
MDs
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.10.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.10.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 01 (2016-04-30)

272

Configuration Guide
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.4 Configuration Example (Ethernet Services Based on

TDM Radio)

On a TDM microwave chain network, Ethernet services need to be configured according to
the following requirements:
l
In this example, few Ethernet services are transmitted only on BTS13 and BTS14. To
meet the service requirements, the TDM microwave network doe not need to be
upgraded and Ethernet services are transmitted in EoS mode.
The Ethernet services from BTS13 occupy a 4 Mbit/s bandwidth and the Ethernet
services from BTS14 occupy a 10 Mbit/s bandwidth.
Ethernet services from BTS13 and BTS14 carry VLAN IDs, and VLAN IDs on the
entire network are planned in a unified manner.
FE links to the BSC are configured with link aggregation group (LAG) protection.
QoS processing is not required.
Figure 9-5 Networking diagram (Ethernet services based on TDM microwave)

E1
BTS12
BTS13
4 Mbit/s
VLAN 120
STM-1
FE+E1
FE+STM-1
NE14
E1
NE13
NE12
NE11
BSC
FE+E1
E1
BTS11
NE15
NE16
BTS15
BTS14
10 Mbit/s
VLAN 130
This figure shows the board configuration of each NE.

Issue 01 (2016-04-30)

273

Configuration Guide
Figure 9-6 Board configuration

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

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

Data Preparation
Table 9-11 External Ethernet port information
Issue 01 (2016-04-30)
Item
Planning Principle
Port information
Port enabled/disabled status
Enabled
All used external ports

should be enabled.

274

Configuration Guide
Item
Planning Principle
Port working mode
Auto-negotiation
In this example, the FE ports

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

planned to the default value,
1522. Change the maximum
the requirements of the
specific base station.
Flow control
Disabled

when the NE or the peer
both ends.
Tag attributes
Tag Aware

Ethernet services carry
VLAN tags. Therefore, the
TAG attributes of all the
ports are Tag Aware.
Entry check
Enabled
Network attributes of ports
UNI
Table 9-12 VCTRUNK information
Issue 01 (2016-04-30)
Item
Planning Principle
VCTRUNK information
Tag attribute
Tag Aware
The tag attributes of

VCTRUNKs should be the
same as their external ports.

275

Configuration Guide
Item
Planning Principle
Entry check
Enabled
UNI
Mapping protocol
GFP
Use the GFP protocol to

encapsulate Ethernet
packets.
LCAS
Enabled
Bound path
NE11 (RTN 950A)

4-EMS6PORT1 (to BSC)
4-EMS6PORT2 (to BSC)
4-EMS6-VCTRUNK1 (to NE12)
VC4-4-VC12(1-5)
VC4-4-VC12(6-7)
NE14 (RTN 950A)

4-EMS6PORT1 (to BTS12)
VC4-4-VC12(1-2)
E1
BTS12
BTS13
4 Mbit/s
VLAN 120
STM-1
FE+E1
FE+STM-1
NE14
E1
NE13
NE12
NE11
BSC
FE+E1
E1
BTS11
NE15
NE16
BTS15
NE15 (RTN 950A)

1-EMS6PORT1 (to BTS14)
VC4-4-VC12(1-5)
BTS14
10 Mbit/s
VLAN 130
Procedure
Step 1 Configure external ports.
1.
Issue 01 (2016-04-30)
Set basic attributes.

276

Configuration Guide
2.
Query tag attributes and ensure that the tag attributes are the same as planned.
3.
Query network attributes and ensure that network attributes are the same as planned.
Issue 01 (2016-04-30)

277

Configuration Guide
Step 2 Configure VCTRUNKs.

1.
Query basic attributes and ensure that basic attributes are the same as planned.
2.
Query network attributes and ensure that network attributes are the same as planned.
Issue 01 (2016-04-30)

278

Configuration Guide
3.
Issue 01 (2016-04-30)
Enable LCAS.

279

Configuration Guide
4.
----End
9.4.2.2 Configuring ERPS Protection

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

bandwidth of Ethernet
services to be transmitted is
14 Mbit/s, which is much
lower than the bandwidth of
an FE port. Therefore, you
do not need to configure the
LAG to the load-sharing
mode to increase the
bandwidth.
System priority
32768
Master port
4-EMS6-PORT1
Slave port
4-EMS6-PORT2
Procedure
Step 1 Configure a LAG on NE11.
Issue 01 (2016-04-30)

280

Configuration Guide
----End
9.4.2.3 Configuring Ethernet Services

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

BSC

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

281

Configuration Guide

Parameter
Between BTS13 and the BSC
Board
4-EMS6
Service type
EPL
Direction
Bidirectional
Source port
PORT1
Source VLAN
120
Sink port
VCTRUNK1
Sink VLAN ID
120

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

282

Configuration Guide
----End
9.4.2.4 Configuring Cross-connections

In this example, cross-connections need to be created between VCTRUNKs and timeslots in
SDH microwave.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Timeslot allocation
information

283

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

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

284

Configuration Guide
----End

Procedure
Step 1 Create a maintenance domain (MD) for NE11, NE14, and NE15.
Issue 01 (2016-04-30)

285

Configuration Guide
Issue 01 (2016-04-30)

286

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


l
Perform the LB test by considering the MEP whose MP ID is 101 as the source MEP and
the MEP whose MP ID is 401 as the sink MEP.
Perform the LB test by considering the MEP whose MP ID is 102 as the source
maintenance point and the MEP whose MP ID is 201 as the sink maintenance point.
Services pass all LB tests.

----End
9.5 Configuration Example (Ethernet Services Traversing a

TDM Network)

On a Hybrid microwave network, Native Ethernet services need to traverse a leased TDM
network before arriving at a BSC.
As shown in the following figure, Ethernet services from BTSs 11 to 15 are received over
Hybrid microwave links, are aggregated on NE11, and then are transmitted to the BSC across
a leased TDM network. Configure Ethernet services according to the following requirements:
l
Issue 01 (2016-04-30)
NE11 uses an EFP8 board to receive Ethernet services from and transmit Ethernet
services to BTS16.
287

Configuration Guide
NE11 and NE17 use the EoPDH technology, wherein Ethernet services are encapsulated
into E1 services so that Ethernet services traverse the TDM network successfully.
NOTE
To facilitate description of service configurations in this example, NE17 is an IDU that supports the
EoPDH function. In addition to an IDU, NE17 can also be an MSTP device that provides the EoPDH
function.
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 from each BTS carry VLAN IDs, and VLAN IDs on the entire network are
planned in a unified manner. Therefore, VLAN-based E-Line services are configured for
service transmission in this example.
VLAN priorities have been configured for base stations based on service types. In
addition, QoS processing is required.
NOTE
In this example, service configurations only on NE11 and NE17 are described. For service configuration
details on NE12 to NE16, see 8.7 Configuration Example (VLAN-based E-Line Services).
Figure 9-7 Networking diagram (Ethernet services traversing a TDM network)

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

288

Configuration Guide
Figure 9-8 Board configuration
ISU2
NE6
ISU2
EG4P
NE cascade
NE13
FE
NE14
ISU2
CSHO
NE6
E1
BTS12 ISU2
EG4P
SP3S
CSHO
ISU2
ISU2
SP3S
GE
NE11
NE12
ISU2
CSHO
CSHO
ISU2
NE6
ISU2
NE6
ISU2
EG4P
EFP8
SP3D
SP3D
FE
E1
E1
BTS16
E1
FE
BTS11
TDM
network
E1
CSHO
NE6
ISU2
NE6
ISU2
EG4P
EG4P
SP3S
NE16
CSHO
ISU2
ISU2
SP3S
NE6
EFP8
SP3D
NE17 FE
NE15
E1
FE
CSHO
BTS15
BSC

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

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

carry VLAN IDs.
1522

the requirements of a
specific base station.

289

Configuration Guide
Item
Planning Principle
4-EFP8-PORT10
Flow control
Disabled
For EFP8, the flow control

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

carry VLAN IDs. Therefore,
the tag attributes of all the
Table 9-17 Information about the IF_ETH port (NE11)

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

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

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

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

290

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

services.
Issue 01 (2016-04-30)

291

Configuration Guide
Data Preparation
Item
Planning Principle

priorities and PHBs
each service port.
packets with VLAN
setting).
VLAN Pri.
PHB
5
3
2
0
BTS12
10 Mbit/s
VLAN 110
VLAN Pri.
EF
AF3
AF2
BE
5
3
2
0
FE
FE
FE
NE16
NE15
BTS15
10 Mbit/s
VLAN 120
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
FE
GE
NE14
NE13
VLAN Pri.
BTS16
10 Mbit/s
VLAN 150
DS mapping
NE12
TDM
network
E1
NE11
E1
FE
BTS11
10 Mbti/s
VLAN 100
NE17
BSC
VLAN Pri.
PHB
Service type
5
3
2
0
EF
AF3
AF2
BE
Voice,signalling
OM,video
R99 data
HSPA data
Procedure
planned setting.
Issue 01 (2016-04-30)

292

Configuration Guide
Issue 01 (2016-04-30)

293

Configuration Guide
NOTE
AF3.
----End
9.5.2.4 Configuring EoS/EoPDH Ethernet Ports

Ports to be configured includes ports and VCTRUNKs.
Data Preparation
Table 9-19 External Ethernet port information
Issue 01 (2016-04-30)
Item
Planning Principle
Port information
Port enabled/disabled status
Enabled
All used external ports

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

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

the requirements of a
specific BTS.
Flow control
Disabled

both ends.

294

Configuration Guide
Item
Planning Principle
Tag attribute
Tag Aware

Ethernet services carry
VLAN IDs. Therefore, the
TAG attributes of all the
Entry check
Enabled
UNI
Table 9-20 VCTRUNK information
Issue 01 (2016-04-30)
Item
Planning Principle
VCTRUNK information
Tag attribute
Tag Aware
The tag attributes for the

VCTRUNKs and their
external ports should be the
same.
Entry check
Enabled
UNI
Mapping protocol
GFP
Use the GFP protocol to

encapsulate Ethernet
packets.
LCAS
Enabled
Bound path

295

Configuration Guide

NE11 (RTN 950A)
4-EFP8-PORT1 (to BTS16)
4-EFP8-PORT9 (to VCTRUNK)
4-EFP8-VCTRUNK1 (to NE17)
VC4-1-VC12(1-10)
VC4-1-VC12(11-20)
BTS12
10 Mbit/s
VLAN 110
FE
BTS16
10 Mbit/s
VLAN 150
FE
GE
NE14
FE
NE13
FE
NE15
NE16
NE12
E1
NE11
BTS11
10 Mbti/s
VLAN 100
BTS15
10 Mbit/s
VLAN 120
TDM
network
E1
FE
NE17
BSC
NE17 (RTN 950A)

4-EFP8-PORT1 (to BSC)
VC4-1-VC12(1-10)
VC4-1-VC12(11-20)
Procedure
Step 1 Configure external ports.
In this example, you only need to enable port 4-EFP8-PORT1; the other parameters take their
default values.
Step 2 Configure internal ports.

In this example, you only need to configure channels to be bound with 4-EFP8-VCTRUNK1
and 4-EFP8-VCTRUNK2; the other parameters take their default values.
Take 4-EFP8-VCTRUNK1 as an example.
Issue 01 (2016-04-30)

296

Configuration Guide
----End
9.5.2.5 Configuring EoS/EoPDH Ethernet Protection

To increase VCTRUNK bandwidth, two VCTRUNKs can be bound to form a load-sharing
link aggregation group (LAG).
Data Preparation
Item

(NE11 and NE17)
Planning Principle
LAG type
Static aggregation
Reversion mode
Load sharing type
Load sharing
Load sharing mode
Load sharing based on IP
System priority
32768
Master port
4-EFP8-VCTRUNK1
Slave port
4-EFP8-VCTRUNK2
Procedure
Step 1 Configure a LAG.
Issue 01 (2016-04-30)

297

Configuration Guide
----End
9.5.2.6 Configuring EoS/EoPDH-based Ethernet Services

In this example, two VLAN-based VPL services need to be created.
Data Preparation
Parameter
Issue 01 (2016-04-30)
NE11
TDM Network
Between NE12 and the

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

298

Configuration Guide
Table 9-22 Information about Ethernet services (NE17)

Parameter
NE17
Between the TDM Network and the
BSC
Board
4-EFP8
Service type
EPL
Direction
Bidirectional
Source port
VCTRUNK1
Source VLAN ID
100, 110, 120, 150
Sink port
PORT1
Sink VLAN ID
100, 110, 120, 150
Procedure
Step 1 Configure Ethernet services.
Take the service between 4-EFP8-1 to VCTRUNK1 on NE11 as an example.
----End
9.5.2.7 Configuring Cross-connections

In this example, cross-connections need to be created between VCTRUNKs and E1s.
Issue 01 (2016-04-30)

299

Configuration Guide
Data Preparation
Table 9-23 Cross-connections of Ethernet services (NE11)
Parameter
Value
Service level
VC-12
Direction
Bidirectional
Source board
4-EFP8
Source port
Source VC-4
VC4-1
Source timeslot range
1-20
Sink slot
2-SP3D
Sink port
Sink VC-4
Sink timeslot range
1-20
Table 9-24 Cross-connections of Ethernet services (NE17)

Parameter
Value
Service level
VC-12
Direction
Bidirectional
Source board
4-EFP8
Source port
Source VC-4
VC4-1
Source timeslot range
1-20
Sink slot
2-SP3D
Sink port
Sink VC-4
Sink timeslot range
1-20
Procedure
Step 1 Configure cross-connections.
Take the cross-connection between 4-EFP8-1 and 2-SP3D on NE11 as an example.
Issue 01 (2016-04-30)

300

Configuration Guide
----End
9.5.2.8 Configuring QoS for EoS/EoPDH-based Ethernet Services

In this example, QoS is deployed based on VLAN priorities.
Data Preparation
Table 9-25 Flow parameters (NE11)
Parameter
Value
Flow type
PORT+VLAN
flow
PORT+VLAN
flow
PORT+VLAN
flow
PORT+VLAN
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
PORT+VLAN
flow
PORT+VLAN
flow
PORT+VLAN
flow
Table 9-26 Flow parameters (NE17)
Issue 01 (2016-04-30)
Parameter
Value
Flow type
PORT+VLAN
flow

301

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

tag

tag
Non-real-time R99 services

tag
O&M and real-time HSDPA

services

tag

tag
Real-time voice service and

signaling

302

Configuration Guide
COS Parameter
CoS Priority
Corresponding BTS
Service Type

tag

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

Take the Port+VLAN (150) flow on NE11 as an example.
Issue 01 (2016-04-30)

303

Configuration Guide
Step 3 Bind CoS.

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

Procedure
Step 1 Create a maintenance domain (MD) for NE11 and NE17.
Issue 01 (2016-04-30)

304

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

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

Issue 01 (2016-04-30)

305

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

Perform the LB test by considering the MEP whose MP ID is 201 as the source maintenance
point and the MEP whose MP ID is 401 as the sink maintenance point.
Services pass LB tests.
----End
Issue 01 (2016-04-30)

306

Configuration Guide
10
10 Configuring MPLS Tunnels
Configuring MPLS Tunnels
About This Chapter

Configuring MPLS tunnels, to be specific, static LSPs, is a prerequisite for configuring PWE3
services.
You need to configure NNIs and L2 Link before configuring MPLS Tunnel.
You need to configure NNIs before configuring MPLS Tunnel.
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection)
10.4 Configuration Example (MPLS Tunnels with No Protection)
10.5 Configuration Example (MPLS Tunnels Traversing L2 Networks)
In this example, the MPLS tunnels traverse an L2 network by using VLAN sub-interfaces.
10.6 Configuration Example (MPLS Tunnels Traversing a TDM Network)
This s example illustrates how MPLS tunnels carried by ML-PPP links traverse a TDM
network.
Issue 01 (2016-04-30)

307

Configuration Guide

You need to configure NNIs and L2 Link before configuring MPLS Tunnel.
Flowchart
Figure 10-1 Flowchart for configuring MPLS tunnels in end-to-end mode
NOTE
l For MPLS tunnels that have been configured on a per-NE basis, follow instructions in A.15.4 Searching
for MPLS Tunnels and PWE3 Services to synchronize the MPLS tunnels to the network layer of the
U2000. This enables end-to-end management of the MPLS tunnels. For MPLS APS protection groups
that have also been configured on a per-NE basis, follow instructions in A.15.5.8 Searching for MPLS
APS Protection Groups to synchronize the protection groups to the network layer of the U2000.
NOTE
l When OptiX RTN 905 transmits MPLS tunnel services through ML-PPP ports, the working modes
of the E1, channelized STM-1, and cascading ports must be set to CES.
l When OptiX RTN 950A housing an MN1 board transmits MPLS tunnel services through ML-PPP
ports, the working modes of the E1 and STM-1 ports on the MP1 and CD1 boards must be set to
CES.
For details, see A.8.2 Setting Working Modes of E1 Ports.
Issue 01 (2016-04-30)

308

Configuration Guide
Configuring MPLS Ports (Not Using VLAN Sub-interfaces)

Table 10-1 Configuring MPLS ports (not using VLAN sub-interfaces)
Operation
Remarks
A.15.5.1 Configuring Port IP

Address Resources
Required when IP addresses need to be automatically

allocated to MPLS ports during the manual creation
of a fiber/cable.
Configuring
Ethernet
ports
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
Required.
A.3.5.2 Creating
Fibers Manually
or A.3.5.1
Creating Optical
Fibers by Using
the Search
Method

allocated to MPLS ports.
A.8.8.4 Setting
Layer 3
Attributes of
Ethernet Ports
Required when IP addresses need to be manually

specified for MPLS ports.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
NOTE
If a LAG is configured to protect services on MPLS ports, set
Automatically Allocate IP Address to Yes only when
creating a fiber/cable for the main port, and set
Automatically Allocate IP Address to No when creating a
fiber/cable for the slave port.
NOTE
The IP addresses of different MPLS ports on an NE must be
in different network segments, but the IP addresses of the
ports at both ends of an MPLS tunnel must be in the same
network segment.
If a LAG needs to be used to protect services on MPLS ports,
set Enable Tunnel on the main port to Enable, and retain the
default value Disabled for Enable Tunnel on the slave port.
set Specify IP Address to Manual Specify for the main port,
and set Specify IP Address to Unspecified for the slave port.
l To enable the function of triggering switching by

bit errors, set Enable Switching Triggered by Bit
Error to Enabled and set Switching Mode
Triggered by Bit Error (SF by default) according
to the plan.
l To enable the bit error detection function, set
Enable Bit Error Detection to Enabled and set
EXC Threshold for Packet Loss at Port and SD
Threshold for Packet Loss at Port according to
the plan.
Configuring
IF_ETH
portsa
Issue 01 (2016-04-30)
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required.

309

Configuration Guide
Operation
Remarks
A.3.5.2 Creating
Fibers Manually
or A.3.5.1
Creating Optical
Fibers by Using
the Search
Method

allocated to MPLS ports.
A.8.9.3 Setting
Layer 3
Attributes of
IF_ETH Ports
Required.
A.8.9.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Optional.
NOTE
If a LAG is configured to protect services on MPLS ports, set
Automatically Allocate IP Address to Yes only when
creating a fiber/cable for the main port, and set
Automatically Allocate IP Address to No when creating a
fiber/cable for the slave port. The protection configuration
method for other microwave links is the same.
NOTE
network segment.
NOTE
a:
l For an OptiX RTN 905 2E-provided microwave link for which 1+1 protection or link aggregation
group (LAG) is configured, set parameters only for the main IF_ETH port. The following operations
described in this section are also applicable only to the main port.
l For OptiX RTN 905 1Es that are stacked to implement physical link aggregation/ (PLA), Enhanced
physical link aggregation(EPLA), 1+1 hot standby (HSB), 1+1 frequency diversity (FD), or 1+1
space diversity (SD), set parameters only for IF_ETH ports on main NEs. The following operations
described in this section are also applicable only to main NEs.
Configuring MPLS Ports (Using VLAN Sub-interfaces)

Table 10-2 Configuring MPLS ports (using VLAN sub-interfaces)
Operation
Setting
attributes of
Ethernet
ports
Issue 01 (2016-04-30)
Remarks
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
Required.

310

Configuration Guide
Operation
Remarks
A.8.8.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.
A.8.12 Creating
VLAN SubInterfaces
Required.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
NOTE
network segment.

to the plan.
the plan.
Setting
attributes of
IF_ETH
portsa
Issue 01 (2016-04-30)
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required.
A.8.12 Creating
VLAN SubInterfaces
Required.
NOTE
network segment.

311

Configuration Guide
NOTE
a:
Configuring ML-PPP (Smart E1s Being MP Group Members)

Table 10-3 Configuring ML-PPP (smart E1s being MP group members)
Remarks
Operation
Setting
attributes of
Smart E1
ports
A.8.6.1
Setting
Basic
Attributes
of Smart E1
Ports
Required.
A.8.6.2
Setting
Advanced
Attributes
of Smart E1
Ports
Optional. Set the parameters as follows:
A.11.11.1 Creating MP
Groups
Set Frame Format and Frame Mode according to the

service plan. Ensure that the same frame mode is used at
both ends.
Normally, the CRC-4 multi-frame format and the PCM31
frame mode are used.
Required.
Configuring ML-PPP (E1s in Channelized STM-1s Being MP Group Members)

Table 10-4 Configuring ML-PPP (E1s in channelized STM-1s being MP group members)
Operation
Remarks
A.8.5 Changing the E1

Frame Format and Frame
Mode for a Channelized
STM-1

both ends.
Creating and
configuring
serial ports
Issue 01 (2016-04-30)
A.8.7.1
Creating
Serial Ports
Required.

312

Configuration Guide
Operation
Remarks
A.8.7.2
Setting
Basic
Attributes
of Serial
Ports
Groups
Required.
Required.

Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
Creating MPLS Tunnels

Table 10-6 Creating MPLS tunnels
Issue 01 (2016-04-30)
Operation
Remarks
A.11.2.1 Setting
Basic MPLS
Attributes
Required.
Global OAM
Parameters
Required when MPLS-TP OAM needs to be configured for an

MPLS tunnel.
A.11.1.1 Creating
ARP Static Entries
Required when the dynamic ARP protocol cannot obtain the nexthop MAC address (for example, when packets traverse a Layer 2
network).

313

Configuration Guide
Operation
Remarks
Searching for Layer

2 Links
If the NEs at both ends of an MPLS tunnel can be managed on the

U2000, a Layer 2 link needs to be created for the MPLS tunnel.
Then, the automatic route computation function can be used to
create the MPLS tunnel.
You can create Ethernet fibers/cables when searching for Layer 2
links.
A.15.5.3 Creating
Non-Protection
MPLS Tunnels (in
an End-to-End
Mode) or A.15.5.4
Creating MPLS
Tunnels Configured
with MPLS APS
Protection in an
End-to-End Mode
Required.
A.11.2.7 Changing
MPLS Tunnel
Information
Perform this operation to set a VLAN ID for related MPLS nodes

if packets on a segment of an MPLS tunnel need to traverse a
Layer 2 network.
Configuring QoS
Verifying MPLS Tunnels

Table 10-7 Verifying MPLS tunnels
Operation
Remarks
A.15.5.5 Verifying
MPLS Tunnels in an
End-to-End Mode
Required. It is recommended that you perform an LSP ping test to

verify the connectivity of an MPLS tunnel.

You need to configure NNIs before configuring MPLS Tunnel.
Issue 01 (2016-04-30)

314

Configuration Guide
Figure 10-2 Flowchart on a per-NE basis (MPLS tunnels)

Ethernet Port or Microwave
Port Being the MPLS Port
MLPPP Being the

MPLS Port
Start
Set MPLS port attributes (not

using VLAN sub-interfaces)
Required
Optional
Start
Set MPLS port attributes

(using VLAN sub-interfaces)
Configure ML PPP (Smart

E1s being MP group
members)
Configure ML PPP (E1s in

channelized STM-1s being
MP group members)
Create LAG for

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

MPLS ports
Set the QoS policy for

MPLS ports
Verify configured
MPLS tunnels
End
Verify configured
MPLS tunnels
End
NOTE
l When OptiX RTN 905 transmits MPLS tunnel services through ML-PPP ports, the working modes
of the E1, channelized STM-1, and cascading ports must be set to CES.
l When OptiX RTN 950A housing an MN1 board transmits MPLS tunnel services through ML-PPP
ports, the working modes of the E1 and STM-1 ports on the MP1 and CD1 boards must be set to
CES.
For details, see A.8.2 Setting Working Modes of E1 Ports.

Table 10-8 Setting attributes of MPLS ports (not using VLAN sub-interfaces)
Operation
Setting
attributes of
Ethernet
ports
Issue 01 (2016-04-30)
Remarks
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
Required.
A.8.8.2
Configuring the
Traffic Control
of Ethernet Ports

connected.

315

Configuration Guide
Operation
Remarks
A.8.8.4 Setting
Layer 3
Attributes of
Ethernet Ports
Required.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
NOTE
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.

to the plan.
the plan.
Setting
attributes of
IF_ETH
portsa
Issue 01 (2016-04-30)
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required.
A.8.9.3 Setting
Layer 3
Attributes of
IF_ETH Ports
Required.
A.8.9.4 Setting
the Advanced
Attributes of
IF_ETH Ports
Optional.
NOTE
network segment.

316

Configuration Guide
NOTE
a:
Configuring MPLS Ports (Using VLAN Sub-interfaces)

Table 10-9 Configuring MPLS ports (using VLAN sub-interfaces)
Remarks
Operation
Setting
attributes of
Ethernet
ports
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
Required.
A.8.8.2
Configuring the
Traffic Control
of Ethernet Ports

connected.
A.8.12 Creating
VLAN SubInterfaces
Required.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports
Optional.
NOTE
network segment.

to the plan.
the plan.
Setting
attributes of
Issue 01 (2016-04-30)
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required.

317

Configuration Guide
Operation
IF_ETH
portsa
Remarks
A.8.12 Creating
VLAN SubInterfaces
Required.
NOTE
network segment.
NOTE
a:
Configuring ML-PPP (Smart E1s Being MP Group Members)

Table 10-10 Configuring ML-PPP (smart E1s being MP group members)
Operation
Setting
attributes of
Smart E1
ports
Remarks
A.8.6.1
Setting
Basic
Attributes
of Smart E1
Ports
Required.
A.8.6.2
Setting
Advanced
Attributes
of Smart E1
Ports
Groups
Issue 01 (2016-04-30)

both ends.
Required.

318

Configuration Guide
Configuring ML-PPP (E1s in Channelized STM-1s Being MP Group Members)

Table 10-11 Configuring ML-PPP (E1s in channelized STM-1s being MP group members)
Operation
Remarks
A.8.5 Changing the E1

Frame Format and Frame
Mode for a Channelized
STM-1

both ends.
Creating and
configuring
serial ports
A.8.7.1
Creating
Serial Ports
Required.
A.8.7.2
Setting
Basic
Attributes
of Serial
Ports
Required.
Groups
Required.

Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
Issue 01 (2016-04-30)

319

Configuration Guide
Configuring MPLS Tunnels

Table 10-13 Configuring MPLS tunnels
Operation
Remarks
A.11.2.1 Setting Basic MPLS

Attributes
Required.
Configuring
MPLS
tunnels
A.11.2.4
Creating a
Unidirectional
MPLS Tunnel
Required if you need to configure a unidirectional

MPLS tunnel.
A.11.2.5
Creating a
Bidirectional
MPLS Tunnel
Required if you need to configure a bidirectional

MPLS tunnel.
A.11.1.1 Creating ARP Static

Entries
Required when the dynamic ARP protocol cannot

obtain the next-hop MAC address (for example, when
packets traverse a Layer 2 network).
Configuring MPLS Protection (Y.1711-based MPLS OAM)

NOTE
Perform the following operations only on ingress and egress nodes, but not on transit nodes.
OptiX RTN 910A does not support Y.1711-compliant MPLS OAM.
Table 10-14 Configuring MPLS protection (Y.1711-based MPLS OAM)

Operation
Configuring
Y.1711based MPLS
OAM
Remarks
A.11.2.3
Changing the
MPLS
Tunnel/PW
OAM Standard
Required if the tunnel OAM standard is not the default

value Y.1711.
A.11.2.9 Setting
MPLS OAM (Y.
1711)
Parameters
Required.
A.11.3.1 Creating an MPLS

APS Protection Group
Issue 01 (2016-04-30)
NOTE
The configuration on the ingress and egress nodes of a
unidirectional tunnel is similar to that of a bidirectional
tunnel. The difference is that you need to select the
corresponding reverse tunnel for configuration on the ingress
and egress nodes of a unidirectional tunnel.
Required when you need to configure protection for

services carried on an MPLS tunnel.

320

Configuration Guide
Configuring MPLS Protection (MPLS-TP OAM)

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

Operation
Configuring
MPLS-TP
OAM
Remarks
A.11.2.2
Configuring
Global OAM
Parameters
Required.
A.11.2.3
Changing the
MPLS
Tunnel/PW
OAM Standard
Required.
A.11.2.16
Configuring
MEP
Parameters for
MPLS-TP
Tunnel OAM
Required for ingress/egress nodes of bidirectional

tunnels.

NOTE
The configuration on the ingress and egress nodes of a
unidirectional tunnel is similar to that of a bidirectional
tunnel. The difference is that you need to select the
corresponding reverse tunnel for configuration on the ingress
and egress nodes of a unidirectional tunnel.
Required when you need to configure protection for

services carried on an MPLS tunnel.
Configuring QoS
Verifying MPLS Tunnels

NOTE
There are many methods to verify MPLS tunnels, for example, by enabling Y.1711-based MPLS OAM,
MPLS-TP OAM, or LSP ping/traceroute. In this process, the first method is used. This method is
applicable when MPLS OAM has not been configured. If one type of MPLS OAM has been configured
for a tunnel, you can directly query the LSP running status.
Table 10-16 Verifying MPLS tunnels
Issue 01 (2016-04-30)
Operation
Remarks
A.11.2.9 Setting MPLS OAM

(Y.1711) Parameters
Required when you need to enable the MPLS OAM

function to detect the tunnel status before creating an
MPLS APS protection group.
A.11.2.12 Querying LSP

Running Status
Required.

321

Configuration Guide
10.3 Configuration Example (MPLS Tunnels with MPLS

APS Protection)

All base station services need to be transmitted through a PSN to the BSC and RNC. Based on
6.5 Configuration Example (Microwave Links on a Packet Network), configure MPLS
tunnels on the packet ring according to the following actual requirements:
l
Bidirectional MPLS tunnels are configured between NE31 and NE11, between NE31
and NE21, and between NE31 and NE32.
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-3.
Figure 10-3 Networking diagram (packet ring network)

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

Issue 01 (2016-04-30)

322

Configuration Guide
10.3.2.1 Configuring MPLS Port

This section describes the procedure for configuring NNI information when IP addresses are
automatically allocated by the U2000.
Data Preparation
l
IP address resources: allocated to ports at both ends of manually created fibers/cables
Ethernet port attributes: Working Mode, Max Frame Length (bytes), Enable Bit
Error Detection and Enable Switching Triggered by Bit Error.
Procedure
Step 1 Configure port IP address resources.
Configuring port IP address resources is a prerequisite for automatically allocating IP
addresses to MPLS ports.
l
Because IP addresses cannot be automatically allocated to some MPLS ports, the

configured IP address resources must not include the IP address resources that have been
allocated to these ports.
If the IP address resources to be configured are inconsecutive, you can configure

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

network segments to which LSR IDs and NE IP addresses belong.
This table provides parameter values for configuring port IP address resources.
Name
Start IP Address
End IP Address
ETH_PORT_IP
46.1.64.0
46.1.64.30
Figure 10-4 Configuring port IP address resources
Issue 01 (2016-04-30)

323

Configuration Guide
Step 2 Manually create fibers/cables.

Create fibers/cables between NEs according to the networking diagram. After a fiber/cable is
created, the U2000 allocates an unused network segment with the length of 30 bits to the
MPLS tunnel from IP Address Resources. That is, two IP addresses in the network segment,
other than the network IP address and the broadcast address, are allocated to the ports at both
ends of the MPLS tunnel.
Figure 10-5 Manually creating fibers/cables
NOTE
After fibers/cables are created, query port attributes. Port Mode is Layer 3, Enable Tunnel is Enabled, and
IP Address is the allocated network segment with the length of 30 bits.
Step 3 Set attributes of Ethernet ports.

Set basic attributes and Layer 3 attributes for Ethernet ports between NEs. The Ethernet port
that NE31 uses to connect to NE21 is used as an example.
Issue 01 (2016-04-30)

324

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

MPLS APS is configured during MPLS tunnel configuration.
Issue 01 (2016-04-30)

325

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

Note the following points:
l
Set Carrier ID according to the network plan if ICC-based MPLS-TP OAM is used. Set
Carrier ID to the same value for all NEs on a network.
Set Channel Type to the same value for all NEs on a network. It is recommended that
you retain the default value for this parameter.
Issue 01 (2016-04-30)

326

Configuration Guide
Step 3 Search for and create Layer 2 links.

After Layer 2 links are created, the NMS can automatically calculate tunnels. When the NMS
searches for the links, L2 Links between NEs are also searched out.
NOTE
After Layer 2 links are searched out, you do not need to create fibers/cables.
Step 4 Create end-to-end MPLS tunnels with MPLS APS protection between NE31 and NE11.
Issue 01 (2016-04-30)

327

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

attributes.
NE( 11)
Select AutoCalculate route.
NE(31)
NE(32)
NE(11)
2.
Issue 01 (2016-04-30)
NE( 21)
3
NE(31)
NE(32)
2-EG4-2(Port-2)
NE(11)
2-EG4-2(Port-2)
1501
1501 1511
1511
1-EG4-1(Port-1)
2-EG4-1(Port-1)
Create the working tunnel.

328

Configuration Guide
NE32
NE11
Select source:
Double-click the
source node.
NE31
5
Select sink: Doubleclick the sink node.NE21
The interfaces are displayed.

Configure labels.
NE(31
)
NE(32
)
NE(11
)
Node information is
displayed.
NE(31
)
NE(32
2-EG4-2(Port-2)
)
NE(11
)
2-EG4-2(Port-2)
3.
1501
1-EG4-1(Port-1)
1501 1511
1511
2-EG41(Port-1)
Or click AutoAssign Label.
Create the protection tunnel.
NE( 31)
NE( 32)
NE( 11)
NE( 21)
Choose Protection Tunnel to

configure the protection tunnel in
the same way as the working
tunnel.
10
The protection node
information is displayed.
11
NE(31)
NE(32)
NE(11)
NE(31)
4.
NE(32)
2-EG4-2(Port-2)
NE(11)
2-EG4-2(Port-2)
1501
1511
1501
1-EG4-1(Port-1)
1511
2-EG4-1(Port-1)
Configure constraints for the tunnels. If the tunnels that are automatically calculated are
not the planned tunnels, you can configure constraints for them manually.
NE31
2-EG4-2(Port-2)
Right-click the explicit
node to display the
shortcut menu.
12
NE11
Issue 01 (2016-04-30)
2-EG4-1(Port-1)
NE21

46.1.64.2
46.1.64.5
Select the explicit port.
13
14
329

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

330

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

Working Tunnel
Protection Tunnel
331

Configuration Guide
Transmit
Transmit
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1712
Outgoing Lable:1712
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1702
Outgoing Lable:1702
Transmit
Ingress
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1712
Outgoing Lable:1712
Board:1-EG4-1
IP: 46.1.64.1
Incoming Lable:1702
Outgoing Lable:1702
NE32
NE31
Transmit
Ingress
NE11
Board:2-EG4-1
IP: 46.1.64.9
Incoming Lable:1722
Outgoing Lable:1722
Board:1-EG4-2
IP: 46.1.64.14
Incoming Lable:1701
Outgoing Lable:1701
NE21
Egress
Board:1-EG4-2
IP: 46.1.64.10
Incoming Lable:1722
Outgoing Lable:1722
Egress
Board:1-EG4-1
IP: 46.1.64.13
Incoming Lable:1701
Outgoing Lable:1701
Working Tunnel
Protection Tunnel
Configure the two protection groups according to the configuration of the protection group
between NE31 and NE11.
----End

This section describes the procedure for deploying a DiffServ domain for NNIs based on
MPLS EXP values.
Data Preparation
Traffic carried on tunnels need to be classified based on the MPLS EXP field in packets. In
this example, the mapping in the default DiffServ domain is used for simple traffic
classification.
l
Mapping in the default DiffServ domain

Table 10-17 Mapping between PHBs and MPLS EXP values
Issue 01 (2016-04-30)
PHB
MPLS EXP Value
Service Category
CS7
CS6
EF
Real-time voice service

and signaling service
AF4

332

Configuration Guide
PHB
MPLS EXP Value
Service Category
AF3
O&M and real-time

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

This section describes the procedure for performing LSP ping tests to verify the connectivity
of MPLS tunnels.
Issue 01 (2016-04-30)

333

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

next NE.
Issue 01 (2016-04-30)

334

Configuration Guide

IP addresses of NNIs must be manually planned and configured.
Data Preparation
Figure 10-13 Planning port IP addresses
Board:2-EG4-2
IP: 46.1.64.2/30
Board:2-EG4-1
IP: 46.1.64.5/30
Board:2-EG4-2
IP: 46.1.64.6/30
Board:1-EG4-1
IP: 46.1.64.1/30
NE32
NE31
NE11
NE21
Board:1-EG4-2
IP: 46.1.64.14/30
Board:2-EG4-1
IP: 46.1.64.9/30
Board:1-EG4-2
IP: 46.1.64.10/30
Board:1-EG4-1
IP: 46.1.64.13/30
Procedure
Step 1 Set attributes of Ethernet ports.
Set basic attributes and Layer 3 attributes for Ethernet ports between NEs. The Ethernet port
that NE31 uses to connect to NE21 is used as an example.
Issue 01 (2016-04-30)

335

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

Labels of MPLS tunnels must be manually planned and configured.
Issue 01 (2016-04-30)

336

Configuration Guide
Data Preparation
l
MPLS tunnels with MPLS APS protection: source and sink board, explicit boards, and
ingress and egress labels
Procedure
LSR ID: 130.0.0.2
NE32
NE31
LSR ID: 130.0.0.3
NE11
LSR ID: 130.0.0.1
NE21
LSR ID: 130.0.0.4
Step 2 Create bidirectional MPLS tunnels (working and protection tunnels in the APS protection
group between NE31 and NE11).
Issue 01 (2016-04-30)

337

Configuration Guide

Transmit
Transmit
Board:2-EG4-1
IP: 46.1.64.5
Incoming Lable:1511
Outgoing Lable:1511
Board:2-EG4-2
IP: 46.1.64.2
Incoming Lable:1501
Outgoing Lable:1501
Egress
Ingress
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1511
Outgoing Lable:1511
Board:1-EG4-1
IP: 46.1.64.1
Incoming Lable:1501
Outgoing Lable:1501
NE32
NE31
Egress
NE11
Ingress
Board:2-EG4-1
IP: 46.1.64.9
IncomingLable:1512
Outgoing Lable:1512
Transmit
Board:1-EG4-2
IP: 46.1.64.10
Incoming Lable:1512
Outgoing Lable:1512
Board:1-EG4-2
IP: 46.1.64.14
Incoming Lable:1502
Outgoing Lable:1502
NE21
Transmit
Board:1-EG4-1
IP: 46.1.64.13
Incoming Lable:1502
Outgoing Lable:1502
Working Tunnel
Protection Tunnel
NE31 is the first node.

Figure 10-16 Configuring a working tunnel between NE31 and NE11
3
1-EG4
1(Port-1)
Issue 01 (2016-04-30)

338

Configuration Guide
NE32 is the transit node on the working tunnel.

Figure 10-17 Configuring a pass-through working tunnel on NE32
3
2-EG4
2(Port-2)
2-EG4
1(Port-1)
Issue 01 (2016-04-30)
NE11 is the last node.

339

Configuration Guide
Figure 10-18 Configuring a working tunnel on NE11

3
1511
2-EG4
1511
1511
NE21 is the transit node of the protection tunnel.

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

340

Configuration Guide
Egress
Egress
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1601
Outgoing Lable:1601
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1622
Outgoing Lable:1622
Ingress
Transmit
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1622
Outgoing Lable:1622
Board:1-EG4-1
IP: 46.1.64.1
Incoming Lable:1601
Outgoing Lable:1601
NE32
NE31
Transmit
NE11
Board:2-EG4-1
IP: 46.1.64.9
Incoming Lable:1612
Outgoing Lable:1612
Board:1-EG4-2
IP: 46.1.64.14
Incoming Lable:1602
Outgoing Lable:1602
NE21
Transmit
Ingress
Transmit
Board:1-EG4-2
IP: 46.1.64.10
Incoming Lable:1612
Outgoing Lable:1612
Board:1-EG4-1
IP: 46.1.64.13
Incoming Lable:1602
Outgoing Lable:1602
Working Tunnel
Protection Tunnel
Transmit
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1712
Outgoing Lable:1712
Transmit
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1702
Outgoing Lable:1702
Transmit
Ingress
Board:2-EG4-2
IP: 46.1.64.6
Incoming Lable:1712
Outgoing Lable:1712
Board:1-EG4-1
IP: 46.1.64.1
Incoming Lable:1702
Outgoing Lable:1702
NE32
NE31
Transmit
Ingress
NE11
Board:2-EG4-1
IP: 46.1.64.9
Incoming Lable:1722
Outgoing Lable:1722
Board:1-EG4-2
IP: 46.1.64.14
Incoming Lable:1701
Outgoing Lable:1701
NE21
Egress
Board:1-EG4-2
IP: 46.1.64.10
Incoming Lable:1722
Outgoing Lable:1722
Egress
Board:1-EG4-1
IP: 46.1.64.13
Incoming Lable:1701
Outgoing Lable:1701
Working Tunnel
Protection Tunnel
Configure tunnels in the two protection groups according to the configuration of tunnels in the
protection group between NE31 and NE11.
----End
Issue 01 (2016-04-30)

341

Configuration Guide
10.3.3.3 MPLS APS

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

Note the following points:
l
Set Carrier ID according to the network plan if ICC-based MPLS-TP OAM is used. Set
Carrier ID to the same value for all NEs on a network.
Set Channel Type to the same value for all NEs on a network. It is recommended that
you retain the default value for this parameter.
Issue 01 (2016-04-30)

342

Configuration Guide
Step 3 Configure MEP parameters for MPLS-TP tunnel OAM.

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

343

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

344

Configuration Guide
Figure 10-24 Enabling the MPLS APS protection protocol
----End

This section describes the procedure for deploying a DiffServ domain for NNIs based on
MPLS EXP values.
Data Preparation
classification.
l

Issue 01 (2016-04-30)
PHB
MPLS EXP Value
Service Category
CS7
CS6
EF

AF4
AF3
O&M and real-time

HSDPA services
AF2
Non-real-time R99
services
AF1

345

Configuration Guide
PHB
MPLS EXP Value
Service Category
BE
HSDPA data services
Tunnel NNIs to which the mapping will be applied
Procedure
classification.
Each NE uses mapping in the default DiffServ domain. The packet type for traffic
4
2
----End
10.3.3.5 Configuration Procedure (Verifying Configured MPLS Tunnels)

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

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

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

Protection)

All base station services need to be transmitted through a packet network to a BSC and an
RNC. Based on 6.5 Configuration Example (Microwave Links on a Packet Network),
configure MPLS tunnels on packet microwave links according to the following requirements:
l
Issue 01 (2016-04-30)
Bidirectional MPLS tunnels need to be configured between NE32 and NE33 and
347

Configuration Guide
Figure 10-27 shows information about NNIs used on the packet microwave links.
Figure 10-27 Networking diagram (packet microwave links)

RTN 950
3-ISV3-1(to NE34)
4-ISV3-1(to NE32)
RTN 905
NE34
NE33
RTN 980
3-ISV3-1(to NE33)
3-ISV3-1(to NE33)
GE
GE
NE32
NE31
NE11
GE
NE21
GE


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

configured IP address resources must not include the IP address resources that have been
allocated to these ports.
348

Configuration Guide
If the IP address resources to be configured are inconsecutive, you can configure

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

network segments to which LSR IDs and NE IP addresses belong.
This table provides parameter values for configuring port IP address resources.
Name
Start IP Address
End IP Address
ETH_PORT_IP
46.1.64.0
46.1.64.30
Figure 10-28 Configuring port IP address resources
Step 2 Manually create fibers/cables.

Create fibers/cables between NEs according to the networking diagram. After a fiber/cable is
created, the U2000 allocates an unused network segment with the length of 30 bits to the
MPLS tunnel from IP Address Resources. That is, two IP addresses in the network segment,
other than the network IP address and the broadcast address, are allocated to the ports at both
ends of the MPLS tunnel.
Issue 01 (2016-04-30)

349

Configuration Guide
Figure 10-29 Manually creating a microwave fiber/cable between NE32 and NE33
NOTE
After fibers/cables are created, query port attributes. Port Mode is Layer 3, Enable Tunnel is Enabled, and
IP Address is the allocated network segment with the length of 30 bits.
Step 3 Set microwave port attributes.

Basic attributes and Layer 3 attributes need to be configured for microwave ports between
NEs. A microwave port is taken as an example in the following figure.
Issue 01 (2016-04-30)

350

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

Labels of MPLS tunnels are automatically allocated by the U2000.
Data Preparation
l
End-to-end MPLS tunnel: source and sink boards and explicit boards
Procedure
Issue 01 (2016-04-30)

351

Configuration Guide
LSR ID: 130.0.0.6
NE34
LSR ID: 130.0.0.5
NE33
LSR ID: 130.0.0.2
NE32
NE31
NE11
NE21
Figure 10-32 Setting the basic attributes of MPLS

searches for Layer 2 links, fibers/cables between NEs are also searched out. Then, create
Layer 2 links on the NMS.
Issue 01 (2016-04-30)

352

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

Figure 10-34 Planning the tunnel between NE32 and NE33
NE34
NE32
NE33
Board:4-ISV3-1
IP: 46.1.64.18/30
Incoming Lable:1801
Outgoing Lable:1801
Board:3-ISV3-1
IP: 46.1.64.17/30
Incoming Lable:1801
Outgoing Lable:1801
Tunnel
1.
Issue 01 (2016-04-30)
Create a tunnel between NE32 and NE33.

353

Configuration Guide
Set the basic

attributes.
4
Double-click an
NE to set it as
the source NE.
The calculation result is displayed. You

can manually adjust the explicit board
and configure labels.
Select Auto-Calculate route.

NE(32)
130.0.0.3
NE(33)
130.0.0.5
NE33
NE32
Double-click an
NE to set it as the
sink NE.
NE(32)
NE(33)
2.
Labels can also be

automatically assigned.
Configure constraints for the tunnels. If the tunnels that are automatically calculated are
not the planned tunnels, you can configure constraints for them manually.
NE31
2-EM6F-2(Port-2)
node to display the
8
shortcut menu.
NE11
2-EM6F-1(Port-1)
46.1.64.2
46.1.64.
5
9
10
NE21
Step 4 Create an end-to-end MPLS tunnel between NE32 and NE34.

NE34
NE32
NE33
Board:3-ISV3-1
IP: 46.1.64.22/30
Incoming Lable:1902
Outgoing Lable:1902
Board:3-ISV3-1
IP: 46.1.64.21/30
Incoming Lable:1902
Outgoing Lable:1902
Board:4-ISV3-1
IP: 46.1.64.18/30
Incoming Lable:1901
Outgoing Lable:1901
Board:3-ISV3-1
IP: 46.1.64.17/30
Incoming Lable:1901
Outgoing Lable:1901
Tunnel
Issue 01 (2016-04-30)

354

Configuration Guide
The configuration method is the same as that for the tunnel between NE32 and NE33.
----End

This section describes the procedure for configuring QoS information for MPLS ports.
Data Preparation
classification.
l
Mapping in the default DiffServ domain:

PHB
MPLS EXP Value
Service Category
CS7
CS6
EF
Real-time voice services

and signaling services
AF4
AF3
OM and real-time HSDPA

services
AF2
R99 non-real-time services
AF1
BE
HSDPA data services
NNI: microwave port
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target NNIs to implement and simple
traffic classification.
Each NE uses the mapping in the default DiffServ domain. The packet type for traffic
Issue 01 (2016-04-30)

355

Configuration Guide
----End

of MPLS tunnels.
Procedure
MPLS tunnels.
Issue 01 (2016-04-30)

356

Configuration Guide
4
6
NOTE
----End
10.4.3 Procedure of Configuration on a Per-NE Basis

next NE.

IP addresses of NNIs must be manually planned and configured.
Issue 01 (2016-04-30)

357

Configuration Guide
Data Preparation
Figure 10-38 Planning IP addresses for microwave ports
NE34
NE32
NE33
Board: 3-ISV3-1
IP: 46.1.64.22/30
Board: 3-ISV3-1
IP: 46.1.64.21/30
Board: 4-ISV3-1
IP: 46.1.64.18/30
Board: 3-ISV3-1
IP: 46.1.64.17/30
Procedure
Issue 01 (2016-04-30)

358

Configuration Guide
----End

The label of MPLS Tunnel must be manually planned and configured.
Data Preparation
l
MPLS tunnel: source and sink boards, explicit boards, and ingress and egress labels
Procedure
LSR ID: 130.0.0.6
NE34
LSR ID: 130.0.0.5
NE33
LSR ID: 130.0.0.2
NE32
NE31
NE11
NE21
Issue 01 (2016-04-30)

359

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

NE34
NE32
NE33
Board:3-ISV3-1
IP: 46.1.64.22/30
Incoming Lable:1902
Outgoing Lable:1902
Board:3-ISV3-1
IP: 46.1.64.21/30
Incoming Lable:1902
Outgoing Lable:1902
Board:4-ISV3-1
IP: 46.1.64.18/30
Incoming Lable:1901
Outgoing Lable:1901
Board:3-ISV3-1
IP: 46.1.64.17/30
Incoming Lable:1901
Outgoing Lable:1901
Tunnel
Issue 01 (2016-04-30)

360

Configuration Guide
3
1901
3-ISV3
1(RTNIF-1)
1901
1901
1
46.1.64.18
Issue 01 (2016-04-30)
NE33 is the transit node of the working tunnel.

361

Configuration Guide
3
1901
4-ISV3
1(RTNIF-1)
1901
1901
3-ISV3
1(RTNIF-1)
1902
1902
46.1.64.22
46.1.64.17
130.0.0.6
130.0.0.2
Issue 01 (2016-04-30)

362

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

NE34
NE32
NE33
Board:4-ISV3-1
IP: 46.1.64.18/30
Incoming Lable:1801
Outgoing Lable:1801
Board:3-ISV3-1
IP: 46.1.64.17/30
Incoming Lable:1801
Outgoing Lable:1801
Tunnel
The configuration method is the same as that for the bidirectional MPLS tunnel between
NE32 and NE34.
----End
Issue 01 (2016-04-30)

363

Configuration Guide

Data Preparation
classification.
l

PHB
MPLS EXP Value
Service Category
CS7
CS6
EF

AF4
AF3
OM and real-time HSDPA

services
AF2
AF1
BE
HSDPA data services
NNI: microwave port
Procedure
Issue 01 (2016-04-30)

364

Configuration Guide
----End

This section describes how to verify MPLS tunnels by using MPLS ping tests.
Procedure
Step 1 Perform MPLS Ping tests to verify the connectivity of MPLS tunnels.
Initiate a ping test on the first node of a tunnel.
Issue 01 (2016-04-30)

365

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

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

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

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

366

Configuration Guide
Figure 10-46 Networking diagram (MPLS tunnels traversing a Layer 2 network)
L2 network
BTS1
VLAN=4060
BSC
NE1
VL
A
NE2
N=
40
NE3
90
NE4
MPLS Tunnel 1
NE5
BTS2
MPLS Tunnel 2
Figure 10-47 shows information about the MPLS ports on the network. The VLAN sub-ports
of ports for carrying the MPLS tunnels on NE1, NE2, and NE4 are enabled so that the MPLS
tunnels can traverse the Layer 2 network.
Issue 01 (2016-04-30)

367

Configuration Guide
Figure 10-47 Networking diagram (MPLS port information)

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

4-EM6T-1 (to NE1)
MPLS Tunnel 1
MPLS Tunnel 2
Enable VLAN sub-interface
Disable VLAN sub-interface
Equipment type

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

VLAN sub-ports need to be created for Ethernet ports connected to a Layer 2 network.
Issue 01 (2016-04-30)

368

Configuration Guide
Data Preparation
Figure 10-48 Data plan for microwave ports and Ethernet sub-ports
Board: 3-EM6T-1
Virtual Interface: 1
IP:46.1.64.6/30
VLAN: 4060
Board: 4-EM6T-1
Board: 3-ISU2-1
IP:46.1.64.5/30
IP:46.1.64.2/30
VLAN: 4060
Board: 3-ISU2-1
IP:46.1.64.1/30
L2 network
VLAN=4060
NE1
VL
AN
Board: 3-EM6T-1
IP:46.1.64.9/30
VLAN: 4090
NE2
=4
0
NE3
90
NE4
Board: 4-EM6T-1
IP:46.1.64.10/30 Board: 3-ISU2-1
VLAN: 4090
IP:46.1.64.13/30
NE5
Board: 3-ISU2-1
IP:46.1.64.14/30
Tunnel
Tunnel
Procedure
Issue 01 (2016-04-30)

369

Configuration Guide
Step 2 Set attributes of Ethernet sub-interfaces.

Ethernet ports between NEs need to be configured with Ethernet sub-ports. Creating a subport for an Ethernet port on NE1 is taken as an example.
Issue 01 (2016-04-30)

370

Configuration Guide
Figure 10-50 Configuring an Ethernet sub-port
Set Port Mode to Layer Mix.

Then you can set the virtual
interface.
1
3
Set the virtual interface,

including VLAN, IP Address,
and Enable Tunnel.
6
4
----End

The configuration method is the same as that for MPLS tunnels over common NNIs.
Data Preparation
l
End-to-end MPLS tunnels with MPLS APS protection: source and sink boards and
explicit boards
Procedure
Issue 01 (2016-04-30)

371

Configuration Guide
LSR ID: 130.0.0.2
LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1
NE2
NE3
NE4
LSR ID: 130.0.0.4
NE5
LSR ID: 130.0.0.5

Issue 01 (2016-04-30)

372

Configuration Guide
NOTE
Step 3 Create an end-to-end MPLS tunnel.
Issue 01 (2016-04-30)

373

Configuration Guide
Figure 10-54 Tunnel plan

Board: 4-EM6T-1
IP: 46.1.64.5/30
Incoming Label: 1002
Outgoing Label: 1002
Board: 3-EM6T-1
IP: 46.1.64.6/30
Board: 3-ISU2-1
IP: 46.1.64.2/30
Board: 3-ISU2-1
IP: 46.1.64.1/30
L2 network
VLAN=4060
NE1
NE2
VL
AN
=4
09
0
NE3
Board:L 3-EM6T-1
NE4
IP: 46.1.64.9/30
Outgoing Label: 1003Board: 4-EM6T-1
NE5
IP: 46.1.64.10/30
Board: 3-ISU2-1
Incoming Label: 1003 IP: 46.1.64.13/30
Outgoing Label: 1003 Incoming Label: 1004
Outgoing Label: 1004 Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
Tunnel
1.
Create an end-to-end tunnel.
2
Double-click an
NE to set it as
the sink NE.
NE(1)
NE2
The calculation result is displayed.

You can manually adjust the explicit
boards and configure labels.

NE(3)
NE(2)
NE1
Double-click an
NE to set it as
the source NE.
NE3
NE(3)
NE(2)
NE(1)
Issue 01 (2016-04-30)

Labels can also be

374

Configuration Guide
Configure constraints for the tunnels. If the tunnels that are automatically calculated
are not the planned tunnels, you can configure constraints for them manually.
NE31
2-EM6F-2(Port-2)
node to display the
8
shortcut menu.
NE11
2.
2-EM6F-1(Port-1)
46.1.64.2
46.1.64.
5
9
10
NE21
Create an end-to-end MPLS tunnel between NE5 and NE1.

The creation method is the same as that for the tunnel between NE3 and NE1.
----End

Data Preparation
classification.
l

Issue 01 (2016-04-30)
PHB
MPLS EXP Value
Service Category
CS7
CS6
EF

AF4
AF3
O&M and real-time

HSDPA services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data services

375

Configuration Guide
NNI: microwave port and Ethernet port (for an Ethernet subinterface, the mapping needs
to be applied to its host Ethernet port.)
Procedure
----End

of MPLS tunnels.
Procedure
MPLS tunnels.
Issue 01 (2016-04-30)

376

Configuration Guide
4
6
NOTE
----End

This section describes how to set parameters for MPLS tunnels that traverse a Layer 2
network.

VLAN sub-ports need to be created for Ethernet ports connected to a Layer 2 network.
Issue 01 (2016-04-30)

377

Configuration Guide
Data Preparation
Board: 3-EM6T-1
IP:46.1.64.6/30
VLAN: 4060
Board: 4-EM6T-1
Board: 3-ISU2-1
IP:46.1.64.5/30
IP:46.1.64.2/30
VLAN: 4060
Board: 3-ISU2-1
IP:46.1.64.1/30
L2 network
VLAN=4060
NE1
VL
AN
Board: 3-EM6T-1
IP:46.1.64.9/30
VLAN: 4090
NE2
=4
0
NE3
90
NE4
Board: 4-EM6T-1
IP:46.1.64.10/30 Board: 3-ISU2-1
VLAN: 4090
IP:46.1.64.13/30
NE5
Board: 3-ISU2-1
IP:46.1.64.14/30
Tunnel
Tunnel
Procedure
Issue 01 (2016-04-30)

378

Configuration Guide
Step 2 Set attributes of Ethernet sub-interfaces.

Ethernet ports between NEs need to be configured with Ethernet sub-ports. Creating a subport for an Ethernet port on NE1 is taken as an example.
Issue 01 (2016-04-30)

379

Configuration Guide
Figure 10-59 Configuring an Ethernet sub-port
Set Port Mode to Layer Mix.

Then you can set the virtual
interface.
1
3
Set the virtual interface,

including VLAN, IP Address,
and Enable Tunnel.
6
4
----End

Data Preparation
l
Procedure
Issue 01 (2016-04-30)

380

Configuration Guide

LSR ID: 130.0.0.2
LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1
NE2
NE3
NE4
LSR ID: 130.0.0.4
NE5
LSR ID: 130.0.0.5
Step 2 Create a bidirectional MPLS tunnel.
Issue 01 (2016-04-30)

381

Configuration Guide

Board: 3-EM6T-1
IP: 46.1.64.6/30
Board: 4-EM6T-1
IP: 46.1.64.5/30
Board: 3-ISU2-1
IP: 46.1.64.2/30
Board: 3-ISU2-1
IP: 46.1.64.1/30
L2 network
VLAN=4060
NE1
VL
AN
=4
09
0
NE2
NE3
Board:L 3-EM6T-1
NE4
IP: 46.1.64.9/30
Outgoing Label: 1003Board: 4-EM6T-1
NE5
IP: 46.1.64.10/30
Board: 3-ISU2-1
Incoming Label: 1003 IP: 46.1.64.13/30
Outgoing Label: 1003 Incoming Label: 1004
Outgoing Label: 1004 Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
Tunnel
1.
Issue 01 (2016-04-30)

382

Configuration Guide
3
1001
3-ISU2
1(RTNIF-1)
1001
1001
1
46.1.64.2
130.0.0.1
Issue 01 (2016-04-30)

383

Configuration Guide
3
1001
3-ISU2
1(RTNIF-1)
1001
1001
Virtual Ethernet
1(VEther-1)
1002
1002
46.1.64.6
46.1.64.1
130.0.0.3
130.0.0.1
Issue 01 (2016-04-30)

384

Configuration Guide
3
1001
Virtual Ethernet
1(VEther-1)
1002
1002
1
46.1.64.5
130.0.0.3
2.

----End

Data Preparation
classification.
l

Issue 01 (2016-04-30)
PHB
MPLS EXP Value
Service Category
CS7
CS6

385

Configuration Guide
PHB
MPLS EXP Value
Service Category
EF

AF4
AF3
O&M and real-time

HSDPA services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data services
NNI: microwave port and Ethernet port (for an Ethernet subinterface, the mapping needs
to be applied to its host Ethernet port.)
Procedure
----End
Issue 01 (2016-04-30)

386

Configuration Guide

Procedure
2
parameters.
3
The test result 5

is displayed.
1
NOTE
128/256/512/1024/1280 bytes as desired.
----End
10.6 Configuration Example (MPLS Tunnels Traversing a

TDM Network)
This s example illustrates how MPLS tunnels carried by ML-PPP links traverse a TDM
network.
Issue 01 (2016-04-30)

387

Configuration Guide

On the network, two MPLS tunnels need to traverse the TDM network.
In this example (as shown in Figure 10-65), two MPLS tunnels need to traverse the TDM
network, to transmit services from BTS1 and BTS2 to the BSC.
Figure 10-65 Networking diagram (MPLS tunnels traversing a TDM network)
RTN 950
RTN 950
3-ISU2-1 (to NE3)

RTN 950
1-ML1-1~2 (to NE2)
1-CQ1-1-VC12:1~4 (to NE4)
3-ISU2-1 (to NE2)
1-ML1-1~2 (to NE1)
TDM network
BTS1
ML-PPP (2E1)
NE2
BSC
NE1
ML
-PP
P(
4V
C1
2
NE3
NE4
MPLS Tunnel 1
RTN 950
MPLS Tunnel 2
3-ISU2-1 (to NE5)
NE5
1-CQ1-1-VC12:1~4 (to
NE1)
BTS2
RTN 950
3-ISU2-1 (to NE4)

Because ML-PPP is involved, NNIs need to be configured on a per-NE basis.

MP groups need to be created for VC-12 timeslots over E1 ports and channelized STM-1
ports connected to a TDM network.
Issue 01 (2016-04-30)

388

Configuration Guide
Data Preparation
Board: 2-ML1-1~2
MP Group2 IP: 46.1.64.6/30
Board: 3-ISU2-1
IP: 46.1.64.2/30
Board: 1-ML1-1~2
MP Group1 IP: 46.1.64.5/30
Board: 3-ISU2-1
IP: 46.1.64.1/30
TDM network
ML-PPP(2E1)
NE1
ML
-P
PP
NE2
(4V
C1
2)
Board: 1-CQ1-1
Serial Interface: 1
NE4
High Channel: VC4-1
Low Channel: VC12-1~4
MP Group1 IP:
Board: 1-CQ1-1
46.1.64.9/30
Serial Interface: 1
High Channel: VC4-1
Board: 3-ISU2-1
Low Channel: VC12-1~4 IP: 46.1.64.13/30
MP Group1
IP: 46.1.64.10/30
NE3
NE5
Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
Tunnel
Procedure
Issue 01 (2016-04-30)

389

Configuration Guide
Step 2 Configure an MP group for an ML1 board. NE1 is taken as an example.

1.
Issue 01 (2016-04-30)
Set attributes of E1 ports.

390

Configuration Guide
Set Port Mode to Layer 3 and

Encapsulation Mode to PPP.
VC12 Frame Format must be set to structured

mode and set to the default value. Frame
Mode can be set to 30 or 31. Frame Mode
must be set consistently for peer ports.
2.
Issue 01 (2016-04-30)
Configure the MP group.

391

Configuration Guide
Set the parameters. The tunnel needs to be

enabled. Sequence Number Type must be
set consistently for the ingress and egress
nodes.
3
Select the configured E1 interface

from the Interface tab page.
Step 3 Configure an MP group for a CQ1 board. NE1 is taken as an example.

1.
Configure the E1 frame format and frame mode for a channelized STM-1.
Select a board.
2.
Issue 01 (2016-04-30)
VC12 Frame Format must be set to structured mode

and set to the default value.
Frame Mode can be set to 30 or 31.
Frame Mode must be set consistently for peer ports.
Create a serial port.

392

Configuration Guide
Set parameters. Only one VC-12

timeslot can be set at a time. The first
to fourth VC-12 timeslots need to be
set separately.
4
1
After the configuration, change Encapsulation Type to PPP and Port Level to Layer 3.
3.
3
enabled. Sequence Number Type needs to
be set consistently for the first and last nodes.
2
1-CQ1
1-CQ1-1(Serial-1)
1-CQ1-1(Serial-2)
1-CQ1-1(Serial-3)
1-CQ1-1(Serial-4)
Select the configured Serial port
----End
Issue 01 (2016-04-30)

393

Configuration Guide

Data Preparation
l
End-to-end MPLS tunnels with MPLS APS protection: source and sink boards and
explicit boards
Procedure
LSR ID: 130.0.0.2
LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1
NE2
NE3
NE4
LSR ID: 130.0.0.4
NE5
LSR ID: 130.0.0.5
Issue 01 (2016-04-30)

394

Configuration Guide

NOTE
Step 3 Create an end-to-end MPLS tunnel.
Issue 01 (2016-04-30)

395

Configuration Guide

Board: 3-ISU2-1
MP Group1 IP: 46.1.64.5/30 IP: 46.1.64.2/30
MP Group2 IP: 46.1.64.6/30

Board: 3-ISU2-1
IP: 46.1.64.1/30
TDM network
ML-PPP(2E1)
NE1
MP Group1 IP: 46.1.64.9/30

NE2
ML
-PP
P(4
VC
12
)
NE3
NE4
MP Group1 IP: 46.1.64.10/30

Board: 3-ISU2-1
IP: 46.1.64.13/30
NE5
Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
Tunnel
1.
Create an end-to-end tunnel.
2
Double-click an
NE to set it as
the sink NE.
The calculation result is displayed.

You can manually adjust the explicit
boards and configure labels.

NE(3)
NE(2)
NE(1)
NE1
NE2
Double-click an
NE to set it as
the source NE.
NE3
NE(3)
NE(2)
NE(1)
Issue 01 (2016-04-30)

Labels can also be

396

Configuration Guide
Configure constraints for the tunnels. If the tunnels that are automatically calculated
are not the planned tunnels, you can configure constraints for them manually.
NE31
2-EM6F-2(Port-2)
node to display the
8
shortcut menu.
NE11
2.
2-EM6F-1(Port-1)
46.1.64.2
46.1.64.
5
9
10
NE21
Create an end-to-end MPLS tunnel between NE5 and NE1.

The creation method is the same as that for the tunnel between NE3 and NE1.
----End

In this example, the planned DiffServ mapping is the same as the default DiffServ mapping.
Therefore, you do not need to configure QoS information.
Data Preparation
classification.
l

Issue 01 (2016-04-30)
PHB
MPLS EXP Value
Service Category
CS7
CS6
EF

AF4
AF3
O&M and real-time

HSDPA services
AF2
AF1
BE
HSDPA data services

397

Configuration Guide
NNI: microwave port and MP group
Procedure
----End

of MPLS tunnels.
Procedure
MPLS tunnels.
Issue 01 (2016-04-30)

398

Configuration Guide
4
6
NOTE
----End

This section describes how to set parameters of MPLS tunnel.

MP groups need to be created for VC-12 timeslots over E1 ports and channelized STM-1
ports connected to a TDM network.
Issue 01 (2016-04-30)

399

Configuration Guide
Data Preparation
Board: 2-ML1-1~2
MP Group2 IP: 46.1.64.6/30
Board: 3-ISU2-1
IP: 46.1.64.2/30
Board: 1-ML1-1~2
MP Group1 IP: 46.1.64.5/30
Board: 3-ISU2-1
IP: 46.1.64.1/30
TDM network
ML-PPP(2E1)
NE1
ML
-P
PP
NE2
(4V
C1
2)
Board: 1-CQ1-1
Serial Interface: 1
NE4
High Channel: VC4-1
Low Channel: VC12-1~4
MP Group1 IP:
Board: 1-CQ1-1
46.1.64.9/30
Serial Interface: 1
High Channel: VC4-1
Board: 3-ISU2-1
Low Channel: VC12-1~4 IP: 46.1.64.13/30
MP Group1
IP: 46.1.64.10/30
NE3
NE5
Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
Tunnel
Procedure
Issue 01 (2016-04-30)

400

Configuration Guide
Step 2 Configure an MP group for an ML1 board. NE1 is taken as an example.

1.
Issue 01 (2016-04-30)
Set attributes of E1 ports.

401

Configuration Guide
Set Port Mode to Layer 3 and

Encapsulation Mode to PPP.
VC12 Frame Format must be set to structured

mode and set to the default value. Frame
Mode can be set to 30 or 31. Frame Mode
must be set consistently for peer ports.
2.
Issue 01 (2016-04-30)

402

Configuration Guide

enabled. Sequence Number Type must be
set consistently for the ingress and egress
nodes.
3
Select the configured E1 interface

Step 3 Configure an MP group for a CQ1 board. NE1 is taken as an example.

1.
Configure the E1 frame format and frame mode for a channelized STM-1.
Select a board.
2.
Issue 01 (2016-04-30)
VC12 Frame Format must be set to structured mode

and set to the default value.
Frame Mode can be set to 30 or 31.
Frame Mode must be set consistently for peer ports.
Create a serial port.

403

Configuration Guide
Set parameters. Only one VC-12

timeslot can be set at a time. The first
to fourth VC-12 timeslots need to be
set separately.
4
1
After the configuration, change Encapsulation Type to PPP and Port Level to Layer 3.
3.
3
enabled. Sequence Number Type needs to
be set consistently for the first and last nodes.
2
1-CQ1
1-CQ1-1(Serial-1)
1-CQ1-1(Serial-2)
1-CQ1-1(Serial-3)
1-CQ1-1(Serial-4)
Select the configured Serial port
----End
Issue 01 (2016-04-30)

404

Configuration Guide

This section describes the procedure for configuring MPLS tunnel information.
Data Preparation
l
Procedure
LSR ID: 130.0.0.2
LSR ID: 130.0.0.3
LSR ID: 130.0.0.1
NE1
NE2
NE3
NE4
LSR ID: 130.0.0.4
NE5
LSR ID: 130.0.0.5
Issue 01 (2016-04-30)

405

Configuration Guide
Step 2 Create a bidirectional MPLS tunnel.

MP Group2 IP: 46.1.64.6/30
Board: 3-ISU2-1
MP Group1 IP: 46.1.64.5/30 IP: 46.1.64.2/30
Board: 3-ISU2-1
IP: 46.1.64.1/30
TDM network
ML-PPP(2E1)
NE1
MP Group1 IP: 46.1.64.9/30

NE2
ML
-PP
P(4
VC
12
)
NE4
MP Group1 IP: 46.1.64.10/30

Board: 3-ISU2-1
IP: 46.1.64.13/30
Tunnel
NE3
NE5
Board: 3-ISU2-1
IP: 46.1.64.14/30
Tunnel
1.
Issue 01 (2016-04-30)

406

Configuration Guide
3
1001
3-ISU2
1(RTNIF-1)
1001
1001
1
46.1.64.2
130.0.0.1
Issue 01 (2016-04-30)

407

Configuration Guide
3
1001
3-ISU2
1(RTNIF-1)
1001
1001
ML-PPP
1(MP-1)
1002
1002
46.1.64.6
46.1.64.1
130.0.0.3
130.0.0.1
Issue 01 (2016-04-30)

408

Configuration Guide
3
1001
ML-PPP
2(MP-1)
1002
1002
1
46.1.64.5
130.0.0.3
2.

----End

In this example, the planned DiffServ mapping is the same as the default DiffServ mapping.
Therefore, you do not need to configure QoS information.
Data Preparation
classification.
l

Issue 01 (2016-04-30)
PHB
MPLS EXP Value
Service Category
CS7

409

Configuration Guide
PHB
MPLS EXP Value
Service Category
CS6
EF

AF4
AF3
O&M and real-time

HSDPA services
AF2
AF1
BE
HSDPA data services
NNI: microwave port and MP group
Procedure
----End
Issue 01 (2016-04-30)

410

Configuration Guide

Procedure
2
parameters.
3
The test result 5

is displayed.
1
NOTE
128/256/512/1024/1280 bytes as desired.
----End
Issue 01 (2016-04-30)

411

Configuration Guide
11
11 Configuring ETH PWE3 Services
Configuring ETH PWE3 Services
About This Chapter

ETH PWE3 services are available in E-Line services carried by PWs, E-Aggr services carried
by PWs, and E-LAN services (VPLS) carried by PWs.
11.1 End-to-End Configuration Process (E-Line Services Carried by PWs)
This process is applicable to scenarios where E-Line services carried by PWs are configured
on the PEs at both ends.
11.2 End-to-End Configuration Process (Hybrid Configuration of PW-Carried E-Line
Services and E-LAN Services)
This process is applicable to scenarios where an access point PE is configured with E-Line
services carried by PWs and a convergence point PE is configured with E-LAN services.
11.3 Per-NE Configuration Process (E-Line Services Carried by PWs)
This section describes the process for configuring E-Line services carried by PWs in end-toend mode, including configuring ports that receive and transmit the E-Line services,
configuring link aggregation groups (LAGs), configuring QoS policies, configuring PW
protection, and verifying the E-Line configurations.
11.4 Per-NE Configuration Process (E-Aggr Services Carried by PWs)
This section describes the process for configuring E-Aggr services carried by PWs on a perNE basis, including configuring UNI ports, configuring protection, and configuring QoS, and
verifying the E-Aggr service configurations.
11.5 Per-NE Configuration Process (E-LAN Services Carried by PWs)
This section describes the process for configuring E-LAN services carried by PWs, including
configuring ports that receive and transmit the E-Line services, configuring link aggregation
groups (LAGs), configuring QoS policies, configuring PW protection, and verifying the ELAN configurations.
11.6 Configuration Example (E-Line Services Carried by SS-PW)
This example assumes that MPLS tunnels have been configured.
11.7 Configuration Example (E-Line Services Carried by MS-PWs)
11.8 Configuration Example (Hybrid Configuration of PW-Carried E-Line Services and ELAN Services)
Issue 01 (2016-04-30)

412

Configuration Guide
In this example, a combination of PW-carried E-Line and E-LAN services is configured for
Ethernet service convergence.
11.9 Configuration Example (E-Aggr Services Carried by PWs)
Issue 01 (2016-04-30)

413

Configuration Guide
11.1 End-to-End Configuration Process (E-Line Services

Carried by PWs)
This process is applicable to scenarios where E-Line services carried by PWs are configured
on the PEs at both ends.
Flowchart
Figure 11-1 Flowchart for configuring E-Line services carried by PWs in end-to-end mode
Required
Start
Optional
Configure LAGs.
Configure E-Line services

carried by PWs.
Configure a PW APS
protection group.
Configure QoS.
Verify E-Line service

configurations.
End
NOTE
For PWE3 services that have been configured on a per-NE basis, follow instructions in A.15.4 Searching for
MPLS Tunnels and PWE3 Services to synchronize the services to the network layer of the NMS. This
enables end-to-end management of the PWE3 services.
Issue 01 (2016-04-30)

414

Configuration Guide

Operation
Remarks
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
Required if UNIs are Ethernet ports. Basic attributes include the port
mode, encapsulation type, and maximum frame length.
A.8.8.3 Setting
the Layer 2
Attributes of
Ethernet Ports
Required if UNIs are Ethernet ports. Layer 2 attributes of Ethernet ports

define link-layer information, including TAG attributes and port
attributes.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports
Required when you need to enable the port self-loop test function, the
automatic loopback shutdown function, or the broadcast packet
suppression function.
Configuring IF_ETH Ports

Table 11-2 Configuring IF_ETH ports
Operation
Remarks
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports
Required if UNIs are IF_ETH ports. Basic attributes of an IF_ETH port

specify the basic information, including the port mode and encapsulation
mode.
A.8.9.2 Setting
the Layer 2
Attributes of
IF_ETH Ports
Required if UNIs are IF_ETH ports. Layer 2 attributes of the IF_ETH

port specify link-layer information, including the TAG attribute and
QinQ type domain.

Issue 01 (2016-04-30)
Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.

415

Configuration Guide
NOTE
Configuring E-Line Services Carried by PWs

Table 11-4 Configuring UNI-NNI E-Line services carried by PWs
Operation
Remarks
A.15.6.1 Creating PWE3 Service

Templates
Optional.
A.15.6.6 Configuring PW-Based

E-Line Services (in an End-toEnd Mode)
Required.
A.11.4.2 Creating an MS-PW
Required for an S-PE.
Perform this operation to customize the default

PWE3 service parameter values.
Set related parameters according to the service plan

and parameter plan.
Set related parameters according to the service plan

and parameter plan.
Configuring PW Protection
Normally, PW APS is configured to work with other equipment configured with MC-PW
APS, therefore achieving dual-homing protection. You can configure dual-homing services in
end-to-end mode on the NMS. For details, see the Configuration Guide of the equipment
where MC-PW APS is configured or the U2000 Online Help.
Configuring QoS
Verifying E-Line Services

Table 11-5 Verifying E-Line services
Issue 01 (2016-04-30)
Operation
Remarks
A.15.6.10 Verifying PW-Based

Ethernet Service Configurations
(in an End-to-End Mode) or A.
15.6.8 Verifying PW
Configurations in an End-toEnd Mode
Required.
Use ETH OAM LB or PW ping to verify the
connectivity of an Ethernet service.

416

Configuration Guide
11.2 End-to-End Configuration Process (Hybrid

Configuration of PW-Carried E-Line Services and E-LAN
Services)
This process is applicable to scenarios where an access point PE is configured with E-Line
services carried by PWs and a convergence point PE is configured with E-LAN services.
Issue 01 (2016-04-30)

417

Configuration Guide
Flowchart
Figure 11-2 Flowchart
Required
Start
Optional
Configure LAGs.
Configure PW-carried E-LAN

services.
Configure a PW APS
protection group.
Configure QoS.
Verify E-LAN service

configurations.
End
Issue 01 (2016-04-30)

418

Configuration Guide

Operation
Remarks
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
A.8.8.3 Setting
the Layer 2
Attributes of
Ethernet Ports

attributes.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports

Issue 01 (2016-04-30)
Operation
Remarks
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports

mode.
A.8.9.2 Setting
the Layer 2
Attributes of
IF_ETH Ports

QinQ type domain.
A.8.9.4 Setting
the Advanced
Attributes of
IF_ETH Ports

419

Configuration Guide

Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
Configuring UNI-NNI E-LAN Services Carried by PWs

Table 11-9 Configuring UNI-NNI E-LAN services carried by PWs
Operation
Remarks
A.9.3.21
Configuring
Global Attributes
of VPLS Services
Optional.
A.15.6.7 Hybird
Configuration of
E-Line and ELAN services
based on PWE3
Required.
A.11.4.2 Creating
an MS-PW
Perform this operation to change the T-PID value of the S-VLAN tag
carried in PW-carried QinQ services.
A combination of PWE3 E-Line services and PWE3 E-LAN services

is used as an end-to-end configuration example.
NOTE
On a packet switched network (PSN), if Ethernet services carried on PEs are
end-to-end services from one UNI to a PW, configure the Ethernet services as
E-Line services carried by PWs on a per-NE basis.
For details about how to configure PW protection, see Configuration Procedure (PW APS) in
PW APS/FPS of the Feature Description.
Configuring QoS
Issue 01 (2016-04-30)

420

Configuration Guide
Verifying PW-Based Ethernet Service

Table 11-10 Verifying PW-Based Ethernet service
Operation
Remarks
Verifying PWBased Ethernet

Service
Configurations
(in an End-toEnd Mode) or A.
15.6.8 Verifying
PW
Configurations in
an End-to-End
Mode
Required.
Use ETH OAM LB or PW ping to verify the connectivity of a PWBased Ethernet service.
11.3 Per-NE Configuration Process (E-Line Services

Carried by PWs)
This section describes the process for configuring E-Line services carried by PWs in end-toend mode, including configuring ports that receive and transmit the E-Line services,
configuring link aggregation groups (LAGs), configuring QoS policies, configuring PW
protection, and verifying the E-Line configurations.
Issue 01 (2016-04-30)

421

Configuration Guide
Flowchart
Figure 11-3 Flowchart for configuring E-Line services carried by PWs
Required
Start
Optional
Configure LAGs.
Configure E-Line services

carried by PWs.
Configure a PW APS
protection group.
Configure QoS.
Verify E-Line service

configurations.
End

Issue 01 (2016-04-30)
Operation
Remarks
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
A.8.8.3 Setting
the Layer 2
Attributes of
Ethernet Ports

attributes.

422

Configuration Guide
Operation
Remarks
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports

Operation
Remarks
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports

mode.
A.8.9.2 Setting
the Layer 2
Attributes of
IF_ETH Ports

QinQ type domain.

Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.
NOTE
Issue 01 (2016-04-30)

423

Configuration Guide
Configuring UNI-NNI E-Line Services Carried by PWs

Table 11-14 Configuring UNI-NNI E-Line services carried by PWs
Operation
Remarks
A.9.3.9
Configuring
UNI-NNI ELine Services
(Carried by
PWs)(U2000)
or A.9.3.10
Configuring
UNI-NNI ELine Services
(Carried by
PWs)(Web
LCT)
Required.
A.11.4.2
Creating an
MS-PW
Configuring QoS
Verifying E-Line Services

Table 11-15 Verifying E-Line services
Issue 01 (2016-04-30)
Operation
Remarks
A.9.9 Using the ethernet service

OAM or A.11.4.4 Performing a
PW Ping Test
Required.
connectivity of an Ethernet service.

424

Configuration Guide
11.4 Per-NE Configuration Process (E-Aggr Services

Carried by PWs)
This section describes the process for configuring E-Aggr services carried by PWs on a perNE basis, including configuring UNI ports, configuring protection, and configuring QoS, and
verifying the E-Aggr service configurations.
Flowchart
Figure 11-4 Flowchart for configuring E-Aggr services
Required
Optional
Start
Configure LAGs.
Configure PW-carried E-Aggr

Services.
Configure a PW APS
protection group.
Configure QoS.

configurations.
End
Issue 01 (2016-04-30)

425

Configuration Guide

Operation
Remarks
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
A.8.8.3 Setting
the Layer 2
Attributes of
Ethernet Ports

attributes.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports

Operation
Remarks
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports

mode.
A.8.9.2 Setting
the Layer 2
Attributes of
IF_ETH Ports

QinQ type domain.

Issue 01 (2016-04-30)
Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.

426

Configuration Guide
NOTE
Configuring E-Aggr Services Carried by PWs

Table 11-19 Configuring E-Aggr services carried by PWs
Operation
Remarks
A.9.3.11
Creating EAGGR
Services
Required.
A.11.4.2
Creating an
MS-PW
NOTE
On a packet switched network (PSN), if Ethernet services carried on PEs are endto-end services from one UNI to a PW and require no VLAN ID swapping,
configure the Ethernet services as E-Line services carried by PWs on a per-NE
basis.
Configuring QoS
Verifying E-Aggr Services Carried by PWs

Table 11-20 Verifying E-Aggr services carried by PWs
Operation
Remarks

PW Ping Test
Required.
connectivity of E-Aggr services.
11.5 Per-NE Configuration Process (E-LAN Services

Carried by PWs)
This section describes the process for configuring E-LAN services carried by PWs, including
configuring ports that receive and transmit the E-Line services, configuring link aggregation
Issue 01 (2016-04-30)

427

Configuration Guide
groups (LAGs), configuring QoS policies, configuring PW protection, and verifying the ELAN configurations.
Flowchart
Figure 11-5 Flowchart for configuring E-LAN services carried by PWs on a Per-NE basis
Required
Start
Optional
Configure LAGs.
Configure PW-carried E-LAN

services.
Configure a PW APS
protection group.
Configure QoS.
Verify E-LAN service

configurations.
End
Issue 01 (2016-04-30)

428

Configuration Guide

Operation
Remarks
A.8.8.1 Setting
the Basic
Attributes of
Ethernet Ports
A.8.8.3 Setting
the Layer 2
Attributes of
Ethernet Ports

attributes.
A.8.8.5 Setting
the Advanced
Attributes of
Ethernet Ports

Operation
Remarks
A.8.9.1 Setting
the Basic
Attributes of
IF_ETH Ports

mode.
A.8.9.2 Setting
the Layer 2
Attributes of
IF_ETH Ports

QinQ type domain.

Issue 01 (2016-04-30)
Operation
Remarks
A.9.2.1
Creating a
LAG
A.9.2.2 Setting
LAG
Parameters
Optional.

429

Configuration Guide
NOTE
Configuring UNI-NNI E-LAN Services Carried by PWs

Table 11-24 Configuring UNI-NNI E-LAN services carried by PWs
Operation
Remarks
A.9.3.21
Configuring
Global
Attributes of
VPLS Services
Optional.
A.9.3.20
Configuring
PW-Carried
E-LAN
Services
(U2000)
Required.
A.11.4.2
Creating an
MS-PW
Perform this operation to change the T-PID value of the S-VLAN tag
carried in PW-carried QinQ services.
NOTE
On a packet switched network (PSN), if Ethernet services carried on PEs are endto-end services from one UNI to a PW, configure the Ethernet services as E-Line
services carried by PWs on a per-NE basis.
Configuring QoS
Verifying E-LAN Services Carried by PWs

Table 11-25 Verifying E-LAN services carried by PWs
Issue 01 (2016-04-30)
Operation
Remarks

PW Ping Test
Required.
connectivity of an E-LAN service.

430

Configuration Guide
11.6 Configuration Example (E-Line Services Carried by

SS-PW)

Ethernet services from BTSs need to be converged to an RNC through PWs based on MPLS
tunnel plan and configuration. The specific service requirements are as follows:
l
Ethernet services (VLAN ID: 310) from BTS31 are received by NE32 and need to be
transmitted to the RNC. A bidirectional tunnel (ID: 1601) with protection is available
between NE32 and NE31. Ethernet services carried by PWs from BTSs are transparently
transmitted over the tunnel.
Ethernet services from all BTSs have been configured with VLAN priorities based on
the service types (real-time voice services, HSDPA real-time services, R99 non-real-time
services, and HSDPA data services). The transmission network provides end-to-end QoS
control based on the VLAN priorities.
NE31's GE ports, which are connected to the RNC, need to be protected by a link
aggregation group (LAG).
Figure 11-6 Networking diagram (E-Line services carried by PWs, a simple example)
NE34
BTS33
NE33
FE
BTS31
R4
R4
Working tunnel
(ID=1601)
GE
Hybrid microwave chain

network
NE32
RTN 980
NE31
RTN 950
NE11
GE
GE
NE21
GE
Hybrid microwave ring

network
RNC
Table 11-26 provides the UNI information about the E-Line services carried by PWs.
Issue 01 (2016-04-30)

431

Configuration Guide
Table 11-26 Service port information

NE
Service Port
Remarks
NE32
2-EG4-3
Receives the Ethernet

services from BTS31.
NE31
1-EG43
1-EG44
Form a LAG.

In actual configuration, LAG and QoS are configured on a per-NE basis.
11.6.2.1 Configuring LAG

aggregation group (LAG) to protect Ethernet links connected to an RNC.
Procedure
Step 1 Configure the interface attributes.
3
4
Step 2 Create a LAG.
Issue 01 (2016-04-30)

432

Configuration Guide
Configure a load non-sharing and

non-revertive static LAG.
Select the working 4

board.
2
Select a protection board from
the Port box on the left.
----End

This section describes the procedure for configuring information about E-Line services
carried by PWs.
Issue 01 (2016-04-30)

433

Configuration Guide
Data Preparation
Figure 11-7 Data plan for PWE3 E-Line services between NE31 and NE32
PW ID:303
PW Incoming Label:40
PW Outgoing Label:40
Tunnel ID:1601
UNI:2-EG4-3
VLAN:310
BTS31
GE
PW ID:303
Tunnel ID:1601
GE
NE32
NE31
NE11
GE
UNI:1-EG4-3
VLAN:310
NE21
RNC
GE
Tunnel
transmitted to the RNC. A bidirectional tunnel (ID: 1601) with protection is available between
NE32 and NE31. Ethernet services carried by PWs connected to BTSs are transparently
Procedure
Step 1 Configure UNIs.
Issue 01 (2016-04-30)

434

Configuration Guide
NE(31)
NE(32)
NE(31)-1-EG4-3(Port-3)
NE(32)-2-EG4-3(Port-3)
Double-click the NE to make it the

source node. You can configure UNIs for
the NE.
Double-click the NE to make it the sink

node. You can configure UNIs by
referring the configuration procedure
applied to the source node.
13
8
NE(31)
NE(32)
6
10
11
12
Step 2 Configure the PW between NE31 and NE32 in end-to-end mode.
NE(31)
NE(32)
NE(31)-1-EG4-3(Port-3)
NE(32)-2-EG4-3(Port-3)
15
16
NE(31)
14
Configure a PW, and select the forward
and reverse tunnels.
A PW label can be automatically allocated
or manually specified.
NE(32)
17
----End

In this example, the DiffServ domain is deployed for UNIs based on C-VLAN priorities.
Issue 01 (2016-04-30)

435

Configuration Guide
Data Preparation
On UNIs, traffic carried on tunnels need to be classified based on the C-VLAN priority field
in packets. On NNIs, traffic carried on tunnels need to be classified based on the MPLS EXP
field in packets. In this example, the mapping in the default DiffServ domain is used for
simple traffic classification.
l

PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS7
CS6
EF
Real-time voice
service and
signaling service
AF4
AF3
O&M and realtime HSDPA

services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data
services
Ports applying the mapping: service UNIs and NNIs
Procedure
Step 1 Apply the mapping in the default DiffServ domain to target UNIs to implement simple traffic
classification.
Each NE uses the mapping in the default DiffServ domain, performing traffic classification
based on the C-VLAN priority field in the packets. The mapping is applied over UNIs and the
UNI port type needs to be changed to CVLAN.
Issue 01 (2016-04-30)

436

Configuration Guide
Figure 11-8 Applying the mapping in the default DiffServ domain to UNIs
4
Select the desired UNI from the
Port box on the left.
For a LAG, only its master port
can be set.
classification.
based on the Tunnel EXP field in the packets. The mapping is applied over NNIs and the NNI
port type needs to be changed to mpls-exp. For details, refer to tunnel QoS configurations.
----End
11.6.2.4 Verifying Services Carried by PWs

This section describes how to perform PW ping tests to check the connectivity of PWs.
Procedure
Step 1 Use the VCCV Ping function in Test and Check to verify the connectivity of PWs.
Issue 01 (2016-04-30)

437

Configuration Guide
Select the application control

channel.
Click this icon to set ping

parameters.
Click this icon to start a 5

ping test.
NOTE
After the verification, view the detailed results to check whether the number of received packets and the
number of transmitted packets are the same.
If a VCCV ping test result shows that the PW is unavailable, perform an LSP ping test to check the
connectivity of the MPLS tunnel.
----End
11.6.3 Per-NE Configuration Procedure

next NE.
11.6.3.1 Configuring UNIs

Set the encapsulation type to Layer 2 for UNIs.
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31 and NE32.
Issue 01 (2016-04-30)

438

Configuration Guide
Set Encapsulation Type to 802.1Q, set Tag to Tag Aware, and set Max Frame
Length(bytes) based on live network conditions. UNI configuration on NE31 is used as an
example.
3
4
----End

Procedure
Issue 01 (2016-04-30)

439

Configuration Guide
3
4


board.
2
Issue 01 (2016-04-30)

440

Configuration Guide
----End

This section describes the procedure for configuring E-Line services carried by PWs.
Data Preparation
PW ID:303
Tunnel ID:1601
UNI:2-EG4-3
VLAN:310
BTS31
GE
PW ID:303
Tunnel ID:1601
GE
NE32
NE31
NE11
GE
UNI:1-EG4-3
VLAN:310
NE21
RNC
GE
Tunnel
transmitted to the RNC. A bidirectional tunnel (ID: 1601) with protection is available between
NE32 and NE31. Ethernet services carried by PWs connected to BTSs are transparently
Procedure
Step 1 Configure PWE3 E-Line services on NE31.
Issue 01 (2016-04-30)

441

Configuration Guide
Set PW parameters and ensure

that the PW ID of a service is
the same on each NE.
Configure a bidirectional UNINNI service.
1601
1601
4
1
9
2
Step 2 Configure PWE3 E-Line services on NE32 by referring to the service configuration on NE31.
----End

Data Preparation
l

Issue 01 (2016-04-30)
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS7
CS6
EF
Real-time voice
service and
signaling service

442

Configuration Guide
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
AF4
AF3

services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data
services
Procedure
classification.
4
can be set.
classification.
Issue 01 (2016-04-30)

443

Configuration Guide
----End

Procedure
Step 1 Perform ping tests at the first and last nodes of the PW to check the connectivity of the PW.
Select the application

control channel.
Select the PW to be checked, right-click,
and choose Ping Test from the dropdown menu.
2
4
Displays the ping

result.
When the service is available, the packet loss ratio should be zero.
----End
11.7 Configuration Example (E-Line Services Carried by

MS-PWs)

On a network, E-Line services are transmitted over two MPLS tunnels.
Ethernet services from BTSs need to be converged to an RNC through PWs, based on MPLS
tunnel plan and configuration. The specific service requirements are as follows:
l
Issue 01 (2016-04-30)
transmitted to the RNC.
444

Configuration Guide
The information about the tunnels between NE34 and NE31 is as follows:
A bidirectional tunnel (ID: 1901) with no protection is available between NE34 and
NE32.
A bidirectional tunnel (ID: 1601) with protection is available between NE32 and
NE31.
Ethernet services from BTSs are carried by PWs on the two tunnels, and PW labels
and tunnel labels are swapped on NE32.
Ethernet services from all BTSs have been configured with VLAN priorities based on
the service types (real-time voice services, HSDPA real-time services, R99 non-real-time
services, and HSDPA data services). The transmission network provides end-to-end QoS
control based on the VLAN priorities.
Figure 11-11 Networking diagram (E-Line services carried by PWs, configured for
transmitting Ethernet services aggregated converged from a Hybrid microwave network)
BTS33
NE34
RTN 905
NE33
BTS31
R4
Tunnel
(ID=1901)
R4
FE
GE
NE32
RTN 980
network
GE
NE31
RTN 950
NE11
GE
Working tunnel
(ID=1601)
NE21
GE
RNC

network
Table 11-29 provides the UNI information about the E-Line services carried by PWs.
Issue 01 (2016-04-30)
NE
Service Port
Remarks
NE34
7EG6-1

NE31
1-EG43
1-EG44
Form a LAG.

445

Configuration Guide

In actual configuration, LAG and QoS are configured on a per-NE basis.

Procedure
3
4
Issue 01 (2016-04-30)

446

Configuration Guide


board.
2
----End

S-PEs need to be set during configuration of service information.
Issue 01 (2016-04-30)

447

Configuration Guide
Data Preparation
PW ID:305
NE34 Tunnel ID:1901
BTS33
UNI:7-EG6-1
VLAN:330
NE33
PW ID:305
Tunnel ID:1901
PW ID:304
Tunnel ID:1601
R4
PW ID:304
Tunnel ID:1601
GE
NE32
NE31
NE11
GE
GE
NE21
Tunnel (ID=1901)
GE
UNI:4-EG4-3
VLAN:330
RNC
Tunnel (ID=1601)
transmitted to the RNC. A bidirectional tunnel (ID: 1901) with no protection is available
between NE34 and NE32. A bidirectional tunnel (ID: 1601) with protection is available
between NE32 and NE31. Ethernet services from BTSs are carried by PWs on the two
tunnels, and PW labels and tunnel labels are swapped on NE32.
Procedure
Step 1 Configure UNIs.
Issue 01 (2016-04-30)

448

Configuration Guide
13
Double-click the NE to make it the sink
node. You can configure UNIs by
referring the configuration procedure
applied to the source node.
NE(31)
Double-click the NE to make it the
source node. You can configure
UNIs for the NE.
NE(32)
NE(31)-1-EG4-3(Port-3)
NE(32)
NE(34)-7-EG6-1(Port-1)
NE(31)-1-EG4-3(Port-3)
NE(32)-2-EG4-3(Port-3)
8
NE(31)
NE(31)
NE(32)
NE(32)
NE(34)
NE(32)
NE31_NE32
NE31_NE32
NE32_NE34
9
NE32_NE34
10
11
12
Step 2 Configure the MS-PW between NE31 and NE34 in end-to-end mode.
NE(34)
NE(32)
16
NE(31)-1-EG4-3(Port-3)
NE(32)
NE(34)-7-EG6-1(Port-1)
17
Click this icon to select the

PW switch node.
NE(31)
NE(32)
NE(32)
NE(34)
NE31_NE32
NE32_NE34
14
Select tunnel segments.

PW labels can be automatically allocated
or manually specified.
15
NE31_NE32
NE32_NE34
18
----End

Issue 01 (2016-04-30)

449

Configuration Guide
Data Preparation
l

PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS7
CS6
EF
Real-time voice
service and
signaling service
AF4
AF3

services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data
services
Procedure
classification.
Issue 01 (2016-04-30)

450

Configuration Guide
4
can be set.
classification.
----End

Procedure
Issue 01 (2016-04-30)

451

Configuration Guide

channel.

parameters.

ping test.
NOTE
----End

next NE.

UNI configuration is not required for S-PEs.
Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31 and NE34.
Issue 01 (2016-04-30)

452

Configuration Guide
example.
3
4
----End

Procedure
Issue 01 (2016-04-30)

453

Configuration Guide
3
4


board.
2
Issue 01 (2016-04-30)

454

Configuration Guide
----End

MS-PW information needs to be configured for S-PEs.
Data Preparation
PW ID:305
NE34 Tunnel ID:1901
BTS33
UNI:7-EG6-1
VLAN:330
NE33
PW ID:305
Tunnel ID:1901
PW ID:304
Tunnel ID:1601
R4
PW ID:304
Tunnel ID:1601
GE
NE32
NE31
NE11
GE
GE
NE21
Tunnel (ID=1901)
GE
UNI:4-EG4-3
VLAN:330
RNC
Tunnel (ID=1601)
transmitted to the RNC. A bidirectional tunnel (ID: 1901) with no protection is available
between NE34 and NE32. A bidirectional tunnel (ID: 1601) with protection is available
between NE32 and NE31. Ethernet services from BTSs are carried by PWs on the two
tunnels, and PW labels and tunnel labels are swapped on NE32.
Procedure
Issue 01 (2016-04-30)

455

Configuration Guide
304
BTS34_RNC
330
Set PW parameters and

ensure that the PW ID of
a service is the same on
each NE.
30
30
Configure a bidirectional
UNI-NNI service.
1601
1601
4
1
9
2
304
BTS34_RNC
330
Step 2 Configure PWE3 E-Line services on NE31 by referring to service configurations on NE34.
Step 3 Configure MS-PW on NE32.
Issue 01 (2016-04-30)

456

Configuration Guide
4
5
1601
1901
1601
1901
Step 4 Configure UNI-NNI E-Line services carried by PWs. For details, see A.9.3.9 Configuring
UNI-NNI E-Line Services (Carried by PWs)(U2000).
----End

Data Preparation
l

Issue 01 (2016-04-30)
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS7

457

Configuration Guide
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS6
EF
Real-time voice
service and
signaling service
AF4
AF3

services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data
services
Procedure
classification.
Issue 01 (2016-04-30)

458

Configuration Guide
4
can be set.
classification.
----End

Procedure
Issue 01 (2016-04-30)

459

Configuration Guide

control channel.
2
4
Displays the ping

result.
----End
11.8 Configuration Example (Hybrid Configuration of PWCarried E-Line Services and E-LAN Services)
In this example, a combination of PW-carried E-Line and E-LAN services is configured for
Ethernet service convergence.

On a network, an access point PE is configured with E-Line services carried by PWs and a
convergence point PE is configured with E-LAN services.
Ethernet services carried by PWs need to be configured Based on MPLS tunnel plan and
configuration. The specific service requirements are as follows:
l
Ethernet services at all preceding BTSs have already been configured with
corresponding VLAN priorities based on service types (real-time voice services, HSDPA
real-time services, R99 non-real-time services, and HSDPA data services), and the
transmission network is required to provide end-to-end QoS control based on the VLAN
priorities.
Issue 01 (2016-04-30)

460

Configuration Guide
Figure 11-16 Networking diagram (hybrid configuration of E-Line and E-LAN services
carried by PWs)
Working tunnel
(ID=1501)
NNI UNI
BTS11
VLAN 100
NE32
NE11
RTN 980
R4
GE
NE31
RTN 950
NE21
RTN 980
E-Line
E-Line
VPLS
RNC
Working tunnel
(ID=1701)
R4
BTS21
VLAN 100
Table 11-32 provides the information about ports of E-Line and E-LAN services carried by
PWs.
NE
Service Port
Remarks
NE11
2EG4-3

NE21
1EG4-3

NE31
1EG4-3
1EG44
Form a LAG.

In actual configuration, QoS is configured on a per-NE basis.

Procedure
Step 1 Set Ethernet port attributes for UNIs on NE31, NE11, and NE21.
example.
Issue 01 (2016-04-30)

461

Configuration Guide
3
4
Step 2 Configure LAG ports on NE31.


board.
2
Issue 01 (2016-04-30)

462

Configuration Guide
----End

This section describes the procedure for configuring hybrid E-Line services and E-LAN
services carried by PWs.
Data Preparation
Figure 11-17 Data plan for E-Line and E-LAN services carried by PWs
BTS11
VLAN 100
VSI ID:100
PW ID:301,302
PW Incoming Lable:60,50
PW Outgoing Lable:60,50
Tunnel ID:1501,1701
PW ID:301
PW Incoming Lable:60
PW Outgoing Lable:60
Tunnel ID:1501
NNI UNI
NE32
NE31
NE11
R4
UNI:2-EG4-3
VLAN:100
UNI:1-EG4-3
VLAN:100
NE21
E-Line
VPLS
RNC
E-Line
R4
PW ID:302
UNI:1-EG4-3 PW Incoming Lable:50
VLAN:100
Tunnel ID:1701
BTS21
VLAN 100
Tunnel (ID=1501)
Tunnel (ID=1701)
NE31 functions as a VPLS node, converging services carried by PWs from NE11 and
NE21.
Procedure
Step 1 Configure hybrid E-Line services and E-LAN services carried by PWs in end-to-end mode.
Issue 01 (2016-04-30)

463

Configuration Guide
Figure 11-18 Configuring hybrid E-Line services and E-LAN services carried by PWs in endto-end mode
NOTE
For OptiX RTN 950A, OptiX RTN 910A, OptiX RTN 905 or OptiX RTN 950 that uses a CSHU/CSHUA
board, MAC Address Learning Mode can be set to IVL.
Figure 11-19 Configuring a split horizon group on the VPLS node
----End

Issue 01 (2016-04-30)

464

Configuration Guide
Data Preparation
l

PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS7
CS6
EF
Real-time voice
service and
signaling service
AF4
AF3

services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data
services
Procedure
classification.
Issue 01 (2016-04-30)

465

Configuration Guide
4
can be set.
classification.
----End

Procedure
Issue 01 (2016-04-30)

466

Configuration Guide

channel.

parameters.

ping test.
NOTE
----End

next NE.

Procedure
Issue 01 (2016-04-30)

467

Configuration Guide
example.
3
4
Issue 01 (2016-04-30)

468

Configuration Guide


board.
2
----End

PWs to which E-LAN services are mounted are a collection of PWs that carry E-Line services
at all access points.
Issue 01 (2016-04-30)

469

Configuration Guide
Data Preparation
Figure 11-21 Data plan for E-Line and E-LAN services carried by PWs
BTS11
VLAN 100
VSI ID:100
PW ID:301,302
PW Incoming Lable:60,50
PW Outgoing Lable:60,50
Tunnel ID:1501,1701
PW ID:301
Tunnel ID:1501
NNI UNI
NE32
NE31
NE11
R4
UNI:2-EG4-3
VLAN:100
UNI:1-EG4-3
VLAN:100
NE21
E-Line
VPLS
RNC
E-Line
R4
PW ID:302
UNI:1-EG4-3 PW Incoming Lable:50
VLAN:100
Tunnel ID:1701
BTS21
VLAN 100
Tunnel (ID=1501)
Tunnel (ID=1701)
NE31 functions as a VPLS node, converging services carried by PWs from NE11 and
NE21.
Procedure
Issue 01 (2016-04-30)

470

Configuration Guide
302
BTS21_RNC
100
Set PW parameters and

ensure that the PW ID of a
service is the same on each
NE.
50
50
Configure a UNI-NNI
bidirectional service.
1701
130.0.0.1
1701
4
1
9
2
302
BTS21_RNC
100
Step 3 Configure E-LAN services carried by PWs.
1.
Issue 01 (2016-04-30)
Configure services on the UNI side.

471

Configuration Guide
NOTE
For OptiX RTN 950A, OptiX RTN 910A, OptiX RTN 905 or OptiX RTN 950 that uses a CSHU/
CSHUA board, MAC Address Learning Mode can be set to IVL.
NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 950A, the total number of VLANs
configured for Ethernet services must not exceed 1024. To avoid this restriction, do as follows:
configured for Ethernet services. However, theses ports cannot participate in other Ethernet services.
The number of VLANs connected to a V-UNI is restricted when VPLS services are configured on
OptiX RTN 980and OptiX RTN 950 using CSH boards. Users can use the preceding method to break
through this restriction or decrease the number of V-UNIs supported by an NE to increase the number
of VLANs that can be connected to a V-UNI.
2.
Issue 01 (2016-04-30)
Configure services carried by PWs to NE11 on the NNI side.

472

Configuration Guide
13
10
14
Configure a PW-carried
service to NE11.
12
1501
1501
15
11
3.

18
19
Configure a PW-carried
service on NE21.
17
1701
1701
20
16
4.
Issue 01 (2016-04-30)
Configure a split horizon group.

473

Configuration Guide
23
25
24
26
21
22
27
----End

Data Preparation
l

Issue 01 (2016-04-30)
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS7
CS6
EF
Real-time voice
service and
signaling service
AF4

474

Configuration Guide
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
AF3

services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data
services
Procedure
classification.
4
can be set.
classification.
Issue 01 (2016-04-30)

475

Configuration Guide
----End

Procedure

control channel.
2
4
Displays the ping

result.
----End
11.9 Configuration Example (E-Aggr Services Carried by

PWs)

On a network, an access point PE is configured with E-Line services carried by PWs and a
convergence point PE is configured with E-Aggr services.
Ethernet services from BTSs (with conflicting VLAN IDs) need to be converged to an RNC
through PWs based on MPLS tunnel plan and configuration. The specific service
requirements are as follows:
Issue 01 (2016-04-30)

476

Configuration Guide
Ethernet services from BTS11, BTS12, and BTS13, which respectively carry VLAN ID
100, VLAN ID 110, and VLAN ID 120, need to be transmitted to NE11 through a
Hybrid microwave chain network and then to the RNC. A bidirectional tunnel (ID: 1501)
with protection is available between NE11 and NE31. Ethernet services carried by PWs
from BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.
Hybrid microwave ring network and then to the RNC by means of VLAN forwarding. A
bidirectional tunnel (ID: 1701) with protection is available between NE21 and NE31.
Ethernet services carried by PWs from BTS21, BTS22, and BTS23 are transparently
priorities.
Figure 11-23 Flowchart for configuring E-Aggr services carried by PWs

VLAN forwarding
Service
BTS31
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
Working tunnel
(ID=1501)
FE
R4
NNI UNI
NE32
RTN 980
R4
network
NE11
RTN 980
NE21
RTN 980
E-Line
R4
E-Line
BTS12
VLAN 110
GE
NE31
RTN 950
E-Aggr
RNC
Working tunnel
(ID=1701)

network
R4
BTS13
VLAN 120
R4
1 BTS21
VLAN 100
R4
2 BTS22
VLAN 110
1 2 3 VLAN IDs conflict.
R4
3 BTS23
VLAN 120
Table 11-35 provides the port information about the E-Line and E-Aggr services carried by
PWs.
Issue 01 (2016-04-30)

477

Configuration Guide

NE
Service Port
Remarks
NE11
3-ISU2-1
Receives Ethernet services

from BTS11, BTS12, and
BTS13 through the Hybrid
microwave chain network.
NE21
1EG43
1EG44
NE21 cross-connects and

loops back the 1EG44
port to the 1EG43 port
by means of a network cable
to convert Native E-LAN
services (from BTS21,
BTS22, and BTS23)
received by the 1EG44
port on the Hybrid
microwave ring network to
E-Line services carried by
PWs.
NE31
1EG43
1EG44
Form a LAG.

next NE.

Procedure
example.
Issue 01 (2016-04-30)

478

Configuration Guide
3
4


board.
2
Issue 01 (2016-04-30)

479

Configuration Guide
----End

PWs to which E-Aggr services are mounted are a collection of PWs that carry E-Line services
at all access points.
Data Preparation
Figure 11-24 Data plan for E-Aggr services
VLAN forwarding
NNI
UNI
PW ID:301
Tunnel ID:1501
PW ID:302
Tunnel ID:1701
NNI
PW ID:301
UNI:3-ISU2-1
VLAN:100,110,120 PW Incoming Label:60
Tunnel ID:1501
BTS11
VLAN 100
100,110,120
100,110,120
UNI
UNI:1-EG4-3
VLAN:100,110,120,
200,210,220
100,110,120
200,210,220
NNI UNI
NE32
R4
network
NE31
NE11
NE21
R4
GE
E-Aggr
RNC

network
BTS12
VLAN 110
R4
BTS13
VLAN 120
UNI
NNI
PW ID:302
UNI:1-EG4-3
VLAN:100,110,120
Tunnel ID:1701
R4
BTS21
VLAN 100
R4
BTS22
VLAN 110
R4
BTS23
VLAN 120
Tunnel (ID=1501)
Tunnel (ID=1701)
Hybrid microwave chain network and then to the RNC. A bidirectional tunnel (ID: 1501)
with protection is available between NE11 and NE31. Ethernet services carried by PWs
from BTS11, BTS12, and BTS13 are transparently transmitted over the tunnel.
Hybrid microwave ring network and then to the RNC by means of VLAN forwarding. A
bidirectional tunnel (ID: 1701) with protection is available between NE21 and NE31.
Ethernet services carried by PWs from BTS21, BTS22, and BTS23 are transparently
Services carried by PWs converge at NE31.
Procedure
Issue 01 (2016-04-30)

480

Configuration Guide
302
NE21_RNC
100,110,120
Set PW parameters
and ensure that the
PW ID of a service is
the same on each NE.
50
50
Configure a bidirectional
UNI-NNI service.
1701
130.0.0.1
1701
4
1
9
2
302
NE21_RNC
100,110,120
Step 3 Create E-Aggr services.
1.
Configure services on the UNI side.
3
2
4
6
Set the location and

VLAN ID.
8
9
2.
Issue 01 (2016-04-30)

481

Configuration Guide
13
12
14
10
15
11
3.

18
17
19
20
16
4.
Issue 01 (2016-04-30)
Configure a VLAN forwarding table.

482

Configuration Guide
21
Create the third VLAN forwarding

table item for the PW whose ID is
301.
23
Displays the created VLAN forwarding table items:

two VLAN forwarding table items have been
created for the PW whose ID is 301.
24
22
For the PW whose ID is 302,

create the third VLAN forwarding
table item.
26
27
Three VLAN forwarding table items have been created
for the PW whose ID is 301.
Two VLAN forwarding table items have been created
for the PW whose ID is 302.
25
28
----End

Data Preparation
l

Issue 01 (2016-04-30)
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
CS7
CS6

483

Configuration Guide
PHB
C-VLAN Priority
MPLS EXP
Value
Service Category
EF
Real-time voice
service and
signaling service
AF4
AF3

services
AF2
Non-real-time R99
services
AF1
BE
HSDPA data
services
Procedure
classification.
4
can be set.
Issue 01 (2016-04-30)

484

Configuration Guide
classification.
----End

Procedure

control channel.
2
4
Displays the ping

result.
----End
Issue 01 (2016-04-30)

485

Configuration Guide
12
12 Configuring CES Services
Configuring CES Services
About This Chapter

CES services allow TDM E1s to be encapsulated to PWs and further transmitted over a packet
switched network (PSN).
NOTE
OptiX RTN 905 does not support the configuration of CES services.

You need to configure UNIs before configuring CES service information.
12.2 Per-NE Configuration Process
12.3 Configuration Example (CES Services Based on CESoPSN Encapsulation)
12.4 Configuration Example (CES Services Based on SAToP Encapsulation)
12.5 Configuration Example (Configuring CES Services Transparently Transmitting STM-1s)
Issue 01 (2016-04-30)

486

Configuration Guide

Flowchart
Required
Optional
Start
Smart E1
Channelized STM-1 E1
Change the E1 frame

format and frame mode
for channelized STM-1
Configure Smart E1
port attributes
Configure CES services
Configure PW APS
Verify CES services
End
NOTE
l For PWE3 services that have been configured on a per-NE basis, follow instructions in A.15.4 Searching
for MPLS Tunnels and PWE3 Services to synchronize the services to the network layer of the NMS.
This enables end-to-end management of the PWE3 services.
l Currently, a CES service transparently transmitting SDH overhead bytes cannot be configured in end-toend mode.
l For OptiX RTN 905, ensure that the working mode of E1 ports, channelized STM-1 ports, and multifunctional cascading ports is CES. For OptiX RTN 950A that houses an MN1 board, ensure that the
working mode of E1 ports and STM-1 ports on the CSHO board is CES. For details, see A.8.2 Setting
Working Modes of E1 Ports.
Issue 01 (2016-04-30)

487

Configuration Guide
Setting Attributes of Smart E1 Ports

Table 12-1 Setting attributes of Smart E1 ports
Operation
Remarks
A.8.6.1 Setting Basic

Attributes of Smart
E1 Ports
Required.
A.8.6.2 Setting
Advanced Attributes
of Smart E1 Ports
Optional. Set 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
timeslot 16.
l If all clocks on the PSN are synchronous, set Re-timing Mode
to Master Mode (that is retiming mode). If not all clocks on
the PSN are synchronous, set Re-timing Mode to another
value.
NOTE
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that
Service Mode of the E1 ports is CES Mode.
Changing the E1 Frame Format and Frame Mode for a Channelized STM-1
Table 12-2 Changing the E1 frame format and frame mode for a channelized STM-1
Operation
Remarks
A.8.5 Changing the

E1 Frame Format
and Frame Mode for
a Channelized
STM-1

The default value is CRC-4 Multiframe.
timeslot 16.
The default value is 31.
Issue 01 (2016-04-30)

488

Configuration Guide

Table 12-3 Configuring CES services
Operation
Remarks

Templates
Optional.
A.15.6.2 Configuring CES

Services in an End-to-End Mode
Required.
A.11.6.2 Modifying CES Service

Parameters
Perform this task to change the PHB of a CES service

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.
Verifying CES Services

Table 12-4 Verifying CES services
Operation
Remarks
Testing E1 Services by Using a

BER Tester or Testing E1 Services
Using PRBS
A CES service that uses fewer than 31 timeslots can

be tested only by means of a BER tester that supports
Nx64 kbit/s service tests.
Testing CES services in

channelized STM-1s using an
SDH analyzer
Perform this operation to test CES services in

channelized STM-1s using an SDH analyzer.
12.2 Per-NE Configuration Process

Issue 01 (2016-04-30)

489

Configuration Guide
Flowchart
Required
Start
Smart E1
Optional
Channelized STM-1 E1
Change the E1 frame

format and frame mode
for channelized STM-1
Configure Smart E1
port attributes
Configure CES services
Configure PW APS
Verify CES services
End
NOTE
l If all clocks on the PSN are synchronous, configure CES service clocks in retiming mode. If not all
clocks on the PSN are synchronous, configure CES service clocks in CES ACR mode. (ACR stands
for adaptive clock recovery.)
l For OptiX RTN 905, ensure that the working mode of E1 ports, channelized STM-1 ports, and
multi-functional cascading ports is CES. For OptiX RTN 950A that houses an MN1 board, ensure
that the working mode of E1 ports and STM-1 ports on the CSHO board is CES. For details, see A.
8.2 Setting Working Modes of E1 Ports.
Setting Attributes of Smart E1 Ports

Issue 01 (2016-04-30)
Operation
Remarks
A.8.6.1 Setting Basic

Attributes of Smart
E1 Ports
Required.

490

Configuration Guide
Operation
Remarks
A.8.6.2 Setting
Advanced Attributes
of Smart E1 Ports

timeslot 16.
l If all clocks on the PSN are synchronous, set Re-timing Mode
to Master Mode (that is retiming mode). If not all clocks on
the PSN are synchronous, set Re-timing Mode to another
value.
NOTE
Changing the E1 Frame Format and Frame Mode for a Channelized STM-1
Table 12-6 Changing the E1 frame format and frame mode for a channelized STM-1
Operation
Remarks
A.8.5 Changing the

E1 Frame Format
and Frame Mode for
a Channelized
STM-1

timeslot 16.

Table 12-7 Configuring CES services
Issue 01 (2016-04-30)
Operation
Remarks
A.11.6.1 Creating CES

Services
Set basic service

attributes.
Required.

491

Configuration Guide
Operation
Remarks
Configuring PWs
l Set the basic attributes of the

PWs. Required.
l Set the advanced attributes of the
PW. Optional.
Advanced attributes of PWs take
their default values.
A.11.6.2 Modifying
CES Service
Parameters
Required when you need to create a CES service for

transparently transmitting overhead bytes.
After creating the CES service at both ends, specify the
overhead bytes as planned.
A.11.4.2 Creating an
MS-PW
Verifying CES Services

Table 12-8 Verifying CES services
Operation
Remarks
Testing E1 Services by Using a

BER Tester or Testing E1 Services
Using PRBS
A CES service that uses fewer than 31 timeslots can

be tested only by means of a BER tester that supports
Nx64 kbit/s service tests.
Testing CES services in

channelized STM-1s using an
SDH analyzer
Perform this operation to test CES services in

channelized STM-1s using an SDH analyzer.
12.3 Configuration Example (CES Services Based on

CESoPSN Encapsulation)

On a network, base station services use E1 frame formats based on CRC4.
Based on 10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection),
configure CES services from BTS35 and BTS36 in Figure 12-3 according to the following
requirements:
Issue 01 (2016-04-30)

492

Configuration Guide
CES service port information is listed in Table 12-9.
A bidirectional tunnel (ID: 1501) with protection is available between NE11 and NE31.
Tunnel configurations and other related configurations have been completed during 10.3
Configuration Example (MPLS Tunnels with MPLS APS Protection).
Figure 12-3 Networking diagram
Working tunnel
(ID=1509)
GE
GE
NE32
NE31
NE11
GE
NE21
E1
BTS36
E1
GE
BSC
BTS35

NE
Service Port
Remarks
NE11
4-ML1-1
Transmits services from

BTS35 over timeslots 1 to
15 and services from BTS36
over timeslots 17 to 31.
NE31
2-ML1-1

BTS35 to the BSC over
timeslots 1 to 15.
2-ML1-2

BTS36 to the BSC over
timeslots 1 to 15.


The port mode needs to be set to Layer 1.
Issue 01 (2016-04-30)

493

Configuration Guide
Procedure
Step 1 Set E1 port attributes on the UNI side of NE31.
NE31 uses two E1 ports for receiving and transmitting services.
Set Port Mode to Layer 1.

2
Set Frame Format to a framed format.

Set Frame Mode to the same value

30 or 31 on both ends of a service.
NOTE
When E1 ports 1 and 16 are used, the DCN function needs to be disabled.
Step 2 Set E1 port attributes on the UNI side of NE11, by referring to configurations on the UNI side
of NE31.
----End

This section describes the procedure for configuring CES services in end-to-end mode.
Issue 01 (2016-04-30)

494

Configuration Guide
Data Preparation
Figure 12-4 Data plan for CESoPSN services
UNI
NNI
UNI
UNI
NNI
PW ID:203
Tunnel ID:1501
UNI:4-ML1-1
64k time slot:1-15
PW ID:203
UNI:2-ML1-1
PW Incoming Lable:203 64k time slot:1-15
Tunnel ID:1501
Working tunnel
(ID=1501)
NNI
PW ID:204
UNI:4-ML1-1
64k time slot:17-31 PW Incoming Lable:204
Tunnel ID:1501
UNI
NNI
PW ID:204
UNI:2-ML1-2
Tunnel ID:1501
NE32
NE31
NE11
E1
NE21
BSC
E1
BTS36
BTS35
Procedure
Step 1 Configure a CESoPSN service for the PW whose PW ID is 203.
1
NE(31)
NE(11)
Respectively double-click the source and sink nodes in
the physical topology to select UNIs.
When configuring the UNIs, select Channeled and
configure 64 kbit/s timeslots.
NE(31)-2-ML-1(Port-1)
NE(11)-4-ML-1(Port-1)
Configure PWs and select the forward and 4
reverse tunnels.
PW labels can be automatically allocated or
manually specified.
NE(31)
NE(11)
NE31_NE11
NE31_NE11
Issue 01 (2016-04-30)

495

Configuration Guide
Step 2 Configure a CESoPSN service for the PW whose PW ID is 204, by referring to configurations
for the PW whose PW ID is 203.
----End

Procedure
1

channel.

parameters.

ping test.
NOTE
----End
Issue 01 (2016-04-30)

496

Configuration Guide


Procedure
Set Port Mode to Layer 1.

2
Set Frame Format to a framed format.

Set Frame Mode to the same value

30 or 31 on both ends of a service.
NOTE
of NE31.
----End

CES services need to be configured one after another.
Issue 01 (2016-04-30)

497

Configuration Guide
Data Preparation
Figure 12-5 Data plan for CESoPSN services
UNI
NNI
UNI:4-ML1-1
64k time slot:1-15
UNI
NNI
PW ID:204
UNI:4-ML1-1
64k time slot:17-31 PW Incoming Lable:204
Tunnel ID:1501
UNI
NNI
PW ID:203
Tunnel ID:1501
PW ID:203
UNI:2-ML1-1
Tunnel ID:1501
Working tunnel
(ID=1501)
UNI
NNI
PW ID:204
UNI:2-ML1-2
Tunnel ID:1501
NE32
NE31
NE11
E1
NE21
E1
BTS36
BSC
BTS35
Procedure
Step 1 Create two CESoPSN services on NE31.
1.
Issue 01 (2016-04-30)
Create the service for the PW whose ID is 203.

498

Configuration Guide
1
4
6
7
2.
Create the service for the PW whose ID is 204, by referring to configuration for the PW
whose ID is 203.
Step 2 Create two CESoPSN services on NE11, by referring to configurations on NE31.

----End

Issue 01 (2016-04-30)

499

Configuration Guide
Procedure

control channel.
2
4
Displays the ping

result.
----End
12.4 Configuration Example (CES Services Based on

SAToP Encapsulation)

CES services based on SAToP encapsulation are configured when the frame format of E1
services from base stations is uncertain.
configure CES services from BTS22 in Figure 12-6 according to the following requirements:
l
Tunnel configurations and other related configurations have been completed during 10.3
Configuration Example (MPLS Tunnels with MPLS APS Protection).
There are no requirements for partial timeslot transmission.
Issue 01 (2016-04-30)

500

Configuration Guide
GE
GE
NE32
E1
NE31
NE11
GE
NE21
GE
BSC
Working tunnel
(ID=1505)
E1 loop
Hybrid radio ring

network
E1
BTS22

NE
Service Port
Remarks
NE21
6-ML11
6-ML12
Receive services from

BTS22 through a Hybrid
microwave network. For
configuration details, see 7.5
Configuration Example
(TDM Services on a
Hybrid Microwave Ring
Network).
6-ML13
6-ML14
Transmit the E1 services

from BTS22 from the TDM
plane to the packet plan by
forming cross-connect loops
with 6-ML11 and 6ML12 ports.
2-ML19
2-ML110
Transmit services from

BTS22 to the BSC.
NE31
NOTE
If E1 services are locally accessed, they can be received by Smart E1 ports. Therefore, cross-connect loops
between PDH ports and Smart E1 ports are not required.
Issue 01 (2016-04-30)

501

Configuration Guide

In actual configuration, UNI configuration and CES service verification are performed on a
per-NE basis.

Procedure
NOTE
of NE31.
----End
Issue 01 (2016-04-30)

502

Configuration Guide

In this example, each CES service exclusively occupies a UNI and all CES services use a
tunnel with the same source and sink; therefore, multiple CES services can be configured at a
time.
Data Preparation
Figure 12-7 Data plan for SAToP services
NNI
UNI
PW ID:201
UNI:2-ML1-9
PW Incoming Label:203 Unframe
Tunnel ID:1701
NNI
UNI
PW ID:202
UNI:2-ML1-10
Tunnel ID:1701
NE32
E1
NE31
NE11
NE21
BSC
Working tunnel
(ID=1701)
Hybrid microwave ring network
UNI
E1
BTS22
UNI:6-ML1-3
Unframe
UNI
UNI:6-ML1-4
Unframe
NNI
PW ID:201
Tunnel ID:1701
NNI
PW ID:202
Tunnel ID:1701
Procedure
Step 1 Configure SAToP services for PWs whose IDs are 201 and 202 in end-to-end mode.
Issue 01 (2016-04-30)

503

Configuration Guide
NE(21)
NE(31)-2-ML-9(Port-9)
NE(31)-2-ML-10(Port-10)
NE(21)-6-ML-3(Port-3)
NE(21)-6-ML-4(Port-4)
NE(31)
NE(31)
3
Respectively double-click the source and sink nodes in the physical

topology to select UNIs numbered 9 and 10 (configure two services
at the same time).
When configuring UNIs, do not select Channeled and do not
configure 64 kbit/s timeslots.
Specify PW ID, Forward Label and Reverse

Label for the two services separately, or select
Auto-Assign.
NE(21)
NE31_NE21
NE31_NE21
201, 202
201, 202
201, 202
----End

Procedure
Issue 01 (2016-04-30)

504

Configuration Guide

channel.

parameters.

ping test.
NOTE
----End

next NE.

Procedure
Issue 01 (2016-04-30)

505

Configuration Guide
NOTE
of NE31.
----End

Issue 01 (2016-04-30)

506

Configuration Guide
Data Preparation
Figure 12-8 Data plan for SAToP services
NNI
UNI
PW ID:201
UNI:2-ML1-9
Tunnel ID:1701
NNI
UNI
PW ID:202
UNI:2-ML1-10
Tunnel ID:1701
NE32
E1
NE31
NE11
NE21
BSC
Working tunnel
(ID=1701)
Hybrid microwave ring network
UNI
UNI:6-ML1-3
Unframe
E1
UNI
BTS22
UNI:6-ML1-4
Unframe
NNI
PW ID:201
Tunnel ID:1701
NNI
PW ID:202
Tunnel ID:1701
Procedure
Step 1 Create two SAToP services on NE31.
1.
Issue 01 (2016-04-30)
Create the service for the PW whose ID is 201.

507

Configuration Guide
1
4
6
7
2.
Create the service for the PW whose ID is 202, by referring to configuration for the PW
whose ID is 201.
Step 2 Create two SAToP services on NE21, by referring to configurations on NE31.

----End

Issue 01 (2016-04-30)

508

Configuration Guide
Procedure

control channel.
2
4
Displays the ping

result.
----End
12.5 Configuration Example (Configuring CES Services

Transparently Transmitting STM-1s)

On a network, E1 payload and SDH overhead bytes in STM-1s need to be transparently
transmitted over Packet microwave.
Packet microwave can be used to transparently transmit STM-1s from an SDH network across
special terrains such as lakes and swamps.
Configure CES services on NE11 and NE12 in Figure 12-9 according to the following
requirements:
l
The CES service transparently transmits the K1 and K2 bytes in STM-1s.
The CES service transparently transmits 2xE1 in STM-1s.
The tunnel and its related information have been configured.
There are no requirements for partial timeslot transmission.
Issue 01 (2016-04-30)

509

Configuration Guide
Figure 12-9 Networking Diagram

Working tunnel
(ID=1501)
Third party
SDH network
STM-1
STM-1
NE 11
Third party
SDH network
NE 12

NE
Service Port
Remarks
NE11
3-CQ1-1(VC12:1-2)
Transparently transmits the

2xE1 in STM-1s to NE12,
over VC-12 timeslots 1 and
2.
3-CQ1-1

K1 and K2 bytes in STM-1s
to NE12.
3-CQ1-1(VC12:1-2)

2xE1 in STM-1s to NE11,
over VC-12 timeslots 1 and
2.
3-CQ1-1

K1 and K2 bytes in STM-1s
to NE11.
NE12

In actual configuration, only CES services carrying E1 payload are configured in end-to-end
mode.

Procedure
Step 1 Set port attributes for the CQ1 board on the UNI side of NE11.
For the CQ1 board, the default port mode is Layer 1 and only VC-12 path parameters need to
be set.
Issue 01 (2016-04-30)

510

Configuration Guide
Set VC12 Frame Format to Unframe for VC12 timeslots transparently transmitting
services.
NOTE
When VC-12s 1, 17, 33, and 49 are used, the DCN function needs to be disabled.
Step 2 Set port attributes for the CQ1 board on the UNI side of NE12, referring to configurations on
NE11.
----End

In this example, each CES service exclusively occupies a UNI and all CES services use a
tunnel with the same source and sink; therefore, multiple CES services can be configured at a
time.
Data Preparation
Figure 12-10 Data plan for CES services carrying E1 payload
UNI
UNI:3-CQ1-1
VC12-1:Unframe
UNI
UNI:3-CQ1-1
VC12-1:Unframe
Third party
SDH network
NNI
NNI
PW ID:101
Tunnel ID:1501
PW ID:101
UNI:3-CQ1-1
PW Incoming Label:101 VC12-1:Unframe
Tunnel ID:1501
NNI
NNI
PW ID:102
Tunnel ID:1501
PW ID:102
UNI:3-CQ1-1
Tunnel ID:1501
Working tunnel
(ID=1501)
STM-1
UNI
STM-1
NE 11
RTN 980
Issue 01 (2016-04-30)
UNI
Third party
SDH network
NE 12
RTN 950

511

Configuration Guide
Procedure
Step 1 Configure SAToP services for PWs whose IDs are 101 and 102 in end-to-end mode.
1
NE(12)
NE(11)
Respectively double-click the source and sink nodes in the
physical topology to select UNIs numbered 1 and 2
(configure two services at the same time).
When configuring UNIs, do not select Channeled and do
not configure 64 kbit/s timeslots.
NE(12)-3-CQ1-1(Port-1)
NE(11)-3-CQ1-1(Port-1)
NE(31)
Specify PW ID, Forward Label and Reverse

Label for the two services separately, or select
Auto-Assign.
NE(21)
NE11_NE12
NE11_NE12
101, 102
101, 102
201, 202
----End
12.5.2.3 Configuring Information About CES Services Transmitting SDH

Overhead Bytes
CES services transmitting SDH overhead bytes does not support end-to-end configuration.
Data Preparation
Figure 12-11 Data plan for CES services transmitting SDH overhead bytes
UNI
NNI
NNI
PW ID:103
UNI:3-CQ1-1
Serive Type:SOH only PW Incoming Label:103
Tunnel ID:1501
Third party
SDH network
STM-1
STM-1
NE 11
RTN 980
Issue 01 (2016-04-30)
Working tunnel
(ID=1501)
UNI
PW ID:103
UNI:3-CQ1-1
PW Incoming Label:103 Serive Type:SOH only
Tunnel ID:1501
Third party
SDH network
NE 12
RTN 950

512

Configuration Guide
Procedure
Step 1 Create a CES service transmitting SDH overhead bytes on NE11.
Set Service Type

to SOH only.
1
4
6
7
Step 2 Create the CES service transmitting SDH overhead bytes on NE12, by referring to
configurations on NE11.
----End

Issue 01 (2016-04-30)

513

Configuration Guide
Procedure
1

channel.

parameters.

ping test.
NOTE
----End

next NE.

Issue 01 (2016-04-30)

514

Configuration Guide
Procedure
Step 1 Set port attributes for the CQ1 board on the UNI side of NE11.
For the CQ1 board, the default port mode is Layer 1 and only VC-12 path parameters need to
be set.
1
Set VC12 Frame Format to Unframe for VC12 timeslots transparently transmitting
services.
NOTE
When VC-12s 1, 17, 33, and 49 are used, the DCN function needs to be disabled.
Step 2 Set port attributes for the CQ1 board on the UNI side of NE12, referring to configurations on
NE11.
----End
12.5.3.2 Configuring Information About CES Services Carrying E1 Payload

Data Preparation
Figure 12-12 Data plan for CES services carrying E1 payload
UNI
UNI:3-CQ1-1
VC12-1:Unframe
UNI
UNI:3-CQ1-1
VC12-1:Unframe
Third party
SDH network
NNI
NNI
PW ID:101
Tunnel ID:1501
PW ID:101
UNI:3-CQ1-1
Tunnel ID:1501
NNI
NNI
PW ID:102
Tunnel ID:1501
PW ID:102
UNI:3-CQ1-1
Tunnel ID:1501
Working tunnel
(ID=1501)
STM-1
UNI
STM-1
NE 11
RTN 980
Issue 01 (2016-04-30)
UNI
Third party
SDH network
NE 12
RTN 950

515

Configuration Guide
Procedure
Step 1 Create two SAToP services on NE11.
3
When configuring two CES services,
you need to specify two Service ID and
Source Low Channel values.
1
4
7
You need to specify two PW
Incoming Label and PW
Outgoing Label values.
6
8
Step 2 Create two SAToP services on NE12, by referring to configurations on NE11.

----End
Issue 01 (2016-04-30)

516

Configuration Guide
12.5.3.3 Configuring Information About CES Services Transmitting SDH

Overhead Bytes
CES services transmitting SDH overhead bytes does not support end-to-end configuration.
Data Preparation
Figure 12-13 Data plan for CES services transmitting SDH overhead bytes
UNI
NNI
NNI
PW ID:103
UNI:3-CQ1-1
Serive Type:SOH only PW Incoming Label:103
Tunnel ID:1501
Third party
SDH network
Working tunnel
(ID=1501)
UNI
PW ID:103
UNI:3-CQ1-1
PW Incoming Label:103 Serive Type:SOH only
Tunnel ID:1501
STM-1
STM-1
NE 11
RTN 980
Third party
SDH network
NE 12
RTN 950
Procedure
Step 1 Create a CES service transmitting SDH overhead bytes on NE11.
Issue 01 (2016-04-30)

517

Configuration Guide
Set Service Type

to SOH only.
1
4
6
7
Step 2 Create the CES service transmitting SDH overhead bytes on NE12, by referring to
configurations on NE11.
----End

Procedure
Issue 01 (2016-04-30)

518

Configuration Guide

control channel.
2
4
Displays the ping

result.
----End
Issue 01 (2016-04-30)

519

Configuration Guide
13
13 Configuring ATM Services
Configuring ATM Services
About This Chapter

ATM services allow ATM cells to be encapsulated to PWs and further transmitted over a
packet switched network (PSN).
NOTE
OptiX RTN 905 does not support the configuration of ATM services.
13.1 End-to-End Configuration Process (ATM Services)

You need to configure UNIs before configuring ATM service information.
13.2 Per-NE Configuration Process (ATM Services)
13.3 Configuration Example (ATM Connection-based ATM Services)
13.4 Configuration Example (Transparently Transmitted ATM Services)
Issue 01 (2016-04-30)

520

Configuration Guide
13.1 End-to-End Configuration Process (ATM Services)

Flowchart
Figure 13-1 shows the flowchart for configuring ATM/IMA E1 services and fractional
ATM/IMA services. The procedure for configuring ATM/IMA E1 services is different from
the procedure for configuring fractional ATM/IMA services.
NOTE
Transparently transmitted (PORT-TRANS) ATM services cannot be configured in end-to-end mode.
Figure 13-1 Flowchart for configuring ATM services in end-to-end mode

Flow chart for configuring
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, follow instructions in A.15.4 Searching for
MPLS Tunnels and PWE3 Services to synchronize the PWE3 services to the network layer of the U2000.
This enables end-to-end management of the PWE3 services.

Issue 01 (2016-04-30)

521

Configuration Guide
Setting UNI Attributes for ATM/IMA E1 Services

Setting UNI attributes for ATM/IMA E1 services mainly involves setting Smart E1 port
attributes.
Remarks
Operation
Setting attributes
of Smart E1
ports
A.8.6.1 Setting
Basic
Attributes of
Smart E1 Ports
Required.
A.8.6.2 Setting
Advanced
Attributes of
Smart E1 Ports

l Set Frame Format and Frame Mode according
to service planning information. Ensure that
Frame Mode is set to the same value for the
local end and the peer end.
Normally, the port that transmits ATM/IMA
services uses the CRC-4 multiframe format and
the PCM30 frame mode.
NOTE
Setting UNI Attributes for Fractional E1 Services

Setting UNI attributes for fractional E1 services mainly involves setting Smart E1 port
attributes, creating serial ports, and configuring serial ports.
Operation
Remarks
Setting attributes
of Smart E1
ports
A.8.6.1 Setting
Basic
Attributes of
Smart E1 Ports
Required.
A.8.6.2 Setting
Advanced
Attributes of
Smart E1 Ports

Set Frame Format and Frame Mode according to
service planning information. Ensure that Frame
Mode is set to the same value for the local end and
the peer end.
Normally, the port that transmits fractional ATM
services uses the CRC-4 multiframe format and the
PCM31 frame mode.
Issue 01 (2016-04-30)

522

Configuration Guide
Operation
Creating and
configuring
serial ports
Remarks
A.8.7.1
Creating Serial
Ports
Required.
A.8.7.2 Setting
Basic
Attributes of
Serial Ports
Required.
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.
NOTE
Configuring ATM/IMA Information

Configuration of ATM/IMA information mainly involves binding ATM trunks, configuring an
IMA group, and configuring ATM ports.
Table 13-3 Configuring ATM/IMA information
Operation
Remarks
A.11.7.1 Binding ATM TRUNKs
Required.
NOTE
When the E1 frame mode is PCM30, timeslot 16
cannot be bound to an ATM trunk.
A.11.7.2 Configuring an IMA group
Required.
A.11.7.3 Setting ATM Port Parameters
Optional.
l Set Port Type and ATM Cell Payload
Scrambling according to the type of the
access equipment. It is recommended
that you retain the default values for
these parameters. The parameters must
be set to the same value for both ends of
a link.
l Other parameters take their default
values.
Configuring the Global ATM QoS Profile

Configuration of the global ATM QoS profile includes configuration of the global ATM
policy profile and configuration of the global CoS mapping table.
Issue 01 (2016-04-30)

523

Configuration Guide
Table 13-4 Configuring the global ATM QoS profile

Operation
Remarks
A.15.6.3 Configuring an ATM Policy

Profile
Required.
A.15.6.4 Configuring an ATM CoS

Mapping Profile
Required if the default CoS mapping

"DefaultAtmCosMap" does not meet
requirements.

Operation
Remarks

Templates
Optional.
A.15.6.5 Configuring ATM Services in an

End-to-End Mode
Required.
Perform this operation when the default

PWE3 service parameter values need to be
customized.
Verifying ATM Services

Operation
Remarks
Testing ATM Services
Test ATM service connectivity using the

ATM OAM function.
NOTE
The microwave equipment does not support
ATM OAM tests on transparently transmitted
services (PORT-TRANS) over an ATM port.
Therefore, it is recommended that an ATM OAM
test be initiated on a CE (for example, a BTS or
RNC) of a PSN, enabling ATM OAM packets to
be transparently transmitted through the
microwave network to the opposite CE on the
PSN. In this manner, an ATM service
connectivity test is implemented.
Issue 01 (2016-04-30)

524

Configuration Guide
13.2 Per-NE Configuration Process (ATM Services)

Flowchart
Figure 13-2 shows the flowchart for configuring ATM/IMA E1 services and fractional
ATM/IMA services. The procedure for configuring ATM/IMA E1 services is different from
the procedure for configuring fractional ATM/IMA services.
Figure 13-2 Flowchart for configuring ATM services in end-to-end mode
Flow chart for configuring
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
Setting UNI Attributes for ATM/IMA E1 Services

Setting UNI attributes for ATM/IMA E1 services mainly involves setting Smart E1 port
attributes.
Issue 01 (2016-04-30)

525

Configuration Guide

Operation
Remarks
Setting attributes
of Smart E1
ports
A.8.6.1 Setting
Basic
Attributes of
Smart E1 Ports
Required.
A.8.6.2 Setting
Advanced
Attributes of
Smart E1 Ports

l Set Frame Format and Frame Mode according
to service planning information. Ensure that
Frame Mode is set to the same value for the
local end and the peer end.
Normally, the port that transmits ATM/IMA
services uses the CRC-4 multiframe format and
the PCM30 frame mode.
NOTE
Setting UNI Attributes for Fractional E1 Services

Setting UNI attributes for fractional E1 services mainly involves setting Smart E1 port
attributes, creating serial ports, and configuring serial ports.
Operation
Remarks
Setting attributes
of Smart E1
ports
A.8.6.1 Setting
Basic
Attributes of
Smart E1 Ports
Required.
A.8.6.2 Setting
Advanced
Attributes of
Smart E1 Ports

Set Frame Format and Frame Mode according to
service planning information. Ensure that Frame
Mode is set to the same value for the local end and
the peer end.
Normally, the port that transmits fractional ATM
services uses the CRC-4 multiframe format and the
PCM31 frame mode.
Creating and
configuring
serial ports
Issue 01 (2016-04-30)
A.8.7.1
Creating Serial
Ports
Required.
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.

526

Configuration Guide
Operation
Remarks
A.8.7.2 Setting
Basic
Attributes of
Serial Ports
Required.
NOTE
Configuring ATM/IMA Information

Configuration of ATM/IMA information mainly involves binding ATM trunks, configuring an
IMA group, and configuring ATM ports.
Table 13-7 Configuring ATM/IMA information
Operation
Remarks
Required.
NOTE
When the E1 frame mode is PCM30, timeslot 16
cannot be bound to an ATM trunk.
Required.
Optional.
l Set Port Type and ATM Cell Payload
Scrambling according to the type of the
access equipment. It is recommended
that you retain the default values for
these parameters. The parameters must
be set to the same value for both ends of
a link.
l Other parameters take their default
values.
Configuring ATM QoS

Configuration of ATM QoS mainly involves configuration of the ATM policy and
configuration of the CoS mapping table. The ATM traffic management policy is not required
for transparently transmitted ATM services but required for ATM connection-based services.
Issue 01 (2016-04-30)

527

Configuration Guide
Table 13-8 Configuring ATM QoS

Operation
Remarks
A.11.9.3 Creating an ATM Policy
Required for services that are not

transparently transmitted ATM services.
A.11.9.1 Creating an ATM-DiffServ

Domain
Required if the default CoS mapping

"DefaultAtmCosMap" does not meet
requirements.

Remarks
Operation
A.11.8.1 Creating ATM
Services
Setting service attributes
Set the basic attributes for

ATM services. Required.
Configuring ATM
connections
Create ATM connections.

Required.
Configuring PWs
l Set the basic attributes

for PWs. Required.
l Set advanced attributes
for PWs. Optional.
If Control Word is No
Use, set Control
Channel Type to Alert
Label. Other advanced
attributes generally take
l Configure the QoS.
Optional.
QoS parameters take
Configuring CoS mapping
Required if the default CoS

mapping
"DefaultAtmCosMap" does
not meet requirements.
Select the policy for
mapping different ATM
service levels to CoS
priorities. In this way,
different quality levels are
provided for different ATM
services.
A.11.4.2 Creating an MSPW
Issue 01 (2016-04-30)

Set related parameters according to the service plan and
parameter plan.

528

Configuration Guide
Verifying ATM Services

Operation
Remarks
Testing ATM Services
Test ATM service connectivity using the

ATM OAM function.
NOTE
The microwave equipment does not support
ATM OAM tests on transparently transmitted
services (PORT-TRANS) over an ATM port.
Therefore, it is recommended that an ATM OAM
test be initiated on a CE (for example, a BTS or
RNC) of a PSN, enabling ATM OAM packets to
be transparently transmitted through the
microwave network to the opposite CE on the
PSN. In this manner, an ATM service
connectivity test is implemented.
13.3 Configuration Example (ATM Connection-based

ATM Services)

ATM connection-based ATM services must be deployed because PW mapping and ATM
traffic monitoring on a network are based on ATM connections.
configure information about ATM services transmitted from BTS13 and BTS14 according to
the following network planning information (as shown in Figure 13-3):
l
Information about ATM service ports is provided in Table 13-9.
A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between
NE11 and NE31. This tunnel and its corresponding information have been configured in
10.3 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).
Issue 01 (2016-04-30)

529

Configuration Guide

Working tunnel
(ID=1501)
GE
GE
NE32
RTN980
NE11
RTN980
Hybrid radio chain network
E1
R99
BTS13
E1
GE
NE21
RTN980
NE31
RTN950
E1
RNC
GE
E1 loop
R99
BTS14
Table 13-9 Information about service ports

NE
Service Port
Remarks
NE11
4-ML1-5
Configure this port to

receive BTS13 services
through a Hybrid
For the service
configuration process, see
7.4 Configuration
Example (TDM Services
on a Hybrid Microwave
Chain Network).
4-ML1-6
4-ML1-7
Configure these ports to

receive BTS14 services
through a Hybrid
For the service
configuration process, see
7.4 Configuration
Example (TDM Services
on a Hybrid Microwave
Chain Network).
4-ML1-8
4-ML1-9
4-ML1-10
Issue 01 (2016-04-30)

Use an E1 cable to connect

this port to port 4-ML1-5 so
that E1 services from
BTS13 are switched from
the TDM plane to the packet
plane.
530

Configuration Guide
NE
Service Port
Remarks
4-ML1-11
4-ML1-12
Use E1 cables to connect

these ports to ports 4-ML1-6
to 4-ML1-9 so that E1
services from BTS14 are
switched from the TDM
plane to the packet plane.
4-ML1-13
4-ML1-14
NE31
2-ML1-10
2-ML1-11
2-ML1-12

transmit BTS13 and BTS14
services to the RNC.
2-ML1-13
2-ML1-14
NOTE
If E1 services are received directly from Smart E1 ports, you do not need to connect the Smart E1 ports
and corresponding PDH ports with E1 cables.

In actual configuration, UNIs, ATM/IMA information, and verification of ATM services are
configured on a per-NE basis.

Port Mode must be set to Layer 2.
Procedure
Step 1 Configure attributes of UNIs on NE31.
Configure attributes of E1 ports 2-MP1-10 to 2-MP1-14.
Issue 01 (2016-04-30)

531

Configuration Guide
4
When setting Frame Format and Frame Mode, ensure
that Frame Mode is set to the same value for the local
and peer ends. Normally, the CRC-4 multi-frame format
and the PCM30 frame mode are used.

Configure attributes of E1 ports 4-MP1-10 to 4-MP1-14 by referring to the configuration
procedure applied to NE31.
----End
13.3.2.2 Configuring ATM/IMA Information

In this example, ATM links connected to user equipment adopts IMA protection.
Issue 01 (2016-04-30)

532

Configuration Guide
Data Preparation
Figure 13-4 Data plan for IMA groups
IMA Group 1
VCTRUNK:
4-ML1-1(Trunk-1)
IMA Group 2
VCTRUNK:
4-ML1-1(Trunk-2)
Bound Path
IMA Group 1
4-ML1-10
VCTRUNK:
2-ML1-1(Trunk-1)
Bound Path
4-ML1-11
4-ML1-12
4-ML1-13
4-ML1-14
Working tunnel
Bound Path
2-ML1-10
2-ML1-11
2-ML1-12
2-ML1-13
2-ML1-14
(ID=1501)
GE
GE
NE32
NE31
NE11
E1
R99
BTS13
E1
NE21
GE
E1
RNC
GE
E1 loop
R99
BTS14
Procedure
Step 1 Create IMA groups on NE11.
1.
Create IMA Group 1.
4
1
6
2
2.
Issue 01 (2016-04-30)
Create IMA Group 2.

533

Configuration Guide
9
8
10
3.
Configure data about IMA group management.

11
IMA must be disabled when only one E1

carries ATM services and can be enabled
when multiple E1s carry ATM services.
Clock Mode must be set to the same value for both ends of an
IMA link. Normally, Clock Mode is set to ITC mode for a BTS.
12
13
Step 2 Configure data about IMA group management on NE31 by referring to the configuration
----End

QoS information configuration for ATM services involves configuration of ATM policies for
ATM connections and CoS mapping relationships.
Data Preparation
l
Prepare data for creating two ATM policies for four types of ATM services: a policy for
one E1 and a policy for four E1s.
Table 13-10 Data required for configuring a policy for one E1
Issue 01 (2016-04-30)
Parameter
CBR Service
(1xE1)
rt-VBR
Service
(1xE1)
nrt-VBR
Service
(1xE1)
UBR Service
(1xE1)
Policy ID

534

Configuration Guide
Parameter
CBR Service
(1xE1)
rt-VBR
Service
(1xE1)
nrt-VBR
Service
(1xE1)
UBR Service
(1xE1)
Policy Name
1e1_cbr
1e1_rtvbr
1e1_nrtvbr
1e1_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparen
tNoScr
ClpTransparen
tScr
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
Table 13-11 Data required for configuring a policy for four E1s
Issue 01 (2016-04-30)
Parameter
CBR Service
(4xE1s)
rt-VBR
Service
(4xE1s)
nrt-TVBR
Service
(4xE1s)
UBR Service
(4xE1s)
Policy ID
Policy Name
4e1_cbr
4e1_rtvbr
4e1_nrtvbr
4e1_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparen
tNoScr
ClpTransparen
tScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
500
2252
9295
9295
Clp01Scr(cell/
s)
2048
8799
Max. Cell
Burst Size
(cell)
1000
1000

535

Configuration Guide
Parameter
CBR Service
(4xE1s)
rt-VBR
Service
(4xE1s)
nrt-TVBR
Service
(4xE1s)
UBR Service
(4xE1s)
Cell Delay
Variation
Tolerance
(0.1us)
102400
10240
Discard
Traffic Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled
Configure data to use the DefaultAtmCosMap.
Procedure
Step 1 Create end-to-end ATM policies. Use the creation of 1e1_cbr as an example to describe how
to create an end-to-end ATM policy.
1.
Issue 01 (2016-04-30)
Create a global ATM policy.

536

Configuration Guide
2.
Apply the ATM policy to NEs.
Issue 01 (2016-04-30)

537

Configuration Guide
Step 2 Create an end-to-end CoS mapping relationship.

The default mapping "DefaultAtmCosMap" is used. If another mapping relationship is
required, use the following steps to create one.
1.
Create a global ATM CoS mapping relationship.
2.
Apply the mapping relationship to NEs.

See operation b in step 1.
----End

In actual configuration, related ATM connections must be created.
Issue 01 (2016-04-30)

538

Configuration Guide
Data Preparation
Figure 13-5 Data plan for ATM services
UNI
NNI
4-ML1-1(Trunk-1)
VPI/VCI:30/32
ATM Policy:1e1_cbr PW ID:300
UNI
Tunnel ID:1501
4-ML1-1(Trunk-1)
VPI/VCI:30/33
ATM Policy:4e1_cbr
NNI
UNI
PW ID:300
Tunnel ID:1501
Working tunnel
(ID=1501)
GE
2-ML1-1(Trunk-1)
VPI/VCI:30/32
ATM Policy:1e1_cbr
VPI/VCI:30/33
ATM Policy:4e1_cbr
GE
NE32
R99
BTS13
NE21
GE
RNC
GE
E1 loop
E1
E1
E1
NE31
NE11
R99
BTS14
Procedure
Step 1 Create ATM services.
1.
Create the source and sink nodes, and PW services.

1
Display source and 6

sink info.
Double-click the
desired sink and
select Trunk-1.
NE(11)
NE(31)
Right-click the sink and
choose Select Sink and select
Trunk-2.
NE(31)-2-ML-1(Trunk-1)
Configure PW info.
Double-click the
desired source and
select Trunk-1.
7
9
NE(31)
NE(11)
NE31_NE11
NE31_NE11
Issue 01 (2016-04-30)

539

Configuration Guide
2.
Create ATM links.
N
E
(
1
1
)
4
M
L
30
2
30
(
T
r
u
n
k
NE(31)
NE(11)
2
)
NE31_NE11
NE(31)
NE(11)
Select created ATM policies, apply 1e1_cbr to the first 12
Link and 4e1_cbr to the second Link and assign VPI and
VCI for them.
5
32
33
NE(31)[Ingress:1e1_cbr,Egress:...
30
32
30
33
30
32
30
33
NE31_NE11
11
13
10
3.
Configure ATM QoS.
NE(11)
14
15
16
NE(31)
NE(11)
NE(31)
NE31_NE11
Select the default ATM CoSMap template

or a customized template for the source
and sink nodes.
NE31_NE11
17
----End

Procedure
Issue 01 (2016-04-30)

540

Configuration Guide

channel.

parameters.

ping test.
NOTE
----End

In actual configuration, data can be configured on a per-NE basis.

Procedure
Issue 01 (2016-04-30)

541

Configuration Guide
4

----End

In this example, ATM links connected to user equipment adopts IMA protection.
Issue 01 (2016-04-30)

542

Configuration Guide
Data Preparation
IMA Group 1
VCTRUNK:
4-ML1-1(Trunk-1)
IMA Group 2
VCTRUNK:
4-ML1-1(Trunk-2)
Bound Path
IMA Group 1
4-ML1-10
VCTRUNK:
2-ML1-1(Trunk-1)
Bound Path
4-ML1-11
4-ML1-12
4-ML1-13
4-ML1-14
Working tunnel
Bound Path
2-ML1-10
2-ML1-11
2-ML1-12
2-ML1-13
2-ML1-14
(ID=1501)
GE
GE
NE32
NE31
NE11
E1
R99
BTS13
E1
NE21
GE
E1
RNC
GE
E1 loop
R99
BTS14
Procedure
1.
Create IMA Group 1.
4
1
6
2
2.
Issue 01 (2016-04-30)
Create IMA Group 2.

543

Configuration Guide
9
8
10
3.

11

12
13
----End

QoS information configuration for ATM services involves configuration of ATM policies for
ATM connections and CoS mapping relationships.
Data Preparation
l
Prepare data for creating two ATM policies for four types of ATM services: a policy for
one E1 and a policy for four E1s.
Table 13-12 Data required for configuring a policy for one E1
Issue 01 (2016-04-30)
Parameter
CBR Service
(1xE1)
rt-VBR
Service
(1xE1)
nrt-VBR
Service
(1xE1)
UBR Service
(1xE1)
Policy ID

544

Configuration Guide
Parameter
CBR Service
(1xE1)
rt-VBR
Service
(1xE1)
nrt-VBR
Service
(1xE1)
UBR Service
(1xE1)
Policy Name
1e1_cbr
1e1_rtvbr
1e1_nrtvbr
1e1_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparen
tNoScr
ClpTransparen
tScr
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
Table 13-13 Data required for configuring a policy for four E1s
Issue 01 (2016-04-30)
Parameter
CBR Service
(4xE1s)
rt-VBR
Service
(4xE1s)
nrt-TVBR
Service
(4xE1s)
UBR Service
(4xE1s)
Policy ID
Policy Name
4e1_cbr
4e1_rtvbr
4e1_nrtvbr
4e1_ubr
Service Type
CBR
RT-VBR
NRT-VBR
UBR
Traffic Type
ClpTransparen
tNoScr
ClpTransparen
tScr
NoClpScr
NoClpNoScr
Clp01Pcr(cell/
s)
500
2252
9295
9295
Clp01Scr(cell/
s)
2048
8799
Max. Cell
Burst Size
(cell)
1000
1000

545

Configuration Guide
Parameter
CBR Service
(4xE1s)
rt-VBR
Service
(4xE1s)
nrt-TVBR
Service
(4xE1s)
UBR Service
(4xE1s)
Cell Delay
Variation
Tolerance
(0.1us)
102400
10240
Discard
Traffic Frame
Disabled
Disabled
Disabled
Disabled
UPC/NPC
Disabled
Disabled
Disabled
Disabled
Configure data to use the DefaultAtmCosMap.
Procedure
Step 1 Create an ATM policy on NE31. Use the creation of 1e1_cbr as an example to describe how
to create an ATM policy.
Step 2 Create a CoS mapping relationship on NE31. The default mapping "DefaultAtmCosMap" is
used. If another mapping relationship is required, use the following steps to create one.
Issue 01 (2016-04-30)

546

Configuration Guide
5
1
Step 3 Configure the same data on NE11.

----End

In actual configuration, related ATM connections must be created.
Data Preparation
UNI
NNI
4-ML1-1(Trunk-1)
VPI/VCI:30/32
ATM Policy:1e1_cbr PW ID:300
UNI
Tunnel ID:1501
4-ML1-1(Trunk-1)
VPI/VCI:30/33
ATM Policy:4e1_cbr
NNI
UNI
PW ID:300
Tunnel ID:1501
Working tunnel
(ID=1501)
GE
2-ML1-1(Trunk-1)
VPI/VCI:30/32
ATM Policy:1e1_cbr
VPI/VCI:30/33
ATM Policy:4e1_cbr
GE
NE32
NE31
NE11
E1
R99
BTS13
E1
GE
NE21
E1
RNC
GE
E1 loop
R99
BTS14
Procedure
Step 1 Create ATM services on NE31.
Issue 01 (2016-04-30)

547

Configuration Guide
1.
Create two ATM connections.

6
A service whose source port is Trunk-1

and VPI/VCI is 30/32 has been created.
1
2.
Create a PW.
10
11
1501
1501
12
13
3.
Issue 01 (2016-04-30)
Configure QoS information.

548

Configuration Guide
14
15
16
----End

Procedure
Issue 01 (2016-04-30)

549

Configuration Guide

control channel.
2
4
Displays the ping

result.
----End
13.4 Configuration Example (Transparently Transmitted

ATM Services)

Transparently transmitted ATM services must be deployed because only transparent
transmission of ATM services is required.
Compared with service requirements in 13.3 Configuration Example (ATM Connectionbased ATM Services), this configuration example has the following different service
requirements:
l
Services from BTS13 and BTS14 are directly transmitted to NE11. The RNC uses
different E1 ports to receive services from different BTSs. For specific ATM service port
information, see Table 13-14.
A bidirectional tunnel (ID: 1501), which has a protection tunnel, is available between
NE11 and NE31. This tunnel and its corresponding information have been configured in
10.3 Configuration Example (MPLS Tunnels with MPLS APS Protection).
The NEs do not need to perform traffic management for ATM services.
Issue 01 (2016-04-30)

550

Configuration Guide

Working tunnel
(ID=1501)
NE32
NE31
NE11
E1
RNC
NE21
E1
E1
R99
R99
BTS13
BTS14
Table 13-14 Information about service ports

NE
Service Port
Remarks
NE11
4-ML1-10

receive BTS13 services.
4-ML1-11
4-ML1-12

receive BTS14 services.
4-ML1-13
4-ML1-14
NE31
2-ML1-10

transmit BTS13 services to
the RNC.
2-ML1-11
2-ML1-12

transmit BTS14 services to
the RNC.
2-ML1-13
2-ML1-14

In actual configuration, UNIs, ATM/IMA information, and verification of ATM services are
configured on a per-NE basis.

Issue 01 (2016-04-30)

551

Configuration Guide
Procedure
4

----End

This section describes the procedure for configuring IMA services.
Issue 01 (2016-04-30)

552

Configuration Guide
Data Preparation
IMA Group 1
VCTRUNK:
4-ML1-1(Trunk-1)
IMA Group 2
VCTRUNK:
4-ML1-1(Trunk-2)
Bound Path
IMA Group 1
VCTRUNK:
2-ML1-1(Trunk-1)
4-ML1-10
IMA Group 2
Bound Path
4-ML1-11
4-ML1-12
4-ML1-13
4-ML1-14
VCTRUNK:
2-ML1-1(Trunk-2)
Working tunnel
(ID=1501)
GE
Bound Path
2-ML1-10
Bound Path
2-ML1-11
2-ML1-12
2-ML1-13
2-ML1-14
GE
NE32
GE
NE21
RNC
GE
E1
E1
R99
BTS13
E1
NE31
NE11
R99
BTS14
Procedure
1.
Create IMA Group 1.
4
1
6
2
2.
Issue 01 (2016-04-30)
Create IMA Group 2.

553

Configuration Guide
9
8
10
3.

11

12
13
----End

You need to configure ATM CoS mapping relationships and download them to NEs.
Data Preparation
Table 13-15 Data plan for QoS of transparently transmitted ATM services
Parameter
Value
NE11 and NE31
Issue 01 (2016-04-30)
Mapping Relation Name
new
PORT-TRANS
EF

554

Configuration Guide
Procedure
Step 1 Create an end-to-end CoS mapping relationship.
1.
Create a global ATM CoS mapping relationship.
5
2
NOTE
PHB service classes for other service types are invalid for transparently transmitted ATM services. It is
recommended that a transparently transmitted ATM service takes its default PHB service class.
2.
Apply the mapping relationship to NEs.
Step 2 Configure an ATM QoS template in end-to-end mode and apply the template to services.
Issue 01 (2016-04-30)

555

Configuration Guide
----End

During configuration, you do not need to configure ATM connections.
Data Preparation
UNI
4-ML1-1(Trunk-1)
UNI
4-ML1-1(Trunk-2)
NNI
PW ID:101
Tunnel ID:1501
NNI
PW ID:102
Tunnel ID:1501
UNI
NNI
PW ID:101
PW Incoming Lable:101 2-ML1-1(Trunk-1)
Tunnel ID:1501
UNI
NNI
PW ID:102
2-ML1-1(Trunk-2)
Tunnel ID:1501
Working tunnel
(ID=1501)
GE
GE
NE32
NE31
NE11
E1
GE
E1
R99
BTS13
NE21
E1
RNC
GE
E1 loop
R99
BTS14
Procedure
Step 1 Configure transparently transmitted ATM services between NE11 and NE31 in end-to-end
mode. In this example, the PW ID 101 is used.
Issue 01 (2016-04-30)

556

Configuration Guide
Set Link Type to ATM transparent cell

transport.
NE(11)-NE(12)
NE(11)-4-ML1-1(Trunk-1)
In the physical topology, double-click

NEs to configure the source and sink
nodes.
NE(31)-2-ML1-1(Trunk-1)
NE(11)
NE(31)
NE(11)_NE(31)
Select an existing global CoS mapping

template named new.
----End

Procedure
Issue 01 (2016-04-30)

557

Configuration Guide

channel.

parameters.

ping test.
NOTE
----End

This section describes the process for configuring transparently transmitted ATM services on
a single NE.

Procedure
Issue 01 (2016-04-30)

558

Configuration Guide
4

----End

This section describes the procedure for configuring IMA services.
Issue 01 (2016-04-30)

559

Configuration Guide
Data Preparation
IMA Group 1
VCTRUNK:
4-ML1-1(Trunk-1)
IMA Group 2
VCTRUNK:
4-ML1-1(Trunk-2)
Bound Path
IMA Group 1
VCTRUNK:
2-ML1-1(Trunk-1)
4-ML1-10
IMA Group 2
Bound Path
4-ML1-11
4-ML1-12
4-ML1-13
4-ML1-14
VCTRUNK:
2-ML1-1(Trunk-2)
Working tunnel
(ID=1501)
GE
Bound Path
2-ML1-10
Bound Path
2-ML1-11
2-ML1-12
2-ML1-13
2-ML1-14
GE
NE32
GE
NE21
RNC
GE
E1
E1
R99
BTS13
E1
NE31
NE11
R99
BTS14
Procedure
1.
Create IMA Group 1.
4
1
6
2
2.
Issue 01 (2016-04-30)
Create IMA Group 2.

560

Configuration Guide
9
8
10
3.

11

12
13
----End

Only the ATM CoS mapping table needs to be configured.
Data Preparation
Table 13-16 Data plan for QoS of transparently transmitted ATM services
Parameter
Value
NE11 and NE31
Issue 01 (2016-04-30)
Mapping Relation Name
new
PORT-TRANS
EF

561

Configuration Guide
Procedure
Step 1 Create a CoS mapping relationship on NE31.
4
2
1
5
Set the parameters for NE11 and NE31 as in the figure.

NOTE
PHB service classes for other service types are invalid for transparently transmitted ATM services. It is
recommended that a transparently transmitted ATM service takes its default PHB service class.
----End

This section describes the procedure for configuring transparently transmitted ATM services.
Issue 01 (2016-04-30)

562

Configuration Guide
Data Preparation
UNI
4-ML1-1(Trunk-1)
UNI
4-ML1-1(Trunk-2)
NNI
PW ID:101
Tunnel ID:1501
NNI
PW ID:102
Tunnel ID:1501
UNI
NNI
PW ID:101
Tunnel ID:1501
UNI
NNI
PW ID:102
Tunnel ID:1501
Working tunnel
(ID=1501)
GE
GE
NE32
E1
GE
E1
E1
NE31
NE11
NE21
RNC
GE
E1 loop
R99
BTS13
R99
BTS14
Procedure
Step 1 Create ATM services on NE31. In this example, PW ID 101 is used.
1.
Create an ATM connection.

3
4
1
2.
Issue 01 (2016-04-30)
Create a PW.

563

Configuration Guide
7
10
1501
1501
11
12
3.
Configure QoS information.
Step 2 Create ATM services on NE11 by referring to the configuration procedure applied to NE31.
----End

Issue 01 (2016-04-30)

564

Configuration Guide
Procedure

control channel.
2
4
Displays the ping

result.
----End
Issue 01 (2016-04-30)

565

Configuration Guide
14
Configuring the Clock
About This Chapter

To ensure that clocks of all the nodes on the transmission network are synchronized, configure
the clocks for these nodes according to a unified clock synchronization policy.
This section describes the process for configuring clocks. The configuration process applies to
clock configuration in the clock synchronization solution for the physical layer.
14.2 Configuration Example (Clocks on a Hybrid Microwave Chain Network)
A microwave network and its connected base stations need to synchronize with the clock of
the RNC.
14.3 Configuration Example (Clocks on a Hybrid Microwave Ring Network)
14.4 Configuration Example (Clocks on a PSN)
Issue 01 (2016-04-30)

566

Configuration Guide

This section describes the process for configuring clocks. The configuration process applies to
clock configuration in the clock synchronization solution for the physical layer.
This figure shows the flowchart for configuring clocks.
Figure 14-1 Flowchart for configuring clocks
Start
Set the SDH retiming
function.
Set the E1 clock
source for a
Channelized STM-1.
Configure clock
sources.
Configure standard or
extended SSM
protection.
Configure standard or
extended SSM
protection.
Configure a clock
source group.
Modify clock source
restoration
parameters.
Modify parameters of
the output clock.
Set the tributary

retiming function.
Required
Query the clock

synchronization
status.
Optional
End

Issue 01 (2016-04-30)

567

Configuration Guide
Table 14-1 Configuring clocks
Issue 01 (2016-04-30)
Operation
Remarks
A.12.1.1 Setting the SDH

Retiming Function
Required when an NE is connected to a third-party

network through a channelized STM-1 channel and the
NE clock and the third-party network clock are
asynchronous.
A.12.1.2 Setting the E1 Clock

Source for a Channelized
STM-1 Interface Board
Required when an E1 clock source needs to be set for a

channelized STM-1.
A.12.1.3 Configuring the

Clock Sources
Required.
Configuri
ng
standard
SSM or
extended
SSM
protection
A.12.1.4
Configuring
Clock Subnets
Required if standard SSM or extended SSM protection

needs to be used.
A.12.1.6
Configuring the
SSM Output
Status
When standard SSM protection or extended SSM

protection is used, set Output S1 Byte Info to Disabled
for a line port that is connected to another clock subnet.
A.12.1.7
Configuring the
Clock ID Output
Status
When extended SSM protection is used, set Output

Clock ID to Disabled for a line port that is connected to
another clock subnet.
A.12.1.5 UserDefined Clock

Quality
Required when an NE cannot identify the external clock

quality used for standard or extended SSM protection.
A.12.1.11 Modifying the

Recovery Parameter of the
Clock Source
Optional.
Modifyin
g
parameter
s of the
output
clock
A.12.1.9
Configuring
Clock Sources for
External Clock
Output
Optional.
A.12.1.8
Modifying the
Parameters of the
Clock Output
Optional.

568

Configuration Guide
Operation
Remarks
A.12.1.12 Querying the Clock

Synchronization Status
In normal cases:
l When a clock subnet uses the internal clock source
of an NE as the reference clock, set NE Clock Mode
to Free-Run Mode for this NE; set NE Clock Mode
to Tracing Mode for the other NEs.
l When a clock subnet uses the clock outside the
subnet as the reference clock, set NE Clock Mode to
Tracing Mode for all the NEs.
A.15.8 Querying the Clock

Tracing Relationship
Generally, the clock tracing relationship is consistent

with that in the network plan.
14.2 Configuration Example (Clocks on a Hybrid

Microwave Chain Network)
the RNC.

Network), configure the clocks according to the following requirements:
l
The microwave transmission network is synchronized with the clock of the BSC through
a link aggregation group (LAG) that consists of two GE links.
Clock synchronization signals are transmitted to BTSs over FE signals.
Figure 14-2 Networking diagram (clocks on a Hybrid microwave chain network)

FE
BTS2
FE
GE
GE
NE14
BTS3
FE
NE13
NE11
BSC
BTS1
FE
FE
NE15
NE16
BTS5
Issue 01 (2016-04-30)
NE12
BTS4

569

Configuration Guide

This section describes the procedure for configuring clock sources based on the planned clock
tracing relationship.
Data Preparation
Item
Planning Principles
Clock source information
You need to configure an

Ethernet clock source for
each link in an LAG.
Clock protection
Not in use.
In this example, a chain

network is set up. Therefore,
only priority-based clock
source protection is used
and the standard SSM or
extended SSM protection is
not used.
Clock synchronization
policy for base stations
A microwave network is
synchronized with the BSC
through GE ports, and
transmits timing reference
signals to base stations
through FE ports.
3-ISV3-1/
4-ISV3-1
Internal
NE14
RTN 905 2E
GE
NE13
RTN 950A
17-EG61 /
Internal
NE15
RTN 950A
4-ISV3-1/
6-ISV3-1
Internal
NE16
RTN 905 1E
3-ISV3-1/
Internal
GE
NE12
RTN 950A
3-ISV3-1/
5-ISV3-1/
Internal
NE11
RTN 980
17-EG2D1 /
17-EG2D-2/
Internal
BSC
Clock
Procedure
Step 1 Configure the priority of a clock source.
To configure the priority of a clock source on NE11, do as follows.
Issue 01 (2016-04-30)

570

Configuration Guide
Step 2 Query the clock synchronization status.

To query the clock synchronization status of NE11, do as follows.
Issue 01 (2016-04-30)

571

Configuration Guide
NE Clock Mode must be Normal Mode for all NEs.

Step 3 A.15.8 Querying the Clock Tracing Relationship
Generally, the clock tracing relationship is consistent with that in the network plan.
----End
14.3 Configuration Example (Clocks on a Hybrid


the BITS.
Network), configure the clocks according to the following requirements:
l
The Hybrid transmission network is synchronized with the clock of the BITS.
OptiX RTN NEs transmit clock synchronization signals through their E1/FE ports to
2G/3G base stations.
Issue 01 (2016-04-30)

572

Configuration Guide
Figure 14-3 Networking diagram (clocks on a Hybrid microwave ring network)
BITS
R4
FE
NE21
BTS21
FE
R4
E1 NE22
NE25
BTS24
BTS22
R4
NE23
NE24
BTS23

This section describes the procedure for configuring SSM to implement clock protection on a
ring network.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Clock source information
Clock protection
Standard SSM
Clock synchronization
policy for base stations
A microwave network is
synchronized with the BITS
through external clock ports,
and transmits timing
reference signals to base
stations through FE ports.

573

Configuration Guide
BITS
NE21
RTN 950A
External/
Internal
NE25
RTN 910A
NE22
RTN 905 2E
7-ISM6-2/
7-ISM6-1/
Internal
4-ISV3-1/
3-ISV3-1/
Internal
NE23
RTN 905 1E
Clock
3-ISV3-1/
7-EG6-1/
Internal
NE24
RTN 905 1E
7-EG6-1/
3-ISV3-1/
Internal
Procedure
To configure the priority of a clock source on NE21, do as follows.
Issue 01 (2016-04-30)

574

Configuration Guide
Step 2 Enable the standard SSM protocol.

To enable the standard SSM protocol on NE21, do as follows:
Issue 01 (2016-04-30)

575

Configuration Guide

To query the clock synchronization status of NE21, do as follows.
NE Clock Mode must be Tracing Mode for all NEs.

Issue 01 (2016-04-30)

576

Configuration Guide
----End
14.4 Configuration Example (Clocks on a PSN)


Based on 3.3 Packet Network, configure the clocks according to the following requirements:
l
The BSC and RNC are synchronized with an external BITS.
The PSN is synchronized with the same BITS as the BSC and RNC. The NEs on the
PSN are synchronized with an upper clock source through physical clocks (clocks from
microwave ports or clocks from Ethernet ports using the synchronous Ethernet function).
The PSN transmits clock synchronization signals through its E1/FE ports to 2G/3G base
stations.
Figure 14-4 Networking diagram (clocks on a PSN)

NE36
RTN 905 1E
NE35
RTN 950A
BTS32
FE
BTS31
R4
R4
FE
GE
NE32
RTN 980
NE33
RTN 980
NE34
RTN 980
E1
BTS33
E1
E
+G
E1
E1
NE31
RTN 950
BSC
R99
BTS34
RNC

On a packet ring, SSM is configured to implement clock protection.
Issue 01 (2016-04-30)

577

Configuration Guide
Data Preparation
Item
Planning Principles
Clock source tracing

information
Clock source priority
See the following table.
Clock protection
Standard SSM
Synchronization policy for

2G base stations
The CES retiming function

is used.
In this example, 2G base

stations need to extract
clock information through
E1 ports on the PSN.
CES retiming is the default

clock recovery solution for
PSNs and therefore does not
need to be enabled
manually.
The PSN implements the

following clock
synchronization:
l Network-wide clock
synchronization
l Synchronization between
the network-wide clock
and the service clock
Therefore, the PSN can use
the CES retiming function
for clock synchronization.
That is, the PSN extracts
system clock information
from the E1 signal
converted from a CES
service and then provides
the clock synchronization
signal through E1 ports to
base stations.
Synchronization policy for

3G base stations
Issue 01 (2016-04-30)
Synchronous Ethernet is
used.
Synchronous Ethernet is the
default clock recovery
solution for PSNs and
therefore does not need to
be enabled manually.

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

Configuration Guide
Figure 14-5 Clock source tracing information

NE36
BTS32
R4
NE35
BTS31
FE
E1
FE
R4
GE
BTS32
GE
NE32
SSM protection NE31
NE33
E1
NE34
GE
GE
E1
BTS33
E
+G
E1
E1
BSC
R99
BTS34
Clock
RNC
Table 14-2 Clock source priority table

NE31
NE32
NE31
NE34
NE35
NE36
External
clock source
1
17-EG2D-1
17-EG2D-2
17-EG2D-1
4-ISV3-1
3-ISV3-1
17-EG2D-2
17-EG2D-1
17-EG2D-2
6-ISV3-1
Internal
clock source
Internal
clock source
Internal
clock source
Internal
clock source
Internal
clock source
Internal
clock source
Procedure
Issue 01 (2016-04-30)

579

Configuration Guide
Step 2 Enable the standard SSM protocol.

Issue 01 (2016-04-30)

580

Configuration Guide

For all NEs, NE Clock Mode is Tracing Mode.

----End
Issue 01 (2016-04-30)

581

Configuration Guide
15
15 Configuring Auxiliary Ports and Functions
Configuring Auxiliary Ports and

Functions
About This Chapter

The product provides various auxiliary ports and the function of environment monitoring,
which require certain data configuration.
15.1 Auxiliary Ports and Functions
This section describes auxiliary ports and functions supported by the product, including the
orderwire, synchronous data services, asynchronous data services, wayside services, and
external alarms.
15.2 Environment Monitoring Functions
The product supports the function of monitoring environment by means of external alarms
and monitors an outdoor cabinet by means of an outdoor cabinet monitoring port.
15.3 Configuration Process (Monitoring the Outdoor Cabinet)
This section describes the process for performing parameter settings and other relevant
operations as required in the procedures for configuring the function of monitoring an outdoor
cabinet.
15.4 Configuration Example (Orderwire)
15.5 Configuration Example (Synchronous Data Services)
15.6 Configuration Example (Asynchronous Data Services)
15.7 Configuration Example (Wayside E1 Services)
Wayside E1 services apply only to SDH microwave.
15.8 Configuration Example (External Alarms)
This example uses external alarms to implement environment monitoring and centralized
control of equipment alarms.
15.9 Configuration Example (Monitoring of an Outdoor Cabinet)
Issue 01 (2016-04-30)

582

Configuration Guide
This example assumes that the outdoor cabinet monitoring port and the outdoor cabinet PMU
are correctly connected.
Issue 01 (2016-04-30)

583

Configuration Guide
15.1 Auxiliary Ports and Functions

This section describes auxiliary ports and functions supported by the product, including the
orderwire, synchronous data services, asynchronous data services, wayside services, and
external alarms.
Orderwire
OptiX RTN 910A/950/950A/980 supports one orderwire phone so that operation or
maintenance engineers at different workstations can perform voice communication through
microwave or SDH overhead bytes.
When using an orderwire phone, note the following points:
l
The orderwire phone numbers of all nodes on the network must be of the same length. A
3-digit number is recommended and all orderwire phone numbers on the entire network
must be unique.
Dual tone multiple frequency is used as the dialing method of the orderwire phone on
each node.
The call waiting time must be set to the same value for all nodes. It is recommended that
you set the call waiting time to 5s if fewer than 30 nodes exist on the orderwire subnet
and to 9s if more than 30 nodes exist on the orderwire subnet.
The product supports the orderwire group call function. When the orderwire group call
number "888" is dialed on an OptiX RTN, orderwire phones of all OptiX RTN devices
on the orderwire subnet ring. When an orderwire phone receives the call, orderwire
phones on other NEs stop ringing. In this case, the orderwire point-to-multipoint group
call changes to a point-to-point common orderwire call.
When orderwire signals are transmitted over a microwave link, they are always
transmitted through one customized overhead byte. When orderwire signals are
transmitted over SDH fibers, they are transmitted through the E1 or E2 byte.
By default, all line ports, IF ports, and unconfigured synchronous data ports on an OptiX
RTN device function as orderwire ports. Therefore, in normal cases, orderwire ports
need to be configured only at the edge of an orderwire subnet.
The equipment supports the transmission of orderwire overhead bytes through a 64 kbit/s
synchronous data port or an external clock port.
If multiple microwave links or optical transmission lines exist between two NEs, ports
corresponding to these links must be configured as orderwire ports. When Hybrid
microwave links are not used in N+1 protection, orderwire signals can be normally
transmitted between two NEs as long as one of microwave links between the two NEs is
available. When orderwire signals are transmitted over Hybrid microwave links in N+1
protection, the protection link cannot transmit orderwire signals.
For definitions of the pins on the ports, see the IDU Hardware Description.
Synchronous Data Services

The synchronous data service is also called the F1 data service. OptiX RTN 910A/
950/950A/980 supports one synchronous data service. Microwave/SDH overhead bytes
transmitted between two NEs can be used for transmitting one 64 kbit/s synchronous data
service.
Issue 01 (2016-04-30)

584

Configuration Guide
When using synchronous data services, note the following points:

l
The synchronous data service is fully transparently transmitted, and the port transmission
rate is 64 kbit/s.
The synchronous data service is clock-sensitive. If the clock is not synchronized, bit
errors occur.
Ports on the equipment comply with ITU-T G.703.
When synchronous data services are transmitted over a microwave link, they are always
transmitted over SDH fibers, they are always transmitted through the F1 byte.
The equipment supports the transmission of overhead bytes in the synchronous data
service through external clock ports to implement the service spanning function.
When the synchronous data service is transmitted over protected microwave links or
optical transmission lines, the synchronous data service is also protected.
Asynchronous Data Services

The asynchronous data service is also called a transparent data service or a broadcast data port
service. OptiX RTN 905/910A/950/950A/980 supports one asynchronous data service.
Microwave/SDH overhead bytes transmitted between two sites can be used for implementing
full-duplex communication between the universal asynchronous receiver/transmitter (UART).
When using asynchronous data services, note the following points:
l
The asynchronous data service is fully transparently transmitted. The transmission rate
and transmission control protocol do not need to be configured. The port transmission
rate is 19.2 kbit/s.
The asynchronous data service is clock-sensitive. If the clock is not synchronized, bit
errors occur.
The equipment provides RS-232 electrical ports that comply with ITU-T V.24/V.28.
The equipment supports only point-to-point communications.
When asynchronous data services are transmitted over a microwave link, they are always
transmitted over SDH fibers, they are transmitted through any of the SERIAL 1 to
SERIAL 4 bytes.
The equipment supports the transmission of overhead bytes in the asynchronous data
service through external clock ports to implement the service spanning function.
When the asynchronous data service is transmitted over protected microwave links or
optical transmission lines, the asynchronous data service is also protected.
Wayside E1 Services
The OptiX RTN 905/910A/950/950A/980 supports one wayside E1 service. The transmitted
overhead bytes in STM-1 microwave signals can be used for transmitting one wayside E1
service between two sites in one hop of STM-1 microwave link.
When using the wayside E1 service, note the following points:
Issue 01 (2016-04-30)

585

Configuration Guide
The wayside E1 service is supported by only STM-1 microwave.
The wayside E1 service is fully and transparently transmitted, and the port transmission
rate 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 pass-through of the wayside E1 service. Therefore, the
wayside E1 service can be transmitted only between two sites on one hop of microwave
link.
When the wayside E1 service is transmitted over microwave links in 1+1 or N+1
protection mode, the wayside E1 service is also protected.
The equipment adds or drops the wayside E1 service through an external clock port. The
external clock port complies with ITU-T G.703, and the impedance on the path is 120
ohms. For definitions of the pins on the ports, see the IDU Hardware Description.
15.2 Environment Monitoring Functions

The product supports the function of monitoring environment by means of external alarms
and monitors an outdoor cabinet by means of an outdoor cabinet monitoring port.
External Alarms
External alarms are also called housekeeping alarms or relay alarms.
This figure shows the port circuits for external alarm input. When the external relay is
switched off, the port circuit generates a high-level signal. When the external relay is
switched on, the port circuit generates a low-level signal. The board generates an alarm based
on the level signal. External alarm input mainly achieves access of the relay alarms generated
by the environmental alarm generator.
Figure 15-1 Circuits for external alarm input
Circuit for external
alarm input
Output level
+3.3 V/+5 V
Pull-up
resistance
External
system
Relay
The port circuit for external alarm output works in a similar manner as the external system
shown in the preceding figure. When the external alarm output conditions specified for the
NE are met, the NE drives the relay to turn on or off the switch according to the conditions
that result in the alarm. Otherwise, the NE drives the relay to change the switch to the reverse
status that results in the alarm. External alarm output helps to provide equipment alarms to the
centralized alarming device.
Issue 01 (2016-04-30)

586

Configuration Guide
Monitoring of an Outdoor Cabinet

OptiX RTN 900 supports the function of monitoring the power system and environment
variables of the following outdoor cabinets:
l
APM30H: The advanced power module with heat exchanger cooler (APM30H) cabinet
supports alternating current (AC) power input and direct current (DC) power output. It
provides a 7U space for installing user equipment.
TMC11H: The transmission cabinet of 11U high with heat exchanger (TMC11H) cabinet
supports DC power input and DC power output. It provides an 11U space for installing
user equipment.
OMB: The outdoor mini box (OMB) cabinet supports AC or DC power input. It provides
a 2U space for installing user equipment.
NOTE
For details about outdoor cabinets, see the chapter that describes outdoor cabinets in the Site
Preparationoutdoor cabinet product description.
On the NMS, an outdoor cabinet is named based on its power input mode (the naming rule applies to the
document):
l An APM30H cabinet is named APM30 AC.
l A TMC11H cabinet is named APM30 DC.
l An OMB (AC power input) cabinet is named OMB AC, and an OMB (DC power input) cabinet is
named OMB DC.
This table describes the logical slots of outdoor cabinets supported by OptiX RTN 900 and
their functions.
Table 15-1 RTN 905/910A
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

management unit of an
outdoor cabinet
TCU in slot 13: temperature
control unit of an outdoor
cabinet
control unit of the battery
compartment in an outdoor
cabinet
APM30 DC
TCU in slot 13

cabinet
OMB AC

slot 13

outdoor cabinet
cabinet
Issue 01 (2016-04-30)

587

Configuration Guide
Logical Board
Function
OMB DC
TCU in slot 13

cabinet
Logical Board
Function
APM30 AC


outdoor cabinet
Table 15-2 RTN 950/950A

cabinet
cabinet
APM30 DC
TCU in slot 15

cabinet
OMB AC
PMU in slot 14+ TCU in

slot 15

outdoor cabinet
cabinet
OMB DC
Issue 01 (2016-04-30)
TCU in slot 15


cabinet
588

Configuration Guide
Table 15-3 RTN 980

Logical Board
Function
APM30 AC


outdoor cabinet
cabinet
cabinet
APM30 DC
TCU in slot 30

cabinet
OptiX RTN 905 uses a CLK/TOD/MON port as the outdoor cabinet monitoring port.
OptiX RTN 910A/950/950A/980 provides an outdoor cabinet monitoring port on its

system control, switching, and timing board.
15.3 Configuration Process (Monitoring the Outdoor

Cabinet)
This section describes the process for performing parameter settings and other relevant
operations as required in the procedures for configuring the function of monitoring an outdoor
cabinet.
Flowchart
This figure shows the flowchart for configuring the function of monitoring an outdoor
cabinet.
Issue 01 (2016-04-30)

589

Configuration Guide
Figure 15-2 Flowchart for configuring the function of monitoring an outdoor cabinet
Required
Start
Optional
Set the function of an auxiliary port.
Set the type of the outdoor cabinet.
Set the logical boards of the outdoor

cabinet.
Set the temperature and fan

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 15-4 Configuring the function of monitoring an outdoor cabinet
Step
Operation
Remarks
A.14.6.1 Configuring the Function for an

Auxiliary Port
Required.
A.14.6.2 Setting the Type of the Outdoor

Cabinet
Required.
A.3.1.6 Configuring the Logical Board
Required.
Ensure that the configured cabinet

type is the same as the type of the
actually used outdoor cabinet.
For details about the logical slots

of outdoor cabinets and their
functions, see 15.2 Environment
Monitoring Functions.
4
Issue 01 (2016-04-30)
Configuring the
function of
monitoring an
outdoor cabinet
Setting the
temperature and fan
information of an
outdoor cabinet
Required if the temperature and fan

information of an outdoor cabinet
need to be monitored.
It is recommended that the
parameters take their default
values, unless otherwise specified.

590

Configuration Guide
Step
Operation
Remarks
Modifying
information about
the power system of
an outdoor cabinet
Required if the power system

information of an outdoor cabinet
needs to be monitored.
Setting the
temperature and
humidity alarm
thresholds for the
PMU
Required if the temperature and

humidity information of the PMU
needs to be monitored.
NOTE
Only APM30 AC cabinets and OMB
AC cabinets support this function.
OMB DC cabinets do not support
setting of parameters related to battery
groups.
NOTE
Only APM30 AC cabinets and OMB
AC cabinets support this function.
15.4 Configuration Example (Orderwire)


Each NE shown in the following networking diagram needs to be configured with the
orderwire. Only microwave links between NE1 and NE2 are configured with 1+1 protection.
Other microwave links use 1+0 non-protection.
Figure 15-3 Networking diagram (orderwire)
1+0
1+1
NE4
RTN 980
64 kbit/s
1+0
1+0
NE6
RTN 980
NE3
RTN 980
NE2
RTN 980
NE1
RTN 980
NE5
RTN 980

This section describes the procedure for configuring the orderwire.
Issue 01 (2016-04-30)

591

Configuration Guide
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Information about orderwire

phone numbers

In this example, the number
of NEs is small. Therefore,
the orderwire phone
numbers are allocated in the
format of 100 + NE ID.

592

Configuration Guide
Item
Planning Principle

ports
l In this example, services

between NE2 and NE3
are forwarded through an
E1 line. Therefore,
service spanning is
required. A 64 kbit/s
synchronous data service
port is used for service
spanning. An external
clock port can also be
used to implement
service spanning
In this case, the external
clock port needs to be
added to the orderwire
port on the NMS.
l NE2 to NE6 are located
on the orderwire subnet.
Therefore, NE2 to NE6
use the default orderwire
ports (all the IF ports,
line ports, and
unconfigured
synchronous data ports)
that are automatically
mapped by the
equipment.
l If NE1 is not located at
the edge of the orderwire
subnet, configure
orderwire ports for NE1
in the way orderwire
ports are configured for
NE2 to NE6. If NE1 is
located at the edge of the
orderwire subnet and if it
is connected to an IF port
or a line port on another
orderwire subnet, delete
the IF port or line port
from the orderwire ports
on the NMS.
Issue 01 (2016-04-30)

593

Configuration Guide
Item
Planning Principle

parameters
l Fewer than 30 NEs exist

on the orderwire subnet.
Therefore, set the call
waiting time to 5s.
l In this example, SDH

optical transmission
equipment is not
involved on the
orderwire subnet.
Therefore, set the
orderwire overhead byte
to E1 (default value).
Figure 15-4 Information about orderwire phone numbers

1+0
1+1
104
NE4
1+0
E1
NE2
NE3
1+0
NE1
101
103
NE5
NE6
102
105
106
Table 15-5 Information about orderwire ports

NE
Orderwire Port
NE1
3-ISV3-1
5-ISV3-1
NE2
3-ISV3-1
5-ISV3-1
F1
NE3
3-ISV3-1
4-ISV3-1
F1
NE4
Issue 01 (2016-04-30)
3-ISV3-1
594

Configuration Guide
NE
Orderwire Port
NE5
3-ISV3-1
4-ISV3-1
NE6
3-ISV3-1
Procedure
Step 1 Configure the orderwire.
To configure the orderwire for an NE whose NE ID is 1, do as follows.
----End
15.5 Configuration Example (Synchronous Data Services)


A network requires synchronous data services to set up data channels between two protocol
converters.
The microwave network shown in the following networking diagram needs to transmit
network information about third-party equipment. Third-party equipment and NMS use
protocol converters to convert network management messages carried by the Ethernet
network into network management messages carried by the 64 kbit/s synchronous data
service. Therefore, the microwave network needs to transparently transmit the corresponding
synchronous data only.
l
64 kbit/s synchronous data services are added or dropped on NE1 and NE6, and passed
through NE2, NE3, and NE5.
Only microwave links between NE1 and NE2 are configured with 1+1 protection. Other
microwave links use 1+0 non-protection.
Issue 01 (2016-04-30)

595

Configuration Guide
Figure 15-5 Networking diagram (synchronous data services)

Third-party
NMS
1+0
1+1
Third-party
equipment
ETH
64 kbit/s
NE4
RTN 980
1+0
1+0
NE3
RTN 980
64 kbit/s
NE2
RTN 980
NE1
RTN 980
64 kbit/s
64K/ETH
converter
NE6
RTN 980
ETH
64K/ETH
converter
NE5
RTN 980

This section describes the procedure for configuring data channels according to the
synchronous data service paths that have been planned.
Data Preparation
Item
Planning Principle
Information about
synchronous data services

In this example, the TDM
service between NE2 and
NE3 needs to be spanned
through the E1 channel. To
implement service spanning
between NE2 and NE3, the
two synchronous data ports
between NE2 and NE3 are
interconnected with each
other.
l An external clock port

can also be used to
implement service
spanning between NE2
and NE3.
l In the case of microwave
links or SDH optical
transmission lines
configured with 1+1
protection, only the main
link is configured with
synchronous data
services.
Table 15-6 Information about synchronous data services
Issue 01 (2016-04-30)
NE
Data Channel
NE1
F1
3-ISV3-1
NE2
3-ISV3-1
F1
NE3
F1
4-ISV3-1
NE5
4-ISV3-1
3-ISV3-1
NE6
3-ISV3-1
F1

596

Configuration Guide
Procedure
Step 1 Configure synchronous data services.
To configure synchronous data services for NE1, do as follows.
----End
15.6 Configuration Example (Asynchronous Data Services)


A network requires asynchronous data services to set up data channels between two protocol
converters.
The microwave network shown in the following networking diagram needs to transmit
network information about third-party equipment. Third-party equipment and NMS use
protocol converters to convert network management messages carried by the Ethernet
network into network management messages carried by the RS-232 asynchronous data
service. Therefore, the microwave network needs to transparently transmit the corresponding
asynchronous data only.
l
Asynchronous data services are added or dropped on NE1 and NE6, and passed through
NE2, NE3, and NE5.
Only microwave links between NE1 and NE2 are configured with 1+1 protection. Other
microwave links use 1+0 non-protection.
Issue 01 (2016-04-30)

597

Configuration Guide
Figure 15-6 Networking diagram (asynchronous data services)

Third-party
NMS
1+0
1+1
Third-party
equipment
ETH
RS-232
NE4
RTN 980
1+0
1+0
NE3
RTN 980
NE2
RTN 980
RS-232
NE1
RTN 980
ETH
RS-232/ETH
converter
RS-232
RS-232/ETH
converter
NE6
RTN 980
NE5
RTN 980

This section describes the procedure for configuring broadcast data sources and broadcast
data sinks according to asynchronous data service paths that have been planned.
Data Preparation
Item
Planning Principle
Information about
asynchronous data services

In this example, the TDM
service between NE2 and
NE3 needs to be spanned
through the E1 channel. To
implement service spanning
between NE2 and NE3, the
two asynchronous data ports
between NE2 and NE3 are
interconnected with each
other.
l An external clock port

can also be used to
implement service
spanning between NE2
and NE3.
Set the overhead byte to

SERIAL1.
l In the case of microwave

links or SDH optical
transmission lines
configured with 1+1
protection, only the main
link is configured with
asynchronous data
services.
Table 15-7 Information about asynchronous data services
Issue 01 (2016-04-30)
NE
Broadcast Data Source
Broadcast Data Sink
NE1
SERIAL1
3-ISV3-1
NE2
3-ISV3-1
SERIAL1
NE3
SERIAL1
4-ISV3-1
NE5
4-ISV3-1
3-ISV3-1
NE6
3-ISV3-1
SERIAL1

598

Configuration Guide
Procedure
Step 1 Configure asynchronous data services.
To configure asynchronous data services for NE1, do as follows.
----End
15.7 Configuration Example (Wayside E1 Services)

Wayside E1 services apply only to SDH microwave.

A network requires wayside E1 services to set up data channels between two protocol
converters.
On the microwave network shown in the following networking diagram, the STM-1
microwave link between NE1 and NE2 needs to transmit network information about thirdparty equipment. Third-party equipment and NMS use protocol converters to convert network
management messages carried by the Ethernet network into network management messages
carried by the wayside E1 service. NEs transmit network management messages over the
wayside E1 channel to maximize the bandwidth utilization.
Figure 15-7 Networking diagram (wayside E1 services)
Third-party
NMS
Third-party
equipment
3-ISV3 to NE1
ETH
E1/ETH
converter
Issue 01 (2016-04-30)
E1
3-ISV3 to NE2
E1
STM-1
NE2
RTN 980
NE1
RTN 980

ETH
E1/ETH
converter
599

Configuration Guide

The input slot of wayside E1 services is the slot of the system control, switching, and timing
board.
Data Preparation
Item
Planning Principle
Information about wayside

E1 services
In the case of microwave

links configured with 1+1 or
N+1 protection, only the
active link is configured
with wayside E1 services.
Table 15-8 Information about wayside E1 services

NE
IF Board
Whether to
Enable Wayside
E1 Services
Input Slot of
Wayside E1
Services (Slot of
the System
Control,
Switching, and
Timing Board)
NE1
3-ISV3
Enabled
15
NE2
3-ISV3
Enabled
15
Procedure
Step 1 Configure wayside E1 services.
To configure wayside E1 services on NE1, do as follows.
----End
Issue 01 (2016-04-30)

600

Configuration Guide
15.8 Configuration Example (External Alarms)

This example uses external alarms to implement environment monitoring and centralized
control of equipment alarms.

A network monitors alarms reported by monitoring sensors using alarm input ports and
reports alarms to a centralized alarming box through an alarm output port.
The following figure shows external alarm requirements of NE1:
l
External alarm input port 1 is connected to the alarm port on the smoke sensor. When the
alarm port on the smoke sensor is closed, NE1 reports a fire alarm.
External alarm input port 2 is connected to the alarm port on the water sensor. When the
alarm port on the water sensor is closed, NE1 reports a water alarm.
External alarm input port 3 is connected to the alarm port on the magnetic door switch
sensor. When the alarm port on the magnetic door switch sensor is closed, NE1 reports
an alarm, indicating that the cabinet door is open.
External alarm output port 1 is connected to a centralized alarming box. When a major or
critical alarm is generated on NE1, the alarm output port is closed.
Figure 15-8 Networking diagram (external alarms)
4-AUX
Input 1
Smoke sensor
Input 2
Water sensor Input 3
NE1 Output 1
RTN 980
Integrated
alarm box
Door status switch

sensor

This section describes the procedure for configuring input alarms according to sensor
requirements.
Data Preparation
Issue 01 (2016-04-30)
Item
Planning Principle
Information about input/

output alarms

601

Configuration Guide
Table 15-9 Information about input alarms

Input
External
Alarm
Channel
Name
Usage Status
Alarm Mode
Severity
Port 1
Fire alarm
Used
An alarm is
generated when
the port is
closed
Critical
Port 2
Water alarm
Used
An alarm is
generated when
the port is
closed
Critical
Port 3
Open cabinet
door
Used
An alarm is
generated when
the port is
closed
Critical
Table 15-10 Information about output alarms

Input External Alarm
Usage Status
Port 1
Used
Procedure
Step 1 Configure external alarms.
Issue 01 (2016-04-30)

602

Configuration Guide
----End
15.9 Configuration Example (Monitoring of an Outdoor

Cabinet)
This example assumes that the outdoor cabinet monitoring port and the outdoor cabinet PMU
are correctly connected.

This section uses an OptiX RTN 905 as an example to describe how to install an OptiX RTN
device in an APM30 DC cabinet.
Issue 01 (2016-04-30)

603

Configuration Guide
As shown in this figure, the CLK/TOD/MON port on the OptiX RTN 905 is connected to the
COM_IN port in the APM30 DC cabinet. The OptiX RTN 905 supports the function of
monitoring the PMU temperature and humidity after the upper and lower thresholds for
temperature and humidity alarms of the PMU are configured.
Figure 15-9 Networking diagram (an OptiX RTN 905 outdoor cabinet)
PMU
COM_IN
IDU
CLK/TOD/
MON

This section describes the procedure for monitoring an APM30 DC outdoor cabinet.
Data Preparation
Item
Planning Principles
Outdoor cabinet monitoring

port mode
1-CSHP-1: External clock

(Hz mode) + outdoor
cabinet (default value)
Outdoor cabinet type
APM30 AC
Alarm thresholds for the

PMU
Default value
Generally, default values are

recommended.
Procedure
Step 1 Query the CLK/TOD/MON port mode and ensure that the External clock (Hz mode) +
outdoor cabinet mode is used.
Issue 01 (2016-04-30)

604

Configuration Guide
Step 2 Configure the type of the outdoor cabinet.
Issue 01 (2016-04-30)

605

Configuration Guide
Step 3 Add PMU and TCU boards.

1
Step 4 In this example, the default PMU alarm thresholds are used. If the thresholds need to be
changes, follow instructions in A.14.6.6 Setting the Temperature and Humidity Alarm
Thresholds for the PMU.
----End
Issue 01 (2016-04-30)

606

Configuration Guide
16
16 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.
16.1 Common Task Collection (Network Topology)
This section describes common tasks such as NE creation and NE ID modification.
16.2 Common Task Collection (Radio Links)
This section describes common tasks such as changing the transmit power and changing the
transmit power.
16.3 Common Task Collection (TDM Services)
This section describes common tasks such as adding TDM services and deleting TDM
services.
16.4 Common Task Collection (Native Ethernet Services)
This section describes common tasks such as creating Native Ethernet services and deleting
Native Ethernet services.
16.5 Common Task Collection (Ethernet Services on the EoS/EoPDH Plane)
This section describes common tasks such as creating Ethernet services and deleting Native
Ethernet services on the EoS/EoPDH plane.
16.6 Common Task Collection (MPLS/PWE3 Services)
This section describes common tasks such as adding/deleting MPLS tunnels and adding/
deleting PWE3 services.
Issue 01 (2016-04-30)

607

Configuration Guide
16.1 Common Task Collection (Network Topology)

This section describes common tasks such as NE creation and NE ID modification.
Table 16-1 Common task collection (Network Topology)
Issue 01 (2016-04-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.3.1.1 Creating NEs

by Using the Search
Method (U2000) or A.
3.1.3 Creating NEs by
Using the Manual
Method (U2000)
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.3.1.9 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.3.1.12
Synchronizing the NE
Time (U2000)
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.
608

Configuration Guide
16.2 Common Task Collection (Radio Links)

This section describes common tasks such as changing the transmit power and changing the
transmit power.
NOTICE
When you add or modify the configurations of a radio link, you need to modify the
configurations of the NE that is located far from the NMS server and then modify the
configurations of the NE that is located near to the NMS server.
NOTE
l For 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main radio
link.
l For 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the
ODU information of the standby radio link.
l Before configuring XPIC workgroups, you need to set IF Service Type separately for IF boards in
the vertical polarization and those in horizontal polarization.
l For N+1 protection, you need to configure the IF/ODU information of the N+1 radio links
respectively.
l The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot
enabled status, STM-1 count, or modulation mode is set inconsistently for both ends of an Integrated
IP microwave link. This alarm should be cleared immediately. Otherwise, services may be
configured unsuccessfully or interrupted.
Table 16-2 Common task collection (radio links)

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.
A.8.10.9
Modifying the
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 01 (2016-04-30)

609

Configuration Guide
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.7.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.
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.
A.5.1
Configuring a
Single-Hop
Radio Link
If the capacity of the

existing TDM services
exceeds the capacity of the
TDM radio link after the
change, you need to delete
the cross-connections of
the excessive TDM
services.
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.
Issue 01 (2016-04-30)
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.
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.
In Power Attributes of the

ODU, change TX
Power(dBm) or parameter
values associated with
power.

610

Configuration Guide
Issue 01 (2016-04-30)
Task
Application
Scenario
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.
Configuration
Operation

Description
For IF 1+1 protection, the
original IF board functions
as the main IF board.
Ensure that TX Status of
the standby ODU is
Unmute.
611

Configuration Guide
Task
Application
Scenario
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.
Configuration
Operation
Description
l To reduce E1s with
high priorities, you
need to delete the
corresponding crossconnections 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 crossconnections 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 crossconnections before
changing Full E1
Capacity. The change
does not affect other E1
services or cause
Ethernet service
interruptions.
l To increase E1s with
low priorities, you need
to add the
corresponding crossconnections after
changing Full E1
Capacity. The change
does not affect other E1
services or cause
Ethernet service
interruptions.
Issue 01 (2016-04-30)

612

Configuration Guide
Task
Application
Scenario
Configuration
Operation
Description
NOTE
The number of added
E1s should be within the
specified range.
l The
MW_CFG_MISMATC
H 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
link.
16.3 Common Task Collection (TDM Services)

This section describes common tasks such as adding TDM services and deleting TDM
services.
Table 16-3 Common task collection (TDM services)
Issue 01 (2016-04-30)
Task
Application
Scenario
Configuration
Operation
Description
Adding TDM
services
More TDM services

need to be accessed on
the network.
A.7.1 Creating the

Point-to-Point Services
or A.7.2 Creating
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.7.6 Deleting CrossConnections

613

Configuration Guide
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.6.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.7.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 crossconnections from the
SNCP services to the
working trail and
from the SNCP
services to the
protection trail so
that the normal
services both in the
receive direction and
in the transmit
direction are
converted to SNCP
services.
16.4 Common Task Collection (Native Ethernet Services)

This section describes common tasks such as creating Native Ethernet services and deleting
Native Ethernet services.
Table 16-4 Common task collection (Native Ethernet services)
Issue 01 (2016-04-30)
Task
Application
Scenario
Configuration Operation
Description
Creating
Ethernet
services
Create the Ethernet

services according to
the service planning
information.
8 Configuring Native
Ethernet Services

614

Configuration Guide
Task
Application
Scenario
Description
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.8 Setting Ethernet Port

Parameters
Deleting
Ethernet
services
Delete the Ethernet

services that are not
used to release the
corresponding
resources.
A.9.3.23 Deleting an E-Line

Service or A.9.3.24 Deleting
E-LAN Services
Creating a
LAG
l When the available

bandwidth is
insufficient, you
can create a LAG
to increase the
bandwidth.
A.9.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.
Changing
logical ports
connected to
an E-LAN
Issue 01 (2016-04-30)
The E-LAN service

requirements change.
As a result, the logical
ports connected to the
E-LAN need to be
changed.
l This
operation
briefly
interrupts
the existing
services.
A.9.3.22 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.
615

Configuration Guide
Task
Application
Scenario
Description
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.9.4 Managing the MAC

Address Table
A.9.8 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
The service
As a result, QoS needs
to be adjusted.
16.5 Common Task Collection (Ethernet Services on the

EoS/EoPDH Plane)
This section describes common tasks such as creating Ethernet services and deleting Native
Ethernet services on the EoS/EoPDH plane.
NOTE
OptiX RTN 905/910A does not support the configuration of Ethernet services on EoS/EoPDH boards.
Issue 01 (2016-04-30)

616

Configuration Guide
Table 16-5 Common task collection (Ethernet services on the EoS/EoPDH plane)
Task
Application
Scenario
Remarks
Creating
Ethernet
services
Create the Ethernet

services according to
the service planning
information.
9 Configuring Ethernet
Services on EoS/EoPDH
Boards
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.10.5 Configuring Ethernet

Ports
Deleting
Ethernet
services
Delete the Ethernet

services that are not
used to release the
corresponding
resources.
A.10.3.7 Deleting an
Ethernet Private Line
Service or A.10.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.10.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 01 (2016-04-30)

l This
operation
briefly
interrupts
the existing
services.
617

Configuration Guide
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.
A.10.3.3 Changing the Ports

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.10.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 01 (2016-04-30)
The service
As a result, QoS needs
to be adjusted.

618

Configuration Guide
16.6 Common Task Collection (MPLS/PWE3 Services)

This section describes common tasks such as adding/deleting MPLS tunnels and adding/
deleting PWE3 services.
Table 16-6 Common task collection (MPLS services)
Task
Application
Scenario
Description
Adding
unprotected
MPLS
tunnels
Add unprotected
MPLS tunnels
according to the
service plan.
A.11.2.4 Creating a
Unidirectional MPLS Tunnel
or A.11.2.5 Creating a
Bidirectional MPLS Tunnel
Adding
MPLS
tunnels with
MPLS APS
protection
Add MPLS tunnels

with MPLS APS
protection according to
the service plan.

Deleting
MPLS
tunnels
Delete MPLS tunnels

that will no longer
carry services to
release resources.
A.11.2.8 Deleting MPLS

Tunnels
Creating
MPLS APS
protection
groups
Create MPLS APS

protection groups to
improve the reliability
of service transmission
over tunnels.
A.11.3 Managing MPLS APS

Protection Groups
When creating
an MPLS APS
protection
group, set
Protocol
Status to
Disabled. Start
the protocol
after an MPLS
APS protection
group has been
created on the
NEs at both
ends.
Table 16-7 Common task collection (CES services)
Issue 01 (2016-04-30)
Task
Application
Scenario
Description
Adding CES
services
Add CES services

according to the
service plan.
A.11.6.1 Creating CES

Services
l If new CES
services are
carried by
PCM

619

Configuration Guide
Issue 01 (2016-04-30)
Task
Application
Scenario
Description
Modifying
CES services
Modify CES services

according to the new
service plan.
A.11.6.2 Modifying CES

Service Parameters
timeslots,
set PW
Type to
CESoPSN.
If new CES
services are
not carried
by PCM
timeslots,
set PW
Type to
SAToP.
l If new CES
services are
carried by
fractional
E1s, set
PW Type
to
CESoPSN.
If Frame
Mode is set
to 30 for
PDH ports,
Source
64K
Timeslot
(e.g.1,3-6)
must
include
timeslot 16.
Deleting CES
services
Delete CES services

that will no longer be
used to release
resources.
A.11.6.4 Deleting a CES

Service.

620

Configuration Guide
Table 16-8 Common task collection (ETH PWE3 services)

Task
Application
Scenario
Description
Creating
LAGs
l Create LAGs to
increase bandwidth.
l When
creating a
LAG,
configure
the port that
already
carries
services as
the main
port.
l Create LAGs to
improve link
reliability.
l This
operation
causes a
transient
service
interruption
.
Issue 01 (2016-04-30)
Creating
UNI-NNI ELine services
carried by
PWs
Create UNI-NNI ELine services

according to the
service plan.
A.9.3.9 Configuring UNINNI E-Line Services

(Carried by PWs)(U2000)
Deleting
UNI-NNI ELine services
carried by
PWs
Delete UNI-NNI ELine services that will

no longer be used to
release resources.
A.9.3.23 Deleting an E-Line

Service
Adjusting
QoS settings
Adjust QoS settings

when service
Modify QoS
parameters to
adapt the QoS
to the service
requirement
changes.

621

Configuration Guide
Table 16-9 Common task collection (ATM PWE3 services)

Task
Application
Scenario
Description
Creating and
configuring
serial ports
Create and configure

serial ports when
fractional ATM/IMA
services need to be
used.
A.8.7 Setting Serial Port

Parameters
l Set Level to
64K
Timeslot.
When the
E1 frame
mode is 30,
timeslot 0
and
timeslot 16
are
unavailable.
When the
E1 frame
mode is 31,
timeslot 0 is
unavailable.
l Set Port
Type to
Layer 2.
l Set
Encapsulat
ion Type to
ATM.
Issue 01 (2016-04-30)

622

Configuration Guide
Task
Application
Scenario
Description
Binding ATM
trunks
l Add/Delete ATM
trunks according to
the service plan.
A.11.7.1 Binding ATM

TRUNKs
l Set
Available
Boards and
Configura
ble Ports
according
to the
service
plan.
l Add/Delete slots/
timeslots bound to
ATM trunks
according to the
service plan.
l Set Level
for the
paths that
can be
bounded,
based on
the service
type. If the
service type
is
ATM/IMA
E1, set
Level to
E1. If the
service type
is fractional
ATM/IMA,
set Level to
Fractional
E1.
l Set
Available
Resources
and
Available
Timeslots
according
to the
service
plan. For
ATM/IMA
E1 services,
select the
E1 ports to
be bound in
Available
Resources.
For
fractional
Issue 01 (2016-04-30)

623

Configuration Guide
Task
Application
Scenario
Description
ATM/IMA
services,
select the
ports to be
bound in
Available
Resources
and the
timeslots to
be bound in
Available
Timeslots.
Issue 01 (2016-04-30)

624

Configuration Guide
Task
Application
Scenario
Description
Managing
IMA groups
l Add/Delete
members of IMA
groups according to
the service plan.
A.11.7.2 Configuring an
IMA group
l Set IMA
Protocol
Status.
l Change the status

of IMA groups
according to the
service plan.
For ATM
E1 and
fractional
ATM, set
IMA
Protocol
Status to
Disabled.
For IMA
E1 and
fractional
IMA, set
IMA
Protocol
Status to
Enabled.
l Set IMA
Protocol
Version.
This
parameter
must be set
to the same
value for
the local
end and the
peer end.
l It is
recommend
ed that you
set other
parameters
such as
IMA
Transmit
Frame
Length and
IMA
Symmetry
Mode to
the default
values.
Issue 01 (2016-04-30)

625

Configuration Guide
Task
Application
Scenario
Description
Managing
ATM ports
Manage ATM port

parameters such as
ATM trunk port type,
ATM cell payload
scrambling, and
loopback mode.
A.11.7.3 Setting ATM Port

Parameters
l Set Port
Type and
ATM Cell
Payload
Scramblin
g according
to the type
of access
equipment.
It is
recommend
ed that you
set the
parameters
to the
default
values.
l Retain the
default
values for
the other
parameters.
Issue 01 (2016-04-30)
Configuring
ATM QoS
Configure/Modify
ATM policies and DS
domains according to
the service plan.
A.11.9 ATM Traffic

Management
Configuring
ATM services
Create ATM services

and PWs for carrying
the ATM services.
A.11.8.1 Creating ATM

Services

626

Configuration Guide
A Task Collection
Task Collection
This document describes various tasks involved in this document.

A.1 U2000 Quick Start
The U2000 quick start guide helps to learn about basic operations on the U2000client.
A.2 Web LCT Quick Start
The Web LCT quick start guide helps to learn about basic operations on theWeb LCT.
A.3 Network Management
Network management involves topology management, communication management, and
security management.
A.4 Security Management
Security management is important in network management.
A.5 Managing Radio Links
Before you configure the radio link between two microwave sites, configure the information
about the radio link.
A.6 Managing the MSP
This section provides the operation tasks associated with MSP. Only the OptiX RTN 980
supports the Two-Fiber Bidirectional Ring MSP.
A.7 Managing TDM Services
The TDM services involve the SDH service and the PDH service.
A.8 Managing Ports
Setting correct port parameter is the basis of configuring ports that transmit services.
A.9 Configuring Native Ethernet Services and Features
Configurations of Native Ethernet services and features include Ethernet port, protection,
service, protocol, and OAM configurations.
A.10 Configuring Ethernet Services and Features on the EoS/EoPDH Boards
Configurations of Ethernet services and features on the EoS/EoPDH boards include relevant
Ethernet port configuration, protection configuration, service configuration, protocol
configuration, and OAM configuration.
A.11 Managing MPLS/PWE3 Services and Features
The OptiX RTN 900 supports multiple MPLS/PWE3 services and features.
A.12 Managing the Clock
Issue 01 (2016-04-30)

627

Configuration Guide
A Task Collection
To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.13 Ethernet Performance Query
This section describes operations related to Ethernet performance query.
A.14 Configuring Auxiliary Ports and Functions
The NE supports auxiliary ports and functions such as asynchronous data service port,
wayside service port, external alarm port, and outdoor cabinet monitoring port.
A.15 End-to-End Configuration Task Collection
End-to-end configuration is simpler than per-NE configuration.
Issue 01 (2016-04-30)

628

Configuration Guide
A Task Collection
A.1 U2000 Quick Start

The U2000 quick start guide helps to learn about basic operations on the U2000client.
A.1.1 Logging in to a U2000 Client

The U2000 uses the client/server architecture and allows multiple clients; you can log in to
the U2000 server by means of a U2000 client to manage OptiX RTN NEs.
Prerequisites
l
The U2000 system has been started on the U2000 server.
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
NOTE
The Web LCT does not support this operation.
Procedure
Step 1 Double-click the U2000 client icon on the desktop.
Step 2 In the Login dialog box, set User Name and Password.
Step 3 Select the desired U2000 server from the Server drop-down list.
Step 4 Click Login.
The Legal Statement dialog box is displayed.
Step 5 Click Agree.
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
Issue 01 (2016-04-30)

629

Configuration Guide
A Task Collection
NOTE
Procedure
Step 1 Choose File > Exit from the Main Menu.
The Confirm dialog box is displayed.
Step 2 Click OK to shut down the U2000 client.
NOTE
If the main topology has changed but the changes have not been stored, a dialog box will be displayed
asking whether to update the main topology. The U2000 client is shut down after you determine whether
to update the main topology.
----End
A.1.3 Using Online Help

Online Help provides help information about the U2000.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose Help > Help Topics from the Main Menu.
The Online Help page is displayed.
NOTE
When using the U2000client, press the F1 key to quickly display the related Online Help page.
----End
Issue 01 (2016-04-30)

630

Configuration Guide
A Task Collection
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
NOTE
Procedure
Step 1 Choose View > Main Topology from the Main Menu, or double-click the Main Topology
icon in Workbench.
The Main Topology view is displayed.
Step 2 Optional: Choose View > Display Settings > Filter from the Main Menu.
The Filter tab page is displayed on the right of the main topology.
NOTE
To quickly navigate to the Main Topology view, click
----End
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

U2000
NOTE
Issue 01 (2016-04-30)

631

Configuration Guide
A Task Collection
Procedure
Step 1 Optional: In Main Topology, double-click the subnet to which the NE belongs.
Step 2 In Main Topology, right-click the icon of the desired NE and choose NE Explorer from the
shortcut menu.
The NE Explorer view is displayed.
NOTE
l To quickly navigate to NE Explorer, click
l To quickly navigate to the NE Panel view, click

l To quickly navigate to Online Help, click
----End
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
NOTE
Procedure
Step 1 Optional: In Main Topology, double-click the subnet to which the NE belongs.
Step 2 Double-click the icon of the desired NE in Main Topology.
NE Panel is displayed.
NOTE
l To quickly navigate to the NE Explorer view, click

l To quickly synchronize the NE time, click
----End
A.2 Web LCT Quick Start

The Web LCT quick start guide helps to learn about basic operations on theWeb LCT.
Issue 01 (2016-04-30)

632

Configuration Guide
A Task Collection
A.2.1 Using Online Help

Online Help provides help information about the Web LCT.
Prerequisites

Web LCT
NOTE
The U2000 does not support this operation.
Procedure
Step 1 In NE List, click
The Online Help page is displayed.

NOTE
When using the Web LCT, press the F1 key to quickly display the related Online Help page.
----End
A.2.2 Navigating to the NE Explorer

The Web LCT provides the NE Explorer view to support users' management on equipment.
The NE Explorer view consists of the Function Tree pane, the Object Tree pane, and the
configuration interface.
Prerequisites

Web LCT
NOTE
The U2000 does not support this operation.
Procedure
Step 1 In NE List, select the NE to which you are logged in and click NE Explorer at the lower
right corner.
The NE Explorer view is displayed.
Issue 01 (2016-04-30)

633

Configuration Guide
A Task Collection
NOTE
l To quickly navigate to the view displaying current alarms, click

l To quickly navigate to the NE List view, click
l To quickly navigate to Online Help, click
.
.
NOTE
You can also navigate to the NE Explorer view using the following methods:
l In NE List, right-click the NE to which you are logged in and choose NE Explorer from the shortcut
menu.
l In NE List, double-click the NE to which you are logged in.
----End
A.3 Network Management

Network management involves topology management, communication management, and
security management.
A.3.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS.
A.3.1.1 Creating NEs by Using the Search Method (U2000)

The U2000 can find all NEs that communicate with a specific gateway NE by using the IP
address of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses.
In addition, the U2000 can create the NEs that are found in batches. Compared with the
method of manually creating NEs, this method is faster and more reliable.
Prerequisites
l
The NMS must have proper communication with NEs.

U2000
Procedure
Step 1 Choose File > Discovery > NE from the Main Menu.
Step 2 Select Transport NE Search tab.
Step 3 Select Search Mode.
Issue 01 (2016-04-30)

634

Configuration Guide
A Task Collection
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
3.
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.
The factory default user name is root, and its corresponding password is Changeme_123. If you
have changed the password, log in to the NE using the correct password.
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.
Issue 01 (2016-04-30)

635

Configuration Guide
A Task Collection
NOTE
The factory default user name is root, and its corresponding password is Changeme_123. If you have
changed the password, log in to the NE using the correct 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
A.3.1.2 Creating NEs by Using the Search Method (Web LCT)

The Web LCT can find all NEs that communicate with a specific gateway NE by using the IP
address of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses.
In addition, the Web LCT can create the NEs that are found in batches. Compared with the
method of manually creating NEs, this method is faster and more reliable.
Prerequisites
l
The NMS must have proper communication with NEs.
Issue 01 (2016-04-30)

636

Configuration Guide
A Task Collection

Web LCT
Procedure
Step 1 Click NE Search in NE List and select a desired search type.
If...
Then...
All NEs are directly connected to the NMS server through

Ethernet cables
Not all NEs are directly connected to the NMS server

through Ethernet cables
Step 2 Select NE Search.

The Search NE dialog box is displayed.
NOTE
The default user name is lct, and its corresponding password is Changeme_123.
Step 3 Set Local IP Address based on the network planning information.

NOTE
Local IP Address indicates the IP address of an Ethernet port on the NMS server. There may be multiple
Local IP Address values because an NMS server may have multiple network adapters.
Step 4 Set NE IP Address based on the network planning information.

NOTE
NE IP Address indicates the IP addresses of all NEs (searched out by the system automatically) that are
connected to the NMS server directly through Ethernet cables.
Step 5 Click OK.

NOTE
When NE Search is selected, the system can directly log in to NEs. You do not need to enter the user
name and password.
Step 6 Select Advanced Search.

The Search NE dialog box is displayed.
Step 7 Optional: If you select IP auto discovery, then:
1.
Issue 01 (2016-04-30)
Click Search.
637

Configuration Guide
2.
A Task Collection
After the Web LCT finds the NEs to be managed, click End Search.
NOTE
In the IP auto discovery mode, the Web LCT searches for the gateway NE and non-gateway NEs that are
managed by the gateway NE in the network segment where the server resides.
Step 8 Optional: If you select Search NE, then:

1.
Click Manage Domain.

The Manage Domain Search dialog box is displayed.
2.
Optional: Click Add to add a network segment. Then, set Domain Type and Domain
Address.
3.
Optional: Select an existing network segment and click Modify to modify the network
segment.
4.
Optional: Select an existing network segment and click Delete to delete the network
segment.
5.
Click Search.
6.
After the WebLCT finds the NEs, click End Search.

NOTE
During initial configuration, Manage Domain takes the default value of 129.9.255.255. After the IP
address of the gateway NE is changed, the value of Manage Domain also needs to be changed. The
default network segment cannot be modified or deleted.
Step 9 Select the NE that needs to be added and click Add NE.
A dialog box is displayed, indicating that the NE is added successfully.
Step 10 Click OK.
A new NE has been added to the NE list.
Step 11 Click Cancel.

----End
A.3.1.3 Creating NEs by Using the Manual Method (U2000)

You can only create NEs one by one by using the manual method. The manual method, unlike
the search method, does not allow creating NEs in batches.
Prerequisites
l
The NMS must have proper communication with the NE to be created.
Issue 01 (2016-04-30)

638

Configuration Guide
A Task Collection
If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be

created belongs must be created.

U2000
Procedure
Step 1 Choose File > New > NE from the Main Menu.
The Create NE dialog box is displayed.
Step 2 Choose RTN Series from the Object Tree and select a desired product.
Step 3 Enter the following information: ID, Extended ID, Name, and Remarks.
Step 4 Set Gateway Type for the NE.
If...
Then...
The Gateway Type parameter is set to

Gateway
Proceed to the next step.
The Gateway Type parameter is set to NonGateway
Select the gateway to which the NE

belongs, and go to Step 6.
Step 5 Specify the protocol and IP address that the NE uses.

Protocol parameter is set to IP. Enter the IP Address of the NE.
NOTE
Security SSL is recommended for communication.
Issue 01 (2016-04-30)

639

Configuration Guide
A Task Collection
Step 6 Specify NE User and Password.

The default user name is root and the default password is Changeme_123.
Step 7 Click OK.
Step 8 Click the Main Topology.
The icon of the NE is displayed at the cursor position.
----End
A.3.1.4 Creating NEs by Using the Manual Method (Web LCT)

You can only create NEs one by one by using the manual method. The manual method, unlike
the search method, does not allow creating NEs in batches.
Prerequisites
l
The NMS must have proper communication with the NE to be created.
If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be

created belongs must be created.

Web LCT
Procedure
Step 1 In NE List, click Add NE. Then, select Europe.
Step 2 Set the NE parameters.
NOTE
l The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.

l ID indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique on the
networks that are managed by the same NMS.
l Do not change the Extended ID when the number of actual NEs does not exceed the range permitted by
the basic NE ID.
l Set the parameters according to the network plan.
l The default user name is lct, and its corresponding password is Changeme_123.
Issue 01 (2016-04-30)

640

Configuration Guide
A Task Collection
NOTE
l SSL is recommended for communication with NEs. Set the port number to 5432 and perform the
following steps to replace the SSL certificate:
1. a. Delete the WebLCT\conf\certificate directory on the Web LCT.
2. Copy the server\etc\ssl\nemanager\default directory on the U2000 to the path WebLCT\conf on the
Web LCT. Rename default to certificate. Note that the installation path on the Web LCT should not
contain Chinese characters, spaces, or special characters.
3. c. Restart the Web LCT.
l Install the SSL certificate to the NE using the U2000. For details, see the Security Configuration
Maintenance & Hardening.
Step 3 Click OK.

A new NE is already added to the NE list.
----End
A.3.1.5 Logging In to an NE (Web LCT)

After an NE is created, you need to log in to the NE before managing the NE.
Prerequisites
l
The NE to be managed is already created in NE List.

Web LCT
Procedure
Step 1 In the NE List, select the target NE and click NE Login.
NOTE
You can select multiple NEs at one time.
The NE Login dialog box is displayed.

Step 2 Enter User Name and Password. Then, click OK.
Issue 01 (2016-04-30)

641

Configuration Guide
A Task Collection
NOTE
l The default User Name is lct.

l The default Password for user lct is Changeme_123.
Login Status of the NE in the NE List changes to Logged In. Alarm Status of the NE is
changed from Unknown to the current alarm status of the NE.
Step 3 Click NE Explorer.
The NE Explorer is displayed.
NOTE
l To quickly start the NE Explorer, double-click the NE to be managed in the NE list.

l Check the legend to learn the specific meanings of different colors and symbols in the slot layout
diagram.
l Click
to collapse/expand the legend.
----End
A.3.1.6 Configuring the Logical Board

If the logical board corresponding to the physical board is not added in the slot layout, add the
logical board in the slot layout. If the physical board is inconsistent with the logical board in
the slot layout, delete the inconsistent logical board and add the correct logical board.
Prerequisites
l
All the boards must be installed correctly.

U2000
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Double-click the NE icon to open the NE layout diagram.
Based on the slot layout, the NE automatically configures the logical boards that are required
but still not be configured for certain physical boards.
NOTE
If you configure the logical board using the Web LCT, perform the following operations:
Click the Slot Layout tab and click Add Physical Boards.
Step 2 Optional: On the slot to which the board is to be added, right-click, and then choose Add
XXX.
NOTE
XXX is the name of the board to be added.
Issue 01 (2016-04-30)

642

Configuration Guide
A Task Collection
Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then choose Delete.
1.
In the displayed confirmation dialog box, click OK.
2.
In the dialog box that is displayed again for confirmation, click OK.
NOTE
Before deleting the board, delete the data, such as the service, clock, and protection, on the board.
Before configuring the COMBO port on an OptiX RTN 905 to function as a GE port, delete the VS2
logical board and add the EG2 logical board.
For OptiX RTN 950A that houses an MN1 board, delete the logical boards SP3S and SL1D integrated
on the CSHO before configuring the logical boards MP1 and CD1 respectively. In this manner, ports on
the logical boards MP1 and CD1 can be configured as Smart E1 ports and channelized STM-1 ports.
----End
A.3.1.7 Configuring an SFP Port

For a port that supports multiple SFP module types, perform this task to set the type of the
SFP module to be installed on the port. If the port has no SFP module, perform this task to
delete the port on the NMS to prevent the NMS from reporting alarms related to SFP
modules.
Prerequisites
l
All the boards and their SFP modules have been installed correctly.

U2000
NOTE
Issue 01 (2016-04-30)

643

Configuration Guide
A Task Collection
Context
The following table lists the boards and the supported SFP module types.
Table A-1 RTN 910A
Board
Supported SFP Module Type
EG6
FE optical module
GE optical module
GE electrical module
EG4/EG4P
FE optical module
GE optical module
SL1DA/CQ1
STM-1 optical module

STM-1 electrical module
Table A-2 RTN 905

Board
EG6
FE optical module
GE optical module
CD1

EG2
FE optical module
GE optical module
Table A-3 RTN 950

Board
EM6F/EM6FA
FE optical module
GE optical module
EMS6
GE optical module
SL1D/SL1DA/CQ1

Issue 01 (2016-04-30)

644

Configuration Guide
A Task Collection
Board
EG4/EG4P/EM6D
FE optical module
GE optical module
Table A-4 RTN 950A

Board
EM6F/EM6FA
FE optical module
GE optical module
EMS6
GE optical module
SL1DA/CQ1

EG4/EG4P/EM6D
FE optical module
GE optical module
EG6
FE optical module
GE optical module
Table A-5 RTN 980

Board
EM6F/EM6FA
FE optical module
GE optical module
EMS6
GE optical module
SL1D/SL1DA/CQ1

EG4/EG4P
FE optical module
GE optical module
SL4D

Issue 01 (2016-04-30)

645

Configuration Guide
A Task Collection
Table A-6 RTN 980L

Board
EM6F
FE optical module
GE optical module
EMS6
GE optical module
SL1DA/CQ1

EG4/EG4P
FE optical module
GE optical module
SL4D

EX1
10GE optical module
Procedure
Step 1 Double-click the icon of an NE to open its slot layout.
NOTE
If you configure the logical board using the Web LCT, perform the following operations:
Click the Slot Layout tab.
Step 2 Right-click the target board and choose Path View. The board's path view is displayed.
Step 3 Optional: To delete a port, perform the following operations:
1.
Right-click the port to be deleted and choose Delete Port from the shortcut menu.
In the confirmation dialog box displayed, click OK.
Step 4 Optional: To add a port and configure the port, do as follows:

1.
Right-click in the blank area and choose Add Port from the shortcut menu.
2.
Set port parameters in Add Port.
3.
Click OK.
Issue 01 (2016-04-30)

646

Configuration Guide
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 port, you can set the SFP module type in Mo mode. For an Ethernet port, you need to delete
the port and add it again if you want to reset the SFP module type. Set the SFP module type when adding
the port.
l For an EG4/EG2D board, its SFP port and fixed GE port share a physical channel. Therefore, if the SFP
port has no SFP module, delete the port and add it again. When adding the port, set Type of the SFP
module to Electrical Port.
----End
A.3.1.8 Configuring the Backplane Bus Rate

When SL92CSH boards and CSHU/CSHUA boards are used as system control, timing, and
switching boards, the backplane bus rate can be increased to 2.5 Gbit/s.
Prerequisites
l
Only OptiX RTN 950 supports this operation.
All the boards have been installed correctly.

U2000
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Configuration > NE Properties from the Function Tree.
Step 2 On the Advance Properties tab page, set the backplane bus rate in Backplane Bus Mode.
----End
A.3.1.9 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.
Issue 01 (2016-04-30)

647

Configuration Guide
A Task Collection
Prerequisites
You must be an NM user with NE maintainer authority or higher.

U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE whose ID needs to be changed. Choose Properties.
The Properties dialog box is displayed.
Step 2 Click the NE Properties[xxx] tab.
NOTE
xxx indicates the current name of the NE.

If you change the NE ID using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE Attribute from the
Function Tree.
Step 3 Click Modify NE ID.

The Modify NE ID dialog box is displayed.
Step 4 Specify New ID and New Extended ID.
Step 5 Click OK.

A dialog box is displayed for confirmation, click OK.
Step 6 Click OK.
----End
A.3.1.10 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
Issue 01 (2016-04-30)

648

Configuration Guide
A Task Collection
NOTE
Procedure
Step 1 In the Main Topology, select the NE whose name is to be changed. Right-click on this NE,
and then choose Properties from the shortcut menu. The Properties dialog box is displayed.
NOTE
If you change the NE name using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree, and choose Configuration > NE Attribute from the
Function Tree.
Step 2 Click the NE Properties [xxx] tab.

NOTE
xxx is the current name of the NE.

NOTE
Skip this step when the Web LCT is used for configuration.
Step 3 Enter the name of the NE in Name.

NOTE
The name of an NE cannot contain any Chinese characters.
Step 4 Click OK. Close the dialog box indicating the operation result.
The new name of the NE is displayed below the NE icon in the Main Topology.
----End
A.3.1.11 Enabling NE Automatic Reporting

After the NE automatic reporting function is enabled, an NE is automatically added on the
U2000 topology when the NE can communicate with the U2000.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

649

Configuration Guide
A Task Collection
Context
NOTE
To perform batch NE configurations on the U2000, choose Configuration > NE Batch Configuration > Set
NE Auto Creation Attributes from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NMS
Server from the Function Tree.
Step 2 Double-click NE Automatic Reporting and select Enabled from the drop-down menu.
Step 3 Set the IP address for the U2000 server based on the network plan.
NOTE
l For a single NMS server, you only need to set Server IP1.
l For dual NMS servers, set Server IP1 and Server IP2.
Step 4 Click Apply.

----End
A.3.1.12 Synchronizing the NE Time (U2000)

By setting the NE time to be synchronous with the time on the NMS or standard NTP server,
you can record the exact time when alarms and abnormal events occur.
Prerequisites
l
When you need to synchronize the NE time with the time on the NMS server, the time
zone and time must be set correctly on the PC or server running the NMS software.
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
.
Issue 01 (2016-04-30)

650

Configuration Guide
A Task Collection
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 5 When you need to synchronize the NE time with the NMS time, set the time synchronization
mode and the related parameters.
1.
Optional: The NE time is synchronized with the NMS time immediately.

a.
Right-click the NE whose time needs to be synchronized, and then choose

Synchronize with NM Time from the shortcut menu.
b.
In the displayed confirmation dialog box, click Yes.
c.
Close the displayed operation result dialog box.
2.
Set Synchronous Mode to NM.
3.
Click Apply.
4.
Optional: Set auto synchronization parameters.

a.
Set auto synchronization parameters.
b.
Click Apply.
c.
d.
NOTE
l When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM.
l When you need to synchronize the NE time with the time on the NTP server, set Synchronous Mode to
Standard NTP. Configure Standard NTP Authentication according to the requirements of the NTP
server.
Step 6 When you need to synchronize the NE time with the time on the NTP server, set the time
synchronization mode and the related parameters.
1.
Set Synchronous Mode to Standard NTP.
2.
Configure Standard NTP Authentication according to the requirements of the NTP

server.
3.
Click Apply.
4.
Click Close. The dialog box that is displayed indicating the operation result is closed.
5.
Configure the upper-layer NTP server.

a.
Issue 01 (2016-04-30)
Select the NE, right-click in the configuration box where the standard NTP server is
configured, and then choose New.

651

Configuration Guide
6.
b.
Configure the parameters related to the NTP server.
c.
Click Apply.
d.
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
Issue 01 (2016-04-30)

652

Configuration Guide
A Task Collection
A.3.1.13 Synchronizing the NE Time (Web LCT)

By setting the NE time to be synchronous with the time on the NMS or standard NTP server,
you can record the exact time when alarms and abnormal events occur.
Prerequisites
l
When you need to synchronize the NE time with the time on the NMS server, the time
zone and time must be set correctly on the PC or server running the NMS software.
When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE
Time Synchronization from the Function Tree.
Step 2 Set the synchronous mode.
If...
Then...
You set Synchronous Mode to NULL
Set the relevant parameters, and then click Apply.
You set Synchronous Mode to NM
Set the relevant parameters, and then click Apply

to perform Step 5.
You set Synchronous Mode to

Standard NTP
Set the related parameters, and then click Apply to

perform Step 3.
NOTE
If you only need to synchronize the NE time and do not need to change the type of synchronization or
parameters, select the synchronization option corresponding to the NE, right-click, and choose Synchronize
with NM Time.
Step 3 Configure the upper-layer standard NTP server of the NE.

1.
Click the Standard NTP Server tab. In the Standard NTP Server tab page, click Add.
2.
After setting the parameters of the standard NTP server, click OK.
NOTE
l If the NE is a gateway NE, set the external NTP server as the standard NTP server.
l If the NE is a non-gateway NE, set the gateway NE as the standard NTP server.
Step 4 Optional: Configure standard NTP keys.

1.
Click the Standard NTP Key Management tab.
2.
Click Add.
The Add Key dialog box is displayed.
Issue 01 (2016-04-30)

653

Configuration Guide
3.
A Task Collection
After the related parameters are configured, click OK.
Step 5 Optional: Set Start Time and click Apply.

----End
A.3.1.14 Localizing the NE Time

When the daylight saving time (DST) is used in the area where the NE is located, you need to
localize the NE time to synchronize the NE time with the local time.
Prerequisites

U2000
NOTE
Context
NOTE
To perform batch NE configurations on the U2000, choose Configuration > NE Batch Configuration > NE
Time Localization Management from the main menu.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the Main Menu.
NOTE
If you localize the NE time using the Web LCT, perform the following operations:
In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time
Localization Management from the Function Tree.
Step 2 Select the NE for time localization management from the Object Tree, and then click
.
NOTE
Issue 01 (2016-04-30)

654

Configuration Guide
A Task Collection
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
A.3.1.15 Configuring Standard NTP Keys

When the NE time is synchronized with the time on the NTP server and the identity
authentication is required, configure NTP keys.
Prerequisites
l
You must be an NM user with NE administrator authority or higher.
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
NOTE
Configuring standard NTP keys using the Web LCT is performed during A.3.1.13 Synchronizing the NE
Time (Web LCT).
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the Standard NTP Key Management tab.
Step 3 In the physical view, select the NE whose NTP keys need to be configured, and then click
.
Step 4 Click Add.
The Add Key and Password dialog box is displayed.
Issue 01 (2016-04-30)

655

Configuration Guide
A Task Collection
Step 5 After the related parameters are configured, click OK.

----End
A.3.2 Configuring the NE Data

If an NE is not configured after being created successfully, you need to configure the NE data
so that the NMS can manage this NE.
A.3.2.1 Uploading the NE Data (U2000)

Uploading the NE data is commonly used for configuring the NE data. By uploading the NE
data, the data such as the configuration, alarm, and performance data of the NE is uploaded to
the NMS.
Prerequisites
l
An NE must be logged in to successfully.
Issue 01 (2016-04-30)

656

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 1 Select the corresponding operation steps according to the NE status.
Then...
If...
An NE is not configured and the NE data In the Main Topology, double-click the NE
needs to be uploaded.
that is not configured, and then perform Step
2 through Step 4.
An NE is configured with data and NE
data needs to be uploaded.
Perform Step 5 through Step 8.
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.3.2.2 Synchronizing NE Data (U2000)

Synchronizing NE data is uploading the NE-side data that is different from the NMS-side data
(including conflicting data and absent data) to the NMS.
Prerequisites
l
The NE is created.
The NE is in unsynchronized state.

NOTE
When an NE is in unsynchronized state, it carries the
Issue 01 (2016-04-30)
mark.

657

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 1 Method 1:
1.
Choose Configuration > Synchronize NE Configuration Data from the Main Menu.
2.
Select one or more NEs from the NE list, and click
3.
Select one or more unsynchronized NEs, and then click the Synchronize button or select
Synchronize from the shortcut menu.
The NMS starts synchronizing the configuration data.
Step 2 Method 2:
1.
In the Main Topology, select the NE with the mark, right-click it, and choose
Synchronize NE Configuration Data from the shortcut menu.
The system displays the Synchronize NE Configuration 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 Yes.
The NMS starts synchronizing the configuration data.
----End
A.3.3 Configuring the Performance Monitoring Status of NEs

By performing this operation task, you can manually enable or disable performance
monitoring for NEs, or set the performance monitoring period.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

658

Configuration Guide
A Task Collection
Context
NOTE
To perform batch NE configurations on the U2000, choose Performance > Set NE Performance
Monitoring Time from the main menu.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE
Performance Monitoring Time from the Function Tree.
Step 2 Configure the performance monitoring parameters of the NEs.
1.
Select 15-Minute or 24-Hour.
2.
Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3.
Set the start time and end time of the performance monitoring of NEs.
NOTE
4.
Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
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.
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.
Click Apply. Close the displayed dialog box.
----End
A.3.4 Suppressing Alarms for Monitored Objects

This section describes how to suppress specific alarms for a specific monitored object.
Prerequisites
Tools, Instruments and Materials

U2000
Issue 01 (2016-04-30)

659

Configuration Guide
A Task Collection
NOTE
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
Step 3 Set Monitored Object and click Query.

Step 4 Set Status in Alarm Suppression.
Step 5 Click Apply.
Step 6 Close the dialog box that is displayed.
NOTE
----End
A.3.5 Connecting Fibers or Cables

To implement the end-to-end management on the NMS, you need to connect fibers or cables.
A.3.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 portsor SDH ports and therefore quickly create optical fibers. The
search-and-create method is the most common method for creating radio links and optical
fibers.
Prerequisites
l
Issue 01 (2016-04-30)

660

Configuration Guide
A Task Collection
The SDH/IF boards of various NEs must be created on the NMS.

U2000
NOTE
Procedure
Step 1 Choose File > Discovery > Fiber/Cable/Microwave Link 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 Physical Root.
Step 3 Click Search.
NOTE
l If Do not search the ports with Fiber/Cable created on NMS is selected, the port whoseoptical
transmission line or radio link is created is not searched on the NMS.
l If you need to check whether the connection ofan optical transmission line or a radio link is the same
as the actual connection of theoptical transmission line or radio link, do not select Do not search the
ports with Fiber/Cable created on NMS.
l If Do not search the ports with Fiber/Cable created on NMS is selected and all the selected ports
are created withoptical transmission lines or radio links, a dialog box is displayed after the search,
indicating that the search domain is null.
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 5 In Physical Fiber/Cable Link List, select one or multipleoptical transmission lines or radio
links, and then click Create Fiber/Cable.
NOTE
l When you select one or multipleoptical transmission lines or radio links from Physical Fiber/Cable
Link List, the conflictingoptical transmission lines or radio links are automatically displayed in
Logical Fiber/Cable Link List. In this manner, you need to delete these conflictingoptical
transmission lines or radio links by referring to Step 6, and then create the links.
l When you createoptical transmission lines or radio links, No fiber to create is displayed if the
selectedoptical transmission lines or radio links are in the Already created state.
Step 6 When you select one or multiple conflictingoptical transmission lines or radio links from
Logical Fiber/Cable Link List, click Delete Fiber/Cable.
----End
Follow-up Procedure
If the information about theoptical transmission lines or radio links that are created using the
search method is incomplete, you can supplement the information by changing the
information about theoptical transmission lines or radio links.
A.3.5.2 Creating Fibers Manually

You can create a fiber by specifying the ports connected by the fiber. This method can be used
for creating SDH fibers, radio links, E1 cables, and Ethernet links.
Issue 01 (2016-04-30)

661

Configuration Guide
A Task Collection
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
NOTE
Procedure
Step 1 In the Main Topology, select the icon
. Then, the cursor is displayed as "+".
Step 2 Click the source NE of a fiber in the Main Topology.

Step 3 In the Select Fiber/Cable Source dialog box, select the source board and source port.
Step 4 Click OK. In the Main Topology, the cursor is displayed as "+".
Step 5 Click the sink NE of the fiber in the Main Topology.
Step 6 In the Select Fiber/Cable Sink dialog box, select the sink board and sink port.
Step 7 Click OK. Set the attributes of the fiber in the Create Fiber/Cable dialog box.
Step 8 Click OK. Then, the created fiber is displayed between the source NE and the sink NE in the
Main Topology.
----End
A.3.5.3 Searching for Ethernet Links

The NMS can detect Ethernet links (L2 links) using the search method and can quickly create
Ethernet fibers/cables using the detected Ethernet links.
Prerequisites
l
The boards of all NEs have been created on the NMS.
All Ethernet links are functioning properly.
Port Mode at both ends of each Ethernet link is Layer 2 or Layer 3.

U2000
NOTE
Issue 01 (2016-04-30)

662

Configuration Guide
A Task Collection
Context
A microwave link is generally not imported to fibers/cables unless IP addresses need to be
automatically assigned at both ends of the microwave link. After IP addresses are assigned,
you need to delete the fibers/cables that the microwave link is imported by choosing File >
Discovery > Fiber/Cable/Microwave Link from the main menu.
Procedure
Step 1 Choose File > Discovery > Link from the main menu.
Step 2 Select the NE for which Ethernet links need to be searched from the Function Tree on the left
.
pane and click
Step 3 Select one or multiple types of links to be searched for from three types: Links note exist in
the NMS, Links exist in the NMS, Conflicting links, and Links to be deleted.
After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Then, click Close.
Step 4 Select one or multiple links from the search result and click Create.
Step 5 Click Yes in the dialog box displayed if you want to create an Ethernet fiber/cable.
The Import Link dialog box is displayed.
Step 6 Select the target links from Available Link in the Import Link window and click
The links are displayed in Selected Link.
OptiX RTN 905
Other NEs
Issue 01 (2016-04-30)

663

Configuration Guide
A Task Collection
Step 7 Click OK.

----End
A.3.5.4 Creating an Extended ECC

Extended ECC connections indicate that the inter-NE DCN communication is implemented
through concatenated NM ports.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose File > Create > Link from the Main Menu. The Create Link dialog box is displayed.
Step 2 Choose Link > Extended ECC.
Step 3 Configure the attributes of the created extended ECC according to the data plan.
Issue 01 (2016-04-30)

664

Configuration Guide
A Task Collection
Step 4 Click OK.

In the Main Topology, the created extended ECC is displayed between the source NE and the
sink NE.
----End
A.3.5.5 Creating a Back-to-Back Radio Connection

Back-to-back radio connections indicate the stacking of multiple OptiX RTN NEs on one site.
Prerequisites
l
The corresponding IF board must be added on the NE Panel.

U2000
NOTE
Procedure
Step 1 In the Main Topology, choose File > New > Link.
The Create Link dialog box is displayed.
Step 2 Select Fiber/Cable > Microwave Back To Back.
Step 3 Select the source NE from the drop-down list of Source NE.
Step 4 Select the sink NE from the drop-down list of Sink NE.
Step 5 Configure the attributes of the back-to-back radio connection.
Step 6 Click OK.

The created back-to-back radio connection is displayed in the Main Topology.
----End
A.3.6 Managing Subnets

To facilitate NE management, you can allocate the NEs that are in the same domain or have
similar attributes into the same subnet.
Issue 01 (2016-04-30)

665

Configuration Guide
A Task Collection
A.3.6.1 Creating a Subnet

In the Main Topology, you can create a subnet object and allocate an NE to this subnet.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click, and then choose New > Subnet.
The Create Subnet dialog box is displayed.
Step 2 Click the Properties tab.
Step 3 Enter the attributes of the subnet.
Step 4 Click the Select Object tab, select a created NE from Available Objects, and then click
to add the NE to Selected Objects.
Issue 01 (2016-04-30)

666

Configuration Guide
A Task Collection
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
A.3.6.2 Copying Topology Objects

In the current topology, you can copy topology objects from one subnet to another subnet.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be copied.
Step 2 Choose Edit > Copy to.
The Select path as Parent Subnet dialog box is displayed.
Issue 01 (2016-04-30)

667

Configuration Guide
A Task Collection
Step 3 Select the subnet that the NE or subnet needs to be pasted to.
Step 4 Click OK.
----End
A.3.6.3 Moving Topology Objects

In the current topology, you can move topology objects from one subnet to another subnet.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be moved.
Step 2 Choose Edit > Move to.
The Select path as Parent Subnet dialog box is displayed.
Step 3 Select the subnet that the NE or subnet needs to be moved to.
Step 4 Click OK.
----End
A.3.7 Managing Communication

To manage the NE by the NMS, ensure that the DCN communication is working properly.
A.3.7.1 Setting NE IP Communication Parameters

The communication parameters of an NE include the IP address of the NE, the gateway IP
address, and the subnet mask.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

668

Configuration Guide
A Task Collection
Context
NOTE
l Do not use the default NE IP address to access the public network (such as Internet).
l The default NE IP address is a temporary address, and is only used for management DCN plug-and-play.
The IP address must be modified in a timely manner.
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
l If configuring multiple parameters, click Apply for each instance.

l When Connection Mode is set to Common + Security SSL for gateway NEs, it is recommended that
you set Connection Mode to Security SSL for the NMS.
----End
A.3.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
Issue 01 (2016-04-30)

669

Configuration Guide
A Task Collection

U2000
NOTE
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
For OptiX RTN 905, the 16th E1 is configured as a 2 Mbit/s external clock port, and external clock
source 2 refers to this 2 Mbit/s external clock port. For OptiX RTN 950/980, external clock source 1
refers to the external clock port on the system control board with a smaller slot ID, and external
clock source 2 refers to the external clock port on the system control board with a larger slot ID.
When Protocol Type is set to TCP/IP for a port that is an ABR's port in a non-backbone area, IP
Address and Subnet Mask must be specified for the port (ABR stands for area border router). In
addition, it is recommended that the IP address of the port and the IP address of the port-located NE
be on different network segments.
When Protocol Type is TCP/IP for a port and the port does not belong to the default process, you
need to set IP Address, Subnet Mask, and OSPF Subnet to which the port belongs.
Step 5 Optional: Create DCCs.

1.
Click Create.
2.
Set the attributes of the DCC.
Issue 01 (2016-04-30)

670

Configuration Guide
A Task Collection
NOTE
Set Protocol Type based on the management protocol used by the DCN solution.
3.
Click OK.
----End
A.3.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
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Step 2 Click the DCC Transparent Transmission Management tab.
Step 3 Click Create.
Then, the Create DCC Trarnsparent Transmission Byte dialog box is displayed.
Step 4 Set the parameters of the DCC transparent transmission byte.
Step 5 Click OK.

----End
Issue 01 (2016-04-30)

671

Configuration Guide
A Task Collection
A.3.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

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN
Step 2 Click the Bandwidth Management tab.
Step 3 Set the VLAN ID and bandwidth used by an inband DCN.
NOTE
l If the default VLAN ID of the inband DCN conflicts with the VLAN ID in the service, the Ethernet
Board VLAN ID of the inband DCN can be changed manually.
l Ethernet Board VLAN ID is an NE-level parameter and its priority is lower than that of the VLAN ID
configured for a specific port.
l Bandwidth(kbit/s) specifies the bandwidth for inband DCN messaging on the Ethernet link.
l IF Port Bandwidth(kbit/s) specifies the bandwidth for inband DCN messaging on the radio link.
l NMS Port VLAN ID is available only when an NE supports distinguish Huawei DCN packets from
third-party DCN packets by VLAN ID.
Issue 01 (2016-04-30)

672

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.3.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
NOTE
Procedure
Communication > DCN Management from the Function Tree.
Step 2 Click the Packet Control tab.
Step 3 Specifies the priority of inband DCN packets.
Step 4 Click Apply.

----End
A.3.7.6 Configuring Inband DCN Ports

This section describes how to set inband DCN channel attributes, such as, the inband DCN
enabled/disabled state and the VLAN ID.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

673

Configuration Guide
A Task Collection
Context
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.
l When ATN Compatibility Mode is Enabled, the NE can auto-negotiate its mode to the ATN mode or
transport equipment mode based on the inband DCN packets received from the peer end.
l The specified VLAN value takes precedence over the configured NE-level VLAN ID. The NE-level
VLAN ID will take effect over inband DCN ports with no VLAN ID specified.
l OSPF Subnet indicates the OSPF process to which a port belongs. When OSPF multi-process is enabled
on an NE, this parameter needs to be planned and specified.
Procedure
Step 2 Click the Port Settings tab.
Step 3 Optional: Select E1 and set port parameters for the ports that need to use inband DCN.
Step 4 Optional: Select CSTM-1 and set port parameters for the ports that need to use inband DCN.
Step 5 Optional: Select FE/GE, configure the port parameters for the inband DCN function.
Step 6 Optional: Select IF, configure the port parameters for the inband DCN function.
Step 7 Click Apply.

----End
A.3.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
Issue 01 (2016-04-30)

674

Configuration Guide
A Task Collection

U2000
NOTE
Context
NOTE
l Do not use the default NE IP address to access the public network (such as Internet).
l The default NE IP address is a temporary address, and is only used for management DCN plug-and-play.
The IP address must be modified in a timely manner.
Procedure
Step 2 Click the Access Control tab.
Step 3 Set the parameters for configuring access control.
NOTE
l If the Enabled Status is set to Enabled, this port can be used to support access of the management
information from the NMS.
l If the Enabled Status is set to Disabled, this port cannot be used to support access of the management
information from the NMS.
Step 4 Click Apply.

----End
A.3.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
NOTE
Issue 01 (2016-04-30)

675

Configuration Guide
A Task Collection
Context
The default extended ECC mode is Autosensing mode.
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the
Function Tree.
Step 2 Optional: You can enable the Auto mode function of the extended ECC.
1.
Set Extended ECC Mode to Auto mode.
2.
Click Apply.
A confirmation dialog box is displayed.
3.
Click OK.
Step 3 Optional: Set parameters for the extended ECC function in Specified mode at the server end.
1.
Set Extended ECC 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 Autosensing mode at the client end.
1.
Set Extended ECC Mode to Autosensing mode.
2.
Set related parameters for the client end.
Issue 01 (2016-04-30)

676

Configuration Guide
3.
Click Apply.
4.
Click OK.
A Task Collection
----End
A.3.7.9 Creating a Static IP Route

When dynamic routes fail to meet the planning requirements, you need to create the
corresponding static IP routes manually.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP
Protocol Stack Management from the Function Tree.
Step 2 Click the IP Route Management tab.
Step 3 Click New.
The Create an IP Route dialog box is displayed.
Step 4 Set the parameters of the static IP route.
NOTE
The created static route has a lower priority than a dynamic route.
Step 5 Click OK.

----End
A.3.7.10 Creating Static Route Entries in Kernel Route Tables

When static routes are used to construct an IP DCN and the U2000 communicates with NEs
through a gateway NE, you need to create static routes to non-gateway NEs on the gateway
NE and static routes to the gateway NE on the non-gateway NEs in the kernel route tables.
Prerequisites

U2000
Issue 01 (2016-04-30)

677

Configuration Guide
A Task Collection
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Communication >
Static Route Entries in the Kernel Route Table from the Function Tree.
The Create a Static Route Entry in the Kernel Route Table dialog box is displayed.
Step 3 Click New.
Step 4 Set the parameters for the static route entry.
Step 5 Click OK.
----End
A.3.7.11 Setting OSPF Protocol Parameters

When the OptiX RTN equipment is interconnected with third-party equipment, routing
protocol communication works properly after you set OSPF protocol parameters of the OptiX
RTN equipment based on related requirements of the third-party equipment.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the OSPF Parameter Settings tab.
Step 3 Set the parameters of the OSPF protocol.
Issue 01 (2016-04-30)

678

Configuration Guide
A Task Collection
NOTE
Set the parameters according to the network plan.
Step 4 Click Apply.

Step 5 Optional: Set OSPF parameters for DCC channels.
1.
Click the Port OSPF Parameter Settings tab.
2.
Set the OSPF parameters for DCC channels.
3.
Click Apply.
----End
A.3.7.12 Creating an OSPF Area

When an NE functions as an ABR, you need to create the non-backbone area to which the
ABR belongs.
Issue 01 (2016-04-30)

679

Configuration Guide
A Task Collection
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Communication > IP Protocol Stack
Step 2 Click the Multi-area OSPF Management tab.
Step 3 Click New.
The New dialog box is displayed.
Step 4 Set the parameters of the new OSPF area.
NOTE
Set parameters according to network planning information.
Step 5 Click OK.

----End
A.3.7.13 Configuring the Network Information of an ABR

This section describes how to add or modify the Network information of an ABR.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

680

Configuration Guide
A Task Collection
Procedure
Step 2 Click the Multi-area OSPF Management tab.
Step 3 Optional: Add a Network to an OSPF area.
1.
Select the OSPF area to add a Network.
2.
In Network Segment, click Add.

The Add dialog box is displayed.
3.
Set the IP address and subnet mask of the new Network.
NOTE
4.
Click OK.
Step 4 Optional: Change a Network of an OSPF area.

1.
In Network Segment, change the IP address and subnet mask of the target Network.
2.
Click Apply.
----End
A.3.7.14 Creating a Manual Route Aggregation Group

An NE supports a maximum of eight manual route aggregation groups.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the Multi-OSPF Management tab.
Step 3 Disable the automatic route aggregation function in an area.
1.
Issue 01 (2016-04-30)
In OSPF Area, select the area where routes need to be manually aggregated and set
Automatic Route Aggregation to Disabled.
681

Configuration Guide
2.
A Task Collection
Click Apply.
Step 4 In Manual Route Aggregation, click Add.

The Add dialog box is displayed.
Step 5 Set the IP address and subnet mask of the Network where routes are manually aggregated.
NOTE
Step 6 Click OK.

----End
A.3.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
NOTE
Procedure
Step 2 Set the OSPF authentication type.
1.
Click the Multi-area OSPF Management tab.
2.
In OSPF Area, change the value of Authentication Type of the desired OSPF area.
NOTE
none indicates no authentication.
3.
Click Apply.
Step 3 Set the passwords used for different types of DCN ports when different OSPF authentication
types are used.
Issue 01 (2016-04-30)

682

Configuration Guide
1.
Click the OSPF Parameter Settings tab.
2.
Set Authentication Type and Authentication Password.
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 4 Click Apply.

----End
A.3.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

U2000
NOTE
Procedure
Step 2 Click the Proxy ARP tab.
Step 3 Set the enable status of the proxy ARP.
NOTE
l The proxy ARP enables the NEs in the same network segment but different domains to communicate with
each other.
l To realize communication between such NEs, the source NE sends the ARP broadcast packet to address
the route to the destination NE. The NE with the proxy ARP function enabled checks the routing table
after sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP
broadcast packet looks for, the NE returns an ARP spoofing packet, which enables the NE that sends the
ARP broadcast packet to consider that the MAC address of the NE that returns the ARP spoofing packet
is the MAC address of the destination NE. In this manner, the packet that is to be sent to the destination
NE is first sent to the NE with the proxy ARP function enabled and then forwarded to the destination NE.
Issue 01 (2016-04-30)

683

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.3.7.17 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is

Used
The RSTP protocol improves stability of an L2 DCN.
Prerequisites

U2000
NOTE
Procedure
Communication > L2DCN Management from the Function Tree.
Step 2 Click Query.
Step 3 Set Configuration Status.
Step 4 Click Apply.

----End
A.3.7.18 Querying ECC Routes

By querying ECC routes, you can check whether the correct HWECC solution is configured
and whether the communication between NEs works properly.
Prerequisites
You must be an NM user with NE monitor authority or higher.
Issue 01 (2016-04-30)

684

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link
Management List.
----End
A.3.7.19 Querying IP Routes

By querying IP routes, you can check whether the IP DCN solution is configured correctly
and whether the communication between NEs works properly.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the IP Route Management tab.
Step 3 Click Query.
Step 4 Check whether the IP routes and related parameters in the routing table are in accordance with
the plan.
----End
Issue 01 (2016-04-30)

685

Configuration Guide
A Task Collection
A.3.7.20 Querying Core Routing Table Entries

By performing this operation, you can learn whether the DCN solution settings are correct and
whether NE communication is normal.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > Core
Routing Table from the Function Tree.
Step 2 Click Query. Close the displayed operation result dialog box.
----End
A.3.7.21 Querying OSPF Neighbor Information

This section describes how to query OSPF neighbor information.
Prerequisites
Issue 01 (2016-04-30)

686

Configuration Guide
A Task Collection
Tools, Instruments, and Materials

U2000
NOTE
Procedure
Step 2 Click the OSPF Neighbor tab.
Step 3 Click Query.
Step 4 Check whether the OSPF neighbor information is correct.

----End
A.3.7.22 Verifying Connectivity of an ECC Network

For a HWECC network, connectivity between two NEs can be verified by means of a ping or
traceroute test.
Prerequisites

U2000
NOTE
Procedure
Communication > NE ECC Link Management from the Function Tree.
Step 2 Click Reachability Test and choose Ping or Trace Route from the drop-down menu.
The Ping Test or Trace Route dialog box is displayed.
Step 3 Set test parameters.
Ping
Issue 01 (2016-04-30)

687

Configuration Guide
A Task Collection
Trace Route
Step 4 Click Start Test.

The test result is displayed.
----End
A.3.7.23 Verifying Connectivity of an IP DCN Network

For an IP DCN network, connectivity between two NEs can be verified by means of a ping or
traceroute test.
Prerequisites

U2000
NOTE
Procedure
Communication > IP Protocol Stack Management from the Function Tree.
Step 2 Click Reachability Test and choose Ping Test or Trace Route from the drop-down menu.
The Ping Test or Trace Route dialog box is displayed.
Step 3 Set test parameters.
Ping Test
Issue 01 (2016-04-30)

688

Configuration Guide
A Task Collection
Trace Route
Step 4 Click Start Test.

The test result is displayed.
----End
A.3.7.24 Setting SNMP Communications Parameters

The Simple Network Management Protocol (SNMP) is the most popular network
management protocol used on the TCP/IP networks. After you set SNMP communications
parameters, the SNMP server can obtain alarm and performance event data from the NE.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and then choose Communication >
SNMP Communication Parameters from the Function Tree.
Step 3 Set SNMP communications parameters of the NE based on the SNMP server requirements.
Issue 01 (2016-04-30)

689

Configuration Guide
A Task Collection
NOTE
l Set NMS IP Address to the IP address of the SNMP server that uses these communications
parameters. If there are no restrictions on the IP address of the SNMP server that accesses the NE,
set this parameter to 0.0.0.0. However, setting the NMS IP address to 0.0.0.0 causes certain security
risks. Therefore, make sure that you know the security risks when setting the NMS IP address to
0.0.0.0.
l If the NMS IP Address is set to 0.0.0.0, the NE does not support the Trap function.
l Verify Read/Write Permissions, Read Community Name, and Write Community Name of the
SNMP server based on the network plan. Read/Write Permissions, Read Community Name, and
Write Community Nam must take the same values as the right parameters set on the SNMP server.
l Set Report SDH Performance Trap, Report IP Performance Trap, and Report Alarm Trap to
Report if an SNMP server is required to automatically report trap packets when the SDH
performance crosses the threshold, the data performance crosses the threshold, or an alarm is
generated on a NE.
l It is recommended that Port take the default value.
l Set the Report Traps Version parameter based on the SNMP protocol version running on the
SNMP server.
Step 4 Click OK.

----End
A.3.7.25 Configuring the Active and Standby Gateway NEs

This section describes how to configure the active and standby gateway NEs in a DCN
network, therefore improving network reliability.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose Administration > DCN Management from the Main Menu.
The Filter dialog box is displayed.
Step 2 Click OK.
Step 3 Click the NE tab.
Step 4 Select the NE for which the standby gateway NE needs to be configured, double-click GNE2,
and select the desired standby gateway NE from the drop-down list.
Issue 01 (2016-04-30)

690

Configuration Guide
A Task Collection
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.3.8 Configuring the NMS Port

This section describes how to configure the NMS port, therefore ensuring normal NMS port
functioning and network security.
A.3.8.1 Configuring Basic Parameters for the NMS Port

By default, an NE can access the NMS or another NE through its Ethernet network
management port or NE cascading port, with the port working mode being auto-negotiation.
Prerequisites

U2000
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.
OptiX RTN 910A does not support the extended NMS port.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication >
Access Control from the Function Tree.
Step 2 Select Enable Ethernet Access. Then, the NE allows NMS access through its Ethernet ports.
Issue 01 (2016-04-30)

691

Configuration Guide
A Task Collection
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.3.8.2 Setting the VLAN ID for Huawei NMS

The Huawei NMS VLAN ID is used to differentiate Huawei DCN packets from third-party
DCN packets over the Ethernet NMS port. Packets with the NMS VLAN ID or without any
VLAN ID will be considered Huawei DCN packets and transmitted through DCN channels,
whereas the other packets are considered third-party DCN packets and transmitted along an ELAN service configured on the NMS port through a service channel.
Prerequisites

U2000
NOTE
Context
OptiX RTN 950 housing CSH boards does not support this operation.
Procedure
Step 2 Click the Bandwidth Management tab.
Step 3 Set NMS Port VLAN ID.
Issue 01 (2016-04-30)

692

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.3.8.3 Changing the Encapsulation Type and QinQ Type Domain for the
Ethernet NMS Port
This operation needs to be performed if the NMS port functions as a QinQ port and thirdparty packets are transmitted through service channels.
Prerequisites

U2000
NOTE
Context
OptiX RTN 950 housing CSH boards does not support this operation.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Interface Management > NMS Interface from the Function Tree.
Step 2 Click the Basic Attributes tab and set Encapsulation Type to QinQ.
Issue 01 (2016-04-30)

693

Configuration Guide
A Task Collection
Step 3 Click the Layer 2 Attributes tab and change the value of QinQ Type Domain.
Step 4 Click Apply.

----End
A.3.8.4 Configuring the Network Management Serial Port on an NE

By default, the NMS can access an NE through the serial port.
Prerequisites

U2000
NOTE
Context
If the LCT cannot access an NE through serial ports when the Enable Serial Port Access
check box is selected, the LCT access function may be disabled.
Procedure
Step 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
Issue 01 (2016-04-30)

694

Configuration Guide
A Task Collection
A.3.8.5 Configuring the Mini USB Port

By default, an NE can access the NMS through its mini USB port.
Prerequisites

U2000
NOTE
Context
This operation is supported only by OptiX RTN 980 (housing CSHNA), OptiX RTN 950
(housing CSHU/CSHUA) and OptiX RTN 905.
Procedure
Step 2 Click the Access Control Tab.
Step 3 Select the Enable OAM Access Control check box and select Access NM.
Step 4 Click Apply. Close the displayed operation result dialog box.
----End
A.4 Security Management

Security management is important in network management.
A.4.1 Configuring an NE User

NE users refer to the users who log in to and operate NEs. Different types of NE users are
assigned different rights to log in and manage NEs.
Issue 01 (2016-04-30)

695

Configuration Guide
A Task Collection
A.4.1.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
NOTE
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.
NOTE
Step 3 Click Add.

The Add NE User Attribute/Value dialog box is displayed.
Step 4 Set the parameters of the NE user according to the network plan.
Issue 01 (2016-04-30)

696

Configuration Guide
A Task Collection
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
A.4.1.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 01 (2016-04-30)

697

Configuration Guide
A Task Collection

U2000
NOTE
NOTE
Periodically change the password of an NE user to avoid password leaks.
Procedure
is successful.
NOTE
Step 3 Select the required NE user from the NE user management list, and click Set Password.
The Set Password of NE User dialog box is displayed.
Step 4 Input New Password, and input it again in Confirm Password.

----End
A.4.1.3 Configuring Additional User Information

This section describes how to configure additional user information, such as the login time
and password active period, for an NE user.
Issue 01 (2016-04-30)

698

Configuration Guide
A Task Collection
Prerequisites
l
An NE user has been created.
The current online NE user is of a higher level than the NE user whose additional user
information will be configured.

U2000
NOTE
Procedure
is successful.
NOTE
Step 3 Click View Additional User Info.

The Additional User Info List dialog box is displayed.
Step 4 Select the desired NE user and configure additional information for the NE user.
Step 5 Click OK and close the dialog box that is displayed.

----End
A.4.1.4 Setting Warning Screen Parameters

This topic describes how to enable the warning screen function. When a user logs in to an NE,
the NMS can display some information to the user. The displayed information can be defined
by users.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

699

Configuration Guide
A Task Collection
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.
Step 3 Click Apply.Close the displayed dialog box.

----End
A.4.1.5 Querying NE User Groups

This section describes how to query NE users in each NE user group on an NE.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer and choose Security > NE
User Group Management from the Function Tree.
Step 2 Click Query and close the dialog box that is displayed.
Step 3 Click the desired NE user group to display all NE users in the group.
Issue 01 (2016-04-30)

700

Configuration Guide
A Task Collection
----End
A.4.1.6 Managing Online NE Users

This section describes how to query current online NE users and force online NE users to log
out.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer and choose Security > Online
User Management from the Function Tree.
Step 2 Click Query and close the dialog box that is displayed. The current online NE user
information is displayed.
Step 3 Select the desired online NE user, click Force Logout and close the dialog box that is
displayed.
----End
Issue 01 (2016-04-30)

701

Configuration Guide
A Task Collection
A.4.1.7 Switching NE Users

This section describes how to switch an NE user to a higher-level NE user when the
operations on the NMS are beyond the operation rights of the NE user.
Prerequisites
l
An NE user is created.

U2000
NOTE
An NE cannot be logged in to and managed by the same NE user from different servers at the
same time. If the same NE user from different servers logs in to an NE at different time, the
first online user will be forcibly logged out of the NE.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Choose Security > NE
Login Management from the Function Tree.
Step 2 Select the required NE, and click Switch NE User.
The Switch Current NE User dialog box is displayed.
Step 3 Set User and Password of the user to be switched.

----End
Issue 01 (2016-04-30)

702

Configuration Guide
A Task Collection
A.4.2 Configuring USB Access Status

By default, a USB flash drive can directly connect to an NE. You can perform this task to
forbid the access.
Prerequisites

U2000
NOTE
Context
This operation is supported only by OptiX RTN 980 (housing CSHNA), OptiX RTN 910A
OptiX RTN 905, OptiX RTN 950A, and OptiX RTN 950 (housing CSHU/CSHUA).
Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer, and choose Communication >
Access Control from the function tree.
Step 2 Select the USB Access Control tab page.
Step 3 Set the USB access status to Enabled or Disabled.
Step 4 Click Apply.

----End
A.4.3 Configuring LCT Access to NEs

When an NE is managed by the NMS, the LCT can access this NE by default.
Prerequisites
Issue 01 (2016-04-30)

703

Configuration Guide
A Task Collection

U2000
NOTE
Context
l
If the LCT requests to log in to an NE to which the NMS has logged in, the NE
determines whether to permit the login of the LCT according to the status of LCT
Access Control Switch.
If the LCT requests to log in to an NE to which the NMS has not logged in, the NE
permits the login of the LCT regardless of the status of LCT Access Control Switch.
The NMS, however, can log in to an NE to which the LCT has logged in. That is, the
login of the LCT does not affect the login of the NMS. After the NMS user logs in to the
NE successfully, the logged LCT user is not affected. If LCT Access Control Switch is
set to Disable Access, the logged LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT
Step 2 Select the required NE from the list, and click Access Allowed to enable the LCT access
function.
NOTE
To disable the LCT access function, click Disable Access.
----End
A.4.4 Configuring SSL Protocol Communication

The security socket layer (SSL) protocol provides encrypted and reliable communication
between entities. Therefore, SSL protocol communication greatly improves the network
management security.
A.4.4.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.
Issue 01 (2016-04-30)

704

Configuration Guide
A Task Collection

U2000
NOTE
l
Two connection modes are supported, which are Common and Security(SSL) and
which can be queried on the U2000 server by running a query command.
The default connection mode is Common.

NOTE
l When the U2000 server and its client are deployed on the same host and the U2000 server uses the
SSL connection mode, the client can log in to the server by using the common or SSL connection
mode. When the U2000 server and its client are deployed on the same host and the U2000 server
uses the common connection mode, the client can log in to the server only by using the common
connection mode.
l When the U2000 server and its client are deployed on different hosts, the client can log in to the
U2000 server only by using the same connection mode as the U2000 server.
Security SSL is recommended for communication.
Procedure
Step 1 Start the U2000 client.
Step 2 In the Login interface, click
.
The Server List dialog box is displayed.
Step 3 Select the required U2000 server and click Modify.
The Modify Server Information dialog box is displayed.
Step 4 Set Mode to Security(SSL).

Step 5 Click OK.
Step 6 Click OK.
----End
A.4.4.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.
Issue 01 (2016-04-30)

705

Configuration Guide
A Task Collection
Prerequisites
l
SSL licenses have been deployed on the gateway NE and the U2000 client according to
the SSL loading guide.

U2000
NOTE
Procedure
Step 1 Configure the connection mode of the U2000 client.
1.
Choose Administration > DCN Management from Main Menu.

The Filter dialog box is displayed.
2.
Click Cancel and then click the GNE tab.

The Filter GNE dialog box is displayed.
, choose the required gateway NE, and then click OK.
3.
Click
4.
Click OK.
5.
Select the required NE, right-click the NE, and choose Modify GNE from the shortcut
menu.
The Modify GNE dialog box is displayed.
6.
Change the value of Connection Mode to Security SSL.
NOTE
If Connection Mode is set to Common or Common + Security SSL and the U2000 logs in to an NE
in common mode, data is transmitted between the U2000 and NE in plaintext and there are security
risks. Security SSL is recommended for communication.
Issue 01 (2016-04-30)

706

Configuration Guide
7.
A Task Collection
Click OK.
A warning dialog box is displayed.
8.
Click OK. Close the displayed dialog box.
Step 2 Configure the connection mode of the gateway NE.

1.
Select the NE from the Object Tree in the NE Explorer. Choose Communication >
2.
Set Connection Mode to Security SSL or Common + Security SSL.

NOTE
If Connection Mode of a gateway NE is Security SSL, tools (such as the Web LCT and DC) that use
the common connection mode cannot communicate with the gateway NE.
3.
Click Apply.
----End
A.4.5 Configuring RADIUS Authentication

The RADIUS authentication function allows a RADIUS server to implement centralized
management over all users that log in to an NE.
A.4.5.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
Issue 01 (2016-04-30)

707

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
RADIUS Configuration from the Function Tree.
Step 2 Enable an NE to be a RADIUS client.
1.
Double-click RADIUS Client and choose Open from the drop-down menu.
2.
Click Apply. Then, close the operation result dialog box that is displayed.
Step 3 Optional: Enable an NE to be a proxy server.

1.
Double-click Proxy Server and choose Open from the drop-down menu.
NOTE
2.
Proxy Server can be set to Open only if RADIUS Client is set to Open.
When an NE uses RADIUS authentication in the proxy NAS mode, set Proxy Server to Close.
Click Apply. Then, close the operation result dialog box that is displayed.
----End
A.4.5.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
NOTE
Issue 01 (2016-04-30)

708

Configuration Guide
A Task Collection
Procedure
Step 2 Click the RADIUS Server Configuration tab.
The RADIUS Server Information dialog box is displayed.
Step 3 Click New.
The New RADIUS Server Information dialog box is displayed.
Step 4 Configure information about the RADIUS server or RADIUS proxy server.
l
If an NE uses RADIUS authentication in the NAS mode or functions as a proxy server,

set the parameters as follows:
NOTE
Issue 01 (2016-04-30)
For both NE RADIUS authentication and NE usage accounting, set this parameter to
Authentication + Accounting or Accounting (when the Authentication function has been
enabled).
Set Server Type to RADIUS Server.
Set Server ID to IP Address and specify the IP address of the RADIUS server.
If an NE uses RADIUS authentication in the proxy NAS mode, set the parameters as
follows:

709

Configuration Guide
A Task Collection
NOTE
For both NE RADIUS authentication and NE usage accounting, set this parameter to
Authentication + Accounting or Accounting (when the Authentication function has been
enabled).
Set Server Type to Proxy Server.
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
A.4.5.3 Configuring RADIUS Server Parameters

This section describes how to configure RADIUS server parameters.
Prerequisites
l
l

The RADIUS server or RADIUS proxy server have been configured for the NE.

U2000
NOTE
Procedure
Step 2 Click New.
The New RADIUS Server Information dialog box is displayed.
.
Step 3 Click
The Select Server dialog box is displayed.
Step 4 Select a configured server and click OK. Then, the system automatically associates out the
values of Function, Server ID, and Server Type.
Step 5 Configure the RADIUS parameters.
l If an NE uses RADIUS authentication in the NAS mode or functions as a proxy server:
Issue 01 (2016-04-30)

710

Configuration Guide
A Task Collection
If an NE uses RADIUS authentication in the proxy NAS mode:
NOTE
l If no standby server is required, set Server Status to Active.

l The NE supports one active server and two standby servers. 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 It is recommended that Interval of Packet Transmission and Packet Retransmission Attempts take
----End
A.4.6 Configuring LLDP

Configuring LLDP to transmit equipment information between neighboring NEs and to
achieve automatic discovery of topology.
A.4.6.1 Configuring the Transmit Parameters for LLDP Packets

The transmit parameters of LLDP packets need to be consistent with those on the LLDP
neighbor equipment.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired NE from the object tree in the NE Explorer and choose Configuration >
LLDP Configuration from the function tree.
Issue 01 (2016-04-30)

711

Configuration Guide
A Task Collection
Step 2 Set packet transmit parameters on the Protocol Time Parameters tab page.
Step 3 Click Apply.

----End
A.4.6.2 Configuring LLDP for an Ethernet Port

Configuring LLDP for Ethernet ports connected to neighbor equipment is a prerequisite for
using LLDP.
Prerequisites

U2000
NOTE
Procedure
Step 2 Configure LLDP for an Ethernet port on the Port Parameters tab page.
NOTE
You can also configure LLDP for IF boards on an OptiX RTN 950 using CSHU/CSHUA boards and an
OptiX RTN 950A using SLF2CSHO board.
Step 3 Click Apply.

----End
A.4.6.3 Querying LLDP Neighbor Relationship

You can query information about an NE on its neighbor NE after the neighbor relationship is
set up between them using LLDP.
Prerequisites
l
LLDP has been enabled for related Ethernet ports.

U2000
Issue 01 (2016-04-30)

712

Configuration Guide
A Task Collection
NOTE
Procedure
Step 2 Click Query and view the neighbor NE information on the Neighboring Node Information
tab page.
NOTE
Alternatively, perform the following steps to query the neighbor NE information on the U2000:
1. Choose Inventory > Base Station Report from the main menu.
2. Select an NE from the left pane and click
----End
A.5 Managing Radio Links

Before you configure the radio link between two microwave sites, configure the information
about the radio link.
A.5.1 Configuring a Single-Hop Radio Link

This task sets the basic attributes for the local NE and the peer NE on a single-hop radio link.
Prerequisites
l
The IF boards and the ODUs/RFUs to which the IF boards are connected have been
added in NE Panel.

U2000
NOTE
l
This task configures a 1+0 radio link, a cross polarization interference cancellation
(XPIC) radio link, or a 1+1 radio link. To configure N+0 radio links, they must be
configured as N 1+0 radio links.
For OptiX RTN 905 1E, this task configures a 1+0 radio link or an XPIC radio link. The
method for configuring an XPIC radio is different from the method for configuring an
XPIC radio link between other OptiX RTN 900 products.
To configure 1+1 radio links between interconnected OptiX RTN 905 1E, perform the
operation A.5.2 Creating an IF 1+1 Protection Group and then configure a 1+0 radio
link between the two main OptiX RTN 905 1Es and a 1+0 radio link between the two
standby OptiX RTN 905 1Es.
Issue 01 (2016-04-30)

713

Configuration Guide
A Task Collection
Link ID, IF Channel Bandwidth, AM, Modulation Mode of the Guaranteed AM

Capacity, Modulation Mode of the Full AM Capacity, and T/R Spacing(MHz) of the
NEs on a hop of radio link are automatically synchronized. That is, if one of the
preceding parameters is modified on an NE, the modification is automatically duplicated
on the peer NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Radio Link
Configuration from the Function Tree.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select an NE from the Object Tree in the NE Explorer. Click the Radio Link Configuration tab.
Step 2 Select the IF board connected to the microwave link from the drop-down list.
The basic information of the radio link connected to the IF board is displayed.
NOTE
Click Open the Opposite NE Explorer to enter the NE Explorer of the peer NE.
NOTE
l If the radio link is in a 1+1 or XPIC group, select any IF board connected to the radio link.
l If the radio link is not working correctly, the basic information of the peer NE is not displayed.
l For an ISM6 board, select an IF port to which the radio link is connected.
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:

a.
Select 1+0, and deselect the XPIC check box.

NOTE
For RTN 905 1E, Protection is unavailable, therefore, deselect XPIC.
b.
Configure the basic attributes of the radio links.
NOTE
After 1+0 is selected and the configuration takes effect, the IF 1+1 protection group or XPIC
workgroup is deleted if the radio link is configured with 1+1 protection or XPIC.
Issue 01 (2016-04-30)
To configure 1+1 protected radio links:

a.
Select 1+1.
b.

714

Configuration Guide
c.
l
A Task Collection
Optional: Click Advanced, and configure the advanced attributes of the radio
links.
To configure XPIC radio links for OptiX RTN 905 1E:

a.
Select XPIC.
b.
c.
After the configuration is complete on the local NE, click Synchronize to

synchronize the radio link configurations to the adjacent NE.
To configure XPIC radio links for other OptiX RTN 900 products:
a.
Select 1+0 and XPIC.
b.
NOTE
To configure XPIC radio links under 1+1 protection, first configure two XPIC radio links,
and then configure IF 1+1 protection by following the instructions in A.5.2 Creating an IF
1+1 Protection Group.
Step 4 Configure IF attributes for the local NE and the peer NE on the radio link.
NOTE
If two XPIC links in an XPIC group are in the same N+1 protection group, configure the E1 capacity
consistently for the two XPIC links.
Step 5 Configure RF attributes for the local NE and the peer NE on the radio link.
NOTE
In IS3 or IS6 runtime mode, the transmit power can reach the configured maximum value in the
corresponding modulation scheme only after the microwave link is available.
Issue 01 (2016-04-30)
Configure a 1+0 non-protected radio link.

715

Configuration Guide
Configure 1+1 protected radio links.
Configure XPIC radio links.
A Task Collection
Step 6 Click Apply.

----End
A.5.2 Creating an IF 1+1 Protection Group

If the radio link requires 1+1 HSB/FD/SD protection, create the IF 1+1 protection group. To
configure an IF 1+1 protection group on two cascaded RTN 905 1Es, you need to configure
an IF 1+1 protection group on eachRTN 905 1E.
Prerequisites
l
The IF boards and the ODUs to which the IF boards are connected have been added on
the NE Panel.
The IF boards of an IF 1+1 FD/SD protection group have been configured in two paired
slots.
The two RTN 905 1Es are connected using a service cascade cable.

U2000
Issue 01 (2016-04-30)

716

Configuration Guide
A Task Collection
NOTE
When a 1+0 service is converted into a 1+1 HSB protection configuration by configuring the
IF 1+1 protection group, the original E1 service is not interrupted. The board that carries the
original service, however, needs to be set as the working board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the IF 1+1 Protection tab.

The Create IF 1+1 Protection dialog box is displayed.
Step 3 Configure the parameters of the IF 1+1 protection group.
OptiX RTN 905 1E
Other OptiX RTN 900 products
Issue 01 (2016-04-30)

717

Configuration Guide
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, it is recommended that you set Enable Reverse Switching to Enabled.
l Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
Enable Reverse Switching must be set to the same value at both ends of a radio hop.
l It is recommended that you set Alarm Report Mode to Only protection group alarms. In this
case, protection group alarms are reported to indicate radio link faults.
l It is recommended that Anti-jitter Time(s) take its default value.
Step 4 Click OK. Close the displayed operation result dialog box.
Step 5 Optional: For RTN 905 1E, repeat the preceding steps to create an IF 1+1 protection group
on the other NE.
----End
A.5.3 Modifying the Parameters of IF 1+1 Protection

This section describes how to modify the parameters of IF 1+1 protection, such as the alarm
reporting mechanism of an IF 1+1 protection group.
Prerequisites
l
An IF 1+1 protection group has been configured.

U2000
NOTE
Issue 01 (2016-04-30)

718

Configuration Guide
A Task Collection
When a 1+0 service is converted into a 1+1 service by configuring the IF 1+1 protection, the
original E1 service is not interrupted. To implement the conversion, set the board where the
1+0 service resides as the working board.
Procedure
NOTE
If you modify the parameters of IF 1+1 protection using the Web LCT, perform the following operations:
Step 2 Click Query. Then, close the dialog box that is displayed. Check the IF 1+1 protection groups
in Protection Group.
Step 3 Select the protection group whose parameters need to be modified. For example, right-click
the Alarm Suppression parameter to suppress the MW_BER_SD, MW_BER_EXC,
MW_RDI, RADIO_RSL_LOW, MAC_EXT_EXC, or MAC_FCS_EXC alarm or cancel the
suppression of the alarm.
Issue 01 (2016-04-30)

719

Configuration Guide
A Task Collection
NOTE
l Enable Reverse Switching is valid only when Working Mode is set to HSB or SD.
l Generally, it is recommended that you set Enable Reverse Switching to Enabled.
l Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
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.
l The Alarm Suppression parameter specifies whether to suppress the W_BER_SD, MW_BER_EXC,
MW_RDI, RADIO_RSL_LOW, MAC_EXT_EXC, or MAC_FCS_EXC alarms. This parameter is valid
only when Alarm Report Mode is set to Only protection group alarms.
Step 4 Click Apply.

----End
A.5.4 Creating an N+1 Protection Group

When multiple STM-1 or Integrated IP microwave services are transmitted in the point-topoint mode, you can adopt the N+1 protection configuration.
Prerequisites
l
the NE Panel.
The IF board works in SDH, Hybrid (Native E1 + Ethernet) or Hybrid (STM-1 +

Ethernet) mode.

U2000
NOTE
l
OptiX RTN 905 does not support this operation.
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.
N+1 protection for OptiX RTN 980 using CSHNA boards is available in two modes:
enhanced N+1 protection and standard N+1 protection. For standard N+1 protection
configured for Integrated IP microwave, the Hybrid/AM attributes of microwave links in
an N+1 protection group must be set consistently. For enhanced N+1 protection, the
Hybrid/AM attributes can be set flexibly for the links.
For Integrated IP microwave on other NEs, the Hybrid/AM attributes must be set
consistently for the microwave links in an N+1 protection group.
Issue 01 (2016-04-30)

720

Configuration Guide
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
NOTE
If you create an N+1 protection group using the Web LCT, perform the following operations:
the Function Tree. Click the N+1 Protection tab.

The Create a N+1 Protection dialog box is displayed.
Step 3 Configure the Attribute of the N+1 protection group.

Step 4 Configure the mapping relationship between the board and the slot.
1.
Select Work Unit from Select Mapping Direction.
2.
Select a port to which a working channel corresponds from Available Boards, and then
click
3.
Repeat Step 4.2 to select the ports to which other working channels correspond. Click
.
4.
Select Protection Unit from Select Mapping Direction.
5.
Select a port to which a protection channel corresponds from Available Boards, 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
Issue 01 (2016-04-30)

721

Configuration Guide
A Task Collection
A.5.5 Querying the IF 1+1 Protection Status

You can learn about the current information about the IF 1+1 protection by querying the IF
1+1 protection status.
Prerequisites
l
The IF 1+1 protection must be configured.

U2000
NOTE
Procedure
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Step 2 Click Query.Close the displayed operation result dialog box. In Protection Group, check the
IF 1+1 protection groups.
Step 3 Select the IF 1+1 protection group whose protection status needs to be queried. Click Query
Switch Status, and then close the displayed prompt dialog box. In Slot Mapping Relation,
check the protection status of the IF 1+1 protection group.
Issue 01 (2016-04-30)

722

Configuration Guide
A Task Collection
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Select the board from Slot Mapping Relation. Right-click on the selected board and choose Query
Switching Status from the shortcut menu to check the protection status of the IF 1+1 protection group.
----End
A.5.6 Querying the IF N+1 Protection Status

You can learn about the current information of the IF N+1 protection by querying the IF N+1
protection status.
Prerequisites
l
The IF N+1 protection must be configured.

U2000
NOTE
Procedure
NOTE
If you query the IF N+1 protection status using the Web LCT, perform the following operations:
Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check
the IF N+1 protection groups.
Step 3 Select the protection group whose protection status needs to be queried.
Step 4 Click Query Switch Status, and then close the displayed dialog box. In Slot Mapping
Relation, check the IF N+1 protection status.
----End
A.5.7 IF 1+1 Protection Switching

You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection
switching.
Prerequisites
l
The IF 1+1 protection must be configured.
Issue 01 (2016-04-30)

723

Configuration Guide
A Task Collection

U2000
NOTE
Context
Two RTN 905 1E NEs are cascaded through a cascade cable and form a 1+1 protection group.
Switching operations are conducted only on the main NE.
Procedure
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Settings, select a working unit or the protection unit of the protection group,
and then right-click the selected unit.
Step 4 Choose the required switching mode from the shortcut menu.
The system displays the dialog box that indicates the successful operation.
Step 5 Click Close.
Step 6 Click Query Switching Status and check whether the switching is successful, and then close
the displayed prompt dialog box.
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Select the working unit or the protection unit, right-click Query Switching Status and check whether the
switching is successful.
----End
A.5.8 IF N+1 Protection Switching

You can perform external switching on the IF N+1 protection by performing IF N+1
protection switching.
Prerequisites
l
The N+1 protection protocol is enabled.
Issue 01 (2016-04-30)

724

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
NOTE
If you perform IF N+1 protection switching using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection
group, and then right-click the selected unit.
Step 4 Choose the desired switching mode from the shortcut menu.
Step 5 In the dialog box that is displayed, click OK.
The system displays the dialog box that indicates the successful operation.
Step 6 Click Close.
Step 7 Click Query Switch Status to check whether the switching operation is successful.
----End
A.5.9 Starting/Stopping the N+1 Protection Protocol

If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be
restored to the initial state.
Prerequisites
l

U2000
NOTE
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
Issue 01 (2016-04-30)

725

Configuration Guide
A Task Collection
working channel is normal, the services are transiently interrupted. If the working
channel is faulty, the services are interrupted until the working channel is restored to
normal or the N+1 protection protocol is started.
Procedure
NOTE
If you start/stop the N+1 protection protocol using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group whose N+1 protection protocol needs to be
started.
Step 3 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box.
Step 4 Click Query to check the protocol status.
----End
A.5.10 Creating a PLA/EPLA/EPLA+/Super EPLA Group

When PLA/EPLA/EPLA+/Super EPLA is used to increase Ethernet service bandwidth or
improve reliability on radio links, you need to create a PLA/EPLA/EPLA+/Super EPLA
group.
Prerequisites
l
the NE Panel.

U2000
NOTE
l
OptiX RTN 910A, OptiX RTN 905, OptiX RTN 950A, OptiX RTN 950 using CSHU/
CSHUA boards, and OptiX RTN 980 using CSHNA boards support EPLA.
Only OptiX RTN 910A, OptiX RTN 950A, and OptiX RTN 950 using CSHU/CSHUA
boards support EPLA+.
Only cascaded OptiX RTN 905 1E NEs support PLA.
For the limitations of PLA/EPLA/EPLA+, see Feature Dependencies and Limitations of

PLA/EPLA/EPLA+ in the Feature Description.
When you create or delete a PLA group on an ISU2 or ISX2 board, the board is cold
reset.
Issue 01 (2016-04-30)

726

Configuration Guide
A Task Collection
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
Physical Link Aggregation from the Function Tree.
Step 2 Click New.
The Create Physical LAG dialog box is displayed. The Create Physical LAG dialog box is
displayed.
l
OptiX RTN 910A
OptiX RTN 950A and OptiX RTN 950

PLA/EPLA/EPLA+:
Issue 01 (2016-04-30)

727

Configuration Guide
A Task Collection
Super EPLA
Issue 01 (2016-04-30)

728

Configuration Guide
A Task Collection
NOTE
Issue 01 (2016-04-30)
When Scheduling Mode is Mode B, In hitless mode, E-band link bandwidth changes do not affect
the transmission of high-priority services. In this mode, high-priority services are transmitted on
common-band links, and low-priority services are transmitted on E-band links. However, if highpriority services exceed the common-band link bandwidth upon a burst, the excessive traffic cannot
be transmitted by E-band links and is discarded.
When Scheduling Mode is Mode A, In common mode, high-priority and low-priority services are
distributed to common-band and E-band links based on their link bandwidths, implementing interfrequency AM.
When Scheduling Mode is Mode B, This threshold can be specified for a Super EPLA group in
hitless mode. Only an SP queue can be configured with a PHB. Services in this SP queue and other
queues with higher-priorities are high-priority services.
OptiX RTN 980L

729

Configuration Guide
Issue 01 (2016-04-30)
A Task Collection
OptiX RTN 980

730

Configuration Guide
Issue 01 (2016-04-30)
A Task Collection
OptiX RTN 905 1E\2E

731

Configuration Guide
A Task Collection
NOTE
Issue 01 (2016-04-30)
If an OptiX RTN 905 2E is configured with cascade EPLA, the cascade port 8-VS2-1 has two
internal channels: channel 1 and channel 2. Channel 1 must connect to port 3-ISV3-1, and channel 2
must connect to port 4-ISV3-1.
If an OptiX RTN 905 1E is configured with cascade PLA/EPLA, only channel 1 at the cascade port
8-VS2-1 can be configured as the cascade channel.
When configuring an OptiX RTN 905 1E/2E as the master NE, configure the cascading channel
connecting to IF boards on the slave NE.
When configuring an OptiX RTN 905 1E/2E as the slave NE, configure the cascading channel
connecting to its IF boards.
If an OptiX RTN 905 2E that runs V100R007C10 or earlier software and is configured with IF 1+1
protection is the slave NE, the two cascading channels must be added to the EPLA group. If an
OptiX RTN 905 2E that runs V100R008C00 software and is configured with 1+1 protection is the
slave NE, only the cascading channel connected to the main IF board must be added to the EPLA
group.

732

Configuration Guide
A Task Collection
Step 3 Configure PLA/EPLA/EPLA+/Super EPLA parameters.

Step 4 Click OK. Then, close the dialog box that is displayed.
Step 5 Optional: Configure Minimum Active Links.
1.
Click Query.
2.
Configure Minimum Active Links.
Step 6 Optional: When RTN 980L is used as long-haul microwave, you can enable hitless EPLA
switching by setting the Hitless Switching parameter.
----End
A.5.11 Querying the Status of a PLA/EPLA/EPLA+/Super EPLA

Group
This section describes how to query the current information about a PLA/EPLA/EPLA+/
Super EPLA group.
Prerequisites
l
A PLA/EPLA/EPLA+/Super EPLA group has been configured.

U2000
NOTE
Procedure
Configuration > Physical Link Aggregation from the Function Tree.
Step 2 Click Query. View the information about the PLA/EPLA/EPLA+/Super EPLA group in
Physical Link Aggregation List.
NOTE
l .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
A.5.12 Configuring Ethernet Frame Header Compression over Air

Interfaces
By default, the Ethernet frame header compression function is disabled.
Prerequisites
l
Issue 01 (2016-04-30)

733

Configuration Guide
A Task Collection
The corresponding IF board has been added in the NE Panel.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the Advanced Attributes tab.
Step 3 Configure the Ethernet frame header compression function and the error frame discarding
over air interfaces function.
NOTE
l If Speed Transmission at L2 is set to Enabled, the Layer-2 Ethernet packets transmitted at microwave
ports will be compressed to improve transmission efficiency.
l The settings of Speed Transmission at L2 must be the same at both ends of a radio link.
l If Speed Transmission at L3 is set to Enabled, the IP packets transmitted at microwave ports will be
compressed to improve transmission efficiency.
l The settings of Speed Transmission at L3 must be the same at both ends of a radio link.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
A.5.13 Configuring Enhanced Ethernet Frame Compression

This section describes how to configure enhanced Ethernet frame compression for an egress
queue at an IF port.
Prerequisites
l
Only ISV3 boards in IS3 mode support this operation.
Context
NOTE
Do not enable enhanced Ethernet frame compression on an NE if the NE interconnects with an NE that does
not support enhanced Ethernet frame compression. Otherwise, services and inband DCN communication
between the two NEs are interrupted.
Issue 01 (2016-04-30)

734

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 1 Select the desired IF board from the Object Tree in the NE Explorer. Choose Configuration >
Enhanced Compression from the Function Tree.
Step 2 Configure enhanced Ethernet frame compression for an egress queue at the IF port on the IF
board.
NOTE
If enhanced Ethernet frame compression is enabled for a QoS queue at an IF port, Ethernet frame header
compression (L2+L3) is automatically enabled for the IF port.
Step 3 Click Apply.

----End
A.5.14 Setting AES-based Encryption at Air Interfaces

This section describes how to enable AES-based encryption at air interfaces and set required
parameters.
Prerequisites

U2000
NOTE
Context
l
RTN 910A/RTN 980/RTN 950A: AES-based encryption at air interfaces is supported

only by ISV3 boards in IS3 mode.
RTN 950: AES-based encryption at air interfaces is supported only when CSHU/
CSHUA boards work with ISV3 boards in IS3 mode.
RTN 980L: AES-based encryption at air interfaces is supported only by ISV3 boards in
IS3 mode or LH ACCP mode.
RTN 905 does not support AES-based encryption at air interfaces.
AES-based encryption at air interfaces cannot be enabled when an ISV3 interconnects

with an ISM6 board or an RTN 905.
Issue 01 (2016-04-30)

735

Configuration Guide
A Task Collection
Procedure
Step 1 In the NE Explorer, select the desired ISV3 board from the Object Tree and choose
Configuration > Radio Interface Encryption from the Function Tree.
Step 2 Click the Radio Interface Encryption tab page.
Step 3 Set Encryption Status to Enabled.
Step 4 Set the key update interval. You can specify Key Negotiation Interval to periodically update
keys or click Negotiate Key Manually to forcibly update keys.
Step 5 Click Set Authentication Code. In the displayed Set Authentication Code dialog box, set
authentication code, and click OK.
NOTE
An authentication code must contain:

l
Eight to 32 characters
At least two types of the following characters:

Digit, uppercase letter, lowercase letter, and special character
Step 6 Click Apply.

----End
A.6 Managing the MSP

This section provides the operation tasks associated with MSP. Only the OptiX RTN 980
supports the Two-Fiber Bidirectional Ring MSP.
A.6.1 Configuring Linear MSP

You can configure linear MSP to protect services over the optical fibers between two nodes.
Prerequisites
l
The corresponding board must be added on the NE Panel.

U2000
Issue 01 (2016-04-30)

736

Configuration Guide
A Task Collection
NOTE
When an unprotected service is converted into a linear MSP service by configuring the linear
MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.
The system displays the Create a Linear Multiplex Section dialog box.
Step 3 Set the parameters of the linear MSP group.
Step 4 Click OK, and then close the dialog box that is displayed.
----End
Issue 01 (2016-04-30)

737

Configuration Guide
A Task Collection
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.
A.6.2 Querying the Status of the Linear MSP

By using this operation, you can know the current information about the linear MSP.
Prerequisites
l
The linear MSP must be configured.

U2000
NOTE
Procedure
Step 2 Click Query > Query Protection Group to query the current linear MSP group. Then close
the dialog box that is displayed.
Step 3 In Protection Group, click the linear MSP group to be queried.
Step 4 Click Query > Query Switching Status In Slot Mapping Settings, query the status of the
linear MSP.
----End
A.6.3 Performing Linear MSP Switching

By using this operation, you can perform the external switching on the linear MSP.
Prerequisites
l
The protection protocol is enabled.

U2000
Issue 01 (2016-04-30)

738

Configuration Guide
A Task Collection
NOTE
Procedure
Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Settings, select
the working unit or protection unit, and then right-click.
Step 3 Right-click and select the required switching mode.
The confirmation dialog box is displayed.

Step 4 Click OK, and close the dialog box that is displayed.
NOTE
If the switching of a higher priority occurs in a channel, the switching of a lower priority will not occur
in the channel.
----End
A.6.4 Starting/Stopping the Linear MSP Protocol

If you first stop the linear MSP protocol and then start it, the linear MSP status can be
restored to the initial state.
Prerequisites
l

U2000
NOTE
Precautions
l
Issue 01 (2016-04-30)
Stopping the ring MSP protocol causes failure of ring MSP.

739

Configuration Guide
A Task Collection
When services are switched onto the protection channel, stopping the ring MSP protocol
causes the services to switch back to the working channel. At this time, if the working
channel is normal, the services are transiently interrupted; if the working channel is
faulty, the services are interrupted until the working channel is restored to normal or the
protocol is started.
Procedure
Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be
stopped.
Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that is
displayed.
Step 4 Click Query > Query Protection Group, close the dialog box that is displayed, and check
Protocol Status.
----End
A.6.5 Configuring Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you
can configure ring MSP to provide protection for the ring network.
Prerequisites

U2000
NOTE
l
Only OptiX RTN 980 support this operation.
The number of nodes on an MSP ring should not exceed 16.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.
Step 3 Click Yes.
The Create a Multiplex Section Ring dialog box is displayed.
Issue 01 (2016-04-30)

740

Configuration Guide
A Task Collection
Step 4 Set parameters of the ring MSP protection group as planned.
----End
A.6.6 Querying Ring MSP Status

This topic describes how to check the current status of a ring MSP protection group.
Prerequisites
l
A ring MSP protection group has been configured.

U2000
NOTE
Issue 01 (2016-04-30)

741

Configuration Guide
A Task Collection
Procedure
Step 2 Click Query.
Step 3 Select Query Protection Group from the drop-down list. Then, close the dialog box that is
displayed. In Protection Group, check basic information about the protection group.
Step 4 Select the required protection group and click Query.
Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is
displayed. In Slot Mapping Relation, check the switching status of the protection group.
----End
A.6.7 TriggeMSP ring Ring Switching

This topic describes how to trigger external MSP ring switching.
Prerequisites
l
MSP Ring has been configured for a service.
The MSP ring protocol has been enabled.

U2000
NOTE
NOTICE
All switching operations except exercise switching may interrupt services.
Procedure
Step 2 Select the required service, right-click the service, and select a switching mode from the dropdown list.
Then, a confirmation dialog box is displayed.
Step 3 Click Yes. Then, close the dialog box that is displayed.
Issue 01 (2016-04-30)

742

Configuration Guide
A Task Collection
Step 4 Click Query.

displayed.
Step 6 Check whether the service is already switched to the protection channel.
----End
A.6.8 Starting/Stopping the MSP Ring Protocol

If you first stop the MSP ring protocol and then start it, the MSP ring protocol is restored to
its initial state.
Prerequisites
l
MSP Ring has been configured for a service.

U2000
Procedure
Step 2 Stop the MSP ring protocol.
1.
Select the required protection group and click Stop Protocol.
NOTICE
After the MSP ring protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the MSP ring protocol is
restarted, if services have been switched to the protection channel.
2.
Click Yes. Then, close the dialog box that is displayed.
Step 3 Start the MSP ring protocol.

1.
Select the required protection group. Click Start Protocol. Then, close the dialog box
that is displayed.
----End
A.6.9 Creating a Packet-based Linear MSP Group

This section describes how to add channelized STM-1 ports into a packet-based linear MSP
group.
Issue 01 (2016-04-30)

743

Configuration Guide
A Task Collection
Prerequisites
l
The corresponding boards have been added in the NE Panel.

U2000
NOTE
l
When an unprotected service is converted into a linear MSP service by configuring the
packet-based linear MSP, the service is not interrupted.
Only the 1:1 packet-based linear MSP can be created.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packetbased linear MS from the Function Tree.
The Create a Packet-based Linear Multiplex Section dialog box is displayed.
Step 3 Configure the parameters for the new linear MSP group.
Issue 01 (2016-04-30)

744

Configuration Guide
A Task Collection
Step 4 Click OK to close the displayed dialog box.

----End
Follow-up Procedure
In the case of the 1:1 linear MSP, you need to configure bidirectional cross-connections
between the services and the working channel. If extra services need to be transmitted, you
need to configure bidirectional cross-connections between the extra services and the
protection channel.
A.6.10 Querying the Status of a Packet-based Linear MSP Group

This section describes how to query the current status of a packet-based linear MSP group.
Prerequisites
l
A packet-based linear MSP group has been configured.

U2000
NOTE
Procedure
Step 2 Choose Query > Query Protection Group and close the dialog box displayed.
Step 3 Select the packet-based linear MSP group whose protection status needs to be queried in
Protection Group.
Step 4 Choose Query > Query Switching Status. Query the status of the packet-based linear MSP
group in Slot Mapping Relation.
----End
A.6.11 Performing Packet-based Linear MSP Switching

This section describes how to perform an external switchover on a packet-based linear MSP
group.
Prerequisites
l
The linear MSP protocol has been enabled.
Issue 01 (2016-04-30)

745

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 2 Select the MSP group on which the switching is to be performed in Protection Group and
right-click the working or protection unit in Slot Mapping Relation.
Step 3 Choose the desired switching mode from the shortcut menu.

NOTE
If switching of a higher priority has occurred on the working or protection channel, the configured
switching will not be triggered.
----End
A.6.12 Enabling/Disabling the Linear MSP Protocol

This section describes how to restore the linear MSP protocol to the initial state by first
disabling the protocol and then enabling the protocol.
Prerequisites
l

U2000
NOTE
Issue 01 (2016-04-30)

746

Configuration Guide
A Task Collection
Precautions
l
Disabling the linear MSP protocol causes the failure of the linear MSP.
When services are switched to the protection channel, disabling the linear MSP protocol
switches the services back to the working channel. At this time, if the working channel is
normal, the services are transiently interrupted. If the working channel is faulty, the
services are interrupted until the working channel is restored to normal or the linear MSP
Procedure
Step 2 Select the protection group for which the linear MSP protocol needs to be disabled in
Protection Group.
Step 3 Click Start Protocol or Stop Protocol and close the dialog box displayed.
Step 4 Choose Query > Query Protection Group and close the dialog box displayed. View
Protocol Status.
----End
A.7 Managing TDM Services

The TDM services involve the SDH service and the PDH service.
A.7.1 Creating the Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service
sink.
Prerequisites
l
The corresponding source and sink boards must be added on NE Panel.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
Issue 01 (2016-04-30)

747

Configuration Guide
A Task Collection
NOTE
If you create the cross-connections of point-to-point services using the Web LCT, perform the following
operations:
Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.

NOTE
If you create the cross-connections of point-to-point services using the Web LCT, perform the following
operations:
Click New.
The Create SDH/PDH Service dialog box is displayed.

Step 4 Configure the parameters of a new SDH/PDH service.
Step 5 Click OK and close the displayed dialog box.

----End
A.7.2 Creating Cross-Connections of SNCP Services

The cross-connection of SNCP services is a cross-connection that a working source and a
protection source correspond to a service sink.
Prerequisites
l
The corresponding source and sink boards must be added on NE Panel.

U2000
NOTE
Issue 01 (2016-04-30)

748

Configuration Guide
A Task Collection
Procedure
Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
NOTE
If you create the cross-connections of SNCP services using the Web LCT, perform the following operations:
Click Scheme to change the VC-12 timeslot numbering policy used by the cross-connection.
Step 3 Click Create SNCP Service.

NOTE
If you create the cross-connections of SNCP services using the Web LCT, perform the following operations:
Click Create SNCP.
The Create SNCP Service dialog box is displayed.

Step 4 Configure the parameters of a new SNCP service.

----End
A.7.3 Modifying the Priorities of E1 Services

This section describes how to adjust the priorities of E1 services.
Prerequisites
l
The corresponding source and sink boards must be added in the NE Panel.
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.
Issue 01 (2016-04-30)

749

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 2 Click Query, A confirmation dialog box is displayed, Click Yes.
Step 3 Select an E1 service in Cross-Connection.
Step 4 Right-click the E1 service and choose Expand to Unidirectional from the shortcut menu.
Step 5 Right-click the E1 service and choose Deactivate from the shortcut menu.
NOTE
Step 6 In the displayed dialog box, click Yes. In the second displayed dialog box, click OK and close
the dialog box that is displayed.
NOTE
Step 7 If the number of E1 services configured on an IF board is smaller than Full E1 Capacity,
select the required E1 service, right-click the service, and choose Modify from the short-cut
menu. Then, change the E1 priority of each timeslot in the dialog box that is displayed.
NOTE
If you modify the priorities of E1 services using the Web LCT, perform the following operations:
If the number of E1 services configured on an IF board is smaller than Full E1 Capacity, double-click E1
Priority and select the target E1 priority from the drop-down list.
NOTE
For an SNCP service, you need to modify E1 Priority of only the services that are transmitted to the
working source and the protection source of the SNCP service.
Issue 01 (2016-04-30)

750

Configuration Guide
A Task Collection
Step 8 If the number of E1 services configured on an IF board is the same as Full E1 Capacity, do
as follows to interchange the priority levels of two E1 services:
1.
Add one to Full E1 Capacity for both ends of the radio link.
2.
Change E1 Priority of the E1 service with a higher priority to Low.
3.
Change E1 Priority of the E1 service with a lower priority to High.
4.
Change Full E1 Capacity to the original values for both ends of the radio link.
NOTE
If Full E1 Capacity uses its maximum value, do as follows to interchange the priority levels of two services.
1. Delete either E1 service.
2. Change the priority of the other E1 service.
3. Add the E1 service that was deleted, setting its E1 Priority to the required value.

----End
A.7.4 Inserting E1_AIS upon a TU_AIS Condition

Perform this operation to configure the function of inserting the TU_AIS upon E1_AIS
detection.
Prerequisites

U2000
NOTE
Context
This operation applies to IF boards that support Integrated IP microwave.
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.
Issue 01 (2016-04-30)

751

Configuration Guide
A Task Collection
NOTE
Generally, it is recommended that Auto take its default value.
Step 3 Click Apply.

----End
A.7.5 Configuring the Automatic Switching of SNCP Services

You can manually add certain alarms for the automatic switching of SNCP services.
Prerequisites
l
The SNCP protection group must be configured.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP
Service Control from the Function Tree.
Step 2 Select the SNCP protection group, and then right-click Switching Condition to which the
working service corresponds.
NOTE
If you configure the automatic switching of SNCP services using the Web LCT, perform the following
operations:
Select the SNCP protection group, and then right-click SD Initiation Condition to which the working service
corresponds.
Step 3 Set the initiation condition for the working service. Click OK.
NOTE
The conditions for automatic switching of higher order services are different from those of lower order
services.
Step 4 Right-click Switching Condition to which the protection service corresponds.

Issue 01 (2016-04-30)

752

Configuration Guide
A Task Collection
NOTE
If you configure the automatic switching of SNCP services using the Web LCT, perform the following
operations:
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 Switching Condition of the working service to be the same as
Switching Condition of the protection service.
If you configure the automatic switching of SNCP services using the Web LCT, it is recommended that
you set Switching Condition of the working service to be the same as Switching Condition of the
protection service.
Step 6 Click Apply, and then close the dialog box that is displayed.
----End
A.7.6 Deleting Cross-Connections

When a service is not used, you can delete the cross-connections of this service to release the
corresponding resources.
Prerequisites
l
The cross-connections of the service must be configured and the service must not be
used.

U2000
NOTE
Procedure
NOTE
If you delete cross-connections using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-Connection
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.
Step 3 Deactivate the service.

Issue 01 (2016-04-30)

753

Configuration Guide
A Task Collection
NOTE
1.
Right-click the service and choose Deactivate from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to deactivate the selected
service.
2.
Click Yes.
Then, a dialog box is displayed, indicating that this operation will clear the
corresponding service data on the NE side.
3.
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.
Click OK. Then, close the dialog box that is displayed.
Step 5 Click Query. The queried information should show that the cross-connection is already
deleted.
----End
A.7.7 Converting a Normal Service into an SNCP Service

By converting a normal service into an SNCP service, you can convert the unidirectional
cross-connections of a normal service into the unidirectional cross-connection in the receive
direction of the SNCP service.
Prerequisites
l
The unidirectional cross-connection of the normal service must be configured and the
source of the cross-connection must be a line board.

U2000
NOTE
When this task is performed to convert a normal service into an SNCP service, the original
services are not interrupted.
Procedure
Service Configuration from the Function Tree.
Issue 01 (2016-04-30)

754

Configuration Guide
A Task Collection
NOTE
If you convert a normal service into an SNCP service using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Cross-Connection
Step 2 Optional: If a bidirectional SDH service is created, select this service in Cross-Connection.
Right-click the selected service and choose Expand to Unidirectional from the shortcut
menu.
NOTE
If a bidirectional SDH service is created, select this service in Cross-Connection. Right-click the selected
service and choose Expand from the shortcut menu.
Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.
NOTE
Select the unidirectional service. Right-click the selected service and choose Convert to SNCP from the
shortcut menu.
Then, a dialog box is displayed, querying whether you need to perform this operation.Then,
the Convert to SNCP Service dialog box is displayed.
Step 4 Click Yes.
NOTE
Then, the Create SNCP Service dialog box is displayed.

Step 5 Set the parameters of the SNCP service.
Step 6 Click OK.

----End
Issue 01 (2016-04-30)

755

Configuration Guide
A Task Collection
A.7.8 Converting an SNCP Service to a Normal Service

By converting an SNCP service to a normal service, you can convert the SNCP crossconnection 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
NOTE
When this task is performed to convert an SNCP service into a normal service, the original
services are not interrupted.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Service Configuration from the Function Tree.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree.
Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and choose
Convert to Non-Protection Service from the shortcut menu.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
In Auto-Created Cross-Connection, select the configured service and click Service Convert. Choose
SNCP Protection Service Convert to Non-Protection Service or SNCP Working Service Convert to
Non-Protection Service from the displayed menu.
To convert the cross-connection into a cross-connection between the working source and the service sink,
choose SNCP Working Service Convert to Non-Protection Service. To convert the cross-connection into a
cross-connection between the protection source and the service sink, choose SNCP Protection Service
Convert to Non-Protection Service.
Then, a dialog box is displayed, querying whether you need to perform this operation.
Step 3 Click OK.
----End
Issue 01 (2016-04-30)

756

Configuration Guide
A Task Collection
Follow-up Procedure
You also need to delete the unidirectional cross-connection between the service source and the
working path or the unidirectional cross-connection between the service source and the
protection path. The SNCP service can be converted into the normal service both in the
receive direction and the transmit direction only after the deletion.
A.7.9 Querying TDM Services

You can learn information about the TDM services that are configured for an NE by querying
TDM services.
Prerequisites
l
TDM services must be configured.

U2000
NOTE
Procedure
NOTE
If you query TDM services using the Web LCT, perform the following operations:
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > CrossConnection Configuration from the Function Tree.
Step 2 Click Query.

Step 3 In the displayed dialog box for confirmation, click Yes.
Step 4 Close the displayed prompt dialog box. In Cross-Connection, query the TDM services.
----End
A.7.10 Switching SNCP Services

You can perform external switching on SNCP services by performing this operation.
Prerequisites
l

U2000
Issue 01 (2016-04-30)

757

Configuration Guide
A Task Collection
NOTE
Procedure
Step 2 Select the SNCP protection group for SNCP service switching.
Step 3 Click Function. Select the required switching mode from the displayed menu.
Step 4 In the displayed dialog box for confirmation, click OK.
Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then,
close the displayed prompt dialog box.
Step 6 Choose Function > Query Switch Status to check whether the switching operation is
successful.
----End
A.7.11 Querying the Protection Status of SNCP Services

You can know the current information of an SNCP service by querying the protection status
of SNCP services.
Prerequisites
l

U2000
NOTE
Procedure
Step 2 Select the SNCP protection group whose service protection status needs to be queried.
Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box.
----End
A.8 Managing Ports

Setting correct port parameter is the basis of configuring ports that transmit services.
Issue 01 (2016-04-30)

758

Configuration Guide
A Task Collection
A.8.1 Setting the Parameters of SDH Ports

The parameters of SDH ports are used to configure the loopback on the SDH interface board
and the laser status.
Prerequisites
l

U2000
NOTE
Procedure
Configuration > Interface Management > 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
A.8.2 Setting Working Modes of E1 Ports

You can set the working mode for an E1 port that supports various working modes to the
TDM or packet mode.
Issue 01 (2016-04-30)

759

Configuration Guide
A Task Collection
Prerequisites

U2000
NOTE
Context
NOTE
l For OptiX RTN 905 housing an MN1 board, you can set Service Mode for ports on the logical board
l For OptiX RTN 950A housing an MN1 board, you can set Service Mode for ports on the logical board
Procedure
Step 1 In the NE Explorer, select the 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.
MP1/VS2 configuration based on E1 ports:
CD1 configuration based on STM-1 ports (63 E1 channels work in the same mode):
----End
A.8.3 Setting the Parameters of PDH Ports

The parameters of PDH ports are used to configure the tributary loopback, service load
indication, and tributary retiming.
Prerequisites
l
Issue 01 (2016-04-30)

760

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Configuration > PDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel).
Step 3 Select Port from the list box.
Step 4 Configure the parameters of PDH ports.
NOTE
On RTN 950A housing SLF2CSHO, Port Service Type can be set to T1 for PDH ports on SP3S/SP3D.
Step 5 Click Apply.

Step 6 Click Yes.
The dialog box is displayed again for confirmation.
Step 7 Click Yes, and then close the dialog box that is displayed indicating the operation result.
----End
A.8.4 Configuring Overhead Bytes

Generally, the default overload bytes can meet the requirements of the device. In certain
special application scenarios, however, such as device interconnection, you need to change
the overload bytes according to the requirements of the interconnected device.
A.8.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

U2000
Issue 01 (2016-04-30)

761

Configuration Guide
A Task Collection
NOTE
Procedure
Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Configure the J0 byte.
1.
Double-click the parameter whose value needs to be changed.

The Please Input the Overhead Byte dialog box is displayed.
2.
Configure overhead bytes.
3.
Click OK.
Step 4 Click Apply.

Step 5 Click Yes, and then close the dialog box that is displayed indicating the operation result.
----End
A.8.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).
Issue 01 (2016-04-30)

762

Configuration Guide
A Task Collection
Prerequisites
l

U2000
NOTE
Procedure
Step 1 Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration
> Overhead Management > VC4 Path Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Optional: Configure the J1 byte.
1.
Click the Trace Byte J1 tab.
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.
Issue 01 (2016-04-30)

763

Configuration Guide
4.
A Task Collection
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
A.8.4.3 Configuring VC-12 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

U2000
NOTE
Procedure
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.
Step 2 Configure the J2 byte.
1.
Click the Trace Byte J2 tab.
2.
Choose Display in Text Format or Display in Hexadecimal.
3.

The Please input the overhead byte dialog box is displayed.
4.
Issue 01 (2016-04-30)

764

Configuration Guide
5.
Click OK.
6.
Click Apply.
7.
Click OK, and then close the dialog box that is displayed.
A Task Collection
Step 3 Configure the signal flag.

1.
Click the Signal Flag V5 tab.
2.
Click Options.
The Options dialog box is displayed.
3.
Click Extended Mode.
4.
Click OK.
5.
Configure the signal flag in the V5 byte.
6.
Click Apply.
7.
Click OK, and then close the dialog box that is displayed.
----End
Issue 01 (2016-04-30)

765

Configuration Guide
A Task Collection
A.8.5 Changing the E1 Frame Format and Frame Mode for a

Channelized STM-1
By default, the E1 frame format in a channelized STM-1 is CRC-4 multiframe and the frame
mode is PCM31.
Prerequisites
l
The corresponding boards must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select a channelized STM-1 interface board from the Object Tree and
choose Configuration > Interface Management > Path Configuration from the Function
Tree.
Step 2 Set the required parameters.
Step 3 Click Apply.

----End
A.8.6 Setting Smart E1 Port Parameters

Smart E1s can be configured as CES E1s, ATM E1s, or MLPPP E1s.
Context
NOTE
RTN 905 does not support ATM services.
A.8.6.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
l
Issue 01 (2016-04-30)
For an E1 port on the logical board MP1 of an OptiX RTN 905, Service Mode has been
set to CES. For information about how to set Service Mode of an E1 port to CES, see
A.8.2 Setting Working Modes of E1 Ports.
766

Configuration Guide
A Task Collection
For an OptiX RTN 950A that houses an MN1 board, set Service Mode of the ports on
the logical board MP1 to CES by following instructions in A.8.2 Setting Working
Modes of E1 Ports.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration >
Interface Management > PDH Interface from the Function Tree.
Step 2 Click the Basic Attributes tab.
Step 3 Select the required port and set the parameters.
----End
A.8.6.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.
Issue 01 (2016-04-30)

767

Configuration Guide
A Task Collection
Prerequisites
l
set to CES. For information about how to set Service Mode of an E1 port to CES, see
A.8.2 Setting Working Modes of E1 Ports.
For an OptiX RTN 950A that houses an MN1 board, set Service Mode of the ports on
the logical board MP1 to CES by following instructions in A.8.2 Setting Working
Modes of E1 Ports.

U2000
NOTE
Procedure
Step 3 Select the required port and set the parameters for its advanced attributes.
Step 4 Click Apply.

----End
A.8.7 Setting Serial Port Parameters

When some 64 kbit/s timeslots of an Smart E1 port are used for transmitting ATM services,
these timeslots can be considered a serial port. When some E1s in a channelized STM-1 are
used as PPP links, these PPP links are also considered a serial port.
A.8.7.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.
Issue 01 (2016-04-30)

768

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Interface Management > Serial Interface from the Function Tree.
Step 3 Click New.
The New Serial Interface dialog box is displayed.
Step 4 Set the parameters for the serial port according to the planning information.
----End
A.8.7.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
NOTE
Issue 01 (2016-04-30)

769

Configuration Guide
A Task Collection
Procedure
Interface Management > Serial Interface from the Function Tree.
Step 3 Select the required port and set the parameters for the serial port according to the planning
information.
----End
A.8.8 Setting Ethernet Port Parameters

Ethernet port parameters include basic attributes, traffic control, Layer-2 attributes, Layer-3
attributes, and advanced attributes.
A.8.8.1 Setting the Basic Attributes of Ethernet Ports

Basic Ethernet port attributes define the physical-layer information, such as the interface
Prerequisites
l
The Ethernet board must be added on the NE Panel.

U2000
NOTE
Procedure
Management > Ethernet Interface from the Function Tree.
Step 3 Set basic Ethernet port attributes.
Issue 01 (2016-04-30)

770

Configuration Guide
A Task Collection
NOTE
l Specifies the level of services that a port carries.

l If Port Mode is Layer 2, the port can carry native Ethernet services.
l If Port Mode is Layer 3, the port can carry MPLS tunnels.
l If Port Mode is Layer Mix, the port can carry both native Ethernet services and MPLS tunnels.
l This parameter specifies the method of the port to process the received packets.
l This parameter is valid only when Port Mode is Layer 2.
l If you set Encapsulation Type to Null, the port transparently transmits the received packets.
l If you set Encapsulation Type to 802.1Q, the port identifies the packets that comply with the IEEE
802.1q standard.
l If you set Encapsulation Type to QinQ, the port identifies the packets that comply with the IEEE
802.1ad QinQ standard.
l The Ethernet ports of different types support different Working Mode. For details, see the IDU
Hardware Description.
l When the equipment on the opposite side works in auto-negotiation mode, set the Working Mode of
the equipment on the local side to Auto-Negotiation.
l When the equipment on the opposite side works in full-duplex mode, set the Working Mode of the
equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex
depending on the port rate of the equipment on the opposite side.
l When the equipment on the opposite side works in half-duplex mode, set the Working Mode of the
equipment on the local side to 10M Half-Duplex, 100M Half-Duplex.
l The value of Max Frame Length(byte) should be greater than the length of any frame to be
transported.
Step 4 Click Apply and close the displayed dialog box.

----End
A.8.8.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

U2000
NOTE
Procedure
Step 2 Click the Flow Control tab.
Issue 01 (2016-04-30)

771

Configuration Guide
A Task Collection
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 OptiX RTN 900 supports only two auto-negotiation flow control modes, namely, Disabled mode
and Enable Symmetric Flow Control mode.
l Non-Autonegotiation Flow Control Mode is valid only when Working Mode is not set to 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 OptiX RTN 900 supports only two non-auto-negotiation flow control modes, namely, Disabled
mode and Enable Symmetric Flow Control mode.

----End
A.8.8.3 Setting the Layer 2 Attributes of Ethernet Ports

Ethernet port Layer 2 attributes define link-layer information.
Prerequisites
l

U2000
NOTE
Procedure
Step 2 Click the Layer 2 Attributes tab.
Issue 01 (2016-04-30)

772

Configuration Guide
A Task Collection
Step 3 Set Ethernet port Layer 2 attributes.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set
QinQ Type Domain. The default value is 88A8.
l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot
set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be
changed.
l If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to Tag Aware.
l If all the accessed services are frames without the VLAN tag (untagged frames), set TAG to Access.
l If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid.
l Default VLAN ID is valid only when TAG is set to Access or Hybrid.
l VLAN Priority is valid only when TAG is set to Access or Hybrid.
Step 4 Click Apply.

----End
A.8.8.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
NOTE
Procedure
Interface Management > Ethernet Interface from the Function Tree.
Issue 01 (2016-04-30)

773

Configuration Guide
A Task Collection
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
A.8.8.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.
Prerequisites
l

U2000
NOTE
Procedure
Step 3 Set Ethernet port advanced attributes.

----End
Issue 01 (2016-04-30)

774

Configuration Guide
A Task Collection
A.8.9 Setting Microwave Port Parameters

Microwave ports are also called IF_ETH ports. 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.8.9.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
NOTE
Procedure
Step 3 Set basic IF_ETH port attributes.
NOTE
l This parameter specifies the level of services that a port carries.

l If Port Mode is Layer 2, the port can carry native Ethernet services.
l If Port Mode is Layer 3, the port can carry tunnels.
l If Port Mode is Layer Mix, the port can carry both tunnels and Native Ethernet services.
l Encapsulation Type specifies the method of the port to process the received packets.
l This parameter is valid only when Port Mode is Layer 2.
l If Encapsulation Type is set to Null, the port transparently transmits the received packets.
l If Encapsulation Type is set to 802.1Q, the port identifies the packets that comply with the IEEE
802.1Q standard.
l If Encapsulation Type is set to QinQ, the port identifies the packets that comply with the IEEE
802.1ad QinQ standard.

----End
Issue 01 (2016-04-30)

775

Configuration Guide
A Task Collection
A.8.9.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
NOTE
Procedure
Step 3 Set IF_ETH port Layer 2 attributes.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set
QinQ Type Domain. The default value is 88A8.
l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot
set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be
changed.
l If all the accessed services are frames that contain the VLAN tag (tagged frames), set Tag to "Tag
Aware".
l If all the accessed services are frames that do not contain the VLAN tag (untagged frames), set Tag
to "Access".
l If the accessed services contain tagged frames and untagged frames, set Tag to "Hybrid".
l Default VLAN ID is valid only when TAG is set to Access or Hybrid.
l VLAN Priority is valid only when TAG is set to Access or Hybrid.

----End
A.8.9.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.
Issue 01 (2016-04-30)

776

Configuration Guide
A Task Collection
Prerequisites
l
Port Mode of the ports on IF boards are set to Layer 3.

U2000
NOTE
Procedure
Interface Management > Microwave Interface from the Function Tree.
Step 3 Set parameters for Layer 3 attributes of the ports on IF boards according to the planning
information.
NOTE
Modifying the IP address may interrupt services.
----End
A.8.9.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
NOTE
Procedure
Issue 01 (2016-04-30)

777

Configuration Guide
A Task Collection
Step 3 Set IF_ETH port advanced attributes.
Step 4 Click Apply and close the displayed dialog box.

----End
A.8.10 Setting IF Port Parameters

This section describes how to set IF port parameters, including IF attributes, ATPC attributes,
and AM attributes.
A.8.10.1 Setting IF Attributes

Set parameters specific to different IF boards.
Prerequisites
l

U2000
NOTE
Procedure
Configuration > IF Interface from the Function Tree.
Step 2 Optional: For a dual-channel IF board, select an IF port.
Step 3 Click the IF Attributes tab.
Step 4 Set the parameters of general attributes.
Issue 01 (2016-04-30)

778

Configuration Guide
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 If the XPIC IF board does not perform the XPIC function, XPIC Enabled should be set to
Disabled.
l Enable IEEE-1588 Timeslot needs to be set consistently between two ends of a radio link.
l If the NE needs to transmit IEEE 1588v2 packets, set Enable IEEE-1588 Timeslot to Enabled. If
the NE does not need to transmit IEEE 1588v2 packets, set Enable IEEE-1588 Timeslot to
Disabled.
l RTN 905, RTN 910A, and ISV3/ISM6 boards on RTN 980/RTN 980L/RTN 950/RTN 950A allow
Alarm and Performance Report to be specified. If Alarm and Performance Report is set to
Disabled, alarms of IF ports and the corresponding ODUs/RFUs are not reported.
l An IF port on an ISU2/ISX2 board can interconnect only with an IF port that supports the IS2 mode.
l RTN 905 1E/2E can work in IS2 or IS3 mode. By default, RTN 905 1E/2E works in IS3 mode. Set
Running Mode to the same value for the two IF units on an RTN 905 2E.
l ISV3 boards can work in IS2 or IS3 mode. By default, ISV3 boards work in IS3 mode.
l IF ports on ISM6 boards can work in IS2, IS3, or IS6 mode. By default, IF ports on ISM6 boards
work in IS6 mode. The two IF ports on an ISM6 board must work in the same mode.
l It is recommended that two interconnected IF ports work in the highest-order mode that they both
support.
l Before switching the running mode of an IF port, delete services on the port.
l If IF ports are configured with services or 1+1, N+1, PLA/EPLA/EPLA+, or LAG protection, their
Running Mode cannot be modified.
l You can set Power Switch for an ISM6 board to turn on or off the power switch of an ODU
connected to the ISM6 board.
Step 5 Configure the parameters of Hybrid/AM attributes for different IF services.
Issue 01 (2016-04-30)

779

Configuration Guide
A Task Collection
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 6 Click Apply.

----End
A.8.10.2 Configuring ATPC Attributes

To configure the ATPC function, set the ATPC attributes of the IF board.
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
NOTE
Procedure
Step 2 Click the ATPC Attributes tab.
Step 3 Set the parameters of ATPC attributes.
Issue 01 (2016-04-30)

780

Configuration Guide
A Task Collection
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
A.8.10.3 Setting Advanced AM Attributes

By performing this operation, you can query and adjust the E1 capacity in each modulation
scheme.
Prerequisites
l
The corresponding IF boards must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from
the Function Tree.
Step 2 Click the AM Advanced Attributes tab.
Step 3 Set each parameter for the advanced AM attributes.
Issue 01 (2016-04-30)

781

Configuration Guide
A Task Collection
NOTE
The E1 service capacity in an intermediate modulation scheme can be changed only after the E1 priority
function is enabled.
Step 4 Click Apply.

----End
A.8.10.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.

U2000
NOTE
Procedure
Step 3 Click Query.
Step 4 Query the AM information in Hybrid/AM Configuration.
----End
A.8.10.5 Querying ATPC Adjustment Records

By querying the ATPC adjustment records, you can view the ATPC running status.
Prerequisites
l
Issue 01 (2016-04-30)

782

Configuration Guide
A Task Collection
The corresponding IF board must be added.

U2000
NOTE
Procedure
Configuration > ATPC Adjustment Records from the Function Tree.
Step 2 Click Query to query the running information.
----End
A.8.10.6 Changing the IF Service Type

This topic describes how to change the IF service type.
Prerequisites
l
The corresponding IF boards have been added in the NE Panel.

U2000
NOTE
Context
NOTE
After the IF service type is changed, the IF board will be reset. Wait until the IF board resets and set
other IF information.
If IF ports are configured with services or 1+1, common N+1, PLA/EPLA/EPLA+, or LAG protection,
their IF service types cannot be changed.
Procedure
Step 3 Change IF Service Type based on the network plan.
Issue 01 (2016-04-30)

783

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.8.10.7 Changing the Running Mode of an IF Port

Two IF ports at two ends of a microwave link hop must work in the same runtime mode.
Prerequisites
l

U2000
NOTE
Context
l
An IF port on an ISU2/ISX2 board can interconnect only with an IF port that supports
the IS2 mode.
RTN 905 1E/2E can work in IS2 or IS3 mode. By default, RTN 905 1E/2E works in IS3
mode. Set Running Mode to the same value for the two IF units on an RTN 905 2E.
ISV3 boards can work in IS2 or IS3 mode. By default, ISV3 boards work in IS3 mode.
IF ports on ISM6 boards can work in IS2, IS3, or IS6 mode. By default, IF ports on
ISM6 boards work in IS6 mode. The two IF ports on an ISM6 board must work in the
same mode.
It is recommended that two interconnected IF ports work in the highest-order mode that
they both support.
Before switching the running mode of an IF port, delete services on the port.
If IF ports are configured with services or 1+1, N+1, PLA/EPLA/EPLA+, or LAG

protection, their Running Mode cannot be modified.
NOTE
When working at a 56 MHz or higher bandwidth, two IF ports on a dual-channel IF board or an RTN 905 2E
cannot switch to the SDH mode. If the two IF ports on a dual-channel IF board or an RTN 905 2E are
required to work in SDH mode at a 56 MHz or higher bandwidth, it is advised to configure a 28 MHz
bandwidth for the two IF ports first, switch their work modes to the SDH mode, and then change the
bandwidth to 56 MHz or higher.
Procedure
Step 3 Change the runtime mode based on the network plan.
Issue 01 (2016-04-30)

784

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.8.10.8 Enabling or Disabling the AM Booster Function

Only ISX2 boards support the AM Booster function.
Prerequisites
l
The corresponding ISX2 board has been added on the NE Panel.
The AM function has been enabled by A.5.1 Configuring a Single-Hop Radio Link.

U2000
NOTE
Only ISX2 boards support the AM Booster function.
Procedure
Step 3 Enable or disable the AM Booster function.
Step 4 Click Apply.

----End
A.8.10.9 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.
Prerequisites
l
Issue 01 (2016-04-30)

785

Configuration Guide
A Task Collection

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 Optional: 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
Modulation Mode of the Guarantee AM Capacity.
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. Perform Step 6 to enable the AM function.
2. Click Apply.
Step 8 Optional: Change the number of high-priority E1 services (namely, Guarantee E1
Capacity) in a radio link.
Issue 01 (2016-04-30)

786

Configuration Guide
If...
A Task Collection
Then...
You need to reduce 1. Perform A.7.6 Deleting Cross-Connections to delete

the number of highunnecessary E1 services.
priority E1 services 2. Decrease Guarantee E1 Capacity.
3. Click Apply.
You need to increase 1. Increase Guarantee E1 Capacity.
the number of high- 2. If Enable E1 Priority is Enabled, increase Full E1 Capacity
priority E1 services
accordingly.
3. Click Apply.
4. Perform A.7.1 Creating the Cross-Connections of Point-toPoint Services or A.7.2 Creating Cross-Connections of SNCP
Services to add required E1 services.
NOTE
l Full E1 Capacity is the total number of high-priority 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 1. Perform A.7.6 Deleting Cross-Connections to delete

the number of lowunnecessary E1 services.
priority E1 services 2. Decrease Full E1 Capacity.
3. Click Apply.
You need to
1. If Enable E1 Priority is Disabled, change Enable E1 Priority
increase the
to Enabled.
number of low2. Increase Full E1 Capacity.
priority E1 services
3. Click Apply.
4. Perform A.7.1 Creating the Cross-Connections of Point-toPoint Services or A.7.2 Creating Cross-Connections of SNCP
Services to add required E1 services.
l Full E1 Capacity is the total number of high-priority E1 services
and low-priority E1 services.
l Adding low-priority E1 services does not affect original E1
services.
----End
A.8.11 Setting RFU/RFU-SD/ODU Port Parameters

This section describes how to set RFU/RFU-SD/ODU port parameters, including the transmit
frequency attributes, power attributes, RFU/RFU-SD/ODU information, and advanced
attributes.
Issue 01 (2016-04-30)

787

Configuration Guide
A Task Collection
A.8.11.1 Setting ODU Transmit Frequency Attributes

The ODU transmit frequency attributes define the DOU transmit frequency and T/R spacing.
Prerequisites
l
The IF boards and the ODU to which the IF boards are connected must be added on the
NE Panel.

U2000
NOTE
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
Step 2 Click the Radio Frequency Attributes tab.
Step 3 Configure Transmit Frequency(MHz) and T/R Spacing(MHz) of the ODU.
NOTE
l The value of Transmit Frequency(MHz) must not be less than the sum of the minimum transmit
frequency supported by the RFU/RFU-SD/ODU and a half of the channel spacing, and must not be
more than the difference between the maximum transmit frequency supported by the RFU/RFUSD/ODU and a half of the channel spacing.
l The difference between the transmit frequencies at both ends of a radio link by ODU 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
A.8.11.2 Querying ODU Information

ODU information provides details about the ODU.
Prerequisites
l
The IF boards and theODUs to which the IF boards are connected must be added on the
NE Panel.
Issue 01 (2016-04-30)

788

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Configuration > ODU Interface from the Function Tree.
Step 2 Click the Equipment Information tab.
Step 3 Click Query to obtain the information about the ODU.
----End
A.8.11.3 Setting ODU Power Attributes

The ODU power attributes define the transmit power and receive power of the ODU.
Prerequisites
l
The IF boards and the ODUs to which the IF boards are connected must be added on the
NE Panel.

U2000
NOTE
Procedure
Step 1 Customize the configuration procedure by equipment.
Option
Description
If the Equipment Type Is...
Then...
ODU
Perform steps 2 to 5.
RFU/RFU-SD
Step 3 Click the Power Attributes tab.
Step 4 Set the parameters of ODU power attributes.
Issue 01 (2016-04-30)

789

Configuration Guide
A Task Collection
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 RFU/RFU-SD/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 RFU/RFU-SD/ODU. This parameter cannot be set to a value that exceeds the nominal
power rang of the RFU/RFU-SD/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 RFU/RFU-SD/ODU
and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically
enables the antenna misalignment indicating function.
l Power to Be Received(dBm) is set according to the network plan. When this parameter takes the
default value, the antenna misalignment indicating function is disabled.
l TX High Threshold(dBm) and TX Low Threshold(dBm) are valid only when the ATPC function
is enabled.
Step 5 Click Apply.

----End
A.8.11.4 Setting ODU Advanced Attributes

ODU advanced attributes define the ODU transmit status.
Prerequisites
l
The IF boards and the ODU to which the IF boards are connected must be added on the
NE Panel.

U2000
NOTE
Procedure
Step 3 Configure the ODU parameters, such as Configure Transmission Status.
Issue 01 (2016-04-30)

790

Configuration Guide
A Task Collection
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
A.8.12 Creating VLAN Sub-Interfaces

When LSPs need to traverse a Layer 2 network or be transmitted together with Native
Ethernet services, you need to create VLAN sub-interfaces.
Prerequisites
l
Ethernet boards and IF boards have been added on the NE Panel.
Port Mode has been set to Layer Mix for Ethernet boards and IF boards.

U2000
NOTE
Context
VLAN sub-interfaces are similar to Layer 3 ports. By configuring Layer 3 port attributes for
VLAN sub-interfaces, you can create MPLS tunnel-based services. After being received by
access-layer RTN equipment and then mapped into an MPLS tunnel, services are allocated
different VLAN IDs at VLAN sub-interfaces in compliance with configuration requirements
for the third-party network that the services need to traverse. In this manner, services are
differentiated and therefore correctly forwarded on the third-party network.
Procedure
Interface Management > Ethernet Virtual Interface from the Function Tree.
Step 3 Choose New > Create Ethernet Virtual Interface.
The Create Ethernet Virtual Interface dialog box is displayed.
Step 4 Set VLAN sub-interface parameters.
Issue 01 (2016-04-30)

791

Configuration Guide
A Task Collection
Step 5 Click OK.

----End
A.9 Configuring Native Ethernet Services and Features

Configurations of Native Ethernet services and features include Ethernet port, protection,
service, protocol, and OAM configurations.
A.9.1 Managing ERPS

Ethernet ring protection switching (ERPS) can be configured on the FE/GE ring or Integrated
IP microwave ring to protect the Ethernet service.
A.9.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, or IF boards must be added to the NE Panel.

U2000
Issue 01 (2016-04-30)

792

Configuration Guide
A Task Collection
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet
Protection > ERPS Management.
Step 2 Click New.
The Create Ethernet Ring Protection Protocol Instance dialog box is displayed.
Step 3 Set the parameters for the ERPS protection instance.
NOTE
l It is recommended that you plan the counterclockwise direction as the main direction of services
transmission, and plan the port that transmits services in the main direction as an east port, and the port
that receives services as a west port.
l Set East Port or West Port to - for the sub-ring ERPS instance on an interconnection node.
l Set ERP Ring Node Flag and Flag Port to matching values according to the network plan by taking the
following suggestions:
Only one node on the ring can be set as the RPL owner or RPL neighbor node for each Ethernet
ring.
If the node is the RPL owner, set this parameter to RPL Port.
If the node is an RPL neighbor node, set this parameter to Neighbor Port.
If the node is the next-hop node of the RPL owner or RPL neighbor node, set this parameter to Next
Neighbor Port.
It is recommended that you set the east port of the RPL owner to RPL Port and the west port of the
RPL neighbor node to Neighbor Port.
It is recommended that you set the east port on RPL owner node's upstream node and the west port
on the RPL neighbor node's downstream node as Next Neighbor Port.
If the node on the ring is not any of the preceding nodes, set this parameter to None.
l This parameter generally takes the default value Revertive. You can set this parameter to Non-Revertive
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
Issue 01 (2016-04-30)

793

Configuration Guide
A Task Collection
A.9.1.2 Setting Global ERPS Protocol Parameters

Configured global ERPS protocol parameters take effect to all ERPS instances.
Prerequisites
l
The ERPS protection instance must be created.

U2000
NOTE
Procedure
Protection > ERPS Management from the Function Tree.
Step 2 Set the parameters of Ethernet ring protocol.
NOTE
Set the parameters according to the network plan. Default values are recommended.
Step 3 Click Apply.

----End
A.9.1.3 Setting Protocol Parameters for an ERPS Instance

Protocol parameters set for an ERPS instance take effect only to the ERPS instance.
Prerequisites
l
Ethernet boards and IF boards have been added to the NE Panel.

U2000
NOTE
Issue 01 (2016-04-30)

794

Configuration Guide
A Task Collection
Procedure
Step 2 Set the parameters for the ERPS instance.
NOTE
In this step, you can set Compatible_Version, Virtual Channel Status, Virtual Channel VLANs, and
Major ERPS Ring ID, and query or modify other ERPS instance protocol parameters.
l For multi-ring networks, Compatible_Version for all ring nodes must be ver2.
l For details about values of Virtual Channel Status and Virtual Channel VLANs, refer to Planning
Guidelines for R-APS Virtual Channels in the Feature Description.
l Set this parameter only for the sub-ring ERPS instance on an interconnection node to associate the subring ERPS instance with the major ring ERPS instance.
Step 3 Click Apply.

----End
A.9.1.4 Creating a Virtual Channel VLAN Forwarding Table

You need to create a virtual channel VLAN forwarding table on an interconnection node.
Prerequisites
l
A multi-ring ERPS instance has been created.

U2000
NOTE
NOTE
l A virtual channel VLAN forwarding table needs to be created only for sub-rings. The sub-rings need to
be associated with corresponding major rings.
l Virtual Channel Status must have been enabled and Virtual Channel VLANs must have been correctly
set for the major ring by A.9.1.3 Setting Protocol Parameters for an ERPS Instance.
Procedure
Step 2 Select the sub-ring.
Step 3 Click Virtual Channel VLAN Forwarding Table.
The Virtual Channel VLAN Forwarding Table dialog box is displayed.
Issue 01 (2016-04-30)

795

Configuration Guide
A Task Collection
Step 4 Click New.

The Create Virtual Channel VLAN Forwarding Table dialog box is displayed.
Step 5 Configure the parameters for the virtual channel VLAN forwarding table.
NOTE
l The system automatically displays the ID of the sub-ring ERPS instance and the ERPS ID of the major
ring with which the sub-ring ERPS instance is associated.
l Set Virtual Channel VLAN to the control VLAN ID of the sub-ring R-APS virtual channel.
l Set Virtual Channel VLAN on Major Ring to the Virtual Channel VLANs of the associated major
ring node.
Step 6 Click OK.

Step 7 Click Close.
----End
A.9.1.5 Setting Parameters for Switching Upon Multiple Failures

This section describes how to set parameters to minimize segmentation on an ERPS-protected
network after multiple failures occur.
Prerequisites
l
The mapping IF boards and RFUs have been added on the NE Panel.

U2000
NOTE
Precautions
l
Understand the network topology and properly configure parameters for switching upon
multiple failures to ensure that proper switching can be triggered on an ERPS sub-ring.
Otherwise, normal services may be interrupted. For details about the switching principles
for minimization of segmentation, see Feature Description.
It is advised to configure a bound MEP for an interconnection node sub-ring port when
the network is normal.
Modify Interconnected Node and Multi-point Failure only after multiple failures
occur. Restore the two parameters to default values immediately after faults are rectified.
Issue 01 (2016-04-30)

796

Configuration Guide
A Task Collection
Procedure
Step 2 Set parameters for switching upon multiple failures.
1.
Select the desired ERPS sub-ring instance.
2.
Optional: Configure a bound MEP for a sub-ring port.
3.
Optional: Set Interconnected Node and Multi-point Failure.
4.
Click Apply.
----End
A.9.1.6 Performing an External ERPS Switchover

This section describes how to perform an external ERPS switchover.
Prerequisites

U2000
NOTE
Procedure
Step 2 Select the desired ERPS instance.
Step 3 Click Switching and select an external switch command from the drop-down list.
Issue 01 (2016-04-30)

797

Configuration Guide
A Task Collection
Step 4 Confirm displayed dialog boxes.

Step 5 Close the dialog box indicating the switchover result.
----End
A.9.1.7 Querying the Status of the Ethernet Ring Protocol

By performing this operation, you can discover the current status of Ethernet ring protection
switching (ERPS).
Prerequisites

U2000
NOTE
Procedure
Step 2 Click Query.
Step 3 Query the status of the Ethernet ring protocol.
----End
A.9.2 Managing the LAG

Link aggregation allows one or multiple links that are attached to the same equipment to be
aggregated together to form a LAG. The aggregated links can be considered as a single
logical link by the MAC address. In this manner, the bandwidth is increased and the
availability of the links is improved.
Issue 01 (2016-04-30)

798

Configuration Guide
A Task Collection

Between two NEs, if the bandwidth and availability of the Ethernet links need to be
improved, the new LAG must be created.
Prerequisites
l
The board on which the LAG port to be created must be added to the NE Panel.

U2000
NOTE
Procedure
Management > Link Aggregation Group Management from the Function Tree.
Step 2 Click the Link Aggregation Group Management tab.
Step 3 Click New.
The system displays the Create Link Aggregation Group dialog box.
Step 4 Set the LAG attributes in Attribute Settings.
Issue 01 (2016-04-30)

799

Configuration Guide
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.
l If Switch LAG upon Air Interface SD is set to Enabled, the MW_BER_SD or MW_BER_EXC alarm
will trigger the LAG switching at the air interface.
Step 5 Set the LAG port in Port Settings.

1.
Set Main Board and Main Port.
2.
In Available Slave Ports, select Board for the slave port.
3.
In Port, select the slave port, and then click
NOTE
Hold the Ctrl key or the Shift key on the keyboard to select multiple ports.
Issue 01 (2016-04-30)

800

Configuration Guide
A Task Collection
NOTE
For a LAG consisting of Native Ethernet ports:
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.
If a port is already configured with Ethernet services, set the port to a master port when a LAG is
configured.
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:
4.
If a LAG needs to be used to protect services on MPLS ports, set Enable Tunnel on the main port
to Enable, and retain the default value Disabled for Enable Tunnel on the slave port.
If a LAG needs to be used to protect services on MPLS ports, set Specify IP Address to Manual
Specify for the main port, and set Specify IP Address to Unspecified for the slave port.
Click OK. A dialog box is displayed for confirmation. Click OK. A dialog box is
displayed, indicating that the operation is successful. Close this dialog box.
----End
A.9.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.
Prerequisites
l
The board on which the LAG to be created must be added to NE Panel.

U2000
NOTE
Procedure
Step 2 Click the Link Aggregation Parameters tab.
Step 3 Set Port Priority and System Load Sharing Hash Algorithm.
Issue 01 (2016-04-30)

801

Configuration Guide
A Task Collection
NOTE
l System Load Sharing Hash Algorithm is valid only when Load Sharing of a LAG is set to Sharing.
l After the configuration data is deployed, System Load Sharing Hash Algorithm takes effect for the
entire NE.

----End
A.9.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.
Issue 01 (2016-04-30)

802

Configuration Guide
A Task Collection
Prerequisites
l
The LAG must be created.

U2000
NOTE
Procedure
Step 3 Click Query.A dialog box is displayed, indicating that the operation is successful. Close this
dialog box.
Step 4 In the Main Interface, select the LAG to be queried.
Step 5 Query port status of the main and slave ports.
NOTE
The system displays the information about the slave port in the lower part of the Main Interface.
Step 6 Right-click on the selected LAG and choose the LAG-specific information from the shortcut
menu.
Step 7 Click Close.

Step 9 Click Query. A dialog box is displayed, indicating that the operation is successful. Close this
dialog box.
Step 10 Query the port priority of the LAG.
----End
A.9.3 Configuring Ethernet Services

The Ethernet service is classified into two types, namely, E-Line service and E-LAN service.
Issue 01 (2016-04-30)

803

Configuration Guide
A Task Collection
A.9.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
NOTE
Procedure
Service Management > QinQ Link from the Function Tree.
Step 2 Click New.
Step 3 Configure the basic attributes of the QinQ link.
----End
A.9.3.2 Configuring the Forwarding Mode for Ethernet Services

This operation is valid only for intra-board Native E-Line services on an EM6T, EM6TA,
EM6F, or EM6FA board.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

804

Configuration Guide
A Task Collection
Context
The intra-board Native E-Line services on an EM6T, EM6TA, EM6F, or EM6FA board can be
forwarded in two modes: Center and Local.
l
When the centralized forwarding mode is used, intra-board Native E-Line services must
be forwarded through the packet switching unit of a system control board. Therefore,
double backplane bandwidth resources of the system control board are consumed.
When the distributed forwarding mode is used, intra-board Native E-Line services are
directly forwarded by the switching units of the board. However, this will restrict the
functions of some packet switching units that depend on system control boards. The
restrictions include:
Intra-board Native E-Line services do not support the LM function of ETH-OAM.

Therefore, the packet loss rate of the Native E-Line services could not be tested
using meter-free tests.
The source and sink ports of intra-board Native E-Line services do not support the
LAG function. If the source or sink ports are configured with the LAG function, the
forwarding mode is automatically switched to centralized mode.
The default forwarding mode configured for an EM6T, EM6TA, EM6F, or EM6FA board
is centralized forwarding.
Other types of Ethernet services on an EM6T, EM6TA, EM6F, or EM6FA board and all types
of Ethernet services on other types of Ethernet boards are forwarded in centralized mode.
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration > Ethernet
Service Forwarding Mode Management from the function tree.
Step 2 Modify the value of Ethernet Service Forwarding Mode.
Step 3 Click Apply.

----End
A.9.3.3 Configuring UNI-UNI E-Line Services (U2000)

This section describes how to create an E-Line service that is transparently transmitted end to
end or is transmitted based on VLANs.
Prerequisites
l
The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line
service.

U2000
Issue 01 (2016-04-30)

805

Configuration Guide
A Task Collection
Context
NOTE
l For an RTN 980, RTN 980L, or an RTN 950 housing a CSH board, the total number of VLANs
configured for E-Line services, VPLS services, UNIs carrying E-Aggr services, and UNIs carrying
802.1ad bridge-based E-LAN services must not exceed 1024.
l For an RTN 905, RTN 910A, RTN 950A, or RTN 950 housing a CSHU/CSHUA board, the total number
of VLANs configured for E-Line services, E-LAN services, and UNIs carrying E-Aggr services must not
exceed 1024.
l For an RTN 980, RTN 980L, or RTN 950 housing a CSH board, the total number of VLANs configured
for PWs in tag mode and E-Aggr services with UNIs being S ports must not exceed 256.
Procedure
Service Management > E-Line Service from the Function Tree.
Step 2 Click New.
The New E-Line Service dialog box is displayed.
Step 3 Set Direction to UNI-UNI.
Step 4 Configure the attributes of the E-Line service.
Step 5 Click OK. Close the displayed dialog box.

----End
A.9.3.4 Configuring UNI-UNI E-Line Services(Web LCT)

This section describes how to create an E-Line service that is transparently transmitted end to
end or is transmitted based on VLANs.
Prerequisites
l
The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line
service.
Issue 01 (2016-04-30)

806

Configuration Guide
A Task Collection

Web LCT
Context
NOTE
exceed 1024.
Procedure
The Create E-Line Service dialog box is displayed.
Step 3 Set Direction to UNI-UNI.
Step 4 Configure the attributes of the E-Line service.
Step 5 Click Port Attributes.

Step 6 Change the Ethernet port attributes of the source and sink ports. Click Apply Port
Attributes.
Step 7 Click OK.
----End
Issue 01 (2016-04-30)

807

Configuration Guide
A Task Collection
A.9.3.5 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(U2000)

This topic describes how to configure QinQ-based E-Line services.
Prerequisites
l
Ethernet boards have been added on the NE Panel.
For ports that carry services, Port Mode has been set to Layer 2 and Encapsulation
Type has been set to QinQ.

U2000
Context
NOTE
exceed 1024.
Procedure
Step 2 Click New.
Step 3 Set Direction to NNI-NNI.
Step 4 Set relevant attributes of the E-Line service.
Issue 01 (2016-04-30)

808

Configuration Guide
A Task Collection
----End
A.9.3.6 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(Web

LCT)
This topic describes how to configure QinQ-based E-Line services.
Prerequisites
l
For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Context
NOTE
exceed 1024.
Procedure
Step 3 Set Direction to NNI-NNI.
Issue 01 (2016-04-30)

809

Configuration Guide
A Task Collection
Step 5 Optional: Click New to configure the source and sink ends.
NOTE
In this manner, you do not need to configure the QinQ links used at the source and sink ends according to the
network planning information ahead of time. However, you need to set Encapsulation Type of ports
corresponding to the QinQ links to QinQ ahead of time.
1.
Click New.
2.
Set the attributes of the QinQ link at the source end.
3.
Click Configure QinQ Link.
4.
Repeat Step 5.2 and Step 5.3 to set the attributes of the QinQ link at the sink end.
5.
Select Use existing resource.
6.
Click
to add QinQ links to Source and Sink.
Step 6 Optional: Select Use existing resource and select created QinQ links as the QinQ links used
at the source and sink ends.
NOTE
In this manner, you need to configure the QinQ links used at the source and sink ends according to the
network planning information ahead of time.
1.
2.
Click
to add QinQ links to Source and Sink.
Step 7 Click OK.

----End
A.9.3.7 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(U2000)

This topic describes how to configure E-Line services carried by QinQ links.
Prerequisites
l
For UNI and NNI ports that carry services, Port Mode has been set to Layer 2. For NNI
ports, Encapsulation Type has been set to QinQ.

U2000
Issue 01 (2016-04-30)

810

Configuration Guide
A Task Collection
Context
NOTE
exceed 1024.
Procedure
Step 2 Click New.
Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.
NOTE
You can configure QinQ links during service creation or before service creation by choosing Configuration >
Ethernet Service Management > QinQ Link.
----End
A.9.3.8 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(Web

LCT)
This topic describes how to configure E-Line services carried by QinQ links.
Issue 01 (2016-04-30)

811

Configuration Guide
A Task Collection
Prerequisites
l
For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Context
NOTE
exceed 1024.
Procedure
Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.

Step 6 Change the attributes of the source Ethernet port.
Step 7 Click Apply Port Attributes.
Issue 01 (2016-04-30)

812

Configuration Guide
A Task Collection
Step 8 Click QinQ Link.

Step 9 Optional: Click New and create the QinQ link used at the sink end.
NOTE
In this manner, you do not need to configure the QinQ link used at the sink end according to the network
planning information ahead of time. However, you need to set Encapsulation Type of ports corresponding to
the QinQ links to QinQ ahead of time.
1.
Click New.
2.
Set the attributes of the QinQ link at the sink end.
3.
4.
5.
Click
6.
to add the QinQ link to Sink.
Step 10 Optional: Select Use existing and select a created QinQ link as the QinQ link used at the sink
end.
NOTE
In this manner, you need to configure the QinQ link used at the sink end according to the network planning
information ahead of time.
1.
2.
Click
3.
to add the QinQ link to Sink.
Step 11 Click OK.

----End
Issue 01 (2016-04-30)

813

Configuration Guide
A Task Collection
A.9.3.9 Configuring UNI-NNI E-Line Services (Carried by PWs)(U2000)

This section describes how to configure E-Line services carried by PWs.
Prerequisites
l
The Ethernet board is added on the NE Panel.
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
Context
NOTE
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by UNIcarried E-Line, VPLS, E-Aggr, and IEEE 802.1ad bridge-based E-LAN services must not exceed 1024.
l For RTN 950 housing CSHU/CSHUA boards, RTN 905, RTN 910, and RTN 950A, the total number of
VLANs used by UNI-carried E-Line, E-Aggr, and E-LAN services must not exceed 1024.
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by TAGmode PW-carried and S-aware UNI-carried E-Aggr services must not exceed 256.
Procedure
Step 2 Click New.
Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to Unprotection 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.11.5.1 Creating a PW APS Protection Group.
Step 4 Set the basic attributes of E-Line services.
Issue 01 (2016-04-30)

814

Configuration Guide
A Task Collection
Step 5 Click Configure PW.

The Configure PW dialog box is displayed.
Step 6 Click the General Attributes tab and set the basic parameters for PWs.
Step 7 Click the QoS tab and set the QoS parameters for PWs.
Step 8 Click the Advanced Attributes tab and set the advanced parameters for PWs.
Issue 01 (2016-04-30)

815

Configuration Guide
A Task Collection
Step 9 Click OK, and close the Configure PW dialog box.

----End
A.9.3.10 Configuring UNI-NNI E-Line Services (Carried by PWs)(Web LCT)

This section describes how to configure E-Line services carried by PWs.
Prerequisites
l
The Ethernet board is added on the NE Panel.
Port Mode is set to Layer 2 for the UNI ports that carry services.

Web LCT
Context
NOTE
Procedure
Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to No Protection for
E-Line services.
NOTE
When E-Line services are initially configured, it is recommended that you set Protection Type to No
Protection for the services. After successful service creation, add the APS protection when necessary. For
details on how to add APS protection, see A.11.5.1 Creating a PW APS Protection Group.
Issue 01 (2016-04-30)

816

Configuration Guide
A Task Collection
Step 4 Set the basic attributes of E-Line services.

Step 6 Change the attributes of the source Ethernet port.
Step 7 Click Apply Port Attributes.
Step 8 Click PW and set the basic attributes of the PW.
Step 9 Click Apply.

Step 10 Click Advanced Attributes.
The Advanced Attributes dialog box is displayed.
Step 11 Set the advanced attributes of the PW.
Issue 01 (2016-04-30)

817

Configuration Guide
A Task Collection
Step 12 Click OK.

----End
A.9.3.11 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 EAGGR service.
Prerequisites
l
For the UNI ports that carry the service, Port Mode has been set to Layer 2 and
Encapsulation Type has been set to 802.1Q or QinQ. For the NNI port that carries the
service, Port Mode has been set to Layer 3.
The MPLS tunnels that carry PWs have been configured.

U2000
NOTE
Context
NOTE
Issue 01 (2016-04-30)

818

Configuration Guide
A Task Collection
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.
Procedure
Ethernet Service Management > E-AGGR Service from the Function Tree.
Step 2 Click New.
The New E-AGGR Service dialog box is displayed.
Step 3 Set the basic attributes for the E-AGGR service.
Step 4 Configure the UNI ports required for the E-AGGR service.
1.
Click the UNI tab. Click Configuration.

The Configure Port dialog box is displayed.
2.
Select the desired port from the Available Port list and click
to the Selected Port list.
3.
In the Selected Port area, set Location and VLANs according to planning information.
to add the port
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.
Issue 01 (2016-04-30)

819

Configuration Guide
A Task Collection
3.
Set parameters in Advanced Attributes according to planning information.
4.
Click OK.
Step 6 Set the attributes for the VLAN forwarding table.

1.
Click VLAN Forwarding Table Item and click New.

The New VLAN Forwarding Table Item dialog box is displayed.
2.
Set related parameters according to VLAN planning information.
3.
Click OK.
Step 7 Optional: Click the Configure QoS tab and set QoS parameters.
1.
Click the PW tab and set EXP and LSP Mode.
2.
Click OK.
Step 8 Click OK.

----End
A.9.3.12 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.
Issue 01 (2016-04-30)

820

Configuration Guide
A Task Collection
Prerequisites
l
A UNI-UNI E-Line service has been created.

U2000
NOTE
Procedure
Step 2 Select the E-Line service for which a VLAN forwarding table needs to be configured.
Step 3 Click the VLAN Forwarding Table Item tab.
Step 4 Click New.
Step 5 Set the attributes for the VLAN forwarding table.
----End
A.9.3.13 Configuring TPID for a Request VLAN

When a request VLAN is used for E-Line services transmitted by PWs, the TPID in the
request VLAN is defaulted to be 0x88A8. The TPID can be set for an NE.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose
Configuration > TPID Configuration from the Function Tree.
Step 2 Set TPID(Hexadecimal) according to planning information.
Issue 01 (2016-04-30)

821

Configuration Guide
A Task Collection
Step 3 Click Apply.

----End
A.9.3.14 Configuring IEEE 802.1d Bridge-Based E-LAN Services(U2000)

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
Context
An IEEE 802.1d bridge-based E-LAN service must be configured according to the service
model described in 802.1D Bridge-based E-LAN Service Models.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.
The New E-LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the E-LAN service according to the network plan.
Step 4 Configure the ports mounted to the bridge on the UNI side.
1.
Click UNI.
2.
Click Configuration.
3.
Issue 01 (2016-04-30)
Configure the ports mounted to the bridge on the UNI side.

822

Configuration Guide
4.
A Task Collection
a.
Select the port to be mounted to the bridge.
b.
Click
to mount the port to the bridge.
Click OK.
Step 5 Optional: Configure split horizon groups.

NOTE
The port members that are added to the same split horizon group cannot communicate with each other.
1.
Click the Split Horizon Group tab and click New.

The New Split Horizon Group dialog box is displayed.
2.
Set port parameters for the split horizon group as planned.
3.
Click
4.
Click OK.

----End
A.9.3.15 Configuring IEEE 802.1d Bridge-Based E-LAN Services(Web LCT)

The E-LAN service refers to Ethernet service dynamic transmission in the multipoint-tomultipoint mode by means of MAC addresses.
Prerequisites

Web LCT
Procedure
Step 2 Click New.
The Create E-LAN Service dialog box is displayed.
Step 3 Click Configure the source and sink. Set the basic attributes of the E-LAN service
NOTE
Set Tag Type to Tag-Transparent.
Issue 01 (2016-04-30)

823

Configuration Guide
A Task Collection
1.
Click Get UNI Port.

The Get UNI Port dialog box is displayed.
2.

a.

NOTE
Preset Encapsulation Type of the port to Null.
b.
3.
Click
Click OK.
Step 5 Optional: Create split horizon groups.

NOTE
1.
Click Set the service parameters and select Split Horizon Group.
2.
Click New.
The Create Split Horizon Group dialog box is displayed.
3.
Select a required port from Available Port List and click
NOTE
Hold the Ctrl key on the key board to select multiple ports.
4.
Click OK.
Step 6 Click OK.

----End
A.9.3.16 Configuring IEEE 802.1q Bridge-Based E-LAN Services(U2000)

An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several
switching domains.
Prerequisites
l
For the ports that carry the IEEE 802.1q bridge-based E-LAN services, Port Mode has
been set to Layer 2 and Encapsulation Type has been set to 802.1Q.

U2000
Context
l
Configure services based on the service model described in 802.1Q Bridge-based E-LAN
Service Models.
For the OptiX RTN 905, OptiX RTN RTN 910A, the OptiX RTN 950A and the OptiX
RTN 950 that houses CSHU/CSHUA boards, the total number of VLAN IDs configured
for all Ethernet services cannot exceed 1024. The total number of VLAN IDs configured
Issue 01 (2016-04-30)

824

Configuration Guide
A Task Collection
for all Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be used to
transmit other Ethernet services.
Procedure
Step 2 Click New.
Step 3 Set basic attributes of the E-LAN service as planned.
1.
Click UNI.
2.
3.
4.
a.
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
Issue 01 (2016-04-30)

825

Configuration Guide
A Task Collection
A.9.3.17 Configuring IEEE 802.1q Bridge-Based E-LAN Services(Web LCT)

An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several
switching domains.
Prerequisites

Web LCT
Context
l
Configure services based on the service model described in 802.1Q Bridge-based E-LAN
Service Models.
Procedure
Step 2 Click New.
Step 3 Click Configure the source and sink. Set basic attributes of the E-LAN service as planned.
NOTE
Set Tag Type to C-Aware.
1.
Click Get UNI Port.

2.

a.
Issue 01 (2016-04-30)

826

Configuration Guide
A Task Collection
NOTE
Preset Encapsulation Type of the port to 802.1Q.
3.
b.
Click
c.
Click OK.

NOTE
1.
2.
Click New.
3.
NOTE
4.
Click OK.
Step 6 Click OK.

----End
A.9.3.18 Configuring IEEE 802.1ad Bridge-Based E-LAN Services(U2000)

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into
several switching domains.
Prerequisites
l
For the board that transmits the IEEE 802.1ad bridge-based E-LAN service, Port Mode
has been set to Layer 2.

U2000
Context
l
Configure services based on the service model described in 802.1ad Bridge-based ELAN Services.
Issue 01 (2016-04-30)

827

Configuration Guide
A Task Collection
Procedure
Step 2 Click New.
Step 3 Set parameters of the E-LAN service as planned.
1.
Click UNI.
2.
3.
4.
a.
b.
Click
c.
If Encapsulation Type is set to 802.1Q for the port mounted to the bridge,
configure the VLAN ID for the port according to the network plan.
Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1.
Click NNI.
2.
3.
Configure the ports mounted to the bridge on the NNI side.
4.
Click OK.

NOTE
1.

2.
3.
Click
Issue 01 (2016-04-30)
.
828

Configuration Guide
4.
A Task Collection
Click OK.

----End
A.9.3.19 Configuring IEEE 802.1ad Bridge-Based E-LAN Services(Web LCT)

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into
several switching domains.
Prerequisites

Web LCT
Context
l
Configure services based on the service model described in 802.1ad Bridge-based ELAN Services.
Procedure
Step 2 Click New.
Step 3 Click Configure the source and sink. Set parameters of the E-LAN service as planned.
NOTE
Set Tag Type to S-Aware.
Issue 01 (2016-04-30)

829

Configuration Guide
A Task Collection
1.
Click Get UNI Port.

2.

a.

NOTE
Preset Encapsulation Type of the port to 802.1Q.
3.
b.
Click
c.
Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1.
Click Get NNI Port.

The Get NNI Port dialog box is displayed.
2.
Configure the ports mounted to the bridge on the NNI side.

NOTE
Preset Encapsulation Type of the NNI port to QinQ.
3.
Click OK.

NOTE
1.
2.
Click New.
3.
NOTE
4.
Click OK.
Step 7 Click OK.

----End
A.9.3.20 Configuring PW-Carried E-LAN Services (U2000)

This topic describes how to configure PW-carried E-LAN services (VPLS services).
Prerequisites
l
Port Mode for the port mounted to a VSI on the UNI side has been set to Layer 2 and
Encapsulation Type has been correctly set based on the service model.

U2000
Issue 01 (2016-04-30)

830

Configuration Guide
A Task Collection
Context
l
For the OptiX RTN 980 and the OptiX RTN 950 that houses CSH boards, the number of
VLAN IDs configured on a VUNI must not exceed the maximum number allowed. If it
exceeds the maximum number, you can increase the maximum number of VLAN IDs
supported by a VUNI by following instructions in A.9.3.21 Configuring Global
Attributes of VPLS Services. Alternatively, configure the VLAN filtering table on the
VUNI to resolve this issue. However, ports in the VLAN filtering table cannot be used to
For the OptiX RTN 905/950A/910A and the OptiX RTN 950 that houses CSHU/CSHUA
boards, the total number of VLAN IDs configured for all Ethernet services cannot
exceed 1024. The total number of VLAN IDs configured for all Ethernet services does
not include the number of VLAN IDs for E-LAN services configured in VLAN
Filtering Table. Ports in VLAN Filtering Table cannot be used to transmit other
Ethernet services.
Only some system control, switching, and timing boards of the RTN 950/980 support
VPLS, as listed in the following table.
Table A-7 VPLS support by system control, switching and timing boards of the RTN
950/980
NE Type
System Control, Switching, and

Timing Board That Supports VPLS
RTN 950
SL92CSH
SL91CSHU
SL91CSHUA
RTN 980
l
SLB2CSHN
A VPLS must be configured according to the service model described in PW-Carried ELAN Services.
Procedure
Step 2 Click New.
Step 3 Set parameters for the E-LAN services according to the network plan.
Issue 01 (2016-04-30)

831

Configuration Guide
A Task Collection
Step 4 Configure the port mounted to the VSI on the UNI side.
1.
Click the UNI tab.
2.
For RTN 905/950A, when Tag Type is set to S-Aware, do not select PB-UNI.
3.
4.
Configure the port mounted to the VSI on the UNI side.

a.
Select the port to be mounted to the VSI and configure VLAN information.
b.
Click
to mount the port to the VSI.
NOTE
For OptiX RTN 950 using CSHU/CSHUA boards and OptiX RTN 905/950A, the total number of
VLANs configured for Ethernet services must not exceed 1024. To avoid this restriction, do as follows:
configured for Ethernet services. However, theses ports cannot participate in other Ethernet services.
The number of VLANs connected to a V-UNI is restricted when VPLS services are configured on
OptiX RTN 980 and OptiX RTN 950 using CSH boards. Users can use the preceding method to break
through this restriction or decrease the number of V-UNIs supported by an NE to increase the number
of VLANs that can be connected to a V-UNI.
Issue 01 (2016-04-30)

832

Configuration Guide
5.
A Task Collection
Click OK.
Step 5 Configure the PW mounted to the VSI on the NNI side.

1.
Click NNI.
2.
Click Add.
3.
Configure the PW mounted to the VSI.
4.
Click OK.

NOTE
1.

2.
3.
Click
4.
Click OK.

----End
A.9.3.21 Configuring Global Attributes of VPLS Services

By configuring global attributes of VPLS services, you can change TPIDs in S-TAGs carried
in QinQ-based VPLS service packets, and for OptiX RTN 905950/980, you can change the
number of VLANs that a VUNI supports by changing the number of VUNIs that one VSI
supports.
Prerequisites

U2000
NOTE
Context
The following table lists the relationships between the number of VUNIs on an OptiX RTN
950/980 and the number of VLANs supported by the VUNIs.
Table A-8 Relationship between the number of VUNI ports and the number of VLANs
Issue 01 (2016-04-30)
Maximum Number of VUNI Ports (X)
Maximum Number of VLANs
X 32
4096
833

Configuration Guide
A Task Collection
Maximum Number of VUNI Ports (X)
Maximum Number of VLANs
32 < X 64
2047
64 < X 128
1023
128 < X 256
511
256 < X 512
255
512 < X 1024
127
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
VPLS Management from the Function Tree.
Step 2 Set the parameters according to the network plan.
NOTE
The default value of TPID (PW S-TAG) is 88A8.
----End
A.9.3.22 Changing Logical Ports Connected to a VB

This section describes how to change the logical ports connected to a VB and the port
attributes.
Prerequisites
l
The E-LAN services must be created.

U2000
NOTE
Procedure
Step 2 Add or delete logical ports connected to a VB.
Issue 01 (2016-04-30)

834

Configuration Guide
A Task Collection
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
3.
Optional: Click
to add ports to the list of ports connected to the VB.

to delete ports from the list of ports connected to the VB.
NOTE
4.
In Selected Port List, set the attributes of the ports connected to the VB.
5.
Click OK.
6.
Click Yes.Close the displayed dialog box.
----End
A.9.3.23 Deleting an E-Line Service

When an E-Line service is not used, you need to delete the E-Line service to release the
resources.
Prerequisites
l
The E-Line service is configured and this service is not used.

U2000
NOTE
Procedure
Step 2 Click Query.Close the displayed dialog box.
Step 3 Select the E-Line service that needs to be deleted and then click Delete.
A dialog box is displayed, querying whether you need to perform this operation.
Step 4 Click Yes. Close the displayed dialog box.
Step 5 Click Query.
The E-Line service is already deleted.
----End
Issue 01 (2016-04-30)

835

Configuration Guide
A Task Collection
A.9.3.24 Deleting E-LAN Services

When an E-LAN service is not required, you can delete this E-LAN service to release the
Ethernet resources.
Prerequisites
l
A configured E-LAN service is not required.

U2000
NOTE
Procedure
Step 3 Select the E-LAN service to be deleted and click Delete.
Step 4 Click Yes.Close the displayed dialog box.
Step 5 Click Query.
The E-LAN service is already deleted.
----End
A.9.4 Managing the MAC Address Table

The MAC address table is the core of the E-LAN service. The OptiX RTN 905 provides
various functions for managing the MAC address table.
A.9.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
Issue 01 (2016-04-30)

836

Configuration Guide
A Task Collection
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to be
created.
Step 3 Click the Static MAC Address tab.
Step 4 Click New.
The New Static MAC Address dialog box is displayed.
Step 5 Configure the parameters of the static MAC address entry.
----End
A.9.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
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses
needs to be created.
Step 3 Click the Disabled MAC Address tab.
Issue 01 (2016-04-30)

837

Configuration Guide
A Task Collection
Step 4 Click New.

The Create Disabled MAC Address dialog box is displayed.
Step 5 Configure the blacklist entry of MAC addresses.
----End
A.9.4.3 Configuring the MAC Address Learning Parameters

This task helps you to configure the aging status and aging duration for a MAC address table.
For the OptiX RTN 950A, the OptiX RTN 950A and the OptiX RTN 950 that houses CSHU/
CSHUA boards, you can also specify the MAC address table capacity and detection
threshold.
Prerequisites
l

U2000
NOTE
Procedure
Step 2 On the main interface, select the desired E-LAN service.
Step 3 Click the MAC Address Learning Parameters tab.
Step 4 Configure the MAC address learning parameters.
----End
Issue 01 (2016-04-30)

838

Configuration Guide
A Task Collection
A.9.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

U2000
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to be
queried or cleared.
Step 3 Click the Self-Learning MAC Address tab.
Step 4 Optional: Select the board whose dynamic MAC address needs to be queried and then check
the dynamic MAC addresses in the MAC address table that is displayed.
Step 5 Optional: Click Clear MAC Address to clear the dynamic MAC addresses.Then, click Yes
in the dialog box that is displayed for confirmation.
----End
A.9.5 Setting the Mode for Processing an Unknown Frame of the

E-LAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the
MAC address table or a multicast frame whose destination MAC address is not listed in the
multicast group. By default, the NE broadcasts the unknown frame. By setting the mode for
processing an unknown frame of the E-LAN service, you can change the processing mode so
that unknown frame can be discarded.
Prerequisites
l

U2000
NOTE
Issue 01 (2016-04-30)

839

Configuration Guide
A Task Collection
Procedure
Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown
frame needs to be set.
Step 3 Click the Unknown Frame Processing tab.
Step 4 Set the mode for processing an unknown frame of the E-LAN service.
----End
A.9.6 Managing the MSTP

The OptiX RTN 900 supports only the MSTP that generates the CIST.
A.9.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
NOTE
Procedure
Protocol Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab.
Then, the Create Port Group dialog box is displayed.
Step 4 Set the attributes of the port group.
1.
Issue 01 (2016-04-30)
Set Protocol Type and Enable Protocol.

840

Configuration Guide
A Task Collection
2.
Select the board where the member port is located from the drop-down list of Board
under Apply Port.
3.
Select the member port from Available Port List. Then, click
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.
4.
Click OK.
----End
A.9.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
NOTE
Procedure
Step 2 Click the Bridge Parameters tab.
Step 3 Select the port group ID.
Issue 01 (2016-04-30)

841

Configuration Guide
A Task Collection
Step 4 Click the Bridge Parameters tab.

Step 5 Set the attributes of the bridge.
Step 6 Click Apply.

Step 7 Click the Port Parameter tab.
Step 8 Set the parameters of each member of the port group.
NOTE
The Ethernet board is product-specific.
Step 9 Click Apply.

----End
A.9.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
NOTE
Procedure
Step 2 Click the CIST&MSTI Parameters tab.
Step 3 Select the port group from the drop-down list of Port Group.
Step 4 Set the parameters of the port group.
Issue 01 (2016-04-30)

842

Configuration Guide
A Task Collection
NOTE
The Ethernet board is product-specific.
Step 5 Click Apply.

----End
A.9.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
NOTE
Procedure
Step 2 Click the CIST Running Information tab.
Step 3 Click Query.
Step 4 Query the CIST running information.
----End
Issue 01 (2016-04-30)

843

Configuration Guide
A Task Collection
A.9.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
NOTE
Procedure
Step 3 Select the target protocol type from the Protocol Type drop-down list of the port group whose
spanning tree protocol needs to be changed.
Step 4 Click Apply.

----End
A.9.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
NOTE
Issue 01 (2016-04-30)

844

Configuration Guide
A Task Collection
Procedure
Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group for
which the MSTP protocol needs to be enabled or disabled.
Step 4 Click Apply.

Step 5 Select Enabled or Disabled from the Enable Protocol drop-down list in Port Group to
enable or disable the MSTP protocol of a port.
Step 6 Click Apply.

----End
A.9.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
NOTE
Procedure
Step 3 Click Config.
Then, the Config Port Group dialog box is displayed.
Step 4 Modify the configuration data of the MSTP port group.
Issue 01 (2016-04-30)

845

Configuration Guide
A Task Collection
Option
Description
If...
Then...
A member port needs to

be added
1. Select the board where the member ports are located from
the drop-down list of Board.
2. Select the port to be added from Available Port List.
3. Click
A member port needs to

be deleted
1. Select the port to be deleted from Selected Port List.

2. Click
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the ports.
Step 5 Click OK.

----End
A.9.7 Managing the IGMP Snooping

If the multicast router exists on a network, the bridge can enable the IGMP Snooping protocol
to realize the multicast function with the operation of the router.
Context
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this operation.
A.9.7.1 Configuring the IGMP Snooping Protocol

This topic describes how to configure the IGMP Snooping protocol for a specific E-LAN
service.
Issue 01 (2016-04-30)

846

Configuration Guide
A Task Collection
Prerequisites
l
OptiX RTN 950A does not support this operation.
OptiX RTN 950 supports this operation only when housing the system control board
CSH.

U2000
Procedure
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab.
Step 3 Set the attributes of the IGMP Snooping protocol.
Step 4 Click Apply.

----End
A.9.7.2 Querying the Port Information of the Routers

By querying the port information of the router, you can be familiar with the port information
of each router that runs the IGMP Snooping protocol.
Prerequisites
l

U2000
Procedure
Step 2 Click the Route Management tab.
Step 3 Click Query.
Step 4 Query the port information of the routers.
----End
Issue 01 (2016-04-30)

847

Configuration Guide
A Task Collection
A.9.7.3 Querying the Information About the Multicast Groups

This topic describes how to query the information about each multicast group in the IGMP
Snooping protocol.
Prerequisites
l

U2000
Procedure
Step 2 Click the Route Member Port Management tab.
Step 3 Click Query.
Step 4 Query the information about the multicast groups.
----End
A.9.7.4 Creating Static Router Ports

Static router ports are not aged.
Prerequisites
l
The NNI port must be configured for the E-LAN service.

U2000
Procedure
Step 2 Click the Route Management tab.
Step 3 Click New.
Step 4 Set the attributes of the static router ports.
1.
Set Service ID and VLAN ID.
1.
Select the static router port from the drop-down list of Available Port. Click
Issue 01 (2016-04-30)

.
848

Configuration Guide
A Task Collection
NOTE
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting
the ports.
2.
Click OK.
----End
A.9.7.5 Creating a Member of a Static Multicast Group

The members of a static multicast group are not aged.
Prerequisites
l
The UNI port must be configured for the E-LAN service.

U2000
Procedure
Step 2 Click the Route Member Port Management tab.
Step 3 Click New.
Step 4 Set the attributes of members in the static multicast group.
1.
Set Service ID and VLAN ID.
2.
Select the member ports from the drop-down list of Available Port. Click
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.
Issue 01 (2016-04-30)

849

Configuration Guide
3.
A Task Collection
Click OK.
----End
A.9.7.6 Adding a Quickly Deleted Port

If an Ethernet port is connected to only one host, you can set this Ethernet port as a quickly
deleted port.
Prerequisites
l

U2000
Procedure
Step 2 Click the Protocol Config tab.
Step 3 Click Add.
Step 4 Set the attributes of the quickly deleted port.
Step 5 Click Apply.

----End
Issue 01 (2016-04-30)

850

Configuration Guide
A Task Collection
A.9.7.7 Calculating IGMP Packets

By calculating IGMP packets, you can be familiar with the information about the IGMP
packets received and transmitted through the IGMP Snooping protocol.
Prerequisites
l
Dynamic or static multicast member ports must be configured.

U2000
Procedure
Step 2 Click the Data Count tab.
Step 3 Click Query.
Step 4 Calculate the IGMP packets.
----End

By managing the QoS, you can provide the services of different levels for different service
types.
A.9.8.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.
Prerequisites
l
The board of the Ethernet ports must be added on NE Panel.

U2000
NOTE
Issue 01 (2016-04-30)

851

Configuration Guide
A Task Collection
The OptiX RTN 900 has a default DS domain, whose Mapping Relation ID is 1 and
Mapping Relation Name is default map. If a port is bound to a new DS domain, the NMS
automatically deletes the port from the default DS domain.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management from the
Function Tree.
Step 2 Click New.
The Create DS Domain dialog box is displayed.
Step 3 On the main interface, configure the DS domain attributes.
Step 4 Click the Inbound Mapping Relation tab.
Step 5 Configure the mapping relationships between the priorities of ingress packets and PHB
service classes.
Step 6 Click the Outbound Mapping Relation tab.
Step 7 Configure the mapping relationships between the priorities of egress packets and PHB service
classes.
Step 8 Select Board where the application ports exist from Application Port.
Step 9 Select a port from Available Port, and then click
NOTE
Hold the Ctrl key on the keyboard to select multiple ports.
Issue 01 (2016-04-30)

852

Configuration Guide
A Task Collection

----End
A.9.8.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.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

853

Configuration Guide
A Task Collection
Mapping Relation Name is default map.
Procedure
Function Tree.
Step 2 Select the created DS domain and change its attributes on the main interface.
Step 3 Optional: Change the mapping relationship in the ingress direction.
1.
Click the Inbound Mapping Relation tab.
2.
Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the ingress direction.
3.
Click Apply.Close the displayed dialog box.
Step 4 Optional: Change the mapping relationship in the egress direction.

1.
Click the Outbound Mapping Relation tab.
2.
Double-click the parameters whose values need to be changed and change the mapping
relationship between the packet priorities and PHB classes in the egress direction.
3.
Click Apply.Close the displayed dialog box.
Step 5 Click OK.

----End
A.9.8.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
Issue 01 (2016-04-30)

854

Configuration Guide
A Task Collection

U2000
NOTE
Mapping Relation Name is default map.
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 drop-down list of
Available Port.
3. Click
You need to delete 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 deleted from the port list of
Selected Port.
3. Click
You need to change the

Select a new packet type from the drop-down list of Packet
packet type identified by the Type.
port
NOTE
Issue 01 (2016-04-30)

855

Configuration Guide
A Task Collection
NOTE
l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in
the packet and indicates the service class and discarding priority of the packet.
l The packets trusted by the OptiX RTN 900 are the C_VLAN, S_VLAN, IP DSCP and MPLS packets that
contain the C_VLAN priority, S_VLAN priority, DSCP value or MPLS EXP value. By default, the
untrusted packets are mapped to the BE service class for best-effort forwarding.

----End
A.9.8.4 Enabling/Disabling DSCP Demapping at the Egress Port of a DiffServ

Domain
If you do not want the RTN transmission network to change the DSCP values in packets from
wireless base stations, you can disable DSCP demapping on RTN equipment.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

856

Configuration Guide
A Task Collection
Procedure
Management > Diffserv Domain Management > Egress DSCP Mapping from the
Function Tree.
Step 2 Choose Enabled or Disabled.
Step 3 Click Apply.

----End
A.9.8.5 Enabling/Disabling Outbound Demapping at the Egress Port of a

DiffServ Domain
You can disable Outbound demapping at an egress port on an RTN NE to forbid the NE
modifying packet priorities.
Prerequisites

U2000
NOTE
Context
NOTE
This function is supported by RTN 905, RTN 950 with CSHU/CSHUA boards and RTN 950A .
Procedure
Step 1 In the NE Explorer, select an NE from the object tree, and choose Configuration > QoS
function tree.
Issue 01 (2016-04-30)

857

Configuration Guide
A Task Collection
Step 4 Select the desired port and modify Enable Outbound Mapping.
Step 5 Click Apply.

----End
A.9.8.6 Creating a Port Policy

This section describes how to create port policies, including scheduling, shaping, packet
dropping, and WRR policies for egress queues.
Prerequisites
l

U2000
NOTE
Procedure
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Click New. The Create Port Policy dialog box is displayed.
Issue 01 (2016-04-30)

858

Configuration Guide
A Task Collection
Step 3 Set the ID and name of the port policy.

Step 4 Configure scheduling, packet dropping policies, and shaping for egress queues.
NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output subqueues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue
has a certain period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue
according to the requirement, and provides one or more queues that comply with the SP algorithm.
Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP
scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After
Reloading can be changed from SP to WRR according to the queue priorities in a descending order
(CS7-BE).

----End
A.9.8.7 Modifying the Port Policy

This section describes how to change the parameter values of a created port policy.
Prerequisites
l
The port policy must be created.

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

859

Configuration Guide
A Task Collection
Step 2 Select the port policy whose parameter values need to be changed.
Step 3 Double-click the parameters whose values need to be changed and change the queue
scheduling, packet dropping policies, and queue shaping of the port queues.
NOTE
congestion events.
(CS7-BE).

----End
A.9.8.8 Creating Traffic

By creating traffic, you can configure ACL, CoS, CAR and shaping for a specified traffic
stream on a specified port.
Prerequisites
l

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

860

Configuration Guide
A Task Collection
Step 2 Click New.

Step 3 Click the Traffic Classification Configuration tab.
Step 4 Click New.
The Create Traffic Classification dialog box is displayed.
Step 5 Set the attributes.
NOTE
Set the parameters according to the network plan.
Issue 01 (2016-04-30)

861

Configuration Guide
A Task Collection
Step 6 Click Apply.

----End
A.9.8.9 Creating a Port WRED Policy

This section describes how to create a port WRED policy (WRED stands for weighted
random early detection).
Prerequisites
l

U2000
NOTE
Procedure
Management > Policy Management > Port WRED Policy from the Function Tree.
Step 2 Click New.
Step 3 Configure discard thresholds and discard rates for packets in different colors.
Step 4 Click OK.

----End
Issue 01 (2016-04-30)

862

Configuration Guide
A Task Collection
A.9.8.10 Creating a Service WRED Policy

This section describes how to create a service WRED policy (WRED stands for weighted
random early detection).
Prerequisites
l

U2000
NOTE
Context
This operation is supported only by OptiX RTN 950A, OptiX RTN 950 (using CSHU or
CSHUA boards), OptiX RTN 910A, and OptiX RTN 905 1E/2E.
Procedure
Management > Policy Management > Service WRED Policy from the Function Tree.
Step 2 Click New.
Step 3 Configure discard thresholds and discard rates for packets in different colors.
Step 4 Click OK.

----End
Issue 01 (2016-04-30)

863

Configuration Guide
A Task Collection
A.9.8.11 Creating a WRR Policy

This section describes how to create a WRR policy.
Prerequisites
l

U2000
NOTE
Context
In the default WRR scheduling policy for OptiX RTN 900, AF4, AF3, AF2, and AF1 occupy
the same weight of 25% and other queues occupy the weight of 0%.
Procedure
Management > Policy Management > WRR Scheduling Policy from the Function Tree.
Step 2 Click New
Step 3 Set the scheduling weight for each queue.
NOTE
This parameter must be set to 0 for SP queues.

The parameters must be set to a value rather than 0 for WRR queues. If a WRR queue does not carry services,
it is advised to set this parameter for the WRR queue to a small number. It is advised to set this parameter for
other WRR queues to numbers without any common divisors, for example, 10:10:13.
Issue 01 (2016-04-30)

864

Configuration Guide
A Task Collection
Step 4 Click OK.

----End
A.9.8.12 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
NOTE
Procedure
Then, the Configure Port dialog box is displayed.
Step 4 Set the port that uses the port policy.
1.
Select Board where the port that needs to use the port policy from Application Port.
2.
Select a port from Available Ports, and then click
NOTE
3.
Click OK.Close the displayed dialog box.
Step 5 Delete the port that uses the port policy.

Issue 01 (2016-04-30)

865

Configuration Guide
1.
Select the port to be deleted from Selected Ports and click
A Task Collection
NOTE
2.
----End
A.9.8.13 Creating a V-UNI Egress Policy

This section describes how to create V-UNI Egress policies, including scheduling, shaping,
packet dropping, and WRR policies for V-UNI Egress queues.
Prerequisites
l

U2000
NOTE
Context
Procedure
Management > Policy Management > V-UNI Egress Policy from the Function Tree.
Step 2 Click New. The Create V-UNI Egress Policy dialog box is displayed.
Step 3 Set the ID and name of the V-UNI Egress policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for V-UNI Egress queues.
Issue 01 (2016-04-30)

866

Configuration Guide
A Task Collection
NOTE
congestion events.
(CS7-BE).

----End
A.9.8.14 Creating a V-UNI Group

This section describes how to create a V-UNI group and set bandwidth limitation for the
group.
Prerequisites
l
The board on which the Ethernet port resides has been added on the NE Panel.

U2000
NOTE
Context
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration > Ethernet
Service Management > V-UNI Group from the function tree.
Issue 01 (2016-04-30)

867

Configuration Guide
A Task Collection
Step 2 Click New and the New V-UNI Group dialog box is displayed.
Step 3 Set parameters for the V-UNI group.
NOTE
For the current version, V-UNI Group Type must be set to Egress.

----End
A.9.8.15 Creating a PW Policy

This section describes how to create PW policies, including scheduling, shaping, packet
dropping, and WRR policies for PW queues.
Prerequisites
l

U2000
Issue 01 (2016-04-30)

868

Configuration Guide
A Task Collection
NOTE
Context
Procedure
Management > Policy Management > PW Policy from the Function Tree.
Step 2 Click New. The Create PW Policy dialog box is displayed.
Step 3 Set the ID and name of the PW policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for PW queues.
NOTE
congestion events.
(CS7-BE).

----End
A.9.8.16 Creating a QinQ Policy

This section describes how to create QinQ policies, including scheduling, shaping, packet
dropping, and WRR policies for QinQ queues.
Issue 01 (2016-04-30)

869

Configuration Guide
A Task Collection
Prerequisites
l

U2000
NOTE
Context
Procedure
Management > Policy Management > QinQ Policy from the Function Tree.
Step 2 Click New. The Create QinQ Policy dialog box is displayed.
Step 3 Set the ID and name of the QinQ policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for QinQ queues.
NOTE
congestion events.
(CS7-BE).

----End
Issue 01 (2016-04-30)

870

Configuration Guide
A Task Collection
A.9.8.17 Applying policies for Ethernet services

This section describes how to apply policies for Ethernet services.
Prerequisites
l
An Ethernet service has been created.
An policy has been created.

U2000
NOTE
Context
Procedure
Step 2 Select the Ethernet service and click QoS.
Step 3 Apply policies for Ethernet services.
l
Apply the PW policy.
Apply the QinQ policy.
Apply the V-UNI Egress policy.
Step 4 Click Apply and close the dialog box that is displayed.
----End
A.9.8.18 Configuring Port Shaping

This section describes how to configure traffic shaping for an egress port.
Issue 01 (2016-04-30)

871

Configuration Guide
A Task Collection
Prerequisites
l
The Ethernet board must be created on the NE Panel.

U2000
NOTE
Procedure
Management > Port Shaping Management from the Function Tree.
Step 2 Click New.
Step 3 Set the parameters for port shaping.
NOTE
If the traffic shaping function is enabled, OptiX RTN 900 processes the packets in the buffer queue through
the following methods when no packets are available in the queue.
l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or
lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the
buffer queue and then is forwarded at a rate equal to the PIR.
l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal
to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by
the PBS.
l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter
the buffer queue and then are forwarded at a rate equal to the PIR.
Step 4 Click OK.

----End
A.9.8.19 Configuring Bandwidth Limitation for MPLS Tunnels

This section describes how to configure bandwidth limitation for MPLS tunnels.
Prerequisites
l
Issue 01 (2016-04-30)

872

Configuration Guide
A Task Collection
An MPLS tunnel has been created.

U2000
NOTE
Procedure
MPLS Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the Static Tunnel tab.
Step 3 Select the MPLS tunnel and set CIR (kbit/s).
----End
A.9.8.20 Configuring Bandwidth Limitation for PWs

This section describes how to configure bandwidth limitation for PWs carrying ETH PWE3
services.
Prerequisites
l
An ETH PWE3 service has been created.

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

873

Configuration Guide
A Task Collection
Step 2 Select the ETH PWE3 service and click QoS.

Step 3 On the PW tab page, set the parameters related to bandwidth limitation.
----End
A.9.8.21 Configuring Bandwidth Limitation for QinQ Links

This section describes how to configure bandwidth limitation for QinQ Links carrying QinQ
services.
Prerequisites
l
An QinQ service has been created.

U2000
NOTE
Context
Procedure
Step 2 Select the QinQ service and click QoS.
Step 3 On the QinQ Link tab page, set the parameters related to bandwidth limitation.
Issue 01 (2016-04-30)

874

Configuration Guide
A Task Collection
----End
A.9.9 Using the ethernet service OAM

By using the ethernet service OAM, you can maintain Ethernet services in an end-to-end
manner.
A.9.9.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
NOTE
Procedure
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 2 Click the Maintenance Association tab.
Step 3 Choose New > New Maintenance Domain.
The system displays the New Maintenance Domain dialog box.
Issue 01 (2016-04-30)

875

Configuration Guide
A Task Collection
Step 4 Set the MD parameters.
NOTE
l Maintenance Domain Level specifies the level of the maintenance domain.

l The values 0 to 7 indicates maintenance domain levels in an ascending order.
l MEPs transparently transmit OAM protocol packets if the packets have a higher level than the
parameter value.
l MEPs discard OAM protocol packets if the packets have a lower level than the parameter value.
l MEPs respond to or terminate OAM protocol packets based on the packet type if the packets have
the same level as the parameter value.

----End
A.9.9.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
NOTE
Procedure
Step 3 Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.
The system displays the New Maintenance Association dialog box.
Step 4 Set the MA parameters.
Issue 01 (2016-04-30)

876

Configuration Guide
A Task Collection
NOTE
Click
in Relevant Service. Select the corresponding services in the displayed Select
Service dialog box.

Step 6 Optional: When Y.1731based Ethernet OAM is used, set Protocol/Standard to Y.1731 and
set the MEG ID corresponding to the MA according to the plan. Then, click Apply.
----End
A.9.9.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
NOTE
Procedure
Step 3 Select the maintenance association in which an MEP needs to be created. Choose New > New
MEP Point.
The system displays the New MEP Point dialog box.
Step 4 Set the MEP parameters.
Issue 01 (2016-04-30)

877

Configuration Guide
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
A.9.9.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
NOTE
Procedure
Step 3 Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog box
is displayed.
Step 4 Click New.
Issue 01 (2016-04-30)

878

Configuration Guide
A Task Collection
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
A.9.9.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
NOTE
Procedure
Step 2 Click the MIP Point tab.
Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New.
The New MIP Maintenance Point dialog box is displayed.
Step 4 Set the parameters of the new MIP.
Issue 01 (2016-04-30)

879

Configuration Guide
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
A.9.9.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
NOTE
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.
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.
Issue 01 (2016-04-30)

880

Configuration Guide
A Task Collection
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
Step 4 Click Close.

----End
A.9.9.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
NOTE
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.
Procedure
Step 3 Select the maintenance domain and maintenance association for the LB test.
Step 4 Choose OAM > Start LB.
Issue 01 (2016-04-30)

881

Configuration Guide
A Task Collection
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
A.9.9.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.

U2000
NOTE
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.
Issue 01 (2016-04-30)

882

Configuration Guide
A Task Collection
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
A.9.9.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
NOTE
Issue 01 (2016-04-30)

883

Configuration Guide
A Task Collection
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.9.9.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
Source and sink maintenance end points (MEPs) in the same maintenance domain (MD)
have been created.

U2000
Context
For details about restriction on the features related to the operation, see Feature Dependencies
and Limitations.
Procedure
Ethernet OAM Management > Ethernet Service OAM Management from the Function
Tree.
Step 3 Select the desired maintenance association (MA).
Step 4 Optional: For OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A, Set the
LM/DM monitoring policy on MEPs at both ends.
1.
Select the MEP to test and choose New > New Test ID.
2.
Set the performance monitoring policy as required.
3.
Click OK.
Issue 01 (2016-04-30)

884

Configuration Guide
A Task Collection
Step 5 For OptiX RTN 905, OptiX RTN 950 housing CSH, and OptiX RTN 980, right-click an MEP
and choose Browse Performance from the shortcut menu. For OptiX RTN 950 housing
CSHU/CSHUA and OptiX RTN 950A, right-click a Test ID and choose Browse
Performance from the shortcut menu.
Step 6 Select the desired statistics item.
If...
Then...
You want to query the current packet loss ratio,

delay, or delay variation
Click the Statistics Group tab and

set required parameters.
You want to query the historical packet loss ratio, Click the History Group tab and set
required parameters.
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

packet loss ratio, delay, or delay variation
Click the RMON Setting tab. Then

click the Event tab and set required
parameters.
You want to set the historical performance

Click the RMON Setting tab. Then
monitoring period for the packet loss ratio, delay, click the Object tab and set required
or delay variation
parameters.
----End
A.9.9.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.
Issue 01 (2016-04-30)

885

Configuration Guide
A Task Collection

U2000
NOTE
Context
l
Creation of MEPs is not a prerequisite for service loopback detection.
During an E-LAN service loopback test, if a node on the network to which the tested
port is connected reports a loopback packet threshold-crossing event, there is an E-LAN
service loop on this node.
This task can also be completed by choosing Service > Service Path View from the
main menu.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 Click Manual Loopback Detection tab.
Step 3 Select the services 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.9.9.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
Issue 01 (2016-04-30)

886

Configuration Guide
A Task Collection
NOTE
Procedure
Step 2 Click the Loopback tab.
Step 3 Click Service Status List.
The Service Status List dialog box is displayed.
Step 4 Select the port where an E-LAN service needs to be reactivated and click Enable. Close the
dialog box that is displayed.
----End
A.9.9.13 Enabling/Disabling Automatic Service Loop Detection

An NE can automatically initiate service loop detection when an E-LAN service is created or
the status of an E-LAN service changes from down to up.
Prerequisites

U2000
NOTE
Context
l
Automatic service loop detection can be applied to a maximum of two services on a

virtual port. Automatic service loop detection disables a virtual port upon detecting that
any service on the port is looped.
If the service that automatic service loop detection applies to is not looped but another
service at the same virtual port is looped, automatic service loop detection cannot detect
the loop.
Upon detecting loops at multiple ports on a ring E-LAN network, automatic service loop
detection disables these ports, and services may become unavailable.
Procedure
Step 1 In the NE Explorer, select an NE from the object tree, and choose Diagnosis&Maintenance >
E-LAN LD Test Management from the function tree.
Step 2 Select Auto or Disabled
Issue 01 (2016-04-30)

887

Configuration Guide
A Task Collection
Step 3 Click Apply.

----End
A.9.10 Using the ethernet port OAM

By using the ethernet port OAM, you can maintain the point-to-point Ethernet links.
A.9.10.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
NOTE
The OAM auto-discovery is realized based on the auto-negotiation between the local
equipment and the opposite equipment. If the negotiation fails, the local equipment reports an
alarm. After OAM auto-discovery is successfully completed, the link performance is
monitored according to the error frame threshold. You can set the error frame threshold on the
NMS.
Procedure
OAM Management > Ethernet Port OAM Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the port, and set OAM Working Mode.
Issue 01 (2016-04-30)

888

Configuration Guide
A Task Collection
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 autodiscovery 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.

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
A.9.10.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
NOTE
Procedure
Step 3 Select the corresponding port and set Link Event Notification to Enabled.

----End
A.9.10.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 01 (2016-04-30)

889

Configuration Guide
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
NOTE
After the OAM auto-discovery operation is successful, the remote link event notification
function is enabled and the monitoring time and errored frame threshold are set at the local
end. If the local equipment detects a link event in the receive direction, it informs the opposite
equipment of the link event. If the remote alarm for the link event is also supported at the
opposite end, the opposite equipment can also inform the local equipment of the link event
that is detected at the opposite end. Then, the corresponding alarm is reported at the local end.
Procedure
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
NOTE
An alarm is reported if the number of errored frame events within Monitor Window or Period Window
exceeds the specified monitoring threshold.

----End
A.9.10.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.
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.
Issue 01 (2016-04-30)

890

Configuration Guide
A Task Collection

U2000
NOTE
l
If a port is capable of responding to loopbacks, it enters the loopback responding state

and reports the loopback responding alarm after receiving the command of enabling the
remote loopback function sent from the opposite OAM port. In this case, the equipment
that initiates the loopback enters the loopback initiation state and reports the loopback
initiation alarm.
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.
Procedure
Step 3 Select the port and set Remote Side Loopback Response to Enabled.

Step 5 Choose Enable Remote Loopback from the drop-down menu of OAM. Close the displayed
dialog box.
NOTE
To release remote loopbacks, select Disable Remote Loopback.
----End
A.9.10.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.
Issue 01 (2016-04-30)

891

Configuration Guide
A Task Collection
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
NOTE
Procedure
Step 3 Set Loopback Check to Enabled.
----End
A.9.11 LPT Configuration

When you use LPT function, you need to configure the relationship between LPT ports and
the related information of LPT ports.
A.9.11.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.

U2000
NOTE
Issue 01 (2016-04-30)

892

Configuration Guide
A Task Collection
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
A.9.11.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.
NOTE
l For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and Model 2 in
QinQ-Based E-Line Service Models.
l For the service models of E-Line services carried by PWs exclusively occupying UNI ports, see Model 3
in PW-Carried E-Line Services.

U2000
Issue 01 (2016-04-30)

893

Configuration Guide
A Task Collection
NOTE
Procedure
Step 2 Click the Point-to-Point LPT tab.
Step 3 Select PW or QinQ services that require the LPT function.
Step 4 Click Bind in the lower right corner of the pane. Then, choose PW+QinQ from the shortcut
menu.
Period(100ms).
----End
A.9.11.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 Service
Models.
l For the service models of E-Line services carried by PWs sharing UNI ports, see Model 1 and Model 2 in
PW-Carried E-Line Services.

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

894

Configuration Guide
A Task Collection
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.
Period(100ms).
----End
A.9.11.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
NOTE
Procedure
Management > Simple LPT from the Function Tree.
Step 2 Click New.
Step 3 Configure the board and port of the Convergence Point.
Step 4 Set Access Point.
1.
In the Board list, select the board of the access point.
2.
In Port, select the required port, and then click
Step 5 Click OK.

----End
Issue 01 (2016-04-30)

895

Configuration Guide
A Task Collection
A.9.12 Configuring IP Packet Coloring and Statistics Collection

IP packet coloring and statistics collection is an IP network performance measurement
technology. It marks IP service packets and counts the marked packets, thereby achieving
accurate packet loss measurement from end to end or by segment.
Prerequisites
l
Only OptiX RTN 950(CSHU/CSHUA), OptiX RTN 950A, OptiX RTN 905 1E/2E and
OptiX RTN 910A support this operation.
You are an NMS user with administrator rights or higher rights.
Native Ethernet services or PW-carried Ethernet services have been created.

U2000
Procedure
Step 1 Click a desired NE in the NE Explorer and choose Diagnose&Maintenance > IP Packet
Marking from the main menu.
Step 2 (Optional) Set the coloring bit. The default value is IP FLAG BIT0.
Step 3 Click New. The Create IP Packet Marking tab is displayed.
Issue 01 (2016-04-30)

896

Configuration Guide
A Task Collection
1.
Set the following parameters: ID, Name, Role, Action, and Auto Stop After(minutes).
2.
Set the packet matching rules and the logical relationship between the matching rules.
Step 4 Set the measurement point.

NOTE
l Uplink/Downlink nodes can be set as VUNI or QinQ measurement points.

l Intermediate nodes can be set as VUNI, QinQ, or tunnel measurement points.
For a VUNI measurement point, set the following parameters: Direction, Service, Port,
VLAN, and Priority.
For a QinQ measurement point, set Direction, Service, and QinQ Link.
For a tunnel measurement point, set Direction, Tunnel ID, Port, PW Label, Service
Tag Role, and PW Type.
Issue 01 (2016-04-30)

897

Configuration Guide
A Task Collection
Step 5 Click Start to start a test.

Step 6 Click Stop to stop a test or wait for the test to automatically stop.
NOTE
l To stop a test, stop the test for an uplink node and then for a downlink node.
l To delete measurement instances, delete the measurement instance from an uplink node and then from a
downlink node.
Step 7 After the test is over, query the test result.

----End
A.10 Configuring Ethernet Services and Features on the

EoS/EoPDH Boards
Configurations of Ethernet services and features on the EoS/EoPDH boards include relevant
Ethernet port configuration, protection configuration, service configuration, protocol
configuration, and OAM configuration.
Context
NOTE
OptiX RTN 905/910A does not support the Ethernet services on EoS/EoPDH boards.
A.10.1 Managing ERPS

Ethernet Ring Protection Switching (ERPS) can be configured on an Ethernet over SDH
(EoS) ring to protect Ethernet services.
A.10.1.1 Creating ERPS Instances

Ethernet Ring Protection Switching (ERPS) is configured by creating ERPS instances.
Prerequisites
l
An EMS6 board has been added to the NE Panel.

U2000
Issue 01 (2016-04-30)

898

Configuration Guide
A Task Collection
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.10.1.2 Setting the Parameters of the ERPS Protocol

The parameters of the Ethernet Ring Protection Switching (ERPS) protocol include the holdoff time, WTR time, and guard time.
Prerequisites
l
An ERPS instance has been created.

U2000
Procedure
ERPS Management from the Function Tree.
Step 2 Optional: Double-click Control VLAN, and then modify the control VLAN ID.
Step 3 Optional: Set the parameters of the ERPS protocol.
Issue 01 (2016-04-30)

899

Configuration Guide
A Task Collection
NOTE
Set the parameters according to the network plan. Default values are recommended.
Step 4 Click Apply.

----End
A.10.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.10.2 Managing LAGs

Link aggregation enables one or multiple links that are connected to the same equipment to be
aggregated into a LAG. The aggregated links are considered as a single logical link at the
MAC layer. In this manner, bandwidth and availability of radio links are improved.

To improve bandwidth and availability of Ethernet links between two NEs, you need to create
the corresponding LAG.
Prerequisites
l
The EFP8/EMS6 board where the LAG ports are located must be added in the NE Panel.

U2000
Issue 01 (2016-04-30)

900

Configuration Guide
A Task Collection
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Step 3 Click New.
The Create Link Aggregation Group dialog box is displayed.
Step 4 In Attributes Settings, set the parameters of the LAG.
Step 5 In Port Settings, set the LAG ports.

1.
Set Main Port.
2.
Select a slave port from Available Standby Ports and then click
NOTE
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the
ports.
Step 6 Click OK.

Step 7 Click OK.
----End
Issue 01 (2016-04-30)

901

Configuration Guide
A Task Collection
A.10.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 3 Set the parameters associated with the system priority and port priority.
Step 4 Click Apply.

----End
A.10.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.
Issue 01 (2016-04-30)

902

Configuration Guide
A Task Collection
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 8 Click Query to check the parameters associated with the port priority and system priority.
----End
A.10.3 Configuring Ethernet Services

The EFP8/EMS6 board supports EPL, EVPL, EPLAN, and EPVLAN services.
A.10.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.
Issue 01 (2016-04-30)

903

Configuration Guide
A Task Collection

U2000
Precautions
For the method of creating QinQ-based Ethernet private line services, see A.10.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.
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.
Issue 01 (2016-04-30)

904

Configuration Guide
A Task Collection
Step 6 Optional: Set the bound path.

1.
The Bound Path Configuration dialog box is displayed. Set the attributes of the bound
path.
2.
In Configurable Ports, select a VCTRUNK as the configurable port.
3.
In Available Bound Paths, set Direction of the bound path.
4.
Select required items in Available Resources and Available Timeslots and click
.
5.
Optional: Repeat Step 6.4 to bind other VC paths.
6.
Click OK.
7.
Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the
result of directly setting the attributes of VCTRUNKs.
Step 7 Click OK.Then, close the dialog box that is displayed.

----End
A.10.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
Issue 01 (2016-04-30)

905

Configuration Guide
A Task Collection

U2000
Precautions
For the method of creating the IEEE 802.1ad bridge, see A.10.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.
Set the attributes of the IEEE 802.1d bridge.
Issue 01 (2016-04-30)

906

Configuration Guide
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 01 (2016-04-30)
Optional: Repeat Step 4.2 to mount other ports.

907

Configuration Guide
4.
A Task Collection
Click OK.

1.
path.
2.
3.
4.
.
Issue 01 (2016-04-30)

908

Configuration Guide
5.
6.
Click OK.
A Task Collection

7.
Click Yes.
NOTE

----End
A.10.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.
Step 5 Click Apply.Then, close the dialog box that is displayed.
----End
A.10.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.
Issue 01 (2016-04-30)

909

Configuration Guide
A Task Collection
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.
Click OK. Then, close the dialog box that is displayed.
----End
A.10.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.
Issue 01 (2016-04-30)

910

Configuration Guide
A Task Collection
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 01 (2016-04-30)

911

Configuration Guide
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.
2.
3.
4.
.
5.
6.
Click OK.
7.
Click Yes.
NOTE
----End
A.10.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.
Issue 01 (2016-04-30)

912

Configuration Guide
A Task Collection
Prerequisites
l

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.
Issue 01 (2016-04-30)
Click Configure Mount.

913

Configuration Guide
A Task Collection
The Service Mount Configuration dialog box is displayed.

2.
Set the parameters for configuring mounted services.
3.
Click Add Mount Port.
4.
Repeat Step 4.2 and Step 4.3 to add the other mounted ports.
5.
Click OK.
6.
Optional: You can change the Ethernet port attributes of the mounted ports in the
Service Mount window.

1.
Issue 01 (2016-04-30)
path.

914

Configuration Guide
A Task Collection
2.
3.
4.
.
5.
6.
Click OK.
7.
Click Yes.
NOTE

----End
A.10.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
Issue 01 (2016-04-30)

915

Configuration Guide
A Task Collection
Procedure
Step 2 Click Query.
Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete.
Step 4 Click Yes.Then, close the dialog box that is displayed.
Step 5 Click Query. At this time, the Ethernet private line service is already deleted.
----End
A.10.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.
Issue 01 (2016-04-30)

916

Configuration Guide
A Task Collection

Step 9 Click Query. At this time, the Ethernet LAN service is already deleted.
----End
A.10.4 Managing the MAC Address Table

The MAC address table is the core of the Ethernet LAN service. The EFP8/EMS6 board
provides various functions for managing the MAC address table.
A.10.4.1 Creating a Static MAC Address Entry

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
Issue 01 (2016-04-30)

917

Configuration Guide
A Task Collection
A.10.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

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
A.10.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
Issue 01 (2016-04-30)

918

Configuration Guide
A Task Collection
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
Step 2 Modify the aging time of the MAC address table entry.
1.
Double-click MAC Address Aging Time corresponding to the EFP8 board.

The MAC Address Aging Time dialog box is displayed.
2.
Set the duration and unit of the aging time.
3.
Click OK.
Step 3 Click Apply.

----End
A.10.4.4 Querying or Deleting a Dynamic MAC Address

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
A.10.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 01 (2016-04-30)

919

Configuration Guide
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
A.10.5 Configuring Ethernet Ports

The EFP8/EMS6 board supports external ports and internal ports.
A.10.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.
Prerequisites
l
Issue 01 (2016-04-30)

920

Configuration Guide
A Task Collection

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
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.
3.
Step 6 Set the network attributes of the port.

1.
Click the Network Attributes tab.
2.
Set the network attributes of the port.
Issue 01 (2016-04-30)

921

Configuration Guide
3.
A Task Collection
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
A.10.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
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.
Issue 01 (2016-04-30)

922

Configuration Guide
A Task Collection
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.
Issue 01 (2016-04-30)
path.

923

Configuration Guide
A Task Collection
2.
3.
4.
.
5.
6.
Click OK.
7.
Click Yes.
NOTE
----End
A.10.5.3 Modifying the Type Field of QinQ Frames

The default type field of QinQ frames is 0x8100.
Prerequisites
l

U2000
Procedure
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Step 3 Click Apply.

----End
A.10.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
Issue 01 (2016-04-30)

924

Configuration Guide
A Task Collection

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.
.
4.
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.
Issue 01 (2016-04-30)

925

Configuration Guide
A Task Collection
Step 7 Click OK.

Step 8 Click Yes.
----End
A.10.6 Managing the Spanning Tree Protocol

The OptiX RTN OptiX RTN 905 supports Spanning Tree Protocol (STP) and Rapid Spanning
Tree Protocol (RSTP).
A.10.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
Procedure
Step 1 In 1the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Layer-2 Switching Management > Spanning Tree from the Function
Tree.
Step 2 Click the Protocol Enabled tab.
Step 3 Set Protocol Enabled and Protocol Type.
Step 4 Click Apply.

----End
A.10.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
Issue 01 (2016-04-30)

926

Configuration Guide
A Task Collection

U2000
Procedure
Tree.
Step 2 Set bridge parameters.
1.
Click the Bridge Parameters tab.
2.
Set bridge parameters.
3.
Click Apply.
Step 3 Set port parameters.

1.
Click the Port Parameters tab.
2.
Set port parameters.
3.
Click Apply.
Step 4 Optional: If Protocol Type is set to RSTP, specify the point-to-point attribute of the Ethernet
port.
1.
Click the Point to Point Attribute tab.
2.
Set the point-to-point attribute of the port.
3.
Click Apply.
----End
A.10.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
Issue 01 (2016-04-30)

927

Configuration Guide
The STP or RSTP must be enabled for the bridge.
A Task Collection

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
Step 2 Query the bridge running information.
1.
Click the Bridge Running Information tab.
2.
Click Query.
3.
Check the bridge running information.
Step 3 Query the port running information.

1.
Click the Port Running Information tab.
2.
Click Query.
3.
Check the port running information.
----End
A.10.7 Managing the IGMP Snooping Protocol

If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol
to implement the multicast function together with the router.
A.10.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.
Issue 01 (2016-04-30)

928

Configuration Guide
A Task Collection
Step 2 Click the Enable IGMP Snooping Protocol tab.

Step 3 Set the information about the IGMP Snooping protocol.
Step 4 Click Apply.

----End
A.10.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 01 (2016-04-30)

929

Configuration Guide
3.
A Task Collection
Click OK.
----End
A.10.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.
Step 2 Click the Multicast Aging Time tab.
Step 3 Modify the aging time of the multicast table entries.
Issue 01 (2016-04-30)

930

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.10.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.
A.10.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.
Issue 01 (2016-04-30)

931

Configuration Guide
A Task Collection

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
A.10.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.
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.
Issue 01 (2016-04-30)

932

Configuration Guide
A Task Collection
The New CAR dialog box is displayed.

Step 4 Set the CAR parameters.
Step 5 Click OK.

----End
A.10.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
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 01 (2016-04-30)

933

Configuration Guide
Issue 01 (2016-04-30)

A Task Collection
934

Configuration Guide
A Task Collection
Step 5 Click OK.

----End
A.10.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.
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
Management > Flow Management from the Function Tree.
Step 2 Click the Flow Configuration tab.
Step 3 Double-click Bound CAR and select the CAR to be bound.

Issue 01 (2016-04-30)

935

Configuration Guide
A Task Collection
Step 4 Double-click Bound CoS and select the CoS to be bound.

Step 5 Click Apply.
----End
A.10.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.
Step 3 Click Apply.

----End
A.10.8.6 Configuring Port Shaping

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.
Issue 01 (2016-04-30)

936

Configuration Guide
A Task Collection
Step 2 Click the Port Shaping tab.

Step 3 Set the port shaping parameters for a port.
Step 4 Click Apply.

----End
A.10.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

U2000
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object Tree and
Function Tree.
Step 2 Click the Port Queue Information tab.
Step 3 Select a port from Port List.
Step 4 Set Scheduling Mode and Weight for the port queue.
Step 5 Click Apply.

----End
A.10.9 Using the Ethernet service OAM

By using the Ethernet service OAM, you can maintain the Ethernet service in an end-to-end
manner.
Issue 01 (2016-04-30)

937

Configuration Guide
A Task Collection
A.10.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.
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
Issue 01 (2016-04-30)

938

Configuration Guide
A Task Collection
A.10.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
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
A.10.9.3 Creating MPs

MPs refer to function entities of Ethernet service OAM, including MEPs and MIPs. The
functions of the Ethernet service OAM can be used only after MPs are created.
Prerequisites
l
Issue 01 (2016-04-30)

939

Configuration Guide
The Ethernet services must be created and activated.
The MD and MA must be created.
A Task Collection

U2000
Precautions
In an OAM test, all MPs that are involved in the operation of the same service flow must be in
the same MD. In an existing MD involved in the same service flow, creating an MP of the
same level or a higher level may damage the existing MD. As a result, the OAM test fails.
Procedure
Step 2 Click New.
The Create MP dialog box is displayed.
Step 3 Set the parameters of the new MP.
Step 4 Optional: Click Advanced. In the displayed dialog box, set the corresponding parameters
and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configurations:
Issue 01 (2016-04-30)
Activate the CC and set the sending period of the CC test.
Set the timeout time for the LB or LT test.

940

Configuration Guide
A Task Collection
Step 5 Click OK.

----End
A.10.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
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Inactivate CC
----End
Issue 01 (2016-04-30)

941

Configuration Guide
A Task Collection

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.
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 01 (2016-04-30)

942

Configuration Guide
A Task Collection
A.10.9.6 Performing an LT Test

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.

NOTE
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
----End
Issue 01 (2016-04-30)

943

Configuration Guide
A Task Collection
A.10.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
A.10.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.
Issue 01 (2016-04-30)

944

Configuration Guide
A Task Collection

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
A.10.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
Issue 01 (2016-04-30)

945

Configuration Guide
A Task Collection
The performance check method provides an in-service test of packet loss ratio and delay
based on the check of the connectivity between the MPs on the Ethernet service processing
unit.
A performance check is implemented as follows: The source MP initiates several LB tests and
counts different packet loss ratio and delay values.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Performance Detect.
The Performance Detect dialog box is displayed.
Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Detect Attempts for the test
packet.
Step 4 Set Source MP ID and Destination MP ID.
Step 5 Click Start Detect. Then, the check result is displayed.
----End
A.10.10 Using the Ethernet port OAM

By using the Ethernet port OAM, you can maintain the point-to-point Ethernet links.
A.10.10.1 Enabling the OAM Auto-Discovery Function

The Ethernet port OAM is achieved based on the OAM auto-discovery function. After the
OAM auto-discovery succeeds, the equipment automatically monitors the faults and
performance of the link.
Prerequisites
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.
Issue 01 (2016-04-30)

946

Configuration Guide
A Task Collection
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
A.10.10.2 Enabling the Link Event Notification

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.
Issue 01 (2016-04-30)

947

Configuration Guide
A Task Collection
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
A.10.10.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.
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:
Issue 01 (2016-04-30)

948

Configuration Guide
A Task Collection
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
A.10.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.
Issue 01 (2016-04-30)

949

Configuration Guide
A Task Collection
Procedure
Step 3 Choose Enable Remote Loopback from the OAM drop-down menu. Then, close the dialog
box that is displayed.
----End
A.10.11 Configuring LPT

After enabling the LPT function for an Ethernet service, you need to configure the LPT port
and the relevant information.
A.10.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.
Issue 01 (2016-04-30)

950

Configuration Guide
A Task Collection
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
A.10.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.
Issue 01 (2016-04-30)

951

Configuration Guide
A Task Collection
Procedure
Configuration > Ethernet Interface Management > LPT Management from the Function
Tree.
Step 2 Click PtoMP LPT. Then, the LPT Management dialog box appears.
Step 3 Click New.
Step 4 Set the parameters in Convergence Point.

Step 5 Set the parameters in Access Point.
1.
Select the ports from Port and then click
2.
If you select a VCTRUNK, set Bearer Mode.
Step 6 Click OK.

----End
A.11 Managing MPLS/PWE3 Services and Features

The OptiX RTN 900 supports multiple MPLS/PWE3 services and features.
A.11.1 Managing Address Resolution

The OptiX RTN 900 runs the Address Resolution Protocol (ARP) to set up mapping between
MAC addresses and IP addresses of ports.
Issue 01 (2016-04-30)

952

Configuration Guide
A Task Collection
A.11.1.1 Creating ARP Static Entries

This topic describes how to create ARP entries that are not aged.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Control Plane Configuration > Address Parse from the Function Tree.
The Add Address Parse dialog box is displayed.
Step 3 Set the parameters for address resolution.
NOTE
Configure the MAC address in an ARP entry according to the MAC address of its next-hop equipment.
Step 4 Click OK. Then, the static ARP entry is successfully created.
----End
A.11.1.2 Querying ARP Entries

You can learn about ARP information.
Prerequisites

U2000
NOTE
Issue 01 (2016-04-30)

953

Configuration Guide
A Task Collection
Procedure
Step 2 Click Query and query ARP entries in the main interface.
----End
A.11.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
NOTE
Procedure
Step 2 Select the required dynamic ARP entry and click Switch to Static Type.
Step 3 Click Query. Then, ARP List Type changes to Static for the selected dynamic ARP entry.
----End
A.11.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.
Issue 01 (2016-04-30)

954

Configuration Guide
A Task Collection
Prerequisites

U2000
NOTE
Procedure
Step 2 Select the required static ARP entry and click Delete.
NOTE
When deleting dynamic ARP entries, click Clear. Exercise caution when performing this operation to avoid
service interruption.

Step 3 Click OK.
Step 4 Click Query. The selected static ARP entry is deleted.
----End
A.11.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
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Control
Plane Configuration > Aging Time from the Function Tree.
Step 2 Select the required port, double-click it, and modify the parameter Dynamic ARP Entry
Aging Time(min).
Issue 01 (2016-04-30)

955

Configuration Guide
A Task Collection
NOTE
It is recommended that Dynamic ARP Entry Aging Time(min) take its default value 720.
Step 3 Click Apply.

----End
A.11.2 Managing MPLS Tunnels

Managing MPLS tunnels include managing MPLS OAM functions.
Context
NOTE
In this topic, MPLS tunnels are all static LSPs.
A.11.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
NOTE
Procedure
MPLS Management > Basic Configuration from the Function Tree.
Step 2 Click Basic Configuration tab.
Step 3 Double-click LSR ID and set the LSR ID of the NE according to the planning information.
NOTICE
When PWE3 services are configured on the NE, the PWE3 services may be interrupted if
LSR ID of the NE is changed.
Step 4 Click Apply.

Issue 01 (2016-04-30)

956

Configuration Guide
A Task Collection
----End
A.11.2.2 Configuring Global OAM Parameters

Once being configured for an NE, global OAM parameters take effect to all tunnels and PWs
on the NE.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
Step 2 Click the Global OAM Parameters tab.
Step 3 Set global OAM parameters.
----End
A.11.2.3 Changing the MPLS Tunnel/PW OAM Standard

The default MPLS Tunnel/PW OAM standard is Y.1711.
Prerequisites
l
Tunnels/PWs have been created.

U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer.
Issue 01 (2016-04-30)

957

Configuration Guide
If...
A Task Collection
Then...
The MPLS tunnel OAM 1. In the NE Explorer, select the required NE from the Object
standard needs to be
Tree and choose Configuration > MPLS Management >
changed
Unicast Tunnel Management from the Function Tree.
2. Click the Static Tunnel tab.
The MPLS PW OAM
standard needs to be
changed
1. In the NE Explorer, select the required NE from the Object

PW Management from the Function Tree.
2. Click the PW Management tab.
Step 2 Right-click the tunnel/PW for which the OAM standard needs to be changed and choose
Switch to Y.1711 or Switch to Y.1731 from the shortcut menu.
NOTE
l MEG IDs adopt the IP-based format after the OAM standard is changed from Y.1711 to Y.1731.
l If MPLS-TP OAM supports the original transmission interval of CC packets, the transmission interval
will not change after the change of OAM standard and no related switching will be triggered. If MPLSTP OAM does not support the original transmission interval of CC packets, the transmission interval will
change to a value closest to the original value and there is a possibility that related switching is triggered.
Step 3 Close the operation result dialog box that is displayed.

NOTE
----End
A.11.2.4 Creating a Unidirectional MPLS Tunnel

When creating a unidirectional MPLS tunnel, you need to manually create an MPLS tunnel in
the reverse direction.
Prerequisites
l
The port attributes are set correctly.
The LSR ID of each NE is set correctly.

U2000
Issue 01 (2016-04-30)

958

Configuration Guide
A Task Collection
NOTE
Procedure
Step 3 Click New and choose Unidirectional Tunnel from the drop-down list.
Step 4 Select New Reverse Tunnel.
Step 5 Set parameters for the new MPLS tunnel.
----End
Issue 01 (2016-04-30)

959

Configuration Guide
A Task Collection
A.11.2.5 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.
The LSR ID of each NE has been correctly configured.

U2000
NOTE
Procedure
Step 3 Click New and choose Bidirectional Tunnel from the drop-down list.
The New Unicast Bidirectional Tunnel dialog box is displayed.
Step 4 Set parameters for the bidirectional MPLS tunnel.
Issue 01 (2016-04-30)

960

Configuration Guide
A Task Collection
----End
A.11.2.6 Querying MPLS Tunnel Information

You can learn about information about all MPLS tunnels configured for an NE.
Prerequisites
l
MPLS tunnels are configured correctly.

U2000
NOTE
Issue 01 (2016-04-30)

961

Configuration Guide
A Task Collection
Procedure
Step 3 Click Query.Then, close the dialog box that is displayed.
Step 4 View the information about all MPLS tunnels configured for the NE in the main interface.
Continue:
----End
A.11.2.7 Changing MPLS Tunnel Information

This section describes how to change parameter values of an MPLS tunnel, for example, the
egress/ingress ports.
Prerequisites
l
The MPLS tunnel has been created.

U2000
NOTE
Procedure
Step 4 Choose the MPLS tunnel whose parameter values need to be changed and click Modify at the
lower right corner.
Issue 01 (2016-04-30)

962

Configuration Guide
A Task Collection
Step 5 In the dialog box that is displayed, modify the MPLS tunnel information.
Step 6 Click OK.
----End
A.11.2.8 Deleting MPLS Tunnels

If a tunnel is no longer used, you can delete it to free the corresponding transmission
resources.
Prerequisites
l
An MPLS tunnel is configured correctly and is no longer used to transmit services.

U2000
NOTE
Issue 01 (2016-04-30)

963

Configuration Guide
A Task Collection
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.11.2.9 Setting MPLS OAM (Y.1711) Parameters

This section describes how to set MPLS OAM (Y.1711) parameters for MPLS tunnel
availability test.
Prerequisites
l
MPLS tunnels are created and enabled.
Node Type is set to Ingress or Egress for tunnels.

U2000
NOTE
Procedure
Step 3 Select the required MPLS tunnel and set MPLS OAM (Y.1711) parameters.
----End
A.11.2.10 Enabling/Disabling FDI

When MPLS OAM (Y.1711) is used to detect MPLS APS, enable the FDI function for an NE
to decrease the MPLS APS switching time.
Issue 01 (2016-04-30)

964

Configuration Guide
A Task Collection
Prerequisites
l
MPLS tunnels are created and enabled.

U2000
NOTE
Procedure
Step 2 Click the FDI tab.
Step 3 Set Enable FDI based on the applications.
----End
A.11.2.11 Starting/Stopping CV/FFD Detection for MPLS Tunnels

Before enabling CV/FD detection, you need to set MPLS OAM (Y.1711) parameters.
Prerequisites
l
The MPLS OAM (Y.1711) function has been enabled and related parameters have been
configured.

U2000
NOTE
Procedure
Step 3 Select the required tunnel and click OAM Operation.
Step 4 Select the required operation from the drop-down list.
Issue 01 (2016-04-30)

965

Configuration Guide
A Task Collection
1.
To enable CV/FFD detection, click Start CV/FFD. Then, close the dialog box that is
displayed.
2.
To disable CV/FFD detection, click Stop CV/FFD. Then, close the dialog box that is
displayed.
NOTE
l For unidirectional tunnels, this operation task can be performed only for a tunnel whose Node Type
is Ingress.
l For bidirectional tunnels, this operation task cannot be performed if Node Type is Transit.
l After the MPLS OAM (Y.1711) function is enabled, CV/FFD detection is enabled by default.
NOTE
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key.
l Alternatively, you can select the required tunnel, right-click the tunnel, and then select Start
CV/FFD or Stop CV/FFD from the drop-down list.
----End
A.11.2.12 Querying LSP Running Status

This section describes how to query the running status of an MPLS tunnel.
Prerequisites
l
The MPLS OAM detection function has been enabled.

U2000
NOTE
Procedure
Step 2 Select a navigation path based on the OAM protocol type used by a tunnel.
l
If the tunnel uses MPLS OAM (Y.1711), query the LSP running status according to
Click the OAM Parameter tab..
If the tunnel uses MPLS-TP OAM, click the MPLS-TP OAM tab page.
Issue 01 (2016-04-30)

966

Configuration Guide
A Task Collection
Step 3 Select the desired tunnel and click OAM Operation at lower right of the main interface.
Step 4 Select Query LSP Status from the drop-down list. Then, close the dialog box that is
displayed.
Step 5 Check the tunnel status according to the LSP Status parameter value in the main interface.
NOTE
For RTN 950A, if MPLS-TP OAM is used, the queried information about LSP status, defect position, and
unavailable duration is invalid.
NOTE
l Alternatively, you can select a tunnel, right-click the tunnel, and select LSP Status from the dropdown list.
----End
A.11.2.13 Clearing OAM Configuration Data for MPLS Tunnel OAM (Y.1711)
This topic describes how to restart MPLS OAM detection by clearing MPLS OAM (Y.1711)
configuration data.
Prerequisites
l
The MPLS OAM (Y.1711) detection function has been enabled.
The tunnel is not configured in any protection group.

U2000
NOTE
Procedure
Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface.
Step 4 Select Clear OAM from the drop-down list. Then, close the dialog box that is displayed.
NOTE
After this step is performed, OAM parameters for the tunnel are restored to default values. If OAM
operations need to be performed, you need to re-enable and configure the OAM functions.
NOTE
l Alternatively, you can select a tunnel, right-click the tunnel, and select Clear OAM from the dropdown list.
----End
Issue 01 (2016-04-30)

967

Configuration Guide
A Task Collection
A.11.2.14 Performing an LSP Ping Test

This topic describes how to detect whether an MPLS tunnel is available.
Prerequisites

U2000
NOTE
Procedure
Step 2 Optional: If MPLS tunnel OAM (Y.1711) is used, Click the OAM Parameters tab..
Step 3 Optional: If MPLS-TP tunnel OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping
Test from the drop-down list.
NOTE
Alternatively, you can select a tunnel, right-click the tunnel, and select Ping Test from the drop-down
list.

Step 5 Set parameters for a ping test.
Step 6 Click Start Test to check the test result.

NOTE
l If LSP ping uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN
communication over IP protocols.
l To stop a test, click Stop Test.
----End
Issue 01 (2016-04-30)

968

Configuration Guide
A Task Collection
A.11.2.15 Performing an LSP Traceroute Test

You can detect fault points on an MPLS tunnel by performing LSP traceroute tests.
Prerequisites

U2000
Procedure
Step 2 Optional: If MPLS tunnel OAM (Y.1711) is used, Click the OAM Parameters tab..
Step 3 Optional: If MPLS-TP tunnel OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required tunnel, click OAM Operation in the lower right corner, and choose
Traceroute Test from the drop-down list.
NOTE
The test can be initiated only by an ingress node.

NOTE
Alternatively, you can select a tunnel, right-click the tunnel, and select Traceroute Test from the dropdown list.
The Traceroute Test dialog box is displayed.

Step 5 Set parameters for the traceroute test.

NOTE
l If LSP traceroute uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN
----End
A.11.2.16 Configuring MEP Parameters for MPLS-TP Tunnel OAM

To use MPLS-TP tunnel OAM to test whether an MPLS tunnel is available, you need to
configure MEP parameters on the ingress and egress nodes of the MPLS tunnel.
Issue 01 (2016-04-30)

969

Configuration Guide
A Task Collection
Prerequisites
l
The MPLS tunnel has been configured, with its ingress/egress node as an MEP.
The MPLS-TP tunnel OAM standard has been changed to Y.1731.

U2000
NOTE
Procedure
Step 2 Click the MPLS-TP OAM tab.
Step 3 Click the MEP tab.
Step 4 Set OAM Status to Enabled and set other OAM parameters.
----End
A.11.2.17 Creating MIPs of MPLS-TP Tunnel OAM

This section describes how to add MIPs of MPLS-TP tunnel OAM at transit nodes.
Prerequisites
l
The MPLS tunnel has been created and the newly created MIP node is a transit node.
The MPLS-TP tunnel OAM standard has been changed to Y.1731.
Global OAM parameters have been configured.

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

970

Configuration Guide
A Task Collection

Step 3 Click the MIP tab.
Step 4 Click New.
The Create Tunnel MIP dialog box is displayed.
Step 5 Set parameters for the newly configured MIP.
NOTE
l An NE allows for only one MIP for one tunnel.

l If MEG ID Type of the MEP on a tunnel is IP Based, you do not need to create an MIP.
----End
A.11.2.18 Starting a CC Test of MPLS-TP Tunnel OAM

After you start a CC test, unidirectional tunnel connectivity is periodically detected. If the link
is fault after the CC test is started at the source MEP, the sink MEP reports the corresponding
alarms.
Prerequisites
l
The MPLS-TP tunnel OAM has been enabled and OAM parameters have been
configured.

U2000
NOTE
Procedure
Step 4 Select one or more tunnels and choose OAM Operation > Start CC.
Issue 01 (2016-04-30)

971

Configuration Guide
A Task Collection
NOTE
l Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual
requirements.
l To stop a CC test, select one or more tunnels and choose OAM Operation > Stop CC.
Step 5 Then, close the operation result dialog box that is displayed.
----End
A.11.2.19 Starting an LB Test of MPLS-TP Tunnel OAM

MEP and the sink MEP or an MIP.
Prerequisites
l
MPLS-TP tunnel OAM has been enabled for both the source MEP and the sink
MEP/MIP and OAM parameters have been configured.

U2000
NOTE
Procedure
Step 4 Select one or more tunnels and choose OAM Operation > Start LB.
Issue 01 (2016-04-30)

972

Configuration Guide
A Task Collection

Step 6 Click Start Test. View the test result in Test Result.
----End
A.11.2.20 Starting an LT Test Provided by MPLS-TP Tunnel OAM

This section describes how to start a link trace (LT) test provided by MPLS-TP tunnel OAM.
Based on LB tests, LT tests further improve the fault location capability. To be specific, a
faulty network segment can be located upon one LT test.
Prerequisites
l
MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and OAM
parameters have been configured.

U2000
An LT test provided by MPLS-TP tunnel OAM can be started only in end-to-end
configuration mode.
Issue 01 (2016-04-30)

973

Configuration Guide
A Task Collection
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
The Set Filter Criteria dialog box is displayed.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter.
The tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the desired tunnel and choose OAM > MPLS-TP OAM Test from the shortcut
menu.
The MPLS-TP OAM Test dialog box is displayed.
Step 4 Select LT from the drop-down menu and click Parameter to configure the LT test.
Step 5 Click OK.

Step 6 Select the desired path, click Run and check the LT test result in LT Statistics.
----End
A.11.2.21 Testing the Delay and Delay Variation of an MPLS Tunnel

This section describes how to test the delay and delay variation of an MPLS tunnel.
Prerequisites
l

U2000
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.
Issue 01 (2016-04-30)

974

Configuration Guide
A Task Collection
NOTE
l It is recommended that you measure the performance of MPLS tunnels deployed in end-to-end manner by
performing the preceding procedure. For MPLS tunnels deployed on a per-NE basis, it is recommended
that you convert the MPLS tunnels to end-to-end ones by referring to A.15.4 Searching for MPLS
Tunnels and PWE3 Services.
l To perform performance measurement for an MPLS tunnel in the NE Explorer, select the desired MPLS
tunnel, right-click, and choose Performance Statistics Management from the shortcut menu. In the
displayed dialog box, create the corresponding monitoring instance. Note that the PE at both ends must be
configured with the corresponding performance monitoring instance for this MPLS tunnel. Otherwise,
errors occur during performance measurement.
Procedure
Step 3 Right-click the desired tunnel and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of an MPLS tunnel according to testing instances in the U2000 User
Guide for PMS.
----End
A.11.2.22 Setting the LCK Status of MPLS-TP Tunnel OAM

Perform this task to lock an MPLS tunnel and suppress alarms on PWs carried by the tunnel.
Prerequisites
l
The MPLS-TP tunnel OAM has been enabled and OAM parameters have been
configured.

U2000
NOTE
Context
Procedure
Issue 01 (2016-04-30)

975

Configuration Guide
A Task Collection

Step 4 Select the desired tunnel, and set Lock Status to Unlock or Lock.
----End
A.11.2.23 Starting a TST Test Provided by MPLS-TP Tunnel OAM

RTN supports testing the packet loss on an MPLS tunnel.
Prerequisites
l
MPLS-TP tunnel OAM has been enabled for both the source MP and the sink MP and
OAM parameters have been configured.

U2000
l
This task is supported only when the configuration is performed in end-to-end mode on
the U2000.
OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all MPLS
tunnels that meet the filter conditions.
menu.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Issue 01 (2016-04-30)

976

Configuration Guide
A Task Collection
Step 5 Select the NE to initiate the TST test and click Run.
Step 6 View the test result in Test Statistics.
----End
A.11.3 Managing MPLS APS Protection Groups

MPLS APS is the commonest protection mode for MPLS tunnels.
A.11.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.
Issue 01 (2016-04-30)

977

Configuration Guide
A Task Collection
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
NOTE
MPLS OAM needs to be enabled for working and protection tunnels. The detection packets
used by MPLS OAM are FFD packets. FFD packets are usually sent at an interval of 3.3 ms.
If the packet transmission delay time of an MPLS tunnel exceeds 3.3 ms, the transmission
interval of FFD packets needs to be a value greater than the delay time.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click the Tunnel APS Management tab.
Step 3 Click New.
The New Tunnel Protection Group dialog box is displayed.
Step 4 Set parameters for the MPLS APS protection group.
NOTE
When creating an MPLS APS protection group, set Protocol Status to Disabled. Start the protocol only
when the MPLS APS protection group is successfully created on nodes at both ends.
Issue 01 (2016-04-30)

978

Configuration Guide
A Task Collection

----End
A.11.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
NOTE
Procedure
APS Protection Management from the Function Tree.
Issue 01 (2016-04-30)

979

Configuration Guide
A Task Collection
Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about
the protection group.
Step 4 Select the required protection group and click Function.
displayed. Check the status of the protection group.
----End
A.11.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
NOTE
Procedure
Step 3 Select the required protection group, click Function, and then select the required switching
mode from the drop-down list.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and then
select the required switching mode from the drop-down list.

Issue 01 (2016-04-30)

980

Configuration Guide
A Task Collection

Step 5 Click Function.
displayed. Check whether switching is performed successfully.
----End
A.11.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
NOTE
Procedure
Step 3 Stop the MPLS APS protocol.
1.
Select the required protection group and click Function.
2.
Select Stop Protocol from the drop-down list.
NOTICE
After the MPLS APS protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the MPLS APS protocol is
Issue 01 (2016-04-30)

981

Configuration Guide
A Task Collection

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.11.4 Managing PWs

All types of PWE3 services are carried by PWs.
A.11.4.1 Querying Information and Running Status of PWs

This topic describes how to query information and running status of PWs.
Prerequisites
l
PW-carried services have been configured.

U2000
NOTE
Procedure
MPLS Management > PW Management from the Function Tree.
Step 2 Click the PW Management tab.
Issue 01 (2016-04-30)

982

Configuration Guide
A Task Collection
NOTE
If you query information and running statuses of PWs using the Web LCT, perform the following operations:
Click the PW Management tab and click the PW Management tab.
Step 3 Click QueryThen, close the dialog box that is displayed.

Step 4 In the main interface, check the basic information and running status of each PW.
Step 5 After selecting a PW, to query other PW information, do as follows:
1.
Click the QoS Information tab and check QoS information of the PW.
2.
Click the Advanced Attributes tab and check the advanced attributes of the PW.
----End

This topic describes how to configure cross-connections for front-end and rear-end PWs at an
S-PE node and create an MS-PW.
Prerequisites

U2000
NOTE
The steps for creating MS-PWs vary according to service types. This topic uses an Ethernet
service as an example to describe how to create MS-PWs.
Procedure
Step 2 Click the MS PW tab.
NOTE
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW Management tab and click the MS PW tab.
Step 3 Click New.

The Create MS PW dialog box is displayed.
Step 4 In the main interface, configure basic service information.
Issue 01 (2016-04-30)

983

Configuration Guide
A Task Collection
Step 5 Click the PW Basic Attributes tab and set PW parameters.

NOTE
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW General Attributes tab and set PW parameters.
Step 6 Click the QoS tab and set QoS parameters.
Step 7 Click the Advanced Attributes tab and set advanced attributes.

----End
A.11.4.3 Setting PW OAM (Y.1711) Parameters

This topic describes how to set PW OAM (Y.1711) parameters for PW availability test.
Issue 01 (2016-04-30)

984

Configuration Guide
A Task Collection
Prerequisites
l
PW-carried services have been configured.

U2000
NOTE
Procedure
Step 2 Click the PW OAM Parameter tab.
Step 3 Select the required PW and set PW OAM (Y.1711) parameters.
----End
A.11.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
NOTE
Procedure
Step 2 Optional: If PW OAM (Y.1711) is used, Click the PW OAM Parameter tab..
Step 3 Optional: If MPLS-TP PW OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required PW and click OAM Operation > Ping Test.
NOTE
Alternatively, you can select a PW, right-click the PW, and select Ping Test from the drop-down list.
Issue 01 (2016-04-30)

985

Configuration Guide
A Task Collection

Step 5 Set parameters for a ping test.

NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN
----End
A.11.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
NOTE
Procedure
Step 2 Optional: If PW OAM (Y.1711) is used, Click the PW OAM Parameter tab..
Step 3 Optional: If MPLS-TP PW OAM (Y.1731) is used, click the MPLS-TP OAM tab.
Step 4 Select the required PW, click OAM Operation in the lower right corner, and choose
Issue 01 (2016-04-30)

986

Configuration Guide
A Task Collection
NOTE
Alternatively, you can select a PW, right-click the PW, and select Traceroute Test from the drop-down
list.
The Traceroute Test dialog box is displayed.

Step 5 Set parameters for the traceroute test.

NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN
----End
A.11.4.6 Configuring MEP Parameters for MPLS-TP PW OAM

To use MPLS-TP PW OAM to test whether a PW is available, you need to configure MEP
parameters on the T-PE of the PW.
Prerequisites
l
The PW has been configured, with its T-PE as an MEP.
The MPLS-TP PW OAM standard has been changed to Y.1731.

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

987

Configuration Guide
A Task Collection
Step 4 Set OAM Status to Enabled and set other OAM parameters.
----End
A.11.4.7 Creating MIPs of MPLS-TP PW OAM

This section describes how to add MIPs of MPLS-TP PW OAM at S-PE nodes.
Prerequisites
l
The MS-PW has been created and the newly created MIP node is an S-PE node.
The MPLS-TP PW OAM standard has been changed to Y.1731.
Global OAM parameters have been configured.

U2000
NOTE
Procedure
Step 3 Click the MIP tab.
Step 4 Click New.
The Create MS PW MIP dialog box is displayed.
Step 5 Set parameters for the newly configured MIP.
NOTE
l An NE allows for only one MIP for one MS-PW.

l If MEG ID Type of the MEP on an MS-PW is IP Based, you do not need to create an MIP.
----End
Issue 01 (2016-04-30)

988

Configuration Guide
A Task Collection
A.11.4.8 Starting a CC Test of MPLS-TP PW OAM

After you start a CC test, unidirectional PW connectivity is periodically detected. If the link is
fault after the CC test is started at the source MEP, the sink MEP reports the corresponding
alarm.
Prerequisites
l
The MPLS-TP PW OAM has been enabled and OAM parameters have been configured.

U2000
NOTE
Procedure
Step 4 Select one or more PWs and choose OAM Operation > Start CC.
NOTE
l Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual
requirements.
l To stop a CC test, select one or more PWs and choose OAM Operation > Stop CC.
Step 5 Then, close the operation result dialog box that is displayed.
----End
A.11.4.9 Starting an LB Test of MPLS-TP PW OAM

MEP and the sink MEP or an MIP.
Issue 01 (2016-04-30)

989

Configuration Guide
A Task Collection
Prerequisites
l
MPLS-TP PW OAM has been enabled for both the source MEP and the sink MEP/MIP
and OAM parameters have been configured.

U2000
NOTE
Procedure
Step 4 Select one or more PWs and choose OAM Operation > Start LB.

Step 6 Click Start Test. View the test result in Test Result.
----End
Issue 01 (2016-04-30)

990

Configuration Guide
A Task Collection
A.11.4.10 Starting an LT Test Provided by MPLS-TP PW OAM

This section describes how to start a link trace (LT) test provided by MPLS-TP PW OAM.
Based on LB tests, LT tests further improve the fault location capability. To be specific, a
faulty network segment can be located upon one LT test.
Prerequisites
l
MPLS-TP PW OAM has been enabled for both the source and sink MPs and OAM

U2000
An LT test provided by MPLS-TP PW OAM can be started only in end-to-end configuration
mode.
Procedure
Step 1 Choose Service > PWE3 Sevice > Manage PWE3 Sevice from the Main Menu.
The PWs that meet the criteria are listed in the query result.
Step 3 Right-click the desired PW and choose PW OAM > TP OAM Test from the shortcut menu.
Step 4 Select LT from the drop-down menu and click Parameter to configure the LT test.
Step 5 Click OK.

Step 6 Select the desired path, click Run and check the LT test result in LT Statistics.
----End
A.11.4.11 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW
This section describes how to query the packet loss ratio, delay, and delay variation of a PW.
Issue 01 (2016-04-30)

991

Configuration Guide
A Task Collection
Prerequisites
l

U2000
U2000.
NOTE
l It is recommended that you measure the performance of PW deployed in end-to-end manner by

performing the preceding procedure. For PW deployed on a per-NE basis, it is recommended that you
convert the PW to end-to-end ones by referring to A.15.4 Searching for MPLS Tunnels and PWE3
Services.
l To perform performance measurement for an PW in the NE Explorer, select the desired PW, right-click,
and choose Performance Statistics Management from the shortcut menu. In the displayed dialog box,
create the corresponding monitoring instance. Note that the PE at both ends must be configured with the
corresponding performance monitoring instance for this PW. Otherwise, errors occur during performance
measurement.
Procedure
Step 3 Right-click the desired PW and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of a PW according to the testing instances in the U2000 User Guide for
PMS.
----End
A.11.4.12 Setting the LCK Status of MPLS-TP PW OAM

Perform this task to lock a PW and suppress alarms at the customer layer carried by the PW.
Prerequisites
l
The MPLS-TP PW OAM has been enabled and OAM parameters have been configured.

U2000
Issue 01 (2016-04-30)

992

Configuration Guide
A Task Collection
NOTE
Context
Procedure
Step 4 Select the desired PW, and set Lock Status to Unlock or Lock.
----End
A.11.4.13 Starting a TST Test of MPLS-TP PW OAM

OptiX RTN 905 supports testing the packet loss on a PW.
Prerequisites
l
MPLS-TP PW OAM has been enabled for both the source MP and the sink MP and

U2000
l
the U2000.
operation.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all PWs that
meet the filter conditions.
Issue 01 (2016-04-30)

993

Configuration Guide
A Task Collection
----End
A.11.5 Managing a PW APS/PW FPS Protection Group

PW APS and PW FPS are two modes for protecting PWs.
Issue 01 (2016-04-30)

994

Configuration Guide
A Task Collection
A.11.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
NOTE
PW OAM needs to be enabled for the working and protection PWs of a PW APS protection
group. The detection packets used by PW OAM are FFD packets. FFD packets are usually
sent at an interval of 3.3 ms. If the packet transmission delay time of a PW exceeds 3.3 ms,
the transmission interval of FFD packets needs to be a value greater than the delay time.
You can create a PW APS protection group during initial service configuration or after service
configuration.
l
During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW APS protection group.
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 Basic Attributes tab and set the basic attributes of the protection PW.
Issue 01 (2016-04-30)

995

Configuration Guide
A Task Collection
NOTE
If you create a PW APS protection group using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.
Step 6 Click the Protection Group tab and set information about the PW APS protection group.
NOTE
When creating a PW APS protection group, set Enabling Status to Disabled. Start the protocol only when
the PW APS protection group is successfully created on nodes at both ends.
Step 7 Click PW OAM and configure OAM information.

NOTE
l When the PW APS protection group is created, the PW OAM function is automatically enabled to
detect the PW status.
l You can also configure OAM information by choosing Configuration > MPLS Management >
PW Management > PW OAM Parameter.
Issue 01 (2016-04-30)

996

Configuration Guide
A Task Collection

----End
A.11.5.2 Creating a PW FPS Protection Group

In a Mixed VPN solution, a PW FPS protection group needs to be configured for NEs
functioning as CSGs, to achieving dual-homing to ASGs.
Prerequisites
l
MPLS FPS protection is not configured for the services.
The tunnels carrying the working and protection PWs have been created.

U2000
Background
Enable MPLS-TP OAM for both the working and protection PWs in the PW FPS protection
group. The packet transmission interval is often set to 3.3 ms for the enabled MPLS-TP
OAM. If the packet transmitting delay jitter in a PW exceeds 3.3 ms, set the packet
transmission interval to a value greater than the delay.
PW APS protection groups can be created when services are initially configured or after
services are configured.
l
During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW FPS protection group.
If services are already configured, create the PW FPS protection group on the Protect
Group tab page.
For SS-PWs and MS-PWs, configuration of the PW FPS protection group needs to be
done on the both source NE and sink NE.
NOTE
l This topic only describes how to configure PW FPS after services are configured.
l A PW-carried E-Line service is used as an example to describe how to configure PW FPS protection. The
methods of configuring PW FPS protection for other types of service are similar.
Issue 01 (2016-04-30)

997

Configuration Guide
A Task Collection
Procedure
Step 2 Select the desired service and click the Protect Group tab.
Step 3 Click PW FPS.
Step 4 Click New.
NOTE
If you configure the PW using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.
Step 6 Click the Protect Group tab and set information about the PW FPS protection group.
Step 7 Click MPLS-TP OAM and configure the OAM information.

Issue 01 (2016-04-30)

998

Configuration Guide
A Task Collection
NOTE
l When the PW FPS protection group is created, the MPLS-TP OAM function is automatically
enabled to detect the PW status.
l You can also choose Configuration > MPLS Management > PW Management > MPLS-TP
OAM to configure the OAM information.

Step 9 Select the service configured with the PW FPS configuration, and set ARP Dual Feed to
Enabled.
----End
A.11.5.3 Configuring Slave Protection Pairs of PW APS

During PW APS switching, the PWs in the slave protection pair are also switched.
Prerequisites
l
The mapping between a slave protection pair and a PW APS protection group has been
specified.
MPLS APS protection is not configured for the service.
The tunnel carrying the working and protection PWs has been created.

U2000
NOTE
The slave protection pairs are bound with a PW APS protection group. You can create a slave
protection pair during initial service configuration or after service configuration.
Issue 01 (2016-04-30)

999

Configuration Guide
A Task Collection
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 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.
Issue 01 (2016-04-30)

1000

Configuration Guide
A Task Collection

----End
A.11.5.4 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
NOTE
Procedure
Step 2 Click the PW APS Management tab.
Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about
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.11.5.5 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
Issue 01 (2016-04-30)

1001

Configuration Guide
A Task Collection
NOTE
Procedure
Step 3 Select the required protection group, click Function, and then select the required switching
mode from the drop-down list.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and then
select the required switching mode from the drop-down list.

Step 5 Click Function and choose Query Switching Status from the drop-down list. Then, close the
dialog box that is displayed. Check whether switching is performed successfully.
----End
A.11.5.6 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
NOTE
Issue 01 (2016-04-30)

1002

Configuration Guide
A Task Collection
Procedure
Step 3 Stop the PW APS protocol.
1.
2.
Select Stop Protocol from the drop-down list.
NOTICE
After the PW APS protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the PW APS protocol is
3.
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.11.6 Managing CES Services

The OptiX RTN 905 does not support PWE3-based CES services.
A.11.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.
Issue 01 (2016-04-30)

1003

Configuration Guide
A Task Collection

U2000
NOTE
l
Generally, UNI-NNI CES services are configured on the equipment. Therefore, this
topic uses a UNI-NNI CES service as an example to describe how to configure CES
services.
It is recommended that you create protection information before creating a CES service.
In this configuration example, Protection Type is set to No Protection. For details on
how to configure protection information, see A.11.5.1 Creating a PW APS Protection
Group and A.11.5.3 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
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.
Issue 01 (2016-04-30)

1004

Configuration Guide
A Task Collection
NOTE
If you create CES services using the Web LCT, click the Port Attributes tab to configure port attributes. The
result of setting the port attributes during the service configuration process is the same as the result of directly
setting the Ethernet service port attributes.
Step 4 Click Configure PW, and set the basic attributes of the PW.
NOTE
If you create CES services using the Web LCT, you can select Use existing resource and then use a created
tunnel, or click New to create a tunnel. It is recommended that you plan and create required tunnels during
initial service configuration.
Step 5 Click Advanced Attributes and set parameters for the advanced attributes.
Step 6 Click OK.

----End
Issue 01 (2016-04-30)

1005

Configuration Guide
A Task Collection
A.11.6.2 Modifying CES Service Parameters

This topic describes how to modify parameters related to CES services, such as parameters of
transparent transmission of CES alarms and overhead bytes in STM-1 frames.
Prerequisites
l
CES services have been created.

U2000
NOTE
Procedure
Step 2 Select the required CES service and click Query. Then, click the dialog box that is displayed.
Modify basic information about services in the main interface, such as parameters of
transparent transmission of overhead bytes in STM-1 frames.
NOTE
The transparently transmitted bytes cannot function as other channels. For example, transparently transmitted
D bytes cannot function as DCCs.
Step 3 Click PW General Attributes to query information about the PW that carry the service.
Step 4 Modify advanced parameters.
1.
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
A.11.6.3 Querying CES Service Information

This topic describes how to query information about a CES service.
Prerequisites
l
Issue 01 (2016-04-30)

1006

Configuration Guide
A Task Collection
CES services have been created.

U2000
NOTE
Procedure
Step 2 Select the required CES service and click Query. Then, close the dialog box that is displayed.
In the main interface, check basic service information.
Step 3 Click PW General Attributes to query information about the PW that carry the service.
Step 4 Click QoS to check the QoS information of the CES service.
Step 5 Click Advanced Attributes to check advanced attributes of the CES service.
Step 6 Click Protection Group to check whether a protection group is configured and to check
information about the protection group if configured.
----End
A.11.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.

U2000
NOTE
Procedure
Step 2 Select the required CES service and click Delete.
Issue 01 (2016-04-30)

1007

Configuration Guide
A Task Collection

Step 4 Click Query, and then close the dialog box that is displayed to check whether the CES
service is successfully deleted.
----End
A.11.6.5 Calculating the Maximum Number of CES Services That an MPLS

Tunnel Can Transmit
This section describes how to calculate the number of CES services an MPLS tunnel can
transmit based on the created CES service type.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click Calculate CES.
The Calculate Max. Number of Remaining CES Services dialog box is displayed.
Step 3 Set the parameters in the main interface based on the type of the CES service to be created.
NOTE
The maximum number of CES services an MPLS tunnel can transmit varies by service type.
Step 4 Click Calculate, and close the dialog box displayed.

Step 5 View the calculation result.
Issue 01 (2016-04-30)

1008

Configuration Guide
A Task Collection
----End
A.11.7 Managing ATM/IMA Ports

The OptiX RTN 905 does not support ATM/IMA services.

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.8.7 Setting Serial Port Parameters.

U2000
NOTE
Issue 01 (2016-04-30)

1009

Configuration Guide
A Task Collection
Context
NOTE
Procedure
Interface 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.

----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.
Issue 01 (2016-04-30)

1010

Configuration Guide
A Task Collection

If the ATM TRUNK binds IMA E1 links or Fractional IMA links, you need to configure the
parameters of the IMA group.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the IMA Group Management tab.
Step 3 Configure the parameters of the IMA group according to the network plan.
NOTE
l Set IMA Protocol Enable Status to Enabled if the links bound in the ATM TRUNK require the
IMA protocol; otherwise, set this parameter to Disabled.
l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound
in the ATM TRUNK start running the IMA protocol.
l The values of Minimum Number of Active Transmitting Links and Minimum Number of
Active Receiving Links must be the same because the OptiX RTN 905 supports Symmetrical
Mode and Symmetrical Operation only. The parameters Minimum Number of Active
Transmitting Links and Minimum Number of Active Receiving Links must assume the same
value on the two ends of an IMA link.
l On the two ends of the IMA link, you need to set IMA Protocol Version, IMA Transmit Frame
Length, and Maximum Delay Between Links (ms) to the same values.
l Clock Mode is set to the same value for the interconnected ends of IMA links.

----End

This topic describes how to configure ATM port parameters.
Issue 01 (2016-04-30)

1011

Configuration Guide
A Task Collection
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the ATM Interface Management tab.
Step 3 Configure and adjust the ATM port attributes.
NOTE
l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface
on the common ATM network or to the user-side interface of the PE on the PSN network that transmits
ATM PWE3 services.
l NNI: the port connecting network-side devices. For example, the NNI port applies to the network-side
interface on the common ATM network.
l The ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is
mapped into E1 signals. Therefore, it is recommended that you set ATM Cell Payload Scrambling to
Enabled.
l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link.
Otherwise, packet loss will occur.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
A.11.7.4 Querying Running Status of an IMA Group

This topic describes how to query the running status of an IMA group.
Prerequisites

U2000
Issue 01 (2016-04-30)

1012

Configuration Guide
A Task Collection
NOTE
Context
NOTE
Procedure
Step 2 Click the IMA Group States tab.Close the displayed dialog box.
Step 4 Query the running status of an IMA group.
----End
A.11.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
NOTE
Context
NOTE
Procedure
Step 2 Click the IMA Link States tab.Then, close the dialog box that is displayed.
Step 3 Click Query, and then close the dialog box that is displayed.
Step 4 Query the running status of the member links of an IMA group.
----End
Issue 01 (2016-04-30)

1013

Configuration Guide
A Task Collection
A.11.8 Managing ATM Services

A.11.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
Generally, UNIs-NNI ATM services are configured on the OptiX RTN 900. Therefore,
this topic uses a UNIs-NNI ATM service as an example to describe how to configure
ATM PWE3 services.
Before creating ATM PWE3 services, you need to bind member links to the ATM
TRUNK, set the parameters of the IMA group, and create the MPLS tunnels that carries
PWs.

U2000
NOTE
l
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.11.5.1 Creating a PW APS Protection Group
and A.11.5.3 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.
Issue 01 (2016-04-30)

1014

Configuration Guide
A Task Collection
Step 4 Click the Connection tab and configure the attributes of the ATM connection.
Step 5 Click PW, and click Add to configure the attributes of PWs.
1.
Click the General Attributes tab and set the basic attributes of PWs.
NOTE
If you create ATM services using the Web LCT, click Use existing resource or New to select a tunnel.
It is recommended that you create tunnels in advance and click Use existing resource to select a
created tunnel.
2.
Issue 01 (2016-04-30)
Click the QoS tab and enable the PW bandwidth restriction.

1015

Configuration Guide
A Task Collection
3.
Click the Advanced Attributes tab to configure the advanced attributes of PWs.
4.
Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.

----End
A.11.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
according to the planning information.

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click Query, and close the dialog box that is displayed.
Step 3 Select the required ATM service and modify the parameters of the ATM service.
Issue 01 (2016-04-30)

1016

Configuration Guide
A Task Collection
----End
A.11.8.3 Querying ATM Services

This topic describes how to query ATM services.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 3 Select the required ATM service and query the parameters of the ATM service.
----End
A.11.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
NOTE
Issue 01 (2016-04-30)

1017

Configuration Guide
A Task Collection
Context
NOTE
Procedure
Step 3 Select the required ATM service and click Delete.
Step 4 In the confirmation dialog box, click OK.
Step 5 After the service is deleted, close the dialog box that is displayed.
----End
A.11.9 ATM Traffic Management

ATM traffic management includes ATM-Diffserv management and ATM policy management.
The OptiX RTN 905 does not support ATM traffic management.
A.11.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
NOTE
Context
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS
Management > Diffserv domain Management > ATM COS Mapping Configuration from
the Function Tree.
Step 2 Click New.
The New ATM CoS Mapping dialog box is displayed.
Issue 01 (2016-04-30)

1018

Configuration Guide
A Task Collection
Step 3 Configure the ATM-Diffserv domain according to the planning information.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN
900 provides different QoS policies for the queues of different service classes.
l CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates.
l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather
than delay or jitter limits.
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take
effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
----End
A.11.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
NOTE
Issue 01 (2016-04-30)

1019

Configuration Guide
A Task Collection
Context
NOTE
Procedure
the Function Tree.
Step 3 Select the required ATM-Diffserv domain and modify its parameters according to the
planning information.
Issue 01 (2016-04-30)

1020

Configuration Guide
A Task Collection
NOTE
----End
A.11.9.3 Creating an ATM Policy

This topic describes how to create an ATM policy for an ATM connection.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Management > Policy Management > ATM Policy from the Function Tree.
Step 2 Click New.
The Create ATM Policy dialog box is displayed.
Step 3 Configure the parameters of the ATM policy according to the planning information.
Issue 01 (2016-04-30)

1021

Configuration Guide
A Task Collection
----End
A.11.9.4 Modifying an ATM Policy

This topic describes how to modify the QoS parameters of an ATM policy.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Management > Policy Management > ATM Policy from the Function Tree.
Step 3 Select the required ATM policy and modify its parameters according to the planning
information.
Issue 01 (2016-04-30)

1022

Configuration Guide
A Task Collection
----End
A.11.10 Using ATM OAM

ATM OAM is an OAM mechanism that is used for detecting and locating ATM faults, and
monitoring ATM performance. The OptiX RTN 905 does not support ATM OAM.
A.11.10.1 Enabling/Disabling the AIS/RDI Insertion Status

An NE can insert AIS/RDI cells only the AIS/RDI insertion function is enabled.
Prerequisites

U2000
NOTE
Context
NOTE
The OptiX RTN 905 does not support ATM OAM.
Procedure
OAM Management from the Function Tree.
Step 2 Click the Insert OAM Cell to ATM tab.
Step 3 Enable/Disable the AIS/RDI insertion function according to the network plan.
Step 4 Click Apply, and close the dialog box displayed.

----End
A.11.10.2 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.
Issue 01 (2016-04-30)

1023

Configuration Guide
A Task Collection

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the Segment End Attributes tab.
Step 3 Set the segment and end attributes of AIS/RDI according to the planning information.
----End
A.11.10.3 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
NOTE
Context
NOTE
Issue 01 (2016-04-30)

1024

Configuration Guide
A Task Collection
Procedure
Step 2 Click the CC Activation Status tab.
Step 3 Configure the parameters of the CC test according to the planning information.
----End
A.11.10.4 Querying or Setting LLIDs

This topic describes how to query or set locate loopback IDs (LLIDs). LLIDs need to be
configured before an LB test.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the LLID tab.
Step 3 Set the LLIDs according to the planning information.
----End
Issue 01 (2016-04-30)

1025

Configuration Guide
A Task Collection

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
NOTE
Context
NOTE
Procedure
Step 2 Click the Remote Loopback Test tab.
Step 3 Configure the attributes of the LB test according to the planning information.
Step 4 Select an ATM connection for which an LB test needs to be performed.
NOTE
By pressing the Ctrl key on the keyboard, you can select multiple ATM connections at one time.
Step 5 Click Test, and close the dialog box that is displayed.
Step 6 Check Test Result.
----End
A.11.11 Managing MP Groups

MLPPP allows one or more PPP links that are connected to the same NE to be aggregated as
an MP group and therefore carry MPLS tunnels. The OptiX RTN 905 does not support
MLPPP.
A.11.11.1 Creating MP Groups

To allow an MLPPP link to carry MPLS tunnels, you need to create an MP group.
Issue 01 (2016-04-30)

1026

Configuration Guide
A Task Collection
Prerequisites
l
Multiple serial ports or E1 ports have been configured with the PPP protocol activated.

U2000
NOTE
Procedure
Interface Management > MP Group Management from the Function Tree.
Step 3 Click New.
Step 4 Set MP group parameters.
Issue 01 (2016-04-30)

1027

Configuration Guide
A Task Collection
----End
A.11.11.2 Querying the MP Group Protocol Information

This section describes how to learn the operating information of the MLPPP protocol.
Prerequisites
l
An MP group has been created.

U2000
NOTE
Issue 01 (2016-04-30)

1028

Configuration Guide
A Task Collection
Procedure
Step 3 Click Running Status. Check Link Status. Then, close the dialog box that is displayed.
----End
A.12 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.12.1 Managing Clocks at the Physical Layer

This section describes how to synchronize clock signals by transmission of reference clock
signals at the physical layer.
A.12.1.1 Setting the SDH Retiming Function

This section describes how to use the SDH retiming function to set all SDH ports on a
channelized STM-1 interface board to trace the SDH line clock from one of the SDH ports,
when an NE is connected to a third-party network through a channelized STM-1 channel and
the NE clock and the third-party network clock are asynchronous.
Prerequisites
l
The corresponding boards have been added in the NE Panel.

U2000
NOTE
Procedure
choose Configuration > Clock Transparent Transmission > Clock Transparent
Transmission.
Step 2 Set the SDH retiming function.
1.
Set Retiming Mode to Line Clock.
2.
Select the SDH port for receiving clock signals from the third-party network from the
drop-down list of Line Clock Port according to the network plan. Set all SDH ports on
the channelized STM-1 interface board to use the SDH port for transmitting and
receiving SDH frames.
Issue 01 (2016-04-30)

1029

Configuration Guide
A Task Collection
Step 3 Click Apply.

----End
A.12.1.2 Setting the E1 Clock Source for a Channelized STM-1 Interface Board
Each channelized STM-1 interface board can transparently transmit two E1 clock sources.
You can set the mapping between E1 clock sources and E1 lines.
Prerequisites
l
The channelized STM-1 interface board has been added in the NE Panel.

U2000
NOTE
Procedure
choose Configuration > Clock Transparent Transmission > Clock Transparent
Transmission.
Step 2 Set the E1 clock source for a CQ1.
1.
Set Retiming Mode to System Clock.
2.
Select the 5th and 6th E1 clock sources for the channelized STM-1 interface board from
the drop-down lists of Port and Timeslot according to the network plan.
Step 3 Click Apply.

----End
A.12.1.3 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.
Issue 01 (2016-04-30)

1030

Configuration Guide
A Task Collection
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Priority.
Step 2 Click the System Clock Source Priority List tab.
The Add Clock Source dialog box is displayed.
Step 4 Select the clock sources.

NOTE
Hold the Ctrl key on the keyboard to select multiple clock sources.
Step 5 Click OK.

Step 6 Optional: Repeat Step 3 to Step 5 to add other clock sources.
Step 7 Optional: Select a clock source and click
this clock source.
or
to adjust the priority of
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.
Issue 01 (2016-04-30)

1031

Configuration Guide
A Task Collection
Step 9 Click Apply.

----End
A.12.1.4 Configuring Clock Subnets

For simple networks, such as chain networks, configure the clock source protection or only
configure the clock priority to implement the clock source protection. For complex networks,
such as ring networks or intersecting and tangent rings that are derived from ring networks,
configure clock subnets and enable the standard SSM protocol or extended SSM protocol to
implement the clock source protection.
Prerequisites
l
The priority list of the clock source must be configured.

U2000
NOTE
Procedure
Physical Clock > Clock Subnet Configuration.
Step 2 Click the Clock Subnet tab.
Step 3 Start the clock protection protocol and configure its parameters.
Step 4 Click Apply.

----End
A.12.1.5 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.
Issue 01 (2016-04-30)

1032

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Physical Clock > Physical Clock Subnet Configuration.
Step 2 Click the Received Quality tab.
Step 3 Click the Clock Source Quality tab.
Step 4 Set the user-defined clock quality.
NOTE
Generally, it is recommended that you use the default value.
Step 5 Click Apply.

Step 6 Click the Manual Setting of 0 Quality Level tab.
Step 7 Set the clock quality for which the quality level is zero.
NOTE
Generally, it is recommended that you use the default value.
Step 8 Click Apply.

----End
A.12.1.6 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
Issue 01 (2016-04-30)

1033

Configuration Guide
The standard SSM or extended SSM protocol is enabled.
A Task Collection

U2000
NOTE
Procedure
Step 2 Click the SSM Output tab.
Step 3 Set the SSM control status.
NOTE
l Output S1 Byte Info is valid only when the SSM protocol or the extended SSM protocol is started.
l Output S1 Byte Info indicates whether the SSM is output at the line port.
l When the line port is connected to an NE in the same clock subnet, set Output S1 Byte Info to Enabled.
Otherwise, set this parameter to Disabled.
Step 4 Click Apply.

----End
A.12.1.7 Configuring the Clock ID Output Status

After the extended synchronization status message (SSM) protocol is enabled, the NE
transmits the clock ID to other NEs through the radio link or optical line by default. To
prevent two clock subnets from affecting each other, the NE needs to forbid the clock ID from
being transmitted on the link that is connected to other clock subnets.
Prerequisites
l
The extended SSM protocol must be enabled.

U2000
NOTE
Issue 01 (2016-04-30)

1034

Configuration Guide
A Task Collection
Procedure
Step 2 Click the Clock ID Output tab.
Step 3 Set the clock ID control status.
NOTE
l Output Clock ID is valid only when the extended SSM protocol is started.
l Output Clock ID indicates whether the clock source ID is output at the line port.
l If the line ports are connected to the NEs in the same clock subnet and if the extended SSM protocol is
started on the opposite NE, Output Clock ID is set to Enabled. Otherwise, this parameter is set to
Disabled.
Step 4 Click Apply.

----End
A.12.1.8 Modifying the Parameters of the Clock Output

The NE outputs the 2-Mbit/s external clock regardless of the clock quality.
Prerequisites

U2000
NOTE
Procedure
Physical Clock > Phase-Locked Source Output by External Clock.
Step 2 Modify the parameters of the clock output.
Step 3 Click Apply.

----End
A.12.1.9 Configuring Clock Sources for External Clock Output

By default, OptiX RTN 900 allows output of the system clock source through the external
clock port. If the external clock port needs to transmit other clock sources, such as a clock
Issue 01 (2016-04-30)

1035

Configuration Guide
A Task Collection
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
l

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
Clock > Physical Clock > Clock Source Priority from the Function Tree.
Step 2 Click the Priority for PLL Clock Sources of 1st External Output tab.
The Add Clock Source dialog box is displayed.
Step 4 Configure the clock sources for external clock output based on network planning information.
NOTE
To select more than one clock source at a time, press and hold the Ctrl key when selecting the clock
sources.
NOTE
l When the PLL clock source of the external clock port extracts the system clock (namely, the local clock
of the NE), Clock Source takes its default value Internal Clock Source. In this case, no manual
configuration is required.
l When the PLL clock source of the external clock port needs to extract the clock from an SDH line board,
clock from a radio link, clock from a PDH tributary board, or synchronous Ethernet clock, set Clock
Source to the corresponding clock source according to the network planning information.
Step 5 Click OK.

Step 6 Select Internal Clock Source and click Delete.
----End
Issue 01 (2016-04-30)

1036

Configuration Guide
A Task Collection
A.12.1.10 Changing the Conditions for Clock Source Switching

You can change the default conditions for clock source switching of the NE for special
purposes.
Prerequisites
l

U2000
NOTE
Procedure
Physical Clock > Clock Source Switching.
Step 2 Click the Clock Source Switching Condition tab.
Step 3 Change the conditions for clock source switching.
Step 4 Click Apply.

----End
A.12.1.11 Modifying the Recovery Parameter of the Clock Source

In the case of the special requirements, you can modify the recovery parameter of the clock
source.
Prerequisites

U2000
NOTE
Procedure
Physical Clock > Clock Source Switching.
Issue 01 (2016-04-30)

1037

Configuration Guide
A Task Collection
Step 2 Click the Clock Source Reversion tab.

Step 3 Set the recovery parameter of the clock source.
Step 4 Click Apply.

----End
A.12.1.12 Querying the Clock Synchronization Status

You can know the current clock synchronization status of an NE by querying the clock
synchronization status.
Prerequisites

U2000
NOTE
Context
OptiX RTN 905 does not support circuit emulation service (CES) adaptive clock recovery
(ACR) clocks.
Procedure
Physical Clock > Clock Synchronization Status.
Step 2 Click Query.
NOTE
This operation is for querying the synchronization state of physical clocks and cannot be used to query the
synchronization status of 1588v2 clocks.
----End
A.12.2 Managing CES ACR Clocks

CES ACR refers to a function that uses the adaptive clock recovery (ACR) technology to
recover clock synchronization information carried by CES packets.
A.12.2.1 Configuring a CES Transmit Clock

This section describes how to configure a CES ACR transmit clock.
Issue 01 (2016-04-30)

1038

Configuration Guide
A Task Collection
Prerequisites
l
set to CES.

U2000
NOTE
Procedure
Step 1 Customize the configuration procedure by board.
If the CES ACR Transmit Clock Is from...
Then...
A port on an ML1/MD1 board,
A port on a CQ1 board or of an OptiX RTN 905,
Step 4 Select a desired port, and set Retiming Mode to Line Clock Mode.
Step 5 Click Apply.
Step 7 Select the desired NE from the object tree in the NE Explorer, and choose Configuration >
Clock > CES Transmit Clock.
Step 8 Set parameters for the CES transmit clock.
1.
Click New.
2.
Set parameters for the CES transmit clock in the displayed dialog box.
Issue 01 (2016-04-30)

1039

Configuration Guide
3.
A Task Collection
Click Apply.
Step 9 Configure CES services that use the CES transmit clock.
1.
Select the configured CES transmit clock and click New in the lower right corner.
2.
Select a CES service in the displayed dialog box.
Issue 01 (2016-04-30)

1040

Configuration Guide
3.
A Task Collection
Click OK.
----End
A.12.2.2 Configuring the Primary Clock for an ACR Clock Domain

An ACR clock domain can use the clock extracted from a CES service as its primary clock.
Prerequisites
l
CES services are configured.
Precautions
NOTICE
l An ACR clock domain can bind only the CES services on a local board.
l On the MD1 board, the four ACR clock domains can bind the CES services either from
the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four
ACR clock domains cannot simultaneously bind the CES services from the former 16 E1
ports and from the latter 16 E1 ports on a local board.
l A maximum of four ACR clock domains can bind CES services.

U2000
NOTE
Procedure
Clock > ACR Clock from the Function Tree.
Step 2 In CES Service, select a CES service for primary clock extraction.
----End
Issue 01 (2016-04-30)

1041

Configuration Guide
A Task Collection
A.12.2.3 Configuring Ports Using the Clock Domain

A CES E1 port can transmit the clock information in the system clock domain or CES ACR
clock domain.
Prerequisites
l
CES services are configured.
Precautions
NOTICE
l 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 The ACR clock domain cannot contain ports from different boards.
l For a Smart E1 interface board, the E1 port providing the master clock in the ACR clock
domain must be added in the clock domain. For CD1 and VS2 on OptiX RTN 905, if only
part E1s of a port need to be added in the ACR clock domain, add the E1s corresponding
to the master clock in the ACR clock domain; if all E1s of a port need to be added in the
ACR clock domain, directly add the port to the ACR clock domain, instead of adding all
E1s in this port one after another.
l On the MD1 board, the four ACR clock domains can bind the CES services either from
the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four
ACR clock domains cannot simultaneously bind the CES services from the former 16 E1
ports and from the latter 16 E1 ports on a local board.

U2000
NOTE
Procedure
Clock > Clock Domain from the Function Tree.
Step 2 Click New.
The Create Clock Domain Port dialog box is displayed.
Issue 01 (2016-04-30)

1042

Configuration Guide
A Task Collection
Step 3 Select Clock Domain.

Step 4 In Clock Domain Board, select the board where the ACR clock domain resides.
Step 5 Set the application ports to the ACR clock domain.
1.
In Board, select a board that uses the ACR clock domain.
2.
In Available Port, select a port that transmits CES services.
3.
Click
Step 6 Click OK.

----End
A.12.2.4 Querying the CES ACR Clock Status

This section describes how to query the current CES ACR clock status and the clock source it
is tracing.
Prerequisites
l
The CES ACR clock has been configured.

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

1043

Configuration Guide
A Task Collection
Step 2 Click Query, and close the dialog box displayed.

Step 3 Query the CES ACR clock status.
----End
A.12.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 highprecision timing signals for 3G base stations.
A.12.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
l

U2000
NOTE
Procedure
Clock > Frequency Selection Mode from the Function Tree.
Step 2 In Select Frequency Source Mode, select different clock synchronization modes.
Step 3 Click Apply.

----End
A.12.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.
Issue 01 (2016-04-30)

1044

Configuration Guide
A Task Collection
Prerequisites

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute.
Step 2 Click Query to query the PTP system time.
Step 3 In PTP System Time, click
, and then set the system time.
NOTE
Set this parameter for the grandmaster only when it uses local real-time clock as a timescale.
Step 4 Click Apply.

----End
A.12.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

U2000
Issue 01 (2016-04-30)

1045

Configuration Guide
A Task Collection
NOTE
Procedure
Step 2 Set parameters for a PTP clock according to the planning information.
NOTE
If a PTP clock or a clock source priority table is configured, the working mode cannot be changed.
Step 3 Click Apply.

----End
A.12.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
NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree.
Step 2 Click the Port Status tab.
Step 3 Click New.
The Create PTP Clock Port dialog box is displayed.
Issue 01 (2016-04-30)

1046

Configuration Guide
A Task Collection
Step 4 Select the required board, select the corresponding port in Available Port, and then click
.
Step 5 Click OK.
----End
A.12.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, and reference clock source, and
IEEE 1588 adaptive clock recovery (ACR) clock status.
Prerequisites
l
PTP clock ports are added.

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree.
Step 2 Click the Port Status tab.
Step 3 Set parameters for PTP clock port attributes according to the planning information.
Issue 01 (2016-04-30)

1047

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.12.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
NOTE
Procedure
Step 2 Click the Port message tab.
Step 3 Set parameters for PTP clock packets according to the planning information.
Step 4 Click Apply.

----End
A.12.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
NOTE
Issue 01 (2016-04-30)

1048

Configuration Guide
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
A.12.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, BC or TC+BC.

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the Clock Subnet tab.
Step 3 Set Clock Subnet No. according to the planning information.
Step 4 Click Apply.

----End
A.12.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.
Issue 01 (2016-04-30)

1049

Configuration Guide
A Task Collection
Prerequisites
l
The clock working mode is OC, BC or TC+BC.

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the BMC tab.
Step 3 Set the parameters for the BMC algorithm according to the planning information.
Step 4 Click Apply.

----End
A.12.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
NOTE
Procedure
Clock > PTP Clock > External Time Interface from the Function Tree.
Step 2 Click the Basic Attribute tab.
Step 3 Set parameters for the basic attributes of external time ports according to the planning
information.
Issue 01 (2016-04-30)

1050

Configuration Guide
A Task Collection
Step 4 Click Apply.

----End
A.12.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, OC or TC+BC for an NE, and Interface Mode in External
Time Interface is set to External Time Interface.

U2000
NOTE
Procedure
Step 2 Click the BMC tab.
Step 3 Set parameters for the BMC algorithm of external time ports according to the planning
information.
Step 4 Click Apply.

----End
A.12.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
NE Clock Type is set to BC, OC or TC+BC for an NE, and Interface Mode in External
Time Interface is set to External Time Interface.

U2000
NOTE
Issue 01 (2016-04-30)

1051

Configuration Guide
A Task Collection
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
A.13 Ethernet Performance Query

This section describes operations related to Ethernet performance query.
Context
NOTE
You can query real-time performance data and recent performance data.
Ethernet performance is monitored through RMON. Available performance monitoring periods include 30s,
30 minutes, custom period 1 (15 minutes by default), and custom period 2 (24 hours by default).
A.13.1 Browsing Current Ethernet Performance

After setting the RMON statistics group. you can browse real-time Ethernet performance
statistics.
Prerequisites
l
The corresponding board must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Issue 01 (2016-04-30)

1052

Configuration Guide
A Task Collection
Table A-9 Packet plane

Performa
nce
Object
Browsed
Object
Navigation Path
Basic
performan
ce/
Extended
performan
ce
Ethernet
porta
Select the corresponding board from the Object Tree in the NE

Explorer. Choose Performance > RMON Performance from
the Function Tree.
PLA group
performan
ce
PLA
group

Tree and choose Configuration > Physical Link
Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC
group
performan
ce
XPIC
group
XPIC
group
performan
ce
XPIC
group
MPLS
tunnel
performan
ce
MPLS
Tunnel

Tree and choose Configuration > Link Configuration.
2. Select the desired XPIC group, right-click, and choose
Tree and choose Configuration > IF 1+1 Protection.
2. Select the desired 1+1 protection group, right-click, and
choose Browse Performance from the shortcut menu.
3. Select one or more tunnels, right-click the tunnel(s), and
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
shortcut menu.
Issue 01 (2016-04-30)

1053

Configuration Guide
A Task Collection
Performa
nce
Object
Browsed
Object
Navigation Path
Port traffic
classificati
on
performan
ce
Ports that
perform
complex
traffic
classificati
on

Choose 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
NOTE
Complete the operation A.9.8.8 Creating Traffic before monitoring the
port traffic classification performance.
Port
priority
performan
ce
Egress
queues
For FE/GE ports:

Choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
2. Click the Basic Attributes tab.
4. Select the desired egress queue in the Object drop-down list.
For Integrated IP microwave ports:
Microwave Interface from the Function Tree.
Port DS
domain
performan
ce
Ports in a
DS
domain

Choose Configuration > QoS Management > Diffserv
Domain Management > Diffserv Domain Management
2. Select the desired DS domain.
ETH OAM
E-Line
service
performan
ce
Issue 01 (2016-04-30)
E-Line
service

Tree and choose Configuration > Ethernet OAM
Management > Ethernet Service OAM Management.
2. Select the desired MEP, right-click, and choose Browse

1054

Configuration Guide
A Task Collection
Performa
nce
Object
Browsed
Object
Navigation Path
MPLS-TP
OAM
TUNNEL

Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
PW

PW Management.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
Step 2 Click the Statistics Group tab.

Step 3 Set the required parameters for the statistics group.
1.
Select the desired object or port from the drop-down list.
2.
Select the performance items for which statistics need to be collected.
3.
Set Sampling Period.

Sampling Period represents the time unit of the performance statistics.
Step 4 Click Resetting begins.

NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
A.13.2 Configuring Ethernet Performance Threshold-Crossing

Parameters
After setting the RMON alarm group. you can monitor whether the Ethernet performance
value crosses its threshold for a long time.
Prerequisites
l
Issue 01 (2016-04-30)

1055

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Performa
nce
Object
Browsed
Object
Navigation Path
Basic
performan
ce/
Extended
performan
ce
Ethernet
porta

the Function Tree.
PLA group
performan
ce
PLA
group

Aggregation.
XPIC
group
performan
ce
XPIC
group
XPIC
group
performan
ce
XPIC
group
MPLS
tunnel
performan
ce
MPLS
Tunnel

Issue 01 (2016-04-30)

1056

Configuration Guide
A Task Collection
Performa
nce
Object
Browsed
Object
Navigation Path
L2 VPNPW
performan
ce
ETH
PWE3
service

L2 VPN
performan
ce
UNI-UNI
E-Line
service

shortcut menu.
shortcut menu.
Port traffic
classificati
on
performan
ce
Ports that
perform
complex
traffic
classificati
on

NOTE
Port
priority
performan
ce
Egress
queues
For FE/GE ports:

Issue 01 (2016-04-30)

1057

Configuration Guide
A Task Collection
Performa
nce
Object
Browsed
Object
Navigation Path
Port DS
domain
performan
ce
Ports in a
DS
domain

ETH OAM
E-Line
service
performan
ce
E-Line
service
MPLS-TP
OAM
TUNNEL

PW

PW Management.
NOTE
Step 2 Click the Event tab and set the corresponding parameters.
----End
A.13.3 Setting Parameters for Monitoring Historical Ethernet

Performance
After configuring a historical control group, you can specify how the historical Ethernet
performance data is monitored.
Issue 01 (2016-04-30)

1058

Configuration Guide
A Task Collection
Prerequisites
l

U2000
NOTE
NOTE
To set parameters for monitoring historical Ethernet performance of multiple NEs on the U2000, choose
Performance > RMON History Control Group Management from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON
History Control Group.
Step 2 Set the parameters of the historical control group.
----End
A.13.4 Browsing Historical Ethernet Performance Data

After configuring an history group, you can browse the historical performance statistics.
Prerequisites
l
The objects and performance events to be monitored must be set.

U2000
NOTE
Procedure
Issue 01 (2016-04-30)

1059

Configuration Guide
A Task Collection

Performa
nce
Object
Browsed
Object
Navigation Path
Basic
performan
ce/
Extended
performan
ce
Ethernet
porta

the Function Tree.
PLA group
performan
ce
PLA
group

Aggregation.
XPIC
group
performan
ce
XPIC
group
XPIC
group
performan
ce
XPIC
group
MPLS
tunnel
performan
ce
MPLS
Tunnel

L2 VPNPW
performan
ce
ETH
PWE3
service
L2 VPN
performan
ce
UNI-UNI
E-Line
service

shortcut menu.
shortcut menu.
Issue 01 (2016-04-30)

1060

Configuration Guide
A Task Collection
Performa
nce
Object
Browsed
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

ETH OAM
E-Line
service
performan
ce
Issue 01 (2016-04-30)
E-Line
service


1061

Configuration Guide
A Task Collection
Performa
nce
Object
Browsed
Object
Navigation Path
MPLS-TP
OAM
TUNNEL

PW

PW Management.
NOTE
Step 2 Click the History Group tab.

Step 3 Set the parameters of the historical group.
1.
Select the desired object or port from the drop-down list.
2.
Click and specify the required time span.
3.
Select the performance items to browse.
4.
Under History Table Type, set the time span for the performance items to be browsed.
Step 4 Click Query.

----End
A.14 Configuring Auxiliary Ports and Functions

The NE supports auxiliary ports and functions such as asynchronous data service port,
wayside service port, external alarm port, and outdoor cabinet monitoring port.
A.14.1 Configuring Orderwire

The orderwire for an NE provides a dedicated communication channel that the network
maintenance personnel can use.
Prerequisites
l
Issue 01 (2016-04-30)

1062

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
Step 2 Click the General tab.
Step 3 Configure the orderwire information.
Step 4 Click Apply.

Step 5 Optional: Change the overhead bytes occupied by the orderwire.
1.
Click the Advanced tab.
2.
Configure Orderwire Occupied Bytes.
3.
Click Apply.
----End
A.14.2 Configuring the Synchronous Data Service

OptiX RTN 900 supports the transmission of a channel of 64-kbit/s synchronous data service
through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N
frame. Such a service is also called F1 data port service.
Issue 01 (2016-04-30)

1063

Configuration Guide
A Task Collection
Prerequisites
l
The AUX board exists on the NE Panel.

U2000
NOTE
Procedure
Step 2 Click the F1 Data Port tab.
Step 3 Hold on the Ctrl key, select two data channels from Available Data Path, and then click
.
Step 4 Click Apply.

----End
A.14.3 Configuring the Asynchronous Data Service

OptiX RTN 900 supports the transmission of a channel of asynchronous data service with a
maximum rate of 19.2 kbit/s through a user-defined byte in the microwave frame or any byte
within the range of SERIAL1-SERIAL4. Such a service is also called broadcast data port
service.
Prerequisites
l
Issue 01 (2016-04-30)

1064

Configuration Guide
A Task Collection

U2000
NOTE
Procedure
Step 2 Click the Broadcast Data Port tab.
Step 3 Configure the parameters of the broadcast data port.
Step 4 Click Apply.

----End
A.14.4 Configuring the Wayside E1 Service

OptiX RTN 900 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service
through 32 user-defined bytes in the SDH microwave frame.
Prerequisites
l
The IF1 board must be added on the NE Panel.
The DCC channels corresponding to external clocks must be disabled.

U2000
Issue 01 (2016-04-30)

1065

Configuration Guide
A Task Collection
NOTE
Procedure
Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.
Step 4 Click Apply.

----End
A.14.5 Configure External Alarms

After the outputting of external alarms is configured, the alarm information of an OptiX RTN
900 can be output to other equipment. After the inputting of external alarms is configured, the
alarm information of other equipment can be input to an OptiX RTN 900.
Prerequisites
l

U2000
NOTE
Context
The external alarms of OptiX RTN 900 are also considered as housekeeping alarms. The
external alarm port of the NE is a relay port. This port can be either in the "on" state or in the
"off" state.
Procedure
Step 1 Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
Step 2 Configure the input alarm.
1.
Select Input Relay from the drop-down list.
2.
Configure the parameters of the input alarm.
Issue 01 (2016-04-30)

1066

Configuration Guide
3.
A Task Collection
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
A.14.6 Monitoring the Outdoor Cabinet

OptiX RTN 900 supports the function of monitoring the outdoor cabinet and its power
monitoring unit (PMU).
A.14.6.1 Configuring the Function for an Auxiliary Port

An auxiliary port may provide multiple functions, but only one function is available at a time.
When configuring an auxiliary port, you must specify a desired function.
Prerequisites

U2000
NOTE
Procedure
Auxiliary Interface from the Function Tree.
Step 2 Specifies the function of an auxiliary port.
Issue 01 (2016-04-30)

1067

Configuration Guide
A Task Collection
NOTE
l For OptiX RTN 950/950A/980/980L, The ID of the outdoor cabinet monitoring port is 2.
l For OptiX RTN 905/910A, The ID of the outdoor cabinet monitoring port is 1.
l For OptiX RTN 950/950A/980/980L/910A, If the outdoor cabinet of the NE is monitored through an
outdoor cabinet monitoring port, set Interface Mode to MON for the outdoor cabinet monitoring
port.
l For OptiX RTN 905, If the outdoor cabinet of the NE is monitored through an outdoor cabinet
monitoring port, set Interface Mode to External clock (Hz)+outdoor cabinet for the outdoor
cabinet monitoring port.
Step 3 Click Apply.

----End
A.14.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
NOTE
Context
NOTE
l An OptiX RTN 980 and OptiX RTN 980L can be installed in any of the following outdoor cabinets:
APM30 AC and APM30 DC cabinets.
l An OptiX RTN 905, OptiX RTN 950, OptiX RTN 950A, and OptiX RTN 910A can be installed in any of
the following outdoor cabinets: APM30 AC, APM30 DC, OMB AC, and OMB DC cabinets.
Issue 01 (2016-04-30)

1068

Configuration Guide
A Task Collection
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.14.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
NOTE
Procedure
Step 1 In the NE Explorer, select TCU from the Object Tree and choose Configuration >
Function Tree.
Step 2 Select Outdoor cabinet interface from the drop-down list.
Step 3 Optional: Click Query to view the temperature and fan information.
Step 4 Optional: Set the working mode of the fan.

Issue 01 (2016-04-30)

1069

Configuration Guide
1.
Set Work mode.
2.
Set other parameters according to the value of Work mode.
3.
A Task Collection
If you set Work mode to Temperature control speed adjustment, you do not
need to set the other parameters.
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.
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).
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.14.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
NOTE
Context
NOTE
Only APM30 AC and OBM AC cabinets support this operation.
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration >
Function Tree.
Issue 01 (2016-04-30)

1070

Configuration Guide
A Task Collection
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.14.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
NOTE
Context
NOTE
Procedure
Function Tree.
Issue 01 (2016-04-30)

1071

Configuration Guide
A Task Collection
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.14.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
NOTE
Context
NOTE
Procedure
Function Tree.
Step 2 Select Outdoor cabinet alarm threshold from the drop-down list.
Step 3 Select Operation Object, and set Upper Alarm Threshold for Ambient Temperature(C),
Lower Alarm Threshold for Ambient Temperature(C), Upper Alarm Threshold for
Ambient Humidity(RH%) and Lower Alarm Threshold for Ambient Humidity(RH%).
Step 4 Click Apply.
NOTE
----End
Issue 01 (2016-04-30)

1072

Configuration Guide
A Task Collection
A.15 End-to-End Configuration Task Collection

End-to-end configuration is simpler than per-NE configuration.
Note
This topic describes only common end-to-end configuration operations on the OptiX RTN
905. For more details, see the U2000 Online Help.
A.15.1 Configuring a Protection Subnet

A protection subnet is a network structure that is capable of self-protection.
A.15.1.1 Searching for Protection Subnets

This section describes how to search for protection subnets. By searching for protection
subnets, you can synchronize protection attributes that have been configured at the NE layer
to the network layer on the U2000. Then the U2000 automatically generates protection
subnets.
Prerequisites
Procedure
Step 1 Choose Service > SDH Protection Subnet > Search for SDH Protection Subnet from the
main menu.
Step 2 In the Subnets/Selected dialog box, select a subnet and click Next.
Step 3 Click Search.
Step 4 After the protection subnet search is complete, click Next.
Step 5 Click Finish.
----End
A.15.1.2 Creating a Linear MSP Protection Subnet

This section describes how to create a linear MSP protection subnet to protect point-to-point
SDH links.
Prerequisites
l
SDH optical fiber connections have been created between NEs in the main topology.
Configuration data on the U2000 is the same as that on NEs.
Issue 01 (2016-04-30)

1073

Configuration Guide
A Task Collection
Context
NOTE
This section uses Create 1+1 Linear MSP as an example. You can create other types of linear MSP
protection subnets in a similar way.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 1+1 Linear MSP from the main menu.
Step 2 Set parameters for the protection subnet to be created.
Step 3 Click Next.

Working Link and Protection Link are displayed.
----End
A.15.1.3 Creating a Ring MSP Protection Subnet

This section describes how to create a ring MSP protection subnet to protect ring SDH
networks.
Prerequisites
l
Context
NOTE
This section uses Create 2f_MS_SPRing as an example. You can create other types of ring MSP protection
subnets in a similar way.
Issue 01 (2016-04-30)

1074

Configuration Guide
A Task Collection
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 2f_MS_SPRing from the main menu.
Step 2 Set parameters for the protection subnet to be created.
Step 3 Click Next.

----End
A.15.1.4 Managing Protection Subnets

This section describes how to manage protection subnets, including querying the information
about a protection subnet and triggering external switching.
Prerequisites
Procedure
Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnet from the
main menu.
Step 2 Click Query Networkwide Switching Status to query network-wide switching status.
----End
A.15.2 Configuring TDM Services in E2E Mode

The SDH trail management function allows for E2E TDM service configuration.
A.15.2.1 Searching for SDH Trails

This section describes how to search for SDH trails. By searching for SDH trails, you can
synchronize TDM services that have been configured at the NE layer to the network layer on
the U2000. Then the U2000 automatically generates corresponding SDH trails.
Issue 01 (2016-04-30)

1075

Configuration Guide
A Task Collection
Prerequisites
l
TDM services have been configured on a per-NE basis.
Procedure
Step 1 Choose Service > SDH Trail > Search for SDH Trail from the main menu.
The Search for Description dialog box is displayed.
Step 2 Specify Search Strategy and click Next.
NOTE
If you select Search by subnet, click Next after selecting a subnet to be searched for.
Step 3 After the trail search is complete, click Next to view searched new trails.
Step 4 Click Next to view searched discrete services.

----End
A.15.2.2 Creating Server Trails

This section describes how to create server trails. Server trails must be created before VC-3 or
VC-12 service trails are created.
Issue 01 (2016-04-30)

1076

Configuration Guide
A Task Collection
Prerequisites
l
Port attributes have been correctly configured for boards on related NEs.
If a server trail to be created passes through intermediate NEs, create the server trail in
end-to-end mode. In this case, higher order VC-4s pass through intermediate NEs.
If a server trail is created by creating trails between adjacent NEs, creating server trails
does not affect data on the NE side or the NE layer on the U2000 side. It only makes a
mark at the network layer on the U2000 side, which indicates that the VC-4 is used and
cannot be used by other VC-4 trails.
Context
Procedure
Step 1 Choose Service > SDH Trail > Create SDH Trail from the main menu.
Step 2 Set Level to VC4 Server Trail.
Step 3 Double-click the desired NE in the physical topology to configure the source and sink of the
server trail.
Step 4 Optional: Select and right-click the desired node and set it to be an explicit node.
Step 5 In the Calculate Route area, select Auto-calculation.
Issue 01 (2016-04-30)

1077

Configuration Guide
A Task Collection
Step 6 Optional: Select Copy after Creation.
Step 7 Click Apply.

The Operation Result dialog box is displayed, indicating that the operation is successful.
Step 8 Optional: Click Browse Trail. In the Manage SDH Trail window, you can view the created
server trail.
----End
A.15.2.3 Creating Point-to-Point Service Trails

This section describes how to create point-to-point service trails. By specifying a service trail
between the source and sink ends, you can configure point-to-point services in end-to-end
mode.
Prerequisites
l
VC-4 server trails have been created.
Procedure
Step 2 Set Level.
NOTE
Set Level to VC12 for Native E1 services.
Step 3 Configure the source and sink of a point-to-point service trail.

1.
Double-click the source NE in the physical topology.

The Select Board Port-Source dialog box is displayed.
2.
Set the sink board and port according to the network plan.
3.
Set the sink NE by referring to Step 3.1 and Step 3.2.
Issue 01 (2016-04-30)

1078

Configuration Guide
A Task Collection
Step 7 Click Apply.

service trail.
----End
A.15.2.4 Creating SNCP Service Trails

This section describes how to create SNCP service trails. By specifying working and
protection paths between the dual-feed point and the selective-receiving point, you can
configure SNCP services in end-to-end mode.
Prerequisites
l
Port attributes have been correctly configured for boards on related NEs.
VC-4 server trails have been created.
Procedure
Step 2 Set Level.
Issue 01 (2016-04-30)

1079

Configuration Guide
A Task Collection
NOTE
Set Level to VC12 for Native E1 services.
Step 3 Configure the source and sink of a point-to-point service trail.

1.
Double-click the source NE in the physical topology.

The Select Board Port-Source dialog box is displayed.
2.
Set the sink board and port according to the network plan.
3.
Set the sink NE by referring to Step 3.1 and Step 3.2.
Step 5 Configure SNCP.

1.
Click the SNCP Setting tab.
2.
Right-click in the blank area and choose Add from the shortcut menu.
The Add the dual-fed and selective-receiving node dialog box is displayed.
3.
Set Dual-Fed Point and Selective-Receiving Point.
4.
Click OK.
Issue 01 (2016-04-30)

1080

Configuration Guide
A Task Collection
Step 8 Click Apply.

point-to-point SNCP service trail.
----End
A.15.2.5 Copying Service Trails

This section describes how to copy service trails. By copying service trails, you can quickly
create a service trail based on a created SDH trail.
Prerequisites
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set filter criteria and click Filter All.
The SDH trails that meet the criteria are listed in the query result.
Step 3 Select and right-click a desired trail and choose Copy from the shortcut menu.
Issue 01 (2016-04-30)

1081

Configuration Guide
A Task Collection
The Copy dialog box is displayed.

Step 4 Select the source and sink to be copied in Reachable Timeslot/Port and click Add.
Step 5 In Copy Setting, set related parameters.
Step 6 Click OK.

The Operation Result dialog box is displayed.
Step 7 Optional: Click Browse Trail. In the Manage SDH Trail window, you can view the copied
service trail.
----End
A.15.2.6 Managing SDH Trails

This section describes how to manage SDH trails, including querying the information about
an SDH trail, modifying trail parameter settings, and triggering external SNCP switching.
Prerequisites
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set filter criteria and click Filter All.
Issue 01 (2016-04-30)

1082

Configuration Guide
A Task Collection
The SDH trails that meet the criteria are listed in the query result.
Step 3 Select an SDH trail from the list and check Detailed Physical Route.
Step 4 Optional: Select an SDH trail from the list, click the Transmission Media Layer Route tab,
and check Reachable Route Information.
Step 5 Optional: Select an SDH trail from the list, click the Service Layer Route tab, and check
Server Trail Information.
Step 6 Optional: Select an SDH trail from the list, click the Cross-Connection Information tab,
and check Cross-Connection Information.
----End
A.15.2.7 Managing Discrete TDM Services

This section describes how to manage discrete TDM services. Discrete TDM services exist on
a single NE and no SDH trail is available.
Prerequisites
l
Before managing discrete services, search for SDH trails to ensure that discrete service
data is correct. For details, see A.15.2.1 Searching for SDH Trails.
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Discrete Service from the main menu.
A prompt dialog box is displayed.
Step 2 Click OK.
Step 3 In the Set Discrete Service Browse Filter Criteria dialog box, set filter conditions, and click
Filter.
The discrete SDH services that meet the criteria are listed in the query result.
Step 4 Select an SDH discrete service and query details about this service.
----End
A.15.3 Configuring Native Ethernet Services (in an End-to-End

Mode)
The U2000 allows Native Ethernet services to be configured in an end-to-end mode.
Issue 01 (2016-04-30)

1083

Configuration Guide
A Task Collection
A.15.3.1 Searching for Native Ethernet Services

This task synchronizes Native Ethernet services from the NE layer of the NMS to the network
layer of the NMS.
Prerequisites
l
Native Ethernet services are configured on a per-NE basis.
Data is synchronized between the NE and the NMS.
Fiber connections between ports on the service path are correct.
Context
NOTE
This task searches for Native Ethernet services that have been configured on a per-NE basis but have not
formed a topology on the network layer of the NMS. If Native Ethernet services are configured in endto-end mode or have formed a topology on the network layer of the NMS, skip this task and follow
instructions in A.15.3.6 Managing Native Ethernet Services to implement network management.
Procedure
Step 1 Choose Service > Native Ethernet Service > Search for Native Ethernet Service from the
Main Menu.
Step 2 Set the search scope.
If...
Then...
The search scope covers all NEs managed by

the U2000
Select All and go to Step 4.
The search scope is specified
Select Select NE and go to the next step.
Step 3 Add NEs to the search scope.

1.
Issue 01 (2016-04-30)
Click Add.
The Select NE dialog box is displayed.

1084

Configuration Guide
2.
Select the NE in the left area and click
3.
Optional: Repeat Step 3.2.
4.
Click OK.
A Task Collection
Step 4 Select the desired service types.
Step 5 Click Start.

The found Native Ethernet services are listed in Discovery Result.
Step 6 Optional: Select a service and click Jump Service to start service query and maintenance
operations.
----End
Issue 01 (2016-04-30)

1085

Configuration Guide
A Task Collection
A.15.3.2 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.
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.
BPDU Private Service: This parameter takes a fixed value of No.
Customer: This parameter is set as required by a user.
Remarks: This parameter is set as required by a user.
Step 3 Configure the source and sink of the E-Line service.

1.
Double-click the source NE in the Physical Topology tab page.

The Select Source dialog box is displayed.
2.
Select the source board and source port.
3.
Set C-VLAN and S-VLAN for the service source according to the planning rules.
Table A-12 E-Line service types
Issue 01 (2016-04-30)
Service Type
C-VLAN
S-VLAN
Point-to-point transparently transmitted

E-Line service
VLAN-based E-Line service
Set based on the

service plan
QinQ-based E-Line
service
PORT-based
service flow whose
source port is a
UNI port

1086

Configuration Guide
A Task Collection
Service Type
C-VLAN
S-VLAN
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 Optional: Select Deploy and ETH OAM CC.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) in the same maintenance association (MA), and activates continuity check (CC).
Step 5 Click Calculate Route.

The created routes are displayed in Physical Topology
NOTE
If correct routes have not been configured on the U2000, perform Step 6 and then click Calculate Route.
Step 6 Optional: Configure the explicit nodes for the E-Line service.
1.
Click Add.
2.
Select the desired NE from the NE list on the left pane and click
3.
Click OK.
4.
In Explicit Node, set Interface.
Step 7 Optional: Under Node List, set C-VLANs and S-VLANs for each node based on the node
type and service type.
Table A-13 Source NE
Issue 01 (2016-04-30)
Service Type
Out C-VLAN
Out S-VLAN
Point-to-point transparently transmitted ELine service
Null
Null
VLAN-based E-Line
service
default value
Null
VLAN switching is
not performed on
Out Interface.

1087

Configuration Guide
A Task Collection
Service Type
Out C-VLAN
Out S-VLAN
VLAN switching is
performed on Out
Interface.
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.
default value
Null
VLAN switching is
performed on In
Interface.
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.
default value
Null
VLAN switching is
performed on Out
Interface and In
Interface.
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-14 Sink NE
QinQ-based E-Line
service
Table A-15 Intermediate NEs
QinQ-based E-Line
service
Step 8 Click OK.

----End
Issue 01 (2016-04-30)

1088

Configuration Guide
A Task Collection
A.15.3.3 Creating an ERP Ring

This task helps you to create ERP rings, including major rings and sub-rings.
Prerequisites
l
Ethernet boards and IF boards have been added in NE Panel.
Procedure
Step 1 Choose Service > ERPS Ring > Create ERPS Ring from the main menu.
Step 2 Set the basic attributes for an ERP ring as follows:
l
Name: Set this parameter according to the service plan or your preference.
Ring Type: Set the ring type to major ring or sub-ring according to the service plan.
Control VLAN: The control VLAN ID must not be the same as the service VLAN ID.
All NEs on the same ERP ring must use the same control VLAN ID.
Revertive Mode: The default value is usually retained. You can also change the value
Step 3 Add NEs to the ERP ring.

1.
Click Add.
The Select NE tab page is displayed.
2.
Select all NEs that will be added to the ERP ring in the NE list on the left and click
.
3.
Issue 01 (2016-04-30)
Click OK.

1089

Configuration Guide
A Task Collection
Step 4 Set NE port information for the ERP ring.

l
The following is an example of NE port information for a major ring.
The following is an example of NE port information for a sub-ring.
Issue 01 (2016-04-30)

1090

Configuration Guide
A Task Collection
NOTE
l It is recommended that you plan the counterclockwise direction as the main direction of services
transmission, and plan the port that transmits services in the main direction as an east port, and the port
that receives services as a west port.
l Set East Port or West Port to - for the sub-ring ERPS instance on an interconnection node.
l Set ERP Ring Node Flag and Flag Port to matching values according to the network plan by taking the
following suggestions:
Only one node on the ring can be set as the RPL owner or RPL neighbor node for each Ethernet
ring.
If the node is the RPL owner, set this parameter to RPL Port.
If the node is an RPL neighbor node, set this parameter to Neighbor Port.
If the node is the next-hop node of the RPL owner or RPL neighbor node, set this parameter to Next
Neighbor Port.
It is recommended that you set the east port of the RPL owner to RPL Port and the west port of the
RPL neighbor node to Neighbor Port.
It is recommended that you set the east port on RPL owner node's upstream node and the west port
on the RPL neighbor node's downstream node as Next Neighbor Port.
If the node on the ring is not any of the preceding nodes, set this parameter to None.
If the ERPS V1 protocol is used, only RPL Port needs to be set.
Step 5 Set parameters for the ERP ring.
NOTE
If all NEs on the ERP ring are Huawei NEs, it is recommended that the default values be retained for all
parameters.
Step 6 Click OK.

Step 7 Optional: Click Select Associated Master Ring to select the major ring associated with the
sub-ring.
----End
Follow-up Procedure
End-to-end ERPS configuration does not involve the ERPS version configuration. To change
the ERPS version, modify the configuration of involved NEs on a per-NE basis.
A.15.3.4 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
Issue 01 (2016-04-30)

1091

Configuration Guide
A Task Collection
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.
Service Name: This parameter is set based on the service plan or user preference.
Customer: This parameter is set as required by a user.
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.
3.
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-Aware
IEEE 802.1ad bridge-based E-LAN

service
S-Aware
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.8.8.1 Setting the Basic Attributes of Ethernet Ports to change its port mode to
Layer 2.
Issue 01 (2016-04-30)

1092

Configuration Guide
4.
A Task Collection
See the following table to set C-VLAN, S-VLAN, and Encapsulation Type.
Table A-16 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.
Click the Interface Information tab.
3.
Set the general attributes for the bridge-mounted ports.

Issue 01 (2016-04-30)
Enable Port:
n
If a port is in use, set this parameter to Enabled.
If a port is not in use, set this parameter to Disabled.
Working Mode:
n
If a bridge-mounted port is connected to an Ethernet port on the equipment

outside the E-LAN service network, set this parameter to the same value for
the two ports. Generally, the Ethernet port outside the E-LAN service network
works in Auto-Negotiation mode.
If a bridge-mounted port is connected to an Ethernet port on the same E-LAN

service network, set this parameter to Auto-Negotiation for the two ports.
1093

Configuration Guide
A Task Collection
Max Frame Length(bytes): If jumbo frames are transmitted, set this parameter
according to the length of jumbo frames. If jumbo frames are not transmitted, it is
recommended that this parameter should take the default value 1536.
Step 6 Set the advanced attributes for the bridge-mounted ports.

1.
Click
2.
Click the Interface Information tab.
3.
Select the desired bridge-mounted ports.
4.
Click
The NE Explorer window is displayed.

5.
Click the Advanced Attributes tab and set the advanced attributes for the ports.
Loopback Check: To check whether a port is looped, set this parameter to

Enabled.
Broadcast Packet Suppression:

n
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.
Broadcast Packet Suppression Threshold(%):When the proportion of the

broadcast packets in the total packets exceeds the value of this parameter, the
received broadcast packets are discarded. The value of this parameter should be
more than the proportion of the broadcast packets in the total packets before the
broadcast storm occurs. In normal cases, this parameter is set to default value.
Loopback Port Block: To allow a looped port to be automatically blocked, set this
parameter to Enabled. The default value of this parameter is Disabled.
NOTE
a:
6.
For an OptiX RTN 905 2E-provided microwave link for which 1+1 protection or link
aggregation group (LAG) is configured, set parameters only for the main IF_ETH port. The
following operations described in this section are also applicable only to the main port.
For OptiX RTN 905 1Es that are stacked to implement physical link aggregation/ (PLA),
Enhanced physical link aggregation(EPLA), 1+1 hot standby (HSB), 1+1 frequency diversity
(FD), or 1+1 space diversity (SD), set parameters only for IF_ETH ports on main NEs. The
following operations described in this section are also applicable only to main NEs.
Click Apply.
Step 7 Optional: Configure Ethernet Ring Protection Switching (ERPS).

.
1.
Click
2.
Click the ERPS tab. Then, click Add.

The Add ERPS dialog box is displayed.
3.
Set the parameters for the ERPS protection instance.
4.
Click OK.
5.
Set the parameters for the ERPS protocol.
Issue 01 (2016-04-30)

1094

Configuration Guide
A Task Collection
NOTE
Set the parameters based on the network plan. Default values are recommended.
The ID of a Control VLAN must not be the same as any VLAN ID used by Ethernet services. All
ring nodes should use the same Control VLAN ID.
Step 8 Optional: Configure a split horizon group.

NOTE
1.
Click
2.
Click the Split Horizon tab. Then, click Add.

The Add Split Horizon Group dialog box is displayed.
3.
Select the desired ports based on the plan, and click
4.
Click OK.
Step 9 Select Deploy and ETH OAM CC.
NOTE
After ETH OAM CC is selected, the U2000 automatically creates source and sink maintenance end points
(MEPs) in the same maintenance association (MA), and activates continuity check (CC).
Step 10 Click OK.

----End
A.15.3.5 Verifying Native Ethernet Services

This section describes how to use ETH OAM to verify connectivity of Native Ethernet
services.
Prerequisites
l
Native Ethernet services are configured in end-to-end mode and ETH OAM CC are
enabled.
The data on the NE and the NMS is synchronized.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the
main menu.
Step 2 In the Set Filter Criteria dialog box, set filter conditions and click Filter.
The Native Ethernet services that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet service, and choose Ethernet OAM > Ethernet
OAM Test from the shortcut menu.
Issue 01 (2016-04-30)

1095

Configuration Guide
A Task Collection
Step 4 Set Measurement Type to LB,

Step 5 Optional: If Ethernet OAM has not been configured during end-to-end E-LAN service
configuration, the Prompt dialog box is displayed.
1.
Click Add.
2.
Set OAM parameters.
3.
Click OK.
Step 6 Optional: If Ethernet OAM has not been configured during end-to-end E-Line service
configuration, the Prompt dialog box is displayed. Click OK. Ethernet OAM will be
automatically configured.
Step 7 In the LB Test dialog box, select the desired service trail.
NOTE
l An LB test checks whether a service is bidirectional available. For a bidirectional service, select the
NE at either end to initiate an LB test.
l If Ethernet services are in different VLANs, the U2000 automatically selects the service in a VLAN
for an LB test.
l One NE cannot be involved in multiple LB tests simultaneously.
Issue 01 (2016-04-30)

1096

Configuration Guide
A Task Collection
Step 8 Optional: Choose Config LB Parameter from the shortcut menu. Set Sent Packets, Sent
Packets Length, and Sent Packets Priority. Then, click OK.
Step 9 Click Run.

Step 10 Click the LB Testing Information and LB Statistics Information tabs, and determine
whether the service is available based on the displayed information.
Normally, Test Results indicates Test Succeeded.
----End
A.15.3.6 Managing Native Ethernet Services

This section describes how to perform management and maintenance operations, such as
querying information about Native Ethernet Services and deploying/deleting Native Ethernet
Services.
Prerequisites
Issue 01 (2016-04-30)

1097

Configuration Guide
A Task Collection
Procedure
Main Menu.
Step 2 In the Set Filter Criteria dialog box that is displayed, set filter conditions and click Filter.
The Native Ethernet Service that meet the criteria are listed in the query result.
Step 3 Optional: Select the desired Native Ethernet Service from the query result, and view
information in the Topology, NE, Interface and Split Horizon Group tab pages.
Step 4 Optional: Select the desired Native Ethernet Service from the query result, click functional
buttons under the query result or right-click the service and choose options from the shortcut
menu to perform related maintenance operations.
----End
A.15.3.7 Testing the Packet Loss Rate, Delay, or Delay Jitter of a Native Ethernet
Service
This section describes how to test performance (including the packet loss rate, delay, and
delay jitter) of a Native Ethernet service by only one-click.
Prerequisites
l

U2000
U2000.
NOTE
For the restrictions on a service performance test, see ETH OAM in Feature Description.
Procedure
Main Menu.

Issue 01 (2016-04-30)

1098

Configuration Guide
A Task Collection
The Native Ethernet Service that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet Service and choose Native Ethernet OAM > ETH
OAM Test from the shortcut menu.
Step 4 Set Measurement to LM or DM according to the network plan.
Step 5 Click Run.

----End
A.15.3.8 Managing Discrete Services Transmitted in Native Ethernet Mode

Discrete services transmitted in Native Ethernet mode are services that are transmitted in
Native Ethernet mode, but cannot become network-layer services and exist only on isolated
NEs.
Prerequisites
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Discrete Service
from the Main Menu.
The E-Line services that meet the criteria are listed in the query result.
----End
Issue 01 (2016-04-30)

1099

Configuration Guide
A Task Collection
A.15.3.9 Adjusting an E-LAN Service Network

This task adjusts an E-LAN service network after E-LAN services are configured in end-toend mode.
Prerequisites
l
E-LAN services are configured.
Procedure
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 01 (2016-04-30)
Service Type
Tag Type

service
Tag-transparent

service
C-Aware
IEEE 802.1ad bridge-based E-LAN

service
S-Aware

1100

Configuration Guide
5.
A Task Collection
.
6.
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
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 01 (2016-04-30)

1101

Configuration Guide
A Task Collection

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
6.
Click OK.
7.
Set the general attributes for the bridge-mounted ports.
Step 6 Configure a split horizon group.

NOTE
1.
Click the Split Horizon tab. Then, click Add.

The Add Split Horizon Group dialog box is displayed.
2.
Select the desired ports based on the plan, and click
3.
Click OK.
----End
A.15.4 Searching for MPLS Tunnels and PWE3 Services

This section describes how to synchronize the configuration data of MPLS tunnels and PWE3
services from the NE layer of the U2000 to the network layer of the U2000.
Prerequisites
l
MPLS tunnels and PWE3 services have been correctly configured for NEs.
The configuration data on the U2000 side is the same as the configuration data on the NE
side.
Issue 01 (2016-04-30)

1102

Configuration Guide
A Task Collection
Procedure
Step 1 Choose Service > Search for Service from the Main Menu.
The Search for Service dialog box is displayed.
Step 2 Set the search domain.
1.
Select Select NE and click Add.

2.
Select the desired NE and click OK.

The NEs are displayed in the NE list.
Step 3 Configure the service type to search for.

1.
In the service list on the left, select one or more service types.
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 01 (2016-04-30)

1103

Configuration Guide
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.
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.
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.15.5.6 Managing MPLS Tunnels in an End-to-End Mode

to query and maintain the found MPLS tunnels.
Follow the instructions in A.15.6.11 Managing and Maintaining PWE3 Services to

query and maintain the found PWE3 services.
Follow the instructions in A.15.5.7 Managing Discrete MPLS Tunnels to query and
maintain the found discrete MPLS tunnels.
Follow the instructions in A.15.6.12 Managing Discrete PWE3 Services to query and
maintain the found discrete PWE3 services.
A.15.5 Configuring MPLS Tunnels in an End-to-End Mode

Configuring MPLS tunnels in an end-to-end mode is the prerequisite for configuring PWE3
services.
Issue 01 (2016-04-30)

1104

Configuration Guide
A Task Collection
A.15.5.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 microwave 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 > IP Address Management from the Main Menu.
Step 2 Click New.
Step 4 Click OK.

----End
A.15.5.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
Procedure
Step 1 Choose Inventory > Link Management from the Main Menu.
Step 2 Click New.
The system displays the Create Link dialog box.
Issue 01 (2016-04-30)

1105

Configuration Guide
A Task Collection
Step 3 Click New.

Step 4 Set Source NE, Source Port, Sink NE, and Sink Port for the L2 link.
----End
Follow-up Procedure
If alarms are reported on the created L2 link, verify the following items.
l
Fibers/cables are correctly connected.
The port IP addresses at both ends of the L2 link are in the same network segment.
A.15.5.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.
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.
Context
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.
Issue 01 (2016-04-30)

1106

Configuration Guide
A Task Collection
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu.
Step 2 Set attributes for MPLS tunnels.
The values for the related parameters are provided as follows.
l
Tunnel Name: Unless otherwise specified, this parameter takes its default value, which
is automatically generated by the U2000 according to the naming rules.
Protocol Type: MPLS
Signaling Type: Static CR
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.
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.
Protection Type: Protection-Free
Step 3 Configure on the nodes at both ends of an MPLS tunnel.

1.
Click Add > NE.
2.
In the Select NE dialog box that is displayed, select one or more NEs, and click
3.
Click OK.
Issue 01 (2016-04-30)

1107

Configuration Guide
4.
A Task Collection
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, set restrictions from the shortcut menu, and click
Calculate route.
Step 5 Optional: Manually specify a route for a tunnel.

1.
Do not select Auto-Calculate route.
2.
Optional: Set Restriction Bandwidth(kbit/s).

It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this
parameter according to the planned tunnel bandwidth.
3.
In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology
tab page.
Issue 01 (2016-04-30)

1108

Configuration Guide
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.
1.
Click Details.
2.
Set information about the working tunnel in the Working Tunnel tab on the right.
3.
Issue 01 (2016-04-30)
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.
LSP Type and EXP: Unless otherwise specified, the two parameters take their
default values.
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.
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.
Optional: Click Configure MPLS-TP OAM to configure MPLS-TP OAM complying

with ITU-T Y.1731. Click Add in the dialog box that is displayed, set the required
parameters, and click OK.
1109

Configuration Guide
A Task Collection
The values for the related parameters are provided as follows:
4.
OAM Status: Set this parameter to Enable.

It is recommended that you set CC Packet Sending Priority to 7 to ensure that CC
packets are preferentially forwarded. CC Packet Sending Priority can be set only
for egress nodes on bidirectional tunnels and ingress nodes.
Detection Mode can be set only for a T-PE. Unless otherwise specified, it is
recommended that this parameter takes its default value Adaptive.
Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
Issue 01 (2016-04-30)
Detection Packet Type: Set this parameter to FFD.

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
Other parameters: Unless otherwise specified, it is recommended that the
parameters take their default value.

1110

Configuration Guide
5.
A Task Collection
Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Reverse Working Tunnel tabs.
Step 7 Choose Deploy and then Enable.

l
After Deploy is selected, the tunnel configuration data is saved on the U2000 side and
deployed to the NE side. Otherwise, the service configuration data is saved on the U2000
side but is not deployed to the NE side.
The OptiX RTN 905 supports only enabling tunnels.
Step 8 Click OK.

Step 9 In the Operation Result dialog box that is displayed, select View Tunnel.
The created tunnels are listed in the tunnel list.
----End
Follow-up Procedure
Follow the instructions in A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode to
query and maintain the created MPLS tunnels.
A.15.5.4 Creating MPLS Tunnels Configured with MPLS APS Protection in an

End-to-End Mode
This section describes how to create MPLS tunnels configured with MPLS APS protection in
an end-to-end mode.
Prerequisites
l
The basic attributes of the MPLS nodes have been correctly configured.
Parameters related to MPLS ports have been correctly configured.
Issue 01 (2016-04-30)

1111

Configuration Guide
A Task Collection
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.
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.
Context
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.
Protocol Type: MPLS
Signaling Type: Static CR
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.
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.
Protection Type: 1:1
Switching Mode: Unless otherwise specified, it is recommended that you set this
parameter to Double-Ended.
Issue 01 (2016-04-30)

1112

Configuration Guide
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 01 (2016-04-30)

1113

Configuration Guide
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, set restrictions in the
dialog box displayed, and click Calculate route.
Step 5 Optional: Manually specify a route for a tunnel.

1.
Do not select Auto-Calculate route.
2.
Optional: Set Restriction Bandwidth(kbit/s).

It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this
parameter according to the planned tunnel bandwidth.
3.
In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology
tab page.
Issue 01 (2016-04-30)

1114

Configuration Guide
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.
3.
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.
LSP Type and EXP: Unless otherwise specified, the two parameters take their
default values.
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.
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.
Optional: Click Configure MPLS-TP OAM to configure MPLS-TP OAM complying

with ITU-T Y.1731. Click Add in the dialog box that is displayed, set the required
parameters, and click OK.
The values for the related parameters are provided as follows:
Issue 01 (2016-04-30)
OAM Status: Set this parameter to Enable.
It is recommended that you set CC Packet Sending Priority to 7 to ensure that CC

packets are preferentially forwarded. CC Packet Sending Priority can be set only
for egress nodes on bidirectional tunnels and ingress nodes.
Detection Mode can be set only for a T-PE. Unless otherwise specified, it is
recommended that this parameter takes its default value Adaptive.

1115

Configuration Guide
4.
A Task Collection
Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
5.
Issue 01 (2016-04-30)
Detection Packet Type: Set this parameter to FFD.
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
Other parameters: Unless otherwise specified, it is recommended that the

parameters take their default value.
Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Protection Tunnel tab, or the Reverse Working Tunnel, Forward Protection Tunnel,
and Reverse Protection Tunnel tabs.
1116

Configuration Guide
A Task Collection
Step 7 Click Configure Protection Group. In the dialog box displayed, set attributes about MPLS
APS protection groups and click OK.
l
Revertive Mode: Unless otherwise specified, it is recommended that you set this
parameter to Revertive.
Other parameters: Unless otherwise specified, it is recommended that the parameters

take their default value.
Step 8 Choose Deploy and then Enable.

l
deployed to the NE side. Otherwise, the service configuration data is saved on the U2000
side but is not deployed to the NE side.
The OptiX RTN 905 supports only enabling tunnels.
Step 9 Click OK.

Step 10 In the Operation Result dialog box that is displayed, select View Tunnel.
The created tunnels are listed in the tunnel list.
----End
Follow-up Procedure
l
Follow the instructions in A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode

to query and maintain the created MPLS tunnels.
Follow the instructions in A.15.5.9 Managing MPLS APS Protection Groups in an

End-to-End Mode to query and maintain the created MPLS APS protection groups.
Issue 01 (2016-04-30)

1117

Configuration Guide
A Task Collection
A.15.5.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.
on the right and set parameters about the LSP ping/LSP

Step 5 Optional: Click the
traceroute test in the dialog box that is displayed.
l
Packet Size: Set this parameter according to requirements.
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.
Other parameters: Other parameters take their default values.
Issue 01 (2016-04-30)

1118

Configuration Guide
A Task Collection
Step 6 Click Run.

Step 7 After the verification, query the verification result of each MPLS tunnel.
----End
A.15.5.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
related maintenance operations.
----End
A.15.5.7 Managing Discrete MPLS Tunnels

This section describes how to query or delete discrete MPLS tunnels.
Prerequisites
Issue 01 (2016-04-30)

1119

Configuration Guide
A Task Collection
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.15.5.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.15.5.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.
Prerequisites
Issue 01 (2016-04-30)

1120

Configuration Guide
A Task Collection
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.15.5.10 Testing the Delay and Delay Variation of an MPLS Tunnel

This section describes how to test the delay and delay variation of an MPLS tunnel.
Prerequisites
l

U2000
U2000.
NOTE
l It is recommended that you measure the performance of MPLS tunnels deployed in end-to-end manner by
performing the preceding procedure. For MPLS tunnels deployed on a per-NE basis, it is recommended
that you convert the MPLS tunnels to end-to-end ones by referring to A.15.4 Searching for MPLS
Tunnels and PWE3 Services.
l To perform performance measurement for an MPLS tunnel in the NE Explorer, select the desired MPLS
tunnel, right-click, and choose Performance Statistics Management from the shortcut menu. In the
displayed dialog box, create the corresponding monitoring instance. Note that the PE at both ends must be
configured with the corresponding performance monitoring instance for this MPLS tunnel. Otherwise,
errors occur during performance measurement.
Procedure
Step 3 Right-click the desired tunnel and choose Performance > Create Monitoring Instance from
the shortcut menu.
Issue 01 (2016-04-30)

1121

Configuration Guide
A Task Collection
Step 4 Query the variation of an MPLS tunnel according to testing instances in the U2000 User
Guide for PMS.
----End
A.15.5.11 Starting a TST Test Provided by MPLS-TP Tunnel OAM

RTN supports testing the packet loss on an MPLS tunnel.
Prerequisites
l
MPLS-TP tunnel OAM has been enabled for both the source MP and the sink MP and

U2000
l
the U2000.
operation.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all MPLS
tunnels that meet the filter conditions.
menu.
Issue 01 (2016-04-30)

1122

Configuration Guide
A Task Collection
----End
A.15.6 Configuring PWE3 Services in an End-to-End Mode

This section describes how to configure a PWE3 service based on a default or customized
service template, in an end-to-end mode.
A.15.6.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 905 does not support
default parameter values in the service template, the U2000 displays parameter values
defaulted to the OptiX RTN 905.
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.
Issue 01 (2016-04-30)

1123

Configuration Guide
A Task Collection
The templates that meet the criteria are listed in the query result.
Step 3 Select the desired template and click Clone.
Step 4 In the Clone dialog box that is displayed, modify the template name and parameter values,
and select/deselect Set as Default Template.
NOTE
Parameters whose default values have been changed must be selected.
Step 5 Click OK.

----End
A.15.6.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.
Issue 01 (2016-04-30)

1124

Configuration Guide
A Task Collection
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.
Service Type: CES
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.
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.
For SAToP CES services, deselect Channeled.
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.

Issue 01 (2016-04-30)

1125

Configuration Guide
A Task Collection
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.
PW ID, Forward Label, and Reverse Label: Set these parameters according to the
service planning information. If the parameter values are not specified in the service
planning information and the entire network is managed by the U2000, the U2000
automatically allocates values for these parameters.
NOTE
If these parameters need to be set according to planning information when multiple pairs of source and
sink ports have configured, you need to set the parameters separately for each pair of source and sink
ports.
Step 5 Optional: Set the advanced attributes of the PW.

1.
Click Detail.
2.
In the Advanced PW Attribute tab page, set the advanced attributes of the PW.
Unless otherwise specified, it is recommended that all parameters in the tab take their
default values.
Step 6 Select Deploy and Enable at the lower left corner.

l
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.
The OptiX RTN 905 only supports enabling PWE3 services.
Step 7 Click OK.

Step 8 In the Operation Result dialog box that is displayed, select Browse Trail.
The new CES service is displayed in the PWE3 service list.
NOTE
If multiple pairs of source and sink service ports have been configured, you need to create a CES service for
each pair of the source and sink ports.
----End
Issue 01 (2016-04-30)

1126

Configuration Guide
A Task Collection
Follow-up Procedure
Follow the instructions in A.15.6.11 Managing and Maintaining PWE3 Servicesto query
and maintain the created PWE3 services.
A.15.6.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.
The Create ATM Profile dialog box is displayed.

Step 3 Set the ATM policy profile according to network planning information so that it is available
for traffic management policy selection during ATM connection creation.
Issue 01 (2016-04-30)

1127

Configuration Guide
A Task Collection
Step 4 Click OK.

Step 5 Optional: Check and manage the global ATM policy profile in the Details, NE Reference,
and NE Unreference tabs.
----End
A.15.6.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 01 (2016-04-30)

1128

Configuration Guide
A Task Collection
NOTE
Step 5 Click OK.

Step 6 Right-click in ATM CoS Mapping Profile and choose Add Global Profile from the shortcut
menu.
The Create ATM CoS Mapping Profile dialog box is displayed.

Step 7 Create a global ATM CoS mapping profile according to network planning information.
NOTE
Issue 01 (2016-04-30)

1129

Configuration Guide
A Task Collection
Step 8 Click OK.

----End
A.15.6.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.
Service Type: ATM
to the service naming rules. An appropriate Service Name improves service
maintainability in the case of centralized management.
Step 3 Configure the NEs and service ports on the NEs that are involved in the ATM service.
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.
Issue 01 (2016-04-30)

1130

Configuration Guide
A Task Collection
NOTE
the service in the physical topology and choose related options from the shortcut menu to create the service
source or sink (a virtual node).
Step 4 Optional: Set the basic attributes of the PW.

Set Forward Tunnel, Reverse Tunnel, PW ID, Forward Label, and Reverse Label.
Step 5 Optional: Configure the QoS information of the PW.
1.
Click Detail.
2.
In the PW QoS tab page, configure the QoS information of the PW.
default values.
Step 6 Optional: Set the advanced attributes of the PW.

1.
Click Detail.
2.
In the Advanced PW Attribute tab page, set the advanced attributes of the PW.
default values.
Step 7 Configure ATM connections.

1.
Click ATM Link.

The Configure Link dialog box is displayed.
2.
Click Add Link.
3.
Set the ATM connection attributes according to network planning information.

NOTE
If multiple ATM connections have been planned, configure all the planned ATM connections.
4.
Click OK.
Step 8 Select Deploy and Enable at the lower left corner.

l
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.
For the OptiX RTN 905, generally only ATM PWE3 services are used. Therefore, always
select Enabled.
Step 9 Click OK.

The new ATM service is displayed in the PWE3 service list.
----End
Issue 01 (2016-04-30)

1131

Configuration Guide
A Task Collection
A.15.6.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.
Service Type: ETH
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.
Issue 01 (2016-04-30)
Set VLAN ID to the VLAN ID planned for the Ethernet services over the UNI port.
If you do not configure VLAN ID, Ethernet services exclusively occupy the UNI
port.

1132

Configuration Guide
3.
A Task Collection
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.
4.
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.
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.
Issue 01 (2016-04-30)

1133

Configuration Guide
A Task Collection
Step 5 Optional: Set the advanced attributes of PWs.

1.
Click Detail.
2.
In the PW QoS tab, configure QoS of the PWs.

default values.
3.
In the Advanced PW Attribute tab, set advanced attributes of the PWs.
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.
Control Word: Not in use
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 side but is not deployed to the NE side.
Step 7 Click OK.
The new Ethernet PWE3 service is displayed in the PWE3 service list.
----End
Follow-up Procedure
Query and verify the created Ethernet PWE3 service by referring to A.15.6.10 Verifying PWBased Ethernet Service Configurations (in an End-to-End Mode).
A.15.6.7 Hybird Configuration of E-Line and E-LAN services based on PWE3

Configuring the E-Line and E-LAN services based on PWE3.
Prerequisites
l
The UNI interfaces have been configured correctly.
Issue 01 (2016-04-30)

1134

Configuration Guide
A Task Collection
The Tunnels have been configured correctly.
Context
After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs to the
RNC by means of PWs. The service requirements are as follows:
l
Ethernet services (VLAN ID: 100) at BTS11 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1501), which has a protection tunnel, is available
Ethernet services (VLAN ID: 100) at BTS21 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1701), which has a protection tunnel, is available
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 A-1 Networking diagram (hybrid configuration of E-Line and E-LAN services carried
by PWs)
Working tunnel
(ID=1501)
NNI UNI
BTS11
VLAN 100
NE32
NE31
RTN 950
NE11
RTN 980
R4
NE21
RTN 980
E-Line
E-Line
GE
VPLS
RNC
Working tunnel
(ID=1701)
R4
BTS21
VLAN 100
Procedure
Step 1 Configure hybrid E-Line services and E-LAN services carried by PWs in end-to-end mode.
Issue 01 (2016-04-30)

1135

Configuration Guide
A Task Collection
Figure A-2 Configuring hybrid E-Line services and E-LAN services carried by PWs in endto-end mode
NOTE
For OptiX RTN 950A, OptiX RTN 910A, OptiX RTN 905 or OptiX RTN 950 that uses a CSHU/CSHUA
board, MAC Address Learning Mode can be set to IVL.
Figure A-3 Configuring a split horizon group on the VPLS node
----End
Issue 01 (2016-04-30)

1136

Configuration Guide
A Task Collection
A.15.6.8 Verifying PW Configurations in an End-to-End Mode

This section describes how to verify connectivity of a PW using the PW ping test or PW
traceroute function.
Prerequisites

U2000
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu.
Step 2 Click Filter.
NOTE
After you click Filter, all configured PWE3 services will be displayed.
Step 3 Right-click the PWE3 service to verify and choose Diagnose > 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
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 01 (2016-04-30)

1137

Configuration Guide
A Task Collection

l
Response Mode: Application Control Channel
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 01 (2016-04-30)

1138

Configuration Guide
A Task Collection

l
Response Mode: Application Control Channel
Unless otherwise specified, it is recommended that other parameters take their default
values.
Step 13 Click OK.

Step 14 Click Run.
----End
A.15.6.9 Verifying ATM Services in an End-to-End Mode

This section describes how to use ATM OAM functions to verify connectivity of an ATM
service in an end-to-end mode.
Prerequisites

U2000
Procedure
Step 2 Click Filter.
NOTE
After you click Filter, all configured PWE3 services will be displayed.
Step 3 Right-click the ATM PWE3 service to verify and choose Connectivity Test from the shortcut
menu.
The Connectivity Test dialog box is displayed.
Issue 01 (2016-04-30)

1139

Configuration Guide
A Task Collection
Step 4 Perform an ATM service connectivity test.

1.
In the Link area, select the ATM connection to verify.
2.
In the Detail area, set Direction and Loopback NE.

3.
Source: indicates the forward direction of an ATM connection. For an ATM PWE3
service, Source indicates the direction from the UNI port side to the MPLS port
side.
Sink: indicates the backward direction of an ATM connection. For an ATM PWE3
service, Sink indicates the direction from the MPLS port side to the UNI port side.
Loopback NE:
n
Before a loopback test between two end points, set the remote end point to the
loopback NE. After the loopback test, release the loopback on the remote end
point to restore the entire link.
Before a loopback test between two section points, set the remote section point
to the loopback NE. After the loopback test, release the loopback on the
remote section point to restore the entire link.
Click Start.
In the dialog box that is displayed asking you to confirm the operation, click Yes.
----End
A.15.6.10 Verifying PW-Based Ethernet Service Configurations (in an End-to-End

Mode)
This section describes how to use Ethernet OAM to verify connectivity of a PW-based
Ethernet service.
Prerequisites
l
PW-based Ethernet services have been configured.
Procedure
Step 2 In the Set Filter Criteria window, select Source NE and Sink Node. Click Filter.
Issue 01 (2016-04-30)

1140

Configuration Guide
A Task Collection
Step 3 Right-click the PWE3 service to verify, and choose Ethernet OAM > LB Test... from the
shortcut menu.
Step 4 In the Eth Oam LB Test dialog box that is displayed, select the source NE for initiating an
LB test.
NOTE
l An LB test detects whether a service is bidirectionally available. For a bidirectional service, it is

recommended that you select either end of a PW as the source NE for initiating the LB test.
l If a PW carries Ethernet services from different VLANs, the U2000 automatically select the service
of a VLAN for the LB test.
Step 5 Optional: Right-click the service that is selected for an LB test, and choose Configure...
from the shortcut menu. In the Config Eth Oam LB Test Parameter dialog box that is
Issue 01 (2016-04-30)

1141

Configuration Guide
A Task Collection
displayed, set Sent Packets, Sent Packets Length, and Sent Packets Priority. Then, click
OK.
Step 6 Right-click the service that is selected for an LB test, and choose Run from the shortcut
menu.
Step 7 Click the LB Statistic Information tab and determines whether the service is available based
on the displayed information.
If Test Result displays Test Succeeded, the service is available.
If Packet Loss Ratio(%) displays 100 and Test Result displays Test Failed, the service is
unavailable. If the service is unavailable, check whether the service configurations are
incorrect.
Issue 01 (2016-04-30)

1142

Configuration Guide
A Task Collection
----End
A.15.6.11 Managing and Maintaining PWE3 Services

This section describes how to perform management and maintenance operations, including
querying PWE3 service information, deploying or deleting a PWE3 service, and detecting PW
faults.
Prerequisites
Procedure
The PWE3 services that meet the criteria are listed in the query result.
Step 3 Optional: Select a desired PWE3 service and browse the service information in the
Topology, SAI, Service Parameter, and PW tab pages at the bottom.
Step 4 Optional: Select the desired PWE3 service from the query result, click functional buttons
under the query result or right-click the service and choose options from the shortcut menu to
perform related maintenance operations.
----End
A.15.6.12 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.
Issue 01 (2016-04-30)

1143

Configuration Guide
A Task Collection
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.15.6.13 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW
This section describes how to query the packet loss ratio, delay, and delay variation of a PW.
Prerequisites
l

U2000
U2000.
NOTE
l It is recommended that you measure the performance of PW deployed in end-to-end manner by

performing the preceding procedure. For PW deployed on a per-NE basis, it is recommended that you
convert the PW to end-to-end ones by referring to A.15.4 Searching for MPLS Tunnels and PWE3
Services.
l To perform performance measurement for an PW in the NE Explorer, select the desired PW, right-click,
and choose Performance Statistics Management from the shortcut menu. In the displayed dialog box,
create the corresponding monitoring instance. Note that the PE at both ends must be configured with the
corresponding performance monitoring instance for this PW. Otherwise, errors occur during performance
measurement.
Issue 01 (2016-04-30)

1144

Configuration Guide
A Task Collection
Procedure
Step 3 Right-click the desired PW and choose Performance > Create Monitoring Instance from
the shortcut menu.
Step 4 Query the variation of a PW according to the testing instances in the U2000 User Guide for
PMS.
----End
A.15.6.14 Starting a TST Test of MPLS-TP PW OAM

OptiX RTN 905 supports testing the packet loss on a PW.
Prerequisites
l
MPLS-TP PW OAM has been enabled for both the source MP and the sink MP and

U2000
l
the U2000.
operation.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all PWs that
meet the filter conditions.
Issue 01 (2016-04-30)

1145

Configuration Guide
A Task Collection
----End
A.15.7 Managing Ethernet Services Based on the Service Path

View
This section provides links to operation and maintenance functions related to service paths.
A.15.7.1 Searching for Service Paths Based on VLANs

For E-Line services, this operation can display the transmission path of the VLAN service
flow on one access port. For E-LAN services, this operation can display the broadcast domain
to which the VLAN belongs.
Issue 01 (2016-04-30)

1146

Configuration Guide
A Task Collection
Prerequisites
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Optional: Search for an E-Line service path.
Step 2 Optional: Search for an E-LAN service path.
----End
Issue 01 (2016-04-30)

1147

Configuration Guide
A Task Collection
A.15.7.2 Searching for Service Paths Based on MAC Addresses

For E-LAN services, this operation allows the information of a MAC address learned by each
NE on a service path to be displayed, illustrating the entire service path through which
packets with the MAC address being the source address travel.
Prerequisites
Procedure
Step 1 Search for an E-LAN service path.
Step 2 Query the Learning of MAC Addresses.
Issue 01 (2016-04-30)

1148

Configuration Guide
A Task Collection
----End
A.15.7.3 Checking the Layer 2 Protocols Used by Ethernet Services

This section describes how to check the Layer 2 protocols, including ERPS, MSTP, and STP,
used by E-LAN services based on service paths.
Prerequisites
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure
Issue 01 (2016-04-30)

1149

Configuration Guide
A Task Collection
Step 2 Check the Layer 2 protocols used by the E-LAN services.
----End
A.15.7.4 Performing Intelligent Service Fault Diagnosis for Ethernet Services

This section describes how to intelligently diagnose faults of Ethernet services based on
service paths.
Prerequisites
Issue 01 (2016-04-30)

1150

Configuration Guide
A Task Collection
Procedure
Step 1 Search for services.
Step 2 Select a service to be diagnosed by specifying a service port.
Step 3 Diagnose the service and display the result.
Issue 01 (2016-04-30)

1151

Configuration Guide
A Task Collection
----End
A.15.7.5 Performing E-LAN Service Loopback Detection

This section checks whether a loopback occurs on Ethernet services based on service paths.
Users can quickly rectify a data storm on a loop after finding out the loopback point.
Prerequisites
created.
Procedure
Issue 01 (2016-04-30)

1152

Configuration Guide
A Task Collection
Step 2 Perform E-LAN service loopback detection.
NOTE
If a service is looped back,
can be seen from the icons .
----End
A.15.7.6 Monitoring Ethernet Service Performance and Traffic Volume Based on

Service Paths
This section describes how to monitor Ethernet service performance based on service paths.
Prerequisites
Issue 01 (2016-04-30)

1153

Configuration Guide
A Task Collection
created.
Procedure
Step 1 Search for service paths.
Step 2 Query the real-time and historical performance data of each measured object on each service
path.
The following figure shows how to query the real-time performance data of priority queues on
a port. Querying the real-time and historical performance data of other measured objects is
similar.
Issue 01 (2016-04-30)

1154

Configuration Guide
A Task Collection
----End
A.15.8 Querying the Clock Tracing Relationship

This section describes how to query the tracing relationship of physical layer clocks and PTP
clocks of NEs.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select Clock View from the Current View drop-down list in Main Topology.
Issue 01 (2016-04-30)

1155

Configuration Guide
A Task Collection
NOTE
Alternatively, right-click in the physical topology view and choose Switch to Clock View from the shortcut
menu.
Step 2 Right-click a desired NE and choose Display Current Tracing Path from the shortcut menu.
l
The clock view displays the clock tracing relationship between NEs.
NOTE
The arrow direction in the clock view indicates the clock tracing direction. For example, if
NE(208-1) points to NE(208-2), NE(208-2) traces the clock information transmitted from
NE(208-1).
The number displayed on the continuous line indicates the priority of the traceable clock. The
smaller the number, the higher the priority. The clock view displays the line clock source IDs only.
Internal clock sources are numbered, but their IDs are not displayed in the clock view.
Details about the clock link are displayed in the lower part of the window.
Step 3 Optional: Modify the information displayed in the clock view.

1.
Issue 01 (2016-04-30)
Choose View > Display Setting > Filter from the main menu and set the filter criteria to
filter information displayed in the clock view.

1156

Configuration Guide
2.
A Task Collection
Choose View > Display Setting > Legend from the main menu to browse meanings of
the icons and colors in the clock view.
----End
Issue 01 (2016-04-30)

1157

Configuration Guide
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 TDM Service Parameters
This section describes the parameters related to TDM services.
B.5 Parameters for Board Interfaces
This topic describes the parameters that are related to board interfaces.
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the
packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet
port parameters, and QoS parameters.
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane
EoS/EoPDH plane, including service parameters, protocol parameters, OAM parameters,
Ethernet port parameters, and QoS parameters.
B.8 Parameters for MPLS/PWE3 Services
This topic describes parameters that are related to MPLS/PWE3 services.
B.9 Clock Parameters
This topic describes the parameters that are related to clocks.
B.10 Parameters for the Orderwire and Auxiliary Interfaces
This topic describes the parameters that are related to the orderwire and auxiliary interfaces.
Issue 01 (2016-04-30)

1158

Configuration Guide
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 (U2000)

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Choose File > Discovery > NE from the Main Menu.
Parameters for the Search Field

Parameter
Value Range
Default Value
Description
Address Type
IP Address of GNE
IP Address Range of
GNE
l If the IP protocol is
used on the DCN, you
can search for an NE
based on IP Address
of GNE or IP
Address Range of
GNE.
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.
Issue 01 (2016-04-30)

1159

Configuration Guide
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.
set to IP Address
Range of GNE, enter
the number of the IP
network segment in
which the gateway
NE is located, such as
129.9.255.255.
set to NSAP Address,
enter the NSAP
address of the
gateway NE.
User Name
This parameter specifies

the user name of the
gateway NE.
Password

the password of the
gateway NE.
Issue 01 (2016-04-30)

1160

Configuration Guide
Parameter for Searching for NEs

Parameter
Value Range
Default Value
Description
Create NE after search
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
to be entered when an
NE is created.
l This parameter is
valid only when
Create NE after
search is selected.
Issue 01 (2016-04-30)

1161

Configuration Guide
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
to be entered when an
NE is created.
No
l This parameter is
valid only when
Create NE after
search is selected.
Connection Mode
Common
Security SSL
Security SSL
Issue 01 (2016-04-30)

The communication
between the client and
the server is encrypted if
this parameter is set to
Security SSL.
1162

Configuration Guide
Parameter
Value Range
Default Value
Description
Port
5432

the communication port.
NE Status
Created

whether the found NE is
created.
Uncreated
B.1.1.2 Parameter Description: NE Searching (Web LCT)

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Click NE Search in NE List and select a desired search type.
Parameters for Searching NEs

Parameter
Value Range
Default Value
Description
Domain

the network segment to
be searched.
NE Name
This parameter displays

the name of the found
NE.
NE ID

the ID of the found NE.
Gateway
GNE

whether the found NE is
a GNE or non-GNE.
Non-GNE
Gateway IP Address

the gateway IP address of
the found NE.
Port No.
1400
1400

the communication port
number of the found NE.
Gateway Type
IP Gateway
IP Gateway

the gateway type of the
found NE.
Issue 01 (2016-04-30)

1163

Configuration Guide
Parameters for Managing a Network Segment

Parameter
Value Range
Default Value
Description
Domain Type
GNE IP Domain
GNE IP Domain
l To search for all the

NEs that
communicate with the
GNE, select GNE IP
Domain.
GNE IP Address
l To search for the

GNE only, select
GNE IP Address.
Domain Address
l When Domain Type

is GNE IP Domain,
enter the IP network
segment where the
GNE is located, for
example,
129.9.255.255.
l When Domain Type

is GNE IP Address,
enter the IP address of
the GNE, for
example, 129.9.x.x.
B.1.1.3 Parameter Description: NE Creation (U2000)

This topic describes the parameters that are related to NE creation.
Navigation Path
1.
Choose File > New > NE from the Main Menu.
2.
Choose RTN Series from the Object Tree and select a desired product.
Parameters on the Main Interface

Parameter
Value Range
Default Value
Description
Type
This parameter
indicates the
type of the NE
to be created.
Issue 01 (2016-04-30)

1164

Configuration Guide
Parameter
Value Range
Default Value
Description
ID
1 to 49151
l The ID refers
to the basic
ID. If the
extended ID
is not used,
the basic ID
of an NE
must be
unique on the
networks that
are managed
by the same
NMS.
l This
parameter is
set according
to the
planning
information.
l The NE ID
consisting of
the basic ID
and extended
ID identifies
an NE on the
NMS.
Extended ID
Issue 01 (2016-04-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.
1165

Configuration Guide
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
This parameter
specifies 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 NonGateway if
the new NE
is a nongateway NE.
l This
parameter is
set according
to the DCN
planning if
the new NE
can function
as a gateway
NE or a nongateway NE.
Issue 01 (2016-04-30)

1166

Configuration Guide
Parameter
Value Range
Default Value
Description
Gateway
This parameter
indicates the
gateway NE of
the new NE
when Gateway
Type is set to
Non-Gateway.
Protocol
IP
IP
l This
parameter
needs to be
set when
Gateway
Type is set to
Gateway.
l In other
cases, this
parameter is
set to IP.
IP Address
This parameter
indicates the IP
address of the
new NE. This
parameter needs
to be set when
Affiliated
Gateway
Protocol is set
to IP.
Connection Mode
Common
Security SSL
The
communication
between the
client and the
server is
encrypted if this
parameter is set
to Security
SSL.
Security SSL
Port
5432
This parameter
specifies the
communication
port.
NE User
This parameter
specifies the
user name to be
entered when an
NE is created.
Issue 01 (2016-04-30)

1167

Configuration Guide
Parameter
Value Range
Default Value
Description
Password
This parameter
specifies the
password to be
entered when an
NE is created.
B.1.1.4 Parameter Description: NE Creation (Web LCT)

This topic describes the parameters that are related to NE creation.
Navigation Path
In NE List, click Add NE. Then, select Europe.

Parameter
Value Range
Default Value
Description
NE ID
1 to 49151
l ID indicates the basic NE ID. When

there is no extended ID, the basic NE
IDs must be unique on the networks
that are managed by the same NMS.
l Set this parameter according to the
DCN planning information.
l The NE ID consisting of the basic ID
and extended ID identifies an NE on
the NMS.
Extended ID
1 to 254
l Do not change the Extended ID when

the number of actual NEs does not
exceed the range permitted by the basic
NE ID.
l It is recommended that this parameter
takes the default value.
Gateway Type
IP Gateway
IP Gateway
Serial Port
SSL Gateway
This parameter specifies the type of the

gateway that is used for the
communication between the Web LCT and
the NEs.
USB
Issue 01 (2016-04-30)

1168

Configuration Guide
Parameter
Value Range
Default Value
Description
IP Address
This parameter is
set to 129.9.0.x
when the NE is
delivered from the
factory. "x"
indicates the basic
NE ID that is set
when the NE is
delivered from the
factory.
This parameter specifies the IP address of

the gateway NE to which the NE to be
created belongs. This parameter is
displayed only when Gateway Type is set
to IP Gateway.
Port
l 1400 (when
Gateway Type
is set to IP
Gateway)
l 1400 (when
Gateway Type
is set to IP
Gateway)
This parameter specifies the port

corresponding to the gateway NE to which
the NE to be created belongs.
l COM1-COM32
(when Gateway
Type is set to
Serial Port)
l COM1 (when
Gateway Type
is set to Serial
Port)
1200bps
115200bps
This parameter specifies the

communication rate between the NE to be
created and the corresponding gateway
NE. This parameter is displayed only when
Gateway Type is set to Serial Port.
Baud Rate
2400bps
4800bps
9600bps
19200bps
38400bps
57600bps
115200bps
User Name
lct
This parameter specifies the name of the

user. This parameter can take the default
value in the case of initial login.
Password
The default password of user lct is

password.
B.1.1.5 Parameter Description: Login to an NE (Web LCT)

This topic describes the parameters that are used for logging into an NE.
Navigation Path
In the NE List, select the target NE and click NE Login.
Issue 01 (2016-04-30)

1169

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
User Name
lct
This parameter specifies the name of the

user. This parameter can take the default
value in the case of initial login.
Password
The default password of user lct is

Changeme_123.
Use same user

name and
password to login
Selected
Deselected
When this parameter is selected, enter

User Name and Password to log in to all
the selected NEs.
Use the user name

and password that
was used last time
Selected
Deselected
When this parameter is selected, enter

User Name and Password that were used
for the latest login to log in to the NE.
Deselected
Deselected
B.1.1.6 Parameter Description:Changing NE IDs

This topic describes the parameters that are used for changing NE IDs.
Navigation Path
1.
In the Main Topology, right-click the NE whose ID needs to be changed.
2.
Choose Properties.
3.
Click Modify NE ID.
Issue 01 (2016-04-30)

1170

Configuration Guide
Parameters for Changing NE IDs

Parameter
Value Range
Default Value
Description
New ID
1-49135
l The new ID refers to

the basic ID. If the
extended ID is not
used, the basic ID of
an NE must be unique
on the networks that
are managed by the
same NMS.
l This parameter is set
according to the
network plan.
NOTE
l The NE ID consisting
of the basic ID and
extended ID identifies
an NE on the NMS.
l The NE ID range is 1
to 49151, in which,
49136 to 49151 are
reserved. Therefore,
the configurable values
are from 1 to 49135.
New Extended ID
1 to 254
If the number of existing

NEs does not exceed the
range represented by the
basic ID, do not change
the extended ID.
B.1.1.7 Parameter Description: NE Time Synchronization (U2000)

This topic describes the parameters that are used for synchronizing the time of NEs.
Navigation Path
1.
Choose Configuration > NE Batch Configuration > NE Time Synchronization from

the Main Menu.
2.
Click the NE Time Synchronization tab.
Parameters for NE Time Synchronization

Parameter
Value Range
Default Value
Description
NE Name

the name of the NE.
NE ID

the ID of the NE.
Issue 01 (2016-04-30)

1171

Configuration Guide
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
parameter is set to IP.
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 01 (2016-04-30)

1172

Configuration Guide
Parameter
Value Range
Default Value
Description
Standard NTP Server
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
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 01 (2016-04-30)

1173

Configuration Guide
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.
DST
Selected
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.
l It is recommended
that you use the
default value.
B.1.1.8 Parameter Description: NE Time Synchronization (Web LCT)

This topic describes the parameters that are used for synchronizing the time of NEs.
Navigation Path
1.
In the NE Explorer, select the NE from the Object Tree and then choose Configuration
> NE Time Synchronization from the Function Tree.
2.
Set the synchronous mode.
Issue 01 (2016-04-30)

1174

Configuration Guide
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.
Synchronous Mode
Standard NTP
Null

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

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

Flag
NE ID
NE ID
IP
NE 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 01 (2016-04-30)

1175

Configuration Guide
Parameter
Value Range
Default Value
Description
Standard NTP Server
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
value "0".
l If the NTP server
needs to be
authenticated, the
authentication is
performed according
to the allocated key of
the NTP server. In
this case, the NE
authenticates the NTP
server based on the
key and the
corresponding
password (specified in
the management of
the standard NTP
key).
Standard NTP Version
Set this parameter

according to the settings
for the standard NTP
protocol version used at
the peer end.
No

whether to select a server
preferentially when
multiple NTP servers are
available.
Used First
Yes
No
Issue 01 (2016-04-30)

1176

Configuration Guide
Parameters of the access control rights

Parameter
Value Range
Default Value
Description
ACL No.
1 to 250
This parameter specifies the number of the

ACL.
NE Flag
NE ID
NE ID
l When ECC is used to communicate

with the standard NTP server, set the
parameter to NE ID.
NE IP
l When the IP protocol is used to

communicate with the standard NTP
server, set the parameter to NE IP.
NE
This parameter specifies the ID or IP

address of an NE.
Whether to
Receive Data
Packet
Yes
Yes
This parameter specifies whether to

receive packets from an NE.
Right Level
query
query
The equipment provides four levels of

access control. When an NTP access
request is received on the local equipment,
the request is matched with the levels from
the minimum access limit to the maximum
access limit, and the first matched level
prevails. The matching order is as follows:
No
synchronize
server
peer
l Peer (minimum access limit): The time

request and the control query can be
carried out for the NTP service of the
local equipment. The local clock can
also be synchronized with the remote
server.
l Server: The time request and the
control query can be carried out for the
NTP service of the local equipment, but
the local clock is not synchronized to
the remote server.
l Synchronization: The time query is
allowed for only the NTP service of the
local equipment.
l Query (maximum access limit): The
control query can be carried out only
for the NTP service of the local
equipment.
Issue 01 (2016-04-30)

1177

Configuration Guide
Parameters of the NTP key management

Parameter
Value Range
Default Value
Description
Encryption Type
MD5
MD5
This parameter specifies the MD5 key

algorithm.
Key
1 to 1024
This parameter specifies the number of the

key.
Password
This parameter specifies the password of

the key.
Trusted
Yes
No
If you set this parameter to No, the key is

verified but cannot be trusted during the
clock synchronization. Therefore, the
clock of the NE cannot be synchronized.
No
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)Period(
days).
l It is recommended
that you use the
default value.
DST
Selected
Deselected
Deselected
l This parameter
indicates whether
Synchronization
Starting Time is the
daylight saving time.
according to the
actual situation.
Issue 01 (2016-04-30)

1178

Configuration Guide
Parameter
Value Range
Default Value
Description
Period(days)
1 to 300
l This parameter
indicates the period of
synchronizing the
time of the NE with
the time of the NMS.
l It is recommended
that you use the
default value.
B.1.1.9 Parameter Description: Localization Management of the NE Time

This parameter describes the parameters that are used for localization management of the NE
time.
Navigation Path
1.
Choose Configuration > NE Batch Configuration > NE Time Localization

Management from the Main Menu.
2.
Select the NE for time localization management from the Object Tree, and then click
.
Parameters for Localization Management of the NE Time

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.
Issue 01 (2016-04-30)

1179

Configuration Guide
Parameter
Value Range
Default Value
Description
DST
Selected
Deselected
l The parameters related to daylight

saving time can be valid only when this
parameter is selected.
Deselected

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
B.1.1.10 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 ID
1 to 1024
l This parameter
indicates the
key for NTP
authentication.
l This parameter
is set
according to
the
requirements
of the external
NTP server.
Issue 01 (2016-04-30)

1180

Configuration Guide
Parameter
Value Range
Default Value
Description
Password
l This parameter
indicates the
password that
corresponds to
Key ID.
l This parameter
is set
according to
the
requirements
of the external
NTP server.
Confirm Password
Issue 01 (2016-04-30)

This parameter
indicates the
password that
corresponds to
Key ID again.
1181

Configuration Guide
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
synchronizatio
n service.
No
l When this
parameter is
set to Yes, the
key
verification is
trusted. After
receiving the
key, the NE
provides the
clock
synchronizatio
n service.
l After
receiving an
unknown or
incorrect key,
the NE rejects
the clock
synchronizatio
n service.
Hence, it is
recommended
that you set a
trusted key
only.
B.1.1.11 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.
Issue 01 (2016-04-30)

1182

Configuration Guide
Parameters for Managing Licenses

Parameter
Value Range
Default Value
Description
Board
Specifies the objects to which licenses are

applied.
License File Type
Specifies the license type corresponding to

each board.
Capability
Specifies the capacity of a license file.
Loaded
Specifies whether a license is loaded to an

object.
B.1.1.12 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
This parameter indicates the type of the

NE.
Operation Type

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)
Issue 01 (2016-04-30)
1 to 2880

1183

Configuration Guide
B.1.2 Parameters for Communications Management

This topic describes the parameters that are used for communications management.
B.1.2.1 Parameter Description: NE Communication Parameter Setting

This topic describes the parameters that are used for NE communication setting.
Navigation Path
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.
Gateway IP
Address
0.0.0.0
Subnet Mask
255.255.0.0
In the HWECC solution, an IP address is

set according to the following rules:
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.
l The IP address of an NE cannot be a
broadcast address, a network address,
or an IP address on network segments
127.0.0.0/8, 192.168.0.0/16, and
192.169.0.0/16.
Extended ID
1 to 254
l Do not change the extended ID when

the number of actual NEs does not
exceed the range permitted by the basic
NE ID.
Issue 01 (2016-04-30)

1184

Configuration Guide
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.
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration

This topic describes the parameters that are used for configuring the DCC rate.
Navigation Path
1.
DCC Management from the Function Tree.
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 01 (2016-04-30)

1185

Configuration Guide
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)

value, except for the following cases:
l If the IP DCN 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
AUTO
l An established microwave link uses

TCP/IP if Protocol Type retains the
default value AUTO at both ends of the
link. If Protocol Type is set to TCP/IP
or HWECC at one end of the link and
AUTO at the other end, the link uses
TCP/IP or HWECC.
TCP/IP
L2DCN
AUTO
l If the IP DCN solution is adopted,

Protocol Type is set to TCP/IP.
l When the L2 DCN solution is used, set
Protocol Type to L2DCN.
Issue 01 (2016-04-30)

1186

Configuration Guide
Parameter
Value Range
Default Value
Description
IP Address
l IP Address is available only if

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.
l If OSPF multi-process is enabled on an
NE, this parameter specifies the IP
address for a port that does not belong
to the default process.
Subnet Mask
l Subnet Mask is available only if

parameter specifies the subnet mask of
the non-backbone area port on the
ABR.
NE, this parameter specifies the subnet
mask for a port that does not belong to
the default process.
OSPF Subnet
1 to 4
This parameter indicates the OSPF process

to which a port belongs. When OSPF
multi-process is enabled on an NE, this
parameter needs to be planned and
specified.
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.
DCC Management from the Function Tree.
2.
Click the DCC Transparent Transmission Management tab.
3.
Click Create.
Issue 01 (2016-04-30)

1187

Configuration Guide
Parameters for DCC Transparent Transmission Management

Parameter
Value Range
Default Value
Description
Source Timeslot/
Porta
This parameter specifies the source

timeslot or port.
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/ISV3/SL1DA /CD1/
ISM6board supports transparent transmission
of the K1/K2 byte.
D10
D11
D12
E1
E2
F1
K1
K2
X1
X2
X3
X4
Sink Timeslot/
Porta
Issue 01 (2016-04-30)
This parameter specifies the sink timeslot

or port.

1188

Configuration Guide
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
E1
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/ISV3/SL1DA /CD1/
ISM6board supports transparent transmission
of the K1/K2 byte.
E2
F1
K1
K2
X1
X2
X3
X4
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functions
the same regardless of the source port or sink port.
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 01 (2016-04-30)

1189

Configuration Guide
Parameters for the ECC Extended Mode

Parameter
Value Range
Default Value
Description
ECC Extended
Mode
Auto mode
Autosensing mode

value.
Specified mode
NOTE
By default, the adaptive mode is enabled for the
extended ECC on an NE. That is, when the
NMS port on an NE finds that the automatic
extended ECC is enabled on another NE in the
same network segment, the automatic extended
ECC is enabled on this NE. Otherwise, the
extended ECC is not enabled on this NE.
Autosensing 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

ECC Extended Mode is set to
Specified mode.
the NE functions as the client of the
extended ECC. Except for the NE that
functions as the server, all other NEs
that use the extended ECC can function
as the client.
l Opposite IP and Port are respectively
set to the IP address of the server NE
and the specified port number.
Issue 01 (2016-04-30)

1190

Configuration Guide
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
This parameter indicates the ECC routing

mode.
SCC No.
This parameter specifies the physical port

through which the ECC route passes. The
value of this parameter is automatically
assigned the NE.
Issue 01 (2016-04-30)

1191

Configuration Guide
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 or Trace Route from the drop-down menu.
Ping 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.
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
Issue 01 (2016-04-30)
0-255
64
Specifies the number of NEs that test

packets will traverse during the forwarding
process.

1192

Configuration Guide
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
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.
Mask
This parameter indicates the subnet mask

of the destination address of the packets.
Gateway
This parameter indicates the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of
the next hop of the packets.
Protocol
l DIRECT: indicates the route between

the local NE and an adjacent NE.
l STATIC: indicates the route that is
created manually.
l OSPF: indicates the route between the
local NE and a non-adjacent NE.
l OSPF_ASE: indicates the route whose
Destination Address is beyond the
OSPF domain.
l OSPF_NSSA: indicates the route
whose Destination Address is in a not
so stubby area (NSSA).
l A route can be deleted in the case of
STATIC only, but cannot be edited in
the other cases.
l Compared with a dynamic route, a
static route has a higher priority. If any
conflict occurs, the static route is
preferred.
Issue 01 (2016-04-30)

1193

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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.
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.
Issue 01 (2016-04-30)

1194

Configuration Guide
Parameter
Value Range
Default Value
Description
Gateway

the gateway on the subnetwork where the
NE is located, namely, the IP address of
the next hop of the packets.
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.
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

Issue 01 (2016-04-30)

1195

Configuration Guide
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.
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.
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 planning information.
l If multiple OSPF areas are configured
on an NE, this parameter takes its
default value 0.0.0.0.
Issue 01 (2016-04-30)

1196

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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.
its default value.
Issue 01 (2016-04-30)

1197

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
its 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).
its default value.
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.
its default value.
Issue 01 (2016-04-30)

1198

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
its default value.
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
management port or NE cascading port.
its 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).
its default value.
Issue 01 (2016-04-30)

1199

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
Static route
Enabled
Disabled
Disabled
l Specifies whether the static route

automatic flooding function is enabled.
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.
Router ID
Issue 01 (2016-04-30)
The Router IP address is always the NE IP

address.

1200

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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.
Issue 01 (2016-04-30)

1201

Configuration Guide
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.
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.
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas

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 Management from the Function Tree.
2.
Issue 01 (2016-04-30)

1202

Configuration Guide
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.
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.
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding

OSPF Areas
This topic describes the parameters that are used for adding OSPF areas.
Issue 01 (2016-04-30)

1203

Configuration Guide
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

according to the planning information.
l An NE can be configured with a
maximum of four OSPF areas.
IP Address
l Set the IP addresses of the Networks in

an area according to planning
information.
l An area supports a maximum of four
Networks.
Subnet Mask
Set the subnet masks of the Networks in an

area according to planning information. A
subnet mask can contain a maximum of 30
bits.
Authentication
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 01 (2016-04-30)

1204

Configuration Guide
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.
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.
B.1.2.15 Parameter Description: Port OSPF Setting

This section describes the parameters that are used for setting port OSPF parameters.
Navigation Path
1.
In the NE Explorer, select the required NE and choose Communication > IP Protocol
2.
Click the Port OSPF Parameter Settings tab.
Issue 01 (2016-04-30)

1205

Configuration Guide
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 DCCs support

Type10 LSA.
B.1.2.16 Parameter Description: Static Route Entries in a Kernel Route

Table_Creation
This topic describes parameters for creating static route entries in a kernel route table.
Navigation Path
1.
In the NE Explorer, select the desired NE from the Object Tree. Choose
Communication > Static Route Entries in the Kernel Route Table from the Function
Tree.
2.
Click Create.
Parameters
Parameter
Value Range
Default Value
Description
Destination NE
Name
This parameter specifies the Name of the

destination NE.
Destination NE ID
This parameter specifies the ID of the

destination NE.
Protocol Type
Only IP protocols are supported.
Next Hop Address

the destination NE.
Routing
Distance(hop)
This parameter specifies the number of

hops between the source NE and the
destination NE.
B.1.2.17 Parameter Description: DCN Management_Bandwidth Management

This topic describes the parameters that are used for bandwidth management of the inband
DCN.
Issue 01 (2016-04-30)

1206

Configuration Guide
Navigation Path
1.
DCN Management from the Function Tree.
2.
Click the Bandwidth Management tab.
Parameters for Bandwidth Management

Parameter
Value Range
Default Value
Description
Ethernet Board
VLAN ID
2 to 4094
4094
Specifies the VLAN ID used by inband

DCN channels.
l The equipment on the traditional DCN
can be connected to the NMS through
the SCC board, but an OptiX RTN 900
can also be connected to the NMS
through an Ethernet port. If an Ethernet
port is used to carry the network
management information, the OptiX
RTN 900 differentiates the network
management information and Ethernet
service information according to the
VLAN ID.
l If the default VLAN ID of the inband
DCN conflicts with the VLAN ID in
the service, the Ethernet Board VLAN
ID of the inband DCN can be changed
manually.
NOTE
This parameter is an NE-level parameter and its
priority is lower than that of the VLAN ID
configured for a specific port.
Bandwidth(kbit/s)
64 to 5000
512
Bandwidth(kbit/s) specifies the

bandwidth for inband DCN messaging on
the Ethernet link.
NOTE
OptiX RTN 950 NEs (using CSH/CST boards)
support an inband DCN bandwidth of 64 to
1000 kbit/s.
E1 Port
Bandwidth(kbit/s)
For OptiX RTN 900 products, this

parameter specifies the inband DCN
bandwidth for a Smart E1 port. This
parameter also takes effect to E1s in an
STM-1.
Tunnel
Bandwidth(kbit/s)
OptiX RTN 900 does not support this

parameter.
Issue 01 (2016-04-30)

1207

Configuration Guide
Parameter
Value Range
Default Value
Description
IF Port
Bandwidth(kbit/s)
64 to 5000
512
IF Port Bandwidth(kbit/s) specifies the

bandwidth for inband DCN messaging on
the radio link.
NOTE
OptiX RTN 950 NEs (using CSH/CST boards)
support an inband DCN bandwidth of 64 to
1000 kbit/s.
NMS Port VLAN

ID
2 to 4094
NMS Port VLAN ID indicates the VLAN

ID of Huawei NMS and is used to
distinguish Huawei DCN packets from
third-party DCN packets on NMS ports.
The OptiX RTN 950 using CSH/CST
boards, OptiX RTN 980, and OptiX RTN
980L do not support this parameter.
The OptiX RTN 950 using CSH/CST
boards and OptiX RTN 980 using CSHN
boards do not support this parameter.
B.1.2.18 Parameter Description: DCN Management_Port Setting

This topic describes the parameters that are used for setting ports of the inband DCN.
Navigation Path
1.
DCN Management from the Function Tree.
2.
Click the Port Settings tab.
Parameters for Setting Ports

Parameter
Value Range
Default Value
Description
Port Name
This parameter indicates the port name.
Enabled Status
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.
Issue 01 (2016-04-30)

1208

Configuration Guide
Parameter
Value Range
Default Value
Description
Protocol Type
IP
IP
l Specifies the DCN protocol used by the

inband DCN.
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 This parameter is available only when

Protocol Type is set to IP.
parameter specifies the interface IP
address of the non-backbone area port
on the ABR.
NE, this parameter specifies the IP
address for a port that does not belong
to the default process.
Subnet Mask

Protocol Type is set to IP.
parameter specifies the subnet mask of
the non-backbone area port on the
ABR.
NE, this parameter specifies the subnet
mask for a port that does not belong to
the default process.
ATN
Compatibility
Mode
Enabled
VLAN
0 to 4094
Issue 01 (2016-04-30)
Disabled
This parameter enables or disables the

ATN compatibility mode for an NE. When
this parameter is set to Enabled, RTN
equipment can auto-negotiate its DCN
mode to the ATN mode or the transmission
equipment mode, based on the format of
inband DCN packets received from the
opposite end.
This parameter takes precedence over the

configured NE-level VLAN ID. The NElevel VLAN ID will take effect over
inband DCN ports with no VLAN ID
specified.
Disabled

1209

Configuration Guide
Parameter
Value Range
Default Value
Description
OSPF Subnet
1 to 4
This parameter indicates the OSPF process

to which a port belongs. When OSPF
multi-process is enabled on an NE, this
parameter needs to be planned and
specified.
OSPF Enabled
Status
Enabled
Enabled
This parameter enables or disables OSPF

for a port.
Disabled
B.1.2.19 Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Navigation Path
l
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
information from the
NMS.
IP Address
Issue 01 (2016-04-30)
0.0.0.0

Specifies the IP address of the

port. The port IP address
must be in a network segment
different from the NE IP
address.
1210

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Subnet Mask
0.0.0.0
Specifies the submask of the

port.
OSPF Enabled Status
Disabled
Disabled
Enabled
B.1.2.20 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.
Packet Priority
CS6
CS6 (Packet Type

is VLAN)
Specifies the VLAN priorities of inband

DCN packets or the PHBs corresponding
to the DSCP values of the inband DCN
packets.
EF
BE (Packet Type is
DSCP)
AF4
AF3
AF2
AF1
BE
B.1.2.21 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.
Issue 01 (2016-04-30)

1211

Configuration Guide

Parameter
Value Range
Default Value
Description
Configuration
Status
Auto
Auto
When an OptiX RTN 900 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 NE level. That is, the RSTP protocol is
automatically enabled/disabled depending
on the enable/disable status of the L2 DCN
function over IF ports.
Real Status
Disabled
l Real Status is queried to be Disabled

in the following scenarios:
Disabled
Enabled
Configuration Status is set to

Disabled.
When Configuration Status is set
to Auto, the L2 DCN function is
disabled for all IF ports on the NE.
l When Configuration 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.
B.1.2.22 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
Control from the Function Tree.
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.
Issue 01 (2016-04-30)
Deselected

1212

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
This parameter displays the working

modes of the NMS port and the NE
cascading port on the system control,
switching, and timing board.
10M Half_Duplex
10M Full_Duplex
100M Half_Duplex
100M Full_Duplex
Actual Work
Mode
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

rate of the serial port at the opposite
end, and the rates at both ends must be
the same.
9600
Parameters for OAM Access Control

Parameter
Value Range
Default Value
Description
Enable OAM
Access
Selected
Selected
After Enable OAM Access is selected, the

NE can access the NMS or command lines
through the mini USB port.
Issue 01 (2016-04-30)
Deselected

1213

Configuration Guide
Parameter
Value Range
Default Value
Description
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
Selected
If Access NM is selected, the serial

interface can be used to access the NMS.
Deselected
Deselected
B.1.2.23 Parameter Description: SNMP Communication

This topic describes parameters related to Simple Network Management Protocol (SNMP)
communication.
Navigation Path
1.
In the NE Explorer, select the desired NE from the Object Tree. Choose
Communication > SNMP Communication Parameters from the Function Tree.
Parameters
Parameter
Value Range
Default Value
Description
Community
Complexity Verify
Enabled
Enabled
Set whether to verify the complexity of a

community name.
Disabled
If this parameter is set to Enabled, the

community name must meet the following
rules:
l The community name is a character
string consisting of at least six
characters.
l The community name is a combination
of at least two types of the following
characters:
Lowercase letters: a to z
Uppercase letters: A to Z
Digits: 0 to 9
Special characters: ` ~ ! @ # $ % ^
&*()-_=+\|[{}];:'",<.
> / ? or space
Issue 01 (2016-04-30)

1214

Configuration Guide
Parameter
Value Range
Default Value
Description
NMS IP Address
0.0.0.0
Set NMS IP Address to the IP address of

the SNMP server that uses these
communications parameters. If there are
no restrictions on the IP address of the
SNMP server that accesses the NE, set this
parameter to 0.0.0.0. However, setting the
NMS IP address to 0.0.0.0 causes certain
security risks. Therefore, make sure that
you know the security risks when setting
the NMS IP address to 0.0.0.0.
If the NMS IP Address is set to 0.0.0.0,
the NE does not support the Trap function.
Read/Write
Permissions
Read Only
Read Only
Verify Read/Write Permissions of the

SNMP server based on the network plan.
Read/Write Permissions must take the
same values as the right parameters set on
the SNMP server.
Report SDH
Performance Trap
Set Report SDH Performance Trap to

Report if an SNMP server is required to
automatically report trap packets when the
SDH performance crosses the threshold,
the data performance crosses the threshold,
or an alarm is generated on the NE.
Report IP
Performance Trap
Set Report IP Performance Trap to

Report if an SNMP server is required to
automatically report trap packets when the
SDH performance crosses the threshold,
the data performance crosses the threshold,
or an alarm is generated on the NE.
Report Alarm
Trap
Set Report Alarm Trap to Report if an

SNMP server is required to automatically
report trap packets when the SDH
performance crosses the threshold, the data
performance crosses the threshold, or an
alarm is generated on the NE.
Trap Port
It is recommended that Port take the

default value.
Read Community
Name
Verify Read Community Name of the

Read Community Name must take the
the SNMP server.
Issue 01 (2016-04-30)
Read/Write

1215

Configuration Guide
Parameter
Value Range
Default Value
Description
Write Community
Name
Verify Write Community Name of the

Write Community Name must take the
the SNMP server.
Report Trap
Version
SNMPV1
SNMPV3
Set the Report Traps Version parameter

based on the SNMP protocol version
running on the SNMP server.
SNMPV2C
SNMPV3
Report Trap
Community Name
Set Report Trap Community Name

Report Trap User

Name
Set Report Trap User Name according to

the network plan.
B.1.2.24 Parameter Description: LLDP

This section describes the LLDP parameters.
Navigation Path
Select the desired NE from the object tree in the NE Explorer and choose Configuration >
Packet Parameter Description

Parameter
Value Range
Default Value
Description
Packet
Transmission
Interval(s)
1 to 3600
30
l Set the transmission interval for LLDP

packets.
TTL Multiplier
4 to 100
l It is recommended that you retain the

default value for this parameter.
4
l Set the TTL multiplier.

l If no information is received from a
neighbor in the TTL multiplier time,
delete all information about the neighbor.
Re-initialization
Delay(s)
1 to 10
l Set the re-initialization delay time, that is

the time before a port can change from
disabled to other status.
Issue 01 (2016-04-30)

1216

Configuration Guide
Parameter
Value Range
Default Value
Description
Packets
Transmitted in
Fast Mode
1 to 8
l Set the number of packets that are

continuously transmitted in Fast mode.
Port Parameter Description

Parameter
Value Range
Default Value
Description
Port
Displays port information.
Mode
Disable
Disable
l Generally, set Mode to

Transmit&Receive for a port for which
the LLDP has been enabled.
Transmit
Receive
l If unidirectional Ethernet connection is set

up between a port for which the LLDP
has been enabled and its neighbor
equipment, set Mode to Transmit or
Receive based on the service direction.
Transmit&Receive
l Set Mode to Disable for a port for which

the LLDP is disabled.
VLAN
1 to 4094
Set VLAN IDs and priorities based on the

network plan.
VLAN Priority
0 to 7
Multicast Mode
Nearest bridge
Nearest bridge
This parameter can only be set to Nearest

bridge.
Neighbor No.
Displays the number of a neighbor.
Neighbor Holding
Time(s)
Displays the latest update time of a neighbor,

that is the latest time a device receives
information from its neighbor.
Neighbor
Remaining
Time(s)
Displays the remaining survival time of a

neighbor.
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: RADIUS Configuration_Creation

This topic describes the parameters that are related to RADIUS configuration.
Issue 01 (2016-04-30)

1217

Configuration Guide
Navigation Path
1.
In the NE Explorer, select the desired NE from the Object Tree and choose Security >
NE RADIUS Configuration from the Function Tree.
2.
Click New.
Parameters
Parameter
Value Range
Default Value
Description
Function
Server ID
Server Type
Specifies the desired RADIUS function, the

authentication server ID, and the server type.
l Function, Server ID, and Server Type
are associated with the servers that are
configured in A.4.5.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 NE supports one active server and
two standby servers. 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.
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.
Issue 01 (2016-04-30)

1218

Configuration Guide
B.1.3.2 Parameter Description: RADIUS Configuration_RADIUS Server

This topic describes the parameters that are related to RADIUS server configuration.
Navigation Path
1.
In the NE Explorer, select the desired NE from the Object Tree and choose Security >
NE RADIUS Configuration from the Function Tree.
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
Proxy Server
RADIUS 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.
authentication in the proxy NAS mode,
set Server Type to Proxy Server.
Issue 01 (2016-04-30)

1219

Configuration Guide
Parameter
Value Range
Default Value
Description
Server ID
IP Address
IP Address
Specifies the address of the server that is

used for NE RADIUS authentication.
NE ID
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.
B.1.3.3 Parameter Description: Enabling/Disabling the RADIUS Function

This topic describes the parameters that are required for enabling/disabling the RADIUS
function.
Navigation Path
In the NE Explorer, select the desired NE from the Object Tree and choose Security > NE
Parameters
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
Issue 01 (2016-04-30)

1220

Configuration Guide
Parameter
Value Range
Default Value
Description
Proxy Server
Open
Close
Specifies whether an NE has the ability to be

a proxy server.
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.
authentication in the proxy NAS mode,
set Proxy Server to Close.
B.2 Radio Link Parameters

This topic describes the parameters that are related to radio links.
B.2.1 Parameter Description: N+1 Protection_Create

This topic describes the parameters that are used for creating an IF N+1 protection group.
NOTE
OptiX RTN 905 does not support the creation of an IF N+1 protection group.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
2.
Click Create.

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.
Issue 01 (2016-04-30)

1221

Configuration Guide
Parameter
Value Range
Default Value
Description
SD Switching
Enabled
Enabled
l This parameter specifies whether the

signal degradation switching function
of N+1 protection is enabled.
Disabled
l When this parameter is set to Enabled,

the signal degradation condition is
considered as a trigger condition of
l It is recommended that you set this
parameter to Enabled.
Protect Group
Type
Enhanced N+1
Standard N+1
Standard N+1
l Only OptiX RTN 980L supports this

parameter. Enhanced N+1 protection
can be configured for only shorthaul
microwave links or longhaul
microwave links on ISV3 boards
running in IS3 mode.
l Only OptiX RTN 980L and OptiX 980
using CSHNA boards support
enhanced N+1 protection.
l Standard N+1 protection is
implemented based on a load sharing
link aggregation group (LAG). The
number of TDM services carried by
each member link in a standard N+1
protection group must be the same.
l N+1 protection in enhanced mode is
implemented based on enhanced
physical link aggregation (EPLA). The
each member link in an enhanced N+1
protection group can be flexibly
configured.
Slot Mapping Relation Parameters

Parameter
Value Range
Default
Value
Description
Select Mapping Direction
Work Unit
Work
Unit
This parameter
specifies the mapping
direction of N+1
protection.
Protection Unit
Issue 01 (2016-04-30)

1222

Configuration Guide
Parameter
Value Range
Default
Value
Description
Available Boards
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.
B.2.2 Parameter Description: N+1 Protection

This topic describes the parameters that are related to IF N+1 protection.
NOTE
OptiX RTN 905 does not support the configuration of IF N+1 protection.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1
Protection Group Parameters

Parameter
Value Range
Default Value
Description
Protection Group
ID
This parameter indicates the ID of the

protection group.
Issue 01 (2016-04-30)

1223

Configuration Guide
Parameter
Value Range
Default Value
Description
Protect Group
Type
Enhanced N+1
Standard N+1
l Only OptiX RTN 980L supports this

parameter. Enhanced N+1 protection
can be configured for only shorthaul
microwave links or longhaul
microwave links on ISV3 boards
running in IS3 mode.
Standard N+1
l Only OptiX RTN 980L and OptiX 980

using CSHNA boards support
enhanced N+1 protection.
l Standard N+1 protection is
implemented based on a load sharing
link aggregation group (LAG). The
each member link in a standard N+1
protection group must be the same.
l N+1 protection in enhanced mode is
implemented based on enhanced
physical link aggregation (EPLA). The
each member link in an enhanced N+1
protection group can be flexibly
configured.
WTR Time(s)
300 to 720
l This parameter indicates or specifies

the WTR time.
reaches the set WTR time, a revertive
switching occurs.
SD Switching
Enabled
Disabled

whether the SD switching function of
N+1 protection is enabled.
the SD condition is considered as a
trigger condition of protection
switching.
Protocol Status
Issue 01 (2016-04-30)
This parameter indicates the status of the

switching control protocol.

1224

Configuration Guide
Slot Mapping Settings Parameters

Parameter
Value Range
Default Value
Description
Unit Type

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.
B.2.3 Parameter Description: IF 1+1 Protection_Create

This topic describes the parameters for creating an IF 1+1 protection group.
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
2.
Click Create.
Issue 01 (2016-04-30)

1225

Configuration Guide
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.
Issue 01 (2016-04-30)

1226

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive Mode
Revertive Mode

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
Non-Revertive, the NE that is in the
switching state keeps the current
state unchanged unless another
switching occurs even though the
former working channel is restored
to normal.
WTR Time(s)
300 to 720
600
l This parameter specifies the wait-torestore (WTR) time.

working channel is restored to
normal reaches the 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 01 (2016-04-30)

1227

Configuration Guide
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, it is recommended that
you set Enable Reverse Switching
to Enabled.
Working/
Protection Unit
Type
Work Unit
Work Unit
This parameter specifies the working

board of the protection group.
Protection Unit
This parameter specifies the protection

board of the protection group.
IF Port
This parameter specifies the working or

protection IF port.
Protection Unit
For RTN 905 1E:

Set Working/Protection Unit Type to
Work Unit for the main RTN 905 1E
and to Protection Unit for the standby
RTN 905 1E.
NOTE
Only the OptiX RTN 905 1E supports this
parameter.
Issue 01 (2016-04-30)

1228

Configuration Guide
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 alarms are
reported.
l It is recommended that you set
Alarm Report Mode to Only
protection group alarms. In this
case, protection group alarms are
reported to indicate radio link faults.
NOTE
The faulty board reports related fault alarms
regardless of parameter settings.
Anti-jitter Time(s)
0 to 600
300
l When Anti-jitter Time(s) is not set

to 0, a protection group does not
report an alarm immediately after it
is degraded, but reports the alarm
after the specified anti-jitter time
expires.
l It is recommended that Anti-jitter
Time(s) take its default value.
NOTE
Anti-jitter Time(s) is valid only for alarms
reported when a protection group degrades.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
B.2.4 Parameter Description: IF 1+1 Protection

This topic describes the parameters that are related to IF 1+1 protection.
Navigation Path
1.
Issue 01 (2016-04-30)
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
1229

Configuration Guide

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 01 (2016-04-30)

1230

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive Mode

the 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
switching state keeps the current state
unchanged unless another switching
occurs even though the former working
channel is restored to normal.
parameter to Revertive Mode.
WTR Time(s)
300 to 720

the 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 You can set WTR Time(s) only when
Revertive Mode is set to Revertive
Mode.
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.
Working Mode is set to HSB or SD.
Issue 01 (2016-04-30)

1231

Configuration Guide
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.
Device Active Port
This parameter indicates the current

working board on the equipment side.
Channel Active
Port
This parameter indicates the current

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 01 (2016-04-30)

1232

Configuration Guide
Parameter
Value Range
Default Value
Description
Alarm
Suppression
Deselected (no
suppression)
Deselected (no
suppression)
l This parameter specifies whether to

suppress the MW_BER_SD,
MW_BER_EXC, MW_RDI,
RADIO_RSL_LOW,
MAC_EXT_EXC, and
MAC_FCS_EXC alarms.
Selected
(suppression)

Alarm Report Mode is set to Only
protection group alarms.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s), Anti-jitter Time (s), and
Slot Mapping Relation Parameters

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
This parameter indicates the status of the

link signal.
B.2.5 Parameter Description: Link Configuration_Creating a PLA/

EPLA/EPLA+/Super EPLA Group
This topic describes the parameters for creating a physical link aggregation (PLA)/enhanced
PLA (EPLA)/enhanced PLA Plus(EPLA+)/Super EPLA group.
NOTE
l Only OptiX RTN 950 using CSHU/CSHUA boards, OptiX RTN 910A, and OptiX RTN 950 support
EPLA+.
l OptiX RTN 910A, OptiX RTN 905, OptiX RTN 950A, OptiX RTN 950 using CSHU/CSHUA boards,
and OptiX RTN 980 using CSHNA boards support EPLA.
Issue 01 (2016-04-30)

1233

Configuration Guide
Navigation Path
1.
In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration
> Physical Link Aggregation from the Function Tree.
2.
Click New.
Parameters for Creating a PLA/EPLA Group (for OptiX RTN 905 1E/2E)
Parameter
Value Range
Default Value
Description
Cascading Status
Cascaded
Cascade
This parameter specifies the cascading

status.
Not Cascaded
PLA ID
This parameter displays the ID of a PLA

group.
Bandwidth(M)
This parameter displays the Bandwidth of

a PLA group.
Protection Type
No NE-level
protection
This parameter is not supported.
NE Role
Master NE
Master NE
This parameter is valid only when

Cascading Status is set to Cascaded, and
specifies whether an NE is the master or
slave NE in a PLA group.
PLA
This parameter specifies the type of a

physical link aggregation group.
Slave NE
PLA Type
PLA
EPLA
Main Board
This parameter specifies the main IF board

in a physical link aggregation group.
Main Port
This parameter specifies the main port in a

Available Cascade
Ports

lists all available cascade ports.
Selected Cascade
Ports

displays selected cascade ports.
Available Slave
Ports
This parameter lists all available slave

ports.
Selected Slave
Ports
This parameter displays selected slave

ports.
Issue 01 (2016-04-30)

1234

Configuration Guide
Parameters for Creating a PLA/EPLA Group (for OptiX RTN 980L/OptiX RTN
980)
Parameter
Value Range
Default Value
Description
Cascading Status
Not Cascaded
Not Cascaded
This parameter specifies the cascading

status.
PLA ID

group.
Bandwidth(M)

a PLA group.
PLA Type
PLA
PLA

EPLA
Main Board

Main Port

Available Slave
Ports

ports.
Selected Slave
Ports

ports.
Parameters for Creating a PLA/EPLA/EPLA+ Group (for OptiX RTN 910A)

Parameter
Value Range
Default Value
Description
PLA ID

group.
PLA Type
PLA
PLA

EPLA
EPLA+
Main Board

Main Port

Available Slave
Ports

ports.
Selected Slave
Ports

ports.
Issue 01 (2016-04-30)

1235

Configuration Guide
Parameters for Creating a PLA/EPLA/EPLA+/Super EPLA Group (for OptiX RTN

950/OptiX RTN 950A)
Parameter
Value Range
Default Value
Description
PLA ID

group.
PLA Type
PLA
PLA

Mode A
This parameter can be specified only when

PLA Type is S-EPLA.
EPLA
EPLA+
S-EPLA
Scheduling Mode
Mode A
Mode B
l When Scheduling Mode is Mode B, In

hitless mode, E-band link bandwidth
changes do not affect the transmission
of high-priority services. In this mode,
high-priority services are transmitted on
common-band links, and low-priority
services are transmitted on E-band
links. However, if high-priority services
exceed the common-band link
bandwidth upon a burst, the excessive
traffic cannot be transmitted by E-band
links and is discarded.
l When Scheduling Mode is Mode A, In
common mode, high-priority and lowpriority services are distributed to
common-band and E-band links based
on their link bandwidths, implementing
inter-frequency AM.
High-Priority
Service Threshold
BE
EF
l When Scheduling Mode is Mode B,

This threshold can be specified for a
Super EPLA group in hitless mode.
Only an SP queue can be configured
with a PHB. Services in this SP queue
and other queues with higher-priorities
are high-priority services.
Auto
l This parameter specifies the priority for

a super EPLA group's member link.
This parameter generally takes the
default value.
AF1
AF2
AF3
AF4
EF
CS6
CS7
Main Port Priority
Auto
Low
High
l This parameter can be specified only

when Scheduling Mode is Mode B.
Issue 01 (2016-04-30)

1236

Configuration Guide
Parameter
Value Range
Default Value
Description
Main Board

Main Port

Available Slave
Ports

ports.
Selected Slave
Ports

ports.
B.2.6 Parameter Description: Link Configuration_PLA/EPLA/

EPLA+/Super EPLA
This topic describes parameters related to physical link aggregation (PLA)/enhanced PLA
(EPLA)/enhanced PLA Plus(EPLA+)/Super EPLA.
NOTE
l Only OptiX RTN 910A, OptiX RTN 950A using CSHU/CSHUA boards and OptiX RTN 950 support
EPLA+.
l OptiX RTN 910A, OptiX RTN 905, OptiX RTN 950A, OptiX RTN 950 using CSHU/CSHUA boards,
and OptiX RTN 980 using CSHNA boards support EPLA.
Navigation Path
1.
Configuration > Physical Link Aggregation from the Function Tree.
PLA/EPLA Parameters (for OptiX RTN 905 1E/2E,RTN 980 and RTN 980L)
Parameter
Value Range
Default Value
Description
Cascading Status
This parameter displays the cascading

status.
PLA ID

group.
PLA Type
This parameter displays the type of a PLA

group.
Protection Type
This parameter is not supported.
NE Role
This parameter displays whether an NE is

the master or slave NE in a PLA group.
Issue 01 (2016-04-30)

1237

Configuration Guide
Parameter
Value Range
Default Value
Description
Master NE
This parameter displays the master NE in a

PLA group.
Cascade Port
This parameter displays a cascade port in a

PLA group.
Local NE Working
Status
This parameter displays the working status

of the local NE.
Minimum Active
Links
This parameter specifies the minimum

number of available links in a PLA group
and helps to trigger Ethernet ring
protection switching (ERPS) switching
even if not all members in the PLA group
fail.
For example, if you set Minimum Active
Links to 2, ERPS switching is triggered
when either PLA member link fails.
Bandwidth(M)

a PLA group.
Extendable
Bandwidth(M)
This parameter displays the Extendable

Bandwidth of a PLA group.
Master NE
This parameter displays the master NE in a

PLA group.
Port
This parameter displays the port in a PLA

group.
NE
This parameter displays NEs that form a

PLA group.
Port Status
This parameter displays the working status

of a port.
Hardware Status
This parameter displays whether the

hardware of the NE in a PLA group is
functional.
Link Status
This parameter displays whether the link in

a PLA group is functional.
Hitless Switching
Enabled
Disabled
Hitless EPLA switching can be enabled for

RTN 980L working as long-haul
microwave.
Disabled
Issue 01 (2016-04-30)

1238

Configuration Guide
PLA/EPLA/EPLA+ Parameters (OptiX RTN 910A)

Parameter
Value Range
Default Value
Description
Cascading Status

status.
PLA ID

group.
PLA Type

group.
Main Board
This parameter displays the main 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 the hardware

status of the main port in a PLA group.
Link Status of
Main Port
This parameter displays the link status of

the main port in a PLA group.
Work Status of
Main Port
This parameter displays the work status of

Minimum Active
Links

fail.
Slave Board
This parameter displays the slave board in

a PLA group.
Slave Port
This parameter displays the slave port in a

PLA group.
Hardware Status
of Slave Port

status of the slave port in a PLA group.
Link Status of
Slave Port

the slave port in a PLA group.
Work Status of
Slave Port

Issue 01 (2016-04-30)

1239

Configuration Guide
PLA/EPLA/EPLA+ Parameters (for OptiX RTN 950/RTN 950A)

Parameter
Value Range
Default Value
Description
Cascading Status

status.
PLA ID

group.
PLA Type

group.
Scheduling Mode
Hitless
Hitless
l When Scheduling Mode is Mode B, In

hitless mode, E-band link bandwidth
changes do not affect the transmission
of high-priority services. In this mode,
high-priority services are transmitted on
common-band links, and low-priority
services are transmitted on E-band
links. However, if high-priority services
exceed the common-band link
bandwidth upon a burst, the excessive
traffic cannot be transmitted by E-band
links and is discarded.
Common
l When Scheduling Mode is Mode A, In

common mode, high-priority and lowpriority services are distributed to
common-band and E-band links based
on their link bandwidths, implementing
inter-frequency AM.
High-Priority
Service Threshold
0-7
l When Scheduling Mode is Mode B,

This threshold can be specified for a
Super EPLA group in hitless mode.
Only an SP queue can be configured
with a PHB. Services in this SP queue
and other queues with higher-priorities
are high-priority services.
Main Port Priority
Auto
Auto
l This parameter specifies the priority for

a super EPLA group's member link.
This parameter generally takes the
default value.
Low
High
l This parameter can be specified only

when Scheduling Mode is Mode B.
Main Board
This parameter displays the main board in

a PLA group.
Main Port
This parameter displays the main port in a

PLA group.
Hardware Status
of Main Port

status of the main port in a PLA group.
Issue 01 (2016-04-30)

1240

Configuration Guide
Parameter
Value Range
Default Value
Description
Link Status of
Main Port

Work Status of
Main Port

Minimum Active
Links

fail.
Slave Board
This parameter displays the slave board in

a PLA group.
Slave Port
This parameter displays the slave port in a

PLA group.
Hardware Status
of Slave Port

status of the slave port in a PLA group.
Link Status of
Slave Port

Work Status of
Slave Port

B.2.7 Parameter Description: Radio Link Management

This topic describes parameters related to radio link management.
Navigation Path
1.
In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration
> Radio Link Configuration from the Function Tree.
Basic Parameters
Parameter
Value Range
Default Value
Description
Protection
1+0
1+0
This parameter specifies the link protection

scheme.
1+1
OptiX RTN 905 1E does not support this

parameter.
Issue 01 (2016-04-30)

1241

Configuration Guide
Parameter
Value Range
Default Value
Description
XPIC
Selected
Deselected
This parameter specifies whether cross

polarization interference cancellation
(XPIC) needs to be enabled on an IF board
that supports XPIC.
l This parameter specifies the radio link

ID.
Deselected
Link ID
1 to 4094
l If the value of Received Link ID is

different from the value of this
parameter, the local end inserts an
alarm indication signal (AIS) to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the
received link ID is different from the
preset link ID.
l This parameter has an invalid random
value when a radio link fails.
Received Link ID
l This parameter displays the received

link ID.
l If the value of this parameter is
different from the value of Link ID, the
local end inserts an AIS to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the
received link ID is different from the
preset link ID.
l This parameter has an invalid random
value when a radio link fails.
IF Parameters
Parameter
Value Range
Default Value
Description
IF Service Type
Hybrid(Native
E1+ETH)
Hybrid(Native
E1+ETH)
This parameter specifies the type of

services carried by an IF board.
NOTE
For details about services that different types of
IF boards support, see the IDU Hardware
Description.
Hybrid(Native
STM-1+ETH)
SDH
Channel Space
Issue 01 (2016-04-30)
This parameter specifies the channel

spacing of a radio link. Set this parameter

1242

Configuration Guide
Parameter
Value Range
Default Value
Description
AM Status
Selected
Deselected
l When this parameter is deselected, the

radio link uses the specified modulation
scheme. In this case, you need to
configure Modulation Mode.
Deselected
l When this parameter is selected, the

radio link uses the corresponding
modulation scheme according to the
channel conditions.
l Only Integrated IP microwave supports
the adaptive modulation (AM) function.
l The AM function is not supported when
IF Channel Bandwidth is 3.5M.
Modulation Mode
l This parameter specifies the modulation

mode that the radio link uses for signal
transmission.
l This parameter is valid only when AM
is deselected.
Guaranteed
Capacity
Modulation
Full Capacity
Modulation

is selected.
l This parameter specifies the lowestorder modulation scheme that the AM
function supports. Set this parameter
Generally, the value of this parameter is
determined by the service transmission
bandwidth that the radio must ensure
and the availability of the radio link
that corresponds to this modulation
scheme.

is selected.
l This parameter specifies the highestorder modulation scheme that the AM
function supports. Set this parameter
determined by the bandwidth of the
services that need to be transmitted
over the radio and the availability of the
radio link that corresponds to this
modulation scheme.
Issue 01 (2016-04-30)

1243

Configuration Guide
Parameter
Value Range
Default Value
Description
Guaranteed E1
Capacity
l When Enable E1 Priority is set to

Disabled, this parameter specifies the
E1 service capacity of an IF port.
Enabled, this parameter specifies the
E1 service capacity in Modulation
Mode of the Guaranteed AM
Capacity.
l This parameter is configurable when IF
Service Type is set to Hybrid(Native
E1+ETH).
STM-1 Capacity
l This parameter specifies the STM-1

service capacity of an IF port.
l This parameter is configurable when IF
STM-1+ETH) or SDH.
Data Service
Bandwidth(Mbit/s
)
This parameter displays the IF bandwidth

occupied by data services on an IF board.
Enable E1 Priority
Disabled
Disabled

E1 priority function needs to be
enabled.
Enabled
l This parameter is configurable when

AM is selected and IF Service Type is
set to Hybrid(Native E1+ETH).
Issue 01 (2016-04-30)

1244

Configuration Guide
RF Parameters
Parameter
Value Range
Default Value
Description
TX Frequency
(MHz)
l This parameter specifies the transmit

frequency of an ODU/RFU, namely, the
channel central frequency.
l The value of this parameter ranges from
the sum of the lower TX frequency
limit supported by an ODU/RFU and a
half of the channel spacing to the
difference between the upper TX
frequency limit supported by an
ODU/RFU and a half of the channel
spacing.
l The difference between the transmit
frequencies of the ODUs/RFUs at both
ends of a radio link is a T/R spacing.
network plan.
Actual RX
Frequency (MHz)
This parameter displays the receive

frequency of an ODU/RFU.
T/R Spacing
(MHz)
l This parameter specifies the spacing

between the transmit and receive
frequencies of an ODU to prevent
interference between them.
l If Station Type of an ODU is TX high,
the transmit frequency is one T/R
spacing higher than the receive power.
If Station Type of an ODU is TX low,
the transmit frequency is one T/R
spacing lower than the receive power.
l If an ODU supports only one T/R
spacing, set this parameter to 0,
indicating that the T/R spacing
supported by the ODU is used.
l A valid T/R spacing value is
determined by an ODU itself. Set T/R
Spacing (MHz) according to the
technical specifications of an ODU.
l Set T/R Spacing (MHz) consistently
for ODUs at both ends of a radio link.
Issue 01 (2016-04-30)

1245

Configuration Guide
Parameter
Value Range
Default Value
Description
ATPC
Selected
Deselected
l This parameter specifies whether

automatic transmit power control
(ATPC) needs to be enabled.
Deselected
l When ATPC is selected, if the RSL is 2

dB or more than 2 dB less than the
value halfway between the upper and
lower ATPC thresholds, the receiver
instructs the transmitter to increase
transmit power so that the RSL does
not deviate more than 2 dB from the
halfway value; if the RSL is 2 dB or
more than 2 dB greater than the value
halfway between the upper and lower
ATPC thresholds, the receiver instructs
the transmitter to decrease transmit
power so that the RSL does not deviate
more than 2 dB from the halfway value.
l Set ATPC consistently at both ends of a
radio link.
l It is recommended that you deselect
ATPC for NEs in areas where fast
fading is severe.
l During the commissioning process,
deselected this parameter to ensure that
the transmit power is not changed.
After commissioning, reset this
parameter.
ATPC Upper
Threshold(dBm)
-45.0
ATPC Lower
Threshold(dBm)
-70.0
TX Power (dBm)
Issue 01 (2016-04-30)
l Set the central value between the ATPC

upper threshold and the ATPC lower
threshold to the expected receive
power.
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.
This parameter displays the transmit power

of an ODU/RFU.

1246

Configuration Guide
Parameter
Value Range
Default Value
Description
Actual TX Power
(dBm)
l This parameter displays the actual

transmit power of an ODU/RFU.
l If ATPC is enabled, the value of this
parameter may be different from the
preset transmit power.
Power to Be
Received (dBm)
This parameter specifies the receive power

of an ODU/RFU.
Actual RX Power
(dBm)
This parameter displays the actual receive

power of an ODU/RFU.
TX Status
This parameter displays the transmit status

of an ODU/RFU.
Equipment Information Parameters

Parameter
Value Range
Default Value
Description
Frequency (GHz)
This parameter displays the operating

frequency band of an ODU/RFU.
Station Type
l This parameter indicates whether an

ODU/RFU is a TX high station or a TX
low station.
l The transmit frequency of a TX high
station is one T/R spacing higher than
the transmit frequency of a TX low
station.
RF Type
This parameter displays the level of the

output power of an ODU/RFU.
Equip Type
This parameter displays the ODU/RFU

type, indicating the ODU/RFU
transmission capability.
Product SN
This parameter displays the manufacturing

serial number and the manufacturer code
of an ODU/RFU.
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.
Issue 01 (2016-04-30)

1247

Configuration Guide
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear
MS from the Function Tree.
2.
Click Create.

Parameter
Value Range
Default Value
Description
Protection Type
1+1 Protection
1+1 Protection

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.
Switching Mode
Single-Ended
Switching
Dual-Ended
Switching
Single-Ended
Switching (1+1
Protection)
Dual-Ended
Switching (1:N
Protection)
l This parameter specifies the 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 01 (2016-04-30)

1248

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Non-Revertive
Non-Revertive (1+1
Protection)
l This parameter specifies the 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
Revertive
l When this parameter is set to NonRevertive, the NE that is in the

occurs even though the former
working channel is restored to normal.
Protection, Revertive Mode can be
set to Revertive only.
WTR Time(s)
300 to 720
600
l This parameter specifies the WTR

time.
reaches the preset WTR time, a
revertive switching occurs.
Revertive Mode is set to Revertive.
l It is recommended that you use the
default value.
SD Switching
Enabled
Enabled
Disabled

whether the switching at the SD alarm
of the linear MSP is enabled.
Enabled, the B2_SD alarm is
considered as a switching condition.
Protocol Type
New Protocol
Restructure
Protocol
New Protocol
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 01 (2016-04-30)

1249

Configuration Guide

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.
l This parameter
specifies the
mapping board
and port in the
mapping
direction.
West Protection Unit
Available Boards
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 Boards
This parameter
indicates the preset
slot mapping
relations, including
the mapping
direction and the
corresponding
mapping mode.
B.3.2 Parameter Description: Linear MSP

This topic describes the parameters that are related to linear MSP groups.
Issue 01 (2016-04-30)

1250

Configuration Guide
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.
Protection Type
This parameter indicates the protection

type of the linear MSP group.
Switching Mode
Single-Ended
Switching

the switching mode of the linear MSP.
Dual-Ended
Switching
l In single-ended mode, the switching

occurs only at one end and the state of
the other end remains unchanged.
Protection, Switching Mode can be
set to Dual-Ended Switching only.
Revertive Mode
Non-Revertive
Revertive

the revertive mode of the linear MSP.
and enables the former working
channel to return to the normal state
some time after the former working
l When this parameter is set to NonRevertive, the NE that is in the
occurs even though the former working
Protection, Revertive Mode can be set
to Revertive only.
Issue 01 (2016-04-30)

1251

Configuration Guide
Parameter
Value Range
Default Value
Description
WTR Time(s)
300 to 720

the WTR time.
default value.
SD Switching
Enabled
Disabled

whether the reverse switching function
is enabled.
the B2_SD alarm is considered as a
switching condition.
Protocol Type
New Protocol
Restructure
Protocol

interconnected NEs run the protocols of
the same type.
the restructure protocol complies with
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.
Issue 01 (2016-04-30)

1252

Configuration Guide
Parameter
Value Range
Default Value
Description
Switching StatusWest

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.
B.3.3 Parameter Description: Packet-based Linear MSP_Creation

This section describes the parameters that are used for creating a packet-based linear MSP
group.
Navigation Path
1.
In the NE Explorer, select an NE from the Object Tree and choose Configuration >
Packet-based linear MS from the Function Tree.
2.
Click Create.

Parameter
Value Range
Default Value
Description
Protection Type
1:N Protection
1:N Protection
Specifies the protection type of a packetbased linear MSP group. Packet-based

linear MSP groups support only 1:1
protection.
Switching Mode
Dual-Ended
Switching
Dual-Ended
Switching
l Specifies the switching mode of the

packet-based linear MSP.
occurs at both ends simultaneously.
Revertive Mode
Revertive
Revertive
l Specifies the revertive mode of the

packet-based linear MSP.
and enables the original working
channel to change to the normal state
some time after the original working
Issue 01 (2016-04-30)

1253

Configuration Guide
Parameter
Value Range
Default Value
Description
WTR Time(s)
300-720
600
l Specifies the WTR time.

l When the time after the original
parameter to the default value.
SD Switching
Enabled
Enabled
Disabled
l Specifies whether an SD alarm of the

packet-based linear MSP can trigger
switching. You can set the parameter
value manually.
a B2_SD alarm is considered as a
Protocol Type
New Protocol
New Protocol
Restructure
Protocol

the restructured protocol complies with
l Ensure that the interconnected NEs run
the protocols of the same type.
SD/SF PRI
Switching Tag
Low priority
Low priority
High priority
l Specifies whether an SD/SF alarm is a

high-priority or low-priority switching
condition. You can set the parameter
value manually.
l When this parameter is set to High
priority, bits 1 to 4 of the K1 byte uses
1101 to indicate a high-priority SF
switching request and 1011 to indicates
a high-priority SD switching request.
l When this parameter is set to Low
priority, bits 1 to 4 of the K1 byte uses
1100 to indicate a low-priority SF
switching request and 1010 to indicates
a low-priority SD switching request.
Switching Mode
Indication
Issue 01 (2016-04-30)
Indication
Indication
Not indication
Specifies whether the switching mode

indication function is enabled for packetbased linear MSP. You can set the
parameter value manually.

1254

Configuration Guide
Slot Mapping Parameters

Parameter
Value Range
Default Value
Description
Select Mapping
Direction
West Working Unit
West Working Unit
Specifies the mapping direction of the

linear MSP. You can set the parameter
value manually.
Available Boards
l Specifies the mapping board and port

in the mapping direction. You can set
the parameter value manually.
West Protection
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 need to
be configured on different boards if
possible.
Mapped Boards
Specifies the preset slot mapping

relationship, including the mapping
direction and the corresponding mapping
mode.
B.3.4 Parameter Description: Packet-based Linear MSP

This section describes the parameters that are related to packet-based linear MSP groups.
Navigation Path
In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packetbased linear MS from the Function Tree.

Parameter
Value Range
Default Value
Description
Protection Group
ID
Specifies the ID of the protection group.
Protection Type
Specifies the protection type of a packetbased linear MSP group.
Switching Mode
Dual-Ended
Switching
l Specifies the switching mode of the

packet-based linear MSP. You can set
Issue 01 (2016-04-30)

1255

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive
l Specifies the revertive mode of the

packet-based linear MSP. You can set
and enables the original working
channel to change to the normal state
some time after the original working
WTR Time(s)
300-720
l Specifies the WTR time. You can set

SD Enable
Enabled
Disabled
l Specifies whether the reverse switching

function is enabled. You can set the
a B2_SD alarm is considered as a
Protocol Type
New Protocol
Restructure
Protocol

interconnected NEs run the protocols of
the same type.
the restructured protocol complies with
Protocol Status
Issue 01 (2016-04-30)
Specifies the protocol status of a packetbased linear MSP.

1256

Configuration Guide
Parameter
Value Range
Default Value
Description
SD/SF PRI
Switching Tag
High priority
Low priority
l Specifies whether an SD/SF alarm is a

high-priority or low-priority switching
condition. You can set the parameter
value manually.
Low priority
l When SD/SF PRI Switching Tag is set

to High priority, bits 1 to 4 of the K1
byte uses 1101 to indicate a highpriority SF switching request and 1011
to indicates a high-priority SD
switching request.
l When SD/SF PRI Switching Tag is set
to Low priority, bits 1 to 4 of the K1
byte uses 1100 to indicate a lowpriority SF switching request and 1010
to indicates a low-priority SD
switching request.
Switching Mode
Indication
Indication
Indication
Specifies whether the switching mode

indication function is enabled for packetbased linear MSP. You can set the
Non-indication
Slot Mapping Parameters

Parameter
Value Range
Default Value
Description
Unit Type
Specifies which of the units, namely, the

west protection unit or the west working
unit, is currently in the protection status.
Unit Name-West
Specifies the west protection unit and the

west working unit of a packet-based linear
MSP.
Switching StatusWest
Specifies the switching status of the line.
Protected Unit
Specifies 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 01 (2016-04-30)

1257

Configuration Guide
B.3.5 Parameter Description: Ring MSP_Creation

This topic describes the parameters that are used for creating ring MSP groups.
Context
NOTE
Only OptiX RTN 980 and OptiX RTN 980L support the configuration of a ring MSP group.
Navigation Path
1.
In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Ring MS from the Function Tree.
2.
Click Create.
A dialog box is displayed, prompting for confirmation.
3.
Click Yes.

Parameter
Value Range
Default Value
Description
Transmission Level
STM-4
STM-4
Specifies the transmission level of

ring MSP services. The parameter
value is always STM-4.
Protection Type
2-fiber
Bidirectional
Multiplex
Section
2-fiber
Bidirectional
Multiplex
Section
Specifies the ring MSP protection

type. The parameter value is always
2-fiber Bidirectional Multiplex
Section.
Local Node ID
0-15
Specifies the node ID that the local

NE uses on the MSP ring. Node IDs
of NEs on the ring must be different
from each other.
West Node ID
0-15
Specifies the node ID of the NE that

is connected to the west line board on
the local NE. The parameter value
must be different from Local Node.
East Node ID
0-15
Specifies the node ID of the NE that

is connected to the east line board on
the local NE. The parameter value
must be different from Local Node.
Issue 01 (2016-04-30)

1258

Configuration Guide
Parameter
Value Range
Default Value
Description
WTR Time(s)
300-720
600
l Specifies the WTR time for the

local NE. After the working
channel recovers, services are
switched back from the protection
channel to the working channel
when the WTR time expires.
l Prevents frequent service
switches. The default value is
recommended.
SD Switching
Enabled
Enabled
Disabled
l Specifies whether the B2_SD

alarm on the local NE functions
as a switching trigger condition.
When the parameter value is
Enabled, the B2_SD alarm on the
local NE functions as a switching
trigger condition.
this parameter to Enabled.
Protocol Type
New Protocol
Restructure
Protocol
New Protocol
l The new MSP protocol is

supported from an early stage,
and is still widely used.
l Compared with the new MSP
protocol, the restructure MSP
protocol is optimized and more
stable, incorporating better
protection measures.
l The new MSP protocol has higher
technology maturity than the
restructure MSP protocol, and
therefore is generally
recommended. The restructure
MSP protocol, however, features
higher standard compliance than
the new MSP protocol. Therefore,
the restructure MSP protocol is
used when the new MSP protocol
fails to support interconnection
between Huawei RTN equipment
and third-party equipment.
l Two interconnected NEs must use
the same MSP protocol type.
Issue 01 (2016-04-30)

1259

Configuration Guide
Parameters for Slot Mapping Settings

Parameter
Value Range
Default Value
Description
Select Mapping
Direction
West Line 1
West Line 1
Specifies the mapping direction of a

member in a ring MSP protection group.
Available Boards
l Specifies the mapping board and port

in the mapping direction.
East Line 1
l It is recommended that you map the

SL4D-1 port to West Line 1 and map
the SL4D-2 port to East Line 1.
Mapped Boards
Displays the configured slot mapping

relationship, including the mapping
direction and the mapping mode.
B.3.6 Parameter Description: Ring MSP

This topic describes the parameters that are related to ring MSP.
Context
NOTE
Only OptiX RTN 980 and OptiX RTN 980L support the configuration of a ring MSP group.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration >

Parameter
Value Range
Default Value
Description
Protection Group
ID
Displays the ID of a ring MSP protection

group.
Level
Displays the transmission level of ring

MSP services. The parameter value is
always STM-4.
Protection Type
Displays the ring MSP protection type.

The parameter value is always 2-fiber
Bidirectional Multiplex Section.
Local Node
Displays the node ID that the local NE

uses on the MSP ring.
West Node
Displays the node ID of the NE that is

connected to the west line board on the
local NE.
Issue 01 (2016-04-30)

1260

Configuration Guide
Parameter
Value Range
Default Value
Description
East Node
Displays the node ID of the NE that is

connected to the east line board on the
local NE.
WTR Time(s)
Displays the wait-to-restore (WTR) time

of the local NE. After the working channel
is restored, revertive switching occurs
when the WTR time expires.
SD Enable
Displays whether SD Enable is Enabled

for the local NE. If SD Enable is Enabled,
the B2_SD alarm is regarded as a
switching trigger condition.
Protocol Type
l Displays the protocol type used by the

local NE.
l The new MSP protocol is supported
from an early stage, and is still widely
used.
l Compared with the new MSP protocol,
the restructure MSP protocol is
optimized and more stable,
incorporating better protection
measures.
Protocol Status
Displays the current protocol status of the

local NE.
Protection Subnet
Displays the current protection subnet.
Parameters for Slot Mapping Relationships

Parameter
Value Range
Default Value
Description
Mapping Direction
Displays the direction of an MSP ring.
Slot Mapping
Displays the slot mapping relationship in a

ring MSP protection group.
Switching Status
Displays the current switching status of the

local NE.
B.4 TDM Service Parameters

This section describes the parameters related to TDM services.
Issue 01 (2016-04-30)

1261

Configuration Guide
B.4.1 Parameter Description: SDH/PDH 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/PDH Service Management 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
Bidirectional
Unidirectional

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.
l In normal cases, it is recommended that
you set this parameter to Bidirectional.
Source Slot
Issue 01 (2016-04-30)
This parameter specifies the slot of the

service source.

1262

Configuration Guide
Parameter
Value Range
Default Value
Description
Source VC4
VC41
VC41

the VC-4 channel where the service
source is located.
VC42
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.
Sink Slot

service sink.
Sink VC4
VC41
VC41

sink is located.
VC42

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.
Issue 01 (2016-04-30)

1263

Configuration Guide
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,
ensured only in full-capacity
modulation scheme
l If the service priority is not specified
during service creation, E1 Priority is
None. In this case, the E1 priority of a
service needs to be changed after the
service is created.
Activate
Immediately
Yes
Yes
No

immediately activate the configured
service.
l To immediately deliver the configured
SDH service to the NE, set this
parameter to Yes.

Configuration_SNCP Service Creation
This topic describes the parameters that are used for creating SNCP services.
Navigation Path
1.
SDH/PDH Service Management from the Function Tree.
2.
Click Options to change the VC-12 timeslot numbering policy used by the crossconnection.
3.
Click Create SNCP Service.

Parameter
Value Range
Default Value
Description
Service Type
SNCP
SNCP
This parameter indicates that the type of

the service to be created is SNCP.
Issue 01 (2016-04-30)

1264

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
l If the service is an E1 service or a data
service that is bound with VC-12
channels, set this parameter to VC12.
l If the service is a data service that is
bound with VC-3 channels, set this
parameter to VC3.
l If all the services on a VC-4 channel
pass through the NE, set this parameter
to VC4.
Issue 01 (2016-04-30)

1265

Configuration Guide
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 holdoff 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 01 (2016-04-30)

1266

Configuration Guide
Parameter
Value Range
Default Value
Description
WTR Time(s)
300 to 720
600
l This parameter specifies the WTR time.

default value.
Source Slot

service source.
Source VC4
VC41
VC41

source is located.
VC42

tributary board.
Source Timeslot
Range(e.g.1,3-6)

Sink Slot

service sink.
Sink VC4
VC41
VC41

sink is located.
VC42

tributary board.
Issue 01 (2016-04-30)

1267

Configuration Guide
Parameter
Value Range
Default Value
Description
Sink Timeslot
Range(e.g.1,3-6)

Configure SNCP
Tangent Ring
Selected
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.

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.
SDH/PDH Service Configuration from the Function Tree.
2.
Optional: If a bidirectional SDH service is created, select this service in CrossConnection. Right-click the selected service and choose Expand to Unidirectional
3.
Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.
Issue 01 (2016-04-30)

1268

Configuration Guide

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
This parameter indicates the level of the

SNCP service.
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)
l If only the SNCP scheme is available, it
is recommended that you set the holdoff time to 0.
Issue 01 (2016-04-30)

1269

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Non-Revertive
Non-Revertive

switch the service to the original
working channel after the fault is
rectified. If this parameter is set to
"Revertive", the service is switched
Revertive
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
WTR Time(s)
300 to 720
600
l This parameter specifies the WTR time.

default value.
Source Slot

service source.
Source VC4

source is located.
tributary board.
Source Timeslot
Range(e.g.1,3-6)

Sink Slot
Issue 01 (2016-04-30)

service sink.

1270

Configuration Guide
Parameter
Value Range
Default Value
Description
Sink VC4

sink is located.
tributary board.
Sink Timeslot
Range(e.g.1,3-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

SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
B.4.4 Parameter Description: SDH/PDH Service Configuration

This topic describes the parameters that are used for configuring SDH services (namely,
configuring cross-connections).
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Issue 01 (2016-04-30)

1271

Configuration Guide
Cross-Connection Parameters
Parameter
Value Range
Def
ault
Val
ue
Description
Level
This parameter indicates the level of the service.
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
This parameter indicates the slot of the source sink.
Sink Timeslot/
Path
This parameter indicates the timeslot or timeslot range of the

service sink.
Activation
Status
Yes
This parameter indicates whether to activate the service.
Bound Group
Number
OptiX RTN 900 does not support this parameter.
Lockout Status
Trail Name
Schedule No.
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.
No
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 full-capacity modulation scheme
l If the service priority is not specified during service
creation, E1 Priority is None. In this case, the E1 priority
of a service needs to be changed after the service is
created.
Parameters for Automatically Created Cross-Connections

Parameter
Value Range
Default Value
Description
Level

service.
Source Slot
This parameter indicates the slot of the

service source.
Issue 01 (2016-04-30)

1272

Configuration Guide
Parameter
Value Range
Default Value
Description
Source Timeslot/
Path
This parameter indicates the timeslot or

timeslot range of the service source.
Sink Slot
This parameter indicates the slot of the

source sink.
Sink Timeslot/
Path
This parameter indicates the timeslot or

timeslot range of the service sink.
Lockout Status

parameter.
Trail Name

parameter.
Schedule No.

parameter.
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,

ensured in any modulation scheme.
l If E1 Priority is set to Low,
ensured only in full-capacity
modulation scheme
l If the service priority is not specified
during service creation, E1 Priority is
None. In this case, the E1 priority of a
service needs to be changed after the
service is created.
B.4.5 Parameter Description: SNCP Service Control

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
Issue 01 (2016-04-30)

1273

Configuration Guide

Parameter
Value Range
Default
Value
Description
Service Type

service protection type of the
protection group.
Protection Group ID
Displays the ID of the protection

group.
Source

timeslots where the working
service source and protection
service source of the protection
group are located.
Sink

timeslots where the working
service sink and protection service
sink of the protection group are
located.
Level
Displays the service level.
Current Status

current switching mode and
switching status of the services of
Revertive Mode
Revertive
l This parameter indicates or

specifies the 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.
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.
this parameter to Revertive.
Issue 01 (2016-04-30)

1274

Configuration Guide
Parameter
Value Range
Default
Value
Description
WTR Time(s)
300 to 720

specifies the WTR time.
l When the time after the
original 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.
l It is recommended that you
use the default value.
Issue 01 (2016-04-30)

1275

Configuration Guide
Parameter
Value Range
Default
Value
Description
Hold-off Time(100ms)
0 to 100

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, Holdoff 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)
l If only the SNCP scheme is
available, it is recommended
that you set the hold-off time
to 0.
Issue 01 (2016-04-30)

1276

Configuration Guide
Parameter
Value Range
Default
Value
Description
Switching Condition
Null

specifies the 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.
SD Initiation Condition to
the same condition for
Working Service and
Protection Service.
l The protection switching
conditions in SD Initiation
Condition are optional values
not included in the default
values, and they are set
according to the planning
information.
Trail Status
This parameter indicates the status

of the working service and
protection service of the
protection group.
Service Grouping
The NE does not support this

parameter.
Group Type
The NE does not support this

parameter.
Active Channel
This parameter indicates whether

the working service or protection
service is currently received by
Trail Name
Displays the trail name.
B.4.6 Parameter Description: TU_AIS Insertion

This section describes the parameters for TU_AIS insertion.
Issue 01 (2016-04-30)

1277

Configuration Guide
NOTE
when Integrated IP microwave links construct an E1 SNCP ring together with SDH microwave links provided
by ISV3 boards, or SDH optical lines, an E1_AIS needs to be converted to a TU_AIS on the IF boards that
construct the Integrated IP microwave links.
Navigation Path
In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered
Alarm Insertion from the Function Tree.

Table B-1 Parameters on the main interface
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 If Insert E1_AIS to TU_AIS is set to

Enable, a TU_AIS alarm is inserted to
an E1 channel upon detection of an
E1_AIS alarm in the channel.
Disable
Auto

Disable, a TU_AIS alarm is not
inserted to an E1 channel upon
detection of an E1_AIS alarm in the
channel.
Auto, a TU_AIS alarm is automatically
inserted to an E1 channel upon
detection of an E1_AIS alarm in the
channel based on scenarios.
you set Insert E1_AIS to TU_AIS to
Auto. During troubleshooting, it is
recommended that you set Insert
E1_AIS to TU_AIS to Disable or
Enable.
B.5 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces.
Issue 01 (2016-04-30)

1278

Configuration Guide
B.5.1 Parameter Description: Working Modes of Ports

This topic describes the parameters that are related to the working modes of ports.
NOTE
l For OptiX RTN 905 housing an MN1 board, you can set Service Mode for ports on the logical board
l For OptiX RTN 950A housing an MN1 board, you can set Service Mode for ports on the logical board
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.
Service Mode
CES
PDH
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.
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.
Issue 01 (2016-04-30)
In the NE Explorer, select the NE from the Object Tree and choose Configuration >
1279

Configuration Guide
2.

NOTE
Before changing Port Mode for a port enabled with inband DCN, disable inband DCN.
Parameter
Value Range
Default Value
Description
Port
Displays the ID of a
service port.
Name
Specifies or displays the

customized port name.
Port Mode
Layer 1
Layer 3
l Specifies the working

mode of a PDH port.
Layer 2
l When this parameter

is set to Layer 1, the
port can transmit
TDM signals. A port
can transmit CES and
serial services only if
Layer 1.
Layer 3

is set to Layer 2, the
port can transmit
ATM signals.
l When Port Mode is
Layer 3 for a port, the
port can carry MLPPP
signals.
Encapsulation Type
l Displays
Encapsulation Type
of a PDH port.
l When Port Mode is
Layer 1,
Encapsulation Type
takes its default value
Null.
l When Port Mode is
Layer 2,
Encapsulation Type
ATM.
l When Port Mode is
Layer 3,
Encapsulation Type
NULL.
Issue 01 (2016-04-30)

1280

Configuration Guide
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.
In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > Interface Management > PDH Interface from the Function Tree.
2.

NOTE
Before changing Frame Format and Frame Mode for a port enabled with inband DCN, disable inband
DCN.
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 01 (2016-04-30)

Displays the line

encoding format. The
parameter value is always
HDB3.
1281

Configuration Guide
Parameter
Value Range
Default Value
Description
Re-timing Mode
Master Mode
Master Mode
l Master Mode: The

system clock is used
as the output clock of
services. The master
mode is the re-timing
mode.
Slave Mode
Line Clock Mode
l Slave Mode: The CES

ACR clock is used as
the output clock of
services. The port
inputting E1 clocks on
Slave is set to Slave
Mode.
l Line Clock Mode:
The upstream E1 line
clock of the opposite
equipment is used as
the output clock of
services. The port
inputting E1 clocks on
Master is set to
System Clock Mode
Issue 01 (2016-04-30)

1282

Configuration Guide
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
canceled 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 precautions
before starting this
function.
l Generally, this
parameter is set to
Non-Loopback.
Impedance
Issue 01 (2016-04-30)

Displays the port

impedance.
1283

Configuration Guide
Parameter
Value Range
Default Value
Description
Frame Mode
30(ATM,ML-PPP)
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,ML-PPP)
l 31 timeslots: In an E1
frame format,
timeslots 1 to 31 are
used to transmit
service data.
l This parameter is
unavailable if Frame
Format is Unframe.
l The port frame modes
need to be the same at
the local and opposite
ends.
CES Encapsulation
Clock Mode
NULL
NULL
Line Clock Mode
l This parameter
specifies the source of
clock signals
transmitted by CES
services.
l When CES services
do not transmit any
clock signals, set this
parameter to NULL.
l When an E1 port
functions as the
master in the CES
ACR solution, set this
parameter to Line
Clock Mode. The
CES services transmit
clock signals sourced
from the E1 line.
B.5.3 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the packet plane.
Issue 01 (2016-04-30)

1284

Configuration Guide
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.
2.

Parameter
Value Range
Default Value
Description
Port
Name
Specifies the port name.
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
Port Mode
Layer 2
Layer 2
Layer 3
Layer Mix
l Specifies the level of

services that a port
carries.
l If Port Mode is
Layer 2, the port can
carry native Ethernet
services.
l If Port Mode is
Layer 3, the port can
carry MPLS tunnels.
l If Port Mode is
Layer Mix, the port
can carry both native
Ethernet services and
MPLS tunnels.
Issue 01 (2016-04-30)

1285

Configuration Guide
Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
specifies the method
of the port to process
the received packets.
802.1Q
QinQ
l This parameter is
valid only when Port
Mode is Layer 2.
l If you set
Encapsulation Type
to Null, the port
transparently
transmits the received
packets.
l If you set
Encapsulation Type
to 802.1Q, the port
identifies the packets
that comply with the
IEEE 802.1q
standard.
l If you set
Encapsulation Type
to QinQ, the port
IEEE 802.1ad QinQ
standard.
Issue 01 (2016-04-30)

1286

Configuration Guide
Parameter
Value Range
Default Value
Description
Working Mode
Auto-Negotiation
Auto-Negotiation
l The Ethernet ports of

different types
support different
Working Mode. For
details, see the IDU
Hardware
Description.
10M Half-Duplex
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
1000M 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.
1000M Half-Duplex

works in full-duplex
mode, set the
Working Mode of
the equipment on the
local side to 10M
Full-Duplex, 100M
Full-Duplex, or
1000M Full-Duplex
depending on the port
rate of the equipment
on the opposite side.
works in half-duplex
mode, set the
Working Mode of
local side to 10M
Half-Duplex, 100M
Half-Duplex.
Max Frame Length
(bytes)
46 to 9600
1522
The value of Max Frame

Length(byte) should be
greater than the length of
any frame to be
transported.
NOTE
This parameter does not
take effect for L3VPN
services.
Issue 01 (2016-04-30)

1287

Configuration Guide
Parameter
Value Range
Default Value
Description
Auto-Negotiation
Ability
10M Half-Duplex
FE: 100M Full-Duplex
10M Full-Duplex
GE: 1000M Full-Duplex
l This parameter
specifies the optimal
working mode that
can be automatically
negotiated.
100M Half-Duplex
100M Full-Duplex
1000M Full-Duplex
l Auto-Negotiation
Ability is valid only
when Working Mode
is set to AutoNegotiation.
1000M Half-Duplex
Logical Port Attribute
Optical Port
Electrical Port
l This parameter
specifies the type of
the SFP module that
an Ethernet port can
house.
l If the specified and
actual SFP module
types are different, the
LASER_MOD_ERR
alarm is reported.
l If an Ethernet port is
shared by an SFP
optical module and an
RJ45 electrical
connector, this
parameter specifies
the port type of the
Ethernet port.
Physical Port Attribute

the physical type of an
Ethernet port.
Running Status

the status of the Ethernet
link.
Traffic Policing Status
Enabled
Disabled
Only after this parameter

is set to Enabled for an
Ethernet port, the
Ethernet port is able to
report the
ETH_NO_FLOW alarm.
Disabled
Issue 01 (2016-04-30)

1288

Configuration Guide
Parameter
Value Range
Default Value
Description
Traffic Policing Period

(min)
1 to 30
15
An Ethernet port reports

an ETH_NO_FLOW
alarm when the following
conditions are met:
l Both Enable Port
and Traffic
Monitoring Status
are set to Enabled.
l The Ethernet link is
working properly.
l The Ethernet port
bears no traffic for
Traffic Monitoring
Period (min).
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 01 (2016-04-30)

1289

Configuration Guide
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
opposite side
l OptiX RTN 900
supports only two
non-auto-negotiation
flow control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
Auto-Negotiation Flow
Control Mode
Disabled
Disabled
Enable Symmetric Flow

Control
Enable Dissymmetric
Flow Control
Enable Symmetric/
Dissymmetric Flow
Control
l Auto-Negotiation
Flow Control Mode
is valid only when
Working Mode is set
to Auto-Negotiation.
l Auto-Negotiation
Flow Control Mode
of the equipment on
the local side must be
consistent with the
auto-negotiation flow
control mode of the
equipment on the
opposite side
l OptiX RTN 900
supports only two
auto-negotiation flow
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
Issue 01 (2016-04-30)

1290

Configuration Guide
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.

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.
TAG
Tag Aware
Tag Aware
Access
Hybrid
l If all the accessed

services are frames
with the VLAN tag
(tagged frames), set
TAG to Tag Aware.
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.
Issue 01 (2016-04-30)

1291

Configuration Guide
Parameter
Value Range
Default Value
Description
Default VLAN ID
1 to 4094
l Default VLAN ID is
valid only when TAG
is set to Access or
Hybrid.
VLAN Priority
0 to 7
l VLAN Priority is
valid only when TAG
is set to Access or
Hybrid.
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
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.
Issue 01 (2016-04-30)

1292

Configuration Guide
Parameter
Value Range
Default Value
Description
Specify IP Address
Manually
Unspecified
l Specifies the method

of setting the IP
address of a port.
Unspecified
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
Manually.
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.
Issue 01 (2016-04-30)

1293

Configuration Guide

Parameter
Value Range
Default Value
Description
Port
This parameter
indicates the port
name.
Port Physical Parameters
This parameter
indicates 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
recommended
that you use
the default
value.
Issue 01 (2016-04-30)

1294

Configuration Guide
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
recommended
that you use
the default
value.
MAC Address
This parameter
indicates the
MAC address of
the port.
Transmitting Rate(kbit/s)
This parameter
indicates the rate
at which the data
packets are
transmitted.
Receiving Rate(kbit/s)
This parameter
indicates the rate
at which the data
packets are
received.
Loopback Check
Enabled
Disabled
This parameter
specifies whether
to enable loop
detection, which
is used to check
whether a loop
exists on the
port.
Disabled
Issue 01 (2016-04-30)

1295

Configuration Guide
Parameter
Value Range
Default Value
Description
Loopback Port Block
Enabled
Disabled
This parameter
indicates whether
to enable the
loop port
shutdown
function.
This parameter
indicates the
egress PIR
bandwidth.
Disabled
Egress PIR Bandwidth(kbit/s)
The NE does not

support this
parameter.
Broadcast Packet Suppression
Disabled
Disabled
Enabled
l When this
parameter is
set to
Enabled, the
traffic of
ingress
broadcast
packets is
limited based
on the ratio of
bandwidth
used by the
broadcast
packets to the
total port
bandwidth.
l For ports that
carry E-LAN
services, it is
recommended
that you set
this
parameter to
Enabled.
Issue 01 (2016-04-30)

1296

Configuration Guide
Parameter
Value Range
Default Value
Description
Broadcast Packet Suppression Threshold(%)
0 to 100
30
When the
proportion of the
broadcast
packets in the
port bandwidth
exceeds the
value of this
parameter, the
received
broadcast
packets are
discarded. The
value of this
parameter should
be more than the
proportion of the
broadcast
packets in the
total packets
before the
broadcast storm
occurs. In normal
cases, this
parameter is set
to default value.
Network Cable Mode
This parameter
displays the
working mode of
the network
cable connected
to an Ethernet
port.
Optical Module Type
This parameter
displays the
optical module
type.
The NE does not
support this
parameter.
Issue 01 (2016-04-30)

1297

Configuration Guide
Parameter
Value Range
Default Value
Description
POE
Disabled
Disabled
l If the PoE
port supports
autonegotiation
and is
connected to
a normal
Ethernet port
or an FO
device (for
example,
OptiX RTN
360)
supporting
the PoE
power level,
set this
parameter to
AutoNegotiation.
In this case,
the PoE port
will
automatically
identify
whether to
supply power
to the peer
device. If the
PoE port
needs to
supply power
to a device
(for example,
OptiX RTN
310/380) that
does not
support autonegotiation,
set this
parameter to
Enabled.
Enabled
AutoNegotiation
l If the PoE
port does not
support autonegotiation
and needs to
supply power
to an FO
device, set
Issue 01 (2016-04-30)

1298

Configuration Guide
Parameter
Value Range
Default Value
Description
this
parameter to
Enabled;
otherwise, set
this
parameter to
Disabled.
l Only the PoE
port on OptiX
RTN 905 2E
supports
autonegotiation.
l OptiX RTN
905 1E does
not support
this
parameter.
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.
Navigation Path
1.
Configuration > Interface Management > Serial Interface from the Function Tree.
2.

Parameter
Value Range
Default Value
Description
Port
Displays the name of the

port where a serial port is
configured.
Name

Issue 01 (2016-04-30)

1299

Configuration Guide
Parameter
Value Range
Default Value
Description
Level
l Specifies the serial

port level.
l 64K Timeslot: 64
kbit/s timeslots of E1
signals can be bound.
l VC12: E1s in a
channelized STM-1
can be used as MLPPP
links.
Used Port
Displays the physical port

that carries the serial port.
High Channel
Displays the high channel

Low Channel
Displays the low channel

64K Timeslot
Displays the timeslots

that a serial port occupies.
The timeslots can be
consecutive or not.
Port Mode
Layer 2
l Displays or specifies
the port mode.
Layer 3
l When a serial port

carries ATM services,
set this parameter to
Layer 2.
carries Multi-Link
Point-to-Point
Protocol (ML-PPP)
links, set this
parameter to Layer 3.
Encapsulation Type
the encapsulation type
of a serial port.
carries ATM services,
ATM.
carries ML-PPP links,
PPP.
Issue 01 (2016-04-30)

1300

Configuration Guide
Parameter
Value Range
Default Value
Description
Max Data Packet

Size(byte)
l This parameter is
valid only when
Encapsulation Type
is set to PPP.
l It is recommended
that you retain the
default value for this
parameter.
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 number

of the serial port.
Name
Specifies the customized

port name.
Level
64K Timeslot
VC12
l Specifies the serial

port level.
VC12

is set to 64K
Timeslot, E1
timeslots can be
bound.
l VC12: E1s in a
channelized STM-1
can be used as
MLPPP links.
Used Board
Specifies the board where

a serial port is located.
Used Port
Displays the board where

a serial port is located.
High Channel
The NE does not support

this parameter.
Issue 01 (2016-04-30)

1301

Configuration Guide
Parameter
Value Range
Default Value
Description
Low Channel(e.g:1,3-6)
Specifies the VC-12

lower order paths bound
with the serial port. The
VC-12 timeslots can be
not consecutive.
64K Timeslot(e.g:1,3-6)
Specifies the 64 kbit/s

timeslots to be bound
with the serial port. The
timeslots can be
consecutive or not.
B.5.5 Channelized STM-1 Port Parameters

This sections describes parameters that are used for configuring channelized STM-1 ports.
B.5.5.1 Parameter Description: Clock Transparent Transmission

This section describes the parameters that are used for configuring clock transparent
transmission over channelized STM-1 ports.
Navigation Path
1.
In the NE Explorer, select a channelized STM-1 interface board from the Object Tree
and choose Configuration > Clock Transparent Transmission > Clock Transparent
Transmission.
Parameters in the Window for Configuring Clock Transparent Transmission

Parameter
Value Range
Default Value
Description
Retiming Mode
System Clock
System Clock

is set to System
Clock, all ports on the
channelized STM-1
interface board are
used to receive and
transmit SDH frames.
l When the channelized
STM-1 interface
board is connected to
a third-party
asynchronous SDH
network, it is
recommended that
you set this parameter
to Line Clock. After
Line Clock
Issue 01 (2016-04-30)

1302

Configuration Guide
Parameter
Value Range
Default Value
Description
Line Clock Port
Port 1 to Port 4
this setting, the

system extracts the
third-party network
clock through the
Line Clock Port on
the channelized
STM-1 interface
board. All ports on the
channelized STM-1
interface board use the
extracted clock for
receiving and
transmitting SDH
frames.
Port
Port 1 to Port 4
Timeslot
VC12-1 to VC12-63
The channelized STM-1

interface board provides
two tributary clock
sources, which are the
fifth and sixth clock
sources. The system can
extract timing
information from an E1
signal stream as an input
to the clock priority table.
B.5.5.2 Parameter Description: Path Configuration

This section describes the parameters that are used for configuring paths over channelized
STM-1 ports.
Navigation Path
1.
In the NE Explorer, select a channelized STM-1 interface board from the Object Tree
and choose Configuration > Interface Management > Path Configuration from the
Function Tree.
Parameters in the Window for Configuring Paths over Channelized STM-1 Ports
NOTE
Before changing VC12 Frame Format and Frame Mode for a port enabled with inband DCN, disable
inband DCN.
Parameter
Value Range
Default Value
Description
Object
Displays each VC-12

path over a channelized
STM-1 port.
Issue 01 (2016-04-30)

1303

Configuration Guide
Parameter
Value Range
Default Value
Description
VC12 Frame Format
Unframe
CRC-4 Multiframe
l Specifies the E1 frame

format encapsulated
in VC-12s.
Double Frame
CRC-4 Multiframe
l In CESoPSN
emulation mode,
VC12 Frame Format
can be set to CRC-4
Multiframe or
Double Frame. It is
recommended that
you set VC12 Frame
Format to CRC-4
Multiframe.
l In SAToP emulation
mode, VC12 Frame
Format needs to be
set to Unframe.
l If E1s are members in
an MP group, it is
recommended that
you set VC12 Frame
Format to CRC-4
Multiframe.
l Set VC12 Frame
Format to the same
value at both ends.
Issue 01 (2016-04-30)

1304

Configuration Guide
Parameter
Value Range
Default Value
Description
Frame Mode
31
31
l If Frame Mode is set

to 30, timeslots 1 to
15 and 17 to 31 are
used to transmit
services and timeslot
16 is transmitted to
transmit signaling.
30
l If Frame Mode is set

to 31, timeslots 1-31
are used to transmit
services.
l Frame Mode is
unavailable when
VC12 Frame Format
is set to Unframe.
l If E1s are members in
an MP group, it is
recommended that
you set Frame Mode
to 31.
l Generally, it is
recommended that
you set Frame Mode
to the same value for
the local and opposite
ports. When E1s are
emulated to CES
services, set Frame
Mode to 31 even if
Frame Mode is set to
30.
Issue 01 (2016-04-30)

1305

Configuration Guide
Parameter
Value Range
Default Value
Description
Loopback Mode
Non-Loopback
Non-Loopback
the port loopback
status.
Inloop
Outloop
l Non-Loopback
indicates that the
loopback is canceled
or not performed.
l Inloop indicates that
the service signals
transmitted to the
opposite end are
looped back.
l Outloop indicates that
the received service
signals are looped
back.
l This function is used
for port fault locating.
This function affects
services on the related
port.
l Normally, this
parameter is set to
Non-Loopback.
B.5.6 Microwave Interface Parameters

This topic describes the parameters that are related to IF_ETH interfaces.
B.5.6.1 Parameter Description: Microwave Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of microwave
interfaces.
NOTE
The maximum frame length (MFL) is invalid for L3VPN services.
Navigation Path
1.
2.
Issue 01 (2016-04-30)

1306

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
Port
This parameter indicates the corresponding

IF port.
Name
This parameter indicates or specifies the

Port Mode
Layer 2
Layer 2
l This parameter specifies the level of

services that a port carries.
Layer 3
l If Port Mode is Layer 2, the port can

carry native Ethernet services.
Layer Mix
l If Port Mode is Layer 3, the port can

carry tunnels.
l If Port Mode is Layer Mix, the port
can carry both tunnels and Native
Ethernet services.
Encapsulation
Type
Null
802.1Q
802.1Q
QinQ
l Encapsulation Type specifies the

method of the port to process the
received packets.
l This parameter is valid only when Port
Mode is Layer 2.
l If Encapsulation Type is set to Null,
the port transparently transmits the
received packets.
l If Encapsulation Type is set to
802.1Q, the port identifies the packets
that comply with the IEEE 802.1Q
standard.
l If Encapsulation Type is set to QinQ,
the port identifies the packets that
comply with the IEEE 802.1ad QinQ
standard.
Traffic Policing
Status
Enabled
Traffic Policing
Period(min)
1 to 30
Disabled
Parameter is set to Enabled, the port is

qualified for capability to report alarms
ETH_NO_FLOW.
15
When port the following conditions are

met, Alarms will be reported
ETH_NO_FLOW.
Disabled
l Traffic Policing Status and Port

Status are set to Enabled.
l Link connection is normal.
l Traffic Policing Period(min) port no
flow.
Issue 01 (2016-04-30)

1307

Configuration Guide
Parameter
Value Range
Default Value
Description
Running Status
This parameter indicates status of the

Ethernet link.
B.5.6.2 Parameter Description: Microwave Interface_Layer 2 Attributes

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

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
Access
Hybrid
Tag Aware
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-2.
Issue 01 (2016-04-30)

1308

Configuration Guide
Parameter
Value Range
Default Value
Description
Default VLAN ID
1 to 4094
l Default VLAN ID is valid only when

TAG is set to Access or Hybrid.
NOTE
For details about the functions of Default
VLAN ID, see Table B-2.
VLAN Priority
l VLAN Priority is valid only when

TAG is set to Access or Hybrid.
NOTE
For details about the functions of VLAN
Priority, see Table B-2.
2
3
4
5
6
7
Table B-2 Data frame processing

Status
Ingress Port
Issue 01 (2016-04-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 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.

1309

Configuration Guide
Status
Egress Port
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.
B.5.6.3 Parameter Description: Microwave Interface_Layer 3 Attributes

This topic describes the parameters that are related to the Layer 3 attributes of an microwave
interfaces.
Navigation Path
1.
Configuration > Interface Management > Microwave Interface from the Function
Tree.
2.

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.
Issue 01 (2016-04-30)

1310

Configuration Guide
Parameter
Value Range
Default Value
Description
Specify IP Address
Manually
Unspecified
l Specifies the method

of setting the IP
address of a port.
Unspecified
l The value
do not need to be
configured for a port.
address of a port can
be manually
configured.
IP Address
0.0.0.0
l Specifies the IP
address for a port.
l This parameter is
available when
Manually.
different ports on the
NE cannot be in the
same network
segment, but the IP
at both ends of the
MPLS tunnel must be
in the same network
segment.
IP Mask
255.255.255.252
l Specifies the subnet

mask of a port.
l This parameter is
available when
Manually.
B.5.6.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.
Issue 01 (2016-04-30)
1311

Configuration Guide
2.
Parameters for Advanced Attributes

Parameter
Value Range
Default Value
Description
Port

IF port.
Error Frame
Discard Enabled
An Ethernet frame which has a CRC error

will be discarded.
MAC Address
This parameter indicates the MAC address

of the port.
Jitter Adjustment
Disabled
Disabled
This parameter indicates or specifies

whether the jitter adjustment function is
enabled for ISU2/ISX2 boards.
Enabled
When this parameter is set to Enabled,

jitter of services carried by ISU2/ISX2
boards can be decreased, but weighted
round robin (WRR) may be inaccurate.
This parameter generally takes the default
value.
parameter.
Speed
Transmission at
L2
Disabled
Disabled
Enabled
l If Speed Transmission at L2 is set to

Enabled, the Layer-2 Ethernet packets
transmitted at microwave ports will be
compressed to improve transmission
efficiency.
l The settings of Speed Transmission at
L2 must be the same at both ends of a
radio link.
Speed
Transmission at
L3
Disabled
Disabled
Enabled
l If Speed Transmission at L3 is set to

Enabled, the IP packets transmitted at
microwave ports will be compressed to
improve transmission efficiency.
l The settings of Speed Transmission at
L3 must be the same at both ends of a
radio link.
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.
Enabled
Loopback Port
Block
Issue 01 (2016-04-30)
Disabled
Enabled

1312

Configuration Guide
Parameter
Value Range
Default Value
Description
Broadcast Packet
Suppression
Disabled
Disabled

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
l If Ethernet services are E-LAN

services, the recommended value is
Enabled.
Broadcast Packet
Suppression
Threshold(%)
0 to 100
30
When the proportion of the broadcast

packets in the port bandwidth exceeds the
value of this parameter, the received
broadcast packets are discarded. The value
of this parameter should be more than the
proportion of the broadcast packets in the
port bandwidth before the broadcast storm
occurs. In normal cases, this parameter is
set to default value.
NOTE
Assume that the bandwidth of an IF port is 400
Mbit/s.
Enable Switching
Triggered by Bit
Error
Disabled
Switching Mode
Triggered by Bit
Error
SF
Disabled
Specifies whether to enable switching

triggered by bit errors.
SF
Specifies the mode of switching triggered

by bit errors.
Enabled
SD
B.5.7 IF Board Parameters

This topic describes parameters that are related to IF boards.
B.5.7.1 Parameter Description: IF Interface_IF Attribute

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
Click the IF Attributes tab.
Issue 01 (2016-04-30)

1313

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
Port

IF interface.
Power Switch
Open
Open
This parameter specifies whether to turn on

or off the ODU power switch for an ISM6
board.
Close
NOTE
Only ISM6 boards support this parameter.
Alarm and
Performance
Report
Enabled
IF Service Type
Hybrid(Native
E1+ETH)
Enabled
RTN 905, RTN 910A, and ISV3/ISM6

boards on RTN 980/RTN 980L/RTN
950/RTN 950A allow Alarm and
Performance Report to be specified. If
Alarm and Performance Report is set to
Disabled, alarms of IF ports and the
corresponding ODUs/RFUs are not
reported.
Hybrid(Native
E1+ETH)
This parameter displays or specifies the

type of services carried by the IF board.
Disabled
NOTE
For details about services that different types of
IF boards support, see the IDU Hardware
Description.
Hybrid(Native
STM-1+ETH)
SDH
Microwave Link
ID
1 to 4094
l Radio Link ID indicates or specifies

the ID of a radio link. As the identifier
of a radio link, this parameter is used to
prevent incorrect connections of radio
links between sites.
l If the value of Received Radio Link
ID does not match the preset value of
Radio Link ID at the local end, the
local end reports MW_LIM alarm to
the NMS.
l Radio Link ID is set according to the
network plan. Each radio link of an NE
should have a unique link ID, and the
link IDs at both ends of a radio link
should be the same.
Received
Microwave Link
ID
Issue 01 (2016-04-30)
This parameter indicates the received ID of

the radio link.

1314

Configuration Guide
Parameter
Value Range
Default Value
Description
IF Port Loopback
Non-Loopback
Non-Loopback

the loopback status of the IF interface.
Inloop
l Non-Loopback indicates that the

loopback is canceled 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 set to NonLoopback.
2M Wayside
Enable Status
Disabled
Disabled
Enabled

whether the radio link transmits the
wayside E1 service.
l Only SDH radio supports wayside E1
services.
2M Wayside Input
Board

the slot housing the system control,
switching, and timing board that
processes wayside E1 services.
2M Wayside Enable Status is set to
Enabled.
l When 1+1 protection is configured for
system control, switching, and timing
boards on the RTN 950, only external
clock ports on the system control,
switching, and timing board in slot 7
can receive/transmit wayside E1
services. In this case, this parameter
takes a fixed value of 7.
l When 1+1 protection is configured for
system control, switching, and timing
boards on the RTN 980/RTN 980L,
only external clock ports on the system
control, switching, and timing board in
slot 15 can receive/transmit wayside E1
services. In this case, this parameter
takes a fixed value of 15.
Consecutive Wave
Status
Stop
Start
Stop

whether an IF port outputs 350 MHz
consecutive waves without modulation
signals.
l Generally, this parameter is set to Stop.
Issue 01 (2016-04-30)

1315

Configuration Guide
Parameter
Value Range
Default Value
Description
XPIC Enabled
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
Timeslot
Enabled
Disabled
Disabled
l Enable IEEE-1588 Timeslot needs to

be set consistently between two ends of
a radio link.
l If the NE needs to transmit IEEE
1588v2 packets, set Enable
IEEE-1588 Timeslot to Enabled. If
the NE does not need to transmit IEEE
1588v2 packets, set Enable
IEEE-1588 Timeslot to Disabled.
Running Mode
IS2
IS3
IS3
IS6
l An IF port on an ISU2/ISX2 board can

interconnect only with an IF port that
supports the IS2 mode.
l RTN 905 1E/2E can work in IS2 or IS3
mode. By default, RTN 905 1E/2E
works in IS3 mode. Set Running Mode
to the same value for the two IF units
on an RTN 905 2E.
l ISV3 boards can work in IS2 or IS3
mode. By default, ISV3 boards work in
IS3 mode.
l IF ports on ISM6 boards can work in
IS2, IS3, or IS6 mode. By default, IF
ports on ISM6 boards work in IS6
mode. The two IF ports on an ISM6
board must work in the same mode.
l It is recommended that two
interconnected IF ports work in the
highest-order mode that they both
support.
l Before switching the running mode of
an IF port, delete services on the port.
l If IF ports are configured with services
or 1+1, N+1, PLA/EPLA/EPLA+, or
LAG protection, their Running Mode
cannot be modified.
NOTE
For RTN 950/980, the IF1 boards support setting of Radio Working Mode but does not support setting of IF
Service Type, XPIC Enabled, Enable IEEE-1588 Timeslot, and Running Mode.
Issue 01 (2016-04-30)

1316

Configuration Guide
Parameters for Hybrid/AM Configuration

NOTE
For RTN 950/980, the IF1 board does not support Hybrid/AM configuration.
Parameter
Value Range
Default Value
Description
Port

IF port.
IF Channel
Bandwidth
IF Channel Bandwidth indicates the

channel spacing of the corresponding radio
link. This parameter is set according to the
network plan.
AM Boost Status
Disabled
Disabled
The adaptive modulation (AM) Boost

function increases the transmit power of an
ODU by 1 to 3 dB when IF boards are
working in AM full capacity mode. As a
result, the fading margin and working time
of radio links also increase.
Enabled
NOTE
Only ISX2 board supports AM Boost function.
AM Status
Disabled
Disabled
Enabled
l When AM 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 Status is set to Enabled,
the radio link uses the corresponding
modulation scheme according to the
channel conditions.
l Only the Integrated IP microwave
supports the AM function.
Modulation Mode
of the Guarantee
AM Capacity
Issue 01 (2016-04-30)

Status is set to Enabled.
l Modulation Mode of the Guarantee
AM Capacity specifies the lowestorder modulation scheme that the AM
function supports. This parameter is set
determined by the bandwidth of
guarantee services and the availability
of the radio link that corresponds to this
modulation scheme.

1317

Configuration Guide
Parameter
Value Range
Default Value
Description
Modulation Mode
of the Full AM
Capacity

Manually
Specified
Modulation Mode
l Modulation Mode of the Full AM

Capacity specifies the highest-order
modulation scheme that the AM
function supports. This parameter is set
determined by the bandwidth of full
services and the availability of the radio
link that corresponds to this modulation
scheme.
-

modulation mode that the radio link
uses for signal transmission.
Status is set to Disabled.
STM-1 Capacity
l This parameter specifies the STM-1

service capacity of an IF port.
l This parameter is valid only when IF
STM-1+ETH) or SDH.
Enable E1
Priority
Disabled
Disabled
Enabled

enable the E1 priority function.
Status is set to Enabled and IF
E1+ETH).
Guarantee E1
Capacity

Disabled, this parameter specifies the
E1 service capacity of an IF port.
Enabled, this parameter specifies the
E1 service capacity in Modulation
Mode of the Guarantee AM
Capacity.
l This parameter is valid when IF
Service Type is Hybrid(Native
E1+ETH).
Guarantee E1
Capacity Range
Issue 01 (2016-04-30)
Displays the E1 capacity range of the IF

board in guarantee capacity modulation
mode.

1318

Configuration Guide
Parameter
Value Range
Default Value
Description
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 less than or equal to the
maximum number of E1 services in full
capacity modulation mode.
l The Full E1 Capacity must be set to
the same value at both ends of a radio
link.
l This parameter is valid when IF
Service Type is Hybrid(Native
E1+ETH).
Full E1 Capacity
Displays the E1 capacity range of the IF

board in full capacity modulation mode.
Transmit-End
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.
Issue 01 (2016-04-30)

1319

Configuration Guide
B.5.7.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.
ATPC Enable
Status
Disabled
Disabled

ATPC function is enabled.
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
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
threshold.
l The settings of the ATPC attributes
must be consistent at both ends of a
radio link.
l In the case of areas where fast fading
severely affects the radio transmission,
it is recommended that you set ATPC
Enable Status to Disabled.
l During the commissioning process, set
this parameter to Disabled to ensure
that the transmit power is not changed.
After the commissioning, re-set the
ATPC attributes.
ATPC Upper
Threshold(dBm)
Issue 01 (2016-04-30)
-45.0
l Set the central value between the ATPC

upper threshold and the ATPC lower
threshold to a value for the expected
receive power.

1320

Configuration Guide
Parameter
Value Range
Default Value
Description
ATPC Lower
Threshold(dBm)
-70.0
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
threshold and 10 dB.
l You can set the ATPC upper threshold
only when ATPC Automatic
Threshold(dBm) is set to Disabled.
ATPC Automatic
Threshold Enable
Status
Enabled
Disabled

ATPC automatic threshold function is
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)
l This parameter indicates that the

equipment automatically uses the preset
ATPC upper and lower thresholds.
ATPC Lower
Automatic
Threshold(dBm)

ATPC Automatic Threshold Enable
B.5.7.3 Parameter Description: IF Port_Advanced Attributes

This section describes the parameters for configuring advanced attributes for IF ports.
Navigation Path
l
In the NE Explorer, select the IF board, and then choose Configuration > IF Interface
Click the AM Advanced Attributes tab.
Issue 01 (2016-04-30)

1321

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
Port

IF interface.
Modulation Mode
Displays the modulation schemes.
E1 Capacity/
STM-1 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.
B.5.7.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.
Issue 01 (2016-04-30)

1322

Configuration Guide
Parameter
Value Range
Default Value
Description
Event NO.
This parameter indicates the number of the

ATPC adjustment event.
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

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.
B.5.8 RFU/ODU Parameters

This topic describes parameters that are related to RFU/ODUs.
B.5.8.1 Parameter Description: RFU/RFU-SD/ODU Interface_Radio Frequency

Attribute
This topic describes the parameters that are related to radio frequency attributes of an ODU.
Navigation Path of ODU

l
Select the ODU from the Object Tree in the NE Explorer. Choose Configuration >
ODU Interface from the Function Tree.
Click the Radio Frequency Attributes tab.
Navigation Path of RFU/RFU-SD

l
Select the RFU/RFU-SD from the Object Tree in the NE Explorer. Choose
Configuration > RF Interface from the Function Tree.
Click the Radio Frequency Attributes tab.
Parameters
Parameter
Value Range
Default Value
Description
Board

RFU/RFU-SD/ODU.
Issue 01 (2016-04-30)

1323

Configuration Guide
Parameter
Value Range
Default Value
Description
Transmit
Frequency(MHz)

the transmit frequency of the RFU/
RFU-SD/ODU, namely, the central
frequency of the channel.
l The value of Transmit
Frequency(MHz) must not be less than
the sum of the minimum transmit
frequency supported by the RFU/RFUSD/ODU and a half of the channel
spacing, and must not be more than the
difference between the maximum
transmit frequency supported by the
RFU/RFU-SD/ODU and a half of the
channel spacing.
l The difference between the transmit
frequencies at both ends of a radio link
by ODU should be one T/R spacing.
Receive
Frequency(MHz)

the spacing between the transmit
frequency and receive frequency of the
RFU/RFU-SD to prevent mutual
interference of the transmitter and
receiver.
NOTE
This parameter is supported by only OptiX
RTN 980L.
Issue 01 (2016-04-30)

1324

Configuration Guide
Parameter
Value Range
Default Value
Description
T/R
Spacing(MHz)

the spacing between the transmit
frequency and receive frequency of the
ODU to prevent mutual interference of
the transmitter and receiver.
l If the ODU is a Tx high station, the
transmit frequency is one T/R spacing
higher than the receive frequency. If the
ODU is a Tx low station, the transmit
frequency is one T/R spacing lower
than the receive frequency.
l If the ODU supports only one T/R
spacing, T/R Spacing(MHz) is set to 0,
indicating that the T/R spacing
supported by the ODU is used.
l A valid T/R spacing value is
determined by the ODU itself, and T/R
Spacing(MHz) should be set according
to the technical specifications of the
ODU.
l The T/R spacing of the ODU should be
set to the same value at both ends of a
radio link.
NOTE
This parameter is not supported by OptiX RTN
980L.
Actual Transmit
Frequency(MHz)
This parameter indicates the actual

transmit frequency of the RFU/RFU-SD/
ODU.
Actual Receive
Frequency(MHz)
This parameter indicates the actual receive

frequency of the RFU/RFU-SD/ODU.
Actual T/R
Spacing(MHz)
This parameter indicates the actual T/R

spacing of the ODU.
NOTE
980L.
The range of
Transmit
frequency
point(MHz)
This parameter indicates the working range

of the transmit frequency of the RFU/RFUSD/ODU.
The range of
Receive frequency
point(MHz)
This parameter indicates the working range

of the receive frequency of the RFU/RFUSD.
NOTE
This parameter is supported by only OptiX
RTN 980L.
Issue 01 (2016-04-30)

1325

Configuration Guide
B.5.8.2 Parameter Description: RFU/RFU-SD/ODU Interface_Power Attributes

This topic describes the parameters that are used for configuring the power attributes of the
RFU/RFU-SD/ODU.

l
Click the Power Attributes tab.

l
Select the RFU/RFU-SD from the Object Tree in the NE Explorer. Choose
Configuration > RFInterface from the Function Tree.
Click the Power Attributes tab.
Parameters
Parameter
Value Range
Default Value
Description
Board

RFU/RFU-SD/ODU.
Maximum
Transmit
Power(dBm)
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
RFU/RFU-SD/ODU in the guaranteed
capacity modulation module.
l This parameter is set to limit the
maximum transmit power of the RFU/
RFU-SD/ODU within this preset range.
l The maximum transmit power adjusted
by using the ATPC function should not
exceed Maximum Transmit
Power(dBm).
Issue 01 (2016-04-30)

1326

Configuration Guide
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 RFU/RFU-SD/ODU. This
parameter cannot be set to a value that
exceeds the nominal power rang of the
RFU/RFU-SD/ODU or a value that
exceeds Maximum Transmit
Power(dBm).
l It is recommended that you set the
transmit power of the RFU/RFUSD/ODU to the same value at both ends
of a radio link.
l Consider the receive power of the RFU/
RFU-SD/ODU at the opposite end
when you set this parameter. Ensure
that the receive power of the RFU/
RFU-SD/ODU at the opposite end can
ensure stable radio services.
Issue 01 (2016-04-30)

1327

Configuration Guide
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
RFU/RFU-SD/ODU and is mainly used
in the antenna alignment stage. After
this parameter is set, the NE
automatically enables the antenna
misalignment indicating function.
l When the antenna misalignment
indicating function is enabled, if the
actual receive power of the RFU/RFUSD/ODU is 3 dB lower than the power
expected to be received, the RFU/RFUSD/ODU indicator on the IF boarda
connected to the RFU/RFU-SD/ODU
blinks yellow (300 ms on, 300 ms off),
indicating that the antenna is not
aligned.
NOTE
a: For OptiX RTN 905, this indicator is the
LINK indicator on the front panel.
l After the antenna alignment, after the

state that the antenna is aligned lasts for
30 minutes, the NE automatically
disables the antenna misalignment
indicating function.
l Power to Be Received(dBm) is set
according to the network plan. When
this parameter takes the default value,
the antenna misalignment indicating
function is disabled.
SD Power to Be
Received(dBm)
-90.0 to -20.0
Specifies the SD power to be received of

an RFU-SD.
NOTE
This parameter is supported only when the SD
combination function is enabled for OptiX RTN
980L.
TX High
Threshold(dBm)
Issue 01 (2016-04-30)
l If the value of the actual transmit power

of the RFU/RFU-SD/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 power
than the preset value of TX High
Threshold(dBm) and the duration
when the value of the actual transmit
power of the RFU/RFU-SD/ODU is
greater than the preset value of TX

1328

Configuration Guide
Parameter
Value Range
Default Value
Description
TX Low
Threshold(dBm)
Low Threshold(dBm) in the

performance events.
than the preset value of TX Low
Threshold(dBm) and is lower than the
preset value of TX High
Threshold(dBm), the system records
the duration when the value of the
actual transmit power of the RFU/RFUSD/ODU is greater than the preset
value of TX Low Threshold(dBm) in
the performance events.
of the RFU/RFU-SD/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 RFU/RFU-SD/ODU is lower
than the preset value of RX Low
actual receive power of the RFU/RFUSD/ODU is lower than the preset value
of RX Low Threshold(dBm) and
duration when the value of the actual
transmit power of the RFU/RFUSD/ODU is lower than the preset value
of RX High Threshold(dBm) in the
performance events.
than the preset value of RX Low
Threshold(dBm) and is lower than the
preset value of RX High
actual receive power of the RFU/RFUSD/ODU is Lower than the preset value
of RX High Threshold(dBm) in the
performance events.
than the preset value of RX High
Issue 01 (2016-04-30)

1329

Configuration Guide
Parameter
Value Range
Default Value
RX Low
Threshold(dBm)
SD RX High
Threshold(dBm)
-90.0 to -20.0
Description
Threshold(dBm), the system does not
record it.
Specifies the upper threshold of SD receive
power of an RFU-SD.
NOTE
980L.
SD RX Low
Threshold(dBm)
-90.0 to -20.0
Specifies the lower threshold of SD receive

power of an RFU-SD.
NOTE
980L.
Actual Transmit
Power(dBm)
l This parameter indicates the actual

transmit power of the RFU/RFU-SD/
ODU.
l If the ATPC function is enabled, the
queried actual transmit power may be
different from the preset value.
Actual Receive
Power(dBm)
This parameter indicates the actual receive

power of the RFU/RFU-SD/ODU.
Actual SD Receive
Power(dBm)
Displays the actual SD receive power of an

RFU-SD.
NOTE
980L.
Actual range of
Power(dBm)
This parameter indicates the range of the

actual transmit power of the RFU/RFUSD/ODU.
Transmission
Power Type

output power of the RFU/RFU-SD/ODU.
B.5.8.3 Parameter Description: RFU/RFU-SD/ODU Interface_Equipment

Information
This topic describes the parameters that are used for configuring the equipment information of
the RFU/RFU-SD/ODU.

l
Issue 01 (2016-04-30)
Configuration > ODU Interface from the Function Tree.
1330

Configuration Guide
Click the Equipment Information tab.

l
Configuration > RF Interface from the Function Tree.
Click the Equipment Information tab.
Parameters
Parameter
Value Range
Default Value
Description
Board

RFU/RFU-SD/ODU.
Frequency(GHz)
This parameter indicates the frequency

band where the RFU/RFU-SD/ODU
operates.
Equipment Type
Displays the ODU type, indicating the

RFU/RFU-SD/ODU transmission
capability.
Actual T/R
Spacing(MHz)
This parameter indicates the T/R spacing

of the ODU.
NOTE
980L.
Intermediate
Frequency
Bandwidth (MHz)
This parameter indicates the IF frequency

bandwidth of the RFU/RFU-SD/ODU.
IF Bandwidth
Type
Displays the IF bandwidth type.
Station Type
l This parameter indicates whether the

RFU/RFU-SD/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

output power of the RFU/RFU-SD/ODU.
Produce Time
This parameter indicates the manufacturing

time of the RFU/RFU-SD/ODU.
Produce SN
This parameter indicates the manufacturing

serial number and the manufacturer code
of the RFU/RFU-SD/ODU.
Issue 01 (2016-04-30)

1331

Configuration Guide
B.5.8.4 Parameter Description: ODU Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes of the
ODU.

l
Parameters
Parameter
Value Range
Default Value
Description
Board
Indicates the corresponding ODU.
RF Loopback
Non-Loopback
Non-Loopback

the loopback status of the RF interface
of the ODU.
Inloop

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
unmute
mute
l Indicates or specifies the transmit status

of the ODU.
l If Configure Transmission Status is
set to mute, the transmitter of the ODU
does not work but can normally receive
microwave signals.
l If Configure Transmission Status is
set to unmute, the ODU can normally
transmit and receive microwave
signals.
l In normal cases, Configure
Transmission Status is set to unmute.
Actual
Transmission
Status
Issue 01 (2016-04-30)
Displays the ODU manufacturer

information.

1332

Configuration Guide
Parameter
Value Range
Default Value
Description
Factory
Information
Indicates the manufacturer information

about the ODU.
Alarm Threshold
for Fade Margin
Shortage(dB)
10.0-35.0
Specifies the alarm threshold for fade

margin shortage for an ODU.
Remarks
Specifies the remarks of the ODU.
B.5.9 Parameters for SDH Interface Boards

This topic describes parameters that are related to SDH interface boards.
B.5.9.1 Parameter Description: SDH Interfaces

This topic describes the parameters that are related to the SDH interfaces.
Navigation Path
1.
Configuration > Interface Management > 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

the on/off state of the laser.
Off
l This parameter is set for SDH optical

interfaces only.
l In normal cases, this parameter is set to
On.
Issue 01 (2016-04-30)

1333

Configuration Guide
Parameter
Value Range
Default Value
Description
Optical(Electrical)
Interface
Loopbacka
Non-Loopback
Non-Loopback

the loopback status on the SDH
interface.
Inloop
Outloop

l Inloop indicates that the SDH signals
looped back.
l Outloop indicates that the received
SDH signals are looped back.
l This function is used for fault locating
for the SDH interfaces. The
Optical(Electrical) Interface
Hence, exercise precaution before
starting this function.
Non-Loopback.
VC4 Loopbackb
Non-Loopback
Inloop
Outloop
Non-Loopback

the loopback status in the VC-4 path.
l Inloop indicates that the VC-4 signals
looped back.
VC-4 signals are looped back.
for the VC-4 paths. The VC4
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.
Issue 01 (2016-04-30)

1334

Configuration Guide
B.5.9.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 Ontest 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.10 Parameters for PDH Interface Boards

This topic describes parameters that are related to PDH interface boards.
B.5.10.1 Parameter Description: PDH Ports

This topic describes the parameters that are related to the PDH ports.
Issue 01 (2016-04-30)

1335

Configuration Guide
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

the loopback status in the associated
path of the tributary unit.
Inloop
Outloop

l Inloop indicates that the PDH signals
looped back.
PDH signals are looped back.
for the paths of the tributary unit. The
Tributary Loopback function is used
for diagnosis and may affect the
services that are transmitted over the
interfaces. Hence, exercise precautions
before starting this function.
Non-Loopback.
Port Impedance
Issue 01 (2016-04-30)
This parameter indicates the impedance of

a path, which depends on the tributary unit.

1336

Configuration Guide
Parameter
Value Range
Default Value
Description
Service Load
Indication
Load
Load

the 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 NonLoaded 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 01 (2016-04-30)

1337

Configuration Guide
Parameter
Value Range
Default Value
Description
Retiming Mode
Normal
Normal

the 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 Crossconnect Clock.
Port Service Type
E1
E1
If the system control board is SLF2CSHO,

the PDH ports of SP3S and SP3D boards
and the PDH port integrated on
SLF2CSHO boards can work in T1 mode.
On other RTN 900 series products, Port
Service Type can be set only to E1.
Unequalized

output signals are equalized.
T1
Output Signal
Equalization
Unequalized
Equalized

default value.
Issue 01 (2016-04-30)

1338

Configuration Guide
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 an
OptiX RTN 900, set E1 Frame Format
of the local E1 port to the same value as
that of the opposite E1 port. It is
recommended that E1 Frame Format
of both the local and opposite E1 ports
be CRC-4 Multiframe.
Double Frame
CRC-4 Multiframe
l In other scenarios wherein an OptiX

RTN 900 is used, it is recommended
that E1 Frame Format take its default
value Unframe. If E1 Frame Format
is Unframe, the OptiX RTN 900
transparently transmits E1 frames and
the local E1 port allows for
interconnection with another E1 port
whose E1 Frame Format is Double
Frame or CRC-4 Multiframe.
NOTE
E1 Frame Format needs to be set to the same
value at both ends of an E1 link.
B.5.11 Parameters for Overhead

This topic describes the parameters that are related to overhead.
B.5.11.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.
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.
Issue 01 (2016-04-30)
Deselected
Deselected

1339

Configuration Guide

Parameter
Value Range
Default Value
Description
Object
This parameter indicates the object to be

set.
J0 to be
Sent([Mode]Conte
nt)
[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]C
ontent)
[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]C
ontent)
This parameter indicates the J0 byte that is

actually received.
B.5.11.2 Parameter Description: VC-4 POHs

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.

Parameter
Value Range
Default Value
Description
Display in Text
Format
Selected
Selected

text format.
Display in
Hexadecimal
Selected
Deselected

hexadecimal format.
Issue 01 (2016-04-30)
Deselected
Deselected

1340

Configuration Guide
Parameters for the Trace Byte J1

Parameter
Value Range
Default Value
Description
Object

set.
J1 to be
Sent([Mode]Conte
nt)
[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]C
ontent)
[Disabled]

J1 byte.
default value.
J1
Received([Mode]C
ontent)
This parameter displays the J1 byte that is

actually received.
Parameters for the Signal Flag C2

Parameter
Value Range
Default Value
Description
Object

set.
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.
Parameters for Overhead Termination

Parameter
Value Range
Default Value
Description
Object

set.
Issue 01 (2016-04-30)

1341

Configuration Guide
Parameter
Value Range
Default Value
Description
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 passthrough service is passed through, and
the VC-4 path overhead in the VC-12
service is terminated.
default value.
B.5.11.3 Parameter Description: VC-12 POHs

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.
Deselected
Deselected
Parameters for the Trace Byte

Parameter
Value Range
Default Value
Description
Object

set.
Issue 01 (2016-04-30)

1342

Configuration Guide
Parameter
Value Range
Default Value
Description
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]

J2 byte.
default value.
NOTE
IF boards do not support this parameter.
J2 Received
This parameter displays the J2 byte that is

actually received.
Parameters for the Signal Flag

Parameter
Value Range
Default Value
Description
Object

set.
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.
B.5.12 Parameter Description: Ethernet Virtual Interfaces

This topic describes the parameters of Ethernet virtual interfaces.
Navigation Path
1.
Issue 01 (2016-04-30)
Configuration > Interface Management > Ethernet Virtual Interface from the
Function Tree.
1343

Configuration Guide
2.
3.
Choose New > Create Ethernet Virtual Interface.
Basic Attributes of Ethernet Virtual Interfaces

Parameter
Value
Range
Default
Value
Description
Port
1 to 8191

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

or specifies the port type
of an Ethernet virtual
interface.
VLAN Sub
Interface
OptiX RTN 900 allows

Port Type to be set to
VLAN Sub Interface
only.
Port Mode
Layer 3

mode of an Ethernet
virtual interface.
Associated Board

or specifies the board
where an Ethernet virtual
interface is located.
Associated Port

where an Ethernet virtual
interface is located.
VPI
Setting this parameter is

not available.
VCI

not available.
AAL5 Encapsulation Type

not available.
Issue 01 (2016-04-30)

1344

Configuration Guide
Parameter
Value
Range
Default
Value
Description
VLAN

the VLAN ID that an
Ethernet virtual interface
uses.
This parameter can be set
when Port Type is
VLAN Sub Interface.
Specify IP Address
Manually
Unspecifie
d
Unspecifie
d

whether to set the IP
address for a port.
l Unspecified:
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

the IP address of a port.
l This parameter can be
set only when Specify
IP Address is
Manually.
different ports on an
NE must be in
different network
segments, but the IP
at both ends of an
MPLS tunnel must be
in the same network
segment.
IP Mask
255.255.25
5.252

the subnet mask for a
port.
only when Specify IP
Address is Manually.
Issue 01 (2016-04-30)

1345

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Enable Tunnel
Enabled
Disabled

whether to enable an
MPLS tunnel.
Disabled

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.
Specify IP
Address
Manually
Unspecified
Unspecified
This parameter displays or specifies

whether to set the IP address for a port.
l Unspecified: indicates that the IP
address will not be specified for a port.
l Manually: indicates that the IP address
will be specified for a port. If the
specified IP address is a valid value, it
will become the IP address of this port.
IP Address
0.0.0.0
This parameter displays or specifies the IP

address of a port.
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.
Issue 01 (2016-04-30)

1346

Configuration Guide
B.6 Parameters for Ethernet Services and Ethernet Features

on the Packet Plane
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.
B.6.1.1 Parameter Description: E-Line Service_Creation (U2000)

This topic describes the interface parameters that are used for creating an Ethernet line (ELine) service.
Navigation Path
1.
Ethernet Service Management > E-Line Service from the Function Tree.
2.
Click New.

Table B-3 Service direction of UNI-UNI
Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294
This parameter
specifies the ID of the
E-Line service.
Service Name
This parameter
specifies the name of
the E-Line service.
Direction
UNI-UNI
UNI-UNI
l This parameter
specifies the
direction of the ELine service.
UNI-NNI
NNI-NNI

to UNI-UNI.
Issue 01 (2016-04-30)

1347

Configuration Guide
Parameter
Value Range
Default Value
Description
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
l RTN NEs support

only Not
Transparently
Transmitted.
l When BPDU is
Not
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
protocol packets. If
port-based E-Line
services (that is,
transparent E-Line
services with the
encapsulation
attribute being
NULL) are
configured,
protocol packets
are forwarded as
service packets. In
this case, protocol
packets are
generally mapped
to BE queues, and
will be discarded
when congestion
occurs.
MTU (bytes)
This parameter cannot

be set here.
Service Tag Role
OptiX RTN 900 does

not support this
parameter.
Issue 01 (2016-04-30)

1348

Configuration Guide
Parameter
Value Range
Default Value
Description
Source Port
l Before setting this

parameter, ensure
that Port Mode is
Layer 2 or Layer
Mix.
l The value of this
parameter cannot
be the same as the
value of sink port.
l The value of this
parameter cannot
be used for the ELAN port.
l This parameter is
set according to the
planning
information.
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 If this parameter is
set to null, all the
services at the
source port are
used as the service
source.
not set to null, only
the service that
contains the VLAN
ID at the source
port can be used as
the service source.
Issue 01 (2016-04-30)

1349

Configuration Guide
Parameter
Value Range
Default Value
Description
Sink Port

parameter, ensure
that Port Mode is
Layer 2 or Layer
Mix.
l The value of this
parameter cannot
be the same as the
value of Source
Port.
l The value of this
parameter cannot
l This parameter is
planning
information.
Sink 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.
services at the sink
port are used as the
service sink.
the service that
contains the VLAN
ID at the sink port
can be used as the
service sink.
Issue 01 (2016-04-30)

1350

Configuration Guide
Table B-4 Service direction of UNI-NNI (carried by PWs)

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294
This parameter
E-Line service.
Service Name
This parameter
the E-Line service.
Direction
UNI-UNI
UNI-UNI
l This parameter
specifies the
direction of the ELine service.
UNI-NNI
NNI-NNI

to UNI-NNI.
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
Transparently
Transmitted
l RTN NEs support

only Not
Transparently
Transmitted.
l When BPDU is
Not
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
protocol packets.
If port-based ELine services (that
is, transparent ELine services with
the encapsulation
attribute being
NULL) are
configured,
protocol packets
are forwarded as
service packets. In
this case, protocol
packets are
generally mapped
to BE queues, and
will be discarded
when congestion
occurs.
Issue 01 (2016-04-30)

1351

Configuration Guide
Parameter
Value Range
Default Value
Description
MTU (bytes)
This parameter cannot

be set here.
Service Tag Role
User
User
This parameter needs

to be specified only
when Direction is
UNI-NNI
and Bearer Type is
PW.

parameter, ensure
that Port Mode is
Layer 2 or Layer
Mix.
Service
Source Port
l The value of this

parameter cannot
be the same as the
value of sink port.
l The value of this
parameter cannot
l This parameter is
set according to
the planning
information.
Issue 01 (2016-04-30)

1352

Configuration Guide
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.
services at the
source port are
used as the service
source.
not set to null,
only the service
that contains the
VLAN ID at the
source port can be
used as the service
source.
PRI
OptiX RTN 900 does

not support this
parameter.
Bearer Type
QinQ Link
PW
For UNI-NNI ETH

PWE3 services, the
parameter value is
always PW.
PW
Issue 01 (2016-04-30)

1353

Configuration Guide
Parameter
Value Range
Default Value
Description
Protection Type
No Protection
No Protection
set to PW APS,
working and
protection PWs
need to be
configured.
PW APS
Slave Protection Pair
set 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-5 Service direction of UNI-NNI (carried by QinQ links)

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294
This parameter
specifies the ID of
the E-Line service.
Service Name
This parameter
the E-Line service.
Direction
UNI-UNI
UNI-UNI
l This parameter
specifies the
direction of the
E-Line service.
UNI-NNI
NNI-NNI

to UNI-NNI.
Issue 01 (2016-04-30)

1354

Configuration Guide
Parameter
Value Range
Default Value
Description
BPDU
Not Transparently
Transmitted
Not Transparently
Transmitted
l RTN NEs support

only Not
Transparently
Transmitted.
Transparently
Transmitted
l When BPDU is
Not
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
protocol packets.
If port-based ELine services
(that is,
transparent ELine services
with the
encapsulation
attribute being
NULL) are
configured,
protocol packets
are forwarded as
service packets.
In this case,
protocol packets
are generally
mapped to BE
queues, and will
be discarded
when congestion
occurs.
.
MTU (bytes)
This parameter
cannot be set here.
Service Tag Role
OptiX RTN 900 does

not support this
parameter.
Issue 01 (2016-04-30)

1355

Configuration Guide
Parameter
Value Range
Default Value
Description
Source Port
l Before setting
this parameter,
ensure that Port
Mode is Layer 2
or Layer Mix.
l The value of this
parameter cannot
be the same as
the value of sink
port.
l The value of this
parameter cannot
l This parameter is
set according to
the planning
information.
Issue 01 (2016-04-30)

1356

Configuration Guide
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 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 contains the
VLAN ID at the
source port can
be used as the
service source.
PRI
OptiX RTN 900 does

not support this
parameter.
Bearer Type
QinQ Link
PW
For NNI-NNI QinQ

services, the
parameter 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 01 (2016-04-30)

1357

Configuration Guide
Table B-6 Service direction of NNI-NNI

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
BPDU
Not Transparently
Transmitted
l Set this parameter to

NNI-NNI.
Not Transparently
Transmitted
Transparently
Transmitted
l RTN NEs support

only Not
Transparently
Transmitted.
l When BPDU is Not
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting protocol
packets. If port-based
E-Line services (that
is, transparent E-Line
services with the
encapsulation
attribute being
NULL) are
configured, protocol
packets are forwarded
as service packets. In
this case, protocol
packets are generally
mapped to BE queues,
and will be discarded
when congestion
occurs.
.
MTU (bytes)
This parameter cannot be

set here.
Service Tag Role
OptiX RTN 900 does not

support this parameter.
Issue 01 (2016-04-30)

1358

Configuration Guide
Parameter
Value Range
Default Value
Description
PRI

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

QinQ Link ID 2
l Selects the QinQ link

ID of the second
QinQ link.
l The QinQ link ID is
QinQ Link ID
Selects or specifies the

ID of a QinQ link. You
can create a QinQ link or
select an existing QinQ
link.
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
l If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters
of working and protection PWs need to be configured. This section considers the parameters of the
working PW as an example.
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.
Issue 01 (2016-04-30)

1359

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
PW Direction
Bidirectional
Bidirectional
Displays the direction

of the PW.
PW Encapsulation Type
MPLS
MPLS
Displays the
encapsulation type of
the packets on the PW.
PW Incoming Label
16 to 1048575
Specifies the PW
Ingress label.
PW Outgoing Label
16 to 1048575
Specifies the PW
Egress label.
Tunnel selection mode
Displays the method to

select tunnels.
Tunnel Type
MPLS
MPLS
Displays the type of the

tunnel that carries the
PW.
Tunnel
A tunnel needs to be
selected. If no tunnel is
available, creation of a
PW will fail.
Egress Tunnel
For a bidirectional
tunnel, the system will
configure the egress
tunnel automatically.
Issue 01 (2016-04-30)

1360

Configuration Guide
Parameter
Value Range
Default Value
Description
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
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
Specifies whether the

bandwidth limit function
is enabled.
l This function limits
the bandwidth of one
or more PWs in an
MPLS tunnel.
l An ETH PWE3
service corresponds to
a PW. Therefore, this
function can also limit
the bandwidth of ETH
PWE3 services in an
MPLS tunnel.
Policy

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.
Issue 01 (2016-04-30)

1361

Configuration Guide
Parameter
Value Range
Default Value
Description
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
Not in use
Not in use
Specifies whether a
product uses control
words when
encapsulating ETH
PWE3 packets.
Used First
NOTE
For information about
whether a product uses
control words when
encapsulating ETH PWE3
packets, see the Feature
Description.
Control Channel Type
None
Alert Label
Alert Label
l Specifies the mode of

PW continuity check.
l None indicates that
VCCV is not used.
CW
l Alert Label indicates

VCCV packets in
Alert Label
encapsulation mode.
l CW: indicates that
VCCV packets
encapsulated based on
the control word are
used.
Issue 01 (2016-04-30)

1362

Configuration Guide
Parameter
Value Range
Default Value
Description
VCCV Verification
Mode
Ping
Ping
l Specifies the VCCV

verification mode.
The VCCV
verification is used for
None
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

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.
Protection Group ID

group ID.
Issue 01 (2016-04-30)

1363

Configuration Guide
Parameter
Value Range
Default Value
Description
Enabling Status
Disabled
Disabled

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 RTN 900 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 RTN 900 supports
dual-ended switching.
Revertive Mode
Non-revertive
Revertive
Revertive
l This parameter
switch services back
to the original
working PW after it
recovers.
l The value Revertive
indicates that services
are switched to the
original working PW
and the value Nonrevertive indicates
that services are not
switched to the
original working PW.
is recommended.
Issue 01 (2016-04-30)

1364

Configuration Guide
Parameter
Value Range
Default Value
Description
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
Revertive Mode is
Revertive.
l The default value is
recommended.
Switchover Delay Time

(100 ms)
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 holdoff 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.
Issue 01 (2016-04-30)

1365

Configuration Guide
Parameter
Value Range
Default Value
Description
OAM Status
Displays the enabling

status of PW OAM.
Detection Mode
Auto-Sensing
Auto-Sensing
l Specifies the detection

mode of OAM
packets.
Manual
l Manual: The CC
packets are sent at the
interval specified by
the user.
l Auto-Sensing: The
CC packets are sent at
the interval of
receiving PW OAM
packets.
l If Detection Mode is
set to Manual, you
need to set the PW
OAM detection
packets to be received
and transmitted.
l The value AutoSensing is
recommended.
Issue 01 (2016-04-30)

1366

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Packet Type
CV
CV
l CV: The detection

packets are sent at a
fixed interval.
FFD
l FFD: The detection

the user.
set to Auto-Sensing,
this parameter
specifies the PW
OAM detection
packets to be
transmitted.
set to Manual, this
parameter specifies
the PW OAM
detection packets to
be received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC 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.
Transmitted PW ID
Specifies the PW ID to be
received.
Issue 01 (2016-04-30)

1367

Configuration Guide
Protection Group Parameters (Slave Protection Pair)

NOTE
to Slave Protection Pair.
Parameter
Value Range
Default Value
Description
Protection Mode

mode.
Protection Group ID

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.
B.6.1.2 Parameter Description: E-Line Service_Creation(Web LCT)

This topic describes the interface parameters that are used for creating an Ethernet line (ELine) service.
Navigation Path
1.
2.
Click Create.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Table B-7 Service direction of UNI-UNI
Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

service.
Service Name

service.
Issue 01 (2016-04-30)

1368

Configuration Guide
Parameter
Value Range
Default Value
Description
Direction
UNI-UNI
UNI-UNI
l This parameter
UNI-NNI
NNI-NNI
BPDU
Not Transparent

UNI-UNI.
Not Transparent
Transparent
l RTN NEs support

only Not
Transparently
Transmitted.
l When BPDU is Not
Transparently
Transmitted, no
special channel is
established for
transparently
services with the
encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
MTU (bytes)

set here.
Service Tag Role
This parameter is not

supported when
Direction is UNI-UNI.
Issue 01 (2016-04-30)

1369

Configuration Guide
Parameter
Value Range
Default Value
Description
Source Port

parameter, ensure that
Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
the same as the value
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the
Source VLAN ID
1 to 4094

set to null, a number,
or several numbers.
When setting this
parameter to several
numbers, use the
comma (,) to separate
the discrete numbers,
or use the endash (-)
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
indicate 1, 3, 4, 5, and
6.
to null, all the
services at the source
service source.
the service that
contains the VLAN
ID at the source port
can be used as the
service source.
Issue 01 (2016-04-30)

1370

Configuration Guide
Parameter
Value Range
Default Value
Description
Sink Interface

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of Source Port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the
Sink VLAN ID
1 to 4094

or several numbers.
When setting this
numbers, use the
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, all the
services at the sink
service sink.
the service that
contains the VLAN
ID at the sink port can
be used as the service
sink.
Issue 01 (2016-04-30)

1371

Configuration Guide
Table B-8 Service direction of UNI-NNI (carried by PWs)

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 Transparent

UNI-NNI.
Not Transparent
Transparent
l RTN NEs support

only Not
Transparently
Transmitted.
l When BPDU is Not
Transparently
Transmitted, no
special channel is
established for
transparently
services with the
encapsulation
attribute being
NULL) are
this case, protocol
mapped to BE
queues, and will be
discarded when
congestion occurs.
MTU (bytes)

set here.
Service Tag Role
User
User
This parameter needs to

be specified only when
Direction is UNI-NNI
and Bearer Type is PW.
Service
Issue 01 (2016-04-30)

1372

Configuration Guide
Parameter
Value Range
Default Value
Description
Source Port

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the
Source VLANs
1 to 4094

or several numbers.
When setting this
numbers, use the
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, all the
service source.
the service that
contains the VLAN
can be used as the
service source.
Pri
Issue 01 (2016-04-30)


1373

Configuration Guide
Parameter
Value Range
Default Value
Description
Bearer Type
QinQ Link
PW
For UNI-NNI ETH

PWE3 services, the
parameter value is
always PW.
No Protection

to PW APS, working
and protection PWs
need to be
configured.
PW
Protection Type
No Protection
PW APS

to Slave Protection
Pair, you need to
bind the slave PW
with the master PW
APS protection
group. The switching
of the master PW
triggers the switching
of the slave PW APS
protection group
simultaneously.
Table B-9 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
Issue 01 (2016-04-30)


UNI-NNI.
1374

Configuration Guide
Parameter
Value Range
Default Value
Description
BPDU
Not Transparent
Not Transparent
l RTN NEs support

only Not
Transparently
Transmitted.
Transparent
l When BPDU is Not

Transparently
Transmitted, no
special channel is
established for
transparently
services with the
encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
MTU (bytes)

set here.
Service Tag Role

supported when
Direction is UNI-NNI
and Bearer Type is
QinQ Link.
Issue 01 (2016-04-30)

1375

Configuration Guide
Parameter
Value Range
Default Value
Description
Source Port

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the
Source VLANs
1 to 4094

or several numbers.
When setting this
numbers, use the
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, all the
service source.
the service that
contains the VLAN
can be used as the
service source.
Pri
Issue 01 (2016-04-30)


1376

Configuration Guide
Parameter
Value Range
Default Value
Description
Bearer Type
QinQ Link
PW
For NNI-NNI QinQ

services, the parameter
value is always QinQ
Link.
PW
Table B-10 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
Issue 01 (2016-04-30)


NNI-NNI.
1377

Configuration Guide
Parameter
Value Range
Default Value
Description
BPDU
Not Transparent
Not Transparent
l RTN NEs support

only Not
Transparently
Transmitted.
Transparent
l When BPDU is Not

Transparently
Transmitted, no
special channel is
established for
transparently
services with the
encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
MTU (bytes)

set here.
Service Tag Role

supported when
Direction is NNI-NNI.
PRI

Bearer Type
QinQ Link
QinQ Link

Parameters for Port Attributes

Parameter
Value Range
Default Value
Description
Port Name

the UNI port.
Issue 01 (2016-04-30)

1378

Configuration Guide
Parameter
Value Range
Default Value
Description
Enable Port
Enabled
l This parameter
displays or specifies
whether the port is
enabled.
Disabled
l Ethernet services can

be received,
processed, and
forwarded normally
only if Port Enable is
set to Enabled.
l Port Enable is
already set in
Ethernet Interface.
Port Mode
Layer 2
Layer 3

mode of an Ethernet
port.
to Layer 2, the port
can be used to access
Ethernet services
from the user
equipment or to carry
Ethernet services that
exclusively occupy
the port.
is set to Layer 3,
Ethernet services over
the port can be carried
by PWs.
Issue 01 (2016-04-30)

1379

Configuration Guide
Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
the method of the port
to process the
received packets.
802.1Q
QinQ
l If you set this

parameter to Null, the
port transparently
packets.
l If you set this
parameter to 802.1Q,
the port identifies the
packets that comply
with the IEEE 802.1q
standard.
l If you set this
parameter to QinQ,
packets that comply
with the IEEE
802.1ad standard.
Issue 01 (2016-04-30)

1380

Configuration Guide
Parameter
Value Range
Default Value
Description
Working Mode
Auto-Negotiation

different types
support different
working modes.
10M Half-Duplex
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
1000M Full-Duplex

the working mode of
local side to AutoNegotiation.
mode, set the working
mode of the
equipment on the
local side to 10M
Full-Duplex, 100M
Full-Duplex, or
1000M Full-Duplex
mode of the
equipment on the
local side to 10M
Half-Duplex, 100M
Half-Duplex, or
Auto-Negotiation
l The GE optical
interface supports the
1000M full-duplex
mode only.
Issue 01 (2016-04-30)

1381

Configuration Guide
Parameter
Value Range
Default Value
Description
Tag
Tag Aware
Tag Aware

services are frames
with the VLAN tag
TAG to Tag Aware.
Access
Hybrid

services are frames
without the VLAN
tag (untagged
frames), set TAG to
Access.
l If the accessed
services contain
tagged frames and
TAG to Hybrid.
Specify IP Address
Unspecified
Manually
l Displays or selects the

method to configure
IP addresses of ports.
l The value
do not need to be
configured for a port.
address of a port can
be manually
configured.
l This parameter is
available when Port
Mode is Layer 3.
IP Address
the IP address of the
port.
l This parameter is
available when
Manually.
IP Mask
the subnet mask of the
port.
l This parameter is
available when
Manually.
Issue 01 (2016-04-30)

1382

Configuration Guide
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
Parameter
Value Range
Default Value
Description
PW ID

PW that carries services.
PW Signaling Type
Static
Static

need to be manually
assigned.
PW Type
Ethernet
Ethernet

the PW.
l PW Type indicates
whether P-TAG is
added to Ethernet
frames that are
encapsulated for
transmission on PWs.
If it is not required to
add VLAN IDs, set
this parameter to
Ethernet. If it is
required to add
VLAN IDs, set this
parameter to Ethernet
Tagged Mode and
then set Request
VLAN in the
Advanced Attributes
tab.
PW Direction
Bidirectional
Bidirectional
Displays the direction of

the PW.
MPLS
MPLS
Displays the
encapsulation type of the
packets on the PW.
PW Incoming Label
16 to 1048575
Specifies the PW Ingress

label.
PW Outgoing Label
16 to 1048575
Specifies the PW Egress

label.
Issue 01 (2016-04-30)

1383

Configuration Guide
Parameter
Value Range
Default Value
Description
Tunnel Type
MPLS
MPLS

PW.
Tunnel
New
New
created or selected. If no
tunnel is available,
creation of a PW will fail.
New
For a bidirectional tunnel,

the system will configure
the egress tunnel
automatically.
Specifies the LSR ID of

the PW at the remote end.
If an existing tunnel is
selected, the LSR ID will
be automatically
assigned.
Use existing PWs
Egress Tunnel
New
Use existing resource
Peer LSR ID
Parameters of Advanced Attributes (PW)

Parameter
Value Range
Default Value
Description
Control Word
Not in use
Not in use
Specifies whether a
words when
encapsulating ETH
PWE3 packets.
Used First
NOTE
control words when
Description.
Issue 01 (2016-04-30)

1384

Configuration Guide
Parameter
Value Range
Default Value
Description
None
Alert Label

Alert Label

VCCV is not used.
CW

VCCV packets in
Alert Label
encapsulation mode.
VCCV packets
used.
VCCV Verification
Mode
Ping
Ping
None

verification mode.
The VCCV
this parameter to
None.
Request VLAN

when PW Type is
Ethernet Tagged
Mode.
do not carry any
VLAN IDs, the PW
the packets as
of this parameter.
QoS Parameters (PWs)

Parameter
Value Range
Default Value
Description
PW ID
Displays the ID of a PW.
Direction

a tunnel.
PW Type
Displays the type of a

PW.
Issue 01 (2016-04-30)

1385

Configuration Guide
Parameter
Value Range
Default Value
Description
Bandwidth Limit

is enabled.
or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.
Policy

CIR (kbit/s)

a PW.
CBS (byte)

PIR (kbit/s)
Specifies the peak

a PW.
PBS (byte)

size (PBS) of a PW.
EXP

LSP Mode
Pipe
Pipe

does not update the
the packets.
Issue 01 (2016-04-30)

1386

Configuration Guide

NOTE
to 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
protection mode.
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
NOTE
Issue 01 (2016-04-30)

1387

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Non-revertive
Revertive
l This parameter
to the original
working PW after it
recovers.
Revertive

are switched to the
original working PW
switched to the
is recommended.
Time (min)
1 to 12
l Specifies the WTR

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.
Issue 01 (2016-04-30)

1388

Configuration Guide
Parameter
Value Range
Default Value
Description

(100 ms)
0 to 100

group.
0, the protection
switching once it
detects faults, but
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 01 (2016-04-30)

1389

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing

mode of OAM
packets.
Manual
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 01 (2016-04-30)

1390

Configuration Guide
Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

the user.
this parameter
specifies the PW
OAM detection
packets to be
transmitted.
set to Manual, this
parameter specifies
the PW OAM
be received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
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.

be received.
Transmitted PW ID
received.
Issue 01 (2016-04-30)

1391

Configuration Guide

NOTE
Parameter
Value Range
Default Value
Description
Protection Mode

mode.
Protection Group ID

PW APS protection
group triggers the
PW APS protection
Working PW ID

protection pair.
Protection PW ID

B.6.1.3 Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet

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.
Issue 01 (2016-04-30)

1392

Configuration Guide
Parameter
Value Range
Default Value
Description
Sink Node

the sink node.
Service Tag Role

the service tag role.
MTU (byte)

queried here.
BPDU
Not Transparently
Transmitted
l RTN NEs support

only Not
Transparently
Transmitted.
Transparently
Transmitted
l When BPDU is Not

Transparently
Transmitted, no
special channel is
established for
transparently
services with the
encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
Deployment Status

whether E-Line service is
deployed.
Parameters Associated with UNI Ports

Parameter
Value Range
Default Value
Description
Port

the UNI port.
Issue 01 (2016-04-30)

1393

Configuration Guide
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
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
l This parameter is
valid only when
Direction is set to
UNI-UNI or UNINNI in the process of
creating an E-Line
service.
to null, all the
services of the UNI
work as the service
source or service sink.
the 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 01 (2016-04-30)

Displays the priority of

each UNI port.
1394

Configuration Guide
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 900 uses
static PWs only.
PW Type

the configured PW type.
PW 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
Displays whether the

ETH PWE3 service uses
Control Word.

the control channel type.
Issue 01 (2016-04-30)

1395

Configuration Guide
Parameter
Value Range
Default Value
Description
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
The OptiX RTN 900 does

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.
l This parameter is
valid only when
Direction is set to
creating an E-Line
service.
Issue 01 (2016-04-30)

1396

Configuration Guide
Parameter
Value Range
Default Value
Description
Port
l This parameter
indicates the NNI
port.
l This parameter is
valid only when
Direction is set to
creating an E-Line
service.
S-VLAN ID
l This parameter
indicates or specifies
the VLAN ID of the
NNI port.
l This parameter is
valid only when
Direction is set to
UNI-NNI or NNINNI in the process of
creating an 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 01 (2016-04-30)

1397

Configuration Guide
Parameter
Value Range
Default Value
Description
Bandwidth Limit

or specifies whether the
is enabled for a PW to
prevent network
congestion.
l Regarding
transmission
channels, this
function can be used
to limit the bandwidth
of one or more PWs
in an MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.
Policy

not support this
parameter.
CIR (Kbit/s)

or specifies the
committed information
rate (CIR) for a PW.
CBS (kbyte)

or specifies the
committed burst size
(CBS) for a PW.
PIR (kbit/s)

or specifies the peak
information rate (PIR) for
a PW.
PBS (kbyte)
Issue 01 (2016-04-30)


burst size (PBS) for a
PW.
1398

Configuration Guide
Parameter
Value Range
Default Value
Description
EXP

not support this
parameter.
LSP Mode
Pipe
Pipe

does not update the
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 01 (2016-04-30)

1399

Configuration Guide
Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
indicates the
the port.
802.1Q
QinQ
l This parameter is
valid only when
Direction is set to
creating an E-Line
service.
to Null, the port
transparently
packets.
to 802.1Q, the port
IEEE 802.1Q
standard.
to QinQ, the port
IEEE 802.1 QinQ
standard.
l This parameter is
preset in General
Attributes of
Ethernet Interface.
TAG
Tag Aware
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 01 (2016-04-30)

1400

Configuration Guide
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 900
supports 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
is recommended.
Issue 01 (2016-04-30)

1401

Configuration Guide
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 (100 ms)
0 to 100
the hold-off time of
0, the protection
switching once it
detects faults, but
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 01 (2016-04-30)

1402

Configuration Guide

NOTE
The following parameters are available only after the slave protection pair is configured.
Parameter
Value Range
Default Value
Description
Protection Group ID

PW APS protection
group triggers the
PW APS protection
Working PW ID

protection pair.
Protection PW ID

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.4 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
Source Interface Type
V-UNI
V-UNI

the network attribute of
the source interface.
Issue 01 (2016-04-30)

1403

Configuration Guide
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.
B.6.1.5 Parameter Description: E-LAN Service_Creation (U2000)

This topic describes the parameters for creating an Ethernet local area network (E-LAN)
service.
Navigation Path
1.
In the NE Explorer, select the NE from the Object Tree. Choose Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
2.
Click New.
Issue 01 (2016-04-30)

1404

Configuration Guide

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294
l This parameter
E-LAN service.
l OptiX RTN 900
supports simultaneous
creation of an E-LAN
service only.
Service Name
Issue 01 (2016-04-30)


the name of the E-LAN
service.
1405

Configuration Guide
Parameter
Value Range
Default Value
Description
BPDU
l In the case of an ELAN service, this

parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l If Spanning Tree
Protocol (STP) is
configured, Not
Transparently
Transmitted
indicates that BPDU
packets are
considered as protocol
packets used for
calculating the STP
topology.
l If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
packets. If IEEE
802.1d-bridge
services (that is,
transparent bridgebased services with
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
Issue 01 (2016-04-30)

1406

Configuration Guide
Parameter
Value Range
Default Value
Description
Tag Type
C-Aware
C-Aware
l C-Aware 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 CAware.
S-Aware
Tag-Transparent
l S-Aware indicates
learnt according to STag (the VLAN tag at
the carrier service
layer). To create the
802.1ad bridge, set
this parameter to SAware.
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 01 (2016-04-30)

1407

Configuration Guide
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.
an 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

this parameter.
Issue 01 (2016-04-30)

1408

Configuration Guide
Parameter
Value Range
Default Value
Description
Protection Mode
No Protection
No Protection

to PW APS, working
and protection PWs
must be configured. If
Slave Protection
Pair, ensure that a
PW APS protection
group to which the
slave protection pair
is bound has been
configured.
PW APS
l When the working

PW in a PW APS
protection group is
faulty, protection
switching occurs on
the PW APS
protection group as
well as on all its slave
protection pairs.
Parameters for UNIs

Parameter
Value Range
Default Value
Description
Port

the UNI port.
SVLAN/SVLANs
1 to 4094
l This parameter
specifies the S-VLAN
ID of the UNI port.
l This parameter is
valid only when Tag
Type is set to SAware.
according to the
Issue 01 (2016-04-30)

1409

Configuration Guide
Parameter
Value Range
Default Value
Description
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
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, all the
services of the UNI
work as the service
source or service sink.
the 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.
VLAN Filtering Table
Issue 01 (2016-04-30)
1 to 4094

If a virtual private line

service (VPLS) is
mounted to a UNI port
configured for PORTbased flows, this
parameter needs to be
configured. Moreover, set
Tag Type to C-Aware or
S-Aware.
1410

Configuration Guide
Parameters of NNIs (Port)

Parameter
Value Range
Default Value
Description
Port
l This parameter
indicates the NNI
port.
l This parameter is
valid only when Tag
SVLANs
l This parameter
ID of the NNI port.
l This parameter is
valid only when Tag
Parameters of NNIs (PW)

NOTE
l PW parameters need to be configured for only PW-carried E-LAN services.

Parameter
Value Range
Default Value
Description
PW ID

PW that carries
services.
PW Signaling Type
Static
Static

need to be manually
assigned.
Issue 01 (2016-04-30)

1411

Configuration Guide
Parameter
Value Range
Default Value
Description
PW Type
Ethernet
Ethernet

the PW.
l PW Type indicates
whether P-TAG is
added to Ethernet
frames that are
encapsulated for
transmission on
PWs. If it is not
required to add
VLAN IDs, set this
parameter to
Ethernet. If it is
required to add
VLAN IDs, set this
parameter to
Ethernet Tagged
Mode and then set
Request VLAN in
the Advanced
Attributes tab.
PW Direction
Bidirectional
Bidirectional

of the PW.
MPLS
MPLS
Displays the
PW Incoming Label
16 to 1048575
Specifies the PW
Ingress label.
PW Outgoing Label
16 to 1048575
Specifies the PW
Egress label.

select tunnels.
Tunnel Type
MPLS
MPLS

PW.
Tunnel
PW will fail.
Egress Tunnel
For a bidirectional
tunnel, the system will
configure the egress
tunnel automatically.
Issue 01 (2016-04-30)

1412

Configuration Guide
Parameter
Value Range
Default Value
Description
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
Parameters for the Split Horizon Group

Parameter
Value Range
Default Value
Description
Split Horizon Group ID
l This parameter
indicates the ID of the
split horizon group.
l The default split
horizon group ID is 1
and cannot be set
manually.
Split Horizon Group

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 OptiX RTN 900
supports only the
division of the split
horizon group
members according to
the Ethernet physical
port.
l If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
member, the physical
port that is mounted
with the logical port is
automatically added
to the split horizon
group member.
Issue 01 (2016-04-30)

1413

Configuration Guide
B.6.1.6 Parameter Description: E-LAN Service_Creation(Web LCT)

This topic describes the parameters that are used for creating an Ethernet local area network
(E-LAN) service.
Navigation Path
1.
Ethernet Service Management > E-LAN Service from the Function Tree.
2.
Click New.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294
l This parameter
E-LAN service.
l The NE supports
simultaneous creation
of an E-LAN service
only.
Service Name
Issue 01 (2016-04-30)


service.
1414

Configuration Guide
Parameter
Value Range
Default Value
Description
BPDU

parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l If Spanning Tree
Protocol (STP) is
configured, Not
Transparently
Transmitted
indicates that BPDU
packets are
packets used for
calculating the STP
topology.
l If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
packets. If IEEE
802.1d-bridge
services (that is,
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
Issue 01 (2016-04-30)

1415

Configuration Guide
Parameter
Value Range
Default Value
Description
Tag Type
C-Aware
C-Aware
l C-Aware indicates
create the 802.1q
bridge, set this
S-Aware
Tag-Transparent
l S-Aware indicates
the carrier service
802.1ad bridge, set
l Tag-Transparent
indicates that the
packets are
transparently
according to the
Issue 01 (2016-04-30)

1416

Configuration Guide
Parameter
Value Range
Default Value
Description
Self-Learning MAC
Address
Enabled
Enabled
l This parameter
enable the MAC
function.
Disabled

an Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
an Ethernet LAN is
disabled, a static
MAC address
forwarding table is
recommended to be
configured.
Mode
IVL
SVL
l This parameter
indicates the mode
address.
VLANs share one
the bridge uses the
IVL mode, each
VLAN has an MAC
address table.
Port
Issue 01 (2016-04-30)


the port name.
1417

Configuration Guide
Parameter
Value Range
Default Value
Description
Port Type

the port type.
l When the parameter
value is UNI, the port
connected to the
bridge is a UNI port.
That is, this port
functions as the UNI
port connected to the
IEEE 802.1d bridge
or IEEE 802.1q
bridge.
value is NNI, the port
connected to the
bridge is an NNI port.
That is, this port
functions as the NNI
IEEE 802.1ad bridge.
value is UNI (PORT
+S-VLAN), a specific
S-VLAN ID is added
to all the traffic flows
that are received by
the UNI port
connected to the IEEE
802.1ad bridge.
value is UNI (PORT
+C-VLAN+SVLAN), a specific SVLAN ID is added to
all the traffic flows
that are received by
the UNI port
connected to the IEEE
802.1ad bridge and
contain the specific
C-VLAN ID.
Issue 01 (2016-04-30)

1418

Configuration Guide
Parameter
Value Range
Default Value
Description
VLAN
1 to 4094
l This parameter is
valid only when Tag
Type is set to CAware and Tag is set
to Access or Hybrid.
value is null, it
indicates that the
entire physical port is
connected to the
bridge.
l You need to set this
parameter according
to the planning
information.
Issue 01 (2016-04-30)

1419

Configuration Guide
Parameter
Value Range
Default Value
Description
C-VLAN
1 to 4094
l This parameter is
valid only when Tag
l This parameter
specifies the VLAN
ID of the UNI port.
l You may set this
parameter to null, a
number, or several
numbers. When you
several numbers, use
"," to separate these
discrete values and
use "-" to indicate
continuous numbers.
For example, "1, 3-6"
indicates numbers 1,
3, 4, 5, and 6.
value is null, the ELAN service
exclusively occupies
the corresponding
UNI port; that is, the
entire physical UNI
port is connected to
the bridge.
value is not null, a
specific S-VLAN ID
is added to only the
traffic flows that are
received by the UNI
port and contain this
VLAN ID.
Issue 01 (2016-04-30)

1420

Configuration Guide
Parameter
Value Range
Default Value
Description
S-VLAN
1 to 4094
l This parameter is
valid only when Tag
l This parameter
ID that needs to be
added to traffic flows
received by the UNI
port or the S-VLAN
ID that the NNI port
can identify.
l You need to set this
parameter according
to the planning
information.
Enable Port
l This parameter
displays whether the
port is enabled.
be received,
processed, and
forwarded normally
only if Enable Port is
set to Enabled.
l Enable Port is
already set in
Ethernet Interface.
Issue 01 (2016-04-30)

1421

Configuration Guide
Parameter
Value Range
Default Value
Description
Working Mode
Auto-Negotiation
Auto-Negotiation

different types
support different
working modes.
10M Half-Duplex
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
1000M Full-Duplex

the working mode of
mode of the
equipment on the
local side to 10M
Full-Duplex, 100M
Full-Duplex, or
1000M Full-Duplex
mode of the
equipment on the
local side to 10M
Half-Duplex, 100M
Half-Duplex, or
Auto-Negotiation
l The GE optical
1000M full-duplex
mode only.
Issue 01 (2016-04-30)

1422

Configuration Guide
Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
802.1Q
QinQ
l If you set this

port transparently
packets.
l If you set this
packets that comply
standard.
l If you set this
parameter to QinQ,
packets that comply
with the IEEE
802.1ad QinQ
standard.
Tag
Tag Aware
Tag Aware
Access
Hybrid

services are frames
with the VLAN tag
(tagged frames), this
parameter is set to
Tag Aware.
services are frames
without the VLAN
tag (untagged
frames), this
parameter is set to
Access.
l If the accessed
services contain
tagged frames and
untagged frames, this
parameter is set to
Hybrid.
Issue 01 (2016-04-30)

1423

Configuration Guide
Parameter
Value Range
Default Value
Description
Default VLAN
1 to 4094
valid only when TAG
is set to Access or
Hybrid.
actual situations.
Parameters on the Main Interface (Setting Service Parameters)

Parameter
Value Range
Default Value
Description
Split Horizon Group
Selected
Deselected

whether to create a split
horizon group.
l This parameter
displays the ID of the
Deselected
l The ID of the split

horizon group is 1 by
default and cannot be
specified manually.
Issue 01 (2016-04-30)

1424

Configuration Guide
Parameter
Value Range
Default Value
Description
Split Horizon Group

Member

logical port member
group.
l The port members
that are added to the
same split horizon
group cannot
communicate with
each other.
l The NE supports only
the division of the
split horizon group
port.
l If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
automatically added
group member.
B.6.1.7 Parameter Description: E-LAN Service(U2000)

This topic describes the parameters that are related to E-LAN services.
Navigation Path

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

the ID of the E-LAN
service.
Issue 01 (2016-04-30)

1425

Configuration Guide
Parameter
Value Range
Default Value
Description
Service Name

service.
BPDU

parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l If Spanning Tree
Protocol (STP) is
configured, Not
Transparently
Transmitted
indicates that BPDU
packets are
packets used for
calculating the STP
topology.
l If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
packets. If IEEE
802.1d-bridge
services (that is,
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
Issue 01 (2016-04-30)

1426

Configuration Guide
Parameter
Value Range
Default Value
Description
Tag Type
C-Aware
C-Aware
l C-Aware indicates
create the 802.1q
bridge, set this
S-Aware
Tag-Transparent
l S-Aware indicates
the carrier service
802.1ad bridge, set
l Tag-Transparent
indicates that the
packets are
transparently
Issue 01 (2016-04-30)

1427

Configuration Guide
Parameter
Value Range
Default Value
Description
Self-Learning MAC
Address
Enabled
Enabled
l This parameter
enable the MAC
function.
an Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
an Ethernet LAN is
disabled, a static
MAC address
forwarding table is
recommended to be
configured.

Mode
l This parameter
indicates the mode
address.
VLANs share one
the bridge uses the
IVL mode, each
VLAN has an MAC
address table.
MTU(byte)

queried here.
Service Tag Role

Deployment Status

whether E-LAN service
is deployed.
Issue 01 (2016-04-30)

1428

Configuration Guide
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.
l This parameter is
valid only when Tag
according to the
Issue 01 (2016-04-30)

1429

Configuration Guide
Parameter
Value Range
Default Value
Description
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
or use the en dash (-)
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, the E-LAN
service exclusively
uses the
corresponding UNI
physical port. That is,
the entire port is
mounted to the
bridge.
to a non-null value,
only the
corresponding UNI
port whose service
packets contain this
VLAN ID works as
the logical port and is
mounted to the
bridge.
Issue 01 (2016-04-30)

1430

Configuration Guide
Parameters for NNIs (Port)

Parameter
Value Range
Default Value
Description
Port
l This parameter
indicates the NNI
port.
l This parameter is
valid only when Tag
SVLANs
l This parameter
ID of the UNI port.
l This parameter is
valid only when Tag
or several numbers.
When setting this
numbers, use the
or use the en dash (-)
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
NNI Parameters (PW)

Parameter
Value Range
Default Value
Description
PW ID

the PW ID.
Working Status

the working status of a
PW.
PW Status

Issue 01 (2016-04-30)

1431

Configuration Guide
Parameter
Value Range
Default Value
Description
PW Signaling Type

the PW signaling type.
NOTE
static PWs only.
PW Type

the configured PW type.
PW Direction


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

ETH PWE3 service uses
Control Word.

VCCV Verification
Mode

the VCCV mode.

local end.
Remote Operating
Status

Issue 01 (2016-04-30)

1432

Configuration Guide
Parameter
Value Range
Default Value
Description
Overall Operating
Status

the comprehensive
Request VLAN

the request VLAN.
Deployment Status

the deployment status.
Tunnel for Auto

Selection

selection policy.
TPID

not support request
VLAN TPID of the PW
level.
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 01 (2016-04-30)

1433

Configuration Guide
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 does not need
to be aged
automatically.
Egress Interface
l This parameter
specifies the Ethernet
port that corresponds
to the MAC address.
according to the
Issue 01 (2016-04-30)

1434

Configuration Guide
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 selflearning MAC
address entries are
valid for all VLANs.
l If MAC Address
to IVL, the preset
self-learning 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 selflearning MAC
address can be aged.
Egress Interface
l This parameter
to the MAC address.
according to the
Issue 01 (2016-04-30)

1435

Configuration Guide
Parameters Associated with MAC Address Learning Parameters

Parameter
Value Range
Default Value
Description
Aging Ability
Enabled
Enabled
OptiX RTN 900 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.
Specified Address Table
Capacity
0 to 65534
512
l This parameter is
supported only by the
OptiX RTN
950A/905/RTN910A
and the OptiX RTN
950 that houses
CSHU/CSHUA
boards.
l This parameter
specifies the MAC
address forwarding
table capacity for ELAN services.
Address Detection
Upper Threshold (%)
Issue 01 (2016-04-30)
80 to 100
95

l This parameter is
OptiX RTN 950A/
905/910A and the
OptiX RTN 950 that
houses CSHU/
CSHUA boards.
l When the MAC
address forwarding
table capacity for ELAN services is
greater than Address
Detection Upper
1436

Configuration Guide
Parameter
Value Range
Default Value
Address Detection
Lower Threshold (%)
60 to 100
90
Description
Threshold (%), an
FDBSIZEALM_ELA
N alarm is reported.
When the MAC
address forwarding
table capacity for ELAN services is less
than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELA
N alarm automatically
clears.
Parameters for Disabled MAC Addresses

Parameter
Value Range
Default Value
Description
VLAN ID

ID of the service. A
disabled MAC address is
valid for the VLAN
whose VLAN ID is equal
to the preset VLAN ID.
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.
Issue 01 (2016-04-30)

1437

Configuration Guide

Parameter
Value Range
Default Value
Description
l This parameter
l The default split
and cannot be set
manually.
Split Horizon Group

Member

logical port member
group.
l The port members
that are added to
different split horizon
groups cannot
communicate with
each other.
l OptiX RTN 900
supports only the
horizon group
port.
l If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
automatically added
group member.
Parameters for Unknown Frame Processing

Parameter
Value Range
Default Value
Description
Frame Type
Unicast

the type of the received
unknown frame.
Multicast
Issue 01 (2016-04-30)

1438

Configuration Guide
Parameter
Value Range
Default Value
Description
Handing Mode
Discard
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.
Broadcast
B.6.1.8 Parameter Description: E-LAN Service(Web LCT)

This topic describes the parameters that are related to E-LAN services.
Navigation Path

Parameter
Value Range
Default Value
Description
Service ID
1 to 4294967294

the ID of the E-LAN
service.
Service Name

service.
Issue 01 (2016-04-30)

1439

Configuration Guide
Parameter
Value Range
Default Value
Description
BPDU

parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
l If Spanning Tree
Protocol (STP) is
configured, Not
Transparently
Transmitted
indicates that BPDU
packets are
packets used for
calculating the STP
topology.
l If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
packets. If IEEE
802.1d-bridge
services (that is,
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.
Issue 01 (2016-04-30)

1440

Configuration Guide
Parameter
Value Range
Default Value
Description
Tag Type
C-Aware
C-Aware
l C-Aware indicates
create the 802.1q
bridge, set this
S-Aware
Tag-Transparent
l S-Aware indicates
the carrier service
802.1ad bridge, set
l Tag-Transparent
indicates that the
packets are
transparently
Issue 01 (2016-04-30)

1441

Configuration Guide
Parameter
Value Range
Default Value
Description
Self-Learning MAC
Address
Enabled
Enabled
l This parameter
enable the MAC
function.
an Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
an Ethernet LAN is
disabled, a static
MAC address
forwarding table is
recommended to be
configured.

Mode
l This parameter
indicates the mode
address.
VLANs share one
the bridge uses the
IVL mode, each
VLAN has an MAC
address table.
Port Parameters
Parameter
Value Range
Default Value
Description
Port

the port name.
Issue 01 (2016-04-30)

1442

Configuration Guide
Parameter
Value Range
Default Value
Description
Port Type

the port type.
value is UNI, the port
connected to the
bridge is a UNI port.
That is, this port
functions as the UNI
IEEE 802.1d bridge
or IEEE 802.1q
bridge.
l If the parameter value
is NNI, the port
connected to the
bridge is an NNI port.
That is, this port
functions as the NNI
is UNI (PORT+SVLAN), a specified
S-VLAN ID is added
to all the traffic flows
received by the UNI
is UNI (PORT+CVLAN+S-VLAN), a
specific S-VLAN ID
is added to all the
traffic flows that are
received by the UNI
IEEE 802.1ad bridge
and contain the
specific C-VLAN ID.
VLAN

the VLAN ID.
C-VLAN

the C-VLAN ID.
S-VLAN

the S-VLAN ID.
Issue 01 (2016-04-30)

1443

Configuration Guide
Parameter
Value Range
Default Value
Description
Enable Port
l This parameter
displays whether the
port is enabled.
be received,
processed, and
forwarded normally
only if Enable Port is
set to Enabled.
l Enable Port is
already set in
Ethernet Interface.
Issue 01 (2016-04-30)

1444

Configuration Guide
Parameter
Value Range
Default Value
Description
Working Mode
Auto-Negotiation
Auto-Negotiation

different types
support different
working modes.
10M Half-Duplex
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
1000M Full-Duplex

the working mode of
mode of the
equipment on the
local side to 10M
Full-Duplex, 100M
Full-Duplex, or
1000M Full-Duplex
mode of the
equipment on the
local side to 10M
Half-Duplex, 100M
Half-Duplex, or
Auto-Negotiation
l The GE optical
1000M full-duplex
mode only.
Issue 01 (2016-04-30)

1445

Configuration Guide
Parameter
Value Range
Default Value
Description
Encapsulation Type
Null
l This parameter
802.1Q
QinQ
l If you set this

port transparently
packets.
l If you set this
packets that comply
standard.
l If you set this
parameter to QinQ,
packets that comply
with the IEEE
802.1ad QinQ
standard.
Tag
Tag Aware
Tag Aware
Access
Hybrid

services are frames
with the VLAN tag
this parameter to "Tag
Aware".
services are frames
without the VLAN
tag (untagged
frames), set this
parameter to
"Access".
l If the accessed
services contain
tagged frames and
this parameter to
"Hybrid".
Issue 01 (2016-04-30)

1446

Configuration Guide
Parameter
Value Range
Default Value
Description
Default VLAN ID
1 to 4094
valid only when Tag
is set to Access or
Hybrid.
actual situations.
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
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 01 (2016-04-30)

1447

Configuration Guide
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 does not need
to be aged
automatically.
Egress Interface
l This parameter
to the MAC address.
according to the
Issue 01 (2016-04-30)

1448

Configuration Guide
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 selflearning MAC
address entries are
valid for all VLANs.
l If MAC Address
to IVL, the preset
self-learning 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 selflearning MAC
address can be aged.
Egress Interface
l This parameter
to the MAC address.
according to the
Issue 01 (2016-04-30)

1449

Configuration Guide
Parameters Associated with MAC Address Learning

Parameter
Value Range
Default Value
Description
Aging Ability
Enabled
Enabled
OptiX RTN 900 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

period, that is, if no new
packet from this MAC
address is received to
enable the re-learning of
this MAC address, this
routing entry is
This mechanism is called
aging, and this period is
called aging time. The
aging time of a MAC
address table is 5 minutes
by default.
Specified Address Table
Capacity
0 to 65534
512
l This parameter is
OptiX RTN
950A/905/RTN910A
and the OptiX RTN
950 that houses
CSHU/CSHUA
boards.
l This parameter
specifies the MAC
address forwarding
table capacity for ELAN services.
Address Detection
Upper Threshold (%)
Issue 01 (2016-04-30)
80 to 100
95

l This parameter is
OptiX RTN 950A and
the OptiX RTN 950
that houses CSHU/
CSHUA boards.
l When the MAC
address forwarding
table capacity for ELAN services is
greater than Address
Detection Upper
Threshold (%), an
1450

Configuration Guide
Parameter
Value Range
Default Value
Address Detection
Lower Threshold (%)
60 to 100
90
Description
FDBSIZEALM_ELA
N alarm is reported.
When the MAC
address forwarding
table capacity for ELAN services is less
than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELA
N alarm automatically
clears.
Parameters for Disabled MAC Addresses

Parameter
Value Range
Default Value
Description
VLAN ID

ID of the service. A
disabled MAC address is
valid for the VLAN
whose VLAN ID is equal
to the preset VLAN ID.
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.
Issue 01 (2016-04-30)

1451

Configuration Guide

Parameter
Value Range
Default Value
Description
l This parameter
l The default split
and cannot be set
manually.
Split Horizon Group

Member

logical port member
group.
l The port members
that are added to
different split horizon
groups cannot
communicate with
each other.
l The supports only the
horizon group
port.
l If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
automatically added
group member.
Parameters for Unknown Frame Processing

Parameter
Value Range
Default Value
Description
Frame Type
Unicast

the type of the received
unknown frame.
Multicast
Issue 01 (2016-04-30)

1452

Configuration Guide
Parameter
Value Range
Default Value
Description
Handing Mode
Discard
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.
Broadcast
B.6.1.9 Parameter Description: QinQ Link_Creation

This topic describes the parameters that are used for creating a QinQ link.
Navigation Path
1.
Ethernet 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 900
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
specifies the VLAN
ID (at the network
operator side) for the
QinQ link.
according to the
Issue 01 (2016-04-30)

1453

Configuration Guide
B.6.1.10 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)

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
E-AGGR service.
Otherwise, configuration
of the E-AGGR service
will fail.
Port
Issue 01 (2016-04-30)


UNI ports.
1454

Configuration Guide
Parameter
Value Range
Default Value
Description
VLANs
1 to 4094
l This parameter
specifies the VLAN
ID 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.
l It is recommended
that you do not set
this parameter to null.
Priority

not available.
NNI (PW) Parameters

Table B-11 Basic attributes
Parameter
Value Range
Default Value
Description
Location
Sink

sink.
Source
You can configure one or

more source ports but
only one sink port for an
E-AGGR service.
Otherwise, configuration
of the E-AGGR service
will fail.
PW ID
1 to 4294967295

the ID of a PW.
PW Status
Displays whether a PW is
enabled.
Issue 01 (2016-04-30)

1455

Configuration Guide
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
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, set this parameter
to Ethernet. If
Request VLAN
needs to be added to
Ethernet frames that
are encapsulated on a
PW, set this parameter
to Ethernet Tagged
Mode.
Currently, this parameter
can be set only to
Ethernet because EAGGR services on OptiX
RTN 900 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 01 (2016-04-30)

1456

Configuration Guide
Parameter
Value Range
Default Value
Description
Tunnel Selection Mode

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 end.
Remote Operating
Status

Overall Operating
Status

the comprehensive
Tunnel for Auto

Selection

selection policy.
Issue 01 (2016-04-30)

1457

Configuration Guide
Table B-12 Advanced attributes

Parameter
Value Range
Default Value
Description
Control Word
Not in use
Not in use
Specifies whether a
words when
encapsulating ETH
PWE3 packets (PWE3
stands for pseudo wire
emulation edge-to-edge).
Used First
NOTE
control words when
Description.
Alert Label
Alert Label
None
CW

the control channel type,
which determines the PW
continuity check (CC)
mode.
l None: indicates that
virtual circuit
connectivity
verification (VCCV)
packets are not used.
l Alert Label: indicates
that VCCV packets in
Alert Label
encapsulation mode
are used.
VCCV packets
used.
VCCV Verification
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.
Issue 01 (2016-04-30)

1458

Configuration Guide
Parameter
Value Range
Default Value
Description
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

a source port.
Source VLAN ID
1 to 4094

the source VLAN ID.
Sink Interface Type
V-UNI
V-UNI

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.
Issue 01 (2016-04-30)

1459

Configuration Guide
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

the type of a PW.
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
corresponds to a PW.
Policy

not available.
CIR (Kbit/s)

or specifies the
The CIR is recommended
to be the same as the PIR.
Issue 01 (2016-04-30)

1460

Configuration Guide
Parameter
Value Range
Default Value
Description
CBS (Kbit/s)

or specifies the
(CBS) for a PW.
PIR (Kbit/s)

a PW.
The PIR is recommended
to be the same as the
CIR.
PBS (Kbit/s)

PW.
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.1.11 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.
Issue 01 (2016-04-30)

1461

Configuration Guide
Parameter
Value Range
Default Value
Description
MTU(byte)

not available.
Service Tag Role

not available.
Deployment Status

whether an E-AGGR
service has been
deployed.
Parameter
Value Range
Default Value
Description
ID

the ID of a UNI port.
Location

sink.
Port

UNI ports.
VLANs

the VLAN ID of a UNI
port.
Priority

not available.
UNI Parameters
NNI (PW) Parameters

Table B-13 Basic attributes
Parameter
Value Range
Default Value
Description
ID

the ID of an NNI port.
Location

sink.
PW ID

the ID of a PW.
Issue 01 (2016-04-30)

1462

Configuration Guide
Parameter
Value Range
Default Value
Description
PW Status

PW Signaling Type

the signaling type of a
PW.
PW Type

the type of a PW.
PW Direction


the encapsulation type of
a PW.
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.

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.
Issue 01 (2016-04-30)

1463

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
Parameters for a VLAN Forwarding Table

Parameter
Value Range
Default Value
Description
V-UNI
V-UNI

a source port.
Source Interface

a source port.
Source VLAN ID
1 to 4094

the source VLAN ID.
Sink Interface Type
V-UNI
V-UNI

the sink port.
Sink Interface

the sink port.
Sink VLAN ID
1 to 4094

the sink VLAN ID.
Issue 01 (2016-04-30)

1464

Configuration Guide
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 01 (2016-04-30)


the type of a PW.
1465

Configuration Guide
Parameter
Value Range
Default Value
Description
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
corresponds to a PW.
Policy

not available.
CIR (Kbit/s)

or specifies the
The CIR is recommended
to be the same as the PIR.
CBS (Kbit/s)

or specifies the
(CBS) for a PW.
PIR (Kbit/s)

a PW.
The PIR is recommended
to be the same as the
CIR.
PBS (Kbit/s)
Issue 01 (2016-04-30)


PW.
1466

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
B.6.2.1 Parameter Description: ERPS Management_Creation

This topic describes the parameters that are used for creating ERPS management tasks.
Navigation Path
1.
Ethernet Protection > ERPS Management.
2.
Click New.
Parameters
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 8

ID of the Ethernet ring
protection switching (ERPS)
instance.
l The IDs of ERPS instances
on an NE must be different
from each other.
Issue 01 (2016-04-30)

1467

Configuration Guide
Parameter
Value Range
Default Value
Description
East Port
This parameter specifies the east

port of the ERPS instance.
NOTE
plan the counterclockwise
direction as the main direction
of services transmission, and
plan the port that transmits
services in the main direction
as an east port, and the port that
receives services as a west port.
l Set East Port or West Port to
- for the sub-ring ERPS
instance on an interconnection
node.
West Port

west port of the ERPS instance.
NOTE
plan the counterclockwise
direction as the main direction
of services transmission, and
plan the port that transmits
services in the main direction
as an east port, and the port that
receives services as a west port.
l Set East Port or West Port to
- for the sub-ring ERPS
instance on an interconnection
node.
ERP Ring Node Flag
None
None
RPL Port
Neighbor Port
Next Neighbor Port
l If the node is the RPL owner,

set this parameter to RPL
Port.
l If the node is an RPL
neighbor node, set this
parameter to Neighbor Port.
l If the node is the next-hop
node of the RPL owner or
RPL neighbor node, set this
parameter to Next Neighbor
Port.
l Only one node on the ring
can be set as the RPL owner
or RPL neighbor node for
each Ethernet ring.
l If the node on the ring is not
any of the preceding nodes,
set this parameter to None.
Issue 01 (2016-04-30)

1468

Configuration Guide
Parameter
Value Range
Default Value
Description
Flag Port
l Set ERP Ring Node Flag

and Flag Port to matching
values according to the
network plan.
l One ERPS ring has only one
RPL Port and one
Neighbor Port.
set the east port of the RPL
owner to RPL Port and the
west port of the RPL
neighbor node to Neighbor
Port.
set the east port on RPL
owner node's upstream node
and the west port on the RPL
neighbor node's downstream
node as Next Neighbor
Port.
Revertive Mode
Revertive
Revertive
Non-Revertive
Issue 01 (2016-04-30)

This parameter generally takes

the default value Revertive.
You can set this parameter to
Non-Revertive according to the
network plan.
1469

Configuration Guide
Parameter
Value Range
Default Value
Description
Control VLAN
1 to 4094

VLAN ID of Control
VLAN.
l Each node on the Ethernet
ring transmits the R-APS
packets on the dedicated ring
APS (R-APS) channel to
ensure consistency between
the nodes when the ERPS
switching is performed.
Control VLAN is used for
isolating the dedicated RAPS channel. Therefore, the
VLAN ID in Control VLAN
cannot be duplicate with the
VLAN IDs that are
contained in the service
packets.
l The ID of a Control VLAN
must not be the same as any
VLAN ID used by Ethernet
services. All ring nodes
should use the same Control
VLAN ID.
Destination Node
01-19-A7-00-00-01
01-19A7-00-00-01

MAC address of the destination
node. The default destination
MAC address in the R-APS
packets is always 01-19A7-00-00-01.
B.6.2.2 Parameter Description: ERPS Management

This topic describes the parameters that are used for Ethernet ring protection switching
(ERPS) management.
Navigation Path
Issue 01 (2016-04-30)

1470

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 8
This parameter
indicates the ID of
the ERPS instance.
East Port
This parameter
indicates the east port
of the ERPS
instance.
West Port
This parameter
indicates the west
port of the ERPS
instance.
ERP Ring Node Flag
l This parameter
indicates the ring
port
corresponding to
ERP Ring Node
Flag.
Flag Port
This parameter
indicates the flag port
of the ERPS
instance.
Issue 01 (2016-04-30)

1471

Configuration Guide
Parameter
Value Range
Default Value
Description
Control VLAN
1 to 4094
l This parameter
indicates or
specifies the
VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring
transmits the RAPS 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 RAPS channel.
Therefore, the
VLAN ID in
Control VLAN
cannot be
duplicate with the
VLAN IDs that
are contained in
the service
packets or inband
DCN packets.
l The Control
VLAN must be
set to the same
value for all the
NEs on an ERPS
ring.
Destination Node
Issue 01 (2016-04-30)
01-19-A7-00-00-01

This parameter
indicates the MAC
address of the
destination node. The
default destination
MAC address in the
R-APS packets is
always 01-19A7-00-00-01.
1472

Configuration Guide
Parameter
Value Range
Default Value
Description
Current Node
This parameter
indicates the node
that initiates a
switching request.
Revertive Mode
Revertive
This parameter
indicates the
revertive mode and
can be reset.
ver2
l This parameter
indicates the
configured
compatible ERPS
protocol version
and can be reset.
Non-Revertive
Compatible_Version
ver2
ver1
l For multi-ring
networks,
Compatible_Ver
sion for all ring
nodes must be
ver2.
l For single ring
networks,
Compatible_Ver
sion for ring
nodes except the
RPL owner can
be either ver1 or
ver2.
Compatible_Ver
sion for the RPL
owner must be
ver2.
Virtual Channel Status
Enable
Enable
Disable
Issue 01 (2016-04-30)

l This parameter
indicates the
configured status
and VLAN ID of
an R-APS virtual
channel, and can
be reset.
l For details about
the value of this
parameter, refer
to Planning
Guidelines for RAPS Virtual
Channels in the
1473

Configuration Guide
Parameter
Value Range
Default Value
Virtual Channel VLANs
1 to 4094
Major ERPS Ring ID
Set this parameter

only for the sub-ring
ERPS instance on an
interconnection node
to associate the subring ERPS instance
with the major ring
ERPS instance.
ETH Type Domain
Transfer mode
Transfer mode
l If an ERP ring
consists of OptiX
RTN and thirdparty equipment
and the type
domain in R-APS
packets used by
the third-party
equipment is
0x8902, set ETH
Type Domain to
Standard mode
(Ox8902) for the
OptiX RTN
equipment.
Standard mode
Description
Feature
Description.
l In other cases,
retain the default
value Transfer
mode (Ox8809)
for this parameter.
Issue 01 (2016-04-30)

1474

Configuration Guide
Parameter
Value Range
Default Value
Description
Hold-Off Time(ms)
l This parameter
indicates or
specifies the holdoff time of the
ERPS hold-off
timer.
l The hold-off
timer is used for
negotiating the
protection
switching
sequence when
the ERPS coexists
with other
protection
schemes so that
the fault can be
rectified in the
case of other
protection
switching (such
as LAG
protection) before
the ERPS occurs.
When a node on
the ring detects
one or more new
faults, it starts up
the hold-off timer
if the preset holdoff time is set to a
value that is not
0. During the
hold-off time, the
fault is not
reported to trigger
an ERPS. When
the hold-off timer
times out, the
node checks the
link status
regardless
whether the fault
that triggers the
startup of the
timer exists. If the
fault exists, the
node reports it to
trigger an ERPS.
This fault can be
Issue 01 (2016-04-30)

1475

Configuration Guide
Parameter
Value Range
Default Value
Description
the same as or
different from the
fault that triggers
the initial startup
of the hold-off
timer.
Issue 01 (2016-04-30)

1476

Configuration Guide
Parameter
Value Range
Default Value
Description
Guard Time(ms)
500
l This parameter
indicates or
specifies the
guard time of the
ERPS guard
timer.
l The nodes on the
ring continuously
forward the RAPS packets to
the Ethernet ring.
As a result, the
outdated R-APS
packets may exist
on the ring
network. After a
node on the ring
receives the
outdated R-APS
packets, an
incorrect ERPS
may occur. The
ERPS guard timer
is an R-APS timer
used for
preventing a node
on the ring from
receiving
outdated R-APS
packets. When a
faulty node on the
ring detects that
the switching
condition is
cleared, the node
starts up the
guard timer and
starts to forward
the R-APS (NR)
packets. During
this period, the RAPS packets
received by the
node are
discarded. The
received R-APS
packets are
forwarded only
after the time of
Issue 01 (2016-04-30)

1477

Configuration Guide
Parameter
Value Range
Default Value
Description
the guard timer
expires.
Issue 01 (2016-04-30)

1478

Configuration Guide
Parameter
Value Range
Default Value
Description
WTR Time(mm:ss)
1 to 12, in step of 1
l This parameter
indicates or
specifies the
WTR time of the
WRT timer in the
case of ERPS
protection.
l The WTR time
refers to the
duration from the
time when the
working channel
is restored to the
time when the
switching is
released. When
the working
channel is
restored, the
WTR timer of the
RPL owner starts
up. In addition, a
signal that
indicates the
operation of the
WTR timer is
continuously
output in the
timing process.
When the WTR
timer times out
and no switching
request of a
higher priority is
received, the
signal indicating
the operation of
the WTR timer is
not transmitted.
In addition, the
WTR release
signal is
continuously
output.
l The WTR timer is
used to prevent
frequent
switching caused
by the unstable
working channel.
Issue 01 (2016-04-30)

1479

Configuration Guide
Parameter
Value Range
Default Value
Description
Packet Transmit Interval(s)
1 to 10
This parameter
the interval for
sending R-APS
packets periodically.
Entity Level
0 to 7
This parameter
the level of the
maintenance entity.
Last Switching Request
This parameter
indicates the last
switching request.
RB Status
This parameter
indicates the RB
(RPL Blocked) status
of the packets
received by the
working node.
l noRB: The RPL
is not blocked.
l RB: The RPL is
blocked.
Issue 01 (2016-04-30)

1480

Configuration Guide
Parameter
Value Range
Default Value
Description
DNF Status
This parameter
indicates the DNF
status of the packets
received by the
working node.
l noDNF: The RAPS packets do
not contain the
DNF flag. In this
case, the packets
are forwarded by
the node that
detects the fault
on a non-RPL
link, and the node
that receives the
packets is
requested to clear
the forwarding
address table.
l DNF: The R-APS
packets contain
the DNF flags. In
this case, the
packets are
forwarded by the
node that detects
the fault on an
RPL link, and the
node that receives
the packets is
informed not to
clear the
forwarding
address table.
Issue 01 (2016-04-30)

1481

Configuration Guide
Parameter
Value Range
Default Value
Description
State Machine Status
This parameter
indicates the status of
the state machine at
the working node.
l Idle: The Ethernet
ring is in normal
state. For
example, no node
on the Ethernet
ring detects any
faults or receives
the R_APS (NR,
RB) packets.
l Protection: The
Ethernet ring is in
protected state.
For example, a
fault on the node
triggers the
ERPS, or a node
on the ring is in
the WTR period
after the fault is
rectified.
Node Carried with Current Packet
This parameter
indicates the MAC
address carried in the
R-APS packets
received by the
current node. The
MAC address refers
to the MAC address
of the source node
that initiates the
switching request.
East Port Status
This parameter
displays the status of
the east port.
West Port Status
This parameter
displays the status of
the west port.
Bound Port
This parameter
displays a sub-ring
port. It applies to
only an ERPS subring.
Issue 01 (2016-04-30)

1482

Configuration Guide
Parameter
Value Range
Default Value
Description
Bound MEP
This parameter
specifies the MEP
with which a subring port is bound. It
applies to only an
ERPS sub-ring.
Interconnected Node
None
None
l This parameter
specifies the
interconnection
node attribute. It
applies to only an
ERPS sub-ring.
Primary
Secondary
Multi-point Failure
Disable
Disable
Primary
Secondary
l After multiple
failures occur, an
interconnection
node triggers
manual ERPS
switching when
the following
conditions are
met: An MEP is
properly bound; a
loss of
connectivity
between the
interconnection
nodes is detected;
the values of
Interconnected
Node and Multipoint Failure are
identical.
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation

This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
1.
Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
2.
Click the Port Group Parameters tab.
3.
Click Create.
Issue 01 (2016-04-30)

1483

Configuration Guide

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 900
supports the CIST
MSTP only.
l STP: stands for
Spanning Tree
Protocol.
Enable Protocol
Enabled
Disabled

whether to enable the
protocol of the port group
or a member port in the
port group.
Disabled
Parameters for Application Ports

Parameter
Value Range
Default Value
Description
Board

the board where the
member of port group is
located.
Available Port

the available port list in
which a port can be
added to the port group.
Selected Port

the selected ports that can
be added to the 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.
Issue 01 (2016-04-30)
1484

Configuration Guide
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.
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
Issue 01 (2016-04-30)


not support this
parameter.
1485

Configuration Guide
Parameter
Value Range
Default Value
Description
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
20
Specifies the maximum

hop count of the MSTP.
Network Diameter
2 to 7
l This parameter
specifies the MSTP
network diameter.
l If the value of
Network Diameter is
greater, the network is
in a larger scale.
Hello Time(s)
1 to 10
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 01 (2016-04-30)

1486

Configuration Guide
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
value of this
parameter 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 01 (2016-04-30)

1487

Configuration Guide
Parameter
Value Range
Default Value
Description
Enable Edge Attribute
Disabled
Disabled
l This parameter
specifies the
management edge
attributes of the port.
Enabled

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
recommended that
you use the default
value.
Actual Edge Attribute
Issue 01 (2016-04-30)


the actual management
edge attributes of the
port.
1488

Configuration Guide
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
according to the
actual working mode.
If the actual working
mode is full-duplex,
the actual point-topoint attribute is true.
mode is half-duplex,
Actual Point-toPoint 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.
l It is recommended
that you use the
default value.
Actual Point-to-Point
Attribute
Issue 01 (2016-04-30)


the actual point-to-point
attribute of the port.
1489

Configuration Guide
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.
l This parameter needs
to be set according to
the planning
information.
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
900 supports only the
MSTP that uses CIST.
Issue 01 (2016-04-30)

1490

Configuration Guide
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
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 01 (2016-04-30)

1491

Configuration Guide
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
MSTP
l This parameter
indicates the running
mode of the protocol.
STP
l MSTP: stands for

Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.
Issue 01 (2016-04-30)

1492

Configuration Guide
Parameter
Value Range
Default Value
Description
Bridge Priority
4096
32768
l This parameter
indicates the priority
of the bridge.
ID indicate the
l When the value is
bridge is more
as the root bridge.
the bridges in the STP
network use the same
value, the bridge
whose MAC address
is the smallest is
selected as the root
bridge.
Bridge MAC Address

the MAC address of the
bridge.
Root Bridge Priority
4096
32768

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 01 (2016-04-30)

1493

Configuration Guide
Parameter
Value Range
Default Value
Description
Root Port Priority
128
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.
Max Age(s)
6 to 40
20
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
value of this
manner and thus the
network adaptation
ability is reduced.
Issue 01 (2016-04-30)

1494

Configuration Guide
Parameter
Value Range
Default Value
Description
Forward Delay(s)
4 to 30
15
l This parameter
specifies the holdoff
the learning state.
the network state
change. Hence, the
slower and the
MST Domain Max Hop

Count

the maximum hop count
of the MSTP.
Topology Change
Identifier

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.
Parameter
Value Range
Default Value
Description
Port

Enable Protocol
Enabled
Disabled

whether the protocol of
the port group or a
member of the port group
is enabled.
Disabled

the role of a port.
Port Parameters
Disabled
Port Role
Issue 01 (2016-04-30)

1495

Configuration Guide
Parameter
Value Range
Default Value
Description
Port Status
Discarding
Discarding

the state of a port.
Learning
l Discarding: receives
only BPDU packets
Forwarding
l Learning: only
receives or transmits
BPDU packets
l Forwarding: forwards
user traffic, and
transmits/receives
BPDU packets
Priority
128

priority.
l When the value is
higher.
Path Cost
1 to 200000000
200000
l This parameter
the network that the
port is connected to.
l In the case of the
bridges on both ends
of the path, set this
parameter to the same
value.
Bridge Priority
4096
32768

ID indicate the
l When the value is
bridge is more
as the root bridge.
the bridges in the STP
network use the same
value, the bridge
whose MAC address
is the smallest is
selected as the root
bridge.
Issue 01 (2016-04-30)

1496

Configuration Guide
Parameter
Value Range
Default Value
Description
Bridge MAC Address

bridge.
Designated Port
Priority

priority.
l When the value is
higher.
Design Port

the designated port.
Edge Port 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
recommended that
you use the default
value.
Actual Edge Port
Attribute
Issue 01 (2016-04-30)
Disabled


the actual management
edge attributes of the
port.
1497

Configuration Guide
Parameter
Value Range
Default Value
Description
Point to Point
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
according to the
actual working mode.
mode is full-duplex,
the actual point-topoint attribute is true.
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.
l It is recommended
that you use the
default value.
Actual Point to Point
Issue 01 (2016-04-30)


the actual point-to-point
attribute of the port.
1498

Configuration Guide
Parameter
Value Range
Default Value
Description
Max Count of
Transmitting Message
1 to 255
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
STP
MSTP
l This parameter
indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.
Hello Time(s)
1 to 10
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 01 (2016-04-30)

1499

Configuration Guide
Parameter
Value Range
Default Value
Description
Max Age(s)
6 to 40
20
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
value of this
manner and thus the
network adaptation
ability is reduced.
Forward Delay(s)
4 to 30
15
l This parameter
specifies the holding
the learning state.
the network state
change. Hence, the
slower and the
Remain Hop

not support this
parameter.
B.6.2.8 Parameter Description: IGMP Snooping Configuration_Protocol

Configuration
This topic describes the parameters that are used for configuring IGMP snooping (IGMP
stands for Internet Group Management Protocol).
Issue 01 (2016-04-30)

1500

Configuration Guide
Navigation Path
1.
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2.
Click the Protocol Configuration tab.

Parameter
Value Range
Default Value
Description
Service ID

the service ID.
Enabled Protocol
Enabled
Disabled
l This parameter
enable the IGMP
Snooping protocol.
Disabled
l If the bridge accesses

a LAN where the
IGMP multicast
server exists, you can
enable the IGMP
Snooping protocol
according to the
requirement.
Issue 01 (2016-04-30)

1501

Configuration Guide
Parameter
Value Range
Default Value
Description
Router Port Aging

Time(min)
1 to 120
l If an entry is not
period (that is, no
IGMP query packet is
received), this entry is
This mechanism is
called aging, and this
period is called aging
time.
to a very large value,
the bridge stores
excessive multicast
entries that are
outdated.
Consequently, the
resources of the
multicast table are
exhausted.
to a very small value,
the bridge may delete
the multicast entry
that is required.
Consequently, the
forwarding efficiency
decreases.
Issue 01 (2016-04-30)

1502

Configuration Guide
Parameter
Value Range
Default Value
Description
Max Nonresponse
Times from Multicast
Members
1 to 4
l This parameter
specifies the
maximum number of
multicast group
members who do not
respond.
l If the IEEE 802.1q
bridge transmits an
IGMP group query
packet to the
multicast member
ports, the IEEE
802.1q bridge starts
the timer for the query
of the maximum
number of responses.
If no IGMP report
packets are received
within the query time,
the IEEE 802.1q
bridge adds one to the
number of no
responses at the port.
When the number of
no responses exceeds
the preset value of
Maximum Times of
No Response from
Multicast Members,
the IEEE 802.1q
bridge deletes the
additional multicast
members from the
multicast group.
Maximum Multicast
Groups
512
128
256
512
Unlimited
Issue 01 (2016-04-30)

l This parameter
specifies the
maximum number of
allowable multicast
groups.
l The multicast group
records the mapping
relationships between
the ports on the
router, MAC
multicast addresses,
and member ports in
the multicast group.
1503

Configuration Guide
Parameter
Value Range
Default Value
Description
Maximum Number of
Multicast Group
Members
1024
l This parameter
specifies the
maximum number of
allowable multicast
group members.
128
256
512
1024
l A multicast group
member refers to the
host that is added to a
multicast group.
Unlimited
Actual Multicast Count

the number of actually
used multicast groups.
Actual Multicast
Members Count

the number of actually
used multicast group
members.
B.6.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be

Quickly Deleted
This topic describes the parameters that are used for adding a port to be quickly deleted.
Navigation Path
1.
Tree.
2.
Click the Protocol Config tab.
3.
Click Add.
Parameters for Fast Leave Ports

Parameter
Value Range
Default Value
Description
Service ID

the service ID.
Issue 01 (2016-04-30)

1504

Configuration Guide
Parameter
Value Range
Default Value
Description
VLAN ID
1 to 4094
l This parameter
specifies the VLAN
where the port to be
quickly deleted is
located.
the planning
information.
Port Type
V-UNI
V-UNI
V-NNI
l This parameter
the port to be quickly
deleted.
the planning
information.
Port

the port to be quickly
deleted.
B.6.2.10 Parameter Description: IGMP Snooping Configuration_Route

Management
This topic describes the parameters that are used for route management for IGMP snooping
(IGMP stands for Internet Group Management Protocol).
Navigation Path
1.
Tree.
2.
Click the Router Port Management tab.
Parameters for Router Port Management

Parameter
Value Range
Default Value
Description
Service ID

the ID of the created ELAN service.
Issue 01 (2016-04-30)

1505

Configuration Guide
Parameter
Value Range
Default Value
Description
VLAN ID

the VLAN ID of the
router port.
Port Type

the type of the router
port.
Port

the router port.
Port Status

the status of the router
port.
Port Created AT

the time when the router
port is created.
Port Remainder Aging

Time(min)

the remaining aging time
of the router port.
B.6.2.11 Parameter Description: IGMP Snooping Configuration_Static Router

Port Creation
This topic describes the parameters that are used for adding static router ports.
Navigation Path
1.
Tree.
2.
Click the Route Management tab.
3.
Click New.
Parameters for Router Port Creation

Parameter
Value Range
Default Value
Description
Service ID

Issue 01 (2016-04-30)

1506

Configuration Guide
Parameter
Value Range
Default Value
Description
VLAN ID
1 to 4094

the VLAN ID of the
router port.
Available Port

the available ports.
Selected Port

the specified router port.
B.6.2.12 Parameter Description: IGMP Snooping Configuration_Route Member

Port Management
This topic describes the parameters that are used for managing route member ports for IGMP
snooping (IGMP stands for Internet Group Management Protocol).
Navigation Path
1.
Tree.
2.
Click the Route Member Port Management tab.
Parameters for Multicast Groups Information

Parameter
Value Range
Default Value
Description
Service ID

VLAN ID

the VLAN ID of the
multicast group.
Multicast MAC Address

the multicast MAC
address.
Multicast Groups Type

the type of the multicast
group.
Multicast Group
Creating Time

the time when the
multicast group is set up.
Issue 01 (2016-04-30)

1507

Configuration Guide
Parameters for Multicast Group Members Information

Parameter
Value Range
Default Value
Description
Service ID

VLAN ID

the VLAN ID of the
multicast group member.
Port Type

the type of the multicast
group member.
Port

the multicast group
member port.
Port Remainder Aging

Times

the remaining nonresponse times of the
multicast group member
port.
B.6.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast

Group Member Creation
This topic describes the parameters that are used for adding static multicast groups.
Navigation Path
1.
Tree.
2.
Click the Route Member Port Management tab.
3.
Click New.
Issue 01 (2016-04-30)

1508

Configuration Guide
Parameters for Router Port Creation

Parameter
Value Range
Default Value
Description
Service ID

VLAN ID
1 to 4094

the VLAN ID of the
multicast group.
Multicast MAC Address

the multicast MAC
address.
Available Port

the available interfaces.
Selected Port

the preset port of the
multicast group
members.
B.6.2.14 Parameter Description: IGMP Snooping Configuration_Data Count

This topic describes the parameters that are used for collecting statistics for IGMP snooping
(IGMP stands for Internet Group Management Protocol).
Navigation Path
1.
Tree.
2.
Click the Data Count tab.
Parameters for Routing Member Interface Management

Parameter
Value Range
Default Value
Description
Service ID

the service ID.
VLAN ID

the VLAN ID of the
service.
Port Type

the port type.
Issue 01 (2016-04-30)

1509

Configuration Guide
Parameter
Value Range
Default Value
Description
Port

the port.
Packet Statistic Status
Clear
Clear

or specifies the status of
collecting the packet
statistics.
Start
Stop
IGMPv1 Query Packet
Count

the number of received
IGMPv1 query packets.
IGMPv2 Query Packet

Count

IGMPv3 Query Packet

Count

IGMP Leaving Packet

Count

the number of leaving
packets that are received.
IGMPv1 Member
Report Packet Count

packets that are reported
by the IGMPv1
members.
IGMPv2 Member
Report Packet Count

by the IGMPv2
members.
IGMPv3 Member
Report Packet Count

by the IGMPv3
members.
Unrecognized or
Unprocessed Packet
Count

the number of packets
that cannot be recognized
or processed.
Discarded Incorrect
Packet Count

the number of discarded
error packets.
Issue 01 (2016-04-30)

1510

Configuration Guide
B.6.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG

Creation
This section describes the parameters that are used for creating a link aggregation group
(LAG).
Navigation Path
1.
Interface Management > Link Aggregation Group Management from the Function
Tree.
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.
l This parameter is
valid only when
Automatically
Assign is not selected.
Automatically Assign
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 01 (2016-04-30)


the LAG name.
1511

Configuration Guide
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

Switch Mode

Link Detection Protocol
Null
Null
This parameter is set

information.
802.3ah
Issue 01 (2016-04-30)

1512

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Revertive Mode
Non-Revertive Mode
l Revertive Mode can

be set only when
Load Sharing is set
to Non-Sharing.
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 01 (2016-04-30)

1513

Configuration Guide
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
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.
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, preventing link
failure.
Load Sharing Hash
Algorithm
Issue 01 (2016-04-30)

Set this parameter in the

Link Aggregation
Parameters tab page.
1514

Configuration Guide
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)
0 to 30
10
l Specifies the WTR

time for the LAG.
l WTR Time(min)
takes effect only when
Revertive Mode is
Revertive Mode.
Issue 01 (2016-04-30)

1515

Configuration Guide
Parameter
Value Range
Default Value
Description
Switch LAG upon Air

Interface SD
Disabled
Disabled
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 or
MW_BER_EXC
alarm will trigger the
LAG switching at the
air interface.
l It is advisable to set
Switch LAG upon
Air Interface SD to
Enabled when
configuring an airinterface LAG.
Packet Receive Timeout
Period
Short period
Short period
Long period
l A LAG switching is
triggered if no LACP
packet is received
after Packet Receive
Timeout Period
times out.
l When LACP protocol
packets pass through
an intermediate
network, it is
recommended to set
Packet Receive
Timeout Period to
Short period. In
other scenarios, set it
to Long period to
avoid mistaken
switching.
l This parameter is
supported only when
LAG Type is set to
Static.
Issue 01 (2016-04-30)

1516

Configuration Guide
Parameter
Value Range
Default Value
Description
LAG Min Active Link

Threshold
To trigger ERPS
switching upon failure of
a member link in a LAG
when LAG and ERPS
coexist, LAG Min
Active Link Threshold
must be set to the total
number of links in the
LAG.
Port Settings Parameters

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.
Board (Available Slave

Ports)
l This parameter
specifies the slave
board in a LAG.
according to the
Issue 01 (2016-04-30)

1517

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
Selected Standby Ports

the selected slave ports.
B.6.2.16 Parameter Description: Ethernet Link Aggregation_Link Aggregation

This section describes the parameters for configuring the port priority and system loadsharing hash algorithm.
Navigation Path
1.
Interface Management > Link Aggregation Group Management from the Function
Tree.
2.
Click the Link Aggregation Parameters tab.

Parameter
Value Range
Default Value
Description
Port

the port whose priority
can be set.
Port Priority
0 to 65535
32768
l This parameter
indicates the priorities
of the ports in a LAG
as defined in the
LACP protocol. The
smaller the value, the
l When ports are added
into a LAG, the port
of the highest priority
is preferred for
service transmission.
Issue 01 (2016-04-30)

1518

Configuration Guide
Parameter
Value Range
Default Value
Description
Load Sharing Hash

Algorithm
Automatic
Automatic
l System Load
Sharing Hash
Algorithm is valid
only when Load
Sharing of a LAG is
set to Sharing.
Source MAC
Destination MAC
Source and Destination
MACs
Source IP Address
Destination IP Address
Source and Destination IP
Address
MPLS Label
l The load sharing

computation methods
include algorithm
auto-sensing,
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),
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
MPLS labels.
l After the
configuration data is
deployed, System
Load Sharing Hash
Algorithm takes
effect for the entire
NE.
l For PW-carried UNINNI E-Line services,
System Load
Sharing Hash
Algorithm cannot be
set to MPLS Label.
B.6.2.17 Parameter Description: LPT Management_Creating Simple LPT

This parameter describes the parameters that are used for creating LPT management.
Issue 01 (2016-04-30)

1519

Configuration Guide
Navigation Path
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > Simple LPT from the Function Tree.
2.
Click New.
Parameters for Convergence Points

Parameter
Value Range
Default Value
Description
Board
This parameter specifies the board at the

convergence point.
Port
This parameter specifies the port on the

board of the convergence point.
NOTE
One port can be in an LPT only.
Parameters for Access Points

Parameter
Value Range
Default Value
Description
Board
This parameter specifies the board at the

access point.
Port
This parameter specifies the port on the

board of the access point.
NOTE
The access point supports selection of multiple
ports on different boards.
B.6.2.18 Parameter Description: LPT Management_Point-to-Point LPT

This topic describes the parameters that are related to point-to-point LPT.
Navigation Path
1.
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
point-to-point services.
Issue 01 (2016-04-30)

1520

Configuration Guide
Parameter
Value Range
Default Value
Description
Primary Function Point

the port where the
primary point of point-topoint LPT resides.
Secondary Function
Point Type

the type of secondary
point for point-to-point
LPT.
Secondary Function
Point

the port where the
secondary point of pointto-point LPT resides.
LPT Instance Status

the status of point-topoint LPT.
LPT Enabled
Enabled
Disabled

or 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

or specifies the recovery
time of point-to-point
LPT.
Hold-Off Times(ms)
0-10000
1000

or specifies the hold-off
time of point-to-point
LPT.
Switching Mode

the switching mode of
point-to-point LPT.
Point-to-point LPT is
available only in strict
mode.
Issue 01 (2016-04-30)

1521

Configuration Guide
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

or 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.
B.6.2.19 Parameter Description: LPT Management_Creating Point-to-Point LPT

This topic describes the parameters that are related to creating point-to-point LPT.
Issue 01 (2016-04-30)

1522

Configuration Guide
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.

the port where the
primary point of point-topoint LPT resides.
VLAN ID
1-4094

the VLAN ID that is
carried by a point-topoint LPT packet to
traverse an L2 network.
LPT package out port

the out port of a point-topoint LPT packet.
B.6.2.20 Parameter Description: LPT Management_Point-to-Multipoint LPT

This topic describes the parameters that are related to point-to-multipoint LPT.
Navigation Path
1.
2.
Click the Point-to-Multipoint LPT tab.
Issue 01 (2016-04-30)

1523

Configuration Guide
Parameters of Primary Point

Parameter
Value Range
Default Value
Description

Type

the type of primary point
for point-to-multipoint
LPT.

the port where the
primary point of point-tomultipoint LPT resides.
LPT Instance Status

the status of point-tomultipoint LPT.
LPT Enabled
Enabled
Disabled

point-to-multipoint LPT.
Disabled
Recovery Times(s)
1-600

or specifies the recovery
time of point-tomultipoint LPT.
Hold-Off Times(ms)
0-10000
1000

or specifies the hold-off
time of point-tomultipoint LPT.
Switching Mode
Strict mode
Strict mode

point-to-multipoint LPT.
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 01 (2016-04-30)

1524

Configuration Guide
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

or specifies the fault
detection period of pointto-multipoint LPT.

port.

ID

the NET IDs of LPT
ends, when the service
network is an L2
network.
Issue 01 (2016-04-30)

1525

Configuration Guide
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.

ID

the NET IDs of LPT
ends, when the service
network is an L2
network.
B.6.2.21 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 01 (2016-04-30)

1526

Configuration Guide
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
only when Point Type is
set to UNI.
Port

the port where the
set to UNI.
Point ID

the service ID for the
primary point of point-tomultipoint LPT.
set to PW or QinQ.
Issue 01 (2016-04-30)

1527

Configuration Guide
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

or specifies the type of
secondary point for pointto-multipoint LPT.
PW
QinQ
L2 net
Issue 01 (2016-04-30)

1528

Configuration Guide
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
point-to-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 01 (2016-04-30)

1529

Configuration Guide
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
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.
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2.
Click the Maintenance Association tab.
3.
Choose New > New Maintenance Domain.
Issue 01 (2016-04-30)

1530

Configuration Guide

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.
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.
Function Tree.
2.
3.
Select the maintenance domain in which a maintenance association needs to be created.

Choose New > New Maintenance Association.

Parameter
Value Range
Default Value
Description
Maintenance
Domain Name
This parameter indicates the maintenance

domain of the created maintenance
association.
Issue 01 (2016-04-30)

1531

Configuration Guide
Parameter
Value Range
Default Value
Description
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
3.33ms
1s
l This parameter specifies the interval for

transmitting packets in the CC.
10ms
l The CC is performed to check the

availability of the service.
100ms
1s
10s
1m
10m
Protocol/Standard
802.1ag
802.1ag
When the Ethernet service OAM based on

IEEE 802.1ag is adopted, set Protocol/
Standard to 802.1ag. When the Ethernet
service OAM based on ITU-T Y.1731 is
adopted, set Protocol/Standard to Y.1731
and set MEGs and MPs according to the
plan.
When the protocol is Y.1731, set this

parameter according to the plan.
Y.1731
MEG ID
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.
Function Tree.
2.
3.
Select the maintenance association in which an MEP needs to be created. Choose New >
New MEP Point.
Issue 01 (2016-04-30)

1532

Configuration Guide

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.
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.
Function Tree.
2.
3.
Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog
box is displayed.
Issue 01 (2016-04-30)

1533

Configuration Guide
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.
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.
Function Tree.
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 01 (2016-04-30)

1534

Configuration Guide
Parameter
Value Range
Default Value
Description
MIP 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.
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.
Function Tree.
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

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.
Source
Maintenance Point
ID
l This parameter specifies the source

maintenance point in the LB test.
Issue 01 (2016-04-30)
Deselected
Deselected
l Only the MEP can be set to the source

maintenance point.

1535

Configuration Guide
Parameter
Value Range
Default Value
Description
Destination
Maintenance Point
ID
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
This parameter indicates the relevant

information and result of the LB test.
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

This topic describes the parameters that are used for enabling the LT.
Issue 01 (2016-04-30)

1536

Configuration Guide
Navigation Path
1.
Function Tree.
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

LT test is performed on the basis of MP
IDs.
Destination
Maintenance Point
MAC Address
Selected
Selected

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.
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
Issue 01 (2016-04-30)

1537

Configuration Guide
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
This parameter indicates the result of the

LT test.
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
2.
Click Manual Loopback Detection tab.
Issue 01 (2016-04-30)

1538

Configuration Guide
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
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter

This topic describes the OAM parameters that are related to Ethernet ports.
Navigation Path
1.
Ethernet OAM Management > Ethernet Port OAM Management from the Function
Tree.
2.
Click the OAM Parameter tab.

Parameter
Value
Range
Default
Value
Description
Port

corresponding port.
Issue 01 (2016-04-30)

1539

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Enable OAM Protocol
Enabled
Disabled
l This parameter indicates

or specifies 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

or specifies the 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.
Issue 01 (2016-04-30)

1540

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Link Event Notification
Enabled
Enabled

local link events can be
notified to the opposite
end.
Disabled
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.
information.
Remote Side Loopback Response
Disabled
Disabled
Enabled

port responds to the
remote loopback.
l Remote loopback
indicates that the local
OAM entity transmits
packets to the remote
OAM entity for
loopback. The local
OAM entity can locate
the fault and test the link
performance through
loopback data analysis.
l If a port does not support
remote loopback
response, this port does
not respond to the
loopback request from
the remote port
regardless of the OAM
port status.
Issue 01 (2016-04-30)

1541

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Loopback Status
NonLoopback

loopback status at the local
end.
Initiate
Loopback at
Local
NOTE
Loopback Status is valid only
after you choose OAM >
Enable Remote Loopback.
Respond
Loopback of
Remote
OAM Discovery Status

OAM discovery status at the
local end.
Port Transmit Status

status of transmitting packets
at the local end.
Port Receive Status

status of receiving packets at
the local end.
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.
Ethernet OAM Management > Ethernet Port OAM Management from the Function
Tree.
2.
Click the OAM Error Frame Monitor tab.

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.
Issue 01 (2016-04-30)

1542

Configuration Guide
Parameter
Value Range
Default Value
Description
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

of monitoring the error frame period.
Error Frame
Second Window(s)
1
60
This parameter specifies the time window

of monitoring the error frame second.
Error Frame
Second
Threshold(s)
1

of 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
number of error frames on the link
exceeds the preset value of Error
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 number of error
frames on the link exceeds the preset
value of Error Frame Second
Threshold(s), an alarm is reported.
B.6.4 QoS Parameters

This topic describes the parameters that are related to QoS.
B.6.4.1 Parameter Description: DiffServ Domain Management

This topic describes the parameters that are used for managing DiffServ (DS) domains.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Function Tree.
Issue 01 (2016-04-30)

1543

Configuration Guide

Parameter
Value Range
Default Value
Description
Mapping Relation ID
1 to 8

the ID of the mapping
relationship between DS
domains.
Mapping Relation
Name
Default Map

the name of the mapping
relationship between DS
domains.
NOTE
If one default DS domain exists on the OptiX RTN 900 equipment, Mapping Relation ID is set to 1, and
Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this
domain.
Parameters for Ingress Mapping Relation

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.
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
priority.
Issue 01 (2016-04-30)

1544

Configuration Guide
Parameter
Value Range
Default Value
Description
IP DSCP
0 to 63
l This parameter
indicates the DSCP
priority of the IP
addresses of the
ingress packets.
l The differentiated
services code point
(DSCP) refers to bits
0-5 of the
differentiated services
(DS) field in the
packet and indicates
the service class and
discarding priority of
the packet.
MPLS EXP
0 to 7
l Displays the MPLS

EXP value of ingress
packets.
l When a packet in an
egress queue leaves
an NNI port, the NNI
port obtains the
packet priority value
according to the
mappings between
PHB service classes
of egress queues and
egress packet
priorities (MPLS EXP
values), and writes the
obtained priority
value into the EXP
field of the egress
MPLS packet.
NOTE
For OptiX RTN 950(CSH
used as the system control
board)/980 (CSHN used as
the system control board),
the MPLS EXP value can
be changed only in the
default DS domain
(Default Map).
Issue 01 (2016-04-30)

1545

Configuration Guide
Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the per-hop
behavior (PHB)
service class of the
DS domain.
AF11
AF12
AF13
AF21
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.
AF22
AF23
AF31
AF32
AF33
AF41
AF42
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.
AF43
EF
CS6
CS7
Issue 01 (2016-04-30)

1546

Configuration Guide
Parameters for Egress Mapping Relation

Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the PHB
DS domain.
AF11
AF12
AF13
l The PHB service

class refers to the
forwarding behavior
behavior aggregate
(BA) operation. The
forwarding behavior
requirements.
AF21
AF22
AF23
AF31
AF32
AF33
AF41
l The PHB service

AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
and MPLS EXP
value) contained in
PHB service classes
of the specified or
default mapping
relationship.
AF42
AF43
EF
CS6
CS7
CVLAN
0 to 7
l This parameter
of the C-VLAN of the
egress packets.
l C-VLAN indicates
and the value 7
priority.
Issue 01 (2016-04-30)

1547

Configuration Guide
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
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.

Parameter
Value Range
Default Value
Description
Port

the port that uses the DS
domain.
Issue 01 (2016-04-30)

1548

Configuration Guide
Parameter
Value Range
Default Value
Description
Packet Type
CVLAN
CVLAN
The packets trusted by

the OptiX RTN 900 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 For the E-Line services
that are transparently
transmitted end to end
(UNI-UNI), a UNI port
only trusts DSCP
value.
l An NNI port carrying
MPLS/PWE3 services
trusts only packets with
MPLS EXP values.
l A QinQ-based NNI
port trusts only packets
with DSCP values or
S-VLAN priorities.
B.6.4.2 Parameter Description: DiffServ Domain Management_Create

This parameter describes the parameters that are used for creating DiffServ (DS) domains.
Navigation Path
1.
Management > Diffserv Domain Management > Diffserv Domain Management
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.
Issue 01 (2016-04-30)

1549

Configuration Guide
Parameter
Value Range
Default Value
Description
Mapping Relation
Name

relationship of a DS
domain.
Parameters for Ingress Mapping Relation

Parameter
Value Range
Default Value
Description
C-VLAN
0 to 7
l This parameter
specifies the C-VLAN
priority of the ingress
packets.
l C-VLAN indicates
and the value 7
priority.
S-VLAN
0 to 7
l This parameter
priority of the ingress
packets.
server-side VLAN,
and the value 7
priority.
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
(DS) field in the
the packet.
Issue 01 (2016-04-30)

1550

Configuration Guide
Parameter
Value Range
Default Value
Description
MPLS EXP
l Displays the MPLS

EXP value of ingress
packets.
egress queue leaves
port obtains the
according to the
mappings between
PHB service classes
egress packet
obtained priority
value into the EXP
field of the egress
MPLS packet.
PHB
BE
AF11
AF12
AF13
l The PHB service

class refers to the
forwarding behavior
behavior aggregate
(BA) operation. The
forwarding behavior
requirements.
AF21
AF22
AF23
AF31
AF32
AF33
AF41
l The PHB service

AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
and MPLS EXP
value) contained in
PHB service classes
of the specified or
default mapping
relationship.
AF42
AF43
EF
CS6
CS7
Issue 01 (2016-04-30)
l This parameter
indicates the PHB
DS domain.

1551

Configuration Guide
Parameters for Outbound Mapping Relationship

Parameter
Value Range
Default Value
Description
PHB
BE
l This parameter
indicates the PHB
DS domain.
AF11
AF12
AF13
l The PHB service

class refers to the
forwarding behavior
behavior aggregate
(BA) operation. The
forwarding behavior
requirements.
AF21
AF22
AF23
AF31
AF32
AF33
AF41
l The PHB service

AF2, AF3, AF4, EF,
CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
and MPLS EXP
value) contained in
PHB service classes
of the specified or
default mapping
relationship.
AF42
AF43
EF
CS6
CS7
C-VLAN
0 to 7
l This parameter
specifies the C-VLAN
priority of the egress
packets.
l C-VLAN indicates
and the value 7
priority.
Issue 01 (2016-04-30)

1552

Configuration Guide
Parameter
Value Range
Default Value
Description
S-VLAN
0 to 7
l This parameter
priority of the egress
packets.
server-side VLAN,
and the value 7
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
(DS) field in the
the packet.
MPLS EXP
l Displays the MPLS

EXP value of egress
packets.
egress queue leaves
port obtains the
according to the
mappings between
PHB service classes
egress packet
obtained priority
value into the EXP
field of the egress
MPLS packet.
Issue 01 (2016-04-30)

1553

Configuration Guide

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.
Packet Type
cvlan
cvlan
l This parameter
the packet.
svlan
ip-dscp
mpls-exp
l The packets trusted by

the OptiX RTN 900
are the C_VLAN,
S_VLAN, IP DSCP
and MPLS packets
that contain the
C_VLAN priority,
S_VLAN priority,
DSCP value or MPLS
EXP value. By
default, the untrusted
packets are mapped to
the BE service class
for best-effort
forwarding.
NOTE
only trusts DSCP value.
MPLS/PWE3 services
MPLS EXP values.
l A QinQ-based NNI port
DSCP values or SVLAN priorities.
Issue 01 (2016-04-30)

1554

Configuration Guide
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.
Navigation Path
1.
Management > Diffserv Domain Management > Diffserv Domain Management
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
Mapping Relation
Name

relation of a DS domain.
Packet Type
CVLAN
CVLAN
The packets trusted by

the OptiX RTN 900 are
the C-VLAN, S-VLAN,
IP DSCP packets, and
MPLS packets that
respectively contain the
C-VLAN priority, SVLAN priority, IP DSCP
value and MPLS EXP
value. By default, the
untrusted packets are
mapped to the BE service
class for best-effort
forwarding.
SVLAN
IP-DSCP
MPLS-EXP
NOTE
only trusts DSCP
value.
MPLS/PWE3 services
MPLS EXP values.
l A QinQ-based NNI
port trusts only packets
with DSCP values or
S-VLAN priorities.
Issue 01 (2016-04-30)

1555

Configuration Guide
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 900, Mapping Relation ID is set to 1, and Mapping
Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
B.6.4.4 Parameter Description: Policy Management

This topic describes the parameters that are related to port policies.
Navigation Path
1.
2.
Click the CoS Configuration tab.
Parameters
Parameter
Value Range
Default Value
Description
Policy ID

the policy ID of the port.
Policy Name

or specifies the policy
name of the port.
WRR Scheduling Policy

the current WRR
scheduling policy.
Issue 01 (2016-04-30)

1556

Configuration Guide
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 900 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
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.
Issue 01 (2016-04-30)

1557

Configuration Guide
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)
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 900
supports the setting of
the SP+WRR
of the CoS queue
according to the
requirement, and
provides one or more
queues that comply
with the SP algorithm.
Except for the default
value, however, the
value of the WRR
and the value of the
SP 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
Issue 01 (2016-04-30)

1558

Configuration Guide
Parameter
Value Range
Default Value
Description
a 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
CIR(kbit/s)

information.
PIR(kbit/s)
If the rate of a packet is

higher than the PIR, it
enters the buffer queue
and then is forwarded at a
rate equal to the PIR.
CBS(byte)

information.
Issue 01 (2016-04-30)

1559

Configuration Guide
Parameter
Value Range
Default Value
Description
PBS(byte)
l When the buffer

queue is empty,
certain burst packets
can be forwarded if
the rate of the packets
is equal to or lower
than the PIR in a
certain period. The
maximum traffic of
the burst packets is
determined by the
PBS.
according to the
Tail Drop Threshold

(256 bytes)
Port WRED Policy
l Two port congestion

avoidance algorithms
are available: tail drop
and weighted random
early detection
(WRED).
l If tail drop is used, set
Tail Drop Threshold
(256 bytes) only.
l If WRED is used, set
Port WRED Policy
only.
B.6.4.5 Parameter Description: Port Policy

This topic describes the parameters that are used for creating port policies.
Navigation Path
1.
2.
Click New. The Create Port Policy dialog box is displayed.
3.
Parameters
Parameter
Value Range
Default Value
Description
Policy ID
This parameter
specifies the policy ID
of the port.
Issue 01 (2016-04-30)

1560

Configuration Guide
Parameter
Value Range
Default Value
Description
Assign Automatically
Selected
Deselected
This parameter
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.
This parameter
specifies the policy
name of the port.
Deselected
Policy Name
Issue 01 (2016-04-30)

1561

Configuration Guide
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%
Issue 01 (2016-04-30)

1562

Configuration Guide
Parameter
Value Range
Default Value
Description
respectively, the
actual bandwidth
allocation weight of
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Issue 01 (2016-04-30)

1563

Configuration Guide
Parameter
Value Range
Default Value
Description
CoS
CS7
l The BE, AF1, AF2,

AF3, AF4, EF, CS6,
and CS7 service
map eight queuing
entities. The OptiX
RTN 900 provides
different QoS
policies for the
queues at different
service class.
CS6
EF
AF4
AF3
AF2
AF1
BE
the highest service
grade, which is
mainly involved in
signaling
transmission.
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.
ensured forwarding.
applicable to the
rate guarantee but
does not require
delay or jitter limit.
l BE: indicates that
the traffic is
forwarded in besteffort manner
without special
processing.
Issue 01 (2016-04-30)

1564

Configuration Guide
Parameter
Value Range
Default Value
Description

Reloading
SP
WRR
AF4, AF3, AF2, AF1:

WRR

(SP) scheduling
algorithm is
designed for the
key services. One
important
required to
minimize the
response delay in
the case of
congestion events.
robin (WRR)
scheduling
algorithm divides
each port into
scheduling is
performed among
the output subqueues to ensure
that each sub-queue
has a certain period
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
Issue 01 (2016-04-30)

1565

Configuration Guide
Parameter
Value Range
Default Value
Description
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 This parameter is
planning
information.
Bandwidth Limitation
Disabled
Disabled
Enabled
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.
l This parameter is
planning
information.
CIR(kbit/s)
Issue 01 (2016-04-30)


according to the
1566

Configuration Guide
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.
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.
l This parameter is
planning
information.
CBS(byte)
Issue 01 (2016-04-30)


according to the
1567

Configuration Guide
Parameter
Value Range
Default Value
Description
PBS(byte)
l When the buffer

queue is empty,
certain burst
packets can be
forwarded if the
rate of the packets
than the PIR in a
certain period. The
maximum traffic of
determined by the
PBS.
l This parameter is
planning
information.
Tail Drop Threshold (256

bytes)
Port WRED Policy
l Two port
congestion
avoidance
algorithms are
available: tail drop
and weighted
random early
detection (WRED).
l If tail drop is used,
set Tail Drop
Threshold (256
bytes) only.
l If WRED is used,
set Port WRED
Policy only.
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 01 (2016-04-30)

1568

Configuration Guide

Parameter
Value Range
Default Value
Description
Traffic Classification ID
1 to 512

the ID of the traffic
classification.
ACL Action
Permit
Permit
l The access control list

(ACL) determines
whether to forward or
discard the packets
that enter the port
according to the
specified matching
rules.
Deny
l When ACL Action is

set to Permit, the
ingress port accepts
and then performs
QoS processing for
only the packets that
meet the specified
mapping rules.
l When ACL Action is
set to Deny, the
ingress port discards
the packets that meet
the specified mapping
rules.
Ingress Parameters
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 900
supports the setting of
the logical AND
between multiple
matching rules.
Issue 01 (2016-04-30)

1569

Configuration Guide
Parameter
Value Range
Default Value
Description
Match Type
DSCP Value
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.
CVlan ID
CVlan priority
SVlan ID
SVlan priority
Source MAC Address
Destination MAC
Address
l Traffic type is based

on the associated
Ethernet packets.
Therefore, this
parameter is set
according to the
packet type and the
Destination IP Address
Source IP Address
Protocol Type
Source Port
Destination Port
l Only OptiX RTN 950

housing CSHU/
CSHUA, OptiX RTN
950A, OptiX RTN
910A and OptiX RTN
905E support traffic
classification by IP
address, protocol
type, port number,
and ICMP type.
ICMP Packect Type Code
Match Value
l If the matching value

of the packets is the
same as the preset
Match Value, the
packets match the
rules of complex
l If Match Value is set
to 0 for the CVLAN
ID, all packets with
CVLAN IDs match
the rules of complex
If Match Value is set
to 0 for the SVLAN
ID, all packets with
SVLAN IDs match
the rules of complex
according to the
Issue 01 (2016-04-30)

1570

Configuration Guide
Parameter
Value Range
Default Value
Description
Wildcard
This parameter is
configurable for OptiX
RTN 950A, OptiX RTN
910A, 905 1E/2E, 950
(CSHU/CSHUA) and is
fixed to 0 for other
products.
NOTE
This parameter is
inconfigurable for the
VLAN and VLAN priority
of OptiX RTN 950A/950
(CSHU/CSHUA) and is
fixed to 0.
CoS
None
None
CS7
CS6
EF
AF4
l This parameter
specifies the PHB
service class queue
mapped by the traffic
classification packets.
to empty (-), the
packets map the PHB
service class queue
according the
mapping 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
and PBS (byte) can
be set only when
Bandwidth Limit is
set to Enabled.
according to the
Issue 01 (2016-04-30)

1571

Configuration Guide
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 01 (2016-04-30)

1572

Configuration Guide
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
priority of the
packets) and then
port. If a network
congestion event
occurs again, the
packets marked
yellow can be
processed according
to the new priority.
according to the
Issue 01 (2016-04-30)

1573

Configuration Guide
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,
are allowed and can
be first forwarded in
the case of network
congestion. The
maximum traffic of
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 maximum traffic
of the burst packets is
determined by the
PBS.
according to the
Coloring Mode
Issue 01 (2016-04-30)


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

Configuration Guide
Parameter
Value Range
Default Value
Description
Packet Color
Red
Packets can be dyed in

three colors: red, yellow,
and green. The packets in
red are first discarded.
l This parameter
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
priority of the
packets) and then
port.
Re-Mark CoS
CS7
CS6
EF
If the handling method is

set to "Remark", you can
reset the CoS of the
packets.
AF4
AF3
AF2
AF1
BE
Issue 01 (2016-04-30)

1575

Configuration Guide
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

and PBS (byte) can
be set only when
Bandwidth Limit is
set to Enabled.
according to the
CIR(kbit/s)
l In the case that no

packets exist in the
egress queue: When
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
passes the restriction
of the PIR directly
enter the egress
queue, which
forwards the packets
to the next port at the
CIR.
according to the
Issue 01 (2016-04-30)

1576

Configuration Guide
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
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
passes the restriction
of the PIR directly
enter the egress
queue, which
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 01 (2016-04-30)

1577

Configuration Guide
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
maximum traffic of
determined by the
PBS.
according to the
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 900
processes the packets in
the buffer queue through
the following methods
when no packets are
available in the queue.
l When the buffer
queue is empty, the
packets are processed
as follows: If the rate
Issue 01 (2016-04-30)

1578

Configuration Guide
Parameter
Value Range
Default Value
Description
PBS (bytes)
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,
can be forwarded if
than the PIR in a
certain period. The
maximum traffic of
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.
B.6.4.8 Parameter Description: Port WRED Policy_Create

This section describes parameters for creating a port WRED policy (WRED stands for
weighted random early detection).
Navigation Path
1.
Management > Policy Management > Port WRED Policy from the Function Tree.
2.
Click New.
Issue 01 (2016-04-30)

1579

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
Policy ID

WRED policy.
Assign automatically
Selected
Deselected

whether to automatically
assign a policy ID to the
WRED policy. If this
parameter is selected, the
policy ID for the WRED
policy is automatically
assigned.
Deselected
Policy Name

the policy name of the
WRED policy.
Packet Color
Green
Packets with different

colors have different
discard thresholds and
discard ratios. In the case
of congestion, lower
priority packets are
discarded first so that
higher priority packets
can pass.
Yellow
Red
Lower Discard
Threshold (256 bytes)
0 to 480
32
Upper Discard
0 to 480
80
Discard Rate (%)
0 to 100
40
If you want to first drop

red packets and then
yellow and green packets
when a queue is full, it is
configure the WRED
policy for the queue as
follows:
1. Low drop threshold
for green packets
High drop threshold
for yellow packets
for yellow packets
High drop threshold
for red packets
B.6.4.9 Parameter Description: Service WRED Policy_Create

This section describes parameters for creating a service WRED policy (WRED stands for
weighted random early detection).
Issue 01 (2016-04-30)

1580

Configuration Guide
Navigation Path
1.
Management > Policy Management > Service WRED Policy from the Function Tree.
2.
Click New.
Parameters
Parameter
Value Range
Default Value
Description
Policy ID

WRED policy.
Selected
Deselected

whether to automatically
assign a policy ID to the
WRED policy. If this
parameter is selected, the
policy ID for the WRED
policy is automatically
assigned.
Deselected
Policy Name

the policy name of the
WRED policy.
Packet Color
Green
Packets with different

colors have different
discard thresholds and
discard ratios. In the case
of congestion, lower
priority packets are
discarded first so that
higher priority packets
can pass.
Yellow
Red
Lower Discard
0 to 480
32
Upper Discard
0 to 480
80
Discard Rate (%)
0 to 100
40
If you want to first drop

red packets and then
yellow and green packets
when a queue is full, it is
configure the WRED
policy for the queue as
follows:
for green packets
High drop threshold
for yellow packets
for yellow packets
High drop threshold
for red packets
Issue 01 (2016-04-30)

1581

Configuration Guide
B.6.4.10 Parameter Description: WRR Scheduling Policy_Create

This section describes parameters for creating a WRR scheduling policy.
Navigation Path
1.
Management > Policy Management > WRR Scheduling Policy from the Function
Tree.
2.
Click New.
Parameters
Parameter
Value Range
Def
ault
Val
ue
Description
Policy ID

policy ID of the WRR scheduling
policy.
Policy Name

policy name of the WRR
scheduling policy.
Selected
Dese
lecte
d
This parameter specifies whether

to automatically assign a policy
ID to the WRED policy. If this
parameter is selected, the policy
ID for the WRED policy is
Deselected
Issue 01 (2016-04-30)

1582

Configuration Guide
Parameter
Value Range
Def
ault
Val
ue
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 parameters must be set to
a value rather than 0 for WRR
queues. If a WRR queue does
not carry services, it is advised
to set this parameter for the
WRR queue to a small
number. It is advised to set
this parameter for other WRR
queues to numbers without
any common divisors, for
example, 10:10:13.
B.6.4.11 Parameter Description: V-UNI Egress Policy

This topic describes the parameters that are used for creating V-UNI Egress policies.
Navigation Path
1.
Management > Policy Management > V-UNI Egress Policy from the Function Tree.
2.
Click New. The Create V-UNI Egress Policy dialog box is displayed.
Parameters
Parameter
Value Range
Default Value
Description
Policy ID
This parameter
of the port.
Issue 01 (2016-04-30)

1583

Configuration Guide
Parameter
Value Range
Default Value
Description
Selected
Deselected
This parameter
the system
set manually.
This parameter
name of the port.
Deselected
Policy Name
Issue 01 (2016-04-30)

1584

Configuration Guide
Parameter
Value Range
Default Value
Description
l This parameter
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
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
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%
Issue 01 (2016-04-30)

1585

Configuration Guide
Parameter
Value Range
Default Value
Description
respectively, the
actual bandwidth
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Issue 01 (2016-04-30)

1586

Configuration Guide
Parameter
Value Range
Default Value
Description
CoS
CS7
l The BE, AF1, AF2,

AF3, AF4, EF, CS6,
and CS7 service
map eight queuing
entities. The OptiX
RTN 900 provides
different QoS
policies for the
queues at different
service class.
CS6
EF
AF4
AF3
AF2
AF1
BE
the highest service
grade, which is
mainly involved in
signaling
transmission.
forwarding. This
service class is
applicable to the
traffic whose delay
is small and packet
example, voice and
video services.
ensured forwarding.
applicable to the
rate guarantee but
does not require
the traffic is
without special
processing.
Issue 01 (2016-04-30)

1587

Configuration Guide
Parameter
Value Range
Default Value
Description

Reloading
SP
WRR
AF4, AF3, AF2, AF1:

WRR

(SP) scheduling
algorithm is
designed for the
key services. One
important
required to
minimize the
response delay in
the case of
congestion events.
robin (WRR)
scheduling
algorithm divides
each port into
scheduling is
performed among
that each sub-queue
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
Issue 01 (2016-04-30)

1588

Configuration Guide
Parameter
Value Range
Default Value
Description
except for the
default value,
Grooming Police
After Reloading
can be changed
from SP to WRR
according to the
descending order
(CS7-BE).
l This parameter is
planning
information.
Disabled
Disabled
Enabled
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.
l This parameter is
planning
information.
CIR(kbit/s)
Issue 01 (2016-04-30)


according to the
1589

Configuration Guide
Parameter
Value Range
Default Value
Description
PIR(kbit/s)
l When the buffer

queue is empty, the
packets are
processed as
PIR, it is directly
forwarded; if the
rate of a packet is
queue and then is
forwarded at a rate
equal to the PIR.
l When the buffer
queue is not empty,
the packets whose
rate passes the
restriction of the
PIR directly enter
the buffer queue
and then are
forwarded at a rate
equal to the PIR.
l This parameter is
planning
information.
CBS(byte)
Issue 01 (2016-04-30)


according to the
1590

Configuration Guide
Parameter
Value Range
Default Value
Description
PBS(byte)
l When the buffer

queue is empty,
certain burst
packets can be
forwarded if the
rate of the packets
than the PIR in a
certain period. The
maximum traffic of
determined by the
PBS.
l This parameter is
planning
information.

bytes)
Port WRED Policy
l Two port
congestion
avoidance
algorithms are
and weighted
random early
detection (WRED).
set Tail Drop
Threshold (256
bytes) only.
l If WRED is used,
set Port WRED
Policy only.
B.6.4.12 Parameter Description: PW Policy

This topic describes the parameters that are used for creating PW policies.
Navigation Path
1.
Management > Policy Management > PW Policy from the Function Tree.
2.
Click New. The Create PW Policy dialog box is displayed.
Issue 01 (2016-04-30)

1591

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
Policy ID
This parameter
of the port.
Selected
Deselected
This parameter
the system
set manually.
This parameter
name of the port.
Deselected
Policy Name
Issue 01 (2016-04-30)

1592

Configuration Guide
Parameter
Value Range
Default Value
Description
l This parameter
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
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
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%
Issue 01 (2016-04-30)

1593

Configuration Guide
Parameter
Value Range
Default Value
Description
respectively, the
actual bandwidth
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Issue 01 (2016-04-30)

1594

Configuration Guide
Parameter
Value Range
Default Value
Description
CoS
CS7
l The BE, AF1, AF2,

AF3, AF4, EF, CS6,
and CS7 service
map eight queuing
entities. The OptiX
RTN 900 provides
different QoS
policies for the
queues at different
service class.
CS6
EF
AF4
AF3
AF2
AF1
BE
the highest service
grade, which is
mainly involved in
signaling
transmission.
forwarding. This
service class is
applicable to the
traffic whose delay
is small and packet
example, voice and
video services.
ensured forwarding.
applicable to the
rate guarantee but
does not require
the traffic is
without special
processing.
Issue 01 (2016-04-30)

1595

Configuration Guide
Parameter
Value Range
Default Value
Description

Reloading
SP
WRR
AF4, AF3, AF2, AF1:

WRR

(SP) scheduling
algorithm is
designed for the
key services. One
important
required to
minimize the
response delay in
the case of
congestion events.
robin (WRR)
scheduling
algorithm divides
each port into
scheduling is
performed among
that each sub-queue
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
Issue 01 (2016-04-30)

1596

Configuration Guide
Parameter
Value Range
Default Value
Description
except for the
default value,
Grooming Police
After Reloading
can be changed
from SP to WRR
according to the
descending order
(CS7-BE).
l This parameter is
planning
information.
Disabled
Disabled
Enabled
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.
l This parameter is
planning
information.
CIR(kbit/s)
Issue 01 (2016-04-30)


according to the
1597

Configuration Guide
Parameter
Value Range
Default Value
Description
PIR(kbit/s)
l When the buffer

queue is empty, the
packets are
processed as
PIR, it is directly
forwarded; if the
rate of a packet is
queue and then is
forwarded at a rate
equal to the PIR.
l When the buffer
queue is not empty,
the packets whose
rate passes the
restriction of the
PIR directly enter
the buffer queue
and then are
forwarded at a rate
equal to the PIR.
l This parameter is
planning
information.
CBS(byte)
Issue 01 (2016-04-30)


according to the
1598

Configuration Guide
Parameter
Value Range
Default Value
Description
PBS(byte)
l When the buffer

queue is empty,
certain burst
packets can be
forwarded if the
rate of the packets
than the PIR in a
certain period. The
maximum traffic of
determined by the
PBS.
l This parameter is
planning
information.

bytes)
Port WRED Policy
l Two port
congestion
avoidance
algorithms are
and weighted
random early
detection (WRED).
set Tail Drop
Threshold (256
bytes) only.
l If WRED is used,
set Port WRED
Policy only.
B.6.4.13 Parameter Description: QinQ Policy

This topic describes the parameters that are used for creating QinQ policies.
Navigation Path
1.
Management > Policy Management > QinQ Policy from the Function Tree.
2.
Click New. The Create QinQ Policy dialog box is displayed.
Issue 01 (2016-04-30)

1599

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
Policy ID
This parameter
of the port.
Selected
Deselected
This parameter
the system
set manually.
This parameter
name of the port.
Deselected
Policy Name
Issue 01 (2016-04-30)

1600

Configuration Guide
Parameter
Value Range
Default Value
Description
l This parameter
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
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
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%
Issue 01 (2016-04-30)

1601

Configuration Guide
Parameter
Value Range
Default Value
Description
respectively, the
actual bandwidth
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.
Issue 01 (2016-04-30)

1602

Configuration Guide
Parameter
Value Range
Default Value
Description
CoS
CS7
l The BE, AF1, AF2,

AF3, AF4, EF, CS6,
and CS7 service
map eight queuing
entities. The OptiX
RTN 900 provides
different QoS
policies for the
queues at different
service class.
CS6
EF
AF4
AF3
AF2
AF1
BE
the highest service
grade, which is
mainly involved in
signaling
transmission.
forwarding. This
service class is
applicable to the
traffic whose delay
is small and packet
example, voice and
video services.
ensured forwarding.
applicable to the
rate guarantee but
does not require
the traffic is
without special
processing.
Issue 01 (2016-04-30)

1603

Configuration Guide
Parameter
Value Range
Default Value
Description

Reloading
SP
WRR
AF4, AF3, AF2, AF1:

WRR

(SP) scheduling
algorithm is
designed for the
key services. One
important
required to
minimize the
response delay in
the case of
congestion events.
robin (WRR)
scheduling
algorithm divides
each port into
scheduling is
performed among
that each sub-queue
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be
Issue 01 (2016-04-30)

1604

Configuration Guide
Parameter
Value Range
Default Value
Description
except for the
default value,
Grooming Police
After Reloading
can be changed
from SP to WRR
according to the
descending order
(CS7-BE).
l This parameter is
planning
information.
Disabled
Disabled
Enabled
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.
l This parameter is
planning
information.
CIR(kbit/s)
Issue 01 (2016-04-30)


according to the
1605

Configuration Guide
Parameter
Value Range
Default Value
Description
PIR(kbit/s)
l When the buffer

queue is empty, the
packets are
processed as
PIR, it is directly
forwarded; if the
rate of a packet is
queue and then is
forwarded at a rate
equal to the PIR.
l When the buffer
queue is not empty,
the packets whose
rate passes the
restriction of the
PIR directly enter
the buffer queue
and then are
forwarded at a rate
equal to the PIR.
l This parameter is
planning
information.
CBS(byte)
Issue 01 (2016-04-30)


according to the
1606

Configuration Guide
Parameter
Value Range
Default Value
Description
PBS(byte)
l When the buffer

queue is empty,
certain burst
packets can be
forwarded if the
rate of the packets
than the PIR in a
certain period. The
maximum traffic of
determined by the
PBS.
l This parameter is
planning
information.

bytes)
Port WRED Policy
l Two port
congestion
avoidance
algorithms are
and weighted
random early
detection (WRED).
set Tail Drop
Threshold (256
bytes) only.
l If WRED is used,
set Port WRED
Policy only.
B.6.5 Parameter Description: IP Packet Marking and Statistics

Collection
This section describes the parameters related to IP packet marking and statistics collection.
Navigation Path
Click a desired NE in the NE Explorer and choose Diagnose&Maintenance > IP Packet
Marking from the main menu.
Issue 01 (2016-04-30)

1607

Configuration Guide
Table B-14 Parameters on the Main Interface

Parameter
Value Range
Default Value
Description
Set IP mark bits
l IP FLAG BIT0
IP FLAG BIT0
Set the flag bit of the

marked packets, which is
used to count the packets.
l IP TOS BIT3
l IP TOS BIT4
l IP TOS BIT5
l IP TOS BIT6
l IP TOS BIT7
ID
1 to 5
Display or set the ID.
Automatically Assign
l Checked
Unchecked
Set the automatically

assign.
l Unchecked
The test ID will be

assigned automatically if
this parameter is
checked.
Name
Display or set the name.
Role
l Upstream
Intermediate
Display and set the role

of the test packets.
Collect only
Set the function of the

testing.
Display and set the time

for automatically
stopping.
l Intermediate
l Downstream
Action
l Collect only
l Mark and collect
l Restore and collect
Auto Stop After

(minutes)
Issue 01 (2016-04-30)
1 to 10080

1608

Configuration Guide
Parameter
Value Range
Default Value
Description
Logical Relation Between

Matched Rules
l And
And
Specifies the logical

matched rules.
l Or
l And indicates that the

packet matches the
flow only when the
packet matches each
rules.
l Or indicates that the
packet matches the
flow when the packet
matches one of the
rules.
NOTE
The equipment supports
only And.
Match Type
l Outer VLAN
Set the match type.
Specifies the Match

Value of each match
type.
l Inner VLAN
l Outer VLAN Priority
l Inner VLAN Priority
l Outer VLAN Drop
Priority
l DSCP Value
l Destination MAC
Address
l Source MAC Address
l Protocol Type
l Destination IP
Address
l Source IP Address
l Destination Port
l Source Port
l Inner VLAN Drop
Priority
l Ethernet Type
l ICMP Packet Type
Code
Match Value
Issue 01 (2016-04-30)

1609

Configuration Guide
Parameter
Value Range
Default Value
Description
Wildcard
Specifies the Wildcard

of the match value.
Adopt 0 for strictly
matched bits, and 1 for
unconcerned bits.
Rules
Example: {Outer VLAN:

1:0}&{Inner VLAN:2:0}
Display and set the rules

for marking. The
conformed packets will
be marked.
Status
l Stop
Stop
Display and set the

testing status.
l Start
Number of Marked
Packets
Display the number of

the marked packets after
testing.
Number of Marked Bytes

the marked bytes after
testing.
Number of Unmarked
Packets

the unmarked packets
after testing.
Number of Unmarked
Bytes

the unmarked packets
after testing.
Table B-15 VUNI parameters

Parameter
Value Range
Default Value
Description
Direction
l Transmit
Display the direction

for the test packets.
l Receive
Service
Display and set the

service ID.
Port
Display and set the

port number.
VLAN
1 to 4094
Display and set the

VLAN ID.
Only the VLANs
with service could
be chosen.
Issue 01 (2016-04-30)

1610

Configuration Guide
Table B-16 QinQ parameters

Parameter
Value Range
Default Value
Description
Direction
l Transmit

l Receive
Service
Display and set the

service ID.
QinQ
Display and set the

QinQ ID.
Table B-17 Tunnel parameters

Parameter
Value Range
Default Value
Description
Direction
l Transmit

l Receive
Tunnel ID
Indicates the tunnel

ID.
Port
Display and set the

port number.
PW Label
Display and set the

PW label.
Service Tag Role
l User
User
Display the service

tag role of E-LAN
service.
Ethernet
Set the PW type.
l Service
l Ethernet
PW Type
PWs of different
types process the
borne services
differently. For
example, the PW in
the Ethernet tagged
mode attaches the
tag on the services
on this PW.
l Ethernet Tag
Mode
Request VLAN
TPID
Specifies the type

field of the request
VLAN when the PW
type is Ethernet
Tagged Mode.
PW Control Word
l Not in use
Not in use
Display the control

word of the PW.
l Used first
l Use required
Issue 01 (2016-04-30)

1611

Configuration Guide
Parameter
Value Range
Default Value
Description
UNI Port
Encapsulation Type
l NULL
NULL
Indicates the way in

which the port
processes accessed
packets.
l C-Tag
l S-Tag
UNI Port TPID
Specifies the type

field of the UNI port
TPID.
Service Type
l E-Line service
E-LAN service
Specifies the type

field of the Service
Type.
Indicates the TPID

of S-VLAN tags in
the PW user packets
of a VPLS service.
l E-LAN service
l E-AGGR service
S-TAG TPID
B.7 Parameters for Ethernet Services and Ethernet Features

on the EoS/EoPDH Plane
EoS/EoPDH plane, including service parameters, protocol parameters, OAM parameters,
Ethernet port parameters, and QoS parameters.
NOTE
OptiX RTN 905/910A does not support the Ethernet services on EoS/EoPDH boards.
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.
Issue 01 (2016-04-30)

1612

Configuration Guide

Parameter
Value Range
Default Value
Description
Board
Displays the board name.
Service Type
EPL
EPL
Specify the Ethernet service type to EPL.
Service Direction
Bidirectional
Bidirectional
l If this parameter is set to

Unidirectional, 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 example, the numbers 1, and 3-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 01 (2016-04-30)

1613

Configuration Guide
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 example, the numbers 1, and 3-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-19 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 01 (2016-04-30)

1614

Configuration Guide
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-20 Parameters for bound paths

Parameter
Value Range
Default Value
Description
VCTRUNK Port
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 VC12Xv.
Service Direction
Bidirectional
Bidirectional
Uplink
l Set this parameter to Bidirectional

unless otherwise specified.
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 01 (2016-04-30)

1615

Configuration Guide
Parameter
Value Range
Default Value
Description
Bound Path Count
Displays the number of the bound VC

path.
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
Defau
lt
Value
Description
Board
Displays the
board name.
Service Type
EPL
EPL
Specifies the
service type to
EVPL(QinQ).
EVPL(
QinQ)
Issue 01 (2016-04-30)

1616

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
Service Direction
Bidire
ctional
Bidirec
tional
l When this
parameter is
set to
Unidirection
al, 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.
Unidir
ectiona
l
l When this
parameter is
set to
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.
l It is
recommende
d that you set
this
parameter to
Issue 01 (2016-04-30)

1617

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
Bidirectional
.
Issue 01 (2016-04-30)

1618

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
Operation Type
l Ad
d
SVL
AN
Strip
SVLAN
l When used
for private
line services,
QinQ can
process
VLAN tags
in different
manners as
required.
l Tra
nsp
are
ntly
tran
smi
t CVL
AN
l Tra
nsp
are
ntly
tran
smi
t SVL
AN
l Tra
nsp
are
ntly
tran
smi
t SVL
AN
and
CVL
AN
l When
Service
Direction is
set to
Unidirection
al, you can
set
Operation
Type to Strip
S-VLAN.
l Set this
parameter
according to
actual
situations.
l Tra
nsl
ate
SVL
AN
l Tra
nsl
ate
S-
Issue 01 (2016-04-30)

1619

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
l Specifies the
port where
the service
source
resides.
VL
AN
and
tran
spa
rent
ly
tran
smi
t CVL
AN
l Stri
p
SVL
AN
Source Port
l When
creating a
bidirectional
Ethernet
service from
a PORT to a
VCTRUNK,
it is
recommende
d that you use
the PORT as
the source
port.
Issue 01 (2016-04-30)

1620

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
Source 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 CVLAN(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
Issue 01 (2016-04-30)

1621

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
a non-null
value, only
the services
of the source
port whose
VLAN IDs
are included
in the value
range of this
parameter
work as the
service
source.
Source S-VLAN
1-4095
l This
parameter
must be set to
a numerical
value.
l Only the
service of the
source port
whose SVLAN ID is
equal to the
value of this
parameter
work as the
service
source.
Issue 01 (2016-04-30)

1622

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
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
recommende
d that you use
the
VCTRUNK
as the sink
port.
Issue 01 (2016-04-30)

1623

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
Sink 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 non-null
Issue 01 (2016-04-30)

1624

Configuration Guide
Parameter
Value
Range
Defau
lt
Value
Description
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 SVLAN IDs
are equal to
the value of
this
parameter
work as the
service sink.
C-VLAN Priority
AUTO
AUTO
Displays the CVLAN priority.
S-VLAN Priority
AUTO
AUTO
Specifies the SVLAN priority.

The bigger the
value, the higher
the priority.
Priorit
y 0 to
Priorit
y7
Table B-22 Parameters of port attributes

Parameter
Value
Range
Default
Value
Description
Port
Displays the ports that

are configured to
transmit the service.
Issue 01 (2016-04-30)

1625

Configuration Guide
Parameter
Value
Range
Default
Value
Description
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.
TAG
This parameter is
invalid for QinQ line
services.

Parameter
Value
Range
Default
Value
Description
VCTRUNK Port
EFP8:
VCTRUN
K1VCTRUN
K16
VCTRUN
K1
Specifies the
VCTRUNK to bind
paths.
Displays the level of

the bound VC path.
EMS6:
VCTRUN
K1VCTRUN
K8
Level
In the case of the EFP8

board, this parameter
always takes the value
of VC12-Xv.
Issue 01 (2016-04-30)

1626

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Service Direction
Bidirection
al
Bidirectio
nal
l Specifies the
direction of the
bound path.
Uplink

to Bidirectional
unless otherwise
specified.
Downlink
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.
Bound Path Count
Displays the number of

the bound VC path.
B.7.1.3 Parameter Description: Ethernet Line Service

This section describes the parameters for Ethernet line services.
Issue 01 (2016-04-30)

1627

Configuration Guide
Navigation Path

Table B-24 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.
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-25 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.
Issue 01 (2016-04-30)

1628

Configuration Guide
Parameter
Value Range
Default Value
Description
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-26 Parameters for port attributes

Parameter
Value Range
Default Value
Description
Port
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

paths.
Issue 01 (2016-04-30)

1629

Configuration Guide
Parameter
Value Range
Default Value
Description
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.

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
802.1ad
Issue 01 (2016-04-30)
l If this parameter is set to 802.1d, an

IEEE 802.1d bridge is created.

1630

Configuration Guide
Parameter
Value Range
Default Value
Description
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 IVL/Ingress
Filter Enable
(IEEE 802.1q
bridge and the
IEEE 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, each VLAN has an MAC
address table.
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 SVL/Ingress
Filter Disable
(IEEE 802.1d
bridge)
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
Self-learning
Displays whether the MAC address selflearning of the bridge is enabled.
Active
Table B-29 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 mounted to the bridge.
Port Type
Displays the network attribute of the port

mounted to the bridge.
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.
Enabled
TAG
Access
Tag Aware
Hybrid
Issue 01 (2016-04-30)

1631

Configuration Guide
Parameter
Value Range
Default Value
Description
Default VLAN ID
Displays or specifies the default VLAN ID

of the port mounted to the bridge.
This parameter is valid only when you set
the tag attribute of the port to Access or
Hybrid.
Working Mode
Auto-Negotiation
Displays or specifies the working mode of

10M Half-Duplex
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

S-VLAN

S-VLAN Priority

C-VLAN Priority

Table B-30 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 Mounted
Ports
Displays which physical port or

VCTRUNK on the Ethernet switch board
is mounted to the bridge.
Issue 01 (2016-04-30)

1632

Configuration Guide

Parameter
Value Range
Default Value
Description
VCTRUNK Port
EFP8:
VCTRUNK1VCTRUNK16
VCTRUNK1
EMS6:
VCTRUNK1VCTRUNK8
Level

parameter always takes the value of
VC12-Xv.
Service Direction
Bidirectional
Bidirectional
Uplink

Downlink
Bound Path

path.

recommended.
Bound Path Count

path.
Activation Status
Displays the activation status of the

bound VC path.
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.
Issue 01 (2016-04-30)

1633

Configuration Guide
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.
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.
802.1d
802.1ad
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 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
Self-learning
Displays whether the MAC address selflearning function of the bridge is enabled.
Issue 01 (2016-04-30)

1634

Configuration Guide
Table B-33 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.
Enabled
TAG
This parameter is invalid in the case of

Ethernet LAN services based on 802.1ad
bridge.
Default VLAN ID
Displays or specifies the default VLAN

ID.
This parameter is valid only when TAG is
set to Access or Hybrid.
Working Mode
Auto-Negotiation
Auto-Negotiation
Displays or specifies the working mode of

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.
Issue 01 (2016-04-30)

1635

Configuration Guide
Parameter
Value Range
Default Value
Description
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
S-VLAN ID to be added and the CVLAN 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 the IEEE 802.1ad bridge.
S-VLAN Priority
Displays or specifies the S-VLAN priority.
C-VLAN Priority
Displays or specifies the C-VLAN priority.
Table B-34 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.
Issue 01 (2016-04-30)

1636

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
S-VLAN
1-4095
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
S-VLAN ID to be added and the CVLAN ID carried by the data frames
that enter the IEEE 802.1ad bridge.
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
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 Port
EFP8:
VCTRUNK1VCTRUNK16
VCTRUNK1
EMS6:
VCTRUNK1VCTRUNK8
Issue 01 (2016-04-30)

1637

Configuration Guide
Parameter
Value Range
Default Value
Description
Level

parameter always takes the value of VC12Xv.
Service Direction
Bidirectional
Bidirectional
Uplink

Downlink
Bound Path

path.

recommended.
Bound Path Count

path.
B.7.1.6 Parameter Description: Ethernet LAN Service

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.
Issue 01 (2016-04-30)

1638

Configuration Guide
Parameter
Value Range
Default Value
Description
VB ID
Displays the ID of the bridge.
VB Name
This parameter is a character string that

describes the bridge. It is recommended
that you set this character string to a value
that indicates the specific purpose of the
bridge.
Bridge Type
Displays the type of the bridge.
Bridge Switch
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-37 Parameters for mounting services

Parameter
Value Range
Default Value
Description
VB Port
Displays the ID of the logical port

of the bridge.
Mount Port
Displays or specifies which

physical port or VCTRUNK on the
Ethernet switch board is mounted
to the bridge.
Port Type
Displays the network attribute of

Port Enabled
Displays or specifies whether the

port mounted to the bridge is
enabled.
Issue 01 (2016-04-30)

1639

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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.
you set the tag attribute of the port
to Access or Hybrid.
Working Mode
Displays or specifies the working

mode of the port mounted to the
bridge.
Active
Displays the activation status of

the bound VC path.
Service Direction
Displays the direction of the

service.
C-VLAN
Displays or specifies the C-VLAN

ID carried by the data frame.
the bridge is an IEEE 802.1ad
bridge and Operation Type is
Add S-VLAN Base for Port and
C-VLAN.
mapping relation between the CVLAN tag carried by the data
frame and the S-VLAN tag to be
added.
Issue 01 (2016-04-30)

1640

Configuration Guide
Parameter
Value Range
Default Value
Description
S-VLAN
Displays or specifies the S-VLAN

ID carried by the data frame.
l When Operation Type is set to
Add S-VLAN Base for Port,
this parameter specifies the SVLAN to be added to the data
frames that enter the IEEE
802.1ad bridge.
Add S-VLAN Base for Port
and C-VLAN, this parameter
and C-VLAN specify the
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.
Mount Port, this parameter is
invalid.
Mount Port and Base for Port
and S-VLAN, this parameter
specifies the S-VLAN tag to be
carried by the data frames that
S-VLAN Priority
Displays the priority of the SVLAN.
C-VLAN Priority
Displays the priority of the CVLAN.
Table B-38 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 01 (2016-04-30)

1641

Configuration Guide
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-39 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 01 (2016-04-30)

bridge.

1642

Configuration Guide
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-40 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 01 (2016-04-30)

1643

Configuration Guide
Table B-42 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.
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-43 Parameters for VLAN MAC address table capacity

Parameter
Value Range
Default Value
Description
VLAN
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-44 Parameters for VB port MAC address table capacity

Parameter
Value Range
Default Value
Description
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 01 (2016-04-30)

1644

Configuration Guide
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
Displays the ports mounted to the bridge.
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.
Issue 01 (2016-04-30)

1645

Configuration Guide
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.
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.
B.7.2 Parameters for Ethernet Protocols

This section describes the parameters for EoS/EoPDH-plane Ethernet protocols.
B.7.2.1 Parameter Description: ERPS Management_Creation

This topic describes the parameters that are used for creating ERPS management tasks.
Issue 01 (2016-04-30)

1646

Configuration Guide
Navigation Path
1.
In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet
2.
Click New.
Parameters
Parameter
Value Range
Default Value
Description
ERPS ID
1 to 7
l This parameter
Ethernet ring
protection switching
(ERPS) instance.
l The IDs of ERPS
instances on an NE
must be different from
each other.
East Port

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
specifies whether the
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
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.
Issue 01 (2016-04-30)

1647

Configuration Guide
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.
l It is recommended
that you set the east
port on an RPL owner
as an RPL Port.
Control VLAN
1 to 4094
l This parameter
specifies the VLAN
ID of Control
VLAN.
l Each node on the
Ethernet ring
transmits the R-APS
packets on the
dedicated ring APS
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
isolating the dedicated
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
that are contained in
the service packets.
l The ID of a Control
VLAN must not be
the same as any
VLAN ID used by
Ethernet services. All
ring nodes should use
the same Control
VLAN ID.
Issue 01 (2016-04-30)

1648

Configuration Guide
Parameter
Value Range
Default Value
Description
Destination Node
01-19-A7-00-00-01
01-19-A7-00-00-01

default destination MAC
address in the R-APS
packets is always 01-19A7-00-00-01.
Loop Detect
Enabled
Enabled

the Loop Detect.
Disabled
B.7.2.2 Parameter Description: ERPS Management

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
This parameter
indicates the ID of
the ERPS instance.
East Port
This parameter
indicates the east
port of the ERPS
instance.
West Port
This parameter
indicates the west
port of the ERPS
instance.
RPL Owner Ring Node Flag
Yes
This parameter
indicates whether a
node on the ring is
the ring protection
link (RPL) owner.
This parameter
indicates the RPL
port.
No
RPL Port
Issue 01 (2016-04-30)

1649

Configuration Guide
Parameter
Value Range
Default Value
Description
Control VLAN
1 to 4094
l This parameter
indicates or
specifies the
VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring
transmits the RAPS packets on
the dedicated ring
APS (R-APS)
channel to ensure
consistency
between the
nodes when the
ERPS switching
is performed.
Control VLAN
is used for
isolating the
dedicated R-APS
channel.
Therefore, the
VLAN ID in
Control VLAN
cannot be
duplicate with the
VLAN IDs that
are contained in
the service
packets or inband
DCN packets.
l The Control
VLAN must be
set to the same
value for all the
NEs on an ERPS
ring.
Destination Node
Issue 01 (2016-04-30)
01-19-A7-00-00-01

This parameter
indicates the MAC
address of the
default destination
MAC address in the
R-APS packets is
always 01-19A7-00-00-01.
1650

Configuration Guide
Parameter
Value Range
Default Value
Description
Hold-Off Time(ms)
l This parameter
indicates or
specifies the
hold-off time of
the ERPS holdoff 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 holdoff time is set to a
value that is not
0. During the
hold-off time, the
fault is not
reported to trigger
an ERPS. When
the hold-off timer
times out, the
node checks the
link status
regardless
whether the fault
that triggers the
startup of the
timer exists. If the
fault exists, the
node reports it to
trigger an ERPS.
This fault can be
Issue 01 (2016-04-30)

1651

Configuration Guide
Parameter
Value Range
Default Value
Description
the same as or
different from the
fault that triggers
the initial startup
of the hold-off
timer.
Issue 01 (2016-04-30)

1652

Configuration Guide
Parameter
Value Range
Default Value
Description
Guard Time(ms)
500
l This parameter
indicates or
specifies the
guard time of the
ERPS guard
timer.
l The nodes on the
ring continuously
forward the RAPS packets to
the Ethernet ring.
As a result, the
outdated R-APS
packets may exist
on the ring
network. After a
node on the ring
receives the
outdated R-APS
packets, an
incorrect ERPS
may occur. The
ERPS guard timer
is an R-APS
timer used for
preventing a node
on the ring from
receiving
outdated R-APS
packets. When a
faulty node on the
ring detects that
the switching
condition is
cleared, the node
starts up the
guard timer and
starts to forward
the R-APS (NR)
packets. During
this period, the RAPS packets
received by the
node are
discarded. The
received R-APS
packets are
forwarded only
after the time of
Issue 01 (2016-04-30)

1653

Configuration Guide
Parameter
Value Range
Default Value
Description
the guard timer
expires.
Issue 01 (2016-04-30)

1654

Configuration Guide
Parameter
Value Range
Default Value
Description
WTR Time(mm:ss)
l This parameter
indicates or
specifies the
WTR time of the
WRT timer in the
case of ERPS
protection.
l The WTR time
refers to the
duration from the
time when the
working channel
is restored to the
time when the
switching is
released. When
the working
channel is
restored, the
WTR timer of the
RPL owner starts
up. In addition, a
signal that
indicates the
operation of the
WTR timer is
continuously
output in the
timing process.
When the WTR
timer times out
and no switching
request of a
higher priority is
received, the
signal indicating
the operation of
the WTR timer is
not transmitted.
In addition, the
WTR release
signal is
continuously
output.
l The WTR timer
is used to prevent
frequent
switching caused
by the unstable
working channel.
Issue 01 (2016-04-30)

1655

Configuration Guide
Parameter
Value Range
Default Value
Description
Packet Transmit Interval(s)
1 to 10
This parameter
the interval for
sending R-APS
packets periodically.
Entity Level
0 to 7
This parameter
the level of the
maintenance entity.
Last Switching Request
This parameter
indicates the last
switching request.
RB Status
This parameter
indicates the RB
(RPL Blocked) status
of the packets
received by the
working node.
l noRB: The RPL
is not blocked.
l RB: The RPL is
blocked.
Issue 01 (2016-04-30)

1656

Configuration Guide
Parameter
Value Range
Default Value
Description
DNF Status
This parameter
indicates the DNF
status of the packets
received by the
working node.
l noDNF: The RAPS packets do
not contain the
DNF flag. In this
case, the packets
are forwarded by
the node that
detects the fault
on a non-RPL
link, and the node
that receives the
packets is
requested to clear
the forwarding
address table.
l DNF: The R-APS
packets contain
the DNF flags. In
this case, the
packets are
forwarded by the
node that detects
the fault on an
RPL link, and the
node that receives
the packets is
informed not to
clear the
forwarding
address table.
Issue 01 (2016-04-30)

1657

Configuration Guide
Parameter
Value Range
Default Value
Description
State Machine Status
This parameter
the state machine at
the working node.
l Idle: The Ethernet
ring is in normal
state. For
example, no node
on the Ethernet
ring detects any
faults or receives
the R_APS (NR,
RB) packets.
l Protection: The
Ethernet ring is in
protected state.
For example, a
fault on the node
triggers the
ERPS, or a node
on the ring is in
the WTR period
after the fault is
rectified.
Node Carried with Current Packet
This parameter
indicates the MAC
address carried in the
R-APS packets
received by the
current node. The
MAC address refers
to the MAC address
of the source node
that initiates the
switching request.
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.
In 1the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Tree.
2.
Click the Protocol Enabled tab.
Issue 01 (2016-04-30)

1658

Configuration Guide

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
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters

This section describes the parameters for the spanning tree protocol.
Navigation Path
1.
Tree.
2.

Parameter
Value Range
Default Value
Description
VB
Issue 01 (2016-04-30)

1659

Configuration Guide
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.
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.
Issue 01 (2016-04-30)

1660

Configuration Guide
Navigation Path
1.
2.
Click the Port Parameters tab.

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.
Protocol Enabled
Enabled
Disabled
Enabled
l Specifies whether the STP or RSTP is

enabled for the port.
l When this parameter is set to Disabled,
the port does not process or transmit
the BPDU.
Issue 01 (2016-04-30)

1661

Configuration Guide
Parameter
Value Range
Default Value
Description
Auto Edge
Detection
Enabled
Disabled
l Is valid only when Admin Edge

Attribute is set to Enabled.
Disabled

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.
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
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.
Issue 01 (2016-04-30)

1662

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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
Navigation Path
1.
2.
Click the Port Running Information tab.

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
ID
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.
Issue 01 (2016-04-30)

1663

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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
Navigation Path
1.
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.
Issue 01 (2016-04-30)

1664

Configuration Guide
Parameter
Value Range
Default Value
Description
Point-to-point
Attribute
Adaptive
connection
Adaptive
connection
l This parameter is valid only when the

RSTP is used.
Link connection
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-topoint attribute of the port is True. If the
port works in half-duplex mode, the
actual point-to-point attribute of the
port is False.
Shared media
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.
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling

This section describes the parameters for enabling the IGMP snooping protocol.
Navigation Path
1.
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from
the Function Tree.
2.
Click the Enable IGMP Snooping Protocol tab.

Parameter
Value Range
Default Value
Description
Board
VB
Issue 01 (2016-04-30)

1665

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
Max.NonResponse Times
1 to 4
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 no-response times of the
port exceed the preset threshold, the bridge
deletes the multicast member from the
multicast group.
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.
the Function Tree.
2.
Click the Static Multicast Table tab.
Issue 01 (2016-04-30)

1666

Configuration Guide
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.
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.
the Function Tree.
2.
Click the Multicast Aging Time tab.

Parameter
Value Range
Default Value
Description
Board
Issue 01 (2016-04-30)

1667

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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.
Specifies the LAG name.
EMS6: 1-8
LAG Name
Issue 01 (2016-04-30)

1668

Configuration Guide
Parameter
Value Range
Default Value
Description
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 reallocated.
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 01 (2016-04-30)
IP Sharing Mode
You can set this parameter only when

Load Sharing is Sharing.

1669

Configuration Guide
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.
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation

This section describes the parameters for port priorities and system priorities.
Navigation Path
1.
2.
Click the Link Aggregation Parameters tab.
Issue 01 (2016-04-30)

1670

Configuration Guide

Parameter
Value Range
Default Value
Description
Port
Port Priority
0-65535
32768

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

LAG Type of a LAG is set to Static.
l This parameter indicates the priority of
a LAG. The smaller the value, the
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
Displays the MAC address of the system.
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.
Issue 01 (2016-04-30)

1671

Configuration Guide
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 01 (2016-04-30)

1672

Configuration Guide
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
l This parameter is valid only in the
reverse direction of LPT.
B.7.2.15 Parameter Description: LPT Management_Creation of Point-toMultipoint 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

the selected port is a VCTRUNK.
GFP-CSF
Port Hold-Off
Time(ms)
Issue 01 (2016-04-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

1673

Configuration Guide
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

the selected port is a VCTRUNK.
GFP-CSF
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
Issue 01 (2016-04-30)
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 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.

1674

Configuration Guide
Parameter
Value Range
Default Value
Description
Mirrored
Downstream 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 01 (2016-04-30)

1675

Configuration Guide
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)
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.
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs

This section describes the parameters for creating a maintenance point (MP).
Issue 01 (2016-04-30)

1676

Configuration Guide
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.
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).
Common MP:
00-00-0000 to FFFF-FF00
Type
MEP
MIP
Issue 01 (2016-04-30)

1677

Configuration Guide
Parameter
Value Range
Default Value
Description
Service Direction
SDH
SDH
l Specifies the MEP direction.
IP
l Set this parameter to SDH if the OAM

data initiated by the MEP travels
through the Ethernet switching unit on
the local NE. Otherwise, set this
parameter to IP.

Table B-56 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.
LT Timeout(ms)
3000 to 60000, in
step of 100
5000
l Specifies the timeout duration of an LT

test.
MEP.
Issue 01 (2016-04-30)

1678

Configuration Guide
Parameter
Value Range
Default Value
Description
CCM Sending
Period(ms)
Standard MP:
Standard MP
1000
1000
10000
Common MP:
Specifies the interval for sending the CCM

packet at the MP where the CC test is
performed.
6000
5000
600000
Common MP:
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.
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

sink maintenance point in
the LB test.
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
only for a standard MP.
Issue 01 (2016-04-30)

1679

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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.
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.
Issue 01 (2016-04-30)

1680

Configuration Guide
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.
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function
Tree.
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.
OAM Working Mode
Active
Active
Passive
The negotiation mode of

Ethernet port OAM
includes active and
passive modes.
If this parameter is set to
Active, the port can
initiate an OAM
connection. If this
parameter is set to
Passive, the port can only
respond to the OAM
connection requests from
the opposite end.
Enabled
Enabled
Disabled
Issue 01 (2016-04-30)


detected link event is
notified to the opposite
end (for example, error
frame periods, error
frames, and error frame
seconds).
1681

Configuration Guide
Parameter
Value Range
Default Value
Description
Max OAM Packet

Length(byte)
Displays the maximum

length of the OAM
packets.
This parameter takes the
same value as the
Maximum Frame
Length (bytes) of the
external port.
Loopback Status
Displays the loopback

status.
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.
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function
Tree.
2.
Click the OAM Error Frame Monitor tab.

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.
Issue 01 (2016-04-30)

1682

Configuration Guide
Parameter
Value Range
Default Value
Description
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)
1
Specifies the threshold of monitoring error

frame seconds.
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.
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.
Issue 01 (2016-04-30)

1683

Configuration Guide
Field
Value Range
Default Value
Description

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.
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.
Navigation Path
1.
2.
Click the Flow Configuration tab.
3.
Click New.
Issue 01 (2016-04-30)

1684

Configuration Guide

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.
Issue 01 (2016-04-30)

1685

Configuration Guide
Parameter
Value Range
Default Value
Description
NOTE
An EMS6 board does not support Port+VLAN
+Priority Flow.
Port
EFP8: PORT1 to
PORT9,
VCTRUNK1 to
VCTRUNK16
PORT1
l When the associated service is the

Layer 2 switching service, set this
parameter to a mounted port of the
bridge.
EMS6: PORT1 to
PORT7,
VCTRUNK1 to
VCTRUNK8
VLAN ID
1 to 4095
l When the associated service is the line

service, set this parameter to the source
port or sink port of the associated
Ethernet service.

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

Flow 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

Flow Type is set to Port+SVLAN
Flow or Port+SVLAN+CVLAN
Flow.
l Set this parameter to the source SVLAN of the associated Ethernet
service.
Priority

Flow Type is PORT+VLAN+Priority
Flow.
l This parameter indicates the VLAN
priority of the flow-associated Ethernet
services.
NOTE
An EMS6 board does not support Priority.
B.7.4.2 Parameter Description: QoS Management_Creation of CAR

This section describes the parameters for creating CAR.
Issue 01 (2016-04-30)

1686

Configuration Guide
Navigation Path
1.
QoS Management > Flow Management from the Function Tree.
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 1024
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 01 (2016-04-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.

1687

Configuration Guide
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 to 1024000, in
steps of 64

be more than the port bandwidth.
Maximum Burst
Size (kbyte)
EFP8: 0 to 1024
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.
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.

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.
EMS6: 1-1054
Issue 01 (2016-04-30)

1688

Configuration Guide
Parameter
Value Range
Default Value
Description
CoS Type
simple
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.
VLAN Priority
IPTOS
DSCP

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, 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 01 (2016-04-30)
Displays the CoS parameters

corresponding to different CoS types.

1689

Configuration Guide
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.
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS

This section describes the parameters for creating CAR/CoS.
Navigation Path
1.
QoS Management > Flow Management from the Function Tree.
2.
Click the Flow Configuration tab.

Parameter
Value Range
Default Value
Description
Flow Type
Displays the type of a flow.
VB ID
Port
Displays the port where a flow is to be

created.
Issue 01 (2016-04-30)

1690

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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
Function Tree.
Click the Port Queue Information tab.

Parameter
Value Range
Default Value
Description
Port
Port Queue
Displays the queue name.
Issue 01 (2016-04-30)

1691

Configuration Guide
Parameter
Value Range
Default Value
Description
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

to 1024000, in steps
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 01 (2016-04-30)
Displays the maximum excess burst size.

1692

Configuration Guide
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.
Weight
An integer ranging
from 1 to 64
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: -
B.7.4.6 Parameter Description: QoS Management_Port Shaping

This section describes the parameters associated with egress port shaping management.
Navigation Path
In the NE Explorer, select the EMS6 board from the Object Tree and choose Configuration >
QoS Management > Port Shaping Management from the Function Tree.
Issue 01 (2016-04-30)

1693

Configuration Guide
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-68 Parameters for the basic attributes
Parameter
Value Range
Default Value
Description
Port
Displays the name of the external port.
Name
Displays or specifies the name of the

external port.
Issue 01 (2016-04-30)

1694

Configuration Guide
Parameter
Value Range
Default Value
Description
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
Auto-Negotiation
EFP8:
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 fullduplex mode, set this parameter to 10M
Full-Duplex or 100M Full-Duplex,
depending on the rate of the opposite
port.
l If the opposite port works in halfduplex mode, set this parameter to 10M
Half-Duplex 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
EFP8 board.
l 100M FullDuplex

EMS6 board.
l 1000M FullDuplex
Issue 01 (2016-04-30)

1695

Configuration Guide
Parameter
Value Range
Default Value
Description
Maximum Frame
Length (bytes)
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-69 Parameters for flow control

Parameter
Value Range
Default Value
Description
Port
Issue 01 (2016-04-30)

1696

Configuration Guide
Parameter
Value Range
Default Value
Description
NonAutonegotiation
Flow Control
Mode
Disabled
Disabled

Working Mode is not set to AutoNegotiation.
Enable Symmetric
Flow Control Mode
l If this parameter is set to Enable

Symmetric Flow Control Mode, the
port can send PAUSE frames and
process the received PAUSE frames.
Send Only
Receive Only
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
non-autonegotiation flow control mode
of the opposite port.
Autonegotiation
Flow Control
Mode
Disabled
Disabled
Enable
Dissymmetric Flow
Control
Enable Symmetric
Control
Enable Symmetric/
Dissymmetric Flow
Control

Working Mode is Auto-Negotiation.
Symmetric Control, the port can send
PAUSE frames and process the
Dissymmetric Flow Control, the port
can send PAUSE frames in the case of
congestion but cannot process the
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.
Issue 01 (2016-04-30)

1697

Configuration Guide
Table B-70 Parameters for the tag attributes

Parameter
Value Range
Default Value
Description
Port
TAG
Tag Aware
Tag Aware
l With different tag attributes, the port

processes frames in different modes.
For details, see Table B-73.
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 This parameter is valid only when TAG

is set to Access or Hybrid.
l For the usage of this parameter, see
Table B-73.
VLAN Priority
0-7
l This parameter is valid only when TAG

is set to Access or Hybrid.
l For the usage of this parameter, see
Table B-73.
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-71 Parameters for the network attributes

Parameter
Value Range
Default Value
Description
Port
Issue 01 (2016-04-30)

1698

Configuration Guide
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-Awareor 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
Table B-72 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 01 (2016-04-30)
Enabled

1699

Configuration Guide
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-73 Methods used by ports to process data frames

Direction
Ingress port
Issue 01 (2016-04-30)
Type of Data
Frame
Processing Method
Tag aware
Access
Hybrid
Tagged frame
Receives the frame.
Discards the frame.
Receives the frame.

1700

Configuration Guide
Direction
Egress port
Type of Data
Frame
Processing Method
Tag aware
Access
Hybrid
Untagged frame
Discards the frame.
The port receives

the frame after
adding to the frame
the VLAN tag that
contains Default
VLAN ID and
VLAN Priority.
The port receives

the frame after
adding to 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.
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.

Table B-74 Parameters for the tag attributes
Parameter
Value Range
Default Value
Description
Port
Displays the name of the internal

port.
Name
Issue 01 (2016-04-30)

1701

Configuration Guide
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-79.
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 This parameter is valid only

when TAG is set to Access or
Hybrid.
l For the usage of this parameter,
see Table B-79.
VLAN Priority
0-7
l This parameter is valid only

when TAG is set to Access or
Hybrid.
l For the usage of this parameter,
refer to Table B-79.
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-75 Parameters for encapsulation or mapping

Parameter
Value Range
Default Value
Description
Port
Displays the name of the internal port.
Issue 01 (2016-04-30)

1702

Configuration Guide
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-76 Parameters for the network attributes

Parameter
Value Range
Default Value
Description
Port
Issue 01 (2016-04-30)

1703

Configuration Guide
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

S-Aware, 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
Table B-77 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 Rs-Ack and then sends the
MST.
l When you set this parameter to
Standard Mode, the LCAS sink first
sends the MST and then sends the 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 01 (2016-04-30)

1704

Configuration Guide
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
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.
300

TSD
Disabled
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.
Disabled
Enabled
Table B-78 Parameters for bound path

Parameter
Value
Range
Default
Value
Description
VCTRUNK Port
EFP8:
VCTRUNK
1VCTRUNK
16
VCTRUNK
1
Specifies the VCTRUNK to

bind paths.
Displays the level of the

bound VC path.
EMS6:
VCTRUNK
1VCTRUNK
8
Level
In the case of the EFP8

board, this parameter
always takes the value of
VC12-Xv.
Issue 01 (2016-04-30)

1705

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Service Direction
Bidirectional
Bidirectional
l Specifies the direction of

the bound path.
Uplink

Bidirectional unless
otherwise specified.
Downlink
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
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
recommended.
Bound Path Count
Displays the number of the

bound VC path.
Used Channel
Displays the number of used

VC paths.
Activation Status
Displays the activation

status of the bound VC path.
Table B-79 Methods used by ports to process data frames

Direction
Ingress port
Issue 01 (2016-04-30)
Type of Data
Frame
Processing Method
Tag aware
Access
Hybrid
Tagged frame
Receives the frame.
Discards the frame.
Receives the frame.

1706

Configuration Guide
Direction
Egress port
Type of Data
Frame
Processing Method
Tag aware
Access
Hybrid
Untagged frame
Discards the frame.
The port receives

the frame after
adding to the frame
the VLAN tag that
contains Default
VLAN ID and
VLAN Priority.
The port receives

the frame after
adding to 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.
B.7.5.3 Parameter Description: Type Field of QinQ Frames

This section describes the parameters for setting the type field of QinQ frames.
Navigation Path
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.
Issue 01 (2016-04-30)

1707

Configuration Guide

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
B.8 Parameters for MPLS/PWE3 Services

This topic describes parameters that are related to MPLS/PWE3 services.
NOTE
For parameters for PW-carried E-Line services, see B.6 Parameters for Ethernet Services and
Ethernet Features on the Packet Plane.
B.8.1 MPLS Tunnel Parameters

This topic describes parameters that are related to MPLS tunnels.
B.8.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
Issue 01 (2016-04-30)

1708

Configuration Guide

Parameter
Value Range
Default Value
Description
LSR ID
0.0.0.0
l Specifies or
displays the LSR
ID of an NE. On a
PSN, each NE is
assigned a unique
LSR ID.
l This parameter
must be set in IPv4
address format.
Start of Global Label Space
0-1015808
l Specifies the start

value of a global
label space. The
OptiX RTN 900
supports a step of
2048.
l The start value of a
global label space
is the smallest
unicast tunnel
label. When Start
of Global Label
Space is 0, the
smallest unicast
tunnel label is 16,
with values 0 to 15
reserved.
l On an MPLSenabled network,
global label spaces
of NEs are
recommended to
overlap each other
if possible.
Global Label Space Size
Displays the size of a

global label space.
Start of Multicast Label Space
The OptiX RTN 900

does not support this
parameter.
TTL Processing Mode
pipe
pipe
Specifies the TTL

Processing Mode.
uniform
Issue 01 (2016-04-30)

1709

Configuration Guide
B.8.1.2 Parameter Description: MPLS Basic Configuration_Global OAM

Parameters
This topic describes the parameters that are used for configuring OAM parameters.
Navigation Path
1.
Select the desired NE from the Object Tree in the NE Explorer. Choose Configuration >
2.
Click the Global OAM Parameters tab.
Parameters in the window for setting global OAM parameters

Parameter
Value Range
Default Value
Description
Default OAM Recommendation
Displays the default

OAM standard. The
default OAM standard
is Y.1711.
Carrier ID
l Set Carrier ID
according to the
network plan if
MPLS-TP OAM
uses the ICC-based
format.
l Set Carrier ID to
the same value for
all NEs on a
network.
Port AIS Status
Disabled
Disabled
Enabled
Issue 01 (2016-04-30)

Set Port AIS Status

to Enabled if you
want to suppress
alarms triggered by an
MPLS tunnel fault
that results from a
port fault.
1710

Configuration Guide
Parameter
Value Range
Default Value
Description
Channel Type
0 to FFFF
7FFA
l Specifies the
channel type in an
MPLS-TP OAM
packet.
l Set Channel Type
to the same value
for all NEs on a
network.
l NEs can receive
OAM packets
from a channel of
the 8902 type
regardless of the
value of this
parameter.
l It is recommended
that this parameter
take its default
value.
CSF Status
Enabled
Enabled
Disabled
Ping/Tracert Socket Port Status
Enabled
When AC link
failures must be
notified to its peer end
in real time, set CSF
Status to Enabled.
Enabled
Disabled
B.8.1.3 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
Tunnel Key
Displays the tunnel Key.
Issue 01 (2016-04-30)

1711

Configuration Guide
Parameter
Value Range
Default Value
Description
Name

customized tunnel name.
Enable State
Enabled
Enabled
Specifies or displays
whether a tunnel is
enabled.
Disabled
NOTE
The OptiX RTN 900
supports only the value
Enabled.
Node Type
l Displays the node

type.
l For bidirectional
tunnels, this parameter
displays the node
types of forward
tunnels.
Direction

a tunnel.
CIR(kbit/s)
No Limit
l Specifies or displays
the committed
information rate (CIR)
of a tunnel.
1024-1024000
l Generally, it is
recommended that
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)

not support this
parameter.
CBS(byte)

not support this
parameter.
PBS(byte)

not support this
parameter.
Issue 01 (2016-04-30)

1712

Configuration Guide
Parameter
Value Range
Default Value
Description
Bandwidth
Remaining(kbit/s)

not support this
parameter.
In Port
Displays the ingress port

of a forward tunnel,
which is also the egress
port of the mapping
reverse tunnel.
Forward Incoming
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.
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

the egress node.
Tunnel Type
Displays the tunnel type.
Issue 01 (2016-04-30)

1713

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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 900,
this parameter can be set to
Pipe only.
MTU(byte)
Issue 01 (2016-04-30)


not support this
parameter.
1714

Configuration Guide
Parameter
Value Range
Default Value
Description
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 01 (2016-04-30)

1715

Configuration Guide
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 LLSP.
CS6
EF
AF4
AF3
the highest service
grade, which is mainly
involved in signaling
transmission.
AF2
AF1
BE

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.
assured forwarding.
applicable to the
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.
Deployment

status of the tunnel.
B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of

Unidirectional Tunnels
This topic describes parameters that are used for creating unidirectional tunnels.
Navigation Path
1.
Issue 01 (2016-04-30)
Function Tree.
1716

Configuration Guide
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-102400
0
l Generally, it is recommended
that you set this parameter to
No Limit. If you need to limit
the tunnel bandwidth, set this
parameter to be the same as the
planned tunnel bandwidth.
CBS(kbit/s)
The OptiX RTN 900 does not

PIR(Byte)

PBS(Byte)

In Board/Logic Interface Type
Specifies the MPLS port at the

ingress direction of a forward
tunnel on a transit or egress node.
Issue 01 (2016-04-30)

1717

Configuration Guide
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.8.8.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.8.8.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.8.9.1
Setting the Basic Attributes
of IF_ETH Ports.
l The Enable Tunnel, Specify
IP Address, and IP Address
parameters of the MPLS port
are set to the values specified
in the network plan according
to A.8.9.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.
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.
Outgoing Label
Issue 01 (2016-04-30)
16-1048575

Specifies the MPLS label at the

egress direction of a forward
tunnel on an ingress or transit
node.
1718

Configuration Guide
Parameter
Value
Range
Default
Value
Description
Next Hop Address
l The Next Hop Address

parameter needs to be set only
for the egress port on an
ingress or transit node.
l Set the IP address of the MPLS
ingress port on the next hop
LSR node to Next Hop
Address according to the
network plan.
Source Node
l The Source Node parameter

needs to be set only on an
egress or transit node.
l Set the LSR ID for the last hop
MPLS node to Source Node
Sink Node
l The Sink Node parameter

needs to be set only on an
l Set the LSR ID for the next
hop MPLS node to Sink Node
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.
Issue 01 (2016-04-30)

1719

Configuration Guide
Parameter
Value
Range
Default
Value
Description
EXP
0-7
None
l Specifies the value of the EXP

field in the packets transmitted
through MPLS tunnels.
None
l This parameter is available

only if Node Type is Ingress.
l If this parameter is set to a
value from 0 to 7, the EXP
field takes its fixed value.
l If this parameter takes its
default value None, the EXP
field is set based on the
DiffServ mappings.
LSP Mode
Pipe
Pipe
l Pipe: When stripping MPLS

tunnel labels from packets, an
egress node does not update
the scheduling priority for the
packets.
l This parameter is available
only if Node Type is Egress.
NOTE
The OptiX RTN 900 supports only
the value Pipe.
MTU
Issue 01 (2016-04-30)


1720

Configuration Guide
Parameter
Value
Range
Default
Value
Description
CoS
CS7
BE

PHB service class of an L-LSP,
if the type of an MPLS tunnel
is L-LSP.
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 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.
B.8.1.5 Parameter Description: Unicast Tunnel Management_Creation of

Bidirectional Tunnels
This topic describes the parameters that are related to creating bidirectional tunnels.
Navigation Path
1.
Function Tree.
2.
3.
Click New and choose Bidirectional Tunnel from the drop-down list.
Issue 01 (2016-04-30)

1721

Configuration Guide

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.
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 limit the PW
bandwidth, set this parameter to be
the same as the planned tunnel
bandwidth.
CBS(kbit/s)
The OptiX RTN 900 does not support

this parameter.
PIR(Byte)

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 01 (2016-04-30)

1722

Configuration Guide
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.8.8.1 Setting the
Basic Attributes of Ethernet
Ports.
l The Enable Tunnel, Specify IP
Address, and IP Address
parameters of the MPLS port are
set to the values specified in the
network plan according to A.8.8.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.8.9.1 Setting the
Basic Attributes of IF_ETH
Ports.
l The Enable Tunnel, Specify IP
Address, and IP Address
parameters of the MPLS port are
set to the values specified in the
network plan according to A.8.9.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
Forward Out Label
16 to 1048575
Issue 01 (2016-04-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.
Specifies the MPLS label at the egress

direction of a forward tunnel on an

1723

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
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.
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
Issue 01 (2016-04-30)

1724

Configuration Guide
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 900 supports only the
value Pipe.
MTU
Issue 01 (2016-04-30)

this parameter.

1725

Configuration Guide
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.
B.8.1.6 Parameter Description: Unicast Tunnel Management_OAM Parameters

This topic describes parameters that are related to MPLS OAM.
Navigation Path
1.
Function Tree.
2.

Parameter
Value Range
Default Value
Description
Tunnel ID
Displays the tunnel ID.
Tunnel Name
Displays the tunnel name.
Node Type
l Displays the node

type.
l For bidirectional
displays the node
types of forward
tunnels.
Issue 01 (2016-04-30)

1726

Configuration Guide
Parameter
Value Range
Default Value
Description
Tunnel Direction

a 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 01 (2016-04-30)

1727

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Adaptive
Adaptive
the MPLS OAM
detection mode.
Manual
l Manual: During a CC
test, MPLS OAM
the user.
l Adaptive: 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
be received and
transmitted.
l Generally, the value
Adaptive is
recommended.
Issue 01 (2016-04-30)

1728

Configuration Guide
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
Mode is set to
Manual, this
parameter specifies
the type of MPLS
OAM detection
packets to be
received.
Mode is set to
Adaptive, this
parameter specifies
the type of MPLS
OAM detection
packets to be
transmitted.
Mode is set to
Manual, this
parameter specifies
the types of MPLS
OAM detection
and transmitted.
l The value FFD is
assumed for MPLS
APS and the value
CV is assumed for
continuous
connectivity check on
MPLS tunnels.
Issue 01 (2016-04-30)

1729

Configuration Guide
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.
Remote LSP Defect

Type
Displays the LSP defect

type.
Issue 01 (2016-04-30)

1730

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
can be set for its
egress node only.
is set to 0, SD
threshold detection is
not supported.
SF Threshold(%)
0-100
the SF threshold.
When the OAM
higher than the
corresponding alarm
is reported.
can be set for its
egress node only.
is set to 0, SF
not supported.
l The SD threshold is
not higher than the SF
threshold.
Source Node
Displays the source node

of a tunnel.
Sink Node
Displays the sink node of

a tunnel.
Issue 01 (2016-04-30)

1731

Configuration Guide
B.8.1.7 Parameter Description: Unicast Tunnel Management_FDI

This topic describes FDI parameters.
Navigation Path
1.
Function Tree.
2.
Click the FDI tab.

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.
B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Ping

This topic describes the parameters that are related to the LSP Ping test.
Issue 01 (2016-04-30)

1732

Configuration Guide
Navigation Path
1.
Function 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.

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 01 (2016-04-30)

1733

Configuration Guide
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,
IPv4 UDP Response.
Issue 01 (2016-04-30)

1734

Configuration Guide
Parameter
Value Range
Default Value
Description
NOTE
For a unidirectional
tunnel, Response
Application Control
Channel Response.
B.8.1.9 Parameter Description: Unicast Tunnel Management_LSP Traceroute

This topic describes the parameters that are related to the LSP Traceroute test.
Navigation Path
1.
Function 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

the MPLS label in test
request packets.
recommended.
Packet Length
84 to 1400
84

recommended.
Issue 01 (2016-04-30)

1735

Configuration Guide
Parameter
Value Range
Default Value
Description
Response Timeout
Period(10ms)
1 to 6000
300

value.
recommended.
Issue 01 (2016-04-30)

1736

Configuration Guide
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.
l The value
Application Control
Channel Response
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
this parameter to
Application Control
the egress node does
not support reverse
supports DCN
channel response by
IPv4 UDP Response.
Issue 01 (2016-04-30)

1737

Configuration Guide
Parameter
Value Range
Default Value
Description
NOTE
For a unidirectional
tunnel, Response
Application Control
Channel Response.
B.8.1.10 Parameter Description: Unicast Tunnel Management_MEP Management

This section describes the MEP parameters of MPLS-TP tunnel OAM.
Navigation Path
1.
2.
Click the MPLS-TP OAM tab.
3.
Click the MEP tab.
Parameters in the window for setting MEP parameters

Parameter
Value Range
Default Value
Description
Tunnel ID
Displays the ID of a
tunnel.
Tunnel Name
Displays the name of a

tunnel.
Node Type

node.
Tunnel Direction
Displays whether a tunnel

is bidirectional or
unidirectional.
Reverse Tunnel ID
This parameter needs to

be set for a unidirectional
tunnel.
OAM Status
Disabled
Disabled
Set this parameter to

Enabled when the
MPLS-TP tunnel OAM
function needs to be used.
Enabled
Issue 01 (2016-04-30)

1738

Configuration Guide
Parameter
Value Range
Default Value
Description
MEG ID Type
IP Based
IP Based
l When all NEs

connected to an MPLS
tunnel are Huawei
devices that supports
I-based MPLS-TP
OAM components, it
is recommended that
you set MEG ID Type
to IP Based. In this
case, you do not need
to configure MEG ID,
MP ID, RMEP ID, or
MIP.
ICC Based
Customer Based
l If some MPLS-TP
tunnel OAM
components cannot be
set to IP Based or
have special
requirements, it is
set MEG ID Type to
ICC Based.
l For interconnection
with non-Huawei
devices, you can set
this parameter to
Customer Based.
MEG ID
l You need to set MEG

ID when MEG ID
Type is not IP Based.
l Set MEG ID to the
same value for nodes
connected to the same
MPLS tunnel.
l Set MEG ID to
different values for
nodes connected to
different MPLS
tunnels.
MEG Level
0 to 7
you set MEG Level to 7.
MEP ID
1 to 8191
RMEP ID
1 to 8191
Set MEP ID at the source

end to the same value as
RMEP ID at the sink
end.
Issue 01 (2016-04-30)

1739

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Adaptive
Adaptive
l Manual: tests whether

a tunnel is available
based on the userdefined CCM
transmission interval.
Manual
l Adaptive: tests
whether a tunnel is
available based on the
interval at which
CCMs have been
received.
l It is recommended that
to Adaptive.
l Detection Mode
cannot be specified for
the ingress node of a
unidirectional tunnel.
CC Status
Displays the CC status.
CC Packet Priority
0 to 7
l It is recommended that
you set CC Packet
Priority to 7 to ensure
that CC packets are
forwarded with
priority.
l CC Packet Priority
cannot be specified for
the egress node of a
Issue 01 (2016-04-30)

1740

Configuration Guide
Parameter
Value Range
Default Value
Description
CC Packet Interval (ms)
3.3
1000
l If the MPLS-TP OAM

CC function is used
for only continuity
check, it is
set CC Packet
Interval (ms) to the
default value 1000.
10
100
1000

CC function is used to
trigger MPLS APS, it
is recommended that
you set CC Packet
Interval (ms) to
3.3ms. If the frame
delay variation on a
set the transmission
interval of CCMs to a
frame delay variation.
l CC Packet Interval
(ms) cannot be
specified for the
egress node of a
AIS Status
Disabled
Disabled
Enabled
l If an NE is the S-PE
of an MS-PW and
alarms triggered by
PW faults that result
from MPLS tunnel
faults need to be
suppressed, set AIS
Status to Enabled.
l AIS Status cannot be
specified for a
Lock Status
Unlock
Unlock
Lock
Set Lock Status to Lock

if a tunnel needs to be
locked.
NOTE
OptiX RTN 950 housing
CSHU/CSHUA and OptiX
RTN 950A do not support
this operation.
Local LSP Status
Issue 01 (2016-04-30)

Displays whether the LSP

is available at the local
end.
1741

Configuration Guide
Parameter
Value Range
Default Value
Description
Local LSP Defect Type
Indicates the type of the

tunnel defect at the local
end.
Local LSP Disabled

Duration (ms)

when the LSP at the local
end is unavailable.
Local LSP Defect

Location

the node that has detected
the LSP defect.
Remote LSP Status
Displays whether the LSP

is available at the
opposite end.
Remote LSP Defect

Type
Specifies the type of the

LSP defect at the opposite
end.
Remote LSP Disabled

Duration (ms)

when the LSP at the
opposite end is
unavailable.
Remote LSP Defect

Location

the node that has detected
the LSP defect.
SD Threshold (%)
0 to 100
the SD threshold. An
alarm is reported if the
OAM packet loss ratio
is larger than the SD
threshold.
can be specified only
for the egress node.
l When the value is set
to 0, SD threshold
detection is not
supported.
Issue 01 (2016-04-30)

1742

Configuration Guide
Parameter
Value Range
Default Value
Description
SF Threshold (%)
0 to 100
the SF threshold. An
alarm is reported if the
OAM packet loss ratio
is larger than the SF
threshold.
can be specified only
for the egress node.
to 0, SF threshold
detection is not
supported.
smaller than or equal
to the SF threshold.
Source Node

of a tunnel.
Sink Node

a tunnel.
B.8.1.11 Parameter Description: Unicast Tunnel Management_Creating Tunnel

MIPs
This section describes the parameters that are used for creating an MIP in MPLS-TP tunnel
OAM.
Navigation Path
1.
2.
3.
Click the MIP tab.
4.
Click New.
Parameters in the Window for Creating an MIP

Parameter
Value Range
Default Value
Description
Tunnel
Specifies the tunnel on

which an MIP needs to be
created.
Issue 01 (2016-04-30)

1743

Configuration Guide
Parameter
Value Range
Default Value
Description
MEG ID Type
ICC Based
ICC Based
l It is recommended
that you set MEG ID
Type to ICC Based.
Customer Based
with non-Huawei
this parameter to
Customer Based.
MEG ID
l Set MEG ID to the

MPLS tunnel.
l Set MEG ID to
nodes connected to
different MPLS
tunnels.
MP ID
1 to 8191
Each MP on an MPLS
tunnel must have a unique
MP ID.
B.8.1.12 Parameter Description: Unicast Tunnel Management_Enabling an LB

Test
This section describes the parameters that are used for enabling the LB test provided by
MPLS-TP tunnel OAM.
Navigation Path
1.
2.
3.
Click the MEP tab.
4.
Select one or more tunnels and choose OAM Operation > Start LB.
Parameters in the window for setting LB parameters

Parameter
Value Range
Default Value
Description
MEG ID
Local MEP ID
Displays the MEG ID and

MEP ID. If the MEG ID
type is in an IP address
format, the MEG ID or
MEP ID is not displayed.
Issue 01 (2016-04-30)

1744

Configuration Guide
Parameter
Value Range
Default Value
Description
Node Type
MEP
MEP

sink end of the tested
tunnel is an MEP or MIP.
l Set Remote
MEP/MIP ID or IP
Address according to
the termination node
of an LB test.
MIP
Remote MEP/MIP ID
or IP Address
l If MEG ID Type is
set to IP Based for the
termination node, set
Remote MEP/MIP
ID or IP Address to
the LSR ID of the
termination node.
l If MEG ID Type is
not set to IP Based
for the termination
node, set Remote
MEP/MIP ID or IP
Address to the MP ID
of the termination
node.
Packet Count
1 to 65535
l Specifies the number

of packets that can be
transmitted each time.
l It is recommended
that this parameter
Packet Priority
0 to 7
l Specifies the packet

priority.
l It is recommended
that this parameter
Issue 01 (2016-04-30)

1745

Configuration Guide
Parameter
Value Range
Default Value
Description
TTL
1 to 255
355
l If Node Type is MIP,

set TTL to the
number of hops
between the source
MEP and the current
MIP.
l If Node Type is
MEP, set TTL to a
value that is greater
than or equal to the
number of hops
between the current
MEP and the remote
MEP. It is
recommended that
this parameter take its
default value.
Transmit Interval
100ms

100ms
1s
l It is recommended
that this parameter
10s
Packet length
128 to 1410

length.
128
l It is recommended
that this parameter
B.8.1.13 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 Status
Displays whether a PW is enabled.
Issue 01 (2016-04-30)

1746

Configuration Guide
Parameter
Value Range
Default Value
Description
PW Signaling
Type
Displays the PW signaling type.
PW Type
NOTE
The RTN 900 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 circuit emulation
services (CESs), set PW Type to
CESoPSN or SATop.
l If a PW transmits ATM services, set PW
Type to ATM n-to-one VCC Cell
transport, ATM one-to-one VCC Cell
Mode, ATM n-to-one VPC Cell
transport, or ATM one-to-one VPC
Cell Mode.
NOTE
OptiX RTN 905 does not support ATM services.
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.
NOTE
The RTN 900 supports only MPLS encapsulation.
Issue 01 (2016-04-30)

1747

Configuration Guide
Parameter
Value Range
Default Value
Description
Tunnel Type
Displays the type of the tunnel that carries a

PW.
NOTE
The RTN 900 supports only MPLS tunnels.
Ingress
Tunnel
Displays the ID of the tunnel that carries a

PW.
Egress Tunnel
Deployment
Status
Displays the deployment status of a PW.
Tunnel
Automatic
Selection
Policy
The RTN 900 does not support this

parameter.
QoS Parameters
Table B-81 CES services
Parameter
Value Range
Default Value
Description
PW ID

PW that carries a service.
Direction

the PW that carries a
service.
CIR(kbit/s)
The RTN 900 does not

EXP

Parameter
Value Range
Default Value
Description
PW ID

Direction

service.
Table B-82 E-Line services
Issue 01 (2016-04-30)

1748

Configuration Guide
Parameter
Value Range
Default Value
Description
Bandwidth Limit

bandwidth is limited.
CIR(kbit/s)
Displays the committed

a PW.
CBS(byte)

PIR(kbit/s)
Displays the peak

a PW
PBS(byte)
Displays the peak burst

size (PBS) of a PW.
EXP

LSP Mode
Displays the LSP mode.

NOTE
The RTN 900 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

a PW
Table B-83 ATM services
Issue 01 (2016-04-30)

1749

Configuration Guide
Parameter
Value Range
Default Value
Description
PBS(byte)
Displays the peak burst

size (PBS) of a PW.
EXP

Policy


Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
RTP Head

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.
Issue 01 (2016-04-30)

1750

Configuration Guide
Parameter
Value Range
Default Value
Description
Threshold of Exiting R
bit Inserting Status

received CES service
packets. The
be cleared after the actual
number of received CES
service packets crosses
this threshold.
Sequence Number
Mode
Displays the sequence

number mode.
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
Displays the VCCV

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.
Issue 01 (2016-04-30)

1751

Configuration Guide

Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
Control Word

transfer packet
information.

channel type.
VCCV Verification
Mode
Displays the VCCV

mode.
Max Concatenated Cell

Count

number of concatenated
cells.
Packet Loading
Time(us)
Displays the packet

loading time.
B.8.1.14 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)
The OptiX RTN 900 does not support this

parameter.
Service Type
Ethernet Service
Ethernet Service
l Specifies the type of services carried by

the MS-PW.
CES Service
ATM Service

NOTE
Issue 01 (2016-04-30)

1752

Configuration Guide
Parameter
Value Range
Default Value
Description
Connection
Type
Port Transparent
Port Transparent

Service Type is ATM Service.
PVP
l PVP: Only the VPIs of the source and

sink are exchanged.
PVC
l PVP: The VPIs and VCIs of the source

and sink are exchanged.
l Port Transparent: ATM transparent
transmission refers to the transparent
transmission of ATM cells that are
encapsulated into PWs as payloads.
NOTE
The OptiX RTN 905 does not support this
parameter.
Parameters for the Basic Attributes of PWs

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.
Issue 01 (2016-04-30)

1753

Configuration Guide
Parameter
Value Range
Default Value
Description
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 structureagnostic emulation,
which does not allow
timeslot compression.
l If Service Type is
ATM Service, set this
parameter according
to the value of
Connection Type.
NOTE
support ATM services.
PW Direction

the PW.
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
PW Outging Label
16 to 1048575

label.
Issue 01 (2016-04-30)

1754

Configuration Guide
Parameter
Value Range
Default Value
Description
Manually
Manually
Specifies the method to

select tunnels.
NOTE
The OptiX RTN 905
Manually.
Tunnel Type
MPLS
MPLS

PW.
Ingress Tunnel
A created tunnel needs to

be selected. If no tunnel
is available, no PW can
be created.
Peer LSR ID

be automatically
assigned.
Egress Tunnel

the reverse tunnel
automatically.
QoS Parameters
NOTE
CES Services
Parameter
Value Range
Default Value
Description
EXP

Issue 01 (2016-04-30)

1755

Configuration Guide
Ethernet services
Parameter
Value Range
Default Value
Description
Bandwidth Limit

is enabled.
or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.
Policy

CIR (kbit/s)

a PW.
CBS (byte)

PIR (kbit/s)
Specifies the peak

a PW.
PBS (byte)

size (PBS) of a PW.
EXP

LSP Mode
Pipe
Pipe

does not update the
the packets.
Issue 01 (2016-04-30)

1756

Configuration Guide
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

not support this
parameter.
CIR (Kbit/s)

the PW.
CBS (kbyte)
Specifies the excess burst

size of the PW.
PIR (kbit/s)
Specifies the peak

the PW.
PBS (kbyte)
Issue 01 (2016-04-30)


excess burst size of the
PW.
1757

Configuration Guide
Parameter
Value Range
Default Value
Description
EXP

not support this
parameter.
Parameters for the Advanced Attributes of PWs

NOTE
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 01 (2016-04-30)

1758

Configuration Guide
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.
l A greater value of this
parameter means
higher encapsulation
efficiency but greater
delays of CES
services.
recommended.
Ingress Clock mode

not support this
parameter.
Egress Clock mode

not support this
parameter.
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.
Issue 01 (2016-04-30)

1759

Configuration Guide
Parameter
Value Range
Default Value
Description
VCCV Verification
Mode
None
Ping

verification mode.
The VCCV
PW connectivity
check.
Ping

this parameter to
None.
64K Timeslot Number
1 to 31

of 64 kbit/s timeslots
that transmit service
traffic. If Frame
Mode of the opposite
end is 30, the source
64 kbit/s timeslots at
the local end must
include the 16th
timeslot.
l On the two ends of a
radio link, the timeslot
lists can be different
but the numbers of
timeslots must be the
same.
l This parameter is
unavailable if PW
Type is SAToP.
Sequence Number
Mode
Issue 01 (2016-04-30)
Huawei Mode
Huawei Mode
Standard Mode

Specifies the sequence

number mode.
1760

Configuration Guide
Ethernet services
Parameter
Value Range
Default Value
Description
Control Word
Not in use
Not in use
Specifies whether a
words when
encapsulating ETH
PWE3 packets.
Used First
NOTE
control words when
Description.
None
Alert Label
Alert Label

VCCV is not used.
CW

VCCV packets in
Alert Label
encapsulation mode.
VCCV packets
used.
VCCV Verification
Mode
Ping
Ping
None

verification mode.
The VCCV
this parameter to
None.
Request VLAN

when PW Type is
Ethernet Tagged
Mode.
do not carry any
VLAN IDs, the PW
the packets as
of this parameter.
Issue 01 (2016-04-30)

1761

Configuration Guide
Parameter
Value Range
Default Value
Description
TPID

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 control word is
used to transmit
packet information.
ATM services
No Use
l Set Control Word to

Must Use if PW Type
is ATM 1:1.
CW
CW
None
Alert Label

PW connectivity
check.
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.
Issue 01 (2016-04-30)

1762

Configuration Guide
Parameter
Value Range
Default Value
Description
VCCV Verification
Mode
Ping
Ping

verification mode.
The VCCV
PW connectivity
check.
None

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.
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.
B.8.1.15 Parameter Description: PW Management_PW OAM

This topic describes parameters that are related to PW OAM.
Issue 01 (2016-04-30)

1763

Configuration Guide
Navigation Path
1.
2.
Click the PW OAM Parameter tab.

Parameter
Value Range
Default Value
Description
PW ID

PW that carries the
service.
PW Type

PW that carries the
service.
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 with AC
Status
Issue 01 (2016-04-30)


not support this
parameter.
1764

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Adaptive
Auto-Sensing
the detection mode for
PW OAM packets.
Manual
l Manual: During a CC
test, PW OAM
the user.
l Adaptive: During a
CC test, PW OAM
interval for receiving
PW OAM packets.
set to Manual, you
need to set the type of
PW OAM detection
and transmitted.
l The value Adaptive is
recommended.
Issue 01 (2016-04-30)

1765

Configuration Guide
Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

the user.
set to Adaptive, this
parameter specifies
the type of PW OAM
be transmitted.
set to Manual, this
parameter specifies
the type of PW OAM
be received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous
connectivity check on
PWs.
Packet Detection
Interval(ms)
3.3
50
10
20
the OAM detection
period.
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.
Issue 01 (2016-04-30)

1766

Configuration Guide
Parameter
Value Range
Default Value
Description
SD Threshold (%)
0-100
the SD threshold.
When the OAM
higher than the
corresponding alarm
is reported.
is set to 0, SD
not supported.
SF Threshold (%)
0-100
the SF threshold.
When the OAM
higher than the
corresponding alarm
is reported.
is set to 0, SF
not supported.
not higher than the SF
threshold.
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
Issue 01 (2016-04-30)

Displays whether PWs at

the local end are
available.
1767

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
B.8.1.16 Parameter Description: PW Management_PW Ping

This topic describes the parameters that are related to the PW Ping test.
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
the highest priority.
recommended.
Issue 01 (2016-04-30)

1768

Configuration Guide
Parameter
Value Range
Default Value
Description
TTL
1 to 255
255

the 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 01 (2016-04-30)

1769

Configuration Guide
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.
l The value
Application Control
Channel Response
indicates that the IPv4
UDP packets
encapsulating MPLS
echo reply messages
are sent as response
packets.
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
this parameter to
Application Control
the remote PE does
not support reverse
supports DCN
channel response by
IPv4 UDP Response.
Issue 01 (2016-04-30)

1770

Configuration Guide
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.
B.8.1.17 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
the highest priority.
recommended.
TTL
1 to 255
255

the PW label in test
request packets.
recommended.
Packet Length
84 to 1400
84

recommended.
Response Timeout
Period(10ms)
1 to 6000
300

value.
recommended.
Issue 01 (2016-04-30)

1771

Configuration Guide
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.
l The value
Application Control
Channel Response
indicates that the IPv4
UDP packets
encapsulating MPLS
echo reply messages
are sent as response
packets.
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
this parameter to
Application Control
the remote PE does
not support reverse
supports DCN
channel response by
IPv4 UDP Response.
Issue 01 (2016-04-30)

1772

Configuration Guide
B.8.1.18 Parameter Description: PW Management_MEP Management

This section describes the MEP parameters of MPLS-TP PW OAM.
Navigation Path
1.
2.
3.
Click the MEP tab.
Parameters in the Window for Configuring MEP Parameters

Parameter
Value Range
Default Value
Description
PW ID
Displays the ID of a PW.
PW Type
Displays the PW service

type.
OAM Status
Disabled
Disabled
Set this parameter to

Enabled when the
MPLS-TP PW OAM
function needs to be used.
IP Based
l When all NEs

connected to a PW are
Huawei devices that
support I-based
MPLS-TP OAM
components, it is
recommended that
you set MEG ID
Type to IP Based. In
this case, you do not
need to configure
MEG ID, MP ID,
RMEP ID, or MIP.
Enabled
MEG ID Type
IP Based
ICC Based
Customer Based
l If some MPLS-TP
PW OAM
components cannot be
set to IP Based or
have special
requirements, it is
recommended that
you set MEG ID
Type to ICC Based.
with non-Huawei
this parameter to
Customer Based.
Issue 01 (2016-04-30)

1773

Configuration Guide
Parameter
Value Range
Default Value
Description
MEG ID
l You need to set MEG

ID when MEG ID
Type is not IP Based.
l Set MEG ID to the
PW.
l Set MEG ID to
nodes connected to
different PWs.
MEG Level
0 to 7
you set MEG Level to 7.
MEP ID
1 to 8191
RMEP ID
1 to 8191
Set MEP ID at the source

end to the same value as
RMEP ID at the sink
end.
Detection Mode
Adaptive
Adaptive
Manual
l Manual: tests
whether a PW is
user-defined CCM
l Adaptive: tests
whether a PW is
interval at which
CCMs have been
received.
l It is recommended
that you set this
parameter to
Adaptive.
CC Status
Displays the CC status.
CC Packet Priority
0 to 7
you set CC Packet
Priority to 7 to ensure
that CC packets are
forwarded with priority.
Issue 01 (2016-04-30)

1774

Configuration Guide
Parameter
Value Range
Default Value
Description
CC Packet Interval (ms)
3.3
1000

CC function is used
for only continuity
check, it is
recommended that
you set CC Packet
Interval (ms) to the
default value 1000.
10
100
1000

CC function is used to
trigger PW APS, it is
recommended that
you set CC Packet
Interval (ms) to
3.3ms. If the frame
delay variation on a
set the transmission
interval of CCMs to a
frame delay variation.
Lock Status
Unlock
Unlock
Lock
Set Lock Status to Lock

if a PW needs to be
locked.
NOTE
this operation.
Local Status
Displays whether a local

PW is available.
Local Defect Type

PW fault at the local end.
Local Disabled
Duration (ms)

when the local PW is
unavailable.
Local Defect Location
Displays the position of a

PW fault.
Remote Status
Displays whether the PW

is available at the
opposite end.
Remote Defect Type

PW fault at the remote
end.
Issue 01 (2016-04-30)

1775

Configuration Guide
Parameter
Value Range
Default Value
Description
Remote Disabled
Duration (ms)

when the remote PW is
unavailable.
Remote Defect Location
Displays the position of a

PW fault.
SD Threshold (%)
0 to 100
the SD threshold. An
alarm is reported if
the OAM packet loss
ratio is larger than the
SD threshold.
to 0, SD threshold
detection is not
supported.
SF Threshold (%)
0 to 100
the SF threshold. An
alarm is reported if
the OAM packet loss
ratio is larger than the
SF threshold.
to 0, SF threshold
detection is not
supported.
smaller than or equal
to the SF threshold.
PW ID to be Received
l For an MS-PW, you

need to manually
specify the LSR ID
and PW ID for the
sink node of the MSPW.
l LSR ID to be
Received and PW ID
to be Received are
available only when
OAM is disabled.
Issue 01 (2016-04-30)

1776

Configuration Guide
Parameter
Value Range
Default Value
Description
GAL Enable Status
Disabled
Disabled
l Specifies whether
OAM packets carry
generic associated
channel header labels
(GALs).
Enabled
l If PWE3 services use

control worlds,
MPLS-TP PW OAM
packets do not
necessarily carry
GALs. Otherwise,
MPLS-TP PW OAM
packets must carry
GALs.
LM Packet Mode
Standard Mode
Standard Mode
Huawei Mode
you set LM Packet
Mode to Standard.
NOTE
this operation.
GAL Mode
RFC5586
RFC5586
Y.1711
When this parameter is

set to RFC5586, the
GAL label is 13. When
this parameter is set to Y.
1711, the GAL label is
14.
B.8.1.19 Parameter Description: PW Management_Creating MIPs

This section describes the parameters that are used for creating an MIP in MPLS-TP PW
OAM.
Navigation Path
1.
2.
3.
Click the MIP tab.
4.
Click New.
Issue 01 (2016-04-30)

1777

Configuration Guide
Parameters in the Window for Creating an MIP

Parameter
Value Range
Default Value
Description
MS PW
Specifies the MS-PW on

which an MIP needs to be
created.
MEG ID Type
ICC Based
ICC Based
l It is recommended
that you set MEG ID
Type to ICC Based.
Customer Based
with non-Huawei
this parameter to
Customer Based.
MEG ID
l Set MEG ID to the

PW.
l Set MEG ID to
nodes connected to
different PWs.
MP ID
1 to 8191
Each MP on a PW must
have a unique MP ID.
B.8.1.20 Parameter Description: PW Management_Enabling an LB

This section describes the parameters that are used for enabling the LB test provided by
MPLS-TP PW OAM.
Navigation Path
1.
2.
3.
Click the MEP tab.
4.
Select one or more PWs and choose OAM Operation > Start LB.
Parameters in the window for setting LB parameters

Parameter
Value Range
Default Value
Description
MEG ID
Displays the MEG ID and

MEP ID. If the MEG ID
type is in an IP address
Issue 01 (2016-04-30)

1778

Configuration Guide
Parameter
Value Range
Default Value
Description
Local MEP ID
format, the MEG ID or

MEP ID is not displayed.
Node Type
MEP
MEP

sink end of the tested
tunnel is an MEP or MIP.
l Set Remote
MEP/MIP ID or IP
Address according to
the termination node
of an LB test.
MIP
Remote MEP/MIP ID
or IP Address
l If MEG ID Type is
set to IP Based for the
termination node, set
Remote MEP/MIP
ID or IP Address to
the LSR ID of the
termination node.
l If MEG ID Type is
not set to IP Based
for the termination
node, set Remote
MEP/MIP ID or IP
Address to the MP ID
of the termination
node.
Packet Count
1 to 65535

of packets that can be
transmitted each time.
l It is recommended
that this parameter
Packet Priority
0 to 7

priority.
l It is recommended
that this parameter
Issue 01 (2016-04-30)

1779

Configuration Guide
Parameter
Value Range
Default Value
Description
TTL
1 to 255
355
l If Node Type is MIP,

set TTL to the
number of hops
between the source
MEP and the current
MIP.
l If Node Type is
MEP, set TTL to a
value that is greater
than or equal to the
number of hops
between the current
MEP and the remote
MEP. It is
recommended that
this parameter take its
default value.
Transmit Interval
100ms
100ms
1s
l It is recommended
that this parameter
10s
Packet length

128 to 1410
128

length.
l It is recommended
that this parameter
B.8.1.21 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.
Issue 01 (2016-04-30)

1780

Configuration Guide

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

group type.
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.
l It is recommended
that you set this
parameter to DualEnded.
Issue 01 (2016-04-30)

1781

Configuration Guide
Parameter
Value Range
Default Value
Description
BDI Status
Disabled
whether the protection
switching is triggered
upon receiving BDI
packets.
Enabled
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
Displays the protocol

packet status.
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.
l It is recommended
that you set this
parameter to
Revertive.
Issue 01 (2016-04-30)

1782

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
l It is recommended
that you set this
parameter to 5.
0-100

group.
0, the protection
switching once it
detects faults, but wait
until the hold-off time
expires, and then
detect whether any
faults persist. If any
faults persist, the
otherwise, no
l It is recommended
that you set this
parameter to 0.
Protocol Status
Displays the protocol

status.
Switching Status

group.
Deployment Status

group.
Issue 01 (2016-04-30)

1783

Configuration Guide
Parameter
Value Range
Default Value
Description
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

a tunnel.
Ingress Tunnel
Displays the ingress

tunnel.
Egress Tunnel
Displays the egress

tunnel.
B.8.1.22 Parameter Description: Tunnel Protection Group_Creation

This topic describes the parameters that are related to creating a tunnel protection group.
Navigation Path
1.
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 900
supports only the value 1:1.
Issue 01 (2016-04-30)

1784

Configuration Guide
Parameter
Value Range
Default Value
Description
Switching Mode
Single-Ended
Dual-Ended
l Specifies the
switching mode to be
adopted when a tunnel
fails.
Dual-Ended
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.
BDI Status
Enabled
Disabled
Disabled
l Specifies whether the

is triggered upon
receiving BDI
packets.
l This parameter is
available only when
Switching Mode is
set to Single-Ended.
l If BDI Status is set to
Enabled, the egress
node notifies the
ingress node of any
detected faults by
sending BDI packets;
upon receiving BDI
packets, the ingress
node triggers the
Working Tunnel Type
MPLS Tunnel
MPLS Tunnel

working tunnel.
NOTE
The OptiX RTN 900
MPLS Tunnel.
Issue 01 (2016-04-30)

1785

Configuration Guide
Parameter
Value Range
Default Value
Description
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

working tunnel in the
ingress direction.
Working Egress Tunnel

ID

tunnel of the
protection group in
the egress direction.
tunnel, if the
parameter Working
Ingress Tunnel ID is
set, a value is
automatically
assigned to the
parameter Working
Egress Tunnel ID.
Working Egress Tunnel

Name

working tunnel in the
egress direction.
Protection Tunnel Type
Displays the type of

protection tunnel, which
is the same as the type of
working tunnel.
Protection Ingress
Tunnel ID

tunnel of the
protection group in
the ingress direction.
for a bidirectional
tunnel, a value is
automatically
assigned to the
parameter Protection
Egress Tunnel ID.
Issue 01 (2016-04-30)

1786

Configuration Guide
Parameter
Value Range
Default Value
Description
Protection Ingress
Tunnel Name

protection tunnel in the
ingress direction.
Protection Egress
Tunnel ID
l Specifies the
protection tunnel of
the protection group
in the egress direction.
tunnel, if the
Ingress Tunnel ID is
set, a value is
automatically
assigned to the
Egress Tunnel ID.
Protection Egress
Tunnel Name

protection tunnel in the
egress direction.
Revertive Mode
Non-Revertive
Non-Revertive
l This parameter
to the original
working tunnel after it
recovers.
Revertive

indicates to switch
services back to the
original working
tunnel after it
recovers; the value
Non-Revertive
indicates not to switch
services back to the
original working
tunnel after it
recovers.
is recommended.
Issue 01 (2016-04-30)

1787

Configuration Guide
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.
0, the protection
switching once it
detects faults, but
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 01 (2016-04-30)

1788

Configuration Guide
B.8.1.23 Parameter Description: PW APS Protection Group_Creation

This topic describes the parameters that are used for creating a PW APS protection group.
Context
NOTE
Navigation Path
The navigation path for CES services is as follows:
1.
CES Service Management from the Function Tree.
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.
ATM Service Management from the Function Tree.
2.
3.
4.
Click New.

Parameter
Value Range
Default Value
Description
PW ID

PW Signaling Type
Static
Static

manually assigned.
PW Type
PW Direction

a PW.
Issue 01 (2016-04-30)

1789

Configuration Guide
Parameter
Value Range
Default Value
Description
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
PW Outgoing Label
16 to 1048575

label.

select tunnels.
Tunnel Type
MPLS
MPLS

PW.
Ingress Tunnel
PW will fail.
Peer LSR ID

be automatically
assigned.
Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
EXP

not support this
parameter.
QoS Parameters
Issue 01 (2016-04-30)

1790

Configuration Guide

Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.
Policy

not support this
parameter.
CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

a PW.
PBS(byte)

size (PBS) of a PW.
EXP

not support this
parameter.
LSP Mode

NOTE
The OptiX RTN 900
supports only Pipe.
Issue 01 (2016-04-30)

1791

Configuration Guide

Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

or more PWs in an
MPLS tunnel.
l An ATM PWE3
the bandwidth of
ATM PWE3 services
in an MPLS tunnel.
CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

a PW.
PBS(byte)

size (PBS) of a PW.
EXP

not support this
parameter.
Policy

not support this
parameter.
Issue 01 (2016-04-30)

1792

Configuration Guide

Parameter
Value Range
Default Value
Description
RTP Head

CES service packets
Packet Loading
Time(us)
Displays the packet

loading time.
Jitter Compensation
Buffering Time(us)

packets.
Ingress Clock Mode

not support this
parameter.
Egress Clock Mode

not support this
parameter.
Displays the mode of PW

continuity check.
VCCV Verification
Mode
Displays the VCCV

verification mode. The
VCCV verification is
used for PW continuity
check.
Enable CES Service

Alarm Transparent
Transmission

service alarms are

CES services. The
this threshold.

packets. The
this threshold.
Issue 01 (2016-04-30)

1793

Configuration Guide
Parameter
Value Range
Default Value
Description
Sequence Number
Mode

number mode.
Parameter
Value Range
Default Value
Description
Control Word

transfer packet
PWE3 services, this
used.

channel type.
VCCV Verification
Mode
Displays the VCCV

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
Displays the VCCV

mode.
Issue 01 (2016-04-30)

1794

Configuration Guide
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
protection mode.
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
NOTE
Issue 01 (2016-04-30)

1795

Configuration Guide
Parameter
Value Range
Default Value
Description
Revertive Mode
Non-revertive
Revertive
l This parameter
to the original
working PW after it
recovers.
Revertive

are switched to the
original working PW
switched to the
is recommended.
Time (min)
1 to 12
l Specifies the WTR

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.
Issue 01 (2016-04-30)

1796

Configuration Guide
Parameter
Value Range
Default Value
Description

(100 ms)
0 to 100

group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.
Detection mode

mode of the PW APS
protection group.
Parameter
Value Range
Default Value
Description
OAM Status

status of PW OAM.
OAM Parameters
Issue 01 (2016-04-30)

1797

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing

mode of OAM
packets.
Manual
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 01 (2016-04-30)

1798

Configuration Guide
Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

the user.
this parameter
specifies the PW
OAM detection
packets to be
transmitted.
set to Manual, this
parameter specifies
the PW OAM
be received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
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.

be received.
Transmitted PW ID
received.
Issue 01 (2016-04-30)

1799

Configuration Guide
B.8.1.24 Parameter Description: PW FPS Protection Group_Creation

This topic describes the parameters that are used for creating a PW FPS protection group.
Navigation Path
1.
2.
3.
Click the PW FPS tab.
4.
Click New.

Parameter
Value Range
Default Value
Description
PW ID

PW Signaling Type
Static
Static

manually assigned.
PW Type
PW Direction

a PW.
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
PW Outgoing Label
16 to 1048575

label.

select tunnels.
Tunnel Type
MPLS
MPLS

PW.
Ingress Tunnel
PW will fail.
Issue 01 (2016-04-30)

1800

Configuration Guide
Parameter
Value Range
Default Value
Description
Peer LSR ID

be automatically
assigned.
Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
QoS Parameters
Enabled

or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.
Policy

not support this
parameter.
CIR(kbit/s)

a PW.
CBS(byte)
Issue 01 (2016-04-30)


1801

Configuration Guide
Parameter
Value Range
Default Value
Description
PIR(kbit/s)
Specifies the peak

a PW.
PBS(byte)

size (PBS) of a PW.
EXP

not support this
parameter.
LSP Mode

NOTE
The OptiX RTN 900
supports only Pipe.

Parameter
Value Range
Default Value
Description
Control Word

transfer packet
PWE3 services, this
used.

channel type.
VCCV Verification
Mode
Displays the VCCV

mode.
Request VLAN
When PW Type is
Ethernet Tag, this
TPID

of the PW level.
Issue 01 (2016-04-30)

1802

Configuration Guide

Parameter
Value Range
Default Value
Description
Protection Type

type.
Protection Group ID

group ID.
Enabling Status
Disabled
Disabled
Specifies the enabling

status of the PW
protection group.
Enabled
Protection Mode

mode.
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
Revertive Mode
Non-revertive
Revertive
l This parameter
to the original
working PW after it
recovers.
Revertive

are switched to the
original working PW
switched to the
is recommended.
Issue 01 (2016-04-30)

1803

Configuration Guide
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
Revertive Mode is
Revertive.
recommended.

(100 ms)
0 to 100

group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.
Detection mode

mode of the PW APS
protection group.
MPLS-TP OAM Parameters

Parameter
Value Range
Default Value
Description
OAM Status

status of PW OAM.
Issue 01 (2016-04-30)

1804

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Adaptive
Adaptive

mode of OAM
packets.
Manual
l Manual: The CC
the user.
l Adaptive: The CC
interval of receiving
PW OAM packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Adaptive is
recommended.
CC Packet Detection
Interval(ms)
3.33ms
1s
10ms

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.
100ms
1s
10s
1min
10min

3.3 for PW APS.

be received.
Transmitted PW ID
received.
GAL Enable Status
Enabled
Enabled
Set the GAL enable

status.
Disabled
Parameter
Value Range
Default Value
Description
OAM Status

status of PW OAM.
Issue 01 (2016-04-30)

1805

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing

mode of OAM
packets.
Manual
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 01 (2016-04-30)

1806

Configuration Guide
Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

the user.
this parameter
specifies the PW
OAM detection
packets to be
transmitted.
set to Manual, this
parameter specifies
the PW OAM
be received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
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.

be received.
Transmitted PW ID
received.
Issue 01 (2016-04-30)

1807

Configuration Guide
B.8.1.25 Parameter Description: Slave Protection Pair of a PW APS Protection

Group_Creation
This topic describes the parameters that are used for creating a slave protection pair of a PW
APS protection group.
Context
NOTE
Navigation Path
The navigation path for CES services is as follows:
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 01 (2016-04-30)

1808

Configuration Guide
Parameter
Value Range
Default Value
Description
PW Direction

a PW.
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
PW Outgoing Label
16 to 1048575

label.

select tunnels.
Tunnel Type
MPLS
MPLS

PW.
Ingress Tunnel
PW will fail.
Peer LSR ID

be automatically
assigned.
Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
EXP

not support this
parameter.
QoS Parameters
Issue 01 (2016-04-30)

1809

Configuration Guide

Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.
Policy

not support this
parameter.
CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

a PW.
PBS(byte)

size (PBS) of a PW.
EXP

not support this
parameter.
LSP Mode

NOTE
The OptiX RTN 900
supports only Pipe.
Issue 01 (2016-04-30)

1810

Configuration Guide

Parameter
Value Range
Default Value
Description
Bandwidth Limit
Disabled

is enabled.
Enabled

or more PWs in an
MPLS tunnel.
l An ATM PWE3
the bandwidth of
ATM PWE3 services
in an MPLS tunnel.
CIR(kbit/s)

a PW.
CBS(byte)

PIR(kbit/s)
Specifies the peak

a PW.
PBS(byte)

size (PBS) of a PW.
EXP

not support this
parameter.
Policy

not support this
parameter.
Issue 01 (2016-04-30)

1811

Configuration Guide

Parameter
Value Range
Default Value
Description
RTP Head

CES service packets
Packet Loading
Time(us)
Displays the packet

loading time.
Jitter Compensation
Buffering Time(us)

packets.
Ingress Clock Mode

not support this
parameter.
Egress Clock Mode

not support this
parameter.

continuity check.
VCCV Verification
Mode
Displays the VCCV

used for PW continuity
check.
Enable CES Service

Alarm Transparent
Transmission

service alarms are

CES services. The
this threshold.

packets. The
this threshold.
Issue 01 (2016-04-30)

1812

Configuration Guide
Parameter
Value Range
Default Value
Description
Sequence Number
Mode

number mode.
Parameter
Value Range
Default Value
Description
Control Word

transfer packet
PWE3 services, this
used.

channel type.
VCCV Verification
Mode
Displays the VCCV

mode.
Request VLAN
When PW Type is
Ethernet Tag, this
TPID

of the PW level.
Parameter
Value Range
Default Value
Description
Control Word

transfer packet
information.

channel type.
VCCV Verification
Mode
Displays the VCCV

mode.
Issue 01 (2016-04-30)

1813

Configuration Guide
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

PW APS protection
group triggers the
PW APS protection
Working PW ID

protection pair.
Protection PW ID

B.8.2 Parameter Description: VPLS Management

This section describes the parameters related to virtual private LAN service (VPLS)
management.
Navigation Path
In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
VPLS Management from the Function Tree.

Parameter
Value Range
Default Value
Description
NE Name

the NE name.
Issue 01 (2016-04-30)

1814

Configuration Guide
Parameter
Value Range
Default Value
Description
T-PID (PW S-TAG)
8100
88A8

the value of TPIDs in STAGs carried in QinQbased VPLS service
packets.
32

the maximum number of
VUNIs that one virtual
switch instance (VSI)
supports.
88A8
9100
VUNI Number
1 to 1024
OptiX RTN 950 using

CSHU/CSHUA and
OptiX RTN 950A/905 do
not support this
parameter.
VLAN Number

the relationship between
the number of VUNIs and
the number of VLAN IDs
that one VUNI supports.
For details, see VPLS.
OptiX RTN 950 using
CSHU/CSHUA and
OptiX RTN 950A/905 do
not support this
parameter.
B.8.3 CES Parameters

This topic describes parameters that are related to CES services.
B.8.3.1 Parameter Description: CES Service Management

This topic describes the parameters that are related to circuit emulation service (CES)
management.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES
Issue 01 (2016-04-30)

1815

Configuration Guide

Parameter
Value Range
Default Value
Description
Service ID

CES service to be
created.
Service name
Displays or specifies the

service name.
Level
Displays the level of the

received TDM frames.
Service Type
Common
Common

is set to common,
CES services are used
to transmit common
CES packets.
SOH only

is set to SOH only,
CES services are used
to transparently
transmit only segment
overhead bytes.
SOH Byte
D1-D12, E1-E2, F1, K1K2 and X1-X4
l Specifies the segment

overhead bytes
transparently
transmitted by CES
services. This
parameter can be set
manually.
l This parameter is
valid only when
Service Type is set to
SOH only.
Source Board
Displays the source board

of the CES service.
Source High Channel
l Specifies the source

higher order channel
of a CES service.
l This parameter is
valid only when the
source board is a
channelized STM-1
board.
Source Low Channel
Issue 01 (2016-04-30)

Displays the source lower

order path.
1816

Configuration Guide
Parameter
Value Range
Default Value
Description
Source 64K Timeslot
Displays the source 64

kbit/s timeslot.
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 involved in
signaling
transmission.
l EF: indicates the
expedited forwarding
of service, which is
applicable to services
of low transmission
delay and low packet
loss rate, for example,
voice and video
services.
l AF1-AF4: indicate the
assured forwarding
classes of service,
which are applicable
to services that require
an assured rate but no
l BE: is applicable to
services that does not
need to be processed
in a special manner.
recommended.
PW ID
Issue 01 (2016-04-30)


PW that carries the CES
service. This parameter is
meaningful when the
CES service type is UNINNI.
1817

Configuration Guide
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
meaningful when the
CES service type is UNINNI.
Sink Board
Displays the sink board

of the CES service. This
parameter is meaningful
when the CES service
type is UNI-UNI.
Sink High Channel
l Specifies the sink

higher order channel
of a CES service.
l This parameter is
valid only when the
CES service is a UNIUNI service and its
sink board is a
channelized STM-1
board.
Sink Low Channel
Displays the sink lower

order path. This
type is UNI-UNI.
Sink 64K Timeslot
Displays the sink 64

kbit/s timeslot. This
type is UNI-UNI.
Deployment Status

status of the CES service.

Parameter
Value Range
Default Value
Description
PW ID

PW that carries the CES
service.
Issue 01 (2016-04-30)

1818

Configuration Guide
Parameter
Value Range
Default Value
Description
Working Status
Displays working status

of the PW.
PW Status

status of the PW.
PW Signaling Type
Displays the PW
signaling type.
NOTE
The OptiX RTN 900
supports static PWs only.
PW Type
Displays the PW type for

CES service
encapsulation.
CESoPSN: Indicates
structure-aware TDM
circuit emulation service
over packet switched
network. Timeslot
compression can be set.
SAToP: Indicates
structure-agnostic TDM
over packet. Timeslot
compression cannot be
set.
Displays the tunnel type

for PW encapsulation.
NOTE
The OptiX RTN 900
supports MPLS only.
PW Incoming Label
Displays the Ingress label

of the PW that carries the
CES service.
PW Outgoing Label
Displays the Egress label

of the PW that carries the
CES service.
Peer LSR ID

Local Working Status

local end.
Remote Working Status

remote end.
Issue 01 (2016-04-30)

1819

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
Tunnel type

PW.
NOTE
The OptiX RTN 900
supports MPLS tunnels
only.
Tunnel

CES service.
Deployment Status

status of the tunnel.
Tunnel Automatic
Selection Policy

not support this
parameter.
Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
Direction

a PW.
CIR(kbit/s)

not support this
parameter.
EXP

not support this
parameter.
QoS Parameters

Parameter
Value Range
Default Value
Description
PW ID
Displays the PW ID.
Issue 01 (2016-04-30)

1820

Configuration Guide
Parameter
Value Range
Default Value
Description
RTP Header
Displays the RTP header.

The RTP header carries
time stamps.
Jitter Compensation
Buffering Time(us)

jitter buffer time.
Packet Loading
Time(us)
Displays the packet

loading time.
Ingress Clock Mode

not support this
parameter.
Egress Clock Mode

not support this
parameter.

continuity check (CC).
VCCV Verification
Mode
Displays the VCCV

used for PW CC.
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.
R Bit Inserting Status
1-65535

threshold of packet loss
ratio of CES services.
The corresponding alarm
will be reported if the
actual packet loss ratio
crosses this threshold.
This parameter is
available only when the
transparent transmission
of CES service alarms is
enabled.
Issue 01 (2016-04-30)
Disabled

1821

Configuration Guide
Parameter
Value Range
Default Value
Description
Bit Inserting Status
1-65535

threshold of received
CES service packets. The
this threshold. This
parameter is available
only when the transparent
transmission of CES
service alarms is enabled.
Sequence Number
Mode
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.
Protection Type

mode.
Issue 01 (2016-04-30)

1822

Configuration Guide
Parameter
Value Range
Default Value
Description
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 900
supports dual-ended
switching.
Revertive Mode
Non-revertive
Revertive
original working PW
after the fault is
rectified.
are switched to the
original working PW
switched to the
is recommended.
Issue 01 (2016-04-30)

1823

Configuration Guide
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 (100 ms)
0 to 100
0, the protection
switching once it
detects faults, but
otherwise, no
Deployment Status

group.
Switchover Status

group.
Protocol Status

Working Path Status


Issue 01 (2016-04-30)

1824

Configuration Guide

NOTE
Parameter
Value Range
Default Value
Description
Protection Group ID

PW APS protection
group triggers the
PW APS protection
Working PW ID

protection pair.
Protection PW ID

DNI PW ID
PW Type
Deployment Status

status of the slave
protection pair.
B.8.3.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.

Parameter
Value Range
Default Value
Description
Service ID (e.g.1,3-6)
1 to 4294967295
Specifies the
service ID.
Service name
Specifies the
service name.
Issue 01 (2016-04-30)

1825

Configuration Guide
Parameter
Value Range
Default Value
Description
Level
E1
E1
The value E1
indicates that the
CES service is
used to transmit
the TDM services
from E1 ports.
Service Type
Common
Common
l When this
parameter is
set to
common, CES
services are
used to
transmit
common CES
packets.
SOH only
l When this
parameter is
set to SOH
only, CES
services are
used to
transparently
transmit only
segment
overhead
bytes.
Mode
UNI-NNI
UNI-NNI
UNI-UNI
l Specifies the
mode of CES
service.
l The value
UNI-NNI
indicates that
the CES
service is
carried by a
PW.
Therefore, the
information
about the PW
needs to be
configured.
Issue 01 (2016-04-30)

1826

Configuration Guide
Parameter
Value Range
Default Value
Description
SOH Byte
D1-D12, E1-E2,
F1, K1-K2 and
X1-X4
l Specifies the
segment
overhead
bytes
transparently
transmitted by
CES services.
This
parameter can
be set
manually.
l This
parameter is
valid only
when Service
Type is set to
SOH only.
Source Board
Specifies the
board where the
source (UNI) of
the CES service is
located.
Source High Channel
l Specifies the
source higher
order channel
of a CES
service.
l This
parameter is
valid only
when the
source board
is a
channelized
STM-1 board.
Source Low Channel (e.g.1,3-6)
Issue 01 (2016-04-30)

If Level is set to
E1, this
parameter
indicates the E1
port where the
service source is
located. If Mode
is set to UNINNI, this
parameter can
assume only one
value.
1827

Configuration Guide
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 radio
link, the
timeslot lists
can be
different but
the numbers of
timeslots must
the same.
l This
parameter
does not need
to be set if
Mode is UNINNI and PW
Type is
SAToP.
Issue 01 (2016-04-30)

1828

Configuration Guide
Parameter
Value Range
Default Value
Description
Priority List
CS7
EF
l Specifies the
priority of a
CES service.
This
parameter is
available only
when Mode is
set to UNINNI.
CS6
EF
AF4
AF3
AF2
AF1
BE
l This
parameter
needs to be
configured if
QoS
processing
needs to be
performed for
different CES
services.
l CS6-CS7:
indicate the
highest service
classes, which
are mainly
involved in
signaling
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
Issue 01 (2016-04-30)

1829

Configuration Guide
Parameter
Value Range
Default Value
Description
require an
assured rate
but no delay
or jitter limit.
l BE: is
applicable to
services that
does not need
to be
processed in a
special
manner.
l The default
value is
recommended.
PW Type
CESoPSN
CESoPSN
SAToP
l Specifies the
type of the
PW. This
parameter is
available only
when Mode is
UNI-NNI.
l CESoPSN:
Indicates
structureaware TDM
circuit
emulation
service over
packet
switched
network.
Timeslot
compression
can be set.
SAToP:
Indicates
structureagnostic TDM
over packet.
Timeslot
compression
cannot be set.
Issue 01 (2016-04-30)

1830

Configuration Guide
Parameter
Value Range
Default Value
Description
Protection Type
No Protection
No Protection
l Specifies the
protection
mode of the
PW. This
parameter is
available only
when Mode is
UNI-NNI.
PW APS
Slave Protection
Pair
l If this
parameter is
set to PW
APS, working
and protection
PWs need to
be configured.
l When this
parameter is
set 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
simultaneousl
y.
Issue 01 (2016-04-30)

1831

Configuration Guide
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
l Specifies the
source higher
order channel
of a CES
service.
l This
parameter is
valid only
when the CES
service is a
UNI-UNI
service and its
sink board is a
channelized
STM-1 board.
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 Mode is
set to UNIUNI.
Issue 01 (2016-04-30)

1832

Configuration Guide
Parameter
Value Range
Default Value
Description
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 radio
link, the
timeslot lists
can be
different but
the numbers of
timeslots must
the same.
l This
parameter is
available only
when Mode is
set to UNIUNI.

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

PW Signaling Type
Static
Static

manually assigned.
PW Type
PW Direction

the PW.
Displays the
PW.
PW Incoming Label
16 to 1048575

label.
Issue 01 (2016-04-30)

1833

Configuration Guide
Parameter
Value Range
Default Value
Description
PW Outgoing Label
16 to 1048575

label.

select tunnels.
Tunnel Type
MPLS
MPLS

PW.
Tunnel
PW will fail.
Peer LSR ID

be automatically
assigned.
Egress Tunnel

the reverse tunnel
automatically.
Parameter
Value Range
Default Value
Description
EXP

QoS Parameters
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.
Issue 01 (2016-04-30)

1834

Configuration Guide
Parameter
Value Range
Default Value
Description
Jitter Compensation
Buffering Time (us)
875 to 16000
8000
l Specifies the jitter

buffer time for the
received CES packets.
The step is 125.
l The larger the jitter
compensation
buffering time, the
larger jitter CES
services can bear, and
the larger the network
latency.
l The jitter
compensation
buffering time should
be larger or equal to
(3 * packet loading
time + 2 * end-to-end
network jitter time).
recommended.
Packet Loading Time

(us)
125 to 5000
1000

fragments in the TDM
data stream. The step
is 125.
l A larger value of this
parameter means
higher encapsulation
efficiency but larger
delays of CES
services.
recommended.
Ingress Clock Mode
Null
Null


Adaptive Clock Mode

Egress Clock Mode
Issue 01 (2016-04-30)

1835

Configuration Guide
Parameter
Value Range
Default Value
Description
None
CW

PW continuity check
(CC).
CW
Alert Label
l The value None

indicates that the
control word is not
PW CC is not
supported.
VCCV packets in
Alert Label
encapsulation mode.
l The value CW
indicates that the
control word is
supported.
VCCV Verification
Mode
None
Ping
Ping

verification mode.
The VCCV
PW CC.
this parameter to
None.
Enable CES Service

Alarm Transparent
Transmission
Issue 01 (2016-04-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. Upon
receiving the fault
notification from the
network side or the
remote end, the local NE
inserts the corresponding
alarm to the AC side.
1836

Configuration Guide
Parameter
Value Range
Default Value
Description
R Bit Inserting Status
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.
Bit Inserting Status
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.
Sequence Number
Mode
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
to PW APS.
Parameter
Value Range
Default Value
Description
Protection Type

type.
Protection Group ID

group ID.
Issue 01 (2016-04-30)

1837

Configuration Guide
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
protection mode.
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
NOTE
Revertive Mode
Non-revertive
Revertive
Revertive
l This parameter
to the original
working PW after it
recovers.
are switched to the
original working PW
switched to the
is recommended.
Issue 01 (2016-04-30)

1838

Configuration Guide
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
Revertive Mode is
Revertive.
recommended.

(100 ms)
0 to 100

group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.
Detection mode

mode of the PW APS
protection group.
OAM Parameters
NOTE
Issue 01 (2016-04-30)

1839

Configuration Guide
Parameter
Value Range
Default Value
Description
OAM Status

status of PW OAM.
Detection Mode
Auto-Sensing
Auto-Sensing

mode of OAM
packets.
Manual
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 01 (2016-04-30)

1840

Configuration Guide
Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

the user.
this parameter
specifies the PW
OAM detection
packets to be
transmitted.
set to Manual, this
parameter specifies
the PW OAM
be received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
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.

be received.
Transmitted PW ID
received.
Issue 01 (2016-04-30)

1841

Configuration Guide

NOTE
Parameter
Value Range
Default Value
Description
Protection Mode

mode.
Protection Group ID

PW APS protection
group triggers the
PW APS protection
Working PW ID

protection pair.
Protection PW ID

B.8.4 ATM Parameters

This topic describes the parameters that are related to ATM services.
B.8.4.1 Parameter Description: ATM IMA Management_IMA Group

Management
This topic describes the parameters that are related to IMA group management.
Navigation Path
1.
2.
Click the IMA Group Management tab.

Parameter
Value Range
Default Value
Description
VCTRUNK
Displays the ATM

TRUNK.
Issue 01 (2016-04-30)

1842

Configuration Guide
Parameter
Value Range
Default Value
Description
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
Issue 01 (2016-04-30)
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 905
supports Symmetrical
Mode and
Symmetrical
Operation only. The
parameters Minimum
Number of Active
1843

Configuration Guide
Parameter
Value Range
Default Value
Description
Minimum Number of
Active Receiving Links
1 to 16
Transmitting Links
and Minimum
Number of Active
Receiving Links must
assume the same
value on the two ends
of an IMA link.
recommended.
IMA Protocol Version
1.0
1.1
l Specifies the IMA

protocol version.
1.1
l The parameter IMA

Protocol Version
must assume the same
of an IMA link.
recommended.
IMA Transmit Frame
Length
32
128
64
l Specifies the IMA

transmit frame length.
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
assume the same
of an IMA link.
recommended.
Issue 01 (2016-04-30)

1844

Configuration Guide
Parameter
Value Range
Default Value
Description
IMA Symmetry Mode
Symmetrical Mode and

Symmetrical Operation
Symmetrical Mode and

Symmetrical Operation
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 01 (2016-04-30)

1845

Configuration Guide
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
of an IMA link.
recommended.
Clock Mode
CTC 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.
B.8.4.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.
Issue 01 (2016-04-30)

1846

Configuration Guide
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
Bidirectional
Bidirectional
Displays the
direction of bound
paths. The fixed
value is
bidirectional.
The OptiX RTN 905

parameter.
Uplink
Downlink
Optical Interface
Issue 01 (2016-04-30)

1847

Configuration Guide
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.8.7
Setting Serial Port
Parameters.
Available Timeslots
The OptiX RTN 905

parameter.
Selected Bound Paths
Displays the bound

paths.
VCTRUNK
Displays the name of

the ATM TRUNK.
Level

bound paths.
Direction
Displays the
direction of bound
paths. The fixed
value is
bidirectional.
Bound Paths
Displays the bound

paths.
Number of Bound Paths
Displays the number

of bound paths.
Display in Combination
Selected
Selected
Specifies whether to
display bound paths
in combination.
Not selected
B.8.4.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 01 (2016-04-30)

1848

Configuration Guide

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.
B.8.4.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.
Differential Delay
Check Status

deferential delay check.
Near-End Receiving
Status
Displays the near-end

receiving status.
Issue 01 (2016-04-30)

1849

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
B.8.4.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 01 (2016-04-30)

1850

Configuration Guide
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
network-side 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 recommended that
you set ATM Cell
Payload Scrambling
to Enabled.
l ATM Cell Payload
Scrambling must
assume the same
of an ATM link.
Otherwise, packet loss
will occur.
Min. VPI
Issue 01 (2016-04-30)


not support this
parameter.
1851

Configuration Guide
Parameter
Value Range
Default Value
Description
Max. VPI

not support this
parameter.
Min. VCI

not support this
parameter.
Max. VCI

not support this
parameter.
VCC-Supported VPI
Count

not support this
parameter.
Loopback
No Loopback
No Loopback
Specifies the loopback

status of the port.
Outloop
Inloop
B.8.4.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 Relation
Name

mapping relationship.
UBR
BE
UBR: BE
CBR
AF11
CBR: EF
AF12
RT-VBR: AF31

PHB service classes that
correspond to different
ATM service types.
l Eight PHB service
classes are available:
BE, AF1, AF2, AF3,
RT-VBR
AF13
NRT-VBR: AF21
NRT-VBR
AF21
UBR+: AF11
UBR+
AF22
PORT-TRANS: BE
Issue 01 (2016-04-30)

1852

Configuration Guide
Parameter
Value Range
PORT-TRANS
AF23
AF31
AF32
AF33
AF41
AF42
AF43
EF
CS6
CS7
Default Value
Description
AF4, EF, CS6, and

CS7. The OptiX RTN
900 provides different
QoS policies for the
queues of different
service classes.
CS6 to CS7: highest
service classes,
mainly applicable to
signaling
transmission.
EF: fast forwarding,
of low transmission
delays and low packet
loss rates.
AF1 to AF4: assured
forwarding, applicable
an assured
transmission rate
rather than delay or
jitter limits.
The AF1 class
includes three
subclasses: AF11,
AF12, and AF13.
Only one of these
subclasses can take
effect for one queue.
It is the same case
with AF2, AF3, and
AF4.
BE: best effort,
that do not require
special processing.
B.8.4.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 01 (2016-04-30)

1853

Configuration Guide
Navigation Path
1.
QoS Management > Diffserv domain Management > ATM COS Mapping
2.
Click New.

Parameter
Value Range
Default Value
Description
Mapping Relation ID
2 to 8

mapping table.
Mapping Relation
Name

mapping relationship.
UBR
BE
AF11
AF12
AF13
AF21
AF22
AF23
AF31
AF32
AF33
AF41
AF42
AF43
EF
CS6
CS7
UBR: BE
Specifies the PHB service

classes that correspond to
different ATM service
types.
l Eight PHB service
classes are available:
BE, AF1, AF2, AF3,
AF4, EF, CS6, and
CS7. The OptiX RTN
900 provides different
QoS policies for the
queues of different
service classes.
l CS6 to CS7: highest
service classes,
mainly applicable to
signaling
transmission.
l EF: fast forwarding,
of low transmission
delays and low packet
loss rates.
l AF1 to AF4: assured
forwarding, applicable
an assured
transmission rate
rather than delay or
jitter limits.
The AF1 class
includes three
subclasses: AF11,
AF12, and AF13.
Only one of these
CBR
RT-VBR
NRT-VBR
UBR+
Issue 01 (2016-04-30)
CBR: EF
RT-VBR: AF31
NRT-VBR: AF21
UBR+: AF11
PORT-TRANS: BE

1854

Configuration Guide
Parameter
Value Range
Default Value
PORT-TRANS
Description
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.
B.8.4.8 Parameter Description: ATM Policy Management

This topic describes the parameters that are related to ATM policy management.
Navigation Path
1.
QoS Management > Policy Management > ATM Policy from the Function Tree.
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 01 (2016-04-30)

1855

Configuration Guide
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 01 (2016-04-30)

1856

Configuration Guide
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
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 01 (2016-04-30)

The Table B-100 lists the

ATM service type, traffic
type descriptor, and the
related traffic parameters.
ATM policies are
configured based on these
mapping relationships.
1857

Configuration Guide
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-100 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 01 (2016-04-30)

1858

Configuration Guide
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.
B.8.4.9 Parameter Description: ATM Policy Management_Creation

This topic describes the parameters that are related to creation of ATM policies.
Navigation Path
1.
QoS Management > Policy Management > ATM Policy from the Function Tree.
2.
Click New.

Parameter
Value Range
Default Value
Description
Policy ID
Specifies the policy ID of

the ATM service. The
policy ID can also be
automatically allocated.
Issue 01 (2016-04-30)

1859

Configuration Guide
Parameter
Value Range
Default Value
Description
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 01 (2016-04-30)

1860

Configuration Guide
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
Issue 01 (2016-04-30)

1861

Configuration Guide
Parameter
Value Range
Default Value
Description
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
UBR+ service are the
same as the
corresponding
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 01 (2016-04-30)

For the mapping

ATM service types, ATM
traffic type descriptors,
and traffic parameters,
see Table B-101. ATM
policies are configured
based on these mapping
relationships.
1862

Configuration Guide
Parameter
Value Range
Default Value
Description
Discard Traffic Frame
Enabled
Disabled
Specifies the frame

discarding mark in ATM
policies. This parameter
is effective to AAL5
traffic.
Disabled
l UPC is user-side
parameter control and
NPC is network-side
parameter control.
Disabled
UPC/NPC
Enabled
Disabled
l After UPC/NPC is
enabled, the cells with
a frame discarding
mark will be
discarded in network
congestion.
Table B-101 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
CBR
nrtVBR
rtVBR
Issue 01 (2016-04-30)

1863

Configuration Guide
ATM
Service
Type
UBR+
ATM Traffic Type

Descriptor
Traffic
Parameter 1
Traffic
Parameter 2
Traffic
Parameter 3
Traffic
Parameter 4
ClpTaggingScrCdvt
Clp01Pcr
Clp0Scr
MBS
CDVT
atmnotrafficdescriptormcr
Clp01Mcr
atmnoclpmcr
Clp01Pcr
Clp01Mcr
atmnoclpmcrcdvt
Clp01Pcr
Clp01Mcr
CDVT
B.8.4.10 Parameter Description: ATM Service Management

This topic describes the parameters that are related to ATM service management.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM

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.
Issue 01 (2016-04-30)

1864

Configuration Guide
Parameter
Value Range
Default Value
Description
PW ID

PW that carries ATM
PWE3 services, if any.
Sink Port
Displays the sink board

of the ATM service.
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 01 (2016-04-30)

1865

Configuration Guide
Parameters for Bound Paths

Parameter
Value Range
Default Value
Description
VCTRUNK
Level

bound paths.
Direction

bound paths. The fixed
value is bidirectional.
Bound Paths
Displays the 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
The OptiX RTN 900
uses 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 01 (2016-04-30)


of the PW.
1866

Configuration Guide
Tab
Parameter
Value Range
Default Value
Description
PW Encapsulation
Type
Displays the
NOTE
The OptiX RTN 900
uses MPLS only.
QoS
PW Incoming
Label
Displays the
configured PW Ingress
label.
PW Outgoing
Label
Displays the
configured PW Egress
label.
Peer LSR ID

the destination.
Tunnel Type
Displays the type of

the 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

of the PW.
Issue 01 (2016-04-30)

1867

Configuration Guide
Tab
Parameter
Value Range
Default Value
Description
Bandwidth Limit
whether the 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
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.
to the same value as
PIR.
CBS (kbyte)
the excess burst size of
the PW.
PIR (kbit/s)
the peak information
rate.
to the same value as
CIR.
PBS (kbyte)
the maximum excess
burst size of the PW.
EXP
The OptiX RTN 900

parameter.
Issue 01 (2016-04-30)

1868

Configuration Guide
Tab
Advanced
Attributes
Parameter
Value Range
Default Value
Description
Policy
The OptiX RTN 900

parameter.
Control Word
Must Use
whether to use the
control word. In the
MPLS packet
switching network, the
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 01 (2016-04-30)

1869

Configuration Guide
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
the packet will be
sent out once the
cell is loaded.
Parameters for CoS Mapping

Parameter
Value Range
Default Value
Description
PW ID

PW that carries the
service.
Issue 01 (2016-04-30)

1870

Configuration Guide
Parameter
Value Range
Default Value
Description
CoS Mapping
Specifies the policy for

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 900
supports dual-ended
switching.
Issue 01 (2016-04-30)

1871

Configuration Guide
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
is 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 (100 ms)
0 to 100
0, the protection
switching once it
detects faults, but
otherwise, no
Issue 01 (2016-04-30)

1872

Configuration Guide
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

PW APS protection
group triggers the
PW APS protection
Working PW ID

protection pair.
Protection PW ID

DNI PW ID
PW Type
Deployment Status

status of the slave
protection pair.
Issue 01 (2016-04-30)

1873

Configuration Guide
B.8.4.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 need to
be configured.
l UNI-UNI: This value
applies to common
ATM services. Only
the attributes in
Connection need to
be configured.
Issue 01 (2016-04-30)

1874

Configuration Guide
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 Nto-1/1-to-1 VPC
encapsulation mode.
l PVC: This value
applies to the Nto-1/1-to-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
UNIs-NNI.
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 01 (2016-04-30)

1875

Configuration Guide
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 01 (2016-04-30)

1876

Configuration Guide
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

need to be manually
assigned.
PW Type
The ATM connection

type is PVC:
The ATM connection

type 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
The ATM connection

type is PVP:
l In the case of ATM

1_to_1 encapsulation,
one PW carries one
VPC or VCC.
The ATM connection

type 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.
Issue 01 (2016-04-30)

1877

Configuration Guide
Parameter
Value Range
Default Value
Description
Tunnel Type
MPLS
MPLS

PW.
Tunnel
PW will fail.
Peer LSR ID

be automatically
assigned.
Parameter
Value Range
Default Value
Description
Bandwidth Limit

bandwidth limit is
enabled.
QoS Parameters
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
Issue 01 (2016-04-30)


not support this
parameter.
1878

Configuration Guide
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

the PW.
PBS (kbyte)

excess burst size of the
PW.
EXP

not support this
parameter.
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 control word is
used to transmit
packet information.
No Use
l Set Control Word to

Must Use if PW Type
is ATM 1:1.
Issue 01 (2016-04-30)

1879

Configuration Guide
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

verification mode.
The VCCV
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 01 (2016-04-30)

1880

Configuration Guide
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
the packet will be sent
out once the cell is
loaded.

NOTE
to 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
protection mode.
Issue 01 (2016-04-30)

1881

Configuration Guide
Parameter
Value Range
Default Value
Description
Working PW ID

working PW.
Protection PW ID

protection PW.
Switching Mode

PW fails.
NOTE
Revertive Mode
Non-revertive
Revertive
Revertive
l This parameter
to the original
working PW after it
recovers.
are switched to the
original working PW
switched to the
is recommended.
Time (min)
1 to 12
l Specifies the WTR

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.
Issue 01 (2016-04-30)

1882

Configuration Guide
Parameter
Value Range
Default Value
Description

(100 ms)
0 to 100

group.
0, the protection
switching once it
detects faults, but
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 01 (2016-04-30)

1883

Configuration Guide
Parameter
Value Range
Default Value
Description
Detection Mode
Auto-Sensing
Auto-Sensing

mode of OAM
packets.
Manual
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
recommended.
Issue 01 (2016-04-30)

1884

Configuration Guide
Parameter
Value Range
Default Value
Description
CV
CV
l CV: The detection

fixed interval.
FFD

the user.
this parameter
specifies the PW
OAM detection
packets to be
transmitted.
set to Manual, this
parameter specifies
the PW OAM
be received and
transmitted.
l The value FFD is
assumed for PW APS
and the value CV is
assumed for
continuous CC on
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.

be received.
Transmitted PW ID
received.
Issue 01 (2016-04-30)

1885

Configuration Guide

NOTE
Parameter
Value Range
Default Value
Description
Protection Mode

mode.
Protection Group ID

PW APS protection
group triggers the
PW APS protection
Working PW ID

protection pair.
Protection PW ID

Parameters for CoS Mapping

Parameter
Value Range
Default Value
Description
PW ID

PW that carries service.
CoS Mapping
Specifies the policy for

priorities. By setting this
parameter, different
quality measures are
provided for different
ATM services.
B.8.4.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.
Issue 01 (2016-04-30)

1886

Configuration Guide
Navigation Path
1.
ATM OAM Management from the Function Tree.
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 01 (2016-04-30)

1887

Configuration Guide
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 01 (2016-04-30)

1888

Configuration Guide
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 01 (2016-04-30)

1889

Configuration Guide
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 segmentend 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.
B.8.4.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 01 (2016-04-30)

1890

Configuration Guide
Navigation Path
1.
2.
Click the CC Activation Status tab.

Parameter
Value Range
Default Value
Description
Source

Sink

Issue 01 (2016-04-30)

1891

Configuration Guide
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
UNI port side to
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 to the UNI
port side.
Issue 01 (2016-04-30)

1892

Configuration Guide
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 01 (2016-04-30)

1893

Configuration Guide
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.
B.8.4.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.
Issue 01 (2016-04-30)

1894

Configuration Guide
Navigation Path
1.
2.
Click the Remote Loopback Test tab.

Parameter
Value Range
Default Value
Description
Source

Sink

Issue 01 (2016-04-30)

1895

Configuration Guide
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
UNI port side to
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 to the UNI
port side.
Issue 01 (2016-04-30)

1896

Configuration Guide
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.
B.8.4.15 Parameter Description: ATM OAM Management_LLID

This topic describes the parameters that are related to LLID configuration.
Navigation Path
1.
2.
Click the LLID tab.
Issue 01 (2016-04-30)

1897

Configuration Guide

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.
B.8.4.16 Parameter Description: ATM OAM_ATM Cell Insertion Status

This section describes the parameters for configuring the ATM cell insertion status.
Navigation Path
1.
Select a desired NE from the Object Tree in the NE Explorer. Choose Configuration >
2.
Click the Insert OAM Cell to ATM tab.
Issue 01 (2016-04-30)

1898

Configuration Guide

Parameter
Value Range
Default Value
Description
Insert OAM Cell to

ATM
Enabled
Enabled
l Normally, retain the

default value Enabled
for this parameter to
ensure normally
functioning of the
AIS/RDI function on
the ATM connection
for which segment
and end attributes
have been configured.
Disabled

Disabled when the
AIS/RDI function on
the ATM connection
for which segment
and end attributes
have been configured
needs to be disabled.
B.8.5 MP Group Parameters

This section describes parameters that are used for configuring an MP group.
B.8.5.1 Parameter Description: MP Group Management_Creation

This parameter describes the parameters that are used for creating an MP group.
Navigation Path
1.
2.
3.
Click New.
Parameters in the Window for Setting MP Group Parameters

Parameter
Value Range
Default Value
Description
MP Group Number
0 to 255
Specifies the MP group

ID.
Name
Specifies the MP group

name.
Issue 01 (2016-04-30)

1899

Configuration Guide
Parameter
Value Range
Default Value
Description
Specify IP Address
Manually
Manually
you set Specify IP
Address to Manually.
Set Specify IP Address

to Manually, and set IP
Address and IP Mask
according to the service
plan.
Borrow NE IP Address
Borrow Interface IP
Address
Unspecified
IP Address
0.0.0.0
IP Mask
255.255.255.252
Peer IP

not allow this parameter
to be specified.
Board for Borrowed IP

Address

to be specified.
Port for Borrowed IP

Address

to be specified.
Min Activated Link

Count
1 to 16
l If you want the

interruption of N PPP
links to trigger MPLS
APS of the entire MP
group, set Min
Activated Link
Count as required.
l Generally, Min
Activated Link
Count takes its
default value 1.
l Set Min Activated
Link Count to the
same value for both
end of a radio link.
Enable Differential
Delay
Disabled
Disabled
Enabled
l If you set Enable

Differential Delay to
Enabled and a
member link has
excessive delay, this
link does not perform
the data packet slicing.
l It is recommended
that this parameter
Issue 01 (2016-04-30)

1900

Configuration Guide
Parameter
Value Range
Default Value
Description
Max Differential Delay

(100us)
25 to 500
500
l This parameter takes

effect only when
Enable Differential
Delay is set to
Enabled.
l It is recommended
that Max Differential
Delay (100us) take its
default value at both
ends of the radio link.
Enable Tunnel
Disabled
Disabled
Enabled
l If you set Enable

Tunnel to Enabled,
the port identifies and
processes MPLS
labels.
l It is recommended
that you set this
l If services have been
configured, do not set
Enable Tunnel to
Disabled.
MTU(byte)
960 to 1620
1450
l Indicates the
maximum transport
unit. When the length
of a packet received
by a port is greater
than the set MTU
value, this packet will
be discarded.
l It is recommended
that you set this
parameter to 1620,
which is the same as
the MTU for MPLS
ports.
Issue 01 (2016-04-30)

1901

Configuration Guide
Parameter
Value Range
Default Value
Description
Fragmentation
Unfragmented
64
l Specifies the
fragmentation size. If
the fragmentation size
is small, the
scheduling efficiency
of each member link is
enhanced. In this case,
packet overheads are
increased. As a result,
bandwidth utilization
of the link is affected.
64
128
256
512
l Set Fragmentation to
the same value for
link.
l It is recommended
that you set this
parameter to
Unfragmented.
Sequence Number Type
Huawei mode
Huawei mode
Long Serial Number

Short Serial Number
l Set Sequence
Number Type to the
same value for both
l When Short Serial
Number is supported
at both ends of the
radio link, Short
Serial Number is
preferred.
OSICP Negotiation

to be specified.
Send CRC BER

Threshold-crossing
Event

to be specified.
B.8.5.2 Parameter Description: MP Group Management_Basic Attributes

This section describes the parameters that are used for configuring the MP group attributes.
Navigation Path
1.
2.
Issue 01 (2016-04-30)

1902

Configuration Guide
Parameters in the window for setting MP group attributes

Parameter
Value Range
Default Value
Description
MP Group Number
Displays the MP group

ID.
Name
Displays the MP group

name.
Link Status
l Displays the link

status.
l If Link Status is Up,
the MLPPP is
functional.
l If Link Status is
Down, the MLPPP is
abnormal. Locate and
handle the fault.
Send Rate (kbit/s)
Displays the send rate of

MP group.
Receive Rate (kbit/s)
Displays the receive rate

of MP group.
Min Activated Link

Count
1 to 16
l If you want the

interruption of some
PPP links to trigger
MPLS APS of the
entire MP group, set
Min Activated Link
Count as desired.
l Generally, Min
Activated Link
Count takes its
default value 1.
l Set Min Activated
Link Count to the
same value for both
end of a radio link.
Enable Differential
Delay
Disabled
Enabled
l If you set Enable

Differential Delay to
Enabled and a
member link has
excessive delay, this
link does not perform
the data packet slicing.
l It is recommended
that this parameter
Issue 01 (2016-04-30)

1903

Configuration Guide
Parameter
Value Range
Default Value
Description
Max Differential Delay

(100us)
25 to 500

effect only when
Enable Differential
Delay is set to
Enabled.
l It is recommended
that Max Differential
Delay (100us) take its
default value at both
Enable Tunnel
Disabled
Enabled
l If you set Enable

Tunnel to Enabled,
the port identifies and
processes MPLS
labels.
l It is recommended
that you set this
l If services have been
configured, do not set
Enable Tunnel to
Disabled.
Max.Reserved
Bandwidth (kbit/s)

to be specified.
TE Measurement

to be specified.
Admin Group

to be specified.
IP Address Negotiation
Result
IP Mask Negotiation
Result
Displays the IP address

and mask of the MP
group.
Issue 01 (2016-04-30)

1904

Configuration Guide
Parameter
Value Range
Default Value
Description
MTU
960 to 1620
l The MTU indicates

the maximum
transport unit. When
the length of a packet
received by a port is
greater than the set
MTU value, this
packet will be
discarded.
l It is recommended
that you set this
parameter to 1620,
which is the same as
the MTU for MPLS
ports.
Fragmentation
Unfragmented
64
128
256
512
l Specifies the
fragmentation size. If
the fragmentation size
is small, the
scheduling efficiency
of each member link is
enhanced. In this case,
packet overheads are
increased. As a result,
bandwidth utilization
of the link is affected.
l Set Fragmentation to
the same value for
link.
l It is recommended
that you set this
parameter to
Unfragmented.
Sequence Number Type
Huawei mode
Long Serial Number

Short Serial Number
l Set Sequence
Number Type to the
same value for both
l When Short Serial
Number is supported
at both ends of the
radio link, Short
Serial Number is
preferred.
OSICP Negotiation
Issue 01 (2016-04-30)


to be specified.
1905

Configuration Guide
Parameter
Value Range
Default Value
Description
Send CRC BER

Threshold-crossing
Event

to be specified.
B.9 Clock Parameters

This topic describes the parameters that are related to clocks.
B.9.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.

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.
B.9.2 Physical Clock Parameters

This topic describes physical clock parameters.
B.9.2.1 Parameter Description: Clock Source Priority Table

This topic describes the parameters that are related to the priority table of a clock source.
Issue 01 (2016-04-30)

1906

Configuration Guide
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 01 (2016-04-30)

1907

Configuration Guide
Parameters
Parameter
Value Range
Default Value
Description
Clock Source
l For OptiX RTN 905,

External clock source
is the external clock
source provided by
the CLK/TOD/MON
port on the front panel
of the chassis.
1 indicates the
external clock source
at the CLK/TOD1
port on the CST or
CSH board in
physical slot 7.
2 indicates the
at the CLK/TOD1
port on the CST or
CSH board in
physical slot 8.
l For OptiX RTN
910A, External clock
source 1 indicates the
at the CLK, TOD, or
MON port on the
CSHR board in
physical slot 1.
l For OptiX RTN
950A, External clock
at the CLK/TOD1
port on the CSHO
board in physical slot
7. External clock
at the CLK/TOD1
port on the CSHO
8.
1 indicates the
Issue 01 (2016-04-30)

1908

Configuration Guide
Parameter
Value Range
Default Value
Description
at the CLK/TOD1
port on the CSHN
15. External clock
at the CLK/TOD1
port on the CSHN
20.
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.
External Clock Source

Mode
2 Mbit/s
2 Mbit/s
2 MHz
l This parameter
indicates the type of
the external clock
source signal.
according to the
external clock signal.
In normal cases, the
external clock signal
is a 2 Mbit/s signal.
Issue 01 (2016-04-30)

1909

Configuration Guide
Parameter
Value Range
Default Value
Description
Synchronous Status
Byte
SA4 to SA8
SA4
l This parameter is
valid only when
External Clock
Source Mode is set to
2 Mbit/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. 1 indicates the
highest clock source
priority.
B.9.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.
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.
Issue 01 (2016-04-30)

1910

Configuration Guide
Parameters for configuring the priority table for the PLL clock source of the
external clock port
Parameter
Value Range
Default Value
Description
Clock Source
Internal 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 01 (2016-04-30)

Displays the valid status

of clock sources.
1911

Configuration Guide
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.
B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet

This topic describes the parameters that are related to a clock subnet.
Navigation Path
1.
> Physical Clock > Clock Subnet Configuration.
2.
Click the Clock Subnet tab.
Parameters for Setting a Clock Subnet

Parameter
Value Range
Default Value
Description
Affiliated Subnet

this parameter.
Issue 01 (2016-04-30)

1912

Configuration Guide
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.
l If the SSM protocol is
stopped, it indicates
Issue 01 (2016-04-30)

1913

Configuration Guide
Parameter
Value Range
Default Value
Description
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 01 (2016-04-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.
1914

Configuration Guide
Parameter
Value Range
Default Value
Description
Clock Source ID
(None)
(None)
l This parameter is
valid only when the
extended SSM
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
B.9.2.4 Parameter Description: Clock Subnet Setting_Clock Quality

This topic describes the parameters that are related clock quality.
Navigation Path
1.
> Physical Clock > Physical Clock Subnet Configuration.
2.
Click the Received Quality tab.
Issue 01 (2016-04-30)

1915

Configuration Guide
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 01 (2016-04-30)

1916

Configuration Guide
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
transit exchange clock
signal specified in
ITU-T G.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
specified in ITU-T G.
812 but higher than
the quality level of the
local exchange clock
signal specified in
ITU-T G.812.
l G.812 Local Clock:
the local exchange
Issue 01 (2016-04-30)

1917

Configuration Guide
Parameter
Value Range
Default Value
Description
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
higher than 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 higher than the
quality level
unavailable in the
synchronous timing
source.
B.9.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 01 (2016-04-30)

1918

Configuration Guide
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,
Disabled.
B.9.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.
Navigation Path
1.
2.
Click the Clock ID Output tab.
Issue 01 (2016-04-30)

1919

Configuration Guide
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.
B.9.2.7 Parameter Description: Clock Source Switching_Clock Source Restoration

Parameters
This topic describes the parameters that are related to clock source restoration.
Issue 01 (2016-04-30)

1920

Configuration Guide
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.
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
recommended that
to Non-Revertive.
Issue 01 (2016-04-30)

1921

Configuration Guide
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
This parameter is
used to avoid frequent
switching of the clock
source due to
instability of the clock
source state within a
short time.
l This parameter is
valid only when
Higher Priority
Clock Source
Reversion is set to
Auto-Revertive.
B.9.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.
> Physical Clock > Clock Source Switching.
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 01 (2016-04-30)

1922

Configuration Guide
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.9.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.
Issue 01 (2016-04-30)

1923

Configuration Guide
Parameter
Value Range
Default Value
Description
Clock Source
Displays the clock

source.
AIS Alarm
Yes
No

recommended.
No

is set to Yes, it
indicates that clock
source switching
occurs if the clock
source reports the AIS
alarm.
is set to No, it
indicates that no clock
source switching
occurs if the clock
source reports 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

is set to Yes, it
indicates that clock
source switching
occurs if the clock
source reports the B2EXC alarm.
is set to No, it
indicates that no clock
source switching
occurs if the clock
source reports the B2EXC alarm.
Issue 01 (2016-04-30)

1924

Configuration Guide
B.9.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
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
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
output of the NE.
External Clock Output

Mode
2 Mbit/s
2 Mbit/s
l This parameter
specifies the mode of
the output clock.
External Clock Source 2
2 MHz

according to the
external clock signal.
In normal cases, the
external clock signal
is a 2 Mbit/s signal.
1 provides 2 MHz
clock signals.
2 provides 2 Mbit/s
clock signals.
Issue 01 (2016-04-30)

1925

Configuration Guide
Parameter
Value Range
Default Value
Description
External Clock Output

Timeslot
SA4 to SA8
ALL
l This parameter is
valid only when
External Clock
Output Mode is set
to 2 Mbit/s.
ALL
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.
l It is recommended
that you use the
default value.
External Source Output
Threshold
Threshold Disabled
Threshold Disabled
Not Inferior to G.813

SETS Signal
Local Signal
Transit Clock Signal
Clock Signal
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.
to Threshold
Disabled, it indicates
that the external clock
source always outputs
the clock signal.
l It is recommended
that 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.
l It is recommended
that you use the
default value.
Issue 01 (2016-04-30)

1926

Configuration Guide
Parameter
Value Range
Default Value
Description
2M Phase-Locked
Source Failure Handing
Shut Down Output
Shut Down Output
l This parameter is
valid only when 2M
Phase-Locked
Source Failure
Condition is not set
to No Failure
Condition.
2M Output S1 Byte
Unavailable
Send AIS
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.
l It is recommended
that you use the
default value.
B.9.2.11 Parameter Description: Clock Synchronization Status

This topic describes the parameters that are related to the clock synchronization status.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
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.
Issue 01 (2016-04-30)

1927

Configuration Guide
Parameter
Value Range
Default Value
Description
Synchronous Source

the synchronization
source.
Issue 01 (2016-04-30)

1928

Configuration Guide
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 01 (2016-04-30)

1929

Configuration Guide
B.9.3 CES ACR Clock Parameters

This topic describes CES ACR clock parameters.
B.9.3.1 Parameter Description: ACR Clock Source

This topic describes parameters that are related to the adaptive clock recovery (ACR) clock
source.
Navigation Path

Parameter
Value Range
Default Value
Description
ACR Clock Source
Identifies the ACR clock

domain.
CES Service

or 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.
B.9.3.2 Parameter Description: Clock Domain

This topic describes parameters that are related to clock domains.
Navigation Path
Clock > Clock Domain from the Function Tree.
Issue 01 (2016-04-30)

1930

Configuration Guide

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.9.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.
CES ACR1 Clock

Domain
CES ACR2 Clock
Domain
CES ACR3 Clock
Domain
CES ACR4 Clock
Domain
Clock Domain Board

the clock domain is
located.
Board
Specifies the board where

the Smart E1 port is
located.
Available Port

ports that are not bound
to a clock domain.
Issue 01 (2016-04-30)

1931

Configuration Guide
Parameter
Value Range
Default Value
Description
Selected Port

ports that are bound to a
clock domain.
B.9.4 PTP Clock Parameters

This topic describes PTP clock parameters.
B.9.4.1 Parameter Description: Clock Synchronization Attribute

This topic describes parameters that are used for creating a point to point (PTP) clock port.
Navigation Path
Issue 01 (2016-04-30)

1932

Configuration Guide

Parameter
Value Range
Default Value
Description
PTP System Time
Displays an upstream
clock source that the
selected PTP NE traces.
The traced time can be
transmitted to a
downstream NE through
a PTP port (using IEEE
1588v2 messages) or an
external time port (using
1PPS+ToD time signals).
NOTE
l An OptiX RTN 900 NE
supporting the IEEE
1588v2 protocol is a
PTP NE.
l A PTP NE's port
supporting the IEEE
1588v2 protocol is a
PTP port.
l If an NE is not tracing a
PTP clock source, you
can specify PTP
System Time for the
NE. You can specify
PTP System Time for
an NE only when
testing the IEEE
1588v2 function on the
NE. On a live network,
PTP System Time
displays the upstream
clock source that the
selected NE traces.
NE Name
Issue 01 (2016-04-30)


local NE.
1933

Configuration Guide
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
TC
TC+BC
l An NE in BC mode
supports multiple PTP
ports and is used as an
intermediate network
node.
l A TC provides
multiple PTP ports for
processing and
forwarding IEEE
1588 messages.
However, it does not
recover a clock from
the received IEEE
1588 messages.
l The TC+BC mode
supports both time
transparent
transmission and time
synchronization.
Static BMC
Disabled
Disabled
Specifies the state of the

BMC algorithm. This
parameter can be set
manually.
NON_SLAVE_ONLY

set only in OC mode.
Enabled
Slave_Only
SLAVE_ONLY
NON_SLAVE_ONLY

is set to
SLAVE_ONLY, the
NE can function only
as a slave clock node.
is set to
NON_SLAVE_ONL
Y, the NE can
function as a master
clock node.
Issue 01 (2016-04-30)

1934

Configuration Guide
Parameter
Value Range
Default Value
Description
PTP Time Adjustment
Enabled
Enabled
l If the PTP system

time needs to be
adjusted (for example,
during network-wide
time synchronization),
Enabled.
Disabled
l If the PTP system

time (for example,
1588 ACR clock)
does not need to be
adjusted, set this
parameter to
Disabled.
Packet Multicast Mode
Fully Multicasted
Fully Multicasted
Partially Multicasted
l If Packet Multicast
Mode is set to Fully
Multicasted, SYNC,
ANNOUNCE, and
DELAY packets are
multicast.
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.
Issue 01 (2016-04-30)

1935

Configuration Guide
Parameter
Value Range
Default Value
Description
Protocol Packet Format
NMEA
UBX
l Specifies the protocol

that an external time
port uses for
transmitting TOD
signals.
UBX
l NMEA is an
international protocol
and the commonest
value.
l UBX is a protocol
defined by the
ULBOX company.
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.
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.
Issue 01 (2016-04-30)

1936

Configuration Guide
Parameter
Value Range
Default Value
Description
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.
Clock Type
l The working mode of

a PTP port can be
manually set to BC or
TC only when NE
Clock Type is set to
TC+BC and the PTP
port is an Ethernet
port.
l Set the parameter
according to the
service plan.
Issue 01 (2016-04-30)

1937

Configuration Guide
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 twostep 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 01 (2016-04-30)

1938

Configuration Guide
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 The parameter at both
ends of a PTP link
must be set to the
same.
In the case of the
OC/BC ports of
RTN equipment
which are directly
connected to
another RTN
equipment, it is
recommended that
PTP messages
adopt Ethernet
encapsulation
without VLAN ID.
Set the VLAN
attribute of a TC
port in compliance
with port L2
attribute and the
requirement for
transparently
transmitting
services.
In the case of the
PTP ports of RTN
equipment which
are connected to
external PTP
equipment, set the
PTP packet
encapsulation
format and VLAN
ID according to the
requirement of
external PTP
equipment.
Issue 01 (2016-04-30)

1939

Configuration Guide
Parameter
Value Range
Default Value
Description
PTP Packet
Encapsulation Format
PTP ETH
PTP ETH
l If Layer 2
encapsulation needs to
be performed for PTP
packets, set this
parameter to PTP
ETH.
PTP IP
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.
Port Status
MASTER+SLAVE
MASTER+SLAVE
MASTER
SLAVE
the default status of a
PTP port.
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.
Issue 01 (2016-04-30)

1940

Configuration Guide
Parameter
Value Range
Default Value
Description
Current Port Status
l Displays the actual

port status.
l This parameter value
is determined based
on the BMC
algorithm.
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.
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 first 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.
l This parameter is
valid only if the ACR
clock source is
configured.
l Not supported by
OptiX RTN 905.
Issue 01 (2016-04-30)

1941

Configuration Guide
Port Message Parameters

Parameter
Value Range
Default Value
Description
Port
Displays the PTP port

names.
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.
l This parameter must
be set to the same
opposite PTP NEs.
The default value is
recommended.
DELAY Packet Period

(s)

for transmitting
DELAY packets.
be set to the same
opposite PTP NEs.
recommended.
NOTE
only if P/E Mode is E2E.
Issue 01 (2016-04-30)

1942

Configuration Guide
Parameter
Value Range
Default Value
Description
PDELAY Packet Period

(s)

for transmitting
PDELAY packets.
be set to the same
opposite PTP NEs.
recommended.
NOTE
only if P/E Mode is P2P.
ANNOUNCE Packet
Period (s)

for transmitting
ANNOUNCE
packets.
be set to the same
opposite PTP NEs.
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.
be set to the same
opposite PTP NEs.
recommended.
Issue 01 (2016-04-30)

1943

Configuration Guide
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 01 (2016-04-30)

1944

Configuration Guide
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.
B.9.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.
B.9.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.
Issue 01 (2016-04-30)
Configuration > Clock > PTP Clock > Clock Subnet Configuration from the
Function Tree.
1945

Configuration Guide
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.
B.9.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.

Parameter
Value Range
Default Value
Description
NE Name

local NE.
Time Quality Level
0-255
187
l The smaller the

higher the quality.
recommended.
Time Precision
0-255
254
l The smaller the

higher the time
accuracy.
recommended.
Issue 01 (2016-04-30)

1946

Configuration Guide
Parameter
Value Range
Default Value
Description
Clock Source Type
INTERNAL_OSCILLAT
OR
INTERNAL_OSCILLAT
OR

the local clock source.
ATOMIC_CLOCK

recommended.
GPS
TERRESTRIAL_RADIO
PTP
NTP
HAND_SET
OTHER
Clock Source Priority 1
0-255
128
l The smaller the

it is recommended
that you set this
parameter to the
default value.
l For other OptiX RTN
900 products, 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.
0-255
128
l The smaller the

recommended.
NOTE
Select the optimal clock
source according to the
following preference
sequence: Clock source
priority 1 > Time precision
> Time quality level >
Clock source priority 2.
B.9.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.
Issue 01 (2016-04-30)

1947

Configuration Guide
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 NE 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.
Egress
l Specifies the time

transmission
direction.
Direction
Egress
Ingress
l If the NE receives
time information from
its external clock port,
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 NE, this parameter
can be set to RS422 only.
Issue 01 (2016-04-30)

1948

Configuration Guide
B.9.4.6 Parameter Description: External Time Port_BMC

This topic describes BMC parameters for an external time port.
Navigation Path
1.
Tree.
2.
Click the BMC tab.

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_OSCILLAT
OR
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
The smaller the

TERRESTRIAL_RADIO
PTP
NTP
HAND_SET
OTHER
INTERNAL_OSCILLAT
OR
Issue 01 (2016-04-30)
0-255

1949

Configuration Guide
Parameter
Value Range
Default Value
Description
0-255
128
The smaller the

higher the clock priority.
NOTE
Select the optimal clock
source according to the
following preference
sequence: Clock source
priority 1 > Time precision
> Time quality level >
Clock source priority 2.
B.9.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.
Tree.
2.
Click the Cable Transmitting Distance tab.

Parameter
Value Range
Default Value
Description

external time port.
Transmitting Direction
Egress
Displays the time input/

output direction.
Ingress
Issue 01 (2016-04-30)

1950

Configuration Guide
Parameter
Value Range
Default Value
Description
Transmitting Distance
Mode
Length
Length
l Specifies the
transmission delay
compensation mode.
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 Time(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.
B.9.5 Parameter Description: Auxiliary Ports

This section describes the parameters required for configuring auxiliary ports.
Issue 01 (2016-04-30)

1951

Configuration Guide
Navigation Path
In the NE Explorer, select the desired NE from the Object Tree and choose Configuration >
Auxiliary Interface from the Function Tree.

Parameter
Value Range
Default Value
Description
Port
Displays the port that

functions as the auxiliary
port.
Interface Mode
l For OptiX RTN

950/950A/980/980L,
The ID of the outdoor
cabinet monitoring
port is 2.
l For OptiX RTN
905/910A, The ID of
the outdoor cabinet
monitoring port is 1.
l For OptiX RTN
950/950A/980/980L/
910A, If the outdoor
cabinet of the NE is
monitored through an
outdoor cabinet
monitoring port, set
Interface Mode to
MON for the outdoor
cabinet monitoring
port.
If the outdoor cabinet
of the NE is
monitored through an
outdoor cabinet
monitoring port, set
Interface Mode to
External clock (Hz)
+outdoor cabinet for
the outdoor cabinet
monitoring port.
B.10 Parameters for the Orderwire and Auxiliary

Interfaces
This topic describes the parameters that are related to the orderwire and auxiliary interfaces.
Issue 01 (2016-04-30)

1952

Configuration Guide
B.10.1 Parameter Description: Orderwire_General

This topic describes the parameters that are used for general orderwire features.
Navigation Path
1.
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 01 (2016-04-30)
Dual-Tone
Frequency
This parameter indicates the dialing mode

of the orderwire phone.

1953

Configuration Guide
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 NE dials the telephone
number 888, the orderwire phones of
all the NEs on the orderwire subnet
ring. When an NE 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.
Phone 1
100 to 99999999
101
l This parameter specifies the orderwire

phone number of the local station. An
addressing call refers to a point-topoint 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.
B.10.2 Parameter Description: Orderwire_Advanced

This topic describes the parameters that are used for advanced orderwire features.
Issue 01 (2016-04-30)

1954

Configuration Guide
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.
B.10.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
This parameter indicates the number of the

F1 data port.
Data Channel 1
l If a synchronous data port functions as

the data channel, set this parameter to
F1.
Data Channel 2
l If an overhead byte of a transmission

line functions as the data channel, set
this parameter to the associated line
port.
Issue 01 (2016-04-30)

1955

Configuration Guide
B.10.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 asynchronous data services.
l In the case of a radio link, a customized
serial overhead byte in the microwave
frame is used to transmit asynchronous
data services.
Broadcast Data
Source
No Data
l If the service source is an asynchronous

data port, set this parameter to
SERIAL1.
l If the service source is an overhead
byte of a transmission line, set this
parameter to the associated line port.
Available
Broadcast Data
Sink
This parameter indicates the available

broadcast data sink.
Selected Broadcast
Data Sink
l If the service sink is an asynchronous

data port, set this parameter to
SERIAL1.
l If the service sink is an overhead byte
of a transmission line, set this
parameter to the associated line port.
B.10.5 Parameter Description: Environment Monitoring Interface

This topic describes the parameters that are used for environment monitoring interfaces.
Navigation Path
Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration >
Function Tree.
Issue 01 (2016-04-30)

1956

Configuration Guide
Parameters for the Basic Attributes

Parameter
Value Range
Default Value
Description
Operation Object
This parameter indicates the operation

object.
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.
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.
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 01 (2016-04-30)

1957

Configuration Guide
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.
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
This parameter indicates whether the

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.
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.
Issue 01 (2016-04-30)

1958

Configuration Guide
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
Issue 01 (2016-04-30)
CSK-1
CSK-2

1959

Configuration Guide
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.
ASBR
See autonomous system boundary router.
Issue 01 (2016-04-30)

1960

Configuration Guide
C Glossary
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.
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.
Issue 01 (2016-04-30)

1961

Configuration Guide
C Glossary
automatic transmit
power control (ATPC)
A method of adjusting the transmit power based on fading of the transmit signal
detected 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.
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.
Issue 01 (2016-04-30)

1962

Configuration Guide
C Glossary
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 Xbit 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
services digital
network (B-ISDN)
A standard defined by the ITU-T to handle high-bandwidth applications, such as

voice. It currently uses the ATM technology to transmit data over SONNET-based
circuits at 155 to 622 Mbit/s or higher speed.
broadcast
A means of delivering information to all members in a network. The broadcast range

is determined by the broadcast address.
broadcast domain
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.
Issue 01 (2016-04-30)

1963

Configuration Guide
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
C Glossary
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
Request Broker
of programs (objects) communicate with other objects in other programs, even if the
Architecture (CORBA) two 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
A tie used to bind cables.
carrier sense multiple

access with collision
detection (CSMA/CD)
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
(CPU)
interprets 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.
Issue 01 (2016-04-30)

1964

Configuration Guide
C Glossary
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.

(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.
cyclic redundancy
check (CRC)
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) errorchecking values.
D
DC
direct current
DC-C
See DC-return common (with ground).
DC-I
See DC-return isolate (with ground).
Issue 01 (2016-04-30)

1965

Configuration Guide
DC-return common
(with ground) (DC-C)
C Glossary
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
ground) (DC-I)
with 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.
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.
Issue 01 (2016-04-30)

1966

Configuration Guide
C Glossary
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 logic 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.
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).
Issue 01 (2016-04-30)

1967

Configuration Guide
C Glossary
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 logic
device (EPLD)
A logic 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.
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.
Issue 01 (2016-04-30)

1968

Configuration Guide
C Glossary
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
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.
Issue 01 (2016-04-30)

1969

Configuration Guide
C Glossary
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This
(GTS)
is 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.
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
Issue 01 (2016-04-30)

1970

Configuration Guide
C Glossary
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.
indoor unit (IDU)
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.
Issue 01 (2016-04-30)

1971

Configuration Guide
C Glossary
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 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 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.
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)
Issue 01 (2016-04-30)
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.

1972

Configuration Guide
C Glossary
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.
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.
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.
Issue 01 (2016-04-30)

1973

Configuration Guide
C Glossary
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.
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.
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
information base
(MIB)
A type of database used for managing the devices in a communications network. It

comprises a collection of objects in a (virtual) database used to manage entities (such
as routers and switches) in a network.
maximum
transmission unit
(MTU)
The largest packet of data that can be transmitted on a network. MTU size varies,
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.
Issue 01 (2016-04-30)

1974

Configuration Guide
C Glossary
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a
instance (MSTI)
simply and fully connected active topology for frames classified as belonging to a
VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be
assigned to multiple MSTIs.
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
A radio link protection system composed of N working channels and one protection
channel.
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
point (NSAP)
available 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
Issue 01 (2016-04-30)

1975

Configuration Guide
C Glossary
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.
P
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.
Issue 01 (2016-04-30)

1976

Configuration Guide
C Glossary
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 (PVP)
Virtual path that consists of PVCs.
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
sequence (PRBS)
of the values of any of the other elements, similar to a real random sequence.
pseudo wire (PW)
Issue 01 (2016-04-30)
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.

1977

Configuration Guide
C Glossary
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of
edge-to-edge (PWE3) a 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
QPSK
See quadrature phase shift keying.
QinQ
See 802.1Q in 802.1Q.
QoS
See quality of service.
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 two-bit 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.
Issue 01 (2016-04-30)

1978

Configuration Guide
C Glossary
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.
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial In User Service
access control mechanism. As a distributed server/client system, RADIUS provides
(RADIUS)
the AAA function.
Request For
Comments (RFC)
A document in which a standard, a protocol, or other information pertaining to the

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 indicator
(RSSI)
The received wide band power, including thermal noise and noise generated in the
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.
Issue 01 (2016-04-30)

1979

Configuration Guide
C Glossary
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.
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.
Issue 01 (2016-04-30)

1980

Configuration Guide
C Glossary
Synchronization Status A message that carries the quality levels of timing signals on a synchronous timing
Message (SSM)
link. SSM messages provide upstream clock information to nodes on an SDH network
or synchronization network.
Synchronous
Transport Module
level 1 (STM-1)
Synchronous transfer mode at 155 Mbit/s.
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
module (STM)
consists of information payload and Section Overhead (SOH) information fields
organized in a block frame structure which repeats every 125. The information is
suitably conditioned for serial transmission on the selected media at a rate which is
synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed
STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic
rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are
under consideration.
T
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
Issue 01 (2016-04-30)

1981

Configuration Guide
C Glossary
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.
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.
Issue 01 (2016-04-30)

1982

Configuration Guide
C Glossary
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.
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.
Issue 01 (2016-04-30)

1983

Configuration Guide
user-to-network
interface (UNI)
C Glossary
The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
V-NNI
virtual network-network interface
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
point-to-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
Issue 01 (2016-04-30)

1984

Configuration Guide
C Glossary
WCDMA
See Wideband Code Division Multiple Access.
WDM
wavelength division multiplexing
WEEE
waste electrical and electronic equipment
WFQ
See weighted fair queuing.
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 highpriority packet when calculating the packet loss ratio.
winding pipe
A tool for fiber routing, which acts as the corrugated pipe.
X
XPIC
Issue 01 (2016-04-30)
See cross-polarization interference cancellation.

1985

RTN 900 V100R009C00 Configuration Guide 01

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RTN 900 V100R009C00 Configuration Guide 01

Hochgeladen von

Copyright:

Verfügbare Formate

OptiX RTN 900 Radio Transmission System

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

About This Document

About This Document

OptiX RTN 900

The intended audiences of this document are:

Installation and commissioning engineer

Data configuration engineer

System maintenance engineer

Huawei Proprietary and Confidential

OptiX RTN 900 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 01 (2016-04-30) Based on Product Version V100R009C00

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

4 Mapping between Configuration Examples and Scenarios................................................13

6 Configuring Microwave Links..................................................................................................55

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

7 Configuring TDM Services....................................................................................................... 83

8 Configuring Native Ethernet Services...................................................................................116

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

8.4 Process of Configuration on a Per-NE Basis (Native Ethernet E-Line)..................................................................... 138

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

8.9.3.5 Verifying Ethernet Services.................................................................................................................................. 216

9 Configuring Ethernet Services on EoS/EoPDH Boards..................................................... 262

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

9.5.2.2 Configuring Native Ethernet Service Information............................................................................................... 290

10 Configuring MPLS Tunnels.................................................................................................. 307

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

10.5.2.4 Verifying MPLS Tunnels.................................................................................................................................... 376

11 Configuring ETH PWE3 Services......................................................................................... 412

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

11.7.2.2 Configuring Service Information........................................................................................................................447

12 Configuring CES Services......................................................................................................486

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

12.4.1 Networking Diagram............................................................................................................................................. 500

13 Configuring ATM Services....................................................................................................520

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

13.4.2.2 Configuring ATM/IMA Information.................................................................................................................. 552

14 Configuring the Clock............................................................................................................ 566

15 Configuring Auxiliary Ports and Functions....................................................................... 582

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System

15.9.2 Configuration Procedure........................................................................................................................................604

16 Adding and Modifying Configuration Data......................................................................607

A Task Collection......................................................................................................................... 627

Huawei Proprietary and Confidential

OptiX RTN 900 Radio Transmission System