RTN 900 V100R009C10 Feature Configuration Guide 02

OptiX RTN 900 Radio Transmission System
V100R009C10
Feature Configuration Guide
Issue 02
Date 2017-12-25
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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 02 (2017-12-25) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Feature 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 V100R009C10
iManager U2000 V200R016C60
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 features in the manual
are based on a specific product, but are applicable to other OptiX RTN 900 products that support the features.
For example, the configuration example for LAG 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
l Data configuration engineer
l System maintenance engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation

which, if not avoided, will result in death or
serious injury.
Issue 02 (2017-12-25) Huawei Proprietary and Confidential ii

Symbol Description
Indicates a potentially hazardous situation

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

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

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

best practices and tips.
NOTE is used to address information not
related to personal injury, equipment
damage, and environment deterioration.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

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

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

V100R009C10
This issue is the second official issue for the V100R009C10 product version.
Issue 02 (2017-12-25) Huawei Proprietary and Confidential iii

Change Description
- Fixed the known bugs.
Updates in Issue 01 (2017-05-20) Based on Product Version

V100R009C10
This is the first document issue for the V100R009C10 product version.
Issue 02 (2017-12-25) Huawei Proprietary and Confidential iv

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

1 Configuring Network Management Features.......................................................................... 1
1.1 Configuration Procedure (HWECC Solution)................................................................................................................ 3
1.2 Configuration Procedure (IP DCN Solution)................................................................................................................. 6
1.3 Configuration Procedure (DCC Bytes Transparent Transmission Solution)................................................................10
1.4 Configuration Procedure (DCC Transmission Through the External Clock Port Solution)........................................ 11
1.5 Configuration Process (L2 DCN Solution).................................................................................................................. 12
1.6 Configuration Process (SNMP).................................................................................................................................... 18
1.7 Configuration Procedure (LLDP)................................................................................................................................. 19
1.8 Configuration Procedure (RADIUS)............................................................................................................................ 20
1.9 Configuration Process (NE Anti-Theft Solution)......................................................................................................... 21
1.10 Configuration Example (HWECC Solution).............................................................................................................. 22
1.10.1 Networking Diagram............................................................................................................................................... 22
1.10.2 Configuration Procedure..........................................................................................................................................23
1.11 Configuration Example (IP DCN Solution in Single OSPF Area).............................................................................29
1.12 Configuration Example (IP DCN Solution in Multiple OSPF Areas)........................................................................36
1.13 Configuration Example (IP DCN Solution Using OSPF Multi-process)................................................................... 47
1.14 Configuration Example (DCC Bytes Transparent Transmission Solution)................................................................54
1.15 Configuration Example (DCC Transmission Through the External Clock Port Solution)........................................ 60
1.16 Configuration Example (L2 DCN Solution, with Third-Party DCN Packets Not Identified by VLAN IDs)............62
1.17 Configuration Example (L2 DCN Solution, with Third-Party DCN Packets Identified by VLAN IDs)...................68
Issue 02 (2017-12-25) Huawei Proprietary and Confidential v


1.18 Configuration Example (SNMP)................................................................................................................................ 76
1.19 Configuration Example (LLDP)................................................................................................................................. 77
1.20 Configuration Example (RADIUS)............................................................................................................................ 79
1.21 Configuration Example (NE Anti-Theft Solution)..................................................................................................... 83
2 Configuring Microwave Features.............................................................................................87

2.1 Configuration Process (1+1 HSB/FD/SD)................................................................................................................... 88
2.2 Configuration Procedure (N+1 Protection).................................................................................................................. 91
2.3 Configuration Process (XPIC)......................................................................................................................................92
2.4 Configuration Process (AM)........................................................................................................................................ 93
2.5 Configuration Procedure (ATPC)................................................................................................................................. 94
2.6 Configuration Process (PLA/EPLA/EPLA+)...............................................................................................................94
2.7 Configuration Example (1+1 HSB/FD/SD on an NE)................................................................................................. 95
2.7.1 Networking Diagram................................................................................................................................................. 95
2.7.2 Configuration Procedure............................................................................................................................................96
2.8 Configuration Example (1+1 HSB/FD/SD on Cascaded NEs).................................................................................. 101
2.9 Configuration Example (XPIC on an NE)..................................................................................................................106
2.10 Configuration Example (XPIC on Cascaded NEs)...................................................................................................111
2.10.1 Networking Diagram............................................................................................................................................. 111
2.10.2 Configuration Procedure........................................................................................................................................112
2.11 Configuration Example (N+1 Protection).................................................................................................................113
2.12 Configuration Example (ATPC)............................................................................................................................... 119
2.13 Configuration Example (AM).................................................................................................................................. 124
Issue 02 (2017-12-25) Huawei Proprietary and Confidential vi

2.14 Configuration Example (PLA on an NE)................................................................................................................. 127

2.15 Configuration Example (PLA on Cascaded NEs).................................................................................................... 131
2.16 Configuration Example (EPLA)............................................................................................................................... 134
3 Configuring SDH Protection Features.................................................................................. 138

3.1 Configuration Procedure(LMSP)............................................................................................................................... 138
3.2 Configuration Procedure(SNCP)................................................................................................................................ 139
3.3 Configuration Procedure (Ring MSP)........................................................................................................................ 140
3.4 Configuration Example (SNCP)................................................................................................................................. 141
3.5 Configuration Example (LMSP)................................................................................................................................ 141
3.6 Configuration Example (Ring MSP).......................................................................................................................... 145
4 Configuring Native Ethernet Features.................................................................................. 149

4.1 Configuration Process (ERPS on a Single-ring Network)..........................................................................................151
4.2 Configuration Process (ERPS on a Multi-ring Network)........................................................................................... 151
4.3 Configuration Procedure (MSTP).............................................................................................................................. 153
4.4 Configuration Procedure (LAG).................................................................................................................................154
4.5 Configuration Procedure (LPT)..................................................................................................................................155
4.6 Configuration Process (QoS/HQoS)...........................................................................................................................157
4.7 Configuration Process (Ethernet Service OAM)........................................................................................................ 162
4.8 Configuration Procedure (Ethernet Port OAM)......................................................................................................... 165
4.9 Configuration Process (Bandwidth Notification)....................................................................................................... 166
4.10 Configuration Procedure (IGMP Snooping).............................................................................................................167
4.11 Configuration Example (ERPS on a Single-ring Network)......................................................................................168
4.12 Configuration Example (ERPS on a Multi-ring Network)....................................................................................... 173
4.13 Configuration Example (MSTP).............................................................................................................................. 179
4.14 Configuration Example (LAG).................................................................................................................................183
Issue 02 (2017-12-25) Huawei Proprietary and Confidential vii


4.15 Configuration Example (LPT for Services Traversing an L2 Network).................................................................. 186
4.15.1 Network Diagram.................................................................................................................................................. 186
4.16 Configuration Example (LPT for Services Traversing a PSN)................................................................................ 190
4.16.1 Network Diagram.................................................................................................................................................. 190
4.17 Configuration Example (QoS)..................................................................................................................................193
4.18 Configuration Example (HQoS)............................................................................................................................... 198
4.19 Configuration Example (Ethernet Service OAM).................................................................................................... 205
4.20 Configuration Example (Ethernet Port OAM)......................................................................................................... 212
4.21 Configuration Example (Bandwidth Notification)................................................................................................... 215
4.22 Configuration Example (IGMP Snooping)...............................................................................................................220
5 Ethernet Features on the EoS/EoPDH Boards...................................................................... 224

5.1 Configuration Procedure (ERPS)............................................................................................................................... 225
5.2 Configuration Procedure (STP/RSTP)....................................................................................................................... 226
5.3 Configuration Procedure (IGMP Snooping)...............................................................................................................227
5.4 Configuration Procedure (LAG).................................................................................................................................228
5.5 Configuration Procedure (LPT)..................................................................................................................................228
5.6 Configuration Procedure (QoS)..................................................................................................................................229
5.7 Configuration Procedure (Ethernet Service OAM).................................................................................................... 230
5.8 Configuration Procedure (Ethernet Port OAM)......................................................................................................... 233
5.9 Configuration Example (EVPL Services Based on the VLAN).................................................................................234
5.9.2 Configuration Process..............................................................................................................................................236
5.10 Configuration Example (EVPL Services Based on QinQ).......................................................................................239
5.10.2 Configuration Process............................................................................................................................................241
5.11 Configuration Example (EPLAN Services Based on the 802.1D Bridge)............................................................... 246
Issue 02 (2017-12-25) Huawei Proprietary and Confidential viii


5.12 Configuration Example (EVPLAN Services Based on the 802.1Q Bridge)............................................................ 251
5.13 Configuration Example (EVPLAN Services Based on the 802.1ad Bridge)........................................................... 256
5.14 Configuration Example (ERPS)............................................................................................................................... 262
5.15 Configuration Example (STP/RSTP)....................................................................................................................... 264
5.16 Configuration Example (IGMP Snooping)...............................................................................................................267
5.17 Configuration Example (LAG).................................................................................................................................268
5.18 Configuration Example (LPT)..................................................................................................................................269
5.19 Configuration Example (QoS)..................................................................................................................................271
5.20 Configuration Example (Ethernet Service OAM).................................................................................................... 276
5.21 Configuration Example (Ethernet Port OAM)......................................................................................................... 278
6 Configuring MPLS/PWE3 Features........................................................................................281

6.1 Configuration Procedure (MPLS OAM_Y.1711)....................................................................................................... 282
6.2 Configuration Procedure (LSP Ping/Traceroute)....................................................................................................... 283
6.3 Configuration Procedure (MPLS APS)...................................................................................................................... 285
6.4 Configuration Procedure (PW OAM_Y.1711)........................................................................................................... 289
6.5 Configuration Procedure (PW Ping/Traceroute)........................................................................................................ 289
6.6 Configuration Procedure (PW APS)...........................................................................................................................290
6.7 Configuration Process (MPLS-TP OAM).................................................................................................................. 293
6.8 Configuration Procedure (IMA)................................................................................................................................. 300
6.9 Configuration Procedure (ATM OAM)...................................................................................................................... 301
6.10 Configuration Procedure (ATM Traffic Management).............................................................................................304
Issue 02 (2017-12-25) Huawei Proprietary and Confidential ix

6.11 Configuration Procedure (ML-PPP)......................................................................................................................... 305

6.12 Configuration Example (MPLS OAM_Y.1711)....................................................................................................... 307
6.12.1 Network Diagram.................................................................................................................................................. 307
6.13 Configuration Example (LSP Ping/Traceroute)....................................................................................................... 308
6.14 Configuration Example (MPLS APS)...................................................................................................................... 311
6.14.1 Network Diagram.................................................................................................................................................. 311
6.15 Configuration Example (PW OAM_Y.1711)........................................................................................................... 314
6.15.1 Network Diagram.................................................................................................................................................. 314
6.16 Configuration Example (PW Ping/Traceroute)........................................................................................................ 315
6.16.1 Network Diagram.................................................................................................................................................. 316
6.17 Configuration Example (PW APS)...........................................................................................................................317
6.17.1 Network Diagram.................................................................................................................................................. 318
6.18 Configuration Example (PW FPS)........................................................................................................................... 322
6.19 Configuration Example (MPLS-TP OAM for Tunnels)...........................................................................................325
6.20 Configuration Example (MPLS-TP OAM for PWs)................................................................................................ 330
6.21 Configuration Example (IMA)................................................................................................................................. 335
6.21.1 Network Diagram.................................................................................................................................................. 335
6.22 Configuration Example (ATM OAM)...................................................................................................................... 338
6.22.1 Network Diagram.................................................................................................................................................. 339
6.23 Configuration Example (ATM Traffic Management)...............................................................................................341
6.23.1 Network Diagram.................................................................................................................................................. 341
7 Configuring Clock Features.................................................................................................... 345

7.1 Configuration Procedure (IEEE 1588v2)................................................................................................................... 346
7.2 Configuration Process (ITU-T G.8275.1)...................................................................................................................349
7.3 Configuration Procedure (CES ACR)........................................................................................................................ 354
7.4 Configuration Procedure (IEEE 1588 ACR).............................................................................................................. 354
Issue 02 (2017-12-25) Huawei Proprietary and Confidential x

7.5 Configuration Example (Network-wide Time Synchronization ).............................................................................. 356

7.5.1 Network Diagram.................................................................................................................................................... 356
7.6 Configuration Example (Transparent Transmission of Time Signals)....................................................................... 363
7.7 Configuration Example (ITU-T G.8275.1).................................................................................................................369
7.8 Configuration Example (CES ACR).......................................................................................................................... 375
7.8.1 Network Diagram.................................................................................................................................................... 375
7.9 Configuration Example (IEEE 1588 ACR)................................................................................................................ 378
7.9.1 Network Diagram.................................................................................................................................................... 378
8 Configuring Maintenance Features....................................................................................... 383

8.1 Configuration Procedure (RMON)............................................................................................................................. 383
8.2 Configuration Process (IP Packet Coloring and Statistics Collection).......................................................................384
8.3 Configuration Example (RMON)............................................................................................................................... 385
8.3.2 Troubleshooting Analysis........................................................................................................................................ 386
8.3.3 Troubleshooting Flow..............................................................................................................................................386
8.4 Configuration Example (IP Packet Coloring and Statistics Collection).....................................................................387
8.4.1 Network Diagram.................................................................................................................................................... 387
A Task Collection......................................................................................................................... 393

A.1 U2000 Quick Start..................................................................................................................................................... 394
A.1.1 Logging in to a U2000 Client................................................................................................................................. 394
A.1.2 Shutting Down a U2000 Client...............................................................................................................................395
A.1.3 Using Online Help.................................................................................................................................................. 395
A.1.4 Navigating to Common Views................................................................................................................................396
A.1.4.1 Navigating to the Main Topology........................................................................................................................396
A.1.4.2 Navigating to the NE Explorer............................................................................................................................ 396
A.1.4.3 Navigating to the NE Panel................................................................................................................................. 397
A.2 Web LCT Quick Start................................................................................................................................................ 398
A.2.1 Using Online Help.................................................................................................................................................. 398
A.2.2 Navigating to the NE Explorer............................................................................................................................... 398
A.3 Network Management............................................................................................................................................... 399
A.3.1 Managing NEs........................................................................................................................................................ 399
A.3.1.1 Creating NEs by Using the Search Method (U2000).......................................................................................... 399
A.3.1.2 Creating NEs by Using the Search Method (Web LCT)..................................................................................... 401
A.3.1.3 Creating NEs by Using the Manual Method (U2000)......................................................................................... 403
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xi

A.3.1.4 Creating NEs by Using the Manual Method (Web LCT).................................................................................... 405
A.3.1.5 Logging In to an NE (Web LCT).........................................................................................................................406
A.3.1.6 Configuring the Logical Board............................................................................................................................ 407
A.3.1.7 Configuring an SFP Port......................................................................................................................................408
A.3.1.8 Configuring the Backplane Bus Rate.................................................................................................................. 412
A.3.1.9 Changing the NE ID............................................................................................................................................ 413
A.3.1.10 Changing the NE Name..................................................................................................................................... 414
A.3.1.11 Enabling NE Automatic Reporting....................................................................................................................415
A.3.1.12 Synchronizing the NE Time (U2000)................................................................................................................ 415
A.3.1.13 Synchronizing the NE Time (Web LCT)........................................................................................................... 418
A.3.1.14 Localizing the NE Time.....................................................................................................................................419
A.3.1.15 Configuring Standard NTP Keys.......................................................................................................................420
A.3.1.16 Configuring NE Anti-Theft............................................................................................................................... 421
A.3.1.17 Querying the Anti-Theft Status of Boards.........................................................................................................424
A.3.2 Configuring the NE Data........................................................................................................................................ 424
A.3.2.1 Uploading the NE Data (U2000)......................................................................................................................... 425
A.3.2.2 Synchronizing NE Data (U2000).........................................................................................................................425
A.3.3 Configuring the Performance Monitoring Status of NEs....................................................................................... 426
A.3.4 Suppressing Alarms for Monitored Objects........................................................................................................... 428
A.3.5 Connecting Fibers or Cables...................................................................................................................................428
A.3.5.1 Creating Optical Fibers by Using the Search Method......................................................................................... 429
A.3.5.2 Creating Fibers Manually.................................................................................................................................... 430
A.3.5.3 Searching for Ethernet Links............................................................................................................................... 430
A.3.5.4 Creating an Extended ECC.................................................................................................................................. 432
A.3.5.5 Creating a Back-to-Back Radio Connection........................................................................................................433
A.3.6 Managing Subnets.................................................................................................................................................. 434
A.3.6.1 Creating a Subnet.................................................................................................................................................434
A.3.6.2 Copying Topology Objects.................................................................................................................................. 436
A.3.6.3 Moving Topology Objects................................................................................................................................... 436
A.3.7 Managing Communication..................................................................................................................................... 437
A.3.7.1 Setting NE IP Communication Parameters..........................................................................................................437
A.3.7.2 Configuring DCCs............................................................................................................................................... 438
A.3.7.3 Configuring DCC Transparent Transmission...................................................................................................... 439
A.3.7.4 Configuring the VLAN ID and Bandwidth Used by an Inband DCN.................................................................440
A.3.7.5 Configuring the Priority of Inband DCN Packets................................................................................................441
A.3.7.6 Configuring Inband DCN Ports........................................................................................................................... 442
A.3.7.7 Configuring Access Control................................................................................................................................ 443
A.3.7.8 Configuring Extended ECC Communication...................................................................................................... 444
A.3.7.9 Creating a Static IP Route....................................................................................................................................446
A.3.7.10 Creating Static Route Entries in Kernel Route Tables.......................................................................................446
A.3.7.11 Setting OSPF Protocol Parameters.................................................................................................................... 447
A.3.7.12 Creating an OSPF Area..................................................................................................................................... 448
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xii

A.3.7.13 Configuring the Network Information of an ABR............................................................................................ 449

A.3.7.14 Creating a Manual Route Aggregation Group...................................................................................................450
A.3.7.15 Configuring the OSPF Authentication Type......................................................................................................451
A.3.7.16 Enabling the Proxy ARP....................................................................................................................................452
A.3.7.17 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used.................................................. 452
A.3.7.18 Querying ECC Routes....................................................................................................................................... 453
A.3.7.19 Querying IP Routes............................................................................................................................................454
A.3.7.20 Querying Core Routing Table Entries............................................................................................................... 454
A.3.7.21 Querying OSPF Neighbor Information............................................................................................................. 455
A.3.7.22 Verifying Connectivity of an ECC Network......................................................................................................456
A.3.7.23 Verifying Connectivity of an IP DCN Network................................................................................................ 457
A.3.7.24 Setting SNMP Communications Parameters..................................................................................................... 458
A.3.7.25 Configuring the Active and Standby Gateway NEs.......................................................................................... 459
A.3.8 Configuring the NMS Port......................................................................................................................................460
A.3.8.1 Configuring Basic Parameters for the NMS Port................................................................................................ 460
A.3.8.2 Setting the VLAN ID for Huawei NMS.............................................................................................................. 461
A.3.8.3 Changing the Encapsulation Type and QinQ Type Domain for the Ethernet NMS Port.................................... 462
A.3.8.4 Configuring the Network Management Serial Port on an NE............................................................................. 463
A.3.8.5 Configuring the Mini USB Port...........................................................................................................................464
A.4 Security Management................................................................................................................................................ 464
A.4.1 Configuring an NE User......................................................................................................................................... 464
A.4.1.1 Creating an NE User............................................................................................................................................ 465
A.4.1.2 Changing the Password of an NE User................................................................................................................466
A.4.1.3 Configuring Additional User Information........................................................................................................... 467
A.4.1.4 Setting Warning Screen Parameters.....................................................................................................................468
A.4.1.5 Querying NE User Groups...................................................................................................................................469
A.4.1.6 Managing Online NE Users.................................................................................................................................470
A.4.1.7 Switching NE Users.............................................................................................................................................471
A.4.2 Configuring USB Access Status............................................................................................................................. 472
A.4.3 Configuring LCT Access to NEs............................................................................................................................ 472
A.4.4 Configuring SSL Protocol Communication............................................................................................................473
A.4.4.1 Configuring SSL Protocol Communication Between a U2000 Server and its Clients........................................473
A.4.4.2 Configuring the Connection Mode Between a U2000 Client and Its Gateway NE............................................ 474
A.4.5 Configuring RADIUS Authentication.................................................................................................................... 476
A.4.5.1 Enabling/Disabling the RADIUS Function......................................................................................................... 476
A.4.5.2 Creating a RADIUS Server or a RADIUS Proxy Server.................................................................................... 477
A.4.5.3 Configuring RADIUS Server Parameters............................................................................................................479
A.4.5.4 Configuring a KMC Key..................................................................................................................................... 480
A.4.6 Configuring LLDP..................................................................................................................................................481
A.4.6.1 Configuring the Transmit Parameters for LLDP Packets.................................................................................... 481
A.4.6.2 Configuring LLDP for an Ethernet Port.............................................................................................................. 482
A.4.6.3 Querying LLDP Neighbor Relationship.............................................................................................................. 482
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xiii

A.5 Managing Radio Links.............................................................................................................................................. 483

A.5.1 Configuring a Single-Hop Radio Link................................................................................................................... 483
A.5.2 Creating an IF 1+1 Protection Group..................................................................................................................... 486
A.5.3 Modifying the Parameters of IF 1+1 Protection..................................................................................................... 488
A.5.4 Creating an N+1 Protection Group......................................................................................................................... 490
A.5.5 Querying the IF 1+1 Protection Status................................................................................................................... 492
A.5.6 Querying the IF N+1 Protection Status.................................................................................................................. 493
A.5.7 IF 1+1 Protection Switching...................................................................................................................................494
A.5.8 IF N+1 Protection Switching.................................................................................................................................. 495
A.5.9 Starting/Stopping the N+1 Protection Protocol...................................................................................................... 496
A.5.10 Creating a PLA/EPLA/EPLA+/Super EPLA Group............................................................................................ 496
A.5.11 Querying the Status of a PLA/EPLA/EPLA+/Super EPLA Group...................................................................... 504
A.5.12 Configuring Ethernet Frame Header Compression over Air Interfaces............................................................... 504
A.5.13 Configuring Enhanced Ethernet Frame Compression.......................................................................................... 505
A.5.14 Setting AES-based Encryption at Air Interfaces.................................................................................................. 506
A.6 Managing the MSP.................................................................................................................................................... 507
A.6.1 Configuring Linear MSP........................................................................................................................................ 507
A.6.2 Querying the Status of the Linear MSP.................................................................................................................. 509
A.6.3 Performing Linear MSP Switching........................................................................................................................ 509
A.6.4 Starting/Stopping the Linear MSP Protocol........................................................................................................... 510
A.6.5 Configuring Ring MSP........................................................................................................................................... 511
A.6.6 Querying Ring MSP Status.....................................................................................................................................512
A.6.7 TriggeMSP ring Ring Switching............................................................................................................................ 513
A.6.8 Starting/Stopping the MSP Ring Protocol.............................................................................................................. 514
A.6.9 Creating a Packet-based Linear MSP Group.......................................................................................................... 514
A.6.10 Querying the Status of a Packet-based Linear MSP Group..................................................................................516
A.6.11 Performing Packet-based Linear MSP Switching.................................................................................................516
A.6.12 Enabling/Disabling the Linear MSP Protocol...................................................................................................... 517
A.7 Managing TDM Services...........................................................................................................................................518
A.7.1 Creating the Cross-Connections of Point-to-Point Services...................................................................................518
A.7.2 Creating Cross-Connections of SNCP Services..................................................................................................... 519
A.7.3 Modifying the Priorities of E1 Services................................................................................................................. 520
A.7.4 Inserting E1_AIS upon a TU_AIS Condition.........................................................................................................522
A.7.5 Configuring the Automatic Switching of SNCP Services...................................................................................... 523
A.7.6 Deleting Cross-Connections................................................................................................................................... 524
A.7.7 Converting a Normal Service into an SNCP Service............................................................................................. 525
A.7.8 Converting an SNCP Service to a Normal Service................................................................................................ 527
A.7.9 Querying TDM Services.........................................................................................................................................528
A.7.10 Switching SNCP Services.....................................................................................................................................528
A.7.11 Querying the Protection Status of SNCP Services............................................................................................... 529
A.8 Managing Ports.......................................................................................................................................................... 529
A.8.1 Setting the Parameters of SDH Ports......................................................................................................................530
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xiv

A.8.2 Setting Working Modes of E1 Ports....................................................................................................................... 530

A.8.3 Setting the Parameters of PDH Ports......................................................................................................................531
A.8.4 Configuring Overhead Bytes.................................................................................................................................. 532
A.8.4.1 Configuring RSOHs.............................................................................................................................................532
A.8.4.2 Configuring VC-4 POHs..................................................................................................................................... 533
A.8.4.3 Configuring VC-12 POHs................................................................................................................................... 535
A.8.5 Changing the E1 Frame Format and Frame Mode for a Channelized STM-1....................................................... 537
A.8.6 Setting Smart E1 Port Parameters...........................................................................................................................537
A.8.6.1 Setting Basic Attributes of Smart E1 Ports..........................................................................................................537
A.8.6.2 Setting Advanced Attributes of Smart E1 Ports.................................................................................................. 538
A.8.7 Setting Serial Port Parameters................................................................................................................................ 539
A.8.7.1 Creating Serial Ports............................................................................................................................................ 539
A.8.7.2 Setting Basic Attributes of Serial Ports............................................................................................................... 540
A.8.8 Setting Ethernet Port Parameters............................................................................................................................ 541
A.8.8.1 Setting the Basic Attributes of Ethernet Ports..................................................................................................... 541
A.8.8.2 Configuring the Traffic Control of Ethernet Ports...............................................................................................542
A.8.8.3 Setting the Layer 2 Attributes of Ethernet Ports..................................................................................................543
A.8.8.4 Setting Layer 3 Attributes of Ethernet Ports........................................................................................................544
A.8.8.5 Setting the Advanced Attributes of Ethernet Ports..............................................................................................545
A.8.9 Setting Microwave Port Parameters....................................................................................................................... 546
A.8.9.1 Setting the Basic Attributes of IF_ETH Ports..................................................................................................... 546
A.8.9.2 Setting the Layer 2 Attributes of IF_ETH Ports.................................................................................................. 547
A.8.9.3 Setting Layer 3 Attributes of IF_ETH Ports........................................................................................................547
A.8.9.4 Setting the Advanced Attributes of IF_ETH Ports.............................................................................................. 548
A.8.10 Setting IF Port Parameters.................................................................................................................................... 549
A.8.10.1 Setting IF Attributes.......................................................................................................................................... 549
A.8.10.2 Configuring ATPC Attributes............................................................................................................................ 551
A.8.10.3 Setting Advanced AM Attributes...................................................................................................................... 552
A.8.10.4 Querying the AM Status.................................................................................................................................... 553
A.8.10.5 Querying ATPC Adjustment Records................................................................................................................553
A.8.10.6 Changing the IF Service Type........................................................................................................................... 554
A.8.10.7 Changing the Running Mode of an IF Port....................................................................................................... 555
A.8.10.8 Enabling or Disabling the AM Booster Function.............................................................................................. 556
A.8.10.9 Modifying the Hybrid/AM Attributes............................................................................................................... 556
A.8.11 Setting RFU/RFU-SD/ODU Port Parameters.......................................................................................................558
A.8.11.1 Setting ODU Transmit Frequency Attributes.................................................................................................... 559
A.8.11.2 Querying ODU Information...............................................................................................................................559
A.8.11.3 Setting ODU Power Attributes.......................................................................................................................... 560
A.8.11.4 Setting ODU Advanced Attributes.................................................................................................................... 561
A.8.12 Creating VLAN Sub-Interfaces............................................................................................................................ 562
A.9 Configuring Native Ethernet Services and Features..................................................................................................563
A.9.1 Managing ERPS......................................................................................................................................................563
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xv

A.9.1.1 Creating Ethernet Ring Protection Instances....................................................................................................... 563

A.9.1.2 Setting Global ERPS Protocol Parameters.......................................................................................................... 565
A.9.1.3 Setting Protocol Parameters for an ERPS Instance............................................................................................. 565
A.9.1.4 Creating a Virtual Channel VLAN Forwarding Table.........................................................................................566
A.9.1.5 Setting Parameters for Switching Upon Multiple Failures..................................................................................567
A.9.1.6 Performing an External ERPS Switchover.......................................................................................................... 568
A.9.1.7 Querying the Status of the Ethernet Ring Protocol............................................................................................. 569
A.9.2 Managing the LAG................................................................................................................................................. 569
A.9.2.1 Creating a LAG....................................................................................................................................................570
A.9.2.2 Setting LAG Parameters...................................................................................................................................... 572
A.9.2.3 Querying the Protocol Information of the LAG.................................................................................................. 573
A.9.3 Configuring Ethernet Services................................................................................................................................574
A.9.3.1 Configuring the QinQ Link................................................................................................................................. 574
A.9.3.2 Configuring the Forwarding Mode for Ethernet Services................................................................................... 575
A.9.3.3 Configuring UNI-UNI E-Line Services (U2000)................................................................................................ 576
A.9.3.4 Configuring UNI-UNI E-Line Services(Web LCT)............................................................................................ 577
A.9.3.5 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(U2000)........................................................ 579
A.9.3.6 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)................................................... 580
A.9.3.7 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(U2000)........................................................ 581
A.9.3.8 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)................................................... 582
A.9.3.9 Configuring UNI-NNI E-Line Services (Carried by PWs)(U2000)....................................................................585
A.9.3.10 Configuring UNI-NNI E-Line Services (Carried by PWs)(Web LCT)............................................................. 587
A.9.3.11 Creating E-AGGR Services............................................................................................................................... 589
A.9.3.12 Creating a VLAN Forwarding Table for an E-Line Service..............................................................................591
A.9.3.13 Configuring TPID for a Request VLAN........................................................................................................... 592
A.9.3.14 Configuring IEEE 802.1d Bridge-Based E-LAN Services(U2000).................................................................. 592
A.9.3.15 Configuring IEEE 802.1d Bridge-Based E-LAN Services(Web LCT)............................................................. 594
A.9.3.16 Configuring IEEE 802.1q Bridge-Based E-LAN Services(U2000).................................................................. 595
A.9.3.17 Configuring IEEE 802.1q Bridge-Based E-LAN Services(Web LCT)............................................................. 596
A.9.3.18 Configuring IEEE 802.1ad Bridge-Based E-LAN Services(U2000)................................................................ 598
A.9.3.19 Configuring IEEE 802.1ad Bridge-Based E-LAN Services(Web LCT)........................................................... 600
A.9.3.20 Configuring PW-Carried E-LAN Services (U2000)..........................................................................................601
A.9.3.21 Configuring Global Attributes of VPLS Services............................................................................................. 604
A.9.3.22 Changing Logical Ports Connected to a VB......................................................................................................605
A.9.3.23 Deleting an E-Line Service................................................................................................................................606
A.9.3.24 Deleting E-LAN Services.................................................................................................................................. 606
A.9.4 Managing the MAC Address Table........................................................................................................................ 607
A.9.4.1 Creating a Static MAC Address Entry.................................................................................................................607
A.9.4.2 Creating a Blacklist Entry of MAC Addresses....................................................................................................608
A.9.4.3 Configuring the MAC Address Learning Parameters......................................................................................... 609
A.9.4.4 Querying or Deleting a Dynamic MAC Address................................................................................................ 609
A.9.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service........................................................610
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xvi

A.9.6 Managing the MSTP............................................................................................................................................... 611

A.9.6.1 Creating the MSTP Port Group............................................................................................................................611
A.9.6.2 Setting the Bridge Parameters of the MSTP........................................................................................................612
A.9.6.3 Setting the Parameters of the CIST..................................................................................................................... 613
A.9.6.4 Querying the CIST Running Information............................................................................................................614
A.9.6.5 Changing the Spanning Tree Protocol Used by the Port Group.......................................................................... 615
A.9.6.6 Enabling/Disabling the MSTP Protocol.............................................................................................................. 615
A.9.6.7 Modifying the Configuration Data of the MSTP Port Group..............................................................................616
A.9.7 Managing the IGMP Snooping............................................................................................................................... 617
A.9.7.1 Configuring the IGMP Snooping Protocol.......................................................................................................... 617
A.9.7.2 Querying the Port Information of the Routers..................................................................................................... 618
A.9.7.3 Querying the Information About the Multicast Groups...................................................................................... 619
A.9.7.4 Creating Static Router Ports................................................................................................................................ 619
A.9.7.5 Creating a Member of a Static Multicast Group..................................................................................................620
A.9.7.6 Adding a Quickly Deleted Port............................................................................................................................621
A.9.7.7 Calculating IGMP Packets...................................................................................................................................622
A.9.8 Managing the QoS.................................................................................................................................................. 622
A.9.8.1 Creating a DS Domain.........................................................................................................................................622
A.9.8.2 Modifying the Mapping Relationships for the DS Domain.................................................................................624
A.9.8.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types.................................................. 625
A.9.8.4 Enabling/Disabling DSCP Demapping at the Egress Port of a DiffServ Domain...............................................627
A.9.8.5 Enabling/Disabling Outbound Demapping at the Egress Port of a DiffServ Domain.........................................628
A.9.8.6 Creating a Port Policy.......................................................................................................................................... 629
A.9.8.7 Modifying the Port Policy................................................................................................................................... 630
A.9.8.8 Creating Traffic....................................................................................................................................................631
A.9.8.9 Creating a Port WRED Policy............................................................................................................................. 633
A.9.8.10 Creating a Service WRED Policy......................................................................................................................633
A.9.8.11 Creating a WRR Policy......................................................................................................................................634
A.9.8.12 Setting the Port That Uses the Port Policy.........................................................................................................636
A.9.8.13 Creating a V-UNI Egress Policy........................................................................................................................ 637
A.9.8.14 Creating a V-UNI Group....................................................................................................................................638
A.9.8.15 Creating a PW Policy.........................................................................................................................................639
A.9.8.16 Creating a QinQ Policy......................................................................................................................................640
A.9.8.17 Applying policies for Ethernet services.............................................................................................................642
A.9.8.18 Configuring Port Shaping.................................................................................................................................. 642
A.9.8.19 Configuring Bandwidth Limitation for MPLS Tunnels.....................................................................................643
A.9.8.20 Configuring Bandwidth Limitation for PWs..................................................................................................... 644
A.9.8.21 Configuring Bandwidth Limitation for QinQ Links..........................................................................................645
A.9.9 Using the ethernet service OAM............................................................................................................................ 646
A.9.9.1 Creating an MD................................................................................................................................................... 646
A.9.9.2 Creating an MA................................................................................................................................................... 647
A.9.9.3 Creating MEPs.....................................................................................................................................................648
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xvii

A.9.9.4 Creating Remote MEPs in an MA....................................................................................................................... 649

A.9.9.5 Creating MIPs...................................................................................................................................................... 650
A.9.9.6 Performing a CC Test.......................................................................................................................................... 651
A.9.9.7 Performing an LB Test.........................................................................................................................................652
A.9.9.8 Performing an LT Test......................................................................................................................................... 653
A.9.9.9 Activating the AIS............................................................................................................................................... 654
A.9.9.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services............................................... 655
A.9.9.11 E-LAN Service Loopback Detection................................................................................................................. 656
A.9.9.12 Reactivating E-LAN Services............................................................................................................................657
A.9.9.13 Setting the Enabling Status of Automatic Service Loop Detection for NEs..................................................... 658
A.9.9.14 Configuring Bandwidth Notification................................................................................................................. 662
A.9.10 Using the ethernet port OAM............................................................................................................................... 663
A.9.10.1 Enabling the OAM Auto-Discovery Function...................................................................................................664
A.9.10.2 Enabling the Link Event Notification ...............................................................................................................665
A.9.10.3 Modifying the OAM Error Frame Monitoring Threshold ................................................................................ 665
A.9.10.4 Performing Remote Loopbacks......................................................................................................................... 666
A.9.10.5 Enabling Self-Loop Detection........................................................................................................................... 667
A.9.11 LPT Configuration................................................................................................................................................ 668
A.9.11.1 Configuring Point-to-Point LPT Traversing an L2 Network.............................................................................668
A.9.11.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network..............................................................669
A.9.11.3 Configuring Point-to-Multipoint LPT................................................................................................................669
A.9.11.4 Configuring Simple LPT....................................................................................................................................670
A.9.12 Configuring IP Packet Coloring and Statistics Collection................................................................................... 671
A.10 Configuring Ethernet Services and Features on the EoS/EoPDH Boards............................................................... 674
A.10.1 Managing ERPS....................................................................................................................................................674
A.10.1.1 Creating ERPS Instances................................................................................................................................... 674
A.10.1.2 Setting the Parameters of the ERPS Protocol.................................................................................................... 675
A.10.1.3 Querying the Status of the ERPS Protocol........................................................................................................ 676
A.10.2 Managing LAGs .................................................................................................................................................. 676
A.10.2.1 Creating a LAG..................................................................................................................................................676
A.10.2.2 Setting Parameters for LAGs.............................................................................................................................678
A.10.2.3 Querying the Protocol Information of LAGs.....................................................................................................678
A.10.3 Configuring Ethernet Services..............................................................................................................................679
A.10.3.1 Creating Ethernet Private Line Services............................................................................................................679
A.10.3.2 Creating Ethernet LAN Services....................................................................................................................... 681
A.10.3.3 Changing the Ports Connected to a VB............................................................................................................. 685
A.10.3.4 Creating the VLAN Filtering Table................................................................................................................... 685
A.10.3.5 Creating QinQ-Based EVPL Services............................................................................................................... 686
A.10.3.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services................................................................................688
A.10.3.7 Deleting an Ethernet Private Line Service.........................................................................................................691
A.10.3.8 Deleting an Ethernet LAN Service.................................................................................................................... 692
A.10.4 Managing the MAC Address Table...................................................................................................................... 693
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xviii

A.10.4.1 Creating a Static MAC Address Entry...............................................................................................................693

A.10.4.2 Creating a Blacklist Entry of a MAC Address.................................................................................................. 694
A.10.4.3 Setting the Aging Time of a MAC Address Table Entry ..................................................................................694
A.10.4.4 Querying or Deleting a Dynamic MAC Address.............................................................................................. 695
A.10.4.5 Querying the Actual Capacity of a MAC Address Table.................................................................................. 695
A.10.5 Configuring Ethernet Ports................................................................................................................................... 696
A.10.5.1 Configuring External Ethernet Ports................................................................................................................. 696
A.10.5.2 Configuring VCTRUNKs on an Ethernet Board...............................................................................................698
A.10.5.3 Modifying the Type Field of QinQ Frames....................................................................................................... 700
A.10.5.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth..................................................................... 700
A.10.6 Managing the Spanning Tree Protocol................................................................................................................. 702
A.10.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol........................................................ 702
A.10.6.2 Setting the Parameters of Spanning Tree Protocol............................................................................................ 702
A.10.6.3 Querying the Running Information About the Spanning Tree Protocol............................................................703
A.10.7 Managing the IGMP Snooping Protocol.............................................................................................................. 704
A.10.7.1 Configuring the IGMP Snooping Protocol........................................................................................................ 704
A.10.7.2 Configuring Static Multicast Entries................................................................................................................. 705
A.10.7.3 Modifying the Aging Time of a Multicast Table Entry..................................................................................... 706
A.10.7.4 Querying the Running Information of the IGMP Snooping Protocol............................................................... 707
A.10.8 Managing the QoS................................................................................................................................................ 707
A.10.8.1 Creating a Flow..................................................................................................................................................707
A.10.8.2 Creating the CAR.............................................................................................................................................. 708
A.10.8.3 Creating the CoS................................................................................................................................................709
A.10.8.4 Binding the CAR/CoS........................................................................................................................................711
A.10.8.5 Configuring Traffic Shaping for Egress Queues............................................................................................... 712
A.10.8.6 Configuring Port Shaping.................................................................................................................................. 712
A.10.8.7 Setting Egress Queue Scheduling Policies........................................................................................................ 713
A.10.9 Using the Ethernet service OAM..........................................................................................................................713
A.10.9.1 Creating MDs.....................................................................................................................................................714
A.10.9.2 Creating MAs.....................................................................................................................................................715
A.10.9.3 Creating MPs..................................................................................................................................................... 715
A.10.9.4 Performing a CC Test........................................................................................................................................ 717
A.10.9.5 Performing an LB Test.......................................................................................................................................718
A.10.9.6 Performing an LT Test....................................................................................................................................... 719
A.10.9.7 Activating the AIS............................................................................................................................................. 720
A.10.9.8 Performing a Ping Test ..................................................................................................................................... 720
A.10.9.9 Performing Performance Check........................................................................................................................ 721
A.10.10 Using the Ethernet port OAM.............................................................................................................................722
A.10.10.1 Enabling the OAM Auto-Discovery Function.................................................................................................722
A.10.10.2 Enabling the Link Event Notification..............................................................................................................723
A.10.10.3 Modifying the OAM Error Frame Monitoring Threshold............................................................................... 724
A.10.10.4 Performing the Remote Loopback...................................................................................................................725
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xix

A.10.11 Configuring LPT.................................................................................................................................................726

A.10.11.1 Configuring LPT for Point-to-Point Services.................................................................................................. 726
A.10.11.2 Configuring LPT for Point-to-Multipoint Services......................................................................................... 727
A.11 Managing MPLS/PWE3 Services and Features...................................................................................................... 728
A.11.1 Managing Address Resolution..............................................................................................................................728
A.11.1.1 Creating ARP Static Entries...............................................................................................................................729
A.11.1.2 Querying ARP Entries....................................................................................................................................... 729
A.11.1.3 Converting Dynamic ARP Entries to Static ARP Entries................................................................................. 730
A.11.1.4 Deleting Static ARP Entries...............................................................................................................................730
A.11.1.5 Setting ARP Aging Time................................................................................................................................... 731
A.11.2 Managing MPLS Tunnels..................................................................................................................................... 732
A.11.2.1 Setting Basic MPLS Attributes..........................................................................................................................732
A.11.2.2 Configuring Global OAM Parameters............................................................................................................... 733
A.11.2.3 Changing the MPLS Tunnel/PW OAM Standard..............................................................................................733
A.11.2.4 Creating a Unidirectional MPLS Tunnel........................................................................................................... 734
A.11.2.5 Creating a Bidirectional MPLS Tunnel............................................................................................................. 736
A.11.2.6 Querying MPLS Tunnel Information.................................................................................................................737
A.11.2.7 Changing MPLS Tunnel Information................................................................................................................ 738
A.11.2.8 Deleting MPLS Tunnels.....................................................................................................................................739
A.11.2.9 Setting MPLS OAM (Y.1711) Parameters.........................................................................................................740
A.11.2.10 Enabling/Disabling FDI................................................................................................................................... 740
A.11.2.11 Starting/Stopping CV/FFD Detection for MPLS Tunnels............................................................................... 741
A.11.2.12 Querying LSP Running Status......................................................................................................................... 742
A.11.2.13 Clearing OAM Configuration Data for MPLS Tunnel OAM (Y.1711)...........................................................743
A.11.2.14 Performing an LSP Ping Test...........................................................................................................................744
A.11.2.15 Performing an LSP Traceroute Test.................................................................................................................745
A.11.2.16 Configuring MEP Parameters for MPLS-TP Tunnel OAM............................................................................ 745
A.11.2.17 Creating MIPs of MPLS-TP Tunnel OAM......................................................................................................746
A.11.2.18 Starting a CC Test of MPLS-TP Tunnel OAM................................................................................................747
A.11.2.19 Starting an LB Test of MPLS-TP Tunnel OAM.............................................................................................. 748
A.11.2.20 Starting an LT Test Provided by MPLS-TP Tunnel OAM...............................................................................749
A.11.2.21 Testing the Delay and Delay Variation of an MPLS Tunnel............................................................................750
A.11.2.22 Setting the LCK Status of MPLS-TP Tunnel OAM........................................................................................ 751
A.11.2.23 Starting a TST Test Provided by MPLS-TP Tunnel OAM.............................................................................. 752
A.11.3 Managing MPLS APS Protection Groups............................................................................................................ 753
A.11.3.1 Creating an MPLS APS Protection Group.........................................................................................................753
A.11.3.2 Querying MPLS APS Status..............................................................................................................................755
A.11.3.3 Triggering MPLS APS Switching......................................................................................................................756
A.11.3.4 Enabling/Disabling MPLS APS Protection....................................................................................................... 757
A.11.4 Managing PWs......................................................................................................................................................758
A.11.4.1 Querying Information and Running Status of PWs........................................................................................... 758
A.11.4.2 Creating an MS-PW...........................................................................................................................................759
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xx

A.11.4.3 Setting PW OAM (Y.1711) Parameters............................................................................................................. 760

A.11.4.4 Performing a PW Ping Test................................................................................................................................761
A.11.4.5 Performing a PW Traceroute Test......................................................................................................................762
A.11.4.6 Configuring MEP Parameters for MPLS-TP PW OAM....................................................................................763
A.11.4.7 Creating MIPs of MPLS-TP PW OAM............................................................................................................. 764
A.11.4.8 Starting a CC Test of MPLS-TP PW OAM....................................................................................................... 765
A.11.4.9 Starting an LB Test of MPLS-TP PW OAM..................................................................................................... 765
A.11.4.10 Starting an LT Test Provided by MPLS-TP PW OAM....................................................................................767
A.11.4.11 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW...............................................................767
A.11.4.12 Setting the LCK Status of MPLS-TP PW OAM............................................................................................. 768
A.11.4.13 Starting a TST Test of MPLS-TP PW OAM................................................................................................... 769
A.11.5 Managing a PW APS/PW FPS Protection Group.................................................................................................770
A.11.5.1 Creating a PW APS Protection Group............................................................................................................... 771
A.11.5.2 Creating a PW FPS Protection Group................................................................................................................773
A.11.5.3 Configuring Slave Protection Pairs of PW APS................................................................................................ 775
A.11.5.4 Querying PW APS Status.................................................................................................................................. 777
A.11.5.5 Triggering PW APS Switching.......................................................................................................................... 777
A.11.5.6 Enabling/Disabling PW APS Protection............................................................................................................778
A.11.6 Managing CES Services....................................................................................................................................... 779
A.11.6.1 Creating CES Services.......................................................................................................................................779
A.11.6.2 Modifying CES Service Parameters.................................................................................................................. 782
A.11.6.3 Querying CES Service Information................................................................................................................... 782
A.11.6.4 Deleting a CES Service......................................................................................................................................783
A.11.6.5 Calculating the Maximum Number of CES Services That an MPLS Tunnel Can Transmit.............................784
A.11.7 Managing ATM/IMA Ports...................................................................................................................................785
A.11.7.1 Binding ATM TRUNKs.....................................................................................................................................785
A.11.7.2 Configuring an IMA group ............................................................................................................................... 787
A.11.7.3 Setting ATM Port Parameters............................................................................................................................ 787
A.11.7.4 Querying Running Status of an IMA Group......................................................................................................788
A.11.7.5 Querying Link Running Status of an IMA Group............................................................................................. 789
A.11.8 Managing ATM Services...................................................................................................................................... 790
A.11.8.1 Creating ATM Services......................................................................................................................................790
A.11.8.2 Modifying ATM Service Parameters................................................................................................................. 792
A.11.8.3 Querying ATM Services.................................................................................................................................... 793
A.11.8.4 Deleting an ATM Service...................................................................................................................................793
A.11.9 ATM Traffic Management.................................................................................................................................... 794
A.11.9.1 Creating an ATM-DiffServ Domain.................................................................................................................. 794
A.11.9.2 Modifying an ATM-Diffserv Domain................................................................................................................795
A.11.9.3 Creating an ATM Policy.................................................................................................................................... 797
A.11.9.4 Modifying an ATM Policy................................................................................................................................. 798
A.11.10 Using ATM OAM............................................................................................................................................... 799
A.11.10.1 Enabling/Disabling the AIS/RDI Insertion Status........................................................................................... 799
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxi

A.11.10.2 Setting Segment and End Attributes of AIS/RDI............................................................................................ 799

A.11.10.3 Performing a Continuity Check Test................................................................................................................800
A.11.10.4 Querying or Setting LLIDs.............................................................................................................................. 801
A.11.10.5 Performing an LB Test.....................................................................................................................................802
A.11.11 Managing MP Groups.........................................................................................................................................802
A.11.11.1 Creating MP Groups........................................................................................................................................ 802
A.11.11.2 Querying the MP Group Protocol Information................................................................................................ 804
A.12 Managing the Clock.................................................................................................................................................805
A.12.1 Managing Clocks at the Physical Layer............................................................................................................... 805
A.12.1.1 Setting the SDH Retiming Function.................................................................................................................. 805
A.12.1.2 Setting the E1 Clock Source for a Channelized STM-1 Interface Board.......................................................... 806
A.12.1.3 Configuring the Clock Sources..........................................................................................................................806
A.12.1.4 Configuring Clock Subnets................................................................................................................................808
A.12.1.5 User-Defined Clock Quality.............................................................................................................................. 808
A.12.1.6 Configuring a Clock Source Group................................................................................................................... 809
A.12.1.7 Configuring the SSM Output Status.................................................................................................................. 811
A.12.1.8 Configuring the Clock ID Output Status........................................................................................................... 811
A.12.1.9 Modifying the Parameters of the Clock Output.................................................................................................812
A.12.1.10 Configuring Clock Sources for External Clock Output...................................................................................813
A.12.1.11 Changing the Conditions for Clock Source Switching.................................................................................... 814
A.12.1.12 Modifying the Recovery Parameter of the Clock Source................................................................................ 815
A.12.1.13 Querying the Clock Synchronization Status....................................................................................................815
A.12.2 Managing CES ACR Clocks................................................................................................................................ 816
A.12.2.1 Configuring a CES Transmit Clock...................................................................................................................816
A.12.2.2 Configuring the Primary Clock for an ACR Clock Domain............................................................................. 818
A.12.2.3 Configuring Ports Using the Clock Domain......................................................................................................819
A.12.2.4 Querying the CES ACR Clock Status............................................................................................................... 821
A.12.3 Managing the PTP Clock......................................................................................................................................821
A.12.3.1 Configuring the PTP Profile.............................................................................................................................. 822
A.12.3.2 Changing the Mode for Selecting the Frequency Source.................................................................................. 822
A.12.3.3 Querying or Modifying the PTP System Time.................................................................................................. 823
A.12.3.4 Setting the PTP NE Attributes........................................................................................................................... 824
A.12.3.5 Creating PTP Clock Ports.................................................................................................................................. 824
A.12.3.6 Setting PTP Clock Port Attributes..................................................................................................................... 825
A.12.3.7 Setting Parameters for PTP Clock Packets........................................................................................................ 826
A.12.3.8 Configuring the Cable Transmission Offset Between NEs............................................................................... 827
A.12.3.9 Configuring a PTP Clock Subnet...................................................................................................................... 827
A.12.3.10 Modifying the BMC Algorithm Parameters for NE Clocks............................................................................ 828
A.12.3.11 Setting Basic Attributes of External Time Ports..............................................................................................829
A.12.3.12 Setting BMC Algorithm Parameters for External Time Ports......................................................................... 829
A.12.3.13 Setting the Cable Transmission Offset for External Time Ports......................................................................830
A.13 Ethernet Performance Query................................................................................................................................... 831
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxii

A.13.1 Browsing Current Ethernet Performance..............................................................................................................831

A.13.2 Configuring Ethernet Performance Threshold-Crossing Parameters................................................................... 836
A.13.3 Setting Parameters for Monitoring Historical Ethernet Performance...................................................................840
A.13.4 Browsing Historical Ethernet Performance Data..................................................................................................840
A.14 Configuring Auxiliary Ports and Functions.............................................................................................................845
A.14.1 Configuring Orderwire......................................................................................................................................... 845
A.14.2 Configuring the Synchronous Data Service......................................................................................................... 846
A.14.3 Configuring the Asynchronous Data Service....................................................................................................... 847
A.14.4 Configuring the Wayside E1 Service....................................................................................................................848
A.14.5 Configure External Alarms...................................................................................................................................848
A.14.6 Monitoring the Outdoor Cabinet.......................................................................................................................... 849
A.14.6.1 Configuring the Function for an Auxiliary Port................................................................................................ 849
A.14.6.2 Setting the Type of the Outdoor Cabinet........................................................................................................... 850
A.14.6.3 Querying and Setting the Temperature and Fan Information of the Outdoor Cabinet...................................... 851
A.14.6.4 Querying and Setting the Information About the Power System of the Outdoor Cabinet................................ 852
A.14.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet..................................................... 853
A.14.6.6 Setting Environment Alarm Parameters for Outdoor Cabinets......................................................................... 854
A.15 End-to-End Configuration Task Collection............................................................................................................. 855
A.15.1 Configuring a Protection Subnet.......................................................................................................................... 855
A.15.1.1 Searching for Protection Subnets.......................................................................................................................855
A.15.1.2 Creating a Linear MSP Protection Subnet.........................................................................................................856
A.15.1.3 Creating a Ring MSP Protection Subnet........................................................................................................... 856
A.15.1.4 Managing Protection Subnets............................................................................................................................ 857
A.15.2 Configuring TDM Services in E2E Mode............................................................................................................ 858
A.15.2.1 Searching for SDH Trails...................................................................................................................................858
A.15.2.2 Creating Server Trails........................................................................................................................................ 859
A.15.2.3 Creating Point-to-Point Service Trails...............................................................................................................860
A.15.2.4 Creating SNCP Service Trails........................................................................................................................... 862
A.15.2.5 Copying Service Trails...................................................................................................................................... 863
A.15.2.6 Managing SDH Trails........................................................................................................................................ 864
A.15.2.7 Managing Discrete TDM Services.................................................................................................................... 865
A.15.3 Configuring Native Ethernet Services (in an End-to-End Mode).........................................................................866
A.15.3.1 Searching for Native Ethernet Services............................................................................................................. 866
A.15.3.2 Creating E-Line Services over Native Ethernet.................................................................................................868
A.15.3.3 Creating an ERP Ring........................................................................................................................................871
A.15.3.4 Creating E-LAN Services over Native Ethernet................................................................................................873
A.15.3.5 Verifying Native Ethernet Services................................................................................................................... 877
A.15.3.6 Managing Native Ethernet Services.................................................................................................................. 880
A.15.3.7 Testing the Packet Loss Rate, Delay, or Delay Jitter of a Native Ethernet Service...........................................881
A.15.3.8 Managing Discrete Services Transmitted in Native Ethernet Mode................................................................. 882
A.15.3.9 Adjusting an E-LAN Service Network..............................................................................................................882
A.15.4 Searching for MPLS Tunnels and PWE3 Services...............................................................................................886
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxiii

A.15.5 Configuring MPLS Tunnels in an End-to-End Mode...........................................................................................887

A.15.5.1 Configuring Port IP Address Resources............................................................................................................ 888
A.15.5.2 Creating L2 Links.............................................................................................................................................. 888
A.15.5.3 Creating Non-Protection MPLS Tunnels (in an End-to-End Mode)................................................................. 889
A.15.5.4 Creating MPLS Tunnels Configured with MPLS APS Protection in an End-to-End Mode............................. 895
A.15.5.5 Verifying MPLS Tunnels in an End-to-End Mode............................................................................................ 901
A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode........................................................................................... 903
A.15.5.7 Managing Discrete MPLS Tunnels....................................................................................................................903
A.15.5.8 Searching for MPLS APS Protection Groups....................................................................................................904
A.15.5.9 Managing MPLS APS Protection Groups in an End-to-End Mode.................................................................. 904
A.15.5.10 Testing the Delay and Delay Variation of an MPLS Tunnel........................................................................... 905
A.15.5.11 Starting a TST Test Provided by MPLS-TP Tunnel OAM.............................................................................. 906
A.15.6 Configuring PWE3 Services in an End-to-End Mode.......................................................................................... 907
A.15.6.1 Creating PWE3 Service Templates....................................................................................................................907
A.15.6.2 Configuring CES Services in an End-to-End Mode.......................................................................................... 908
A.15.6.3 Configuring an ATM Policy Profile...................................................................................................................911
A.15.6.4 Configuring an ATM CoS Mapping Profile...................................................................................................... 912
A.15.6.5 Configuring ATM Services in an End-to-End Mode......................................................................................... 914
A.15.6.6 Configuring PW-Based E-Line Services (in an End-to-End Mode)..................................................................916
A.15.6.7 Hybird Configuration of E-Line and E-LAN services based on PWE3............................................................ 919
A.15.6.8 Verifying PW Configurations in an End-to-End Mode..................................................................................... 922
A.15.6.9 Verifying ATM Services in an End-to-End Mode............................................................................................. 924
A.15.6.10 Verifying PW-Based Ethernet Service Configurations (in an End-to-End Mode).......................................... 925
A.15.6.11 Managing and Maintaining PWE3 Services.................................................................................................... 928
A.15.6.12 Managing Discrete PWE3 Services.................................................................................................................928
A.15.6.13 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW.............................................................. 929
A.15.6.14 Starting a TST Test of MPLS-TP PW OAM................................................................................................... 930
A.15.7 Managing Ethernet Services Based on the Service Path View.............................................................................931
A.15.7.1 Searching for Service Paths Based on VLANs..................................................................................................931
A.15.7.2 Searching for Service Paths Based on MAC Addresses....................................................................................933
A.15.7.3 Checking the Layer 2 Protocols Used by Ethernet Services............................................................................. 934
A.15.7.4 Performing Intelligent Service Fault Diagnosis for Ethernet Services..............................................................935
A.15.7.5 Performing E-LAN Service Loopback Detection..............................................................................................937
A.15.7.6 Monitoring Ethernet Service Performance and Traffic Volume Based on Service Paths..................................938
A.15.8 Querying the Clock Tracing Relationship............................................................................................................ 940
B Parameters Description............................................................................................................943
B.1 Parameters for Network Management....................................................................................................................... 943
B.1.1 Parameters for NE Management............................................................................................................................. 944
B.1.1.1 Parameter Description: NE Searching (U2000)...................................................................................................944
B.1.1.2 Parameter Description: NE Searching (Web LCT)..............................................................................................948
B.1.1.3 Parameter Description: NE Creation (U2000)..................................................................................................... 949
B.1.1.4 Parameter Description: NE Creation (Web LCT)................................................................................................ 953
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxiv

B.1.1.5 Parameter Description: Login to an NE (Web LCT)........................................................................................... 954

B.1.1.6 Parameter Description:Changing NE IDs............................................................................................................ 955
B.1.1.7 Parameter Description: NE Time Synchronization (U2000)............................................................................... 956
B.1.1.8 Parameter Description: NE Time Synchronization (Web LCT).......................................................................... 959
B.1.1.9 Parameter Description: Localization Management of the NE Time....................................................................964
B.1.1.10 Parameter Description: Standard NTP Key Management................................................................................. 965
B.1.1.11 Parameter Description: License Management................................................................................................... 967
B.1.1.12 Parameter Description: Automatic Disabling of the Functions of NEs............................................................. 968
B.1.2 Parameters for Communications Management....................................................................................................... 969
B.1.2.1 Parameter Description: NE Communication Parameter Setting.......................................................................... 969
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration................................................................970
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management............................... 972
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC..........................................................974
B.1.2.5 Parameter Description: NE ECC Link Management........................................................................................... 976
B.1.2.6 Parameter Description: ECC Link Management_Availability Test..................................................................... 977
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management................................................978
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route Management Creation................................. 979
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test......................................................... 980
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings......................................... 981
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP..................................................................................... 987
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas.........................................................................987
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas......................................988
B.1.2.14 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be Manually Aggregated. 990
B.1.2.15 Parameter Description: Port OSPF Setting........................................................................................................ 990
B.1.2.16 Parameter Description: Static Route Entries in a Kernel Route Table_Creation...............................................991
B.1.2.17 Parameter Description: DCN Management_Bandwidth Management..............................................................991
B.1.2.18 Parameter Description: DCN Management_Port Setting.................................................................................. 993
B.1.2.19 Parameter Description: DCN Management_Access Control.............................................................................995
B.1.2.20 Parameter Description: DCN Management_Packet Control............................................................................. 996
B.1.2.21 Parameter Description: L2 DCN Management..................................................................................................996
B.1.2.22 Parameter Description: Access Control............................................................................................................. 997
B.1.2.23 Parameter Description: SNMP Communication................................................................................................ 999
B.1.2.24 Parameter Description: LLDP..........................................................................................................................1001
B.1.3 Parameters for Network Security Management.................................................................................................... 1002
B.1.3.1 Parameter Description: RADIUS Configuration_Creation............................................................................... 1002
B.1.3.2 Parameter Description: RADIUS Configuration_RADIUS Server................................................................... 1004
B.1.3.3 Parameter Description: Enabling/Disabling the RADIUS Function................................................................. 1005
B.2 Radio Link Parameters.............................................................................................................................................1006
B.2.1 Parameter Description: N+1 Protection_Create....................................................................................................1006
B.2.2 Parameter Description: N+1 Protection................................................................................................................ 1008
B.2.3 Parameter Description: IF 1+1 Protection_Create................................................................................................ 1010
B.2.4 Parameter Description: IF 1+1 Protection............................................................................................................ 1014
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxv

B.2.5 Parameter Description: Link Configuration_Creating a PLA/EPLA/EPLA+/Super EPLA Group..................... 1018

B.2.6 Parameter Description: Link Configuration_PLA/EPLA/EPLA+/Super EPLA.................................................. 1022
B.2.7 Parameter Description: Radio Link Management.................................................................................................1026
B.3 Multiplex Section Protection Parameters.................................................................................................................1032
B.3.1 Parameter Description: Linear MSP_Creation..................................................................................................... 1032
B.3.2 Parameter Description: Linear MSP..................................................................................................................... 1035
B.3.3 Parameter Description: Packet-based Linear MSP_Creation............................................................................... 1038
B.3.4 Parameter Description: Packet-based Linear MSP............................................................................................... 1040
B.3.5 Parameter Description: Ring MSP_Creation........................................................................................................ 1043
B.3.6 Parameter Description: Ring MSP........................................................................................................................1045
B.4 TDM Service Parameters......................................................................................................................................... 1046
B.4.1 Parameter Description: SDH/PDH Service Configuration_Creation................................................................... 1047
B.4.2 Parameter Description: SDH/PDH Service Configuration_SNCP Service Creation........................................... 1049
B.4.3 Parameter Description: SDH/PDH Service Configuration_Converting Normal Services Into SNCP Services.. 1053
B.4.4 Parameter Description: SDH/PDH Service Configuration................................................................................... 1056
B.4.5 Parameter Description: SNCP Service Control.................................................................................................... 1058
B.4.6 Parameter Description: TU_AIS Insertion............................................................................................................1062
B.5 Parameters for Board Interfaces...............................................................................................................................1064
B.5.1 Parameter Description: Working Modes of Ports................................................................................................. 1064
B.5.2 PDH Port Parameters............................................................................................................................................ 1064
B.5.2.1 Parameter Description: PDH Ports_Basic Attributes........................................................................................ 1064
B.5.2.2 Parameter Description: PDH Ports_Advanced Attributes................................................................................. 1066
B.5.3 Parameters for the Ports on Ethernet Boards........................................................................................................ 1069
B.5.3.1 Parameter Description: Ethernet Interface_Basic Attributes............................................................................. 1070
B.5.3.2 Parameter Description: Ethernet Interface_Flow Control................................................................................. 1074
B.5.3.3 Parameter Description: Ethernet Interface_Layer 2 Attributes..........................................................................1076
B.5.3.4 Parameter Description: Ethernet Port_Layer 3 Attributes................................................................................. 1078
B.5.3.5 Parameter Description: Ethernet Interface_Advanced Attributes......................................................................1079
B.5.4 Serial Port Parameters...........................................................................................................................................1085
B.5.4.1 Parameter Description: Serial Port_Basic Attributes.........................................................................................1085
B.5.4.2 Parameter Description: Serial Port_Creation of Serial Ports............................................................................. 1087
B.5.5 Channelized STM-1 Port Parameters....................................................................................................................1088
B.5.5.1 Parameter Description: Clock Transparent Transmission..................................................................................1088
B.5.5.2 Parameter Description: Path Configuration....................................................................................................... 1089
B.5.6 Microwave Interface Parameters.......................................................................................................................... 1092
B.5.6.1 Parameter Description: Microwave Interface_Basic Attributes........................................................................ 1092
B.5.6.2 Parameter Description: Microwave Interface_Layer 2 Attributes.....................................................................1094
B.5.6.3 Parameter Description: Microwave Interface_Layer 3 Attributes.....................................................................1096
B.5.6.4 Parameter Description: Microwave Interface_Advanced Attributes................................................................. 1097
B.5.7 IF Board Parameters............................................................................................................................................. 1099
B.5.7.1 Parameter Description: IF Interface_IF Attribute..............................................................................................1099
B.5.7.2 Parameter Description: IF Interface_ATPC Attribute........................................................................................1106
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxvi

B.5.7.3 Parameter Description: IF Port_Advanced Attributes....................................................................................... 1107

B.5.7.4 Parameter Description: ATPC Adjustment Records.......................................................................................... 1108
B.5.8 RFU/ODU Parameters.......................................................................................................................................... 1109
B.5.8.1 Parameter Description: RFU/RFU-SD/ODU Interface_Radio Frequency Attribute.........................................1109
B.5.8.2 Parameter Description: RFU/RFU-SD/ODU Interface_Power Attributes.........................................................1112
B.5.8.3 Parameter Description: RFU/RFU-SD/ODU Interface_Equipment Information.............................................. 1116
B.5.8.4 Parameter Description: ODU Interface_Advanced Attributes...........................................................................1118
B.5.9 Parameters for SDH Interface Boards................................................................................................................... 1119
B.5.9.1 Parameter Description: SDH Interfaces............................................................................................................. 1119
B.5.9.2 Parameter Description: Automatic Laser Shutdown..........................................................................................1121
B.5.10 Parameters for PDH Interface Boards.................................................................................................................1121
B.5.10.1 Parameter Description: PDH Ports...................................................................................................................1121
B.5.11 Parameters for Overhead..................................................................................................................................... 1125
B.5.11.1 Parameter Description: Regenerator Section Overhead...................................................................................1125
B.5.11.2 Parameter Description: VC-4 POHs................................................................................................................ 1126
B.5.11.3 Parameter Description: VC-12 POHs.............................................................................................................. 1128
B.5.12 Parameter Description: Ethernet Virtual Interfaces............................................................................................ 1129
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane.........................................................1133
B.6.1 Parameters for Ethernet Services.......................................................................................................................... 1133
B.6.1.1 Parameter Description: E-Line Service_Creation (U2000)............................................................................... 1133
B.6.1.2 Parameter Description: E-Line Service_Creation(Web LCT)........................................................................... 1154
B.6.1.3 Parameter Description: E-Line Service..............................................................................................................1178
B.6.1.4 Parameter Description: VLAN Forwarding Table Items for E-Line Services_Creation................................... 1189
B.6.1.5 Parameter Description: E-LAN Service_Creation (U2000).............................................................................. 1190
B.6.1.6 Parameter Description: E-LAN Service_Creation(Web LCT).......................................................................... 1200
B.6.1.7 Parameter Description: E-LAN Service(U2000)............................................................................................... 1211
B.6.1.8 Parameter Description: E-LAN Service(Web LCT).......................................................................................... 1225
B.6.1.9 Parameter Description: QinQ Link_Creation.................................................................................................... 1239
B.6.1.10 Parameter Description: E-AGGR Services_Creation...................................................................................... 1240
B.6.1.11 Parameter Description: E-AGGR Services...................................................................................................... 1247
B.6.2 Parameters for Ethernet Protocols........................................................................................................................ 1253
B.6.2.1 Parameter Description: ERPS Management_Creation...................................................................................... 1253
B.6.2.2 Parameter Description: ERPS Management...................................................................................................... 1256
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation................................................................. 1269
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration........................................................ 1270
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters................................................................... 1271
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters...................................................................... 1276
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST..................................... 1278
B.6.2.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration.............................................1286
B.6.2.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted......................... 1290
B.6.2.10 Parameter Description: IGMP Snooping Configuration_Route Management................................................ 1291
B.6.2.11 Parameter Description: IGMP Snooping Configuration_Static Router Port Creation.....................................1292
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxvii

B.6.2.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management.......................... 1293
B.6.2.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation.............. 1294
B.6.2.14 Parameter Description: IGMP Snooping Configuration_Data Count............................................................. 1295
B.6.2.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation..........................................1297
B.6.2.16 Parameter Description: Ethernet Link Aggregation_Link Aggregation.......................................................... 1304
B.6.2.17 Parameter Description: LPT Management_Creating Simple LPT.................................................................. 1305
B.6.2.18 Parameter Description: LPT Management_Point-to-Point LPT......................................................................1306
B.6.2.19 Parameter Description: LPT Management_Creating Point-to-Point LPT....................................................... 1308
B.6.2.20 Parameter Description: LPT Management_Point-to-Multipoint LPT............................................................. 1309
B.6.2.21 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT.............................................. 1312
B.6.3 Parameters for the Ethernet OAM........................................................................................................................ 1316
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation........................1316
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation..................1317
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation..................................................1318
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation.................................... 1319
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation................................................... 1320
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling.................................................... 1321
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling.....................................................1322
B.6.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback Detection..................................1324
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter....................................................1325
B.6.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring........................... 1328
B.6.3.11 Parameter Description: Ethernet OAM Management_Configuring Bandwidth Notification..........................1329
B.6.4 QoS Parameters.....................................................................................................................................................1330
B.6.4.1 Parameter Description: DiffServ Domain Management.................................................................................... 1330
B.6.4.2 Parameter Description: DiffServ Domain Management_Create....................................................................... 1336
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification............................................................. 1342
B.6.4.4 Parameter Description: Policy Management..................................................................................................... 1343
B.6.4.5 Parameter Description: Port Policy....................................................................................................................1347
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration........................................................ 1355
B.6.4.7 Parameter Description: Port Shaping Management_Creation........................................................................... 1365
B.6.4.8 Parameter Description: Port WRED Policy_Create.......................................................................................... 1366
B.6.4.9 Parameter Description: Service WRED Policy_Create..................................................................................... 1367
B.6.4.10 Parameter Description: WRR Scheduling Policy_Create................................................................................1368
B.6.4.11 Parameter Description: V-UNI Egress Policy..................................................................................................1369
B.6.4.12 Parameter Description: PW Policy.................................................................................................................. 1377
B.6.4.13 Parameter Description: QinQ Policy............................................................................................................... 1385
B.6.5 Parameter Description: IP Packet Marking and Statistics Collection...................................................................1393
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane............................................... 1398
B.7.1 Parameters for Ethernet Services.......................................................................................................................... 1398
B.7.1.1 Parameter Description: Ethernet Line Service_Creation................................................................................... 1398
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services.........................1402
B.7.1.3 Parameter Description: Ethernet Line Service...................................................................................................1413
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxviii

B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE 802.1d/
802.1q Bridge................................................................................................................................................................. 1416
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN Service
........................................................................................................................................................................................ 1419
B.7.1.6 Parameter Description: Ethernet LAN Service..................................................................................................1424
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation.................................................................................. 1431
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries................................................................1432
B.7.2 Parameters for Ethernet Protocols........................................................................................................................ 1432
B.7.2.1 Parameter Description: ERPS Management_Creation...................................................................................... 1432
B.7.2.2 Parameter Description: ERPS Management...................................................................................................... 1435
B.7.2.3 Parameter Description: Spanning Tree_Protocol Enabling............................................................................... 1444
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters...............................................................................1445
B.7.2.5 Parameter Description: Spanning Tree_Port Parameters...................................................................................1446
B.7.2.6 Parameter Description: Spanning Tree_Bridge Running Information...............................................................1448
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information...................................................................1449
B.7.2.8 Parameter Description: Spanning Tree_Point-to-Point Attribute...................................................................... 1450
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling............................................................................ 1451
B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries...................... 1452
B.7.2.11 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries........................... 1453
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs..........................................................1454
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation.......................................................... 1456
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT......................................1457
B.7.2.15 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT............................. 1459
B.7.2.16 Parameter Description: Port Mirroring_Creation............................................................................................ 1460
B.7.3 Parameters for the Ethernet OAM........................................................................................................................ 1461
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs....................................................................1461
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs....................................................................1462
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs.................................................................... 1462
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB.......................................................................... 1465
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT...........................................................................1466
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter..........................................................................1467
B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring...................................................1468
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter............................................................ 1469
B.7.4 QoS Parameters.....................................................................................................................................................1470
B.7.4.1 Parameter Description: QoS Management_Creation of Flows..........................................................................1470
B.7.4.2 Parameter Description: QoS Management_Creation of CAR........................................................................... 1472
B.7.4.3 Parameter Description: QoS Management_Creation of CoS.............................................................................1474
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS................................................................... 1476
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues.......................................1477
B.7.4.6 Parameter Description: QoS Management_Port Shaping..................................................................................1479
B.7.5 Parameters for the Ports on Ethernet Boards........................................................................................................ 1480
B.7.5.1 Parameter Description: Ethernet Port_External Port......................................................................................... 1480
B.7.5.2 Parameter Description: Ethernet Port_Internal Port.......................................................................................... 1487
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxix

B.7.5.3 Parameter Description: Type Field of QinQ Frames......................................................................................... 1493

B.8 Parameters for MPLS/PWE3 Services.....................................................................................................................1494
B.8.1 MPLS Tunnel Parameters..................................................................................................................................... 1494
B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels...................................................................... 1494
B.8.1.2 Parameter Description: MPLS Basic Configuration_Global OAM Parameters................................................1496
B.8.1.3 Parameter Description: Unicast Tunnel Management_Static Tunnel................................................................ 1497
B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels............................. 1502
B.8.1.5 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels................................1507
B.8.1.6 Parameter Description: Unicast Tunnel Management_OAM Parameters......................................................... 1512
B.8.1.7 Parameter Description: Unicast Tunnel Management_FDI...............................................................................1518
B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Ping...................................................................... 1518
B.8.1.9 Parameter Description: Unicast Tunnel Management_LSP Traceroute............................................................ 1521
B.8.1.10 Parameter Description: Unicast Tunnel Management_MEP Management..................................................... 1524
B.8.1.11 Parameter Description: Unicast Tunnel Management_Creating Tunnel MIPs................................................1529
B.8.1.12 Parameter Description: Unicast Tunnel Management_Enabling an LB Test.................................................. 1530
B.8.1.13 Parameter Description: PW Management_PW Management..........................................................................1532
B.8.1.14 Parameter Description: PW Management_MS-PW Creation..........................................................................1538
B.8.1.15 Parameter Description: PW Management_PW OAM..................................................................................... 1549
B.8.1.16 Parameter Description: PW Management_PW Ping....................................................................................... 1554
B.8.1.17 Parameter Description: PW Management_PW Traceroute..............................................................................1557
B.8.1.18 Parameter Description: PW Management_MEP Management........................................................................1559
B.8.1.19 Parameter Description: PW Management_Creating MIPs.............................................................................. 1563
B.8.1.20 Parameter Description: PW Management_Enabling an LB............................................................................ 1564
B.8.1.21 Parameter Description: MPLS APS Protection Management......................................................................... 1566
B.8.1.22 Parameter Description: Tunnel Protection Group_Creation............................................................................ 1570
B.8.1.23 Parameter Description: PW APS Protection Group_Creation.........................................................................1575
B.8.1.24 Parameter Description: PW FPS Protection Group_Creation......................................................................... 1586
B.8.1.25 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation............................... 1594
B.8.2 Parameter Description: VPLS Management......................................................................................................... 1600
B.8.3 CES Parameters.................................................................................................................................................... 1601
B.8.3.1 Parameter Description: CES Service Management........................................................................................... 1601
B.8.3.2 Parameter Description: CES Service Management_Creation............................................................................1611
B.8.4 ATM Parameters................................................................................................................................................... 1628
B.8.4.1 Parameter Description: ATM IMA Management_IMA Group Management....................................................1628
B.8.4.2 Parameter Description: ATM IMA Management_Bound Path Configuration.................................................. 1632
B.8.4.3 Parameter Description: ATM IMA Management_IMA Group Status...............................................................1634
B.8.4.4 Parameter Description: ATM IMA Management_IMA Link Status................................................................. 1635
B.8.4.5 Parameter Description: ATM IMA Management_ATM Interface Management............................................... 1636
B.8.4.6 Parameter Description: Configuration of ATM Service Class Mapping Table................................................. 1638
B.8.4.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation..................................1639
B.8.4.8 Parameter Description: ATM Policy Management............................................................................................ 1641
B.8.4.9 Parameter Description: ATM Policy Management_Creation............................................................................ 1645
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxx

B.8.4.10 Parameter Description: ATM Service Management........................................................................................ 1650

B.8.4.11 Parameter Description: ATM Service Management_Creation.........................................................................1660
B.8.4.12 Parameter Description: ATM OAM Management_Segment and End Attributes............................................1672
B.8.4.13 Parameter Description: ATM OMA Management_CC Activation Status....................................................... 1676
B.8.4.14 Parameter Description: ATM OAM Management_Remote End Loopback Status......................................... 1680
B.8.4.15 Parameter Description: ATM OAM Management_LLID................................................................................1683
B.8.4.16 Parameter Description: ATM OAM_ATM Cell Insertion Status.....................................................................1684
B.8.5 MP Group Parameters...........................................................................................................................................1685
B.8.5.1 Parameter Description: MP Group Management_Creation............................................................................... 1685
B.8.5.2 Parameter Description: MP Group Management_Basic Attributes...................................................................1688
B.9 Clock Parameters..................................................................................................................................................... 1692
B.9.1 Parameter Description: Frequency Selection Mode..............................................................................................1692
B.9.2 Physical Clock Parameters....................................................................................................................................1692
B.9.2.1 Parameter Description: Clock Source Priority Table.........................................................................................1692
B.9.2.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port.......................... 1696
B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet............................................................................ 1698
B.9.2.4 Parameter Description: Clock Subnet Setting_Clock Quality........................................................................... 1701
B.9.2.5 Parameter Description: Clock Subset Setting_SSM Output Control.................................................................1704
B.9.2.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status......................................................... 1705
B.9.2.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters.................................1706
B.9.2.8 Parameter Description: Clock Source Switching_Clock Source Switching......................................................1708
B.9.2.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions................................... 1709
B.9.2.10 Parameter Description: Output Phase-Locked Source of the External Clock Source..................................... 1711
B.9.2.11 Parameter Description: Clock Synchronization Status.................................................................................... 1713
B.9.3 CES ACR Clock Parameters.................................................................................................................................1716
B.9.3.1 Parameter Description: ACR Clock Source.......................................................................................................1716
B.9.3.2 Parameter Description: Clock Domain.............................................................................................................. 1716
B.9.3.3 Parameter Description: Clock Domain_Creation.............................................................................................. 1717
B.9.4 PTP Clock Parameters.......................................................................................................................................... 1718
B.9.4.1 Parameter Description: Clock Synchronization Attribute................................................................................. 1718
B.9.4.2 Parameter Description: Clock Synchronization Attribute_Creation of PTP Clock Ports..................................1731
B.9.4.3 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet............................................................. 1731
B.9.4.4 Parameter Description: Setting of a PTP Clock Subnet_BMC..........................................................................1732
B.9.4.5 Parameter Description: External Time Port_Basic Attributes........................................................................... 1733
B.9.4.6 Parameter Description: External Time Port_BMC............................................................................................ 1735
B.9.4.7 Parameter Description: External Time Port_Cable Transmission Distance...................................................... 1736
B.9.5 Parameter Description: Auxiliary Ports................................................................................................................ 1738
B.10 Parameters for the Orderwire and Auxiliary Interfaces......................................................................................... 1739
B.10.1 Parameter Description: Orderwire_General........................................................................................................1739
B.10.2 Parameter Description: Orderwire_Advanced.................................................................................................... 1741
B.10.3 Parameter Description: Orderwire_F1 Data Port................................................................................................1742
B.10.4 Parameter Description: Orderwire_Broadcast Data Port.................................................................................... 1742
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxxi

B.10.5 Parameter Description: Environment Monitoring Interface............................................................................... 1743
C Glossary.................................................................................................................................... 1747
Issue 02 (2017-12-25) Huawei Proprietary and Confidential xxxii

Feature Configuration Guide 1 Configuring Network Management Features
1 Configuring Network Management

Features
About This Chapter
This topic provides hyperlinks to configuration processes and configuration examples of

various network management features.
1.1 Configuration Procedure (HWECC Solution)

Configuring the HWECC solution includes configuring communication data at the near end
and creating NEs on the NMS.
1.2 Configuration Procedure (IP DCN Solution)
Configuring the IP DCN solution includes configuring communication data at the near end
1.3 Configuration Procedure (DCC Bytes Transparent Transmission Solution)
The configuration of the DCC bytes transparent transmission solution consists of two parts,
namely, the configuration of communication data at the near end and the creation of NEs on
the NMS.
1.4 Configuration Procedure (DCC Transmission Through the External Clock Port Solution)
To configure the solution of transparently transmitting DCCs through the external clock port,
you need to perform other configuration operations in addition to configuring the HWECC
solution.
1.5 Configuration Process (L2 DCN Solution)
Configuring the L2 DCN solution includes configuring communication data at the near end
and creating NEs on the NMS. The core configuration task is to set the DCN protocol used by
the DCC channels or inband DCN to L2 DCN.
1.6 Configuration Process (SNMP)
After the communication parameters are configured for an SNMP server, the SNMP server
can sets and query NE information based on the parameters and MIB files.
1.7 Configuration Procedure (LLDP)
When using the LLDP protocol, you must enable the LLDP function on the ports that connect
to adjacent equipment and set related parameters.
1.8 Configuration Procedure (RADIUS)
Issue 02 (2017-12-25) Huawei Proprietary and Confidential 1

This section describes the procedures for configuring related information on the RADIUS
server to use the RADIUS function.
1.9 Configuration Process (NE Anti-Theft Solution)
This section describes the process of configuring NE anti-theft. The process includes
generating a key pair and enabling NE anti-theft.
1.10 Configuration Example (HWECC Solution)
This section provides an example of how to plan and configure HWECC on a transmission
network that consists of OptiX radio transmission equipment and OptiX optical transmission
equipment.
1.11 Configuration Example (IP DCN Solution in Single OSPF Area)
This section provides an example of how to plan and configure the IP DCN solution in a
single OSPF area on a transmission network that consists of OptiX radio transmission
equipment and third-party radio transmission equipment.
1.12 Configuration Example (IP DCN Solution in Multiple OSPF Areas)
This section provides an example of how to plan and configure the IP DCN solution in
multiple OSPF areas on a transmission network that consists of OptiX radio transmission
1.13 Configuration Example (IP DCN Solution Using OSPF Multi-process)
This section provides an example of how to plan and configure the IP DCN solution using
OSPF multi-process on a transmission network that consists of OptiX radio transmission
equipment.
1.14 Configuration Example (DCC Bytes Transparent Transmission Solution)
This section provides an example of how to plan and configure the DCC bytes transparent
transmission solution on a transmission network that consists of OptiX radio transmission
equipment and third-party SDH equipment.
1.15 Configuration Example (DCC Transmission Through the External Clock Port Solution)
This section provides an example of how to plan and configure the DCC transmission through
the external clock port solution. The solution enables a DCN to traverse a third-party TDM
network.
1.16 Configuration Example (L2 DCN Solution, with Third-Party DCN Packets Not
Identified by VLAN IDs)
This section provides an example of how to plan and configure the L2 DCN solution. In this
solution, third-party DCN packets are not identified by VLAN IDs, so that Huawei DCN
packets and third-party DCN packets are forwarded by the system control unit of the RTN
equipment.
1.17 Configuration Example (L2 DCN Solution, with Third-Party DCN Packets Identified by
VLAN IDs)
solution, third-party DCN packets are identified by VLAN IDs, so that Huawei DCN packets
are forwarded by the system control unit of the RTN equipment whereas the third-party DCN
packets are transparently transmitted by the packet switching unit.
1.18 Configuration Example (SNMP)
This section provides an example of how to plan and configure NEs when a third-party
SNMP server is used to manage the network.
1.19 Configuration Example (LLDP)

This section provides an example of how to plan and configure the Link Layer Discovery
Protocol (LLDP) function on OptiX RTN 900 when LLDP is used between OptiX RTN 900
and a NodeB for topology discovery.
1.20 Configuration Example (RADIUS)
This section provides an example of how to plan and configure RADIUS for NEs when a
RADIUS server is used to implement centralized authentication of users who log in to the
NEs.
1.21 Configuration Example (NE Anti-Theft Solution)
This section provides an example of how to configure NE anti-theft.
1.1 Configuration Procedure (HWECC Solution)

Configuring the HWECC solution includes configuring communication data at the near end

Configuration Flowchart
Figure 1-1 Flowchart for configuring the HWECC solution
Required Start
Optional
Configure basic
attributes of NEs.
Configure DCC
channels.
Configure the inband

DCN.
Configure Extended
ECC Communication
Configure DCC byte

transparent
transmission.
Query ECC routes.
Configure Ethernet
network management
port for NEs.
Create NEs on the

centralized NMS.
End

Configuration Procedure
Table 1-1 Procedure for configuring the HWECC solution

Ste Operation Description
p
1 Setting A.3.1.9 Changing Required.

basic NE the NE ID
attributes
A.3.7.1 Setting NE Required.
IP Communication
Parameters
2 A.3.7.2 Configuring DCCs Required.
3 Configurin A.3.7.4 Perform this operation if the VLAN ID and

g the Configuring the bandwidth of the inband DCN planned for
inband VLAN ID and OptiX equipment do not take their default
DCN Bandwidth Used values. (The default VLAN ID is 4094 and the
by an Inband DCN default bandwidth is 512 kbit/s.)
NOTE
You can set the VLAN ID of the inband DCN based
on NEs or ports.
A.3.7.6 Required.
Configuring
Inband DCN Ports
A.3.7.7 Required when a gateway NE needs to

Configuring communicate with the NMS through an
Access Control Ethernet service port.
A.3.7.5 Required when priorities need to be specified

Configuring the for DCN packets.
Priority of Inband
DCN Packets
4 A.3.7.8 Configuring Extended Required for the NEs that are connected
ECC Communication through the Ethernet network management port
or NE cascading port.
5 A.3.7.3 Configuring DCC When the DCN route protection function is

Transparent Transmission affected due to the division of a DCN subnet,
this operation enables D1 to D3 bytes to be
transmitted over other DCN subnets and
therefore ensures proper functioning of the
DCN route protection.
6 A.3.7.18 Querying ECC Routes This operation applies only to a gateway NE.
NOTE
You can check the route status by testing route
connectivity, in addition to querying ECC routes.


p
7 A.3.8.1 Configuring Basic Required when an OptiX NE is connected to

Parameters for the NMS Port external equipment through its network
management port or NE cascading port and the
working mode of the external equipment is not
auto-negotiation.
8 Creating A.3.1.11 Enabling Required when an NE needs to be

NEs on the NE Automatic automatically created on the U2000 after it
centralized Reporting communicates with the U2000.
NMS
A.3.1.3 Creating It is recommended that you perform this
NEs by Using the operation to add one or more NEs to a large
Manual Method existing network on the centralized NMS.
(U2000) or A.3.1.2 NOTE
Creating NEs by If NE Automatic Reporting is enabled, an NE is
Using the Search automatically created on the U2000 after it
Method (Web communicates with the U2000.
LCT)
A.3.1.1 Creating It is recommended that you perform this

NEs by Using the operation to create NEs on the centralized
Search Method NMS in other cases.
(U2000) or A.3.1.4 NOTE
Creating NEs by If NE Automatic Reporting is enabled, an NE is
Using the Manual automatically created on the U2000 after it
Method (Web communicates with the U2000.
LCT)
1.2 Configuration Procedure (IP DCN Solution)

Configuring the IP DCN solution includes configuring communication data at the near end

Figure 1-2 Flowchart for configuring the IP DCN solution
Required Start
Optional
Configure basic
attributes of NEs.
Configure DCC
channels.
Configure the inband

DCN.
Configure IP routes.
Configure multiple
OSPF areas.
Querying IP Routes
Configure Ethernet
network management
ports for NEs.
Create NEs on the

centralized NMS.
End

Table 1-2 Procedure for configuring the IP DCN solution

p
1 Setting A.3.1.9 Changing the Required.

basic NE NE ID
attributes
A.3.7.1 Setting NE IP Required.
Communication
Parameters
2 A.3.7.2 Configuring DCCs Required.
3 Configuri A.3.7.4 Configuring Perform this operation if the VLAN ID and

ng the the VLAN ID and bandwidth of the inband DCN planned for
inband Bandwidth Used by an OptiX equipment do not take their default
DCN Inband DCN values. (The default VLAN ID is 4094 and
the default bandwidth is 512 kbit/s.)
NOTE
You can set the VLAN ID of the inband DCN
based on NEs or ports.
A.3.7.6 Configuring Required.

Inband DCN Ports NOTE
The ATN-compatible mode can be enabled by
port. In this mode, RTN equipment can
autonegotiate 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.
A.3.7.7 Configuring Required when a gateway NE needs to

Access Control communicate with the NMS through an
Ethernet service port.
A.3.7.5 Configuring Required when the priority needs to be

the Priority of Inband specified for DCN packets.
DCN Packets
4 Configuri A.3.7.11 Setting OSPF Required.

ng IP Protocol Parameters
routes
A.3.7.15 Configuring Optional.
the OSPF
Authentication Type
A.3.7.9 Creating a Optional.

Static IP Route


p
Enabling the proxy If the third-party NMS and the third-party

ARP equipment are on the same IP network
segment and the OptiX transmission network
provides an IP route between the third-party
NMS and the third-party equipment, enable
the proxy ARP on the OptiX NE connected
to the third-party NMS and the OptiX NE
connected to the third-party equipment.
5 Configuri Changing the network Required for an ABR.

ng multi- segment of the
area backbone area for an
OSPF ABR
A.3.7.12 Creating an When multi-area OSPF is deployed on a

OSPF Area network, create a non-backbone area to
which the ABR belongs.
Adding a network Required when the area to which an ABR

segment to which an belongs has multiple network segments.
ABR belongs
A.3.7.14 Creating a If automatic route aggregation is unavailable,

Manual Route configure manual route aggregation on the
Aggregation Group ABR to reduce the number of routes.
6 A.3.7.19 Querying IP Routes l The gateway NE has a route to the NMS.

l The gateway NE has routes to non-
gateway NEs and non-gateway NEs have
routes to the gateway NE.
l If the third-party equipment is connected
to the third-party NMS through an OptiX
NE, the OptiX NE has routes to the third-
party NMS and to the third-party
equipment.
NOTE
You can check the route status by testing route
connectivity, in addition to querying IP routes.
7 A.3.8.1 Configuring Basic Optional.

Parameters for the NMS Port Required when the OptiX RTN 950 is
connected to the external equipment through
its network management port or NE
cascading port and the working mode of the
external equipment is not auto-negotiation.
8 Creating A.3.1.11 Enabling NE Required when an NE needs to be

NEs on Automatic Reporting automatically created on the U2000 after it
the communicates with the U2000.
centralize
d NMS


p
A.3.1.3 Creating NEs It is recommended that you perform this

by Using the Manual operation to add one or more NEs to a large
Method (U2000) or A. existing network on the centralized NMS.
3.1.2 Creating NEs by NOTE
Using the Search If NE Automatic Reporting is enabled, an NE is
Method (Web LCT) automatically created on the U2000 after it
communicates with the U2000.

by Using the Search operation to create NEs on the centralized
Method (U2000) or A. NMS in other cases.
Using the Manual If NE Automatic Reporting is enabled, an NE is
1.3 Configuration Procedure (DCC Bytes Transparent

Transmission Solution)
The configuration of the DCC bytes transparent transmission solution consists of two parts,
namely, the configuration of communication data at the near end and the creation of NEs on
the NMS.
Table 1-3 Procedure for the DCC bytes transparent transmission solution
Step Operation Remarks
1 A.3.1.9 Changing the Required.

NE ID
2 A.3.7.1 Setting NE IP Required.

Communication
Parameters
3 A.3.7.2 Configuring Required when the third-party equipment uses

DCCs bytes D1 to D3 as DCCs.
4 A.3.7.3 Configuring When the OptiX NE needs to transparently

DCC Transparent transmit the DCC byte of the third-party
Transmission equipment, configure the DCC byte of the third-
party equipment to be transparently transmitted in
the planned route through this operation.
5 A.3.7.19 Querying IP Perform this operation only on the GNE. In normal

Routes cases:
l There is an ECC route between the GNE and
each of its managed non-GNEs.

6 Creating Enabling Required when an NE needs to be automatically

NEs on the NE created on the U2000 after it communicates with
the automatic the U2000.
centralize reporting
d NMS
A.3.1.3 It is recommended that you create NEs on the
Creating centralized NMS by using this method when you
NEs by need to add one or more NEs on a large-scale
Using the network.
Manual NOTE
Method If NE Automatic Reporting is enabled, an NE is
(U2000) automatically created on the U2000 after it
or A.3.1.2 communicates with the U2000.
Creating
NEs by
Using the
Search
Method
(Web
LCT)
A.3.1.1 In the other cases, this method is preferred.

Creating NOTE
NEs by If NE Automatic Reporting is enabled, an NE is
Using the automatically created on the U2000 after it
Search communicates with the U2000.
Method
(U2000)
or A.3.1.4
Creating
NEs by
Using the
Manual
Method
(Web
LCT)
1.4 Configuration Procedure (DCC Transmission Through

the External Clock Port Solution)
To configure the solution of transparently transmitting DCCs through the external clock port,
you need to perform other configuration operations in addition to configuring the HWECC
solution.

Table 1-4 Procedure for configuring the solution of transparently transmitting DCCs through
the external clock port
1 A.3.7.2 Configuring Required. Set parameters as follows:

DCCs NOTE
For OptiX RTN 950/980, the external clock port on the
system control, switching, and timing board in the slot
with a smaller slot number corresponds to External
Clock Source 1, and the external clock port on the
system control, switching, and timing board in the slot
with a larger slot number corresponds to External Clock
Source 2.
2 A.7.1 Creating the Required in indirect connection mode

Cross-Connections of Perform this operation to set up the point-to-point
Point-to-Point cross-connection between the E1 port connected to
Services the external clock port and the specific timeslot of
the port on the SDH line board. This port on the
SDH line board is used to interconnect with the
third-party equipment. The specific timeslot is
used to transparently transmit network
management messages.
NOTE
For OptiX RTN 905, the point-to-point cross-connection
between the 16th E1 to the specific timeslot on the SDH
line port needs to be created.
1.5 Configuration Process (L2 DCN Solution)

Configuring the L2 DCN solution includes configuring communication data at the near end
and creating NEs on the NMS. The core configuration task is to set the DCN protocol used by
the DCC channels or inband DCN to L2 DCN.
Depending on how third-party DCN packets are transmitted, the L2 DCN solution is available
in the following transmission schemes:
l DCN channel transmission: Without being identified by VLAN IDs, third-party DCN
packets are received at the NMS port of the RTN equipment, forwarded by the system
control unit, and transmitted over the DCN channel.

Figure 1-3 DCN channel transmission solution
3rd-party Msg
MAC 3rd-party Msg
NM-ETH OptiX Msg 3rd-party Msg
MAC
MAC MAC
NM-ETH
DCC DCC
Without VLAN
Third-party NMS NM
NM
LAN Switch
NM
OptiX Msg GE
OptiX NMS GE
MAC OptiX Msg
OptiX Msg
Inband DCN MAC
MAC OptiX Msg
Inband DCN
NM-ETH MAC
Inband DCN
OptiX equipment Third-party equipment
Ethernet link Radio link
l Service channel transmission: Identified by VLAN IDs, third-party DCN packets are
received at the NMS port of the RTN equipment, forwarded by the packet switching unit,
and transmitted over the service channel.
Figure 1-4 Service channel transmission solution
OptiX Msg 3rd-party Msg

3rd-party Msg
MAC MAC 3rd-party Msg
MAC
DCC channel Service channel MAC
NM-ETH
NM-ETH
With VLAN
Third-party NMS NM
NM
LAN Switch
NM
OptiX Msg GE
OptiX NMS GE
MAC OptiX Msg
OptiX Msg
Inband DCN MAC
MAC OptiX Msg
Inband DCN
NM-ETH MAC
Inband DCN
NOTE
The DCC channel and inband DCN channel of a microwave port cannot use the L2 DCN solution at the
same time. Disable the channel that is not in use.

Configuration Flowchart (L2 DCN Solution)

Figure 1-5 shows the flowchart for configuring the L2 DCN solution.
Figure 1-5 Configuration Flowchart (L2 DCN Solution)
Start Required
Optional
Change an NE ID.
Set NE communications
parameters.
Configure the Configure the

outband DCN. inband DCN.
Setting the VLAN ID for

Huawei NMS.
Disable the OSPF protocol
Create static IP routes.
Confirm the RSTP protocol status.
Configure Ethernet network

management port for NEs.
Creating NEs on the centralized

NMS
Setting the Tag-Attributions

for the Ethernet NMS Port
Configuring E-LAN services for

transparently transmitting
third-arty DCN packets
End

Procedure for Configuring the L2 DCN Solution
Table 1-5 Procedure for configuring the L2 DCN solution

p
1 A.3.1.9 Changing the NE ID Required. Set the parameters as follows:

l Set ID to be the NE ID according to the
DCN plan.
l If a special extended ID is required for
the NE according to the DCN plan,
change Extended ID.
2 A.3.7.1 Setting NE IP Required.

Communication Parameters l Set IP Address and Subnet Mask
according to the network plan.
l For NEs configured with no static IP
route on an L2 DCN subnet, set its
gateway IP address to the IP address of
the NE configured with a static IP route.
3 Using the A.3.7.2 Configuring Required.

outband DCCs l For DCC channels between L2 DCN
DCN subnets, set Enabled/Disabled to
Enabled and set Protocol Type to
TCP/IP.
l For DCC channels within an L2 DCN
subnet, set Enabled/Disabled to Enabled
and set Protocol Type to L2DCN.
Disabling inband DCN Required if the IF board uses DCC channels

channels of a as L2 DCN channels.
microwave port In the IF tab, set Enabled Status to
Disabled for IF ports whose DCC channels
are planned to be enabled.


p
4 Using the A.3.7.4 Configuring Required.

inband the VLAN ID and l If the default VLAN ID of the inband
DCN Bandwidth Used by an DCN conflicts with the VLAN ID used
Inband DCN by the service, you can manually modify
Ethernet Board VLAN ID of the inband
DCN. The same VLAN ID is used for
inband DCN communication over the
entire network.
l Bandwidth(kbit/s) specifies the
bandwidth for inband DCN messaging
over Ethernet ports. IF Port
Bandwidth(kbit/s) specifies the
bandwidth for inband DCN messaging on
a radio link. The default value is 512
kbit/s.

Inband DCN Ports l For IF ports that are planned to use the
inband DCN function, set Enabled
Status to Enabled.
l For the inband DCN channels between
L2 DCN subnets, set Protocol Type to
TCP/IP.
l For the inband DCN channels within an
L2 DCN subnet, set Protocol Type to
L2DCN.
Disabling DCC Required if the IF board uses inband DCN

channels channels as L2 DCN channels.
For IF ports that are planned to use inband
DCN channels, set Enabled/Disabled to
Disabled.
5 Setting the VLAN ID for Huawei If the DCN packets from Huawei NMS carry
NMS a VLAN ID when they are transmitted over
an NMS port, set NMS port VLAN ID for
the port according to the NMS requirements.
NOTE
OptiX RTN 950 housing a CSH board and OptiX
RTN 980 housing a CSHN board do not support
this function.
6 Disabling the OSPF protocol Optional.

If static IP routes are planned to be used
between L2 DCN subnets, it is recommended
that you disable the OSPF protocol.


p
7 A.3.7.9 Creating a Static IP Route Configure static IP routes if communication

between L2 DCN subnets needs to be
implemented based on L3 forwarding.
8 A.3.7.17 Enabling/Disabling the By default, the NE automatically enables/

RSTP Protocol When the L2 DCN disables the RSTP protocol according to the
Solution Is Used L2 DCN enabled/disabled status of the port.
You can perform this operation to manually
enable/disable the RSTP protocol.
9 A.3.8.1 Configuring Basic Required when an OptiX NE is connected to

Parameters for the NMS Port external equipment through its network
management port or NE cascading port and
the working mode of the external equipment
is not auto-negotiation.
10 Creating A.3.1.11 Enabling NE Required when an NE needs to be

NEs on Automatic Reporting automatically created on the U2000 after it
the communicates with the U2000.
centralize
d NMS A.3.1.3 Creating NEs It is recommended that you perform this
by Using the Manual operation to add one or more NEs to a large
Method (U2000) or A. existing network on the centralized NMS.
Using the Search If NE Automatic Reporting is enabled, an NE is

by Using the Search operation to create NEs on the centralized
Method (U2000) or A. NMS in other cases.
Using the Manual If NE Automatic Reporting is enabled, an NE is
11 A.3.8.3 Changing the If the third-party DCN packets are

Encapsulation Type and QinQ encapsulated using the S-Tag:
Type Domain for the Ethernet l Set Encapsulation Type to QinQ in
NMS Port Basic Attributes.
l Set QinQ Type Domain in Layer 2
Attributes as required. The default value
is 0x88A8.
NOTE
this function.


p
12 Configuring E-LAN services for Required. Third-party DCN packets can be

transparently transmitting third-arty transparently transmitted as E-LAN services
DCN packets on the packet switching plane.
l Configure E-LAN service ports based on
the plan of E-LAN services and the
networking of the third-party DCN. The
E-LAN service port type can be C-Aware
(IVL/SVL), S-Aware (IVL/SVL), or Tag-
Transparent (SVL).
l The third-party DCN packets must carry
VLAN IDs and be received through NMS
ports (logical ports: NMS-1).
l In this scenario, NMS ports can only
function as UNIs of E-LAN services.
NOTE
this function.
NOTE
To prevent loops in an L2 DCN and further prevent broadcast storms, the STP/RSTP protocol needs to
be enabled for a switch that is connected to the L2 DCN.
1.6 Configuration Process (SNMP)

After the communication parameters are configured for an SNMP server, the SNMP server
can sets and query NE information based on the parameters and MIB files.

Table 1-6 Configuration process of SNMP

Operation Remarks
A.3.7.24 Setting SNMP Required. Set parameters as follows:

Communications Parameters l Set NMS IP Address to
– the IP address of the SNMP server if the SNMP
server requires a special communicate name
and right.
– the default value 0.0.0.0 if all SNMP servers
share a community name and right.
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 Based on actual requirements, set Report MW
Performance Trap, Report IP Performance
Trap, and Report Alarm Trap to Report.
l It is recommended that Port take the default value.
l Set Traps Version to SNMPV3.
1.7 Configuration Procedure (LLDP)

When using the LLDP protocol, you must enable the LLDP function on the ports that connect
to adjacent equipment and set related parameters.
Table 1-7 Procedure for configuring LLDP

Operation Description
Configuring the LLDP function Required.

of Ethernet ports
A.4.6.1 Configuring the Optional.

Transmit Parameters for LLDP
Packets
NOTE
l When RTN equipment is interconnected with CX/ATN equipment and LLDP needs to be used, set
VLAN ID to 0.
l IF ports on the RTN 950 that houses CSHU/CSHUA boards and the RTN 950A that houses
SLF2CSHO boards support LLDP.

1.8 Configuration Procedure (RADIUS)

This section describes the procedures for configuring related information on the RADIUS
server to use the RADIUS function.
Figure 1-6 shows the flowchart for configuring RADIUS.
Figure 1-6 Flowchart for configuring RADIUS

Required
Start
Optional
Enable or disable RADIUS
for an NE.
Create a RADIUS server or

proxy server.
Configure RADIUS server

parameters.
End
NOTE
For an NE using the proxy NAS mode, configure the NE to be a RADIUS client and a proxy NAS.
Table 1-8 provides the configuration procedure when an NE uses the NAS mode or functions
as a proxy NAS.
Table 1-8 Procedure for configuring RADIUS (for a RADIUS client using the NAS mode or
a proxy NAS)
Step Operation Description
1 A.4.5.1 Enabling/ Required.

Disabling the RADIUS
Function
2 A.4.5.2 Creating a Required.

RADIUS Server or a NOTE
RADIUS Proxy Server If you need to collect data about usage of NEs by
users during authentication, enable Accounting
after enabling Authentication. This method
applies when you need to enable Accounting
after Authentication is enabled.
3 A.4.5.3 Configuring Required.

RADIUS Server
Parameters

4 Configuring a key for a Required when an NE functions as a proxy.

proxy NAS
Table 1-9 provides the configuration procedure when an NE uses the proxy NAS mode.
Table 1-9 Procedure for configuring RADIUS (for a RADIUS client using the proxy NAS
mode)
1 A.4.5.1 Enabling/Disabling Required.

the RADIUS Function NOTE
Disable the proxy server function for NEs that use
the proxy NAS mode.
2 A.4.5.2 Creating a RADIUS Required.

Server or a RADIUS Proxy NOTE
Server If you need to collect data about usage of NEs by
users during authentication, enable Accounting
after enabling Authentication. This method is
applicable when you need to enable Accounting
after Authentication is enabled.

RADIUS Server Parameters
1.9 Configuration Process (NE Anti-Theft Solution)

This section describes the process of configuring NE anti-theft. The process includes
generating a key pair and enabling NE anti-theft.
NOTE
The RTN 950 housing CST/CSH boards, the RTN 980 housing CSHN/CSHNA boards and the RTN 905
1A/2A/1C do not support NE anti-theft.

Table 1-10 Configuring NE anti-theft
1 A.3.1.16 Configuring NE Anti-Theft Required. Anti-theft

policies consist of
configuration
control and service
control policies.
l Configuration
control policies
take effect
immediately
when the device
becomes
unreachable to
the NMS. That
is, all
configuration
commands are
restricted.
l Service control
policies take
affect a specified
period (7 days,
by default) after
the device
becomes
unreachable to
the NMS. That
is, after the
specified period
arrives, services
are limited to 10
Mbit/s.
1.10 Configuration Example (HWECC Solution)

This section provides an example of how to plan and configure HWECC on a transmission
network that consists of OptiX radio transmission equipment and OptiX optical transmission
equipment.
1.10.1 Networking Diagram

This section describes the networking of NEs. OptiX radio transmission equipment and OptiX
optical transmission equipment must be in different ECC subnets.
Figure 1-7 shows the transmission network consisting of the OptiX optical transmission
equipment and the OptiX radio transmission equipment.

l On the network, both the number of OptiX optical transmission NEs and the number of
OptiX radio transmission NEs exceed half of the maximum number of NEs allowed by a
DCN subnet.
l The centralized NMS can manage all the OptiX equipment on the network.
Figure 1-7 Networking diagram of HWECC
NE205
NE203
NE204
NE202
NE201 NE103
NE101
NE102
NMS
NE104
NE105
OptiX optical transmission equipment
OptiX radio transmission equipment
Router LAN switch
Radio link Fiber Network cable
1.10.2 Configuration Procedure

This example provides the configurations only of the typical NEs, NE201, NE202, and
NE203.

Data Preparation
Figure 1-8 Data plan

9-205
129.9.0.205
9-203 0.0.0.0
129.9.0.203
0.0.0.0
9-204
129.9.0.204
11.0.0.1/16 9-202 0.0.0.0
11.0.0.202
11.0.0.1
9-201
129.9.0.201
0.0.0.0
10.0.0.1/16 9-103
9-101 129.9.0.103
10.0.0.101 0.0.0.0
0.0.0.0
10.0.0.100/16
9-102
129.9.0.102
9-104 9-105 0.0.0.0
129.9.0.104 129.9.0.105
0.0.0.0 0.0.0.0
Extended ID-Basic ID
IP address
Gateway
l Both the optical transmission equipment quantity and the radio transmission equipment
quantity exceed half of the maximum equipment quantity allowed on a DCN subnet.
Therefore, divide the ECC network into two DCN subnets by equipment type.
l Select the central node NE101 of the optical transmission service and the central node
NE202 of the radio transmission service as gateway NEs.
l The NMS and NE101 are located at the same place and NE202 is located at another
place. Therefore, you need to construct the external DCN between the NMS and NE202
through a router or protocol converter.
l Allocate IDs and IP addresses for all the NEs based on network conditions.
l Plan the extended ECC.
– There is no DCC between NE203 and NE204 or between NE203 and NE205.
Therefore, you need to use network cables to connect the Ethernet network
management ports and the NE cascading ports to extend the ECC. The extended
ECC function works in the automatic mode.
NOTE
If FE/GE services are configured between NE203, NE204, and NE205, communication between
the three NEs can also be implemented based on the inband DCN. To prevent interchange
between different protocols, the inband DCN uses the HWECC protocol.

l Divide the ECC network.

– Shut down the DCC channels of the east and west ports on NE201 so that the DCC
between two DCN subnets is disconnected.
– Set pass-through of the D1 to D3 bytes on NE201. In this manner, the ECC route
protection function is not affected.
Procedure
Step 1 Change the NE IDs.
The values for the related parameters are provided as follows.
Parameter Value
NE201 NE202 NE203
New ID 201 202 203
New Extended ID 9 9 9
3
1
Step 2 Set NE communication parameters.

Parameter Value
NE201 NE202 NE203
IP Address 129.9.0.201 11.0.0.202 129.9.0.203
Gateway IP 0.0.0.0 11.0.0.1 0.0.0.0

Address

Parameter Value
NE201 NE202 NE203
Subnet Mask 255.255.0.0 255.255.0.0 255.255.0.0
Step 3 Configure the DCC channels.

Parameter Value
East and West Other IF/Line All the IF/Line

Ports on the Ring Ports (NE201) Ports (NE202 and
(NE201) NE203)
Enabled/Disabled Disabled Enabled Enabled
Channel - D1 (default value of D1 (default value of

an IP port in PDH an IP port in PDH
radio mode whose radio mode whose
capacity is lower capacity is lower
than 16 E1s) than 16 E1s)
D1-D3 (default D1-D3 (default
values of other line values of other line
ports) ports)
Protocol Type - HWECC HWECC

Step 4 Disable the inband DCN function for all ports.

Disable the inband DCN function for all ports on NE201, NE202, and NE203. Set parameters
as follows.
Parameter Value
All Ports (NE201) All Ports (NE202) All Ports (NE203)
Enabled Status Disabled Disabled Disabled
Step 5 Enable the extended ECC function in Auto mode for NE203.
For NE203, select Auto mode from the drop-down list and click Apply.

Step 6 Configure DCC byte transparent transmission on NE201.

Parameter Value
Source Timeslot/ Related parameter Related parameter Related parameter

Port values of west ports values of west ports values of west ports
on the ring on the ring on the ring
Transparent D1 D2 D3
Transmission of
Overhead Bytes at
Source Port
Sink Timeslot/Port Related parameter Related parameter Related parameter

values of east ports values of east ports values of east ports
on the ring on the ring on the ring
Transparent D1 D2 D3
Transmission of
Overhead Bytes at
Sink Port

Step 7 Query ECC routes of NE101 and NE202.
In the NE Explorer, choose Function Tree > Communication > NE ECC Link
Management. The expected query results are as follows.
l The routes to all the OptiX optical transmission NEs can be queried on NE101 while the
routes to NE201 and NE202 cannot be queried.
l The routes to all the OptiX radio transmission NEs can be queried on NE202 while the
routes to NE101 and NE102 cannot be queried.
Step 8 See A.3.1.1 Creating NEs by Using the Search Method (U2000) and create NEs by
searching for the NEs on the centralized NMS.
Search for NEs by using 10.0.0.101 and 11.0.0.202 as IP Address of GNE.
NOTE
As the IP address of NE202 (11.0.0.202) and the IP address of the centralized NMS are not on the same
network segment, configure static routes on both the NMS and the related router to guarantee that the TCP/IP
communication between them is normal. Then, create NEs.
Normally, all NEs can be created on the centralized NMS.
----End
1.11 Configuration Example (IP DCN Solution in Single

OSPF Area)
This section provides an example of how to plan and configure the IP DCN solution in a
single OSPF area on a transmission network that consists of OptiX radio transmission

This section describes the networking of NEs. OptiX radio equipment and third-party
equipment do not exchange routing information using the OSPF protocol.

As shown in Figure 1-9, the OptiX radio transmission equipment and the third-party radio
transmission equipment construct a radio transmission network. On the radio transmission
network:
l The third-party radio equipment is located at the edge and the OptiX radio equipment is
located in the center.
l The third-party radio equipment does not support OSPF. Therefore, the OptiX radio
equipment needs to transparently transmit the network management messages between
the third-party radio equipment at the edge of the network and the third-party NMS in
the center of the network.
l Specifically, the IP address of the gateway NE of the third-party equipment is 130.9.0.7,
and the IP address of the third-party NMS is 11.0.0.100.
l The total number of NEs is smaller than the maximum number of NEs allowed by a
DCN subnet, so only a single OSPF area is used.
Figure 1-9 Networking diagram of IP DCN (in a single OSPF area)
NE7 NE8
IP:130.0.9.7 IP:130.0.9.8
Third-party
NMS
IP:11.0.0.100 NE6 NE4
NE5
IP:10.0.0.200
NE3
NMS NE1 NE2
Third-party equipment OptiX equipment
Router LAN switch
Radio link Ethernet link

This section describes the procedure for configuring the IP DCN solution in a single OSPF
area to import static routes of third-party equipment and the NMS to an OSPF area consisting
of OptiX radio transmission equipment.

Data Preparation
NE8
NE7
130.9.0.8/16
130.9.0.7/16
11.0.0.200/16 NE4
9-6 9-5 9-4
130.9.0.6 129.9.0.5 129.9.0.4
0.0.0.0 0.0.0.0 0.0.0.0
11.0.0.100/16 NE6 NE5
9-3
129.9.0.3
0.0.0.0
10.0.0.200/16 NE3
9-1 9-2
10.0.0.1 129.9.0.2
0.0.0.0 0.0.0.0
NE1 NE2
10.0.0.100/16
IP address
Gateway
ID and IP Address Information

Allocate IDs and IP addresses for all the NEs based on network conditions. Allocate the NE
IP addresses properly so that:
l The IP address of NE1 (connected to the external DCN) meets the requirements of the
external DCN.
l The IP addresses of the NEs that are connected through Ethernet network management
ports are on the same network segment.
Route Information
l Plan the following route information between the OptiX NEs:

– On NE1, configure a static route to the third-party NMS whose IP address is
11.0.0.100. The gateway uses the router interface IP address, 10.0.0.200.
– On NE1, enable the OSPF route flooding function for the static routes.
– On NE3 and NE4, enable the inband DCN function for Ethernet ports.
– On NE6, configure a static route to the third-party gateway NE NE7. Enable the
route flooding function for the static route.
l In addition, plan the following routes:
– On the gateway NE of the third-party equipment, configure a static route to the
third-party NMS whose IP address is 11.0.0.100. The gateway uses the IP address
of NE6, 130.9.0.6.
– On the third-party NMS, configure a static route to the gateway NE of the third-
party equipment whose IP address is 130.9.0.7. The gateway uses the IP address of

the router interface, 11.0.0.200. Alternatively, you can set the IP address 11.0.0.200
to be the default gateway of the third-party NMS.
– On the router, configure the routes according to the gateway NE of the third-party
equipment whose IP address is 130.9.0.7.
NOTE
In this configuration example, only the configuration information about the typical NEs, NE1, NE3, NE4, and
NE6 is provided.
Procedure
Parameter Value
NE1 NE3 NE4 NE6
New ID 1 3 4 6
New Extended 9 9 9 9
ID
3
1

Parameter Value
NE1 NE3 NE4 NE6
IP Address 10.0.0.1 129.9.0.3 129.9.0.4 130.9.0.6

Parameter Value
NE1 NE3 NE4 NE6
Gateway IP 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0

Address
Subnet Mask 255.255.0.0 255.255.0.0 255.255.0.0 255.255.0.0
Step 3 Configure the DCC channels.

Parameter Value
IF Port (NE1) IF Port (NE3) IF Port (NE4) IF Port (NE6)
Enabled/ Enabled Enabled Enabled Enabled

Disabled
Channel D1 (default D1 (default D1 (default D1 (default

value of an IP value of an IP value of an IP value of an IP
port in PDH port in PDH port in PDH port in PDH
radio mode radio mode radio mode radio mode
whose capacity whose capacity whose capacity whose capacity
is lower than 16 is lower than 16 is lower than 16 is lower than 16
E1s) E1s) E1s) E1s)
D1-D3 (default D1-D3 (default D1-D3 (default D1-D3 (default
values of other values of other values of other values of other
IF ports) IF ports) IF ports) line ports)
Protocol Type TCP/IP TCP/IP TCP/IP TCP/IP

Step 4 Set OSPF parameters.

Parameter Value
NE1 NE3 NE4 NE6
OSPF Status Enabled Enabled Enabled Enabled
Static route Enabled Disabled Disabled Enabled
LAN Interface Disabled Enabled Enabled Enabled
Step 5 Create static IP routes.


Parameter Value
NE1 NE6
Destination Address 11.0.0.100 130.9.0.7
Subnet Mask 255.255.255.255 255.255.255.255
Gateway 10.0.0.200 130.9.0.7
Step 6 Query the IP routes.

In the NE Explorer, choose Function Tree > Communication > IP Protocol Stack
Management, and click Query.
The expected query results are provided as follows.
For NE1:
l Routes to the NE IP addresses 129.9.0.2, 129.9.0.3, 129.9.0.4, 129.9.0.5, 130.9.0.6, and
130.9.0.7, with the gateway whose IP address is 129.9.0.2
l Route to the network segment 10.0.0.0, with the gateway whose IP address is 10.0.0.1
l Route to the NE IP address 11.0.0.100, with the gateway whose IP address is 10.0.0.200
For NE6:
l Routes to the NE IP addresses 129.9.0.2, 130.9.0.3,129.9.0.4, and 129.9.0.5, with the
gateway whose IP address is 129.9.0.5
l Routes to the NE IP addresses 10.0.0.0, 10.0.0.1, and 11.0.0.100, with the gateway
whose IP address is 129.9.0.5

Search for NEs by using 10.0.0.1 as IP Address of GNE.

----End
Follow-up Procedure
To ensure communication between the third-party NMS and the third-party gateway NE,
perform the following settings:
l On the third-party gateway NE, configure a static route to the third-party NMS (IP
address: 11.0.0.100). The gateway uses the IP address of NE6, 130.9.0.6.
l On the third-party NMS, configure a static route to the third-party gateway NE whose IP
address is 130.9.0.7. The gateway uses the interface IP address of the router, 11.0.0.200.
Alternatively, you can set the IP address 11.0.0.200 to be the default gateway of the
third-party NMS.
l On the router, configure the routes according to the third-party gateway NE whose IP
address is 130.9.0.7.
1.12 Configuration Example (IP DCN Solution in Multiple

OSPF Areas)
This section provides an example of how to plan and configure the IP DCN solution in
multiple OSPF areas on a transmission network that consists of OptiX radio transmission

This section describes the networking of NEs. OptiX radio equipment and third-party
equipment exchange routing information using the OSPF protocol.
As shown in Figure 1-11, the OptiX radio transmission equipment and the third-party radio
transmission equipment construct a radio transmission network. On the radio transmission
network:
l The convergence network (GE packet ring) provides access of a radio transmission
network consisting of OptiX radio NEs and a radio transmission network consisting of
third-party radio NEs.
l The third-party radio NEs support the OSPF protocol and can communicate the OSPF
protocol with OptiX Radio NEs.
l On the entire network, the number of NEs exceeds the maximum number of NEs
allowed by a DCN subnet. Therefore, multiple OSPF areas are configured.
l The IP addresses of the Huawei NMS and the third-party NMS are on the 10.2.0.0/16
network segment.
l The IP addresses of all the third-party NEs are on the 129.11.0.0/16 network segment.

Figure 1-11 Networking diagram of IP DCN (multiple OSPF areas)

NMS
RT 1
NE 5 NE 6
Third-party
NMS
NE 4
RT 2 NE 1 NE 3
NE 7
NE 8
NE 2
OptiX equipment Third party equipment
Optical GE link Ethernet link Radio link

This section describes the procedure for configuring OptiX radio transmission equipment and
third-party equipment in different OSPF areas.
Data Preparation

NMS
Area
10.2.0.150 Interface IP: 0.0.0.1
129.10.0.100 9-5 9-6
RT 1 129.10.0.5 129.10.0.6
10.2.0.100
0.0.0.0 0.0.0.0
Third-party 9-4 NE 5 NE 6
NMS 129.9.0.4
0.0.0.0
NE 4
NE 3
10.2.0.200 9-1 Area 9-3
129.9.0.1 129.9.0.3
0.0.0.0 0.0.0.0 0.0.0.0
RT 2 NE 7
NE 1 NE 8
129.9.0.7 129.11.0.8
129.9.0.100
NE 2 Area
9-2 0.0.0.2
129.9.0.2 Interface IP:
0.0.0.0
129.11.0.100
Extended ID-Basic ID OptiX equipment Third party equipment

IP address
Gateway Optical GE link Ethernet link Radio link
OSPF Area and NE ID/IP Address Information:
l The entire network is divided into three OSPF areas. The convergence network is the
backbone area (Area 0), in which all NE IP addresses belong to the 129.9.0.0 network
segment. The edge network is divided into Area 1 and Area 2 (non-backbone areas). The

NE IP addresses in Area 1 belong to the 129.10.0.0 network segment and the NE IPs in
Area 2 belong to the 129.11.0.0 network segment. Area1 and Area2 are non-stub areas.
l The OptiX NMS and the third-party NMS belong to the 10.2.0.0 network segment and
communicate with the gateway NE (NE1, whose IP address is 129.9.0.1) on the
backbone area respectively through RT1 (IP address: 10.2.0.150) and RT2 (IP address:
129.9.0.100).
l NE4 (IP address: 129.9.0.4) functions as an ABR in Area 1, with its NE IP address on
the same network segment (129.9.0.0) as those of NEs in Area 0. The interface IP
address of the ABR is 129.10.0.100 and is on the same network segment as the other
NEs in Area 1.
l NE7 (IP address: 129.9.0.7) functions as an ABR in Area 2, with its NE IP address on
the same network segment (129.9.0.0) as those of NEs in Area 0. The interface IP
address of the ABR is 129.11.0.100 and is on the same network segment as the other
NEs in Area 2.
l Automatic route aggregation is enabled for Area 1 and Area 2.
Route Information:
l Plan the following route information between the OptiX radio NEs.
– On NE1 (gateway NE in the backbone area), configure a static route to the Huawei
NMS (IP address: 10.2.0.100) and a static route to the third-party NMS (IP address:
10.2.0.200).
– On NE1, enable the OSPF route flooding function, enabling NE2, NE3, NE4, NE5,
and NE6 to obtain routes to the Huawei NMS and enabling NE7 and NE8 to obtain
the routes to the third-party NMS.
– On the Huawei NMS, configure a static route to the gateway OptiX NE (IP address:
129.9.0.1). The gateway uses the router interface IP address, 10.2.0.150.
– On the third-party NMS, configure a static route to the third-party gateway NE (IP
address: 129.9.0.7). The gateway uses the router interface IP address, 10.2.0.150.
– On RT1 and RT2, configure related routes.
– On the third-party gateway NE (IP address: 129.9.0.7), create Area 2 and specify
the interface IP address as 129.11.0.100.
DCN Channel Information:
l On the GE packet-switched ring, NEs use the inband DCN for DCN communication.
The management VLAN ID takes the default value 4094, and the inband DCN
bandwidth is set to 1000 kbit/s.
l On the edge network, NEs use DCC channels for DCN communication.
l NE3 and NE7 use network management ports for DCN communication between each
other.
NOTE
This example describes the process for data configuration on the OptiX equipment.
Procedure

Paramete Value
r
NE1 NE2 NE3 NE4 NE5 NE6
New ID 1 2 3 4 5 6
New 9 9 9 9 9 9
Extended
ID
3
1

Paramete Value
r
IP 129.9.0.1 129.9.0.2 129.9.0.3 129.9.0.4 129.10.0.5 129.10.0.6

Address
Gateway 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0

IP
Address
Subnet 255.255.0. 255.255.0. 255.255.0. 255.255.0. 255.255.0. 255.255.0.

Mask 0 0 0 0 0 0

Step 3 Enable DCCs corresponding to IF ports.

Parameter Value
IF Port (NE4) IF Port (NE5) IF Port (NE6)
Enabled/Disabled Enabled Enabled Enabled
Protocol Type TCP/IP TCP/IP TCP/IP
IP Address 129.10.0.100 - -
Subnet Mask 255.255.255.255 - -
Step 4 Configure the VLAN ID and bandwidth for an inband DCN.


Parameter Value
NE1 NE2 NE3 NE4
Ethernet 4094 4094 4094 4094

Board VLAN
ID
Bandwidth(kbi 1000 1000 1000 1000

t/s)
Step 5 Configure ports for which inband DCN is enabled.

Parame Value
ter
Ports Ports Ports IF Port Ports IF Ports IF Port

Used Used Used Used Used Used Used
for for for for for for for
Interco Interco Interco Interco Interco Interco Interco
nnectio nnectio nnectio nnectio nnectio nnectio nnectio
n with n with n with n with n with n with n with
NE2 NE1 NE2 NE5 NE1 NE4 NE5
and and and and and
NE4 NE3 NE4 NE3 NE6
Enabled Enabled Enabled Enabled Disabled Enabled Disabled Disabled

Status
Protocol IP IP IP - IP - -
Type

Parame Value
ter
Ports Ports Ports IF Port Ports IF Ports IF Port

Used Used Used Used Used Used Used
for for for for for for for
Interco Interco Interco Interco Interco Interco Interco
nnectio nnectio nnectio nnectio nnectio nnectio nnectio
n with n with n with n with n with n with n with
NE2 NE1 NE2 NE5 NE1 NE4 NE5
and and and and and
NE4 NE3 NE4 NE3 NE6
IP - - - - - - -
Address
Subnet - - - - - - -
Mask

The values for the related OSPF parameters of each NE are provided as follows.
Paramete Value
r
Area 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.1 0.0.0.1
OSPF Enabled Enabled Enabled Enabled Enabled Enabled

Status

Paramete Value
r
Static Enabled Disabled Disabled Disabled Disabled Disabled

route
LAN Disabled Disabled Enabled Disabled Disabled Disabled

Interface
Step 7 Change the network segment of the backbone area for an ABR.
Set the network segment of a backbone area on NE4. The values for the related parameters are
provided as follows.
Parameter Value
IP Address 129.9.0.0
Subnet Mask 255.255.0.0

Step 8 Create an OSPF area for an ABR NE and configure the network segment of the ABR NE.
Create an OSPF area Area 1 on NE4. The values for the related parameters are provided as
follows.
Parameter Value
ID 0.0.0.1
Authentication Type none
Automatic Route Aggregation Enabled
Stub Type NON-STUB

Step 9 Create static routes on NE1.

Parameter Value
Route to the Huawei Route to the Third-Party

NMS NMS
Destination Address 10.2.0.100 10.2.0.200
Subnet Mask 255.255.255.255 255.255.255.255
Gateway 129.9.0.100 129.9.0.100

Step 10 Query IP routes.

Management, and click Query.
The expected query results are provided as follows.
For NE1:
l Routes to the NE IP addresses 129.9.0.2, 129.9.0.3, and 129.9.0.4

l Route to the network segment 129.10.0.0, with the gateway whose IP address is
129.9.0.4
129.9.0.2
l Route to the NE IP address 10.2.0.100, with the gateway whose IP address is
129.9.0.100
l Route to the NE IP address 10.2.0.200, with the gateway whose IP address is
129.9.0.100
For NE4:
l Routes to the NE IP addresses 129.9.0.1, 129.9.0.2, and 129.9.0.3

129.9.0.5
129.9.0.3
Search for NEs by using 129.9.0.1 and 129.9.0.4 as IP Address of GNE.

NOTE
As the IP addresses of NE1 and the centralized NMS are on different network segments, configure static
routes on both the NMS and the related router to guarantee that the TCP/IP communication between them is
normal, before creating NEs.
----End
Follow-up Procedure
To ensure communication between the third-party NMS and the third-party gateway NE,
perform the following settings:
l On the third-party NMS, configure a static route to the third-party gateway NE (IP
address: 129.9.0.7), with the gateway using the router interface IP address 10.2.0.150.
l On RT1 and RT2, configure related routes.
l On the third-party gateway NE (IP address: 129.9.0.7), create Area 2 and specify the
interface IP address as 129.11.0.100.
1.13 Configuration Example (IP DCN Solution Using

OSPF Multi-process)
This section provides an example of how to plan and configure the IP DCN solution using
OSPF multi-process on a transmission network that consists of OptiX radio transmission
equipment.

Multiple OSPF processes need to be deployed to reduce the number of NEs in an OSPF area.
Figure 1-13 shows a microwave network consisting of OptiX radio transmission equipment.
On this network:
l The GE packet ring consisting of OptiX radio transmission equipment is connected to
the microwave network as an aggregation network.
l The number of NEs on the microwave network exceeds the maximum number allowed
for a DCN subnet. Therefore, multiple OSPF processes need to be deployed.
l The NMS IP address belongs to the network segment 10.2.0.0.

Figure 1-13 Networking diagram for the IP DCN solution (OSPF multi-process)
NMS
RT 1
NE 6
NE 5
NE 4
RT 2
NE 1 NE 3
NE 7
NE 2
NE 8
OptiX equipment

This section describes the procedure for deploying multiple OSPF processes on the gateway
NE.

Data Preparation

NMS
10.2.0.150
RT 1 9-6
129.9.0.6
0.0.0.0
9-5 NE 6
129.9.0.5
0.0.0.0
NE 5
9-4
129.9.0.4
0.0.0.0 Area 0.0.0.0
NE 4
RT 2
129.9.0.100 9-1
129.9.0.1
0.0.0.0 9-3
129.10.0.3 9-7
NE 1 0.0.0.0 129.10.0.7
9-2
129.10.0.2 0.0.0.0
NE 3
0.0.0.0 NE 7
NE 2 9-8
Interface IP: 129.10.0.8
Area 0.0.0.0 0.0.0.0
129.10.0.100
NE 8
Extended ID-Basic ID OptiX equipment

IP address
Gateway
OSPF areas and NE IDs/IP addresses:
l Two OSPF processes are deployed on the network. NE1 interface (129.10.0.100)
connected to NE2 belongs to the same OSPF process (OSPF process 2) as NE2, NE3,
NE7, and NE8. The NE1 interface connected to NE4 belongs to the same OSPF process
(OSPF process 1) as NE4, NE5, and NE6. There is no reachable OSPF route between the
two processes.
l The OptiX equipment NE1 (129.9.0.1) belongs to the two OSPF processes. The NE1
interface (129.10.0.100) connected to NE2 belongs to OSPF process 2, and all other
DCN interfaces on NE1 belong to OSPF process 1 (default).
Routing information:
l Plan the following routing information for NEs that are OptiX equipment:
– On NE1 (gateway NE in the backbone area), configure a static route to Huawei
NMS (10.2.0.100).
– On NE1, enable the OSPF route flooding function for the static route so that other
NEs can obtain the route to Huawei NMS.
– On Huawei NMS, configure a static route to the gateway NE (129.9.0.1), with the
gateway IP address being the router interface IP address 10.2.0.150.
– Configure routes between RT1 and RT2.
DCN channel information:

l GE packet equipment uses inband DCN. The management VLAN ID takes the default
value 4094, and the bandwidth is set to 1000 kbit/s.
l Other equipment uses DCC channels.
NOTE
This section describes only the configuration on NE1. For the configuration on other OptiX equipment, see
the IP DCN solution using OSPF single-area.
Procedure
Step 1 Change NE IDs.
This table provides parameter values for changing NE IDs.
Parameter Value
NE1
New ID 1
New Extended ID 9
3
1

This table provides the values of NE communication parameters.
Parameter Value
NE1
Gateway IP Address 0.0.0.0

Parameter Value
NE1
Step 3 Set the VLAN ID and bandwidth for the inband DCN.
This table provides the values of the VLAN ID and bandwidth.
Parameter Value
NE1
Ethernet Board VLAN ID 4094
Bandwidth(kbit/s) 1000

Step 4 Configure the interface on which inband DCN needs to be enabled.

This table provides the parameter values for configuring the interface.
Parameter Value
NE1
Interface Connected to NE2
Enabled Status Enabled
Protocol Type IP
IP Address 129.10.0.100
Subnet Mask -
OSPF subnet ID 2

This table provides the OSPF parameter values.
Parameter Value
NE1
Area 0.0.0.0
OSPF Status Enabled
Static route Enabled
LAN Interface Disabled

Step 6 Create a static route on NE1.

This table provides the parameter values for creating a static route on NE1.
Parameter Value
Route to Huawei NMS
Destination Address 10.2.0.100
Subnet Mask 255.255.255.255
Gateway 10.2.0.100

Step 7 Query IP routes.

Management and click Query.
In normal cases, the routes to other NEs can be viewed on NE1.
Step 8 Create NEs by searching for them on the centralized NMS. For details, see A.3.1.1 Creating
NEs by Using the Search Method (U2000).
Set IP Address of GNE to 129.9.0.1 and search for NEs.
NOTE
The IP addresses of NE1 and the centralized NMS are on different network segments. Therefore, you need to
configure static routes on the NMS and the related router to ensure that the TCP/IP communication between
them is normal, before creating NEs.
In normal cases, all NEs can be created on the centralized NMS.
----End
1.14 Configuration Example (DCC Bytes Transparent

Transmission Solution)
This section provides an example of how to plan and configure the DCC bytes transparent
transmission solution on a transmission network that consists of OptiX radio transmission
equipment and third-party SDH equipment.

This section describes the networking of NEs. On the network, third-party equipment does not
support IP DCN.
In the networking diagram shown in Figure 1-15, the OptiX radio transmission equipment
and the third-party SDH optical transmission equipment form an STM-1 ring network. The
third-party equipment does not support the IP DCN.

Figure 1-15 Networking diagram of the DCC bytes transparent transmission solution
NMS
NE1 NE2
Third-party
NMS
NE4 NE3
OptiX equipment Third-party transmission equipment
Ethernet link Radio link Fiber

This section describes the procedure for configuring the DCC bytes transparent transmission
solution. Configure OptiX radio transmission equipment to use D4-D12 bytes as DCCs and
transparently transmit D1-D3 bytes used by third-party equipment.

Data Preparation
Figure 1-16 Service plan of the DCC Bytes Transparent Transmission solution
NMS
10.0.0.100
9-1 9-2
10.0.0.1 129.9.0.2
0.0.0.0 0.0.0.0
NE1 NE2
Third-party
NMS
9-4 9-3
129.9.0.4 129.9.0.3
0.0.0.0 0.0.0.0
NE4 NE3
IP address
Gateway
NOTE
Third-party equipment uses D1-D3 bytes as DCCs.
Procedure
Step 1 Change the NE ID.
Take NE1 as an example.

Step 2 Set NE Communication Parameters.

Step 3 Configure DCCs.

Step 4 Configuring DCC Transparent Transmission.
Step 5 Query ECC Routes.


The expected result is as follows: The ECC routes to NE2, NE3, and NE4 can be queried on
NE1.
Step 6 Create NEs by using the Search Method (U2000).
The search domains include the following: The search domain when the IP address of the
GNE is 10.0.0.1.

In normal cases, all the NEs can be created on the centralized NMS.
----End
1.15 Configuration Example (DCC Transmission Through

the External Clock Port Solution)
This section provides an example of how to plan and configure the DCC transmission through
the external clock port solution. The solution enables a DCN to traverse a third-party TDM
network.

This section describes the networking of NEs. The OptiX equipment on one side of the
network provides an E1 port to connect to a TDM network, and the OptiX equipment on the
other side provides an SDH optical port to connect to the TDM network.
Figure 1-17 shows a transmission network consisting of OptiX equipment and third-party
equipment. On the network, third-party equipment provides an SDH optical port to connect to
NE1 and an E1 port to connect to NE2.
Figure 1-17 Networking diagram for DCC transmission through external clock ports
NE1 NE2
NMS
NE4
NE3
Network cable E1 cable
Radio link Fiber


This section describes the procedure for configuring the DCC transmission through the
external clock port solution. This example provides the configurations of only NE1 and NE2
that are connected to a third-party TDM network.
Context
NOTE
In this configuration example, only the configurations different from the HWECC solution are provided.
Data Preparation
Item in This Example Planning Principle Planning Principle
External clock access mode See the following figure. -
DCC Channel D1-D3 -
Figure 1-18 Service plan of the DCC transmission through the external clock port solution
4-SP3S-1(E1)
15-CSHN(External Clock Source 1）

15-CSHN(External Clock Source 1）
NE1 NE2
NMS
RTN 980 RTN 980
NE4
NE3
NOTE
l Use the first VC-12 timeslot of the SL1D board in slot 6 (6-SL1D-1) on NE1 to transparently transmit
network management messages of the OptiX equipment.
l If NE1 is an OptiX RTN 905 NE, fiber/cable connections to NE1 are not required.
l If NE2 is an OptiX RTN 905 NE, an E1 cable is directly connected to the 16th port.
Procedure
Step 1 Configuring DCCs.

Step 2 Creating the Cross-Connections of Point-to-Point Services for NE1.
----End
1.16 Configuration Example (L2 DCN Solution, with

Third-Party DCN Packets Not Identified by VLAN IDs)
solution, third-party DCN packets are not identified by VLAN IDs, so that Huawei DCN
packets and third-party DCN packets are forwarded by the system control unit of the RTN
equipment.


This section describes the networking of NEs. In this example, the network is divided into
two L2 DCN subnets. L2 DCN is used for forwarding DCN information within each subnet,
and IP is used for forwarding DCN information between subnets.
The OptiX RTN 900 equipment and third-party radio equipment constructs a microwave
transmission network, as shown in Figure 1-19. On the microwave transmission network:
l The OptiX RTN 900 NEs are managed by the Huawei NMS. The third-party radio
equipment is managed by the third-party NMS.
l The third-party radio equipment uses the L2 DCN solution and does not support dynamic
routes. Therefore, to simplify network route configurations, the OptiX RTN 900
equipment also needs to use the L2 DCN solution.
Figure 1-19 Networking diagram of L2 DCN
Huawei NMS
NE11 Third-party NMS
NE42
NE12 NE31 NE32 NE41
NE51
NE21
NE43
NE22 NE52
NE53
NE24
NE23
NE54
OptiX RTN equipment Third-party equipment
Router Switch
Ethernet


This section describes the procedure for configuring L2 DCN. This example provides the
configurations of only the typical NEs: NE11, NE12, NE21, and NE41.
Data Preparation
The network is divided into two L2 DCN subnets. The following figure shows the subnet and
IP address plan.
Figure 1-20 Subnet and IP address plan in the L2 DCN solution

Ethernet port 1
10.1.1.128 10.1.1.64/24
Subnet
10.3.1.0/24
Huawei NMS
Ethernet port 3
10.3.1.128
10.2.1.64/24
NE11 Ethernet port 2 Third-party NMS

10.3.1.11 10.2.1.128
Huawei radio link 1 Third-party radio link 1
NE41 NE42
NE31 NE32 10.3.3.42
NE12 10.3.2.31 10.3.3.32 10.3.3.41
10.3.2.12
NE51
NE21 10.3.3.51 NE43
10.3.2.21 10.3.3.43
Subnet Subnet
10.3.2.0/24 10.3.3.0/24
NE22 NE52
10.3.2.22 10.3.3.52
NE53
NE24 10.3.3.53
10.3.2.24
NE23
10.3.2.23
NE54
10.3.3.54
OptiX RTN equipment Third-party equipment
Router Switch
Ethernet
NOTE
l Radio links comprised of the OptiX RTN 900 NEs use DCC channels to transmit DCN information.
l To prevent loops in an L2 DCN and further prevent broadcast storms, the STP/RSTP protocol needs to be
enabled for a switch that is connected to the L2 DCN.

Procedure
Step 1 Change the NE ID.
Step 2 Set NE Communication Parameters.


Step 3 Configure DCC channels

Step 4 Disable OSPF for NE11 and NE12.

Step 5 Create static IP routes for NE11 and NE12.

Take the configuration of a static IP route from NE11 to a subnet whose gateway address is
10.3.2.0 as an example.

Step 6 Enable RSTP on the L2 DCN.

Step 7 Create NEs by using the Search Method (U2000).

Take 10.3.1.0 as an example of Search Address.

The search domains are 10.3.1.0, 10.3.2.0, and 10.3.3.0.
In normal cases, all the NEs can be created on the centralized NMS.
----End
Follow-up Procedure
l To ensure the normal communication between Huawei NMS and Huawei NEs, configure
static routes for related routers.
l To ensure proper communication between the third-party NMS and third-party radio
equipment, see Planning Information About IP Routes of Third-Party Radio Equipment
to configure the static routes of the third-party radio equipment.
1.17 Configuration Example (L2 DCN Solution, with

Third-Party DCN Packets Identified by VLAN IDs)
solution, third-party DCN packets are identified by VLAN IDs, so that Huawei DCN packets
are forwarded by the system control unit of the RTN equipment whereas the third-party DCN
packets are transparently transmitted by the packet switching unit.

This section describes the networking of NEs.

Figure 1-21 illustrates a microwave transmission network formed by OptiX RTN 900 NEs
from Huawei, microwave NEs from vendor A, and microwave NEs from vendor B.
Information about the network is as follows:
l OptiX RTN 900 NEs from Huawei are in the center of the network, and microwave NEs
from vendors A and B are at the edge of the network.
l Each vendor's subnet contains several hundreds of NEs.
l Microwave NEs from vendors A and B do not support any dynamic routing protocol but
support a Layer 2 data communication network (L2 DCN).
l Each vendor's NEs are managed by their separate network management systems
(NMSs).
To manage the DCN subnets each of which can contain up to 1024 NEs and to transparently
transmit DCN packets from the NEs from vendors A and B, configure the service channel
transmission scheme for L2 DCN on the OptiX RTN 900 NEs. The Service channel
transmission scheme for L2 DCN solution simplifies DCN configurations and obviates the
configuration of a large number of static routes.
Figure 1-21 Networking diagram for the Service channel transmission scheme for L2 DCN
iManager NMS
VLAN 100/ VLAN 100
200/300
VLAN 200
Vender A NMS
VLAN 300
Vender B NMS
NMS Port
RTN
network
Vender A NMS Port NMS Port Vender B

VLAN 200 VLAN 300

This section describes the procedure for configuring the L2 DCN solution.
Data Preparation
For details about the RTN NE plan, see the following figure.

Figure 1-22 L2 DCN plan

9-11
129.9.0.11
0.0.0.0
C-Aware/IVL
Switch Huawei NMS
3-ISU2 (VLAN 200,300)
9-14 4-ISU2 (VLAN 200,300) VLAN 100 (iManager U2000)
NMS-1 (VLAN 200,300) VLAN 129.9.0.1/16
129.9.0.14
0.0.0.0 100/200/300
Inband DCN: VLAN 200 Vender A NMS
C-Aware/IVL VLAN 4094, 1024kbit/s 129.10.0.1/16
3-ISU2 (VLAN 200,300) 3-ISU2: L2DCN
4-ISU2 (VLAN 200,300) 4-ISU2: L2DCN VLAN 300 Vender B NMS
NMS-1 (VLAN 200) NMS port 129.11.0.1/16
Inband DCN: 9-12

Huawei RTN
VLAN 4094, 1024kbit/s 129.9.0.12
VLAN 100
3-ISU2: L2DCN NE11 0.0.0.0
NE14
4-ISU2: L2DCN
C-Aware/IVL
Vender A Vender B 3-ISU2 (VLAN 200,300)

NMS port NMS port 4-ISU2 (VLAN 200,300)
VLAN 200 NE12 VLAN 300
NMS-1 (VLAN 300)
NE13 Inband DCN:

VLAN 4094, 1024kbit/s
129.11.0.0/16 129.11.0.0/16 3-ISU2: L2DCN
9-13 4-ISU2: L2DCN
129.9.0.13
0.0.0.0
C-Aware/IVL
3-ISU2 (VLAN 200,300)
Legend 4-ISU2 (VLAN 200,300)
NE ID
NE IP Inband DCN:
Subnet mask VLAN 4094, 1024kbit/s
E-LAN service type 3-ISU2: L2DCN
4-ISU2: L2DCN
Ports (VLANs) in E-LAN
VLAN ID and bandwidth

for Inband DCN
Ports what use L2DCN
The following table provides the planning thoughts.
Item Description
VLAN ID VLAN IDs are used to distinguish DCN packets from equipment of
different vendors. The VLAN ID of OptiX RTN equipment is 100, of
Vendor A's equipment is 200, and of Vendor B's equipment is 300.
Transmission DCN packets from the OptiX RTN equipment are transmitted through the
channel of inband DCN channels on IF ports. The VLAN ID of an inband DCN
Huawei DCN channel is 4094, and the bandwidth is 2560 kbit/s because there are many
packets NEs.
Transparent The OptiX RTN equipment needs to be configured with E-LAN services
transmission for transparently transmitting DCN packets from vendor A and vendor B.
method for Because all of the equipment works at Layer 2, the E-LAN service port
third-party type can be set to C-Aware.
DCN packets
DCN packet When OptiX RTN equipment and Vendor A's equipment or Vendor B's
communicati equipment are co-sited, they are interconnected through NMS ports to
on transparently transmit DCN packets.

Item Description
RSTP l The OptiX RTN equipment forms a ring network, so RSTP must be
enabled on the control plane to prevent DCN loops.
l If ERPS is enabled for the ring network, loops of service packets
(including third-party DCN packets) can be prevented. There is no need
to configure MSTP on the service plane.
NMS DCN Because VLAN IDs are used to distinguish DCN packets from equipment
of different vendors, the network management center can use a switch to
separate the DCN packets and send them to the corresponding NMSs.
Static route In this example, the equipment of each vendor and the corresponding NMS
are in the same broadcast domain (the same IP network segment), and do
not require static routes.
Procedure
Step 1 Change an NE ID.
Step 2 Set the communication parameters of the NE.


Step 3 Set the VLAN ID and bandwidth for an inband DCN.

Step 4 Enable the inband DCN channel for an IF port.


Step 5 Disable the DCC of the IF port.

Step 6 Set the VLAN ID for Huawei NMS.


Step 7 Verify that Configuration Status is set to Enabled for RSTP of the L2 DCN on the NE.
Step 8 Search for and create NEs on the U2000.

Normally, all OptiX RTN NEs can be created on the centralized NMS.
Step 9 Configure E-LAN services for transparently transmitting third-party DCN packets.

----End
1.18 Configuration Example (SNMP)

This section provides an example of how to plan and configure NEs when a third-party
SNMP server is used to manage the network.

This section describes the networking of NEs when IP DCN is used.
As shown in Figure 1-23, an IP DCN network is configured for the OptiX RTN 900 NEs. An
IP route is created between the SNMP server and each NE using DCN configurations. The
SNMP server needs to directly query the information on each NE. IP address of the SNMP
server is 10.10.10.3.
Figure 1-23 Networking diagram of SNMP

NE2
NE3 NE1 (GNE)

IP DCN External DCN
SNMP server
IP address: 10.10.10.3
NE4

This section describes the procedure for configuring SNMP. This example provides the
configurations that enable the SNMP server to query NE2 information.

Data Preparation
Item Value in This Example Planning Principle
NMS IP Address 10.10.10.3 -
Read/Write-related l Read/Write Permissions: The SNMP version, read/

information Enabled write permissions, and
l Read/Write Community community name planned
Name: rtn900_read_01/ for an NE must be the same
rtn900_write_01 as those of the SNMP
server.
Traps Version SNMPV2C
Trap reporting flag All report -
Port 162 -
Procedure
Step 1 Set SNMP communications parameters.
----End
1.19 Configuration Example (LLDP)

This section provides an example of how to plan and configure the Link Layer Discovery
Protocol (LLDP) function on OptiX RTN 900 when LLDP is used between OptiX RTN 900
and a NodeB for topology discovery.


This section describes the networking of NEs. In this example, OptiX RTN 900 communicates
with a NodeB through an Ethernet port.
As shown in Figure 1-24, the LLDP function should be enabled on the OptiX RTN 900 and
its adjacent NodeB, so that NodeB maintenance personnel can use the M2000 to query OptiX
RTN 900 information saved on the NodeB, facilitating fault diagnosis.
Figure 1-24 Networking diagram (LLDP)
M2000
3-EG4-1 to NodeB
RTN
network
NodeB NE1
RTN
equipment
Ethernet link

This section describes the procedure for configuring LLDP. Retain default values for LLDP
parameters that have not been planned.
Data Preparation
Table 1-11 LLDP planning information
Port 3-EG4-1 -
Working mode Tx/Rx mode -

Multicast mode Nearest Bridge -
Packet sending period 2s -
TTL multiplier/Delay time for Default value -

initialization/Number of
transmitted packets in FAST mode
Procedure
Step 1 Configure the LLDP function of Ethernet ports.
----End
1.20 Configuration Example (RADIUS)

This section provides an example of how to plan and configure RADIUS for NEs when a
RADIUS server is used to implement centralized authentication of users who log in to the
NEs.

This section describes the networking information about the NEs.
As shown in Figure 1-25, a user logs in to NE1 and NE2 using the NMS. The RADIUS
server performs centralized authentication and management on users to ensure the equipment
security. The description of the networking diagram is as follows:
l The DCN on the equipment side uses the HWECC solution, and IP routes have been
configured between NE1 and the RADIUS server.
l NE1 is a gateway NE and NE2 is a non-gateway NE. For NE1, its IP address is
10.10.10.3, its NE ID is 11, and its extended ID is 9.

l The RADIUS server is configured with 1+1 protection. The IP address of the active
RADIUS server is 10.10.10.1, and the IP address of the standby RADIUS server is
10.10.10.2.
Figure 1-25 Networking diagram of RADIUS

NE2
U2000/LCT
NE3
HWECC network External DCN
Active RADIUS
NE1(GNE)
server IP address:
NE ID:9-11
10.10.10.1
IP address:
10.10.10.3
Standby RADIUS
NE4 server IP address:
10.10.10.2
OptiX RTN equipment

This section describes the procedure for configuring RADIUS. This example provides the
configurations of only the typical NEs: NE1 and NE2.
Data Preparation
Service class and flag l NE1 is configured as the -

RADIUS server and is
configured with 1+1
protection. The IP
address of the main
RADIUS server is
10.10.10.1 and that of
the standby RADUIS
server is 10.10.10.2.
l NE2 is configured as the
proxy RADIUS server
and its NE ID is NE1.

RADIUS function enabling The RADIUS client and -

status proxy RADIUS server
functions are enabled for the
RADIUS server, and the
RADIUS client function is
enabled for the proxy
RADIUS server.
Shared Key RADIUS server: Abcd1234 NEs using the NAS mode
Proxy server: - need to be configured with a
shared key that is the same
as that on the RADIUS
server.
Interval of Packet Default values. -

Transmission/Packet
Retransmission Attempts
Procedure
Step 1 Enable/Disable the RADIUS function.
Step 2 Create a RADIUS server or a RADIUS proxy server.

Take the configuration of NE1 to be the main RADIUS server as an example.

Step 3 Configure RADIUS server parameters.

Take parameter settings on NE1, the main RADIUS server, as an example.

----End
1.21 Configuration Example (NE Anti-Theft Solution)


As shown in Figure 1-26, the U2000 manages a hop of microwave link. You can use the
U2000 to enable anti-theft for devices.

Figure 1-26 Networking diagram

Data Preparation
Table 1-12 Data prepared for NE anti-theft
Item Value in This Example
Anti-theft State Enabled
Control Policy Configuration
Procedure
Step 1 Generate a pair of public and private keys.
1. Choose Administration > NE Security Management > NE Anti-theft from the main
menu.
2. In the Add RSA Keypair dialog box that appears, configure a user name.

NOTE
After the user name is configured, it cannot be modified.
3. Click Export RSA Key to back up the stored RSA key.
4. Click Export Public Key to back up the public key.
Step 2 Configure NE anti-theft.
1. In the physical view, select the NE that requires anti-theft, and then click .
2. Enable anti-theft and configure anti-theft policies.

3. Click Apply.
----End

Feature Configuration Guide 2 Configuring Microwave Features
2 Configuring Microwave Features
About This Chapter

various microwave features.
2.1 Configuration Process (1+1 HSB/FD/SD)

1+1 HSB, 1+1 FD, and 1+1 SD have different implementation modes and therefore have
different configuration processes.
2.2 Configuration Procedure (N+1 Protection)
To configure an N+1 protection group of Integrated IP microwave links, you need to
configure the IF/RF information of the working links and the protection link and then create
the N+1 protection group.
2.3 Configuration Process (XPIC)
XPIC-enabled microwave links have different implementation modes and therefore have
2.4 Configuration Process (AM)
When configuring AM, you need to set the modulation mode of the guaranteed AM capacity
and the modulation mode of the maximum AM capacity.
2.5 Configuration Procedure (ATPC)
When configuring the ATPC, you need to set the ATPC parameters and the power attributes of
ODUs according to the actual requirements.
2.6 Configuration Process (PLA/EPLA/EPLA+)
PLA/EPLA/EPLA+ group configuration is the most important part in PLA/EPLA/EPLA+
configuration.
2.7 Configuration Example (1+1 HSB/FD/SD on an NE)
In this example, a microwave link with 1+1 HSB is configured, with one NE configured at
each end of the link.
2.8 Configuration Example (1+1 HSB/FD/SD on Cascaded NEs)
In this example, a microwave link with 1+1 HSB is configured, with a pair of cascaded RTN
905 1E NEs at each end of the link.
2.9 Configuration Example (XPIC on an NE)

In this example, an XPIC-enabled microwave link with 1+1 HSB is configured, with an NE at
2.10 Configuration Example (XPIC on Cascaded NEs)
In this example, an XPIC-enabled microwave link is configured, with a pair of cascaded RTN
2.11 Configuration Example (N+1 Protection)
In this example, a microwave link with N+1 protection is configured.
2.12 Configuration Example (ATPC)
This topic uses an example to describe how to plan and configure the ATPC according to the
conditions of the network.
2.13 Configuration Example (AM)
This topic uses an example to describe how to plan and configure the AM according to the
2.14 Configuration Example (PLA on an NE)
In this example, PLA protection is configured for a 2+0 microwave link, with one NE at each
end of the link.
2.15 Configuration Example (PLA on Cascaded NEs)
In this example, PLA protection is configured for a 2+0 microwave link, with a pair of
cascaded RTN 905 1E NEs at each end of the link.
2.16 Configuration Example (EPLA)
In this example, EPLA protection is configured for a 3+0 microwave link, with one NE at
2.1 Configuration Process (1+1 HSB/FD/SD)

1+1 HSB, 1+1 FD, and 1+1 SD have different implementation modes and therefore have
Table 2-1 Configuring microwave links with 1+1 HSB on an NE
1 A.8.10.7 Changing the The IF ports on both ends of a microwave link

Running Mode of an must work in the same mode.
IF Port
2 A.8.10.6 Changing the Perform this step to change the IF service type
IF Service Type when the planned value for IF Service Type is not
the default value Hybrid (Native E1+ETH).
3 A.5.1 Configuring a Required.

Single-Hop Radio
Link
4 A.5.3 Modifying the Optional.

Parameters of IF 1+1 If only protection group alarms are expected to be
Protection reported, it is advisable to set Alarm Report
Mode to Only protection group alarms.

5 Configuri A.9.2.1 Required when a hop of 1+1 Integrated IP

ng an air- Creating microwave links need to use LAGs.
interface a LAG
LAG.
A.5.10 Required when a hop of 1+1 Integrated IP
Creating microwave links need to use EPLAs.
a PLA/
EPLA/
EPLA+/
Super
EPLA
Group
NOTE
For configurations when XPIC and IF 1+1 protection coexist, see 2.3 Configuration Process (XPIC)
for XPIC.
Table 2-2 Configuring microwave links with 1+1 HSB on cascading NE s


Running Mode of an IF must work in the same mode.
Port
2 A.8.10.6 Changing the l Perform this step to change the IF service

IF Service Type type when the planned value for IF Service
Type is not the default value Hybrid (Native
E1+ETH).
l Configurations for the main and standby NEs
must be consistent.

3 A.5.2 Creating an IF 1+1 Required. Create a 1+1 HSB protection group

Protection Group on each of the main and standby NEs.
Set parameters as follows:
l Set Working Mode as planned.
l Set Working/Protection Unit Type to
Working Unit for the main NEs and to
Protection Unit for the standby NEs.
l It is recommended that you retain the default
value Revertive for Revertive Mode.
l WTR Time(s) can be set only when
Revertive Mode is set to Revertive.
l It is recommended that you set Enable
Reverse Switching to Enable.
l The following parameters should be set
consistently for the four NEs at both ends of
a radio hop: Working Mode, Revertive
Mode, WTR Time(s), and Enable Reverse
Switching.
NOTE
If 1+1 protection fails to be configured, verify that:
l The modem chips on the main and standby NEs
work in different modes.
l No feature that conflicts with 1+1 protection, such
as cross polarization interference cancellation
(XPIC) and physical link aggregation (PLA), has
been configured.
l The cascade cables between the main and standby
OptiX RTN 905 1E NEs are properly connected.

Single-Hop Radio Link In a 1+1 HSB/SD protection group, the IF and
ODU information of the working NE and the
protection NE must be the same. In a 1+1 FD
protection group, the IF information of the
working NE and the protection NE must be the
same.
5 A.5.3 Modifying the Optional.

Parameters of IF 1+1 If only protection group alarms are expected to
Protection be reported, it is advisable to set Alarm Report
Mode to Only protection group alarms.
NOTE
When the information about radio links in a 1+1 protection group needs to be modified, the main and
standby NEs need to be configured consistently.

2.2 Configuration Procedure (N+1 Protection)

To configure an N+1 protection group of Integrated IP microwave links, you need to
configure the IF/RF information of the working links and the protection link and then create
the N+1 protection group.
NOTE
The OptiX RTN 905 does not support N+1 protection.
Table 2-3 Procedure for configuring an N+1 protection group

1 A.8.10.7 The IF ports on both ends of a microwave link must work in the
Changing the same mode.
Running Mode
of an IF Port
2 A.8.10.6 Perform this step to change the IF service type when the
Changing the planned value for IF Service Type is not the default value
IF Service Hybrid (Native E1+ETH).
Type
3 A.5.1 Required. To configure Integrated IP microwave links with N+1

Configuring a protection, you need to configure the IF and RF information for
Single-Hop each working link and the protection link.
Radio Link NOTE
Configure the same IF information for each working link and the
protection link.
4 A.5.4 Creating Required.

an N+1
Protection
Group
NOTE
If the information about radio links in an N+1 protection group needs to be modified, the modification needs
to be made to only one working link. If two member links in the N+1 protection group form an XPIC group
and both links are main links, the modification needs to be made to the link in the vertical polarization
direction.
During the configuration of microwave services under N+1 protection, take note of the following:
l If the microwave services are TDM services, only the TDM services on a working link need to be
configured. If extra services need to be transmitted, it is necessary to configure extra services on a
protection link.
l If the microwave services are Native ETH services and packet services, the services need to be configured
only over the Integrated IP microwave port on the first working board in the N+1 protection group.

2.3 Configuration Process (XPIC)

XPIC-enabled microwave links have different implementation modes and therefore have
Table 2-4 Configuring XPIC-enabled links on an NE

Ste Operation Remarks
p
1 A.8.10.7 Changing the Optional.

Running Mode of an IF The IF ports on both ends of a microwave link must
Port work in the same mode.
2 A.8.10.6 Changing the IF Perform this step to change the IF service type when
Service Type the planned value for IF Service Type is not the
default value Hybrid (Native E1+ETH).
3 A.5.1 Configuring a Single- Required.

Hop Radio Link
4 A.5.2 Creating an IF 1+1 Required when two XPIC workgroups need to form
Protection Group two 1+1 protection groups.
5 A.5.4 Creating an N+1 Required if members in an XPIC workgroup need to

Protection Group be configured in an N+1 protection group.
6 Configuring A.5.10 Required when XPIC-enabled Integrated IP

an air- Creating a microwave uses PLA/EPLA.
interface PLA/EPLA/
LAG. EPLA+/
Super
EPLA
Group
A.9.2.1 Required when XPIC-enabled Integrated IP

Creating a microwave uses LAG.
LAG
Table 2-5 Configuring XPIC-enabled links on cascading NEs


Running Mode of an IF must work in the same mode.
Port
2 A.8.10.6 Changing the Perform this step to change the IF service type
IF Service Type when the planned value for IF Service Type is
not the default value Hybrid (Native E1+ETH).


Single-Hop Radio Link After the configuration is complete on the local
NE, click Synchronize to synchronize the radio
link configurations to the adjacent NE.
4 A.5.10 Creating a PLA/ Required when XPIC-enabled Integrated IP

EPLA/EPLA+/Super microwave uses PLA/EPLA.
EPLA Group
2.4 Configuration Process (AM)

When configuring AM, you need to set the modulation mode of the guaranteed AM capacity
and the modulation mode of the maximum AM capacity.
Table 2-6 Configuration process of AM

1 A.5.1 Required. Configure the AM function, E1 priority, and

Configuring other IF and RF information.
a Single-
Hop Radio
Link
2 A.8.10.3 Optional.
Setting l You can specify the maximum number of E1s that can
Advanced be transmitted in intermediate modulation schemes, by
AM setting the advanced attributes correspondingly.
Attributes
l Generally, it is recommended that you use the default
values.
l To ensure that a specific number of E1s can be
transmitted in intermediate modulation schemes, adjust
the E1 capacity in each modulation scheme according to
the network planning information. When a new
modulation scheme is adopted, the system transmits
only the number of E1 services allowed by the
modulation scheme and discards the excess E1 services.
3 A.8.10.8 Required when the AM booster function is required.

Enabling or Only ISX2 boards support the AM Booster function.
Disabling
the AM
Booster
Function

NOTE
When an AM-enabled microwave link is configured with the E1 priority, configure E1 Priority for each
cross-connection on the link as follows:
l If a cross-connection is configured for a point-to-point 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 cross-
connection is created.
l If the E1 priority is not specified for a cross-connection during creation, set E1 Priority to Low or
High for the cross-connection after it is created.
2.5 Configuration Procedure (ATPC)

When configuring the ATPC, you need to set the ATPC parameters and the power attributes of
ODUs according to the actual requirements.
Table 2-7 Procedure for configuring the ATPC

1 A.5.1 Required.
Configuring a l If the ATPC function is required, select ATPC.
Single-Hop
Radio Link l Do not select ATPC during site commissioning.
l It is recommended that you set ATPC Upper
Threshold(dBm) to the central value plus 10 dB.
l It is recommended that you set ATPC Lower
Threshold(dBm) to the central value minus 10 dB.
l Set ATPC Automatic Threshold Enable Status to
Disabled by A.8.10.2 Configuring ATPC Attributes.
2 A.8.11.3 Setting To set the maximum transmit power that is supported by the
ODU Power ATPC adjustment function, you need to set Maximum
Attributes Transmit Power(dBm) according to the actual requirements.
TX High Threshold(dBm), TX Low Threshold(dBm), RX
High Threshold(dBm), and RX Low Threshold(dBm) affect
ATPC performance events. Set these parameters if necessary.
2.6 Configuration Process (PLA/EPLA/EPLA+)

PLA/EPLA/EPLA+ group configuration is the most important part in PLA/EPLA/EPLA+
configuration.

Table 2-8 Flow for configuring PLA/EPLA/EPLA+
1 A.5.10 Required.
Creating a NOTE
PLA/EPLA/ l Only OptiX RTN 950 housing CSHU/CSHUA boards, OptiX
EPLA+/Super RTN 950A and OptiX RTN 910A support EPLA+.
EPLA Group
l Only OptiX RTN 980 housing CSHN boards and OptiX RTN 950
housing CSH boards do not support EPLA.
l When PLA/EPLA is implemented by stacking NEs, a PLA/
EPLA group must be created on both the master and slave NEs.
l For other PLA/EPLA configuration requirements, see Feature
Dependencies and Limitations.
2.7 Configuration Example (1+1 HSB/FD/SD on an NE)

In this example, a microwave link with 1+1 HSB is configured, with one NE configured at

The topic describes the networking information of the NEs.
Figure 2-1 shows a hop of important radio link. To ensure the reliable transmission of
services, the radio link between NE1 and NE2 adopts the 1+1 HSB protection.
Figure 2-1 Networking diagram of 1+1 HSB protection

101
14930M
14510M
28M
1+1 HSB
Enabled
Disabled
H-polarzation
Tx high Tx low
NE2 NE1
Link ID
Tx high station Tx Freq.
Tx low station Tx Freq.
Chanel spacing
RF configuarion
AM enabling
ATPC enabling
Polarization


This section describes the procedure for configuring data.

Data Preparation
Item Value in This Example Planning Guideline
Basic information about Figure 2-2 provides the l Slot:

radio links in a 1+1 HSB details. Single-polarized – For OptiX RTN 905
protection group antennas are used on this 2E, it is
network. recommended to set
the IF unit in slot 3 as
the main IF unit.
– Single-channel IF
boards on the OptiX
RTN 950/950A/980
can form a 1+1
FD/SD protection
group only if they are
housed in paired
slots. Slots for single-
channel IF boards in
a 1+1 HSB protection
group are not
restricted. However,
it is recommended
that single-channel IF
boards in a 1+1 HSB
protection group be
housed in paired
slots.
– The two IF ports on a
dual-channel IF
boards can form an
intra-board 1+1
HSB/FD/SD
protection group. The
two IF ports on a
dual-channel IF board
can form two inter-
board 1+1
HSB/FD/SD
protection groups
with the two IF ports
on another dual-
channel IF board only
if the two IF ports on
each board form an
XPIC group.
l If 1+1 HSB works in
revertive mode, set the
wait to restore (WTR)
time to a value between
5 and 12 minutes. The

default value (10

minutes) is
recommended.
l It is recommended that
you set Alarm Report
Mode to Only
protection group
alarms.
you set Enable Reverse
Switching to Enabled.
Hybrid/AM attribute Table 2-9 provides the l Ensure that the air
information details. The Hybrid radio interface bandwidth for a
capacity and the AM radio link in AM
function are available only if guaranteed capacity
the corresponding license mode is higher than the
files are loaded. total bandwidth of high-
priority services, and link
availability meets
availability requirements
of high-priority services.
l Ensure that the air
interface bandwidth of
full AM capacity is
higher 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, E1
service bandwidth of full
AM capacity ≤ Service
bandwidth of full AM
capacity - Service
bandwidth of guaranteed
AM capacity + E1
service bandwidth of
guaranteed AM capacity.
Power information Table 2-10 provides the -

details.
NOTE
In the case of radio links configured with 1+1 HSB, one protection group maps one link. You need to
configure only the IF and RF information on the main equipment.

Figure 2-2 Basic information about radio links in a 1+1 HSB protection group
101 Link ID
14930M Tx high station Tx Freq
14510M Tx low station Tx Freq
28M Chanel spacing
420M T/R Spacing
1+1 HSB RF configuration
3-ISV3 Working Board
5-ISV3 Protection Board
Tx high Tx low
NE2 NE1
Table 2-9 Hybrid/AM attribute information
Parameter NE1 NE2
3-ISV3 3-ISV3
AM Selected Selected
Modulation Mode of the QPSK QPSK

Guarantee AM Capacity
Modulation Mode of the 128QAM 128QAM

Full AM Capacity
Guarantee E1 Capacity 16 16
Table 2-10 Power information
Parameter NE1 NE2
53-ODU 53-ODU
TX Power(dBm) 10 10

Parameter NE1 NE2
53-ODU 53-ODU
Power to Be -45 -45

Received(dBm)
ATPC Deselected Deselected
Procedure
Step 1 Configure a hop of radio link for a 1+1 HSB protection group.
Step 2 Modify parameters of the IF 1+1 protection.

----End
2.8 Configuration Example (1+1 HSB/FD/SD on Cascaded

NEs)
In this example, a microwave link with 1+1 HSB is configured, with a pair of cascaded RTN

Figure 2-3 shows a hop of important radio link. 1+1 hot standby (HSB) protection is
configured to ensure reliable transmission of services.
Figure 2-3 Networking diagram for 1+1 HSB protection

Link ID: 101
Transmit frequency of the Tx high site : 14930 MHz
Transmit frequency of the Tx low site: 14510 MHz
Channel spacing: 28 MHz
RF configuration: 1+1 HSB
NE 1
NE 3
1-COMBO 1-COMBO
ODU ODU
1-COMBO 1-COMBO
Hybrid Hybrid
coupler Antenna Antenna coupler
NE 2 NE 4
ODU ODU
OptiX RTN 905 1E Radio link Cascading cable


Data Preparation
1+1 HSB protection Figure 2-4 provides the l If 1+1 HSB works in
information details. Single-polarized revertive mode, set the
antennas are used on this wait to restore (WTR)
network. time to a value between
5 and 12 minutes. The
default value (10
minutes) is
recommended.
you set Alarm Report
Mode to Only
protection group
alarms.
you set Enable Reverse
Switching to Enabled.

Hybrid/AM attribute Table 2-11 provides the l Ensure that the air
information details. The Hybrid radio interface bandwidth for a
capacity and the AM radio link in AM
function are available only if guaranteed capacity
the corresponding license mode is higher than the
files are loaded. total bandwidth of high-
priority services, and link
availability meets
availability requirements
of high-priority services.
l Ensure that the air
interface bandwidth of
full AM capacity is
bandwidth of all
services, and link
availability requirement
of low-priority services.
l When the E1 priority
function is enabled, E1
service bandwidth of full
AM capacity ≤ Service
bandwidth of full AM
capacity - Service
bandwidth of guaranteed
AM capacity + E1
service bandwidth of
guaranteed AM capacity.
Power information Table 2-12 provides the -

details.
NOTE
In the case of radio links configured with 1+1 HSB, one protection group maps one link. You need to
configure only the IF and RF information on the main equipment.

Figure 2-4 Basic information about radio links in a 1+1 HSB protection group
Link ID: 101
T/R Spacing: 420M
RF configuration: 1+1 HSB
Working NE: NE1 and NE 3
NE 1 Protection NE: NE2 and NE 4 NE 3
1-COMBO 1-COMBO
ODU ODU
1-COMBO 1-COMBO
Hybrid Hybrid
coupler Antenna Antenna coupler
NE 2 NE 4
ODU ODU

Parameter Value of the Main Link Value of the Standby Link
NE1 NE3 NE2 NE4
AM Deselected Deselected Deselected Deselected
Manually 128QAM 128QAM 128QAM 128QAM

Specified
Modulation
Mode
Guarantee E1 16 16 16 16
Capacity
Table 2-12 Power information

Parameter Value of the Main Link Value of the Standby Link
NE1 NE3 NE2 NE4
ATPC Deselected Deselected Deselected Deselected
TX 16 16 16 16
Power(dBm)
Power to Be -46 -46 -46 -46

Received(dBm)

Procedure
Step 1 Create an IF 1+1 protection group.
Step 2 Configure a hop of radio link.
----End

2.9 Configuration Example (XPIC on an NE)

In this example, an XPIC-enabled microwave link with 1+1 HSB is configured, with an NE at

This topic describes the networking information about the NEs.
The service requirements between two sets of OptiX RTN 980 are as follows:
l The radio link needs to transmit 32xE1 services and 400 Mbit/s Ethernet services at the
same time.
l According to the preceding service requirements and available spectrum resources, the
XPIC-enabled radio links shown in Figure 2-5 are configured to meet the requirement
for large-capacity transmission.
l Two XPIC workgroups form two 1+1 HSB protection groups and load-sharing LAGs are
configured.
l As shown in Figure 2-6, NE1 and NE2 have the same board configurations.

101 102
32660M 32660M
31848M 31848M
56M 56M
1+1 HSB 1+1 HSB
V-polarization H-polarization
NE1 NE2
Tx high
Tx low
Link ID
Channel spacing
RF Configuration
Polarization

Figure 2-6 Board configuration


Data Preparation
XPIC radio link information Figure 2-7 provides the l When CCDP is applied
details. to radio links, XPIC IF
NOTE boards must be installed
The link planning information and the XPIC function
that is not associated with the must be enabled.
configuration of IDU (except
for the polarization direction) l The transmit frequency,
is not provided in this transmit power, T/R
example. spacing, ATPC
In this example, two XPIC parameters (including
workgroups need to form two ATPC enable status and
1+1 HSB protection groups. ATPC adjustment
Therefore, the IDs of the radio thresholds), channel
links in the vertical
spacing, modulation
polarization direction of the
two XPIC workgroups must be scheme, and AM
set to 101 and the IDs of the parameters must be set
radio links in the horizontal consistently for the links
polarization direction of the in the horizontal and
two XPIC workgroups must be vertical polarization
set to 102.
directions in an XPIC
Hybrid/AM attribute Table 2-13 provides the workgroup.
information details.
Power and ATPC Table 2-14 provides the

Figure 2-7 Basic information about XPIC radio links

101 102
32660M 32660M
31848M 31848M
56M 56M
1+1 HSB 1+1 HSB
3-ISX2 4-ISX2
5-ISX2 6-ISX2
V-polarization H-polarization
NE1 NE2
Tx high
Tx low
Link ID
Channel spacing
RF Configuration
Working Board
Protection Board
Polarization


Parameter Link 1 Link 2
E1 capacity 16 16
AM status Disabled Disabled
Modulation scheme 64QAM 64QAM
Table 2-14 Power and ATPC information

Parameter Link 1 Link 2
TX Power (dBm) 6.0 (NE1) 6.0 (NE1)

6.0 (NE2) 6.0 (NE2)
RX Power (dBm) -45.0 (NE1) -45.0 (NE1)

-45.0 (NE2) -45.0 (NE2)
ATPC status Disabled Disabled
Procedure
Step 1 Configure a hop of radio link as the main link in an XPIC workgroup.

Step 2 Create an IF 1+1 protection group.

The 1+1 HSB protection group parameter configurations on NE1 and NE2 are identical, so
the configurations of NE1 are used as an example.
3
1
Step 3 Create a LAG group.

----End
2.10 Configuration Example (XPIC on Cascaded NEs)

In this example, an XPIC-enabled microwave link is configured, with a pair of cascaded RTN

The service requirements on a hop of radio link are as follows:
l The radio link needs to transmit 32xE1 services and 400 Mbit/s Ethernet services at the
same time.
l According to the preceding service requirements and available spectrum resources, the
XPIC-enabled radio links shown in Figure 2-8 are configured to meet the requirement
for large-capacity transmission.


Link ID: 101
RF configuration: XPIC
NE 1 V-polarization NE 3
1-COMBO 1-COMBO
ODU ODU
1-COMBO 1-COMBO
Antenna Antenna
NE 2 NE 4
ODU Link ID: 102 ODU
H-polarization

Data Preparation
XPIC work group Figure 2-9 provides the l XPIC must be enabled if
configurations details. CCDP is enabled.
l Set the transmit
frequency, transmit
power, T/R spacing,
ATPC parameters (ATPC
enabling status and
ATPC adjustment
thresholds), channel
spacing, modulation
scheme, and AM
parameters to the same
values for the links in the
horizontal and vertical
polarization directions in
an XPIC workgroup.

Figure 2-9 Configuration about an XPIC work group

Link ID: 101
NE 1
V-polarization NE 3
1-COMBO 1-COMBO
ODU ODU
1-COMBO 1-COMBO
Antenna Antenna
NE 2 NE 4
ODU Link ID: 102 ODU
H-polarization
Procedure
Step 1 Configure an XPIC work group that is implemented through cascading.
2
3
After configuring the radio links on NE1 and

NE3, click Synchronize to synchronize the
radio link configurations to the adjacent NE2
and NE4.
----End
2.11 Configuration Example (N+1 Protection)

In this example, a microwave link with N+1 protection is configured.

NOTE
The OptiX RTN 905 does not support N+1 protection.

The topic describes the networking information about the NEs.
As shown in Figure 2-10, the service requirements between two sets of OptiX RTN 980 are
as follows:
l The Integrated IP microwave link needs to transmit 32xE1 services and 300 Mbit/s
Ethernet services at the same time.
l The link that is configured with the N+1 (N=2) protection.
l The AM function needs to be enabled.
l As shown in Figure 2-11, NE1 and NE2 have the same board configurations. This
example uses the ISU2 board.

101 102 103
14935M 14963M 14991M
14515M 14543M 14571M
28M 28M 28M
Working Channel 1 Protection Channel Working Channel 2
V-polarization H-polarization V-polarization
User A User A
16E1+FE(100M) NE1 NE2 16E1+FE(100M)
User B Tx high
16E1+FE(100M) Tx low User B
16E1+FE(100M)
FE(100M) Link ID
Tx low station Tx Freq. FE(100M)
User C Channel spacing
Channel Type User C
Polarization

Dual-polarized
antenna
ODU
Working channel 1
Hybrid
coupler ODU
Protection channel
ODU
Working channel 2
PIU PIU
FAN
System control, Switch & Timing board
System control, Switch & Timing board
IF board IF board
IF board


Data Preparation
Basic information about Figure 2-12 provides the l When capacity of

radio links details. services to be transmitted
over a radio link is larger
than the capacity of one
channel and the radio
link needs to be
protected, you can adopt
N+1 protection. For a
radio link that transmits
only Ethernet services, it
is recommended that you
use air-interface LAG
protection instead of N
+1 protection.
l Ensure that channels of
SDH radio use the same
channel spacing,
modulation scheme, and
air interface capacity.
Hybrid/AM attribute Table 2-15 provides the Ensure that channels of

information details. Integrated IP microwave use
the same channel spacing,
modulation scheme, air
interface capacity for TDM
services, capacity of
Ethernet services, and
parameters for capacity
(including AM parameters
and E1 priority parameters).
Power and ATPC Table 2-16 provides the -

Information about the N+1 Table 2-17 provides the l It is recommended that
(N=2) protection details. the slot ID for the IF
board of the protection
channel be greater than
that of the working
channel.
you set the wait to
restore time to 10
minutes.
you set SD as a
switching condition.

Figure 2-12 Basic information about radio links in a N+1 protection group
101 102 103
14935M 14963M 14991M
14515M 14543M 14571M
28M 28M 28M
Working Channel 1 Protection Channel Working Channel 2
V-polarization H-polarization V-polarization
User A User A
16E1+FE(100M) NE1 NE2 16E1+FE(100M)
User B Tx high
16E1+FE(100M) Tx low User B
16E1+FE(100M)
FE(100M) Link ID
Tx low station Tx Freq. FE(100M)
User C Channel spacing
Channel Type User C
Polarization
Parameter Link 1 Link 2 Link 3

(working link 1) (protection link) (working link 2)
IF Service Type Hybrid (Naive E1+ETH) Hybrid (Naive E1+ETH) Hybrid (Naive E1+ETH)
Number of E1 services 16 16 16
Capacity of Ethernet 100 100 100

services (Mbit/s)
Enable AM Enabled Enabled Enabled
AM guaranteed capacity QPSK QPSK QPSK

mode
AM full capacity mode 256QAM 256QAM 256QAM
Enable E1 priority Disabled Disabled Disabled
Table 2-16 Power and ATPC information
Parameter Link 1 Link 2 Link 3

(working link 1) (protection link) (working link 2)
Transmit power (dBm) 16.5 (NE1) 16.5 (NE1) 16.5 (NE1)

16.5 (NE2) 16.5 (NE2) 16.5 (NE2)
Power to be received -46 (NE1) -46 (NE1) -46 (NE1)

(dBm) -46 (NE2) -46 (NE2) -46 (NE2)
ATPC enabling Disabled Disabled Disabled

Table 2-17 Information about the N+1 (N=2) protection

Parameter NE1 NE2
Work Unit 3-ISU2 3-ISU2

5-ISU2 5-ISU2
Work Unit 6-ISU2 6-ISU2
Procedure
Step 1 Configure a hop of radio link.
Link 101 between NE1 and NE2 is used as an example. For details, see
.
Step 2 Create an N+1 protection group.
NE1 is used as an example. The configuration on NE2 is similar.

5
6
8
9
10
----End
2.12 Configuration Example (ATPC)

This topic uses an example to describe how to plan and configure the ATPC according to the


As shown in Figure 2-13, the ATPC function needs to be enabled for the radio link between
the two sets of OptiX RTN 980. With this function, the RSL at both ends of a radio link can
be always about -46 dBm, and the transmit power of the ODU will not exceed 20 dBm.

3-ISV3-1(to NE2) 3-ISV3-1(to NE1)
1+0
NE1 NE2


Data Preparation
ATPC configuration Figure 2-14 provides the l The ATPC parameter

details. settings must be
consistent at both ends of
a hop of radio link.
the ATPC function be
disabled for areas where
fast fading is severe.
l Set the central value
between the ATPC upper
threshold and the ATPC
lower threshold to the
expected receive power.
l Ensure that the
difference between the
ATPC upper threshold
and the ATPC lower
threshold is equal to or
more than 5 dB.
l Set the maximum
transmit power when the
transmit power needs to
be restricted to a certain
range.
you disable automatic
ATPC adjustment
threshold setting.

Figure 2-14 ATPC configuration
Board
ATPC Enable Status
Middle RSL Value (dBm)
Maximum Transmit Power
of an ODU (dBm)

Enabled Enabled
-46 -46
20 20
1+0
NE1 NE2
Procedure
Step 1 Configure ATPC information for a link on Configuring a Hop of Radio Link.
NE1 is used as an example.

Step 2 Set the ODU power attributes.

2 4
----End

2.13 Configuration Example (AM)

This topic uses an example to describe how to plan and configure the AM according to the

To balance link availability with service bandwidth, the AM function and E1 priority function
need to be enabled for the radio link between NE1 and NE2. See Figure 2-15. The
modulation mode of the link is originally 128QAM.
Figure 2-15 Networking diagram of the AM

1+0
NE1 NE2
Modulation Mode of the Guarantee Capacity:QPSK
Modulation Mode of the Full Capacity:128QAM
Guarantee E1 Capacity:1
Full E1 Capacity:4


Data Preparation
AM configuration Figure 2-16 provides the l Planning guidelines for

information details. AM enabling/disabling:
– If various types of
services transmitted
on a radio link need
to meet the same
availability
requirements, it is
recommended that
you disable the AM
function. Instead,
determine a fixed
modulation scheme
based on the
availability
requirements and the
maximum service
capacity.
– If the types of
services meet
different availability
requirements (that is,
a part of E1 signals
and Ethernet signals
can be discarded
when the signal
quality deteriorates),
it is recommended
that you enable the
AM function.
l Planning guidelines for
AM attributes:
– Ensure that the air
interface bandwidth
for a radio link in AM
guaranteed capacity
mode is higher than
the total bandwidth of
high-priority services,
and link availability
meets availability
requirements of high-
priority services.
– Ensure that the air
interface bandwidth
of full AM capacity is

bandwidth of all
services, and link
availability
requirement of low-
priority services.
l Planning guidelines on
E1 priority:
– When Hybrid
microwave transmits
IMA services, E1
priority can be
enabled. Ensure that
E1 capacity equals
the E1 capacity
required by high-
priority IMA
services, and full E1
capacity equals E1
capacity required by
IMA services.
– When the E1 priority
function is enabled,
E1 service bandwidth
of full AM capacity ≤
Service bandwidth of
full AM capacity -
Service bandwidth of
guaranteed AM
capacity + E1 service
bandwidth of
guaranteed AM
capacity.
– The priority of an E1
service is irrelevant to
its IF board (unit)
timeslot but is
specified when its
cross-connection is
being configured. E1
service priorities can
be set to either High
or Low.
– When an E1 service
traverses multiple
radio links, priorities
set for the service
must be consistent on
the links.

Figure 2-16 Networking diagram of the AM function
1+0
NE1 NE2
Modulation Mode of the Guarantee Capacity:QPSK
Modulation Mode of the Full Capacity:128QAM
Guarantee E1 Capacity:1
Full E1 Capacity:4
Procedure
Step 1 Configure AM information for a link on Microwave Link Configuration.
1 3
----End
2.14 Configuration Example (PLA on an NE)

In this example, PLA protection is configured for a 2+0 microwave link, with one NE at each
end of the link.


This section describes the networking information about each NE.
As shown in Figure 2-17, the Ethernet transmission channels on the two Integrated IP
microwave links between NE1 and NE2 are aggregated as a PLA group.
Main link
Slave link
NE 1 NE 2
PLA
Main port: 3-ISU2-1 Main port: 3-ISU2-1
Slave port: 5-ISU2-1 Slave port: 5-ISU2-1


Data Preparation
PLA configurations Figure 2-18 provides the l Slot:

details. – For OptiX RTN 905
2E, it is
recommended to set
the IF unit in slot 3 as
the main IF unit.
– Single-channel IF
boards on the OptiX
RTN 950/950A/980
can form a PLA
group only if they are
housed in paired
slots.
– A dual-channel IF
board supports only
an intra-board PLA
group.
l Member links in a PLA
group must use the same
channel spacing.
l The IF services
transmitted by the
members in a PLA group
must be of the same type.
l The master and slave
ports in a PLA group
must use the same
Ethernet header
compression mode.
l PLA parameter settings
must be the same at both
receive and transmit
ends.

Minimum Active Links 1 When PLA coexists with

Ethernet protection like
ERPS or LPT, Ethernet
protection switching can be
triggered when some
are faulty. To trigger
Ethernet protection
switching by some failed
members, set Minimum
Active Links to 1 plus the
maximum number of
remaining activated member
links upon the triggering of
protection switching.
Main link
Slave link
NE 1 NE 2
PLA
Procedure
Step 1 Create a PLA group.

6
5
----End
2.15 Configuration Example (PLA on Cascaded NEs)

In this example, PLA protection is configured for a 2+0 microwave link, with a pair of
cascaded RTN 905 1E NEs at each end of the link.

As shown is Figure 2-19, Ethernet service transmission channels of OptiX RTN 905 1E are
aggregated as a PLA group by stacking NEs, so that the bandwidth utility and reliability of
the Ethernet services transmitted by the integrated IP microwave are improved.

Ethernet Service Main link Ethernet Service
NE 1 NE 3
Slave link
PLA
NE 2 NE 4
Service cascading cable

Data Preparation
PLA configuration Figure 2-20 provides the l Member links in a PLA

details. group must use the same
channel spacing.
l The master and slave
ports in a PLA group
must use the same
Ethernet header
compression mode.
l PLA parameter settings
ends.

Minimum Active Links 1 When PLA coexists with

triggered when some
Ethernet protection
maximum number of
Ethernet Service Main link Ethernet Service
NE 1 NE 3
Slave link
PLA
NE 2 NE 4
Service cascading cable
Procedure
Step 1 A.5.10 Creating a PLA/EPLA/EPLA+/Super EPLA Group.

6
1
----End
2.16 Configuration Example (EPLA)

In this example, EPLA protection is configured for a 3+0 microwave link, with one NE at

The section describes the networking of NEs.
As shown in Figure 2-21, Ethernet channels on the three Integrated IP microwave links
between NE1 and NE2 need to be aggregated to an enhanced physical link aggregation
(EPLA).
NE1 and NE2 are both OptiX RTN 950A NEs.

Main link
Slave link
Slave link
NE 1 NE 2
EPLA

Data Preparation
EPLA configurations Figure 2-22 provides the l EPLA is preferred if it is

details. supported at both ends of
a radio link.
l The IF services
transmitted by the
members in an EPLA
group must be of the
same type.
l EPLA parameter settings
ends.

Minimum Active Links 1 When EPLA coexists with

triggered when some
members in an EPLA group
Ethernet protection
maximum number of
Main link
Slave link
Slave link
NE 1 NE 2
EPLA
Procedure
Step 1 Create an EPLA group.

7
6
8
2
NOTE
If the system control board on the OptiX RTN 980 is CSHNA, the bandwidth of an EPLA group must be
configured during EPLA configuration. The bandwidth of an EPLA group must not be less than the total
maximum Ethernet service bandwidth of all member links. If the bandwidth of an EPLA group is greater than
2.5 Gbit/s, the EPLA ID must be set to 10.
----End

Feature Configuration Guide 3 Configuring SDH Protection Features
3 Configuring SDH Protection Features
About This Chapter

various SDH Protection.
3.1 Configuration Procedure(LMSP)

To configure a linear MSP service, you need to create the linear MSP protection group and
then create the service cross-connections.
3.2 Configuration Procedure(SNCP)
For SNCP services, you need to perform service configuration on the service add/drop NE
and service pass-through NEs separately.
3.3 Configuration Procedure (Ring MSP)
To configure a ring MSP service, you need to create a ring MSP protection group and then
create service cross-connections.
3.4 Configuration Example (SNCP)
By using an example, this topic describes how to plan and configure the SNCP according to
the network conditions.
3.5 Configuration Example (LMSP)
This topic uses an example to describe how to plan and configure the linear MSP service.
3.6 Configuration Example (Ring MSP)
This section uses an example to describe how to plan and configure ring MSP according to
network conditions.
3.1 Configuration Procedure(LMSP)

To configure a linear MSP service, you need to create the linear MSP protection group and
then create the service cross-connections.

Table 3-1 Procedure for configuring a linear MSP service

1 A.6.1 Configuring Linear MSP Required when the linear MSP is

configured for the optical transmission line.
The parameters need to be set according to
the service planning.
2 A.7.1 Creating the Cross- Required when the service is a point-to-

Connections of Point-to-Point point service.
Services The parameters need to be set according to
NOTE
Under linear MSP, only TDM services on a working link need to be configured. Under 1:N linear MSP,
configure extra TDM services on a protection link if required.
3.2 Configuration Procedure(SNCP)

For SNCP services, you need to perform service configuration on the service add/drop NE
and service pass-through NEs separately.
Table 3-2 Procedure for configuring the SNCP service on an add/drop NE

1 A.7.2 Creating Cross- Required.

Connections of SNCP Services The parameters need to be set according to
2 A.7.5 Configuring the Optional when the TDM service is an SNCP

Automatic Switching of SNCP service.
Services
3 A.7.3 Modifying the Priorities Required when the working source, protection
of E1 Services source, or sink of an SNCP service is a link
where the AM function and the E1 priority
function are enabled.
Modify E1 Priority according to service
planning.

Table 3-3 Procedure for configuring the SNCP service on a pass-through NE

1 A.7.1 Creating the Cross- Required.

Connections of Point-to-Point The parameters need to be set according to
Services the service planning.
2 A.7.4 Inserting E1_AIS upon a Optional when the IFU2/IFX2/ISX2/ISU2/

TU_AIS Condition ISV3/ISM6 and IF1 boards work as the east
interface board and west interface board on
the SNCP ring and pass-through services are
configured between these interface boards.
Perform the operation for the E1 port on the
IFU2, IFX2, ISX2, ISU2, ISM6 or ISV3
board that the pass-through services involve.
The RTN 900 allows the TU_AIS to be
automatically inserted upon detection of the
E1_AIS. Therefore, ensure that E1_AIS to
TU_AIS takes its default value Auto.
NOTE
In the case of TDM services with the SNCP, you need to configure the cross-connections of SNCP services
on the add-drop NEs and configure the cross-connections of point-to-point services on the pass-through NEs.
3.3 Configuration Procedure (Ring MSP)

To configure a ring MSP service, you need to create a ring MSP protection group and then
create service cross-connections.
NOTE
Only OptiX RTN 980 support the ring MSP feature.
Table 3-4 Configuration procedure for a ring MSP service

1 A.6.5 Configuring Ring MSP Required when the

optical transmission line
is configured with ring
MSP.
You need to set the
parameters according to

2 Configuring the cross- A.7.1 Creating the Required when the

connections of TDM Cross-Connections of service is a point-to-point
servicesa Point-to-Point Services service.
You need to set the
parameters according to
NOTE
a: Under ring MSP, only TDM services on a working link need to be configured.
3.4 Configuration Example (SNCP)

By using an example, this topic describes how to plan and configure the SNCP according to
For SNCP application examples, see Configuration Example (TDM Services on a Hybrid
Microwave Ring Network).
3.5 Configuration Example (LMSP)

This topic uses an example to describe how to plan and configure the linear MSP service.

As shown in Figure 3-1, the relative networking information is as follows:
l To ensure the reliable transmission of the services between NE11 and NE13, the linear
MSP is configured for the optical transmission line between NE11 and NE13.
l NE11 transmits the services in the first 16 E1s of the STM-1 to NE12.
l NE11 is an OptiX RTN 980.
Figure 3-1 Networking diagram of the linear MSP
16xE1
STM-1
NE12 NE11 NE13

Working port: 16-SL4D-1
Protection port: 16-SL4D-2
Sink board: 1-ISU2


Data Preparation
NOTE
In this example, no extra service needs to be transmitted, so single-ended non-revertive 1+1 linear MSP is
used to protect optical services between NE11 and a third-party SDH network.
Protection Type 1+1 Linear MSP It is recommended that you

select the 1+1 single-ended
Switching Mode Single-Ended Switching non-revertive mode or the
1:N dual-ended revertive
mode as required.
l In 1+1 single-ended non-
revertive mode, a
switchover is performed
in a simple manner and
the switching time is
short. In addition, the
NEs at both ends do not
need to be
interconnected.
l In 1:N dual-ended
revertive mode, extra
services can be
transmitted.
NOTE
Channelized STM-1 links only
support 1:1 linear MSP, and
the standby channel cannot
transmit extra services.
Revertive Mode Non-Revertive If the protection is in the

revertive mode, set the wait
to restore time to a value
between 5 and 12 minutes.
The default value (10
minutes) is recommended.
SD Switching Enabled (default value) It is recommended that you

set SD as a switching
condition.
NOTE
Unless otherwise specified,
retain the default value for SD
Switching.

Protocol Type New Protocol (default The MSP protocols used at

value) both ends must be
consistent. It is
recommended that you
apply the new MSP protocol
when both ends use the
OptiX equipment.
NOTE
retain the default value for
Protocol Type.
West Working Unit 16-SL4D-1 For OptiX RTN 950/950A/

980, it is recommended that
West Protection Unit 16-SL4D-2 you use the line ports on one
line board for the working
channel and those on
another line board for the
protection channel, to
prevent protection failures
when one line board
becomes faulty.
Procedure
Step 1 Configure linear MSP.

5
6
Step 2 Create cross-connections for point-to-point services.
The following table provides parameter values for NE11.
3 2

Step 3 Testing E1 Services Using PRBS

Test any two E1 services on each base station. The test results show that the E1 services
contain no bit errors.
----End
3.6 Configuration Example (Ring MSP)

This section uses an example to describe how to plan and configure ring MSP according to
network conditions.
NOTE
Only OptiX RTN 980 support the ring MSP feature.

The section describes the networking information about NEs.
As shown in Figure 3-2, one OptiX RTN 950 (NE4) and three OptiX transmission devices
form a two-fiber bidirectional MSP ring. NE4 transmits 16xE1 services between NE1 and
NE5.
Figure 3-2 Two-fiber bidirectional MSP ring
IF board: 3-ISV3
West line: 16-SL4D-1
East line: 16-SL4D-2
NE 1
16E1
NE 2 MSP ring NE 4
NE 5
NE 3


Data Preparation
Planning Service Timeslots On an optical ring network, —

services from NE1 to NE5
occupy the first to sixteenth
VC-12 timeslots of the first
VC-4 on the east line board
of NE4. On a radio link,
services from NE1 to NE5
occupy the first to sixteenth
VC-12 timeslots on the IF
board of NE4.
Local Node 4 (NE ID) Planning guidelines for node

IDs:
West Node 3 (NE ID)
l The number of nodes
East Node 5 (NE ID) must not exceed 16. The
value range of a node ID
is from 0 to 15.
l In the case of a new ring
network, it is
set the node ID of the
central node to 0 and
allocate node IDs to the
other NEs
counterclockwise.
Ensure that the node ID
of an NE is the node ID
of its previous NE plus 1.
l If you add an NE to an
existing ring network, it
is recommended that you
set the node ID of the
new NE to the number
that is the maximum
number of the nodes
(including the new NE)
on the ring network
minus 1.
SD enable Enabled It is recommended that you

set SD as a switching
condition.
WTR time (s) 600 Set the wait to restore

(WTR) time to a value
between 5 minutes to 12
minutes. The default value
(10 minutes) is
recommended.

Protocol type New protocol The MSP protocols used on

a ring network must be
consistent. It is
adopt the new MSP
protocol.
NOTE
retain the default value for
Protocol Type.
West line 1 16-SL4D-1 The east and west ports of a

two-fiber bidirectional MSP
East line 1 16-SL4D-2 ring can be two STM-4
ports from system control
board. It is recommended
that the east and west ports
be ports with the same port
number from two system
control boards.
Procedure
Step 1 Configure ring MSP.

Step 2 Create cross-connections for point-to-point services.

The following table provides parameter values for NE4.
3 2
Step 3 Testing E1 Services Using PRBS

Test any two E1 services on each base station. The test results show that the E1 services
contain no bit errors.
----End

Feature Configuration Guide 4 Configuring Native Ethernet Features
4 Configuring Native Ethernet Features
About This Chapter

various Native Ethernet Features.
4.1 Configuration Process (ERPS on a Single-ring Network)

The key to configuring Ethernet ring protection switching (ERPS) for an Ethernet ring
network is creating Ethernet ring protection (ERP) instances. ERPS V1 or ERPS V2 can be
deployed on a single-ring network to protect Ethernet services. ERPS V1 is used as an
example here.
4.2 Configuration Process (ERPS on a Multi-ring Network)
network is creating Ethernet ring protection (ERP) instances. For a multi-ring network, create
ERPS V2-based instances.
4.3 Configuration Procedure (MSTP)
To use the MSTP protocol, you need to configure the port group, set the bridge parameters
and CIST parameters, and then enable the MSTP protocol.
4.4 Configuration Procedure (LAG)
When applying the LAG protocol, you need to configure the LAG and configure the priorities
of ports in the LAG as required.
4.5 Configuration Procedure (LPT)
The configuration procedure for LPT contains only one configuration task.
4.6 Configuration Process (QoS/HQoS)
Configure QoS/HQoS policies, and then apply them to QoS objects.
4.7 Configuration Process (Ethernet Service OAM)
When you use the Ethernet service OAM function, you need to define appropriate OAM
maintenance points according to the actual situation and then perform OAM operations as
required.
4.8 Configuration Procedure (Ethernet Port OAM)
When you use the Ethernet port OAM function, you can perform appropriate OAM operations
as required.

4.9 Configuration Process (Bandwidth Notification)

When bandwidth notification is used, an egress maintenance end point (MEP) that matches
the MEP on the interconnected router must be created on the microwave equipment.
4.10 Configuration Procedure (IGMP Snooping)
When the IGMP Snooping protocol is applied, you can set the static router port and the static
routing member, except for the IGMP Snooping parameters.
4.11 Configuration Example (ERPS on a Single-ring Network)
This section provides an example of how to plan and configure Ethernet ring protection
switching (ERPS) for a single-ring network based on network conditions.
4.12 Configuration Example (ERPS on a Multi-ring Network)
switching (ERPS) for a multi-ring network based on network conditions.
4.13 Configuration Example (MSTP)
This topic uses an example to describe how to plan and configure the MSTP according to the
4.14 Configuration Example (LAG)
By using an example, this topic describes how to plan and configure LAGs according to the
network conditions.
4.15 Configuration Example (LPT for Services Traversing an L2 Network)
With an example, this section describes how to plan and configure LPT according to network
conditions.
4.16 Configuration Example (LPT for Services Traversing a PSN)
conditions.
4.17 Configuration Example (QoS)
This topic uses an example to describe how to plan and configure the QoS according to the
4.18 Configuration Example (HQoS)
This section provides an example of how to plan and configure hierarchical quality of service
(HQoS) based on network conditions.
4.19 Configuration Example (Ethernet Service OAM)
This section uses an example to describe how to plan and configure the Ethernet service OAM
feature.
4.20 Configuration Example (Ethernet Port OAM)
This topic describes how to plan and configure Ethernet port OAM by using an example.
4.21 Configuration Example (Bandwidth Notification)
This section provides an example of how to plan and configure bandwidth notification based
on network conditions.
4.22 Configuration Example (IGMP Snooping)
This topic describes how to plan and configure the IGMP Snooping by using an example.

4.1 Configuration Process (ERPS on a Single-ring

Network)
network is creating Ethernet ring protection (ERP) instances. ERPS V1 or ERPS V2 can be
deployed on a single-ring network to protect Ethernet services. ERPS V1 is used as an
example here.
Table 4-1 Process of configuring ERPS

1 A.9.1.1 Required. Set parameters as follows:

Creating l Set ERPS ID, East Port, West Port, ERP Ring Node
Ethernet Ring Flag, Flag Port, and Control VLAN according to the
Protection network plan.
Instances
l When setting ERP Ring Node Flag, note the following:
– An ERP ring has only one ring protection link (RPL)
owner node.
– For an ERPS V1 protection instance, set ERP Ring
Node Flag to RPL Port for the RPL owner node on an
ERP ring and to None for other nodes on the ring.
– For an ERPS V2 protection instance, you also need to set
the neighbor port and the next neigbor port.
l Set Control VLAN to a value different from the VLAN IDs
of Ethernet service packets.
2 A.9.1.3 Setting ERPS V1-based instance required.

Protocol Set Compatible_Version to ver1.
Parameters for
an ERPS
Instance
3 A.9.1.2 Setting Required. It is recommended that you set parameters to default

Global ERPS or planned values.
Protocol
Parameters
4.2 Configuration Process (ERPS on a Multi-ring Network)

network is creating Ethernet ring protection (ERP) instances. For a multi-ring network, create
ERPS V2-based instances.

Table 4-2 Process of configuring ERPS


Creating l Set ERPS ID, East Port, West Port, ERP Ring Node
Ethernet Ring Flag, Flag Port, and Control VLAN according to the
Protection network plan.
Instances
l When setting ERP instances for a multi-ring network, note
the following:
– A major ring or sub-ring can have only one ring
protection link (RPL) owner node. A ring node adjacent
to the RPL owner node is the RPL neighbor node.
– It is recommended that you plan the counterclockwise
direction as the main direction of service transmission on
a major ring or sub-ring. For a node on the ring, set the
port that transmits services to East Port and the port that
receives services to West Port.
– A sub-ring has only an East Port or West Port on an
interconnection node. Set the non-existent East Port or
West Port to -.
– It is recommended that you set the east port on the RPL
owner node to RPL Port, the west port on the RPL
neighbor node to Neighbor Port, and the east port on the
RPL owner node's upstream node and the west port on
the RPL neighbor node's downstream node to Next
Neighbor Port.
l Set Control VLAN for a ring to a value different from the
VLAN IDs of Ethernet service packets carried by the ring.
2 A.9.1.3 Setting Required.

Protocol l If ring automatic protection switching (R-APS) virtual
Parameters for channels are required by sub-ring instance, set Virtual
an ERPS Channel Status to Enable (default) and set Virtual
Instance Channel VLANs according to the network plan. If R-APS
virtual channels are not required, set Virtual Channel
Status to Disable.
l If an interconnection node is shared by a major ring and a
sub-ring, set Major ERP Ring ID for the sub-ring
according to the network plan, so the sub-ring is associated
with the major ring.
l If an interconnection node is shared by two sub-rings, set
Major ERP Ring ID for the downstream sub-ring
according to the network plan, so the downstream sub-ring
is associated with the upstream sub-ring.

Global ERPS It is recommended that you set parameters to default or planned
Protocol values.
Parameters

4 A.9.1.4 Required when R-APS virtual channels are used.

Creating a Set parameters according to the network plan.
Virtual
NOTE
Channel VLAN
Forwarding l The control VLAN ID of an R-APS virtual channel must be
different from the VLAN IDs of the services carried by the same
Table
ERP ring.
l The control VLAN ID of an R-APS virtual channel must be
different from the control VLAN ID of the R-APS channel on the
same ERP ring.
5 A.9.1.5 Setting Optional. This operation is required when segmentation needs

Parameters for to be minimized after multiple failures occur on an ERPS-
Switching protected network.
Upon Multiple Set parameters according to the network topology and fault
Failures points.
l Set Bound MEP when the network is in the normal state.
l Modify Interconnected Node and Multi-point Failure
after multiple failures occur and restore the two parameters
to default values after faults are rectified.
NOTE
Before configuring Bound MEP, configure an ingress MEP for each
interconnection mode and enable CC tests.
4.3 Configuration Procedure (MSTP)

To use the MSTP protocol, you need to configure the port group, set the bridge parameters
and CIST parameters, and then enable the MSTP protocol.
Table 4-3 Procedure for configuring the MSTP

1 A.9.6.1 Required when you need to configure the MSTP. Set the
Creating the parameters as follows:
MSTP Port l Set Protocol Type, Board, and Selected Port according to
Group the network planning information.
l Subsequent adjustments to the MSTP parameters in the
configuration process may affect the use of the MSTP
protocol. Hence, it is recommended that you set Enable
Protocol to Disabled.
2 A.9.6.2 Setting Optional.

the Bridge Use the default value unless otherwise specified.
Parameters of
the MSTP


the Parameters Use the default value unless otherwise specified.
of the CIST
4 A.9.6.6 Required when you need to configure the MSTP. Set Enable
Enabling/ Protocol to Enabled to enable the MSTP protocol.
Disabling the
MSTP Protocol

When applying the LAG protocol, you need to configure the LAG and configure the priorities
of ports in the LAG as required.
NOTE
l The Ethernet links in a LAG are considered as one link at the data link layer. Therefore, the Ethernet port
attributes or IF_ETH port attributes of a master port are set to the same as those of a slave port.
l If a port is already configured with Ethernet services, set the port to a master port when a LAG is
configured.
l When a LAG is configured, do not set a port that is already configured with services to a slave port.
l For an Ethernet link for which a LAG is configured, configure parameters only for the main IF_ETH port.
The following operations described in this section are also applicable to the main IF_ETH port only.
Table 4-4 Process of Configuring LAG
A.9.2.1 Set the parameters as follows:

Creating a l Set LAG Type to the same value as that at the opposite end.
LAG Generally, set LAG Type to Static at both ends.
l Set Load Sharing to the same value as that at the opposite end. It is
recommended that you set Load Sharing to Non-Sharing at both
ends, if the LAG is configured only to provide protection. It is
recommended that you set Load Sharing to Sharing at both ends, if
the LAG is configured to increase the bandwidth.
l Set Revertive Mode to the same value as that at the opposite end.
Generally, set Revertive Mode to Revertive at both ends. This
parameter is valid only to LAGs whose Load Sharing is set to Non-
Sharing.
l It is recommended that the main and slave ports take the same
settings at both ends. In this case, you can set System Priority as
required. It is recommended that this parameter take its default value.
This parameter is valid only to static LAGs.
l Set Main Board, Main Port, and Selected Standby Ports according
to the network plan. It is recommended that the same main and slave
ports are used for the LAGs at both ends.

A.9.2.2 Setting Optional.

LAG It is recommended that you set Load Sharing Hash Algorithm to the
Parameters default value Automatic.
Setting the Optional.

Minimum To trigger ERPS switching upon failure of some member links in a LAG
Number of when LAG and ERPS coexist, Minimum Active Links must be set to
Active Links the total number of member links in the LAG.
For example, if Minimum Active Links is set to 2, ERPS switching is
triggered when one member link in the LAG fails.

Configuration Flow Chart

Figure 4-1 provides procedures for configuring LPT.
Figure 4-1 Configuration flow chart
Required Start
Optional
Configuring Configuring Configuring
Point-to-point Point-to- Simple
LPT Multipoint LPT
When the service LPT
network is an L2 When the service network
network is a PSN or QinQ network
Configuring Point-to- Configuring Point-to- Configuring

Configuring
Point LPT Traversing Point LPT Traversing a Point-to-
Simple LPT
an L2 Network PSN or QinQ Network Multipoint LPT
End
The procedures in the configuration flow chart are described as follows.

Table 4-5 Procedures for configuring LPT for point-to-point services

1 Configur A.9.11.1 Configuring Point-to- Required when LPT needs to be

ing Point LPT Traversing an L2 configured for point-to-point
point-to- Network services traversing an L2
point network.
LPT Set parameters according to the
service plan.
NOTE
Before configuring LPT for point-
to-point services traversing an L2
network, ensure that L2 services
have been configured. L2 services
include UNI-UNI E-Line services
and UNI-UNI E-LAN services
transmitted in a point-to-point
manner.
A.9.11.2 Configuring Point-to- Required when LPT needs to be

Point LPT Traversing a PSN configured for point-to-point
or QinQ Network services traversing a PSN or
QinQ network.
Set parameters according to the
service plan.
NOTE
l Before configuring LPT for
point-to-point services
traversing a PSN, ensure that
E-Line services carried by PWs
that exclusively occupy UNIs
have been configured.
l Before configuring LPT for
point-to-point services
traversing a QinQ network,
ensure that QinQ services
exclusively occupying UNIs
have been configured.

Table 4-6 Procedure for configuring LPT for point-to-multipoint services
1 A.9.11.3 Configuring Point-to- Required.

Multipoint LPT Set parameters according to the
service plan.
NOTE
Before configuring LPT for point-to-
multipoint services, ensure that at least
one of the following types of services has
been configured:
l L2 services
l QinQ services sharing UNIs
l E-Line services carried on PWs
sharing UNIs
Table 4-7 Procedure for configuring the Simple LPT
1 A.9.11.4 Configuring Simple LPT Required.

Set the aggregation
port and the
corresponding
access port
according to the
planning
information.
4.6 Configuration Process (QoS/HQoS)

Configure QoS/HQoS policies, and then apply them to QoS objects.
NOTE
Among OptiX RTN 900 products, only the following products support HQoS:
l OptiX RTN 950A
l OptiX RTN 950 that houses CSHU or CSHUA boards
l OptiX RTN 910A
l OptiX RTN 905 1E/2E
l OptiX RTN 980
l OptiX RTN 980L
NOTE
PW policy, QinQ policy, and V-UNI Egress policy are supported only by OptiX RTN 950A, OptiX RTN
950 (using CSHU or CSHUA boards), OptiX RTN 910A,OptiX RTN 980,OptiX RTN 980L and OptiX
RTN 905 1E/2E.

Flowchart
Figure 4-2 Flowchart for configuring QoS/HQoS

Start
Required Configure a DiffServ domain.
Optional
Create policies.
Create WRR policies.
HQoS
Create port WRED policies. Create service WRED policies.
Create V-UNI
Create port policies. Create PW policies. Create QinQ policies.
egress policies.
Apply the port policies to ports.
Apply the PW/QinQ/V-UNI

egress policies to services.
Native Ethernet service

(carried by ports) QinQ service L3VPN service
ETH PWE3 service
Outbound: UNI-NNI UNI-NNI UNI-NNI
Configure bandwidth limitation Configure bandwidth limitation Configure bandwidth limitation

Apply the V-UNI egress on MPLS tunnels. on QinQ links. on MPLS tunnels.
policies.
Configure bandwidth limitation Apply the QinQ policies.

Configure bandwidth limitation on PWs.
on V-UNI groups.
NNI-UNI
Apply the V-UNI

Apply the PW policies. egress policies.
NNI-UNI
Apply the V-UNI Configure bandwidth limitation

egress policies. on V-UNI groups.
Configure bandwidth limitation

on V-UNI groups.
End

Configuring a DiffServ Domain
Table 4-8 Configuring a DiffServ Domain

1 A.9.8.2 Preferentially use the default DiffServ domain for OptiX RTN
Modifying the equipment to reduce networkwide QoS configuration workload.
Mapping Set parameters according to the service plan.
Relationships
for the DS 1. If the mapping that is planned between the packet priority
Domain and PHB service classes for base stations or interconnected
equipment are different from the mapping that is configured
A.9.8.3 for the default DiffServ domain of OptiX RTN equipment,
Changing the change the mapping of the OptiX RTN equipment to be the
Ports Applied same as the mapping planned for the base stations or
to a DS interconnected equipment.
Domain and 2. If the packet priority type (that is, the trusted packet type)
Their Trusted supported by base stations or interconnected equipment is
Packet Types different from the trusted packet type (C-VLAN priority, by
default) for the default DiffServ domain of the OptiX RTN
equipment, change the trusted packet type of the UNI port in
the DiffServ domain that receives the Ethernet service
packets to be the same as the trusted packet type of the base
stations or interconnected equipment.
2 A.9.8.1 Required when the default DiffServ domain does not meet the
Creating a DS requirements.
Domain Set the parameters according to the service plan.
3 A.9.8.4 If you do not want the RTN transmission network to change the
Enabling/ DSCP values in packets from wireless base stations, you can
Disabling disable DSCP demapping on RTN equipment.
DSCP
Demapping at
the Egress Port
of a DiffServ
Domain
4 A.9.8.5 If you do not want the RTN transmission network to change

Enabling/ service packet priorities, you can disable PHB demapping on
Disabling RTN equipment.
Outbound
Demapping at
the Egress Port
of a DiffServ
Domain

Creating Policies
Table 4-9 Creating port policies

1 A.9.8.11 Required when the default weighted round robin (WRR)

Creating a policies do not meet the requirements.
WRR Policy
2 A.9.8.9 Required when egress port queues use the weighted random
Creating a Port early detection (WRED) algorithm. Egress port queues use the
WRED Policy tail drop algorithm by default.
3 A.9.8.6 Required when the queues at a port need to be configured with

Creating a Port the scheduling algorithm, queue shaping, and drop algorithm.
Policy
4 A.9.8.8 Required when a flow at a port requires access control list

Creating (ACL), class of service (CoS), committed access rate (CAR), or
Traffic shaping operations.
NOTE
If a flow at a port matches both DiffServ simple and complex traffic
classification rules configured for the port, complex traffic
classification takes effect.
Table 4-10 Creating PW/QinQ/V-UNI egress policies

1 A.9.8.11 Required when the default WRR policies do not meet the
Creating a requirements.
WRR Policy
2 A.9.8.10 Required when flow queues use the weighted random early
Creating a detection (WRED) algorithm. Flow queues use the tail drop
Service WRED algorithm by default.
Policy
3 A.9.8.15 Required when the flow queues on a PW need to be configured

Creating a PW with the scheduling algorithm, queue shaping, and drop
Policy algorithm.
A.9.8.16 Required when the flow queues on a QinQ link need to be

Creating a configured with the scheduling algorithm, queue shaping, and
QinQ Policy drop algorithm.
A.9.8.13 Required when the flow queues on a V-UNI need to be

Creating a V- configured with the scheduling algorithm, queue shaping, and
UNI Egress drop algorithm.
Policy

Applying Port Policies
Table 4-11 Applying port policies

1 A.9.8.12 Setting Required when you need to apply created port policies to ports.
the Port That
Uses the Port
Policy
2 A.9.8.18 Required when you need to limit the egress port bandwidth that
Configuring an Ethernet service occupies.
Port Shaping
Applying V-UNI Egress Policies to Local Ethernet Services Carried by Ports
Table 4-12 Applying V-UNI egress policies to local Ethernet services carried by ports
1 Applying V- Apply V-UNI egress policies when creating local Ethernet

UNI egress services carried by ports. Allocate bandwidths, drop policies,
policies and scheduling policies to services with different priorities such
as voice services and Internet access services.
2 A.9.8.14 Limit the bandwidth of a V-UNI group whose member ports

Creating a V- carry multiple user services at the egress UNI port to reserve
UNI Group bandwidths for other services at the port.
Applying PW Policies to ETH PWE3 Services
Table 4-13 Applying PW policies to ETH PWE3 services

1 A.9.8.19 When a tunnel carries multiple PWs, limit the bandwidth of

Configuring each PW and the bandwidth of the entire tunnel.
Bandwidth
Limitation for
MPLS Tunnels
2 A.9.8.20
Configuring
Bandwidth
Limitation for
PWs

3 Applying PW Apply PW policies in the UNI-to-NNI direction when creating

policies ETH PWE3 services. Allocate bandwidths, drop policies, and
scheduling policies to services with different priorities such as
voice services and Internet access services.
4 Applying V- Apply V-UNI egress policies in the NNI-to-UNI direction when

UNI egress creating ETH PWE3 services. Allocate bandwidths, drop
policies policies, and scheduling policies to services with different
priorities such as voice services and Internet access services.

Applying QinQ Policies to QinQ Services
Table 4-14 Applying QinQ policies to QinQ services

1 A.9.8.21 When multiple QinQ services are converged at one port, limit
Configuring the bandwidth of each QinQ service.
Bandwidth
Limitation for
QinQ Links
2 Applying QinQ Apply QinQ policies in the UNI-to-NNI direction when

policies creating QinQ services. Allocate bandwidths, drop policies, and
scheduling policies to services with different priorities such as
voice services and Internet access services.
3 Applying V- Apply V-UNI egress policies in the NNI-to-UNI direction when

UNI egress creating ETH PWE3 services. Allocate bandwidths, drop
policies policies, and scheduling policies to services with different
priorities such as voice services and Internet access services.

4.7 Configuration Process (Ethernet Service OAM)

When you use the Ethernet service OAM function, you need to define appropriate OAM
maintenance points according to the actual situation and then perform OAM operations as
required.

Table 4-15 Procedure for configuring Ethernet service OAM

1 A.9.9.1 Creating an MD Required in the case of the NE where the

Ethernet ports involved in the service test are
located. Set the parameters as follows:
l Set Maintenance Domain Name and
Maintenance Domain Level to the same
values for the NEs for which OAM operations
are performed.
l In the test of Ethernet services between two
edge nodes on the transport network, it is
recommended that Maintenance Domain
Level should take the value of 4. In the test of
Ethernet services between two NEs within the
transport network, set Maintenance Domain
Level to a value less than 4. In the test of
Ethernet services between two Ethernet ports
on the same NE, set Maintenance Domain
Level to a value less than the value that is set
in the test of Ethernet services between two
NEs within the transport network.
2 A.9.9.2 Creating an MA Required in the case of the NE where the

l Set Maintenance Domain Name to the value
of Maintenance Domain Name that is set in
the previous step.
l Set Maintenance Association Name to the
same value for the NEs for which OAM
operations are performed.
l Set Relevant Service to the same service for
the NEs for which OAM operations are
performed.
l 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.

3 A.9.9.3 Creating MEPs Required in the case of the NE where the

value of Maintenance Association Name
that is set in the previous step.
l Set Board and Port to the board and port
where the OAM operation is started or
terminated.
l Set VLAN to a VLAN. The settings of the
source and sink MEPs must be the same.
l In the same MA, the value of MP ID must be
unique.
l If the traffic flow between the MEPs that
perform the OAM operation is towards the
packet switching unit, the direction is set to
Ingress. Otherwise, the direction is set to
Egress. Generally, the ETH OAM function is
applied to end-to-end maintenance of a
certain service. Therefore, Direction is
always set to Ingress for the MPs.
l If the sink maintenance point is identified
based on the MP ID, CC Status must be set
to Active.
4 A.9.9.4 Creating Remote Required in the case of the NE where the

MEPs in an MA Ethernet ports involved in the OAM operation
are located. Set the parameters as follows:
the first step.
value of Maintenance Association Name
that is set in the second step.
l If other MEPs may initiate OAM operations
to an MEP in the same MA, set the other
MEPs to be the remote MEPs.
5 A.9.9.5 Creating MIPs Required when you need to perform LT tests and
divide the faulty part into sections.
the first step.
l Set Board and Port to the board and port
through which the Ethernet service passes.
l In the same MA, the value of MIP ID must
be unique.

6 A.9.9.6 Performing a CC Required when you need to perform a CC test.

Test
A.9.9.7 Performing an LB Required when you need to perform an LB test.

Test
A.9.9.8 Performing an LT Required when you need to perform an LT test.

Test
A.9.9.9 Activating the Required When the AIS of the maintenance point
AIS needs to be activated.
When there are multiple maintenance domain
nesting in the link, by setting AIS Active Status
and setting masked AIS Client Layer Level for
accurate location of the faulty maintenance point.
Activated AIS maintenance point After a fault
has been detected, an AIS message is sent to the
upper maintenance point to inform the
maintenance point of failure.
A.9.9.10 Monitoring Required when you need to perform an LM, DM,

Packet Loss Ratio, Delay, or VM test.
or Delay Variation of NOTE
Ethernet Services The Web LCT does not support this operation.
7 A.9.9.11 E-LAN Service Required when you need to check whether

Loopback Detection packets in an E-LAN service are looped back.
NOTE
Skip steps 1 to 6 in a service LB test.
8 A.9.9.13 Setting the Required for an NE to automatically initiate

Enabling Status of service loopback detection.
Automatic Service Loop
Detection for NEs

When you use the Ethernet port OAM function, you can perform appropriate OAM operations
as required.
Table 4-16 Procedure for configuring Ethernet port OAM

1 Enabling OAM Auto- Required. Set the parameters as follows:

Discovery l Set Enable OAM Protocol to Enabled.
l Set OAM Working Mode to Active for the NE that
starts the discovery.

2 Link A.9.10.2 Optional.

Performanc Enabling Set Link Event Notification to Enabled if the opposite
e the Link NE needs to be informed of the faults or performance
Monitoring Event events that are detected.
Notificat
ion
A.9.10.3 Optional.
Modifyin You can perform this operation when you need to adjust
g the the thresholds of the performance events.
OAM
Error
Frame
Monitori
ng
Threshol
d
Remote A.9.10.4 Optional.

Loopback Performi Set Remote Side Loopback Response to Enabled
ng when you need to perform a remote loopback operation.
Remote
Loopbac
ks
3 Local A.9.10.5 Optional.

loopback Enabling Set Loopback Check to Enabled when you need to
detection Self- perform local loopback detection for the ports.
Loop
NOTE
Detectio Skip steps 1 and 2 in local loopback detection.
n
4.9 Configuration Process (Bandwidth Notification)

When bandwidth notification is used, an egress maintenance end point (MEP) that matches
the MEP on the interconnected router must be created on the microwave equipment.
Table 4-17 Process of configuring bandwidth notification

1 A.9.9.1 Creating an Required. Set parameters as follows:

MD l Set the Maintenance Domain Name and
Maintenance Domain Level consistently on the
microwave equipment and interconnected router.

2 A.9.9.2 Creating an Required. Set parameters as follows:

MA l Set Maintenance Domain Name to the
Maintenance Domain Name configured in step 1.
l Set Maintenance Association Name consistently
on the microwave equipment and interconnected
router.
l Set Protocol/Standard to Y.1731.
3 A.9.9.3 Creating Required. Set parameters as follows:

MEPs l Set Maintenance Association Name to the
Maintenance Association Name configured in
step 2.
l Set Port to a microwave port or the master port in
an S-EPLA group.
l Set VLAN to the VLAN ID configured on the
interconnected router.
l Set MP ID to a unique value in a maintenance
association (MA).
l Set Direction to Egress.
4 A.9.9.14 Configuring Required. Set parameters as follows:

Bandwidth l Set Advertisement to Enable.
Notification
l Set Client Layer Level to be the same as that of
the MEP on the router, which is higher than or
equal to that of the local MEP.

When the IGMP Snooping protocol is applied, you can set the static router port and the static
routing member, except for the IGMP Snooping parameters.
Table 4-18 Procedure for Configuring the IGMP Snooping

1 A.9.7.1 Configuring the IGMP Required.

Snooping Protocol After IGMP Snooping is enabled,
the parameters need to be set
according to the service planning.
It is recommended that you use
the default values.

2 A.9.7.4 Creating Static Router Ports Optional.

If a routing port need not be aged,
you can configure the port as a
static routing port.
3 A.9.7.5 Creating a Member of a Optional.

Static Multicast Group If a multicast member need not
be aged, you can configure the
port as a static multicast group
member.
4 A.9.7.6 Adding a Quickly Deleted Optional.

Port If only one receiver of the
multicast service is connected to
the multicast member port, you
can set the fast leave function for
the member port. After receiving
the leave packets, the member
port is deleted immediately and
does not forward the query
packet.
NOTE
OptiX RTN 950 using CSH boards, OptiX RTN 980, OptiX RTN 980L, OptiX RTN 910A and OptiX RTN
905 support IGMP Snooping.
4.11 Configuration Example (ERPS on a Single-ring

Network)
switching (ERPS) for a single-ring network based on network conditions.

As shown in Figure 4-3, NE1, NE2, NE3, and NE4 construct a Hybrid microwave ring
network. The ERPS is configured to protect the Ethernet services on the ring network.
Generally, when a Hybrid microwave ring network is configured with the ERPS, the RPL
owner node (NE3) blocks the east RPL ports and all the services are transmitted through west
RPL ports. If a link on the ring network fails or an NE on the ring network becomes faulty,
NE3 enables the blocked east RPL ports so that the services can be transmitted through these
east RPL ports.


Hybrid IF board (E):
3-ISU2
Hybrid IF board (W):
4-ISU2
E W
ETH
NE1
BSC
E
ETH W RPL ETH
ERPS
NE2 E NE4 BTS4
BTS1 W
Hybrid IF board (E): Hybrid IF board (E):

3-ISU2 RPL Port
3-ISU2
Hybrid IF board (W)： ETH Hybrid IF board (W):
4-ISU2 W E 4-ISU2
NE3
BTS3

3-ISU2
Bloked port
4-ISU2
RPL Owner

During the configuration, all other Ethernet ring protection switching (ERPS) parameters take
default values except the parameters whose values are already specified in the plan.
Data Preparation
Table 4-19 ERPS plan

ERPS ID is 1. For details about -

ERP instance parameters other parameters, see Figure 4-4.

Protocol version ver1 l ERPS V1 or ERPS V2 can be

deployed on a single-ring
network to protect Ethernet
services. ERPS V1 is used as an
example here.
l If an ERPS V2-based instance
needs to be configured for a
single-ring network, specify the
neighbor port and next neighbor
port.
Hold-off time (ms) 0 Set this parameter according to the

plan. Generally, the default value is
recommended.
Guard time (ms) 500 Set this parameter according to the

recommended.
WTR time (min) 5 l Set this parameter according to

the plan. Generally, the default
value is recommended.
l Set this parameter only for an
RPL owner.
Packet transmit interval (s) 5 Set this parameter according to the

recommended.

Figure 4-4 Parameters for configuring ERP instances

3-ISU2
4-ISU2
E W
ETH
NE1
BSC
E
ETH W RPL ETH
ERPS
NE2 E NE4 BTS4
BTS1 W
Hybrid IF board (E): Hybrid IF board (E):

3-ISU2 RPL Port
3-ISU2
Hybrid IF board (W)： ETH Hybrid IF board (W):
4-ISU2 W E 4-ISU2
NE3
BTS3

3-ISU2
Bloked port
4-ISU2
RPL Owner
Procedure
Step 1 Create ERP instances.

NOTE
When configuring ERP Ring Node Flag, only one RPL port must be configured on a ring.
Step 2 Set the protocol version.

Step 3 Set global ERPS protocol parameters.


----End
4.12 Configuration Example (ERPS on a Multi-ring

Network)
switching (ERPS) for a multi-ring network based on network conditions.

As shown in Figure 4-5, NE 1, NE 2, NE 3, NE 4, NE 5, and NE 6 constitute an Integrated IP
microwave multi-ring network. Ethernet ring protection switching (ERPS) V2 is configured to
protect Ethernet services carried on the network.
Service transmission on the network is expected as follows:
l When the major ring is in the normal state, the ring protection link (RPL) owner node
(NE 4) blocks its RPL port (east port), and the RPL neighbor node (NE 1) blocks its RPL
neighbor port (west port). All services are transmitted along the path NE 1 -> NE 2 ->
NE 3 -> NE 4. When a link or an NE on the major ring fails, NE 4 unblocks its RPL port
and NE 1 unblocks its RPL neighbor port, so services can be transmitted over the link
between NE 1 and NE 4.
l When the sub-ring is in the normal state, the RPL owner node (NE 6) blocks its RPL
port (east port), and the RPL neighbor node (NE 5) blocks its RPL neighbor port (west
port). All services are transmitted over the link between NE 2 and NE 6 and the link
between NE 3 and NE 5. When a link or an NE on the sub-ring fails, NE 6 unblocks its
RPL port and NE 5 unblocks its RPL neighbor port, so services can be transmitted over
the link between NE 5 and NE 6. Note that the interconnection node NE 2 has only an
east port on the sub-ring, and the interconnection node NE 3 has only a west port on the
sub-ring.

In addition, the following requirements must be met:

l A ring automatic protection switching (R-APS) virtual channel is deployed on the major
ring.
l The ring network uses the revertive mode.
Figure 4-5 Networking diagram for ERPS
RPL neighbor node RPL Owner
3-ISU2 (E) 3-ISU2 (E, RPL port)
4-ISU2 (W, Neighbor port) 4-ISU2 (W)
NE1 NE4
Major ring 3-ISU2 (E, Major ring port,

3-ISU2 (E, Major ring port)
Next neighbor port)
4-ISU2 (W, Major ring port,
4-ISU2 (W, Major ring port)
Next neighbor port)
5-ISU2 (E, Sub-ring port, Next 5-ISU2 (W, Sub-ring port,
neighbor port) next neighbor port)
NE2 NE3
Sub-ring RPL neighbor node

RPL owner
3-ISU2 (E, RPL port) 3-ISU2 (E, Neighbor port)
4-ISU2 (W) 4-ISU2 (W)
NE6 NE5
Blocked port
Ring link
Ring link (blocked)
Ethernet service direction

This section describes the procedure for configuring Ethernet ring protection switching
(ERPS).

Data Preparation
Table 4-20 ERPS plan

l ERPS ID of the major ring: 1; l A major ring or sub-ring can

ERPS ID of the sub-ring: 2 have only one RPL owner node.
l Control VLAN: 4093 The ring node adjacent to the
RPL owner node is an RPL
l For details about the other neighbor node. It is
parameters, see Figure 4-6. recommended that you
configure the east port on the
RPL owner node as the RPL
port and configure the west port
on the RPL neighbor node as
the RPL neighbor port. It is also
recommended that you, along
the anti-clockwise direction,
configure the east port on the
RPL owner node's upstream
node and the west port on the
RPL neighbor node's
downstream node as RPL next
neighbor ports.
l Plan control VLAN IDs for R-
APS channels on both major
rings and sub-rings. The control
VLAN IDs must differ from
Ethernet service VLAN IDs on
the ERP ring. All ring nodes on
an ERP ring must use the same
control VLAN ID. It is
recommended that you use the
same control VLAN ID for R-
APS channels on all ERP rings
ERP instance parameters of a ring network.
Protocol version ver2 ERPS V2 is deployed to protect

Ethernet services on interconnected
rings.
Hold-off time (ms) 0 Set this parameter according to the

recommended.
Guard time (ms) 500 Set this parameter according to the

recommended.

WTR time (min) In this example, ERPS is set to l Plan the ERPS reversion mode
revertive. The WTR time is set to as required. Generally, the
the default value 5 minutes for default value is recommended.
NE4 and NE6. l Set this parameter only for an
RPL owner.
Packet transmit interval (s) 5 Set this parameter according to the

recommended.
Virtual channel parameters l Virtual-channel VLAN for all l R-APS virtual channels must be
NEs: 4092 enabled on the two
l For NE2 and NE3: virtual interconnection nodes of the
channel status: enabled; major sub-ring.
ERPS ring ID: 1 l The control VLAN ID of an R-
l Virtual channel VLAN APS virtual channel must differ
forwarding table configured for from the VLAN IDs of the
NE2 and NE3: as planned in services carried on the same
Table 4-21 ring.
l The control VLAN ID of an R-
APS virtual channel must differ
from the control VLAN ID of
the R-APS channel on the same
ring.
l A VLAN switching table for R-
APS virtual channels must be
configured on the two
interconnection nodes shared by
a major ring and a sub-ring.

Figure 4-6 Parameters for configuring ERP instances
RPL neighbor node RPL Owner
3-ISU2 (E) 3-ISU2 (E, RPL port)
4-ISU2 (W, Neighbor port) 4-ISU2 (W)
NE1 NE4
Major ring 3-ISU2 (E, Major ring port,

3-ISU2 (E, Major ring port)
Next neighbor port)
4-ISU2 (W, Major ring port,
4-ISU2 (W, Major ring port)
Next neighbor port)
5-ISU2 (E, Sub-ring port, Next 5-ISU2 (W, Sub-ring port,
neighbor port) next neighbor port)
NE2 NE3
Sub-ring RPL neighbor node

RPL owner
3-ISU2 (E, RPL port) 3-ISU2 (E, Neighbor port)
4-ISU2 (W) 4-ISU2 (W)
NE6 NE5
Blocked port
Ring link
Ring link (blocked)
Ethernet service direction
Table 4-21 Parameters for configuring a VLAN switching table for R-APS virtual channels
Parameter NE2 NE3
ERPS ID 2 2
Virtual channel VLANs 4093 4093
Major ERPS ring ID 1 1
Virtual channel VLAN on 4092 4092

major ring
NOTE
Set Virtual Channel VLANs to the control VLAN ID for R-APS channels on the sub-ring. Set Virtual
Channel VLANs on the major ring to the Virtual Channel VLANs for the interconnection node.
Procedure
Step 1 Create ERP instances.

Create ERP instances for NE1, NE2, NE3, and NE4 on the major ring and for NE2, NE3,
NE5 and NE6 on the sub-ring. NE1 is used as an example.
Step 2 Set the protocol version.

NE1 on the major ring is used as an example.
Step 3 Set global ERPS protocol parameters.

NE1 on the major ring is used as an example.

Step 4 Create a VLAN switching table for R-APS virtual channels for NE2 and NE3.
4
2
----End
4.13 Configuration Example (MSTP)

This topic uses an example to describe how to plan and configure the MSTP according to the

As shown in Figure 4-7, NE1 is the RTN 900, and LAN switch 1 and LAN switch 2 are two
Ethernet switches that run the MSTP protocola.
l The Ethernet port on LAN switch 1 is connected to port 1 on the EM6T board in slot 2 of
NE1.

l The Ethernet port on LAN switch 2 is connected to port 2 on the EM6T board in slot 2 of
NE1.
After the port group is configured for NE1, NE1 runs the MSTP protocol together with LAN
switch 1 and LAN switch 2 on the access side, considering LAN switch 1 as the root. In this
manner, no loops will be generated on the network on the access side and thus the protection
for the network is realized.
NOTE
a: The RTN 900 supports only the MSTP that generates the CIST.
ETH
LAN Swich 1 NodeB
Root
NE1
ETH
NodeB
RNC
LAN Swich 2
ETH
Port group NodeB

To use the Multiple Spanning Tree Protocol (MSTP), you need to create a port group, set
bridge and CIST parameters, and enable MSTP.
Data Preparation
Table 4-22 MSTP plan
l Protocol type: MSTP It is recommended that you disable

l Enable protocol: enabled the protocol when creating an
MSTP port group and that you
l Member ports: 2-EM6T-1 and enable the protocol after all the
2-EM6T-2 MSTP parameters are set. In this
manner, the possible impact on the
MSTP protocol are prevented in
the case of adjustments to the
Port group parameters MSTP parameters.

Bridge parameters All parameters take the default Set the bridge parameters based on
values. the requirements of the user-side
equipment. Generally, default
values are recommended.
CIST parameters Change the path overhead to Set the CIST parameters based on
200000. the requirements of the user-side
equipment. Generally, default
Procedure
Step 1 On NE1, create an MSTP port group.
The values for the MSTP port group parameters are provided as follows.
Step 2 Set MSTP bridge parameters.

Step 3 Set CIST parameters.
Step 4 Enable the MSTP protocol.

----End

By using an example, this topic describes how to plan and configure LAGs according to the
network conditions.

As shown in Figure 4-8, the Hybrid radio link between NE1 and NE2 adopts the 2+0 non-
protection scheme. Hence, the Integrated IP microwave ports that correspond to the radio link
need to be configured as a load-sharing LAG.
Link 1
Link 2
NE1 NE2
LAG
Standby port: 4-ISU2-1 Standby port: 4-ISU2-1

This section describes the procedure for configuring link aggregation groups (LAGs).

Data Preparation
Table 4-23 LAG plan

Static (default value) Configure the same aggregation

type at both ends. Static
LAG type aggregation is recommended.
Load sharing mode Sharing Configure the same load sharing

mode at both ends. Configure a
load non-sharing LAG to provide
protection, and a load sharing LAG
to increase bandwidth.
Load sharing hash algorithm auto (default value) The automatic load sharing hash
algorithm is recommended.
l If the OptiX RTN 900 and
OptiX equipment are
interconnected to form a load
non-sharing LAG, it is
recommended that the LAG be
set to revertive and the WTR
time take the default value.
l If the OptiX RTN 900 and
another type of equipment are
interconnected to form a load
non-sharing LAG, it is
recommended that the LAG be
set to non-revertive.
System priority 32768 (default value) The default value is recommended.

The system priority can be set only
in static aggregation.
Master and slave ports l Master port: 3-ISU2-1 It is recommended that you set the
l Slave port: 4-ISU2-1 main and slave ports consistently
for the equipment at both ends.
Minimum number of active links 2 To trigger switching upon failure

of a member link in a LAG when
LAG exists with other types of
protection, set the minimum
number of active links to the total
number of links in the LAG.
Switching upon air interface SD Enable It is recommended that you enable

this function when a LAG is
configured at air interfaces.

Procedure
Step 1 Create LAGs.
Step 2 Set LAG parameters.

----End

4.15 Configuration Example (LPT for Services Traversing

an L2 Network)
conditions.
4.15.1 Network Diagram

On the network as shown in Figure 4-9, NE1, NE2, and NE3 transmit services between
routers through VLAN-based E-Lines. When faults occur on the network between NE1 and
NE2 and the network between NE1 and NE3, NE1, NE2, and NE3 need to disconnect their
access links to instruct router A, router B, and router C respectively to start a backup network
for uninterrupted communication. Therefore, point-to-multipoint LPT needs to be configured
on NE1, and point-to-point LPT needs to be configured on NE2 and NE3.
Figure 4-9 Network diagram of LPT (traversing an L2 network)

4-EM6T-1 (to Router B)
4-EM6T-1 (to Router A)
1-ISU2-1 (to NE2) 1-ISU2-1 (to NE1)
2-ISU2-1 (to NE3) VLAN:100
VLAN:100, 200
NE2 Router B
Router A
NE1
VLAN:200
NE3 Router C
4-EM6T-1 (to Router C)

1-ISU2-1 (to NE1)

This section describes the procedure for configuring link state pass through (LPT).

Data Preparation
Table 4-24 LPT plan

Point-to-multipoint LPT NE1 functions as the primary point l Plan point-to-point LPT for a
configuration for NE1 of the point-to-multipoint LPT, and point-to-point network
the primary point resides on the topology. Plan point-to-
UNI port 4-EM6T-1. multipoint LPT for a point-to-
Secondary LPT point 1 (NE1 to multipoint network topology.
NE2) l Allocate a unique L2 net ID to
l Packet out port: 1-ISU2 each LPT function point on the
network side.
l L2 net ID: 11
l The LPT packets sent from L2
l VLAN ID: 100
network-side ports can carry
Secondary LPT point 2 (NE1 to VLAN IDs.
NE3)
– If the L2 network transmits
l Packet out port: 2-ISU2 packets based on VLAN
l L2 net ID: 12 IDs, set the VLAN ID of the
l VLAN ID: 100 LPT packets the same as the
service VLAN ID. This
Point-to-point LPT configuration l L2 net ID: 21 ensures that LPT packets are
for NE2 l VLAN ID carried by LPT transmitted along the service
packets: 100 path.
– If the L2 network does not
Point-to-point LPT configuration l L2 net ID: 31 transmit packets based on
for NE3 l VLAN ID carried by LPT VLAN IDs, setting VLAN
packets: 200 IDs for LPT packets is not
required.

LPT parameters All parameters take default values. l Set the LPT switching mode for
point-to-multipoint LPT. LPT
switching is generally set to the
strict mode, which means that
LPT switching is triggered
when all secondary points
detect faults. If LPT switching
is set to the non-strict mode,
when any of the secondary
points detects a fault.
l Set the WTR time and hold-off
time according to the actual
requirement. Generally, default
l Set the fault detection period of
LPT OAM according to the
actual requirement. A shorter
detection period indicates
shorter LPT switching time but
requires more resources.
Procedure
Step 1 Configure point-to-multipoint LPT for NE1.

1
3
Step 2 Configure point-to-point LPT that traverses the L2 network for NE2 and NE3.

----End
4.16 Configuration Example (LPT for Services Traversing a

PSN)
conditions.

On the network as shown in Figure 4-10, NE1, NE2, and NE3 transmit E-line services carried
by VLAN-based PWs. When faults occur on the network between NE1 and NE2 and the
network between NE1 and NE3, NE1, NE2, and NE3 need to disconnect their access links to
instruct router A, router B, and router C respectively to start a backup network for
uninterrupted communication. Since E-line services carried by VLAN-based PWs share UNI
ports, point-to-multipoint LPT needs to be configured on NE1, NE2, and NE3.

Figure 4-10 Network diagram of LPT (traversing a PSN)

4-EM6T-1 (to Router B
4-EM6T-1 (to Router A VLAN:100
VLAN:100,200 PW ID: 101
NE2 Router B
PSN
VLAN:200
Router A NE1 PW ID: 102
NE3 Router C
4-EM6T-1 (to Router C

This section describes the procedure for configuring link state pass through (LPT).
Data Preparation
Table 4-25 LPT plan

The primary LPT point is a UNI l Plan the LPT type based on the
port 4-EM6T-1. service type. Plan point-to-point
l The secondary LPT point 1 is a LPT for services that
PW, with an ID of 101. exclusively occupy UNI ports
and point-to-multipoint LPT for
Point-to-multipoint LPT l The secondary LPT point 2 is a services that share UNI ports.
configuration for NE1 PW, with an ID of 102.
l LPT must be bound to specific
Point-to-multipoint LPT l The primary LPT point is a ETH PWE3 services.
configuration for NE2 UNI port 4-EM6T-1.
l The secondary LPT point 1 is a
PW, with an ID of 101.
Point-to-multipoint LPT l The primary LPT point is a

configuration for NE3 UNI port 4-EM6T-1.
l The secondary LPT point 1 is a
PW, with an ID of 102.

LPT parameters All parameters take default values. l Set the LPT switching mode for
point-to-multipoint LPT. LPT
switching is generally set to the
strict mode, which means that
when all secondary points
detect faults. If LPT switching
is set to the non-strict mode,
when any of the secondary
points detects a fault.
l The shortest detection period of
LPT OAM is 1000 ms. If a
shorter detection period is
required, configure PW OAM
according to the plan.
l For ETH PWE3 services that
are carried over MS-PWs, PW
OAM must be configured to
check the service network.
Procedure
Step 1 Configure point-to-multipoint LPT for NE1, NE2, and NE3.

----End

This topic uses an example to describe how to plan and configure the QoS according to the

The packet microwave network shown in Figure 4-11 has the following quality of service
(QoS) requirements:
l Different types of Ethernet services, including the VoIP service, video service, and data
service, on NodeB 33 and NodeB 31 have different differentiated services code point
(DSCP) values.
l On the packet microwave network, Ethernet services require end-to-end QoS
management based on the DSCP values planned on the NodeB side.

Figure 4-11 Networking diagram for QoS

To NE33:3-ISV3-1
To NodeB33:7-EG6-1
To NE34:3-ISV3-1
NodeB33 NE34 To NE32:4-ISV3-1
To NE33:3-ISV3-1
VLAN 330 To NE31:4-EG4-2
NE33
To NodeB31:4-EG4-1 To NE32:4-EG4-1
FE To RNC:4-EG4-2
RNC
NE32 NE31
GE GE
NodeB31
RTN 905 VLAN 310
FE
RTN 950
RTN 980

This section describes the procedure for configuring quality of service (QoS).
Data Preparation
Table 4-26 QoS plan

l In this example, the mapping l During the mapping from

defined for the default DiffServ DSCP values to PHBs, using
domain is used. For details, see CS7/CS6 is not recommended,
Figure 4-12. because CS7/CS6 may be used
l Change the type of packets to transmit Ethernet protocol
trusted by the ports in the packets or inband DCN packets
DiffServ domain to DSCP, between NEs.
because these ports trust l If the mapping defined for the
packets with DSCP values, default DiffServ domain meets
instead of packets with C- requirements, creating another
VLAN priorities. DiffServ domain is not
required. This minimizes the
workload for configuring
network-wide QoS.
l The same DiffServ
configuration is applied to all
DiffServ ports involved in the service.

Queue scheduling policy Figure 4-12 shows the queue —

scheduling policies for the Ethernet
ports and microwave ports
involved in the service and their
respective weights.
Congestion management mode Figure 4-12 shows the congestion —

management modes used by the
Ethernet ports and microwave ports
involved in the service.
Port WRED policy In this example, the port WRED —

policy has an ID of 3 and is named
Port_WRED. For details, see
Figure 4-12.
Figure 4-12 QoS plan

DiffServ
Ingress Egress
Service
DSCP PHB DSCP
Type
VoIP 40 EF 40
Video 32 AF41 32
Queue scheduling policy
Data 16 AF21 16
SP
SP
SP
WRR (weight = 5)
Egress queues WRR (weight = 60)
Bandwidth WRR (weight = 30)
NodeB DSCP CS7
Limit CS6 WRR (weight = 5)
VoIP 40 20 Mbit/s EF SP
Video 32 30 Mbit/s AF4
AF3
Data 16 30 Mbit/s AF2
AF1 Upper Drop Lower Drop Drop
BE Color Threshold Threshold Probability
WRED (256 Bytes) (256 Bytes) (%)
WRED
Green 460 400 10
WRED Yellow 64 32 100
Congestion
Red 64 32 100
management
Port WRED policy
Procedure
Step 1 Specify the ports to which the DiffServ domain is applied and the type of packets trusted by
the ports.
1. Query the mapping of the default DiffServ domain for each NE. Retain the default
values.
NOTE
In this example, the mapping between the trusted packet type (DSCP) and the PHB planned for NodeBs
is the same as the mapping defined for the default DiffServ domain of the OptiX RTN equipment.
Therefore, the default DiffServ domain is used.

2. Set the type of packets trusted by the ports carrying Ethernet services to DSCP for each
NE.

Step 2 Create a new WRR policy for each NE.

Step 3 Create a new port WRED policy for each NE.
Step 4 Create a new port policy for each NE.


Step 5 Set the port to which the port policy is applied for each NE.
----End
4.18 Configuration Example (HQoS)

This section provides an example of how to plan and configure hierarchical quality of service
(HQoS) based on network conditions.

Two users' services need to be separated from each other and have their bandwidths
guaranteed. Each user's services need to be identified by type. Each type of service requires
bandwidth guarantee and service forwording priority.
The packet microwave network shown in Figure 4-13 has the following quality of service
(QoS) requirements:

l Ethernet services of NodeB1 and NodeB2 are carried over MPLS/PWE3. The two
services need to be separated from each other and have their bandwidths guaranteed.
l Different services including VoIP, video, and data services of the same NodeB are
identified by VLAN priority values. Each service requires a committed bandwidth.

Service of NodeB1 Required Bandwidth VLAN Priority Value CoS
VoIP 20 Mbit/s 5 EF
Video 30 Mbit/s 4 AF4
Data 30 Mbit/s 2 AF2
PSN
NodeB1
VLAN 100 PW1
PW2
NE1 LSP NE2 RNC
UNI NNI NNI UNI
NodeB2 To NE2: ISV3-1 To NE1: ISV3-1

VLAN 200 To NodeB1: EG4-1 To RNC: EG4-1
To NodeB2: EG4-2
Service of NodeB2 Required Bandwidth VLAN Priority Value CoS
VoIP 20 Mbit/s 5 EF
RTN 950A or RTN 950
Video 25 Mbit/s 4 AF4
Data 25 Mbit/s 2 AF2

This section describes the procedure for configuring hierarchical quality of service (HQoS).
Data Preparation
DiffServ mapping Use the default DiffServ If the default DiffServ

mapping. The default mapping meets the
DiffServ domain contains requirements, a new
the UNI and NNI ports in DiffServ domain is not
Figure 4-14. required and consequently
Set the UNI and NNI ports networkwide QoS
so the UNI ports trust C- configuration workload is
VLAN priority values and reduced.
the NNI ports trust MPLS
EXP values.

Bandwidth limitation on See Figure 4-14. Different types of services

flow queues on a PW of the same NodeB have
their bandwidths guaranteed
using bandwidth limitation
on PW flows.
PW bandwidth limitation Services of NodeB1 (PW1): The bandwidth of each

80 Mbit/s NodeB is guaranteed using
Services of NodeB2 (PW2): PW bandwidth limitation.
70 Mbit/s
Queue scheduling policy Figure 4-15 shows the —

queue scheduling policies
for the Ethernet ports and
microwave ports involved in
the service and their
respective weights.
Congestion avoidance In this example, the service —

WRED policy for PW flow
queues has an ID of 3 and is
named PW_WRED. For
details, see Figure 4-15

Figure 4-14 DiffServ mapping and PW bandwidth limitation

DiffServ
UNI NNI
VLAN MPLS
Service Type PHB
Priority Value EXP Value
VoIP 5 EF 5
Video 4 AF41 4
Data 2 AF21 2
NodeB1
VLAN 100
PSN
PW1
PW2
NE1 LSP
NE2 RNC
UNI NNI NNI UNI
NodeB2
VLAN 200 PW2 queues
VLAN Priority Bandwidth
NodeB2 VLAN ID CS7
Value Limitation Bandwidth limitation on
CS6 PW2: 70 Mbit/s
VoIP 200 5 20 Mbit/s EF
25 Mbit/s AF4 PW
Video 200 4
AF3
Data 200 2 25 Mbit/s AF2
AF1
BE
PW1 queues
VLAN Priority Bandwidth

NodeB1 VLAN ID CS7
Value Limitation Bandwidth limitation on
CS6 PW1: 80 Mbit/s
VoIP 100 5 20 Mbit/s EF
AF4 PW
Video 100 4 30 Mbit/s
AF3
Data 100 2 30 Mbit/s AF2
AF1
BE

Figure 4-15 Queue scheduling policy and congestion avoidance

Queue scheduling policy
SP
SP
SP
WRR (weight = 20)
PW1/PW2 queues WRR (weight = 20)
CS7 WRR (weight = 40)
CS6 WRR (weight = 20)
EF SP
AF4
AF3
AF2
AF1 Upper Drop Lower Drop Drop
BE Color Threshold Threshold Probability
WRED (256 Bytes) (256 Bytes) (%)
WRED
Green 460 400 10
WRED Yellow 64 32 100
Congestion
Red 64 32 100
avoidance
Service WRED policy
Procedure
Step 1 Configure a DiffServ domain.
1. Query the default DiffServ mapping of NE1 and NE2 to ensure that the default values
are the same as the planned values.
The mapping in the egress direction is as follows.

NOTE
The default DiffServ mapping complies with the network planning requirements and therefore does not
need to be modified.
2. Modify the configuration of the NNI ports carrying ETH PWE3 services in the default
DiffServ domain on NE1 and NE2 so they trust MPLS EXP values.

NOTE
The UNI ports that trust C-VLAN priority values by default do not need to be modified.
Step 2 Create a new WRR policy for each NE.
Step 3 Create a service WRED policy for each NE.
Step 4 Create PW policeies for each NE.
The screenshot shows the policy for PW1. The policy for PW2 is created in the same way.

Step 5 Apply the new PW policies to the ETH PWE3 services and set the PW bandwidth limitation.
The screenshot shows applying the policy for PW1. The policy for PW2 is applied in the
same way.
----End

This section uses an example to describe how to plan and configure the Ethernet service OAM
feature.

Figure 4-16 shows a radio network that transmits Ethernet services for base station
backhauls. The network is divided into VLANs. VLANs 100 to 109 process the traffic of
NodeB A, and VLANs 110 to 119 process the traffic of NodeB B. After faults occur in VLAN
100 and VLAN 110, LT tests should be performed to identify the faults.

l On NE1, the service from NodeB A to NE2 is named NodeAtoNE2_Vline, with an ID of

1. Whereas the service from NodeB B to NE2 is named NodeBtoNE2_Vline, with an ID
of 2.
l ON NE2, the Ethernet service from NE1 to NE3 is named NE1toNE3_Vline, with an ID
of 1.
l On NE3, the Ethernet service from NE2 to the RNC is named NodeBtoRNC_Vline, with
an ID of 1.
Figure 4-16 Networking diagram of the Ethernet service OAM

NodeB A
VLAN 100-109
4-ISU2-1(to NE2)
1-EM6T-1(to NodeB A) 4-ISU2-1(to NE3) 4-ISU2-1(to NE2)
3-ISU2-1(to NE1) 1-EM6T-1(to RNC)
1-EM6T-5(to NodeB B)
NE 1 NE 2 NE 3 RNC
NodeB B
VLAN 110-119 Ethernet link Radio link

This section describes the procedure for configuring OAM.
Data Preparation
Table 4-27 OAM plan

For details about values of the -

maintenance domain, maintenance
association, and maintenance point
OAM parameters (MP), see Figure 4-17.
LT test parameters In this example, an LT test is used

to verify the OAM.
Other parameters All parameters take the default

values.

Figure 4-17 Parameters for configuring OAM

MA1
1-EM6T-1 4-ISU2-1 3-ISU2-1 4-ISU2-1 4-ISU2-1 1-EM6T-1
VLAN100
MEP1 MIP5 MIP6 MIP7 MIP8 MEP2
MA2
1-EM6T-5 4-ISU2-1 3-ISU2-1 4-ISU2-1 4-ISU2-1 1-EM6T-1
VLAN110
MEP3 MIP5 MIP6 MIP7 MIP8 MEP4
Procedure
Step 1 Create a maintenance domain containing NE1, NE2, and NE3.

Step 2 Create a maintenance association containing NE1 and NE3.

2
6
Step 3 Create maintenance association end points (MEPs) on NE1 and NE3.

Step 4 Create remote MEPs on NE1 and NE3.

MEP1 on NE1 is used as an example.

Step 5 Create maintenance association intermediate points (MIPs) on NE1, NE2, and NE3.
MIP5 on NE1 is used as an example.

Step 6 On NE1, perform LT tests for the service from NodeB A to the RNC and the service from
NodeB B to the RNC.

In normal cases, all the MPs on the link under an LT test respond to LTM frames. If any fault
occurs, locate the fault based on the test result.
----End

This topic describes how to plan and configure Ethernet port OAM by using an example.

The application of the Ethernet port OAM function does not focus on specific services.
Instead, the application of the Ethernet port OAM function focuses on the maintenance of the
point-to-point Ethernet link between two sets of equipment that are directly connected to each
other. When the equipment supports the Ethernet port OAM protocol, the OAM auto-
discovery is performed if the Ethernet port OAM protocol is enabled on two ports that are
connected to each other. If the OAM auto-discovery is successful, you can perform OAM
operations as required.
As shown in Figure 4-18, you can enable the Ethernet port OAM protocol if you need to
monitor the performance over the Ethernet link between NE1 and NE2, which are connected
directly to each other.
Figure 4-18 Networking diagram of the Ethernet port OAM
Ethernet port
OAM
1-EM6T-1 (to NE2) 1-EM6T-1 (to NE1)
NE3 NE1 NE2 NE4
Client Ethernet equipment
Microwave equipment

This section describes the procedure for configuring OAM.

Data Preparation
Table 4-28 OAM plan

Enable OAM auto-discovery for l Only the end in active mode

NE1 and NE2 and set the working can initiate an auto-discovery or
mode to active. a remote loopback. The OAM
modes can be set to active at
both ends, or active at one end
and passive at the other end.
Note that the OAM modes
cannot be set to passive at both
ends.
l You do no need to enable OAM
auto-discovery in a local
OAM auto-discovery loopback detection test.
OAM operation In this example, the link The OAM error frame monitoring
performance monitoring function is threshold is a standard for OAM to
used to monitor bit errors on the check the link performance.
link. The window values and Generally, the default value is
threshold values for link used. You can modify the value
performance events take default according to the actual link status.
values.
Procedure
Step 1 Enable OAM auto-discovery for 1-EM6T-1 of NE1 and 1-EM6T-1 of NE2.

Step 2 Enable link event notification for 1-EM6T-1 of NE1 and 1-EM6T-1 of NE2.
Step 3 Configure the OAM error frame monitoring threshold for 1-EM6T-1 of NE1 and 1-EM6T-1 of
NE2.

----End
4.21 Configuration Example (Bandwidth Notification)

This section provides an example of how to plan and configure bandwidth notification based
on network conditions.

l A microwave link is configured between NE1 and NE2. NE2 is connected to a router.
l Bandwidth notification needs to be configured so that the router can be informed of air
interface bandwidth changes and perform the QoS function accordingly.
Figure 4-19 Networking diagram for bandwidth notification

This section describes the procedure for configuring bandwidth notification.

Data Preparation
Table 4-29 Data plan
Item Parameter Value
MD configuration Maintenance Domain Name MD1
Maintenance Domain Level 4
MA configuration Maintenance Domain Name MD1
Maintenance Association Name MA1
Relevant Service 1-NE1ToNE2
CC Test Transmit Period 1s
Protocol/Standard Y.1731
MEP configuration Maintenance Domain Name MD1
Board 7-ISM6-1
Port 7-ISM6-1(RTNIF-1)
VLAN 3
MEP ID 1
Direction Egress
CC Status Active
Client Layer Level 4
Bandwidth notification Maintenance Domain Name MD1

configuration
MEP ID 1
Advertisement Enable
Client Layer Level 7
Periodic Period
Periodic(s) 1
Hold Time(s) 0
NOTE
The table lists only microwave equipment configurations. For configurations of the interconnected
equipment, see the corresponding product documentation.

Procedure
Step 1 Create an MD.
Step 2 Create an MA.


Step 3 Create an MEP.

MEP1 on NE2 is used as an example.

Step 4 Configure bandwidth notification.


----End

This topic describes how to plan and configure the IGMP Snooping by using an example.

As shown in Figure 4-20, the E-LAN service (service ID: 1; service name: qlan_igmp) of
NE1 carries the multicast service. To increase the multicast efficiency, you need to enable the
IGMP Snooping function. The service requirements are as follows:
l NE1 functions as the end node and accesses the network through the 3-IFU2 board.
l The 5-EM6T-3 port is directly connected to a host.

Figure 4-20 Networking Diagram
IF

This section describes the procedure for configuring IGMP Snooping.

Data Preparation
Table 4-30 IGMP Snooping plan

IGMP Snooping parameters In this example, IGMP Snooping l Set IGMP Snooping parameter
parameters are set as follows: according to the service plan
l The aging time is set to the after enabling IGMP Snooping.
default value, 8 minutes. Default values are
recommended.
l The maximum number of no
response times is set to the l Setting a static router port and a
default value, 3. fast leave port is not necessarily
required.
l The router port can only be an
Integrated IP microwave port. l If a multicast member does not
Therefore, you can set the 3- need to be aged, set the port as
IFU2 port to a static router port a static multicast group
to prevent it from being aged. member.
l The 5-EM6T-3 port is l If a router port does not need to
connected to a host. Therefore, be aged, set the port as a static
you can set the port to a fast router port.
leave port. After receiving l If a multicast group member
IGMP Leave packets, the port is connected to only one
equipment can quickly delete multicast service receiver, you
the port from the multicast can set the member port as a
group. fast leave port.
Procedure
Step 1 Configure the IGMP Snooping protocol for NE1.
Step 2 Set port 5-EM6T-3 of NE1 to a fast leave port.

Step 3 Set port 3-IFU2 of NE1 to a static router port.
----End

Feature Configuration Guide 5 Ethernet Features on the EoS/EoPDH Boards
5 Ethernet Features on the EoS/EoPDH

Boards
About This Chapter

Ethernet Features on the EoS/EoPDH Boards.
NOTE
The OptiX RTN 905 and OptiX RTN 910A do not support these features.
5.1 Configuration Procedure (ERPS)

The key to configuring ERPS is creating an ERPS protection instance.
5.2 Configuration Procedure (STP/RSTP)
When a bridge requires the STP/RSTP protocol, you need to configure the STP/RSTP type
and protocol parameters, and then enable the STP/RSTP.
When the IGMP Snooping protocol is used for the bridge, you need to set the IGMP
Snooping parameters. In addition, you can set the static routing member as required.
To use the LAG protocol, you need to configure a LAG. In addition, you can configure the
priorities of the ports in the LAG as required.
5.6 Configuration Procedure (QoS)
When you plan QoS, define a flow and set required QoS parameters.
5.7 Configuration Procedure (Ethernet Service OAM)
When you use the Ethernet service OAM feature, define appropriate OAM MPs according to
the actual situation and then perform OAM operations as required.
When you use the Ethernet port OAM feature, perform appropriate OAM operations as
required.

5.9 Configuration Example (EVPL Services Based on the VLAN)

This section uses an example to describe how to plan and configure an Ethernet service based
on the VLAN according to network conditions.
5.10 Configuration Example (EVPL Services Based on QinQ)
This section uses examples to describe how to plan and configure QinQ-based EVPL services
according to network conditions.
5.11 Configuration Example (EPLAN Services Based on the 802.1D Bridge)
This section uses examples to describe how to plan and configure 802.1D bridge-based
EPLAN services according to network conditions.
5.12 Configuration Example (EVPLAN Services Based on the 802.1Q Bridge)
This section uses an example to describe how to plan and configure an EVPLAN service
based on the 802.1Q bridge according to network conditions.
5.13 Configuration Example (EVPLAN Services Based on the 802.1ad Bridge)
This section uses examples to describe how to plan and configure the 802.1ad bridge-based
EVPLAN services according to network conditions.
5.14 Configuration Example (ERPS)
This section uses an example to describe how to plan and configure ERPS.
5.15 Configuration Example (STP/RSTP)
This section uses an example to describe how to plan and configure STP/RSTP according to
network conditions.
This section uses an example to describe how to plan and configure IGMP Snooping
This section describes how to plan and configure LAGs according to the network conditions
by using an example.
5.18 Configuration Example (LPT)
This section uses an example to describe how to plan and configure LPT according to network
conditions.
This section uses an example to describe how to plan and configure QoS according to network
conditions.
This section uses an example to describe how to plan and configure Ethernet service OAM
This section uses an example to describe how to plan and configure Ethernet port OAM
5.1 Configuration Procedure (ERPS)

The key to configuring ERPS is creating an ERPS protection instance.

Table 5-1 Procedure for configuring ERPS

1 A.10.1.1 Required when you configure ERPS. Set the parameters as

Creating ERPS follows:
Instances l Set ERPS ID, East Port, West Port, RPL Owner Ring
Node Flag, RPL Port, and Control VLAN according to the
network plan.
l When setting RPL Owner Ring Node Flag, note that only
one RPL owner can exist on an Ethernet ring network.
l When setting RPL Port, note that ERPS protection
instances cannot share ring ports.
l When setting Control VLAN, note that Control VLAN
cannot be the same as the VLAN ID of any Ethernet service
packet.
2 A.10.1.2 Setting Required when you configure ERPS. It is recommended that

the Parameters you use the default values or set the parameters according to the
of the ERPS network plan.
Protocol
5.2 Configuration Procedure (STP/RSTP)

When a bridge requires the STP/RSTP protocol, you need to configure the STP/RSTP type
and protocol parameters, and then enable the STP/RSTP.
Table 5-2 Procedure for configuring the STP/RSTP

1 A.10.6.1 Required. Set the parameter as follows:

Configuring l Set Protocol Enabled to Disabled to temporarily disable
the Type and the STP/RSTP.
Enabled Status
of the l Set Protocol Type to the planned STP/RSTP type.
Spanning Tree CAUTION
Protocol Before you set Protocol Enabled to Disabled, check whether the
operation will affect the services.

2 A.10.6.2 Setting Required. Set the parameter as follows:

the Parameters l According to the network planning, set the following
of Spanning parameters of a bridge: Priority, Max Age(s), Hello
Tree Protocol Time(s), Forward Delay(s), and TxHoldCout(per
second).
l According to the network planning, set the following
parameters of a port: Priority, Port Path Cost, Admin
Edge Attribute, Protocol Enabled, and Auto Edge
Detection.
NOTE
Protocol Enabled of a port that is connected to the access equipment
should be set to Enabled, whereas Protocol Enabled of a port that is
connected to the transmission equipment should be set to Disabled.
3 A.10.6.1 Required. Set the parameter as follows:

Configuring Set Protocol Enabled to Enabled.
the Type and
Enabled Status
of the
Spanning Tree
Protocol

When the IGMP Snooping protocol is used for the bridge, you need to set the IGMP
Snooping parameters. In addition, you can set the static routing member as required.
Table 5-3 Procedure for configuring IGMP Snooping
1 A.10.7.1 Configuring the IGMP Required

Snooping Protocol l Set Protocol Enable to
Enabled.
l Set The Discarded Tag of the
Packet Excluded in the
Multicast Group according
to the network planning
information.
2 A.10.7.3 Modifying the Aging Time Optional.

of a Multicast Table Entry Multicast Aging Time(Min)
needs to be set according to the
service planning. It is
default loading sharing type.


To use the LAG protocol, you need to configure a LAG. In addition, you can configure the
priorities of the ports in the LAG as required.
Table 5-4 Procedure for configuring a LAG

St Operation Description
ep
1 A.10.2.1 Creating a Required. Set the major parameters as follows:

LAG l Set LAG Type to the same value as the opposite
equipment. Generally, set LAG Type 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 to provide
protection, it is recommended that you set Load Sharing
to Non-Sharing for the equipment at both ends. If the
LAG is configured to increase bandwidths, it is
recommended that you set Load Sharing to Sharing for
the equipment at both ends.
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 only to the
sharing LAG.
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
only to the non-sharing LAG.
l Set Main Port and Selected Standby Ports according to
the planning information. It is recommended that the main
and slave ports at both ends adopt the same settings.

Parameters for Unless otherwise specified, adopt the default values of
LAGs System Priority and Port Priority.

NOTE
You need to configure Ethernet line services before configuring the LPT for point-to-point services. This
restriction does not apply to the LPT for point-to-multipoint services.

Table 5-5 Procedure for configuring LPT for point-to-point services
Configuring LPT for A.10.11.1 Configuring LPT Required when the service is a
Point-to-Point Services for Point-to-Point Services point-to-point service.
The parameters need to be set
according to the service
planning.
Table 5-6 Procedure for configuring LPT for point-to-multipoint services
Configuring LPT for A.10.11.2 Configuring LPT Required when the service is a
Point-to-Multipoint for Point-to-Multipoint point-to-multipoint service.
Services Services The parameters need to be set
according to the service
planning.
5.6 Configuration Procedure (QoS)

When you plan QoS, define a flow and set required QoS parameters.
Table 5-7 provides the procedure for configuring QoS on EFP8and EMS6 boards.
NOTE
The bridging port (PORT 10) that connects to the packet plane on an EFP8 boardand the bridging port (PORT
8) that connects to the packet plane on an EMS6 board supports QoS only on the packet plane. 4.6
Configuration Process (QoS/HQoS) provides the procedure for configuring QoS on the two bridging ports.
Table 5-7 Procedure for configuring QoS
1 A.10.8.1 Required when the CAR or CoS operations are required for a
Creating a certain flow at the port.
Flow
2 A.10.8.2 Required when the ingress bandwidth and burst size in the
Creating the ingress direction need to be limited.
CAR
3 A.10.8.3 Required when the packets in a flow need to be scheduled to

Creating the egress queues with different priorities.
CoS
4 A.10.8.4 Required when the preset CAR or CoS policy needs to be

Binding the applied to a flow.
CAR/CoS

5 A.10.8.5 Required when the shaping function needs to configured for

Configuring egress queues.
Traffic Shaping
for Egress
Queues
6 A.10.8.6 Required when the traffic shaping policy needs to be

Configuring configured for queues at the port on the EMS6 board.
Port Shaping
7 A.10.8.7 Setting Required when the default egress queue scheduling method of
Egress Queue the EMS6 board needs to be modified.
Scheduling
Policies
5.7 Configuration Procedure (Ethernet Service OAM)

When you use the Ethernet service OAM feature, define appropriate OAM MPs according to
the actual situation and then perform OAM operations as required.

Table 5-8 Procedure for configuring Ethernet service OAM

1 A.10.9.1 Creating MDs Required in the case of the NEs

where the two Ethernet ports
involved in the service test are
located. Set the parameters as
follows:
l Set Maintenance Domain
Name and Maintenance
Domain Level to the same
values for the two NEs.
l In the test of an Ethernet
service between two edge
nodes on the transport network,
it is recommended that
Maintenance Domain Level
takes the default value 4. In the
test of an Ethernet service
between two internal NEs on
the transport network, set
Maintenance Domain Level to
a value smaller than 4. In the
test of an Ethernet service
between two Ethernet ports on
the same NE, set Maintenance
Domain Level to a value
smaller than the value that is set
in the test of an Ethernet
service between two internal
NEs on the transport network.
2 A.10.9.2 Creating MAs Required when you need to create

a standard MP. Set the parameters
as follows:
l Set Maintenance Domain
Name to the value of
Maintenance Domain Name
that is set in Step 1.
l Set Maintenance Association
Name to the same values for
the NEs on which OAM
operations are performed.

3 A.10.9.3 Creating MPs Required. Set the parameters as

follows:
l In the case of a standard MP,
set Maintenance Domain
Association Name to the
values of Maintenance
Domain Name and
Maintenance Association
Name that are set in Step 2.
l In the case of a common MP,
set Maintenance Domain
Association Name to NULL.
l In the case of an MEP, set Node
to the port of EFP8 board that
initiate and terminate OAM
operations. In the case of an
MIP, set Node to the port of
EFP8 board that Ethernet
services travel through.
l Optional: Set VLAN ID to any
VLAN of the configured
Ethernet services. The source
MEP and the sink MEP must
have the same configuration.
l In the same MA, the value of
MEP ID must be unique.
l If the services between MEPs
travel through the Ethernet
switching unit on the EFP8
board, set the Service
Direction to Ingress;
otherwise, set the direction to
Egress. Generally, ETH-OAM
is applicable to end-to-end
maintenance of a certain
service. Therefore, Service
Direction is set to Ingress for
MPs. In the case of MIPs, set
Service Direction to
Bidirectional.
l In the case of a standard MP, if
the sink MP is identified based
on the MP ID during the LB or
LT test, set CC Status to
Active.


NOTE
If an LT test is performed and the
specified faulty segment needs to be
identified, the MIP must be set.
4 A.10.9.4 Performing a CC Test Required when you need to

perform a CC test.
A.10.9.5 Performing an LB Test Required when you need to

perform an LB test.
A.10.9.6 Performing an LT Test Required when you need to

perform an LT test.
5 A.10.9.7 Activating the AIS Required when you need to inform

the MP at the higher level layer of
a fault.
6 A.10.9.8 Performing a Ping Test Required when you need to check

the service connectivity between
the local equipment and the data
communications equipment that
supports the ICMP protocol.
7 A.10.9.9 Performing Required when you need to check

Performance Check the performance of services
between the local equipment and
the OptiX equipment that supports
performance check.

When you use the Ethernet port OAM feature, perform appropriate OAM operations as
required.
Table 5-9 Procedure for configuring Ethernet port OAM
1 A.10.10.1 Enabling the OAM Auto- Required. Set the

Discovery Function major parameters as
follows:
l Set Enable
OAM Protocol
to Enabled.
l It is
recommended
that you set
OAM Working
Mode to Active.

2 Link Performance A.10.10.2 Enabling Optional.

Monitoring the Link Event Set Link Event
Notification Notification to
Enabled if the
opposite NE needs
to be informed of
the faults or
performance
threshold-crossing
events that are
detected.
A.10.10.3 Optional.
Modifying the Perform this
OAM Error Frame operation when you
Monitoring need to adjust the
Threshold thresholds of
performance events.
Performing Remote A.10.10.4 Optional.

Loopback Performing the The EFP8and EMS6
Remote Loopback board can only
initiate a remote
loopback. Therefore,
a remote loopback
initiated by the
EFP8 and EMS6
board is successful
only when the
remote end responds
to the request.
Self-loop test Self-loop test Optional.

Perform this
operation when you
need to perform a
self-loop for a port.
5.9 Configuration Example (EVPL Services Based on the

VLAN)
This section uses an example to describe how to plan and configure an Ethernet service based
on the VLAN according to network conditions.


As shown in Figure 5-1, the Ethernet services from the BTSs are aggregated on NE1, and
then are transmitted on the E1 private line to traverse the TDM network. Finally, the Ethernet
services arrive at BSC.
l On the network, the services from each BTS carry VLAN tags, and the VLAN IDs on
the entire network are planned in a unified manner. In addition, the services are isolated
by VLAN.
l NE1 and NE2 use the EoPDH technology, wherein Ethernet services are encapsulated
into E1 services so that Ethernet services traverse the TDM network successfully.
l Table 5-10 and Table 5-11 list the Ethernet service connections on NE1 and NE2
respectively.

BTS1
10Mbit/s
VLAN 101
Hybrid
E1 TDM E1 FE
Microwave
network network
BTS2
10Mbit/s NE1 NE2 BSC
VLAN 102
FE
BTS3
10Mbit/s
VLAN 103
Table 5-10 Connections of Ethernet links (NE1)
Link Port Description
To the leased network 1-SP3S-1 to 1-SP3S-16 Connects to the leased E1 lines. In

this example, 16 E1 lines are used
to transmit Ethernet services.
To the Hybrid radio link 4-EFP8-9 (connecting to a Hybrid Transmits/Receives the Ethernet
IF board) services to/from BTS1 and BTS2.
To BTS3 4-EFP8-1 Transmits/Receives the Ethernet

services to/from BTS3.
To the leased network 1-SP3S-1 to 1-SP3S-16 Connects to the leased E1 lines. In


To BSC 4-EFP8-1 Transmits/Receives the Ethernet

services to/from BSC.
5.9.2 Configuration Process

This section describes the procedure of data configuration.
Procedure
Step 1 See A.10.5.1 Configuring External Ethernet Ports.
The values for the required parameters are provided as follows.
Parameter NE1 NE2
4-EFP8-PORT1 4-EFP8-PORT9 4-EFP8-PORT1
Enabled/Disabled Enabled - Enabled
Working Mode Auto-Negotiation - Auto-Negotiation

Function Function
Maximum Frame 1522 1522 1522

Length (bytes)
Non- Disabled Disabled Disabled

Autonegotiation
Flow Control Mode
Autonegotiation Disabled - Disabled

Flow Control Mode
TAG Tag Aware Tag Aware Tag Aware
Entry Detection Enabled Enabled Enabled
Port Attributes UNI UNI UNI
Step 2 See A.10.5.2 Configuring VCTRUNKs on an Ethernet Board.
Parameter NE1 NE2
4-EFP8-VCTRUNK1 4-EFP8-VCTRUNK1
TAG Tag Aware Tag Aware
Entry Detection Enabled Enabled
Port Attributes UNI UNI

Parameter NE1 NE2
Mapping Protocol GFP GFP
Enabling LCAS Enabled Enabled
Level VC12-Xv VC12-Xv
Service Direction Bidirectional Bidirectional
Bound Path VC4-1-VC12(1-16) VC4-1-VC12(1-16)
Step 3 See A.10.3.1 Creating Ethernet Private Line Services.
Parameter NE1 NE2
Board 4-EFP8 4-EFP8 4-EFP8
Service Type EPL EPL EPL
Service Direction Bidirectional Bidirectional Bidirectional
Source Port PORT1 PORT9 PORT1
Source VLAN(e.g. 101, 102 103 101, 102, 103

1,3-6)
Sink Port VCTRUNK1 VCTRUNK1 VCTRUNK1
Sink VLAN(e.g. 101, 102 103 101, 102, 103

1,3-6)
Step 4 See A.7.1 Creating the Cross-Connections of Point-to-Point Services.
Parameter NE1 NE2
Level VC-12 VC-12
Direction Bidirectional Bidirectional
Source Slot 4-EFP8-1 4-EFP8-1
Source VC4 VC4-1 VC4-1
Source Timeslot 1-16 1-16

Range(e.g.1,3-6)
Sink Slot 1-SP3S 1-SP3S
Sink VC4 - -

Parameter NE1 NE2
Sink Timeslot Range(e.g. 1-16 1-16

1,3-6)
Step 5 See A.9.9.1 Creating an MD.

Parameter NE1 NE2
4-EFP8 4-EFP8
Maintenance Domain MD1 MD1

Name
Maintenance Domain 4 4
Level
Step 6 See A.9.9.2 Creating an MA.

Paramete NE1 NE2

r
4-EFP8 4-EFP8
Maintena MD1 MD1 MD1 MD1 MD1 MD1

nce
Domain
Name
Maintena MA1 MA2 MA3 MA1 MA2 MA3

nce
Associatio
n Name
Step 7 See A.9.9.3 Creating MEPs.

Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Domain
Name

Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Associatio
n Name
Node PORT9 PORT9 PORT1 PORT1 PORT1 PORT1
VLAN ID 101 102 103 101 102 103
MEP ID 101 102 103 201 202 203
Type MEP MEP MEP MEP MEP MEP
Service Ingress Ingress Ingress Ingress Ingress Ingress

Direction
CC Status Active Active Active Active Active Active
CCM 1000 1000 1000 1000 1000 1000

Sending
Period(m
s)
Step 8 See perform LB tests to test the Ethernet service configurations and perform the relevant
configuration for NE2.
l Consider the MEP whose MP ID is 201 as the source MEP and the MEP whose MP ID
is 101 as the sink MEP. Then, perform an LB test.
All LB tests should be reported to be successful.
----End
5.10 Configuration Example (EVPL Services Based on

QinQ)
This section uses examples to describe how to plan and configure QinQ-based EVPL services

This section describes the networking information about NEs.
then are transmitted on the leased E1 private line to traverse the TDM network. Finally, the
Ethernet services arrive at BSC.

l The VLAN tags used by the services from the BTSs are allocated by the BTSs
themselves. Therefore, the VLANs of services on different BTSs may be the same. To
solve this problem, the BSC allocates an S-VLAN tag for the service on each BTS, and
the S-VLAN IDs on the entire network are planned in a unified manner.
respectively.

BTS1
10Mbit/s
SVLAN 101
Hybrid
E1 TDM E1 FE
Microwave
network network
BTS2
SVLAN 102
FE
BTS3
10Mbit/s
SVLAN 103

To the leased network 1-SP3S-1 to 1-SP3S-8 Connects to the leased E1 line. In

this example, 8 E1 lines are used to
transmit Ethernet services.
To the Hybrid radio link 4-EFP8-9 Transmits/Receives the Ethernet

services to/from BTS1 and BTS2.






Procedure
Parameter NE1 NE2

Function Function

Length (bytes)

Autonegotiation
Flow Control Mode

Flow Control Mode
Port Attributes S-Aware S-Aware S-Aware
Parameter NE1 NE2
Port Attributes S-Aware S-Aware

Parameter NE1 NE2
Step 3 See A.10.3.5 Creating QinQ-Based EVPL Services.

Parameter NE1 N
E
2
Board 4- 4- 4-
E E E
F F F
P P P
8 8 8
Service Type E E E
V V V
P P P
L L L
( ( (
Q Q Q
in in in
Q Q Q
) ) )
Service Direction B B B
id id id
ir ir ir
e e e
ct ct ct
io io io
n n n
al al al

Parameter NE1 N
E
2
Operation Type T T T
ra ra ra
n n n
s s s
p p p
ar ar ar
e e e
nt nt nt
ly ly ly
tr tr tr
a a a
n n n
s s s
m m m
itt itt itt
in in in
g g g
S S S
- - -
V V V
L L L
A A A
N N N
ta ta ta
g g g
s s s
Source Port P P P
O O O
R R R
T T T
1 9 1
Source VLAN (e.g. 1, 3-6) - - -
Source S-VLAN 1 1 1
0 0 0
1, 3 1,
1 1
0 0
2 2,
1
0
3

Parameter NE1 N
E
2
Sink Port V V V
C C C
T T T
R R R
U U U
N N N
K K K
1 1 1
Sink VLAN(e.g. 1, 3-6) - - -
Sink S-VLAN 1 1 1
0 0 0
1, 3 1,
1 1
0 0
2 2,
1
0
3

Parameter NE1 NE2
Level VC-12 VC-12

Range(e.g.1,3-6)
Sink VC4 - -

1,3-6)


Parameter NE1 NE2
4-EFP8 4-EFP8

Name
Level
Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Domain
Name

nce
Associatio
n Name
Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Domain
Name

nce
Associatio
n Name
VLAN ID 101 102 103 101 102 103
MEP ID 101 102 103 201 202 203

Paramete NE1 NE2

r
4-EFP8 4-EFP8

Direction
CCM 1000 1000 1000 1000 1000 1000

Sending
Period(m
s)
l MP Consider the MEP whose MP ID is 201 as the source MEP and the MEP whose MP
ID is 101 as the sink MEP. Then, perform an LB test.
----End
5.11 Configuration Example (EPLAN Services Based on

the 802.1D Bridge)
This section uses examples to describe how to plan and configure 802.1D bridge-based
EPLAN services according to network conditions.

l The base station services are transparently transmitted.
respectively.


BTS1
10Mbit/s
Hybrid
E1 TDM E1 FE
Microwave
network network
BTS2 NE1 NE2 BSC
10Mbit/s
FE
BTS3
10Mbit/s








Procedure
Step 1 See A.10.5.1 Configuring External Ethernet Ports and configure external ports of the
Ethernet board.

Parameter NE1 NE2

Function Function

Length (bytes)

Autonegotiation
Flow Control Mode

Flow Control Mode
Entry Detection Disabled Disabled Disabled
Step 2 See A.10.5.2 Configuring VCTRUNKs on an Ethernet Board and configure the internal
ports of the Ethernet board.
Parameter NE1 NE2
Entry Detection Disabled Disabled
Step 3 See A.10.3.2 Creating Ethernet LAN Services and create the E-LAN services for NE1.
Parameter NE1
Board 4-EFP8
VB name vb1

Parameter NE1
Bridge Type 802.1d
Bridge Switch Mode SVL/Ingress filter disable
Bridge Learning Mode SVL
Ingress Filter Disabled
MAC Address Self-learning Enabled
Mount Port PORT1

PORT9
VCTRUNK1
Step 4 See A.10.3.1 Creating Ethernet Private Line Services and create the E-Line services for
NE2.
Parameter NE2
Board 4-EFP8
Service Type EPL
Service Direction Bidirectional
Source Port PORT1
Source VLAN(e.g. 1,3-6) -
Sink Port VCTRUNK1
Sink VLAN(e.g. 1,3-6) -
Step 5 See A.7.1 Creating the Cross-Connections of Point-to-Point Services and configure point-
to-point service cross-connections.
Parameter NE1 NE2
Level VC-12 VC-12

Range(e.g.1,3-6)

Parameter NE1 NE2
Sink VC4 - -

1,3-6)
Step 6 See A.9.9.1 Creating an MD and create the maintenance domain for NE1 and NE2.
Parameter NE1 NE2
4-EFP8 4-EFP8

Name
Level
Step 7 See A.9.9.2 Creating an MA and create the maintenance association for NE1 and NE2.
Parameter NE1 NE2
4-EFP8 4-EFP8
Maintenance MD1 MD1 MD1 MD1

Domain Name
Maintenance MA1 MA2 MA1 MA2

Association
Name
Step 8 See A.9.9.3 Creating MEPs and create the maintenance end points for NE1 and NE2.
Parameter NE1 NE2
4-EFP8 4-EFP8

Domain Name

Association
Name

Parameter NE1 NE2
4-EFP8 4-EFP8
Node PORT1 PORT9 PORT1 PORT1
VLAN ID - - - -
MEP ID 101 102 201 202
Type MEP MEP MEP MEP
Service Ingress Ingress Ingress Ingress

Direction
CC Status Active Active Active Active
CCM Sending 1000 1000 1000 1000

Period(ms)
Step 9 See perform LB tests to test the Ethernet service configurations and test the Ethernet
services on NE2.
----End
5.12 Configuration Example (EVPLAN Services Based on

the 802.1Q Bridge)
This section uses an example to describe how to plan and configure an EVPLAN service
based on the 802.1Q bridge according to network conditions.

l On the network, the services from each BTS carry VLAN tags, and the VLAN IDs on
the entire network are planned in a unified manner. In addition, the services are isolated
by VLAN.
respectively.


BTS1
10Mbit/s
VLAN 101
Hybrid
E1 TDM E1 FE
Microwave
network network
BTS2
VLAN 102
FE
BTS3
10Mbit/s
VLAN 103


To the Hybrid radio link 4-EFP8-9 (connecting to a Hybrid Transmits/Receives the Ethernet
IF board) services to/from BTS1 and BTS2.





Procedure

Parameter NE1 NE2

Function Function

Length (bytes)

Autonegotiation
Flow Control Mode

Flow Control Mode

Parameter NE1 NE2
Step 3 See A.10.3.2 Creating Ethernet LAN Services and perform the relevant configuration for
NE1.

Parameter NE1
Board 4-EFP8
VB name vb1
Bridge Type 802.1q
Bridge Switch Mode IVL/Ingress filter enable
Bridge Learning Mode IVL
Ingress Filter Enabled
Mount Port PORT1

PORT9
VCTRUNK1
Step 4 See A.10.3.4 Creating the VLAN Filtering Table and perform the relevant configuration for
NE1.
Parameter NE1
VLAN ID(e.g.1,3-6) 101,102 103
Selected forwarding ports PORT9 PORT1

VCTRUNK1 VCTRUNK1
Step 5 See A.10.3.1 Creating Ethernet Private Line Services and perform the relevant
Parameter NE2
Board 4-EFP8
Service Type EPL
Source Port PORT1
Source VLAN(e.g. 1,3-6) 101, 102, 103
Sink Port VCTRUNK1
Sink VLAN(e.g. 1,3-6) 101, 102, 103

Parameter NE1 NE2
Level VC-12 VC-12

Range(e.g.1,3-6)
Sink VC4 - -

1,3-6)
Parameter NE1 NE2
4-EFP8 4-EFP8

Name
Level
Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Domain
Name

nce
Associatio
n Name


Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Domain
Name

nce
Associatio
n Name
VLAN ID 101 102 103 101 102 103
MEP ID 101 102 103 201 202 203

Direction
CCM 1000 1000 1000 1000 1000 1000

Sending
Period(m
s)
----End
5.13 Configuration Example (EVPLAN Services Based on

the 802.1ad Bridge)
This section uses examples to describe how to plan and configure the 802.1ad bridge-based
EVPLAN services according to network conditions.


l The VLAN tags used by the services from the BTSs are allocated by the BTSs
themselves. Therefore, the VLANs of services on different BTSs may be the same. To
solve this problem, the BSC allocates an S-VLAN tag for the service on each BTS, and
the S-VLAN IDs on the entire network are planned in a unified manner.
respectively.

BTS1
10Mbit/s
SVLAN 101
Hybrid
E1 TDM E1 FE
Microwave
network network
BTS2
SVLAN 102
FE
BTS3
10Mbit/s
SVLAN 103









Procedure
Step 1 See A.10.5.1 Configuring External Ethernet Ports and perform the relevant configurations.
Parameter NE1 NE2
4-EFP8- 4-EFP8- 4-EFP8-

PORT1 PORT9 PORT1
Working Mode Auto- - Auto-

negotiation negotiation
Maximum Frame Length (bytes) 1522 1522 1522
Non-Autonegotiation Flow Disabled Disabled Disabled

Control Mode
Autonegotiation Flow Control Disabled - Disabled

Mode
Port Attributes S-Aware S-Aware S-Aware
Step 2 See A.10.5.2 Configuring VCTRUNKs on an Ethernet Board and perform the relevant
configurations.

Parameter NE1 NE2
4-EFP8- 4-EFP8-
VCTRUNK1 VCTRUNK1
Port Attributes S-Aware S-Aware
Step 3 See A.10.3.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services and perform the
relevant configuration for NE1.
Parameter NE1
Board 4-EFP8
VB Name vb1
Bridge Type 802.1ad
Bridge Switch Mode IVL/Ingress filter enable
Bridge Learning Mode IVL
Ingress Filter Enabled
Operation Type Mount Port and Mount Port and Mount Port and
base for Port base for Port base for Port
and S-VLAN and S-VLAN and S-VLAN
VB Port 1 2 3
Mount Port PORT1 PORT9 VCTRUNK1
C-VLAN - - -
S-VLAN 103 101, 102 101, 102, 103
C-VLAN Priority - - -
S-VLAN Priority - - -

Step 4 See A.10.3.4 Creating the VLAN Filtering Table and perform the relevant configuration for
NE1.
Parameter NE1
VLAN ID(e.g.1,3-6) 101, 102 103
Selected forwarding ports PORT9 PORT1

VCTRUNK1 VCTRUNK1
Step 5 See A.10.3.5 Creating QinQ-Based EVPL Services and perform the relevant configurations
for NE2.
Parameter NE2
Board 4-EFP8
Service Type EVPL(QinQ)
Operation Type Transparently

transmitting
S-VLAN tags
Source Port PORT1
Source VLAN (e.g. 1, 3-6) -
Source S-VLAN 101, 102, 103
Sink Port VCTRUNK1
Sink VLAN(e.g. 1, 3-6) -
Sink S-VLAN 101, 102, 103
Step 6 See A.7.1 Creating the Cross-Connections of Point-to-Point Services and configure the
STP/RSTP.
Parameter NE1 NE2
Level VC12 VC12

Parameter NE1 NE2

Range(e.g.1,3-6)
Sink VC4 - -

1,3-6)
Step 7 See A.9.9.1 Creating an MD and perform the relevant configurations.

Parameter NE1 NE2
4-EFP8 4-EFP8

Name
Level
Step 8 See A.9.9.2 Creating an MA and perform the relevant configurations.

Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Domain
Name

nce
Associatio
n Name
Step 9 See A.9.9.3 Creating MEPs and perform the relevant configurations.

Paramete NE1 NE2

r
4-EFP8 4-EFP8

nce
Domain
Name

nce
Associatio
n Name
VLAN ID 101 102 103 101 102 103
MEP ID 101 102 103 201 202 203

Direction
CCM 1000 1000 1000 1000 1000 1000

Sending
Period(m
s)
configurations for NE2.
----End
5.14 Configuration Example (ERPS)

This section uses an example to describe how to plan and configure ERPS.

This section provides the diagram of the network using ERPS.

As shown in Figure 5-6, NE1, NE2, NE3, and NE4 construct an SDH microwave ring
network. ERPS is configured to protect the Ethernet services on the ring network.
In normal cases, the RPL owner, NE3, blocks the east RPL port, and all the services are
transmitted through the west RPL port. If a link segment fails or an NE becomes faulty, NE3
unblocks the east RPL port, and the services can be transmitted through the east RPL port.
Figure 5-6 Network diagram

East:
4-EMS6-VCTRUNK1
West:
4-EMS6-VCTRUNK2
E W
East: NE1 East:

4-EMS6-VCTRUNK1 4-EMS6-VCTRUNK1
BSC
West: West:
4-EMS6-VCTRUNK2 4-EMS6-VCTRUNK2
E
W RPL
ERPS
NE2 RPL Port
BTS1 E NE4 BTS4
W
East:
4-EMS6-VCTRUNK1
W E
West: NE3
4-EMS6-VCTRUNK2
BTS3
RPL Owner Bloked port

This section describes the process for data configuration.
Procedure
Step 1 See A.10.1.1 Creating ERPS Instances and create an ERPS protection instance.
Parameter Value
NE1 NE2 NE3 NE4
ERPS ID 1 1 1 1
East Port 4-EMS6- 4-EMS6- 4-EMS6- 4-EMS6-

VCTRUNK1 VCTRUNK1 VCTRUNK1 VCTRUNK1
West Port 4-EMS6- 4-EMS6- 4-EMS6- 4-EMS6-

VCTRUNK2 VCTRUNK2 VCTRUNK2 VCTRUNK2
RPL Owner Ring No No Yes No

Node Flag

Parameter Value
NE1 NE2 NE3 NE4
RPL Port - - 4-EMS6- -

VCTRUNK1
Control VLAN 4093 4093 4093 4093
Step 2 See A.10.1.2 Setting the Parameters of the ERPS Protocol and set the ERPS parameters.
Parameter Value
NE1 NE2 NE3 NE4
Hold-Off 0 0 0 0
Time(ms)
Guard Time(ms) 500 500 500 500
WTR - - 5 -
Time(mm:ss)
Packet Transmit 5 5 5 5
Interval(s)
----End
5.15 Configuration Example (STP/RSTP)

This section uses an example to describe how to plan and configure STP/RSTP according to
network conditions.

As shown in Figure 5-7,
l NE1 aggregates EPLAN services on the internal port, and transmits the services to NE2
through the SDH radio link.
l NE1 and the Layer 2 switches (LAN Switch 1 and LAN Switch 2) on the access side
need to run the RSTP that uses LAN Switch 1 as the root switch. This prevents a
network loop on the access side, and therefore protects the network.
respectively.


LAN Swich 1
Root
ETH
RNC NE1 NE2 NodeB

10Mbit/s 10Mbit/s
LAN Swich 2
Port group
To LAN Switch 1 4-EFP8-PORT1 Transmits/Receives the Ethernet

service to/from LAN Switch 1.
To LAN Switch 2 4-EFP8-PORT2 Transmits/Receives the Ethernet

service to/from LAN Switch 2.
To the radio link that is connected 3-ISU2 Transmits the Ethernet services to
to NE2 NE2.
To the radio link that is connected 3-ISU2 Transmits the Ethernet services to
to NE1 NE1.
To NodeB 4-EFP8-PORT1 Transmits/Receives the Ethernet

service to/from NodeB.

Procedure
Step 1 See A.10.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol.
The values for enabling the STP/RSTP on NE1 are provided as follows.

Parameter Value Range
Protocol Enabled Disabled
Protocol Type RSTP
Step 2 See A.10.6.2 Setting the Parameters of Spanning Tree Protocol.

The values for the relevant parameters of bridge VB1 of NE1 are provided as follows.
Priority 32768
Max Age(s) 20
Hello Time(s) 2
Forward Delay(s) 15
TxHoldCout(per second) 6
The values for the parameters of the Ethernet port on NE1 are as follows.
PORT1 PORT2 VCTRUNK1
Priority 128 128 -
Port Path Cost 19 19 -
Admin Edge Attribute Disabled Disabled -
Protocol Enabled Enabled Enabled Disabled
Auto Edge Detection Disabled Disabled -
Step 3 See A.10.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol.
The values for enabling the STP/RSTP on NE1 are provided as follows.
Protocol Enabled Enabled
----End


This section uses an example to describe how to plan and configure IGMP Snooping

As shown in Figure 5-8, NE1 functions as the end node and connects to the network through
the 3-ISU2 board. The EVPLAN service based on the 802.1Q bridge is configured on NE1 to
provide multicast services. The IGMP Snooping feature is enabled to improve multicast
efficiency.
NE1
VOD server
Internet/Intranet
FE
FE FE
Ethernet
switch
host
Ethernet
switch
host host host host

Procedure
Step 1 See A.10.7.1 Configuring the IGMP Snooping Protocol.
The values for the parameters of Enable IGMP Snooping Protocol are provided as follows.
NE1
Protocol Enable Enabled

NE1
The Discarded Tag of the Packet Excluded in the Disabled

Multicast Group
Step 2 See A.10.7.3 Modifying the Aging Time of a Multicast Table Entry.
The values of Multicast Aging Time are provided as follows.
NE1
Multicast Aging Time(Min) 10
----End

This section describes how to plan and configure LAGs according to the network conditions
by using an example.

As shown in Figure 5-9, the Ethernet services on the Hybrid microwave network are
aggregated on NE1, and then are transmitted across the TDM network through leased E1
private lines. Finally, the Ethernet services arrive at the BSC. On the ring:
l The LAG can be configured for the Ethernet link between NE2 and the BSC to improve
link reliability.

BTS1
10Mbit/s
VLAN 101
LAG
Hybrid
E1 TDM E1 FE
microwave
network network
BTS2
VLAN 102
Main port: 4-EFP8-PORT1
Slave port: 4-EFP8-PORT2

BTS3
10Mbit/s
VLAN 103


Procedure
Step 1 See A.10.2.1 Creating a LAG.
The values for the related parameters that need to be set in Attribute Settings are as follows.
Parameter 4-EFP8
Value Range
LAG No. 1
LAG Name LAG_1
LAG Type Static
Load Sharing Non-sharing
Revertive Mode Revertive
The values for the related parameters that need to be set in Port Settings are as follows.
Parameter 4-EFP8
Value Range
Main Port PORT1
Selected Standby Ports PORT2
----End
5.18 Configuration Example (LPT)

This section uses an example to describe how to plan and configure LPT according to network
conditions.

As shown in Figure 5-10, NE1 is configured with point-to-multipoint LPT. NE2 is configured
with point-to-point LPT. When the communication between NE1 and NE2 becomes faulty,
NE1 disables the Ethernet ports that are connected to each BTS. In addition, NE1 notifies
each BTS to start the backup network and then the transmission of important data is ensured.

Figure 5-10 Networking diagram of LPT
NE1 NE2
4-EFP8-PORT1 (to BTS1) 4-EFP8-PORT1 (to BSC)
4-EFP8-PORT2 (to BTS2) 4-EFP8-VCTRUNK1 (to NE1)
4-EFP8-VCTRUNK1 (to NE2)
NE1 NE2
FE
FE
BTS1 E1
FE BSC
BTS2

Procedure
Step 1 See A.10.11.2 Configuring LPT for Point-to-Multipoint Services.
The values for the relevant parameters of NE1 are provided as follows.
l The following table provides the parameter settings of the convergence node.
Port VCTRUNK1
Bearer Mode GFP (Huawei)
Port Hold-Off Time(ms) 0
l The following table provides the parameter settings of the access node.
Port PORT1
PORT2
Step 2 See A.10.11.1 Configuring LPT for Point-to-Point Services.

The following tables list the parameter settings of NE2.
l The following table lists the settings in the positive direction.

Parameter Value
PORT PORT1
VCTRUNK Port VCTRUNK1
Direction Positive
LPT Yes
Bearer Mode GFP(HUAWEI)
Port-Type Port Hold-Off Time(ms) 0
VCTRUNK Port Hold-Off Time(ms) -
l The following table lists the settings in the reverse direction.
Parameter Value
PORT PORT1
VCTRUNK Port VCTRUNK1
Direction Reverse
LPT Yes
Bearer Mode GFP(HUAWEI)
Port-Type Port Hold-Off Time(ms) -
VCTRUNK Port Hold-Off Time(ms) 0
----End

This section uses an example to describe how to plan and configure QoS according to network
conditions.

As shown in the following figure, BTS11, BTS12, BTS15, and BTS16 receive and transmit
Ethernet services over the Hybrid radio links; these Ethernet services are aggregated on NE11
and then transmitted to the BSC over the leased TDM network. Configure QoS according to
the following requirements:
l The EFP8 board on NE11 receives the Ethernet services from BTS16.

NOTE
In this example, NE17 is the IDU that provides the EoPDH function. Instead of the IDU, NE17 can be
the MSTP equipment that provides the EoPDH function.
l The bandwidth occupied by the Ethernet services from each BTS is already known.
l Corresponding VLAN priorities are already configured for base stations based on service
types. In addition, QoS processing is required.
NOTE
This example provides the QoS configuration on NE11 and NE17 only. For the QoS configuration on other
NEs, see the Configuration Guide.

BTS12
10 Mbit/s
VLAN 110
BTS16
10 Mbit/s
FE VLAN 150
FE
GE
NE14 TDM
FE E1 network
NE13 NE12 NE11
E1
FE
BTS11
FE 10 Mbti/s
NE16 NE15 VLAN 100 NE17
BSC
BTS15
10 Mbit/s
VLAN 120

NE11
NE13 NE cascade NE12 PIU PIU
E1+FE CSH CSH
ISU2 ISU2 ISU2
NE14 NE6
ISU2 ISU2 NE6
ISU2
BTS12
ISU2 EM6T SP3S EM6T SP3D
CSHA
GE CSHN
E1
ISU2
FE E1 ISU2 EFP8
BTS11 FE
SP3D
E1
BTS16
CSH TDM
ISU2 ISU2 network
NE6 PIU PIU
CSHA ISU2 ISU2
EM6T SP3S
NE16
NE15 E1
E1+FE
CSHN
BTS15
EFP8
SP3D
NE17 FE
BSC

Procedure
Step 1 See A.10.8.1 Creating a Flow and create the flows.
l The values for the relevant parameters of NE11 are provided as follows.
Parameter Value
4-EFP8
Flow Type Port+VLAN Port+VLAN Port+VLAN Port+VLAN

Flow Flow Flow Flow
Port PORT1 PORT9 PORT9 PORT9
VLAN ID 150 100 110 120
Parameter Value
4-EFP8

Flow Flow Flow Flow

Parameter Value
4-EFP8
VLAN ID 100 110 120 150
Step 2 See A.10.8.3 Creating the CoS and create the CoS.
Parameter Value
4-EFP8
CoS ID 1
CoS Type VLAN priority
CoS Parameter CoS Priority
User Priority 0 in the VLAN Tag 0
Parameter Value
4-EFP8
CoS ID 1
CoS Type VLAN priority

Step 3 See A.10.8.4 Binding the CAR/CoS and bind the CAR/CoS.
Parameter Value
4-EFP8

Flow Flow Flow Flow
C-VLAN 150 100 110 120
Bound CAR - - - -
Bound CoS 1 1 1 1
Parameter Value
4-EFP8

Flow Flow Flow Flow
C-VLAN 150 100 110 120
Bound CAR - - - -
Bound CoS 1 1 1 1
----End


This section uses an example to describe how to plan and configure Ethernet service OAM

Figure 5-13 shows a TDM microwave network that transmits Ethernet services for base
station backhauls. The network is divided into multiple VLANs. VLAN 100 is used by
services of NodeB 1, and VLAN 110 is used by services of NodeB 2. Due to a fault on the
microwave network, the services of NodeB 1 and the services of NodeB 2 become faulty. In
this case, LT tests need to be performed to locate the fault.
Figure 5-13 Networking diagram of Ethernet service OAM

NodeB 1
VLAN 100 3-ISU2-1 (to NE2) 3-ISU2-1 (to NE1)
4-EFP8-PORT1 (to NodeB 1) 4-EFP8-PORT1 (to RNC)
4-EFP8-PORT2 (to NodeB 2)
NE 1 NE 2 RNC
NodeB 2
VLAN 110 Ethernet link Radio link

Procedure
Step 1 See A.10.9.1 Creating MDs.
NE1 NE2
Maintenance Domain Name MD1 MD1
Maintenance Domain Level 4 4
Step 2 See A.10.9.2 Creating MAs.

NE1 NE2

Domain Name

Association
Name
Step 3 See A.10.9.3 Creating MPs.
The values for the involved parameters of NE1 are provided as follows.
MEP MIP

Domain Name

Association
Name
Node 4-EFP8-PORT1 4-EFP8-PORT2 4-EFP8- 4-EFP8-

VCTRUNK1 VCTRUNK1
VLAN ID 100 110 100 110
MP ID 1 3 5 7
Type MEP MEP MIP MIP
Direction Ingress Ingress Bidirectional Bidirectional
The values for the involved parameters of NE2 are provided as follows.
MEP MIP

Domain Name

Association
Name

MEP MIP
Node 4-EFP8-PORT1 4-EFP8-PORT1 4-EFP8- 4-EFP8-

VCTRUNK1 VCTRUNK1
VLAN ID 100 110 100 110
MP ID 2 4 6 8
Type MEP MEP MIP MIP
Direction Ingress Ingress Bidirectional Bidirectional
Step 4 See A.10.9.6 Performing an LT Test.

l The values for the parameters that are associated with the LT test for Ethernet services
from NodeB 1 to RNC are provided as follows.
LT Source MP ID 1
LT Sink MP ID 2
l The values for the parameters that are associated with the LT test for Ethernet services
from NodeB 2 to RNC are provided as follows.
LT Source MP ID 3
LT Sink MP ID 4
In normal cases, all the MPs on the link under an LT test respond to LTM frames. If any fault
occurs, locate the fault based on the test result.
----End

This section uses an example to describe how to plan and configure Ethernet port OAM

The application of the Ethernet port OAM feature does not focus on specific services. Instead,
the application of the Ethernet port OAM feature focuses on the maintenance of the point-to-

point Ethernet link between two sets of equipment that are directly connected to each other.
When all the equipment supports the Ethernet port OAM protocol, the OAM auto-discovery is
performed if the IEEE 802.3ah OAM protocol is enabled on all the interconnected ports. If the
OAM auto-discovery is successful, you can perform OAM operations as required.
As shown in Figure 5-14, you can enable the Ethernet port OAM protocol if you need to
monitor the performance of the Ethernet link between NE1 and NE2, which are connected
directly to each other.
Figure 5-14 Networking diagram of Ethernet port OAM
IEEE 802.3ah
4-EFP8-PORT1 (to NE2) 4-EFP8-PORT1 (to NE1)
NodeB 1 NE3 NE1 NE2 NE4 RNC
Ethernet equipment of the customer
Ethernet link
NOTE
EFP8 and EMS6 boards support only remote loopback. A remote loopback test initiated on an EFP8/EMS6
board can be conducted successfully only when the Remote Side Loopback Response function is enabled at
the remote end. Therefore, a remote loopback test cannot be conducted between NE1 and NE2 as shown in
Figure 5-14.

Procedure
Step 1 See A.10.10.1 Enabling the OAM Auto-Discovery Function to enable the Ethernet port
OAM protocol.
The following table lists the parameter settings of NE1 and NE2.
Enable OAM Protocol Enabled
OAM Working Mode Active
Step 2 See A.10.10.2 Enabling the Link Event Notification.

Link Event Notification Enabled
Step 3 See A.10.10.3 Modifying the OAM Error Frame Monitoring Threshold.
Port 4-EFP8-PORT1
Error Frame Monitor Window(ms) 1000
Error Frame Monitor Threshold(frames) 2
Error Frame Period Window(frame) 148800
Error Frame Period Threshold(frames) 2
Error Frame Second Window(s) 60
Error Frame Second Threshold(s) 2
----End

Feature Configuration Guide 6 Configuring MPLS/PWE3 Features
6 Configuring MPLS/PWE3 Features
About This Chapter

various MPLS/PWE3.
6.1 Configuration Procedure (MPLS OAM_Y.1711)

The OAM configurations for MPLS APS are different from those for LSP long-term
monitoring.
6.2 Configuration Procedure (LSP Ping/Traceroute)
The configuration procedure of LSP ping/traceroute contains only one configuration task.
6.3 Configuration Procedure (MPLS APS)
When MPLS APS is configured, OAM is configured simultaneously.
6.4 Configuration Procedure (PW OAM_Y.1711)
The OAM configurations of PW APS are different from those of the PW long-term
monitoring.
6.5 Configuration Procedure (PW Ping/Traceroute)
The configuration procedure of PW ping/traceroute contains only one configuration task.
6.6 Configuration Procedure (PW APS)
When PW APS is configured, OAM is configured simultaneously.
6.7 Configuration Process (MPLS-TP OAM)
Set MEG IDs/MP IDs before using MPLS-TP OAM functions. If MEG IDs/MP IDs are set to
be IP-based, an NE can automatically generate MEG IDs/MP IDs and no configuration is
required.
6.8 Configuration Procedure (IMA)
On an OptiX RTN 950, an ATM trunk is used to describe an IMA group. Therefore, the key to
configuring IMA is to configuring an ATM trunk.
6.9 Configuration Procedure (ATM OAM)
The ATM OAM configurations of an F4 flow are the same as those of an F5 flow.
6.10 Configuration Procedure (ATM Traffic Management)
ATM traffic management is configured based on ATM connections.

6.11 Configuration Procedure (ML-PPP)

Configure PPP links and then MP groups.
6.12 Configuration Example (MPLS OAM_Y.1711)
This section uses an example to describe how to plan and configure MPLS OAM (Y.1711) for
long-term LSP monitoring according to network conditions.
6.13 Configuration Example (LSP Ping/Traceroute)
This section uses an example to describe how to plan and configure LSP ping/traceroute
6.14 Configuration Example (MPLS APS)
This section uses an example to describe how to plan and configure MPLS APS according to
network conditions.
6.15 Configuration Example (PW OAM_Y.1711)
This section uses an example to describe how to plan and configure PW OAM (Y.1711) for
long-term PW monitoring according to network conditions.
6.16 Configuration Example (PW Ping/Traceroute)
This section uses an example to describe how to plan and configure PW ping/traceroute
6.17 Configuration Example (PW APS)
This section uses an example to describe how to plan and configure PW APS according to
network conditions.
6.18 Configuration Example (PW FPS)
This configuration example describes how to configure PW FPS for RTN devices when the
RTN devices form a Mixed VPN with CX devices.
6.19 Configuration Example (MPLS-TP OAM for Tunnels)
This section uses an example to describe how to plan and configure MPLS-TP tunnel OAM
6.20 Configuration Example (MPLS-TP OAM for PWs)
This section uses an example to describe how to plan and configure MPLS-TP PW OAM
6.21 Configuration Example (IMA)
This section uses an example to describe how to plan and configure IMA according to
network conditions.
6.22 Configuration Example (ATM OAM)
This section uses an example to describe how to plan and configure ATM OAM according to
network conditions.
6.23 Configuration Example (ATM Traffic Management)
This section uses an example to describe how to plan and configure ATM traffic management
6.1 Configuration Procedure (MPLS OAM_Y.1711)

The OAM configurations for MPLS APS are different from those for LSP long-term
monitoring.

NOTE
OptiX RTN 910A does not support Y.1711-compliant MPLS OAM.

This section describes only the OAM configurations for LSP long-term monitoring. The OAM
parameters for MPLS APS are configured during the Configuration of MPLS APS.
Table 6-1 Flow for configuring MPLS OAM (Y.1711)

1 Changing Required if the tunnel OAM does not comply with Y.1711.
the OAM Change the tunnel OAM to be compliant with Y.1711 (the
Standard default setting).
2 A.11.2.9 Required. Set the major parameters as follows:

Setting l Set OAM Status on the ingress/egress node of the
MPLS required LSP to Enabled.
OAM (Y.
1711) l Regarding a unidirectional tunnel, set Detection Packet
Parameters Type of the ingress node of the required LSP to CV;
regarding a bidirectional tunnel, set Detection Packet
Type of the ingress/egress node of the required LSP to
CV.
l Set Detection Mode of the node of the required LSP to
Auto-Sensing.
l Regarding a unidirectional tunnel, set Reverse Tunnel
ID.
l It is recommended that you set SD Threshold(%) and
SF Threshold(%) to 0 (default value).
NOTE
If Packet Detection Interval(ms) needs to be set as required, set
Detection Packet Type to FFD.
Enabling/ Enable Enable FDI.
Disabling
FDI
6.2 Configuration Procedure (LSP Ping/Traceroute)

The configuration procedure of LSP ping/traceroute contains only one configuration task.
NOTE
OptiX RTN 910A does not support LSP ping/traceroute.

Table 6-2 Flow for configuring LSP ping

1 A.11.2.14 Performing Required. Regarding an MPLS tunnel, perform the

an LSP Ping Test operation on the required LSP on the ingress node.
Set the major parameters as follows:
l Set Packet Count to the default value.
l Set Packet Length and EXP Value as
required.
l Set Response Mode based on the tunnel
direction and the support capability of the
egress node:
– If the tunnel is bidirectional and the egress
node supports the reverse channel response,
set Response Mode to Application
Control Channel.
node does not support the reverse channel
response but supports DCN channel
response by using IP protocols, set
Response Mode to IPv4 UDP Response.
– If the tunnel is unidirectional and the egress
node supports DCN channel response by
using IP protocols, set Response Mode to
IPv4 UDP Response.
– In other cases, set Response Mode to No
Response.

Table 6-3 Flow for configuring LSP traceroute

1 A.11.2.15 Performing Required. Regarding an MPLS tunnel, perform the

an LSP Traceroute operation on the required LSP on the ingress node.
Test Set the major parameters as follows:
l Set Packet Length and EXP Value as
required.
l Set Response Mode based on the tunnel
direction and the support capability of egress
node:
node supports the reverse channel response,
set Response Mode to Application
Control Channel.
node does not support the reverse channel
response but supports DCN channel
response by using IP protocols, set
– If the tunnel is unidirectional and the egress
node supports DCN channel response by
using IP protocols, set Response Mode to
IPv4 UDP Response.
Response.
6.3 Configuration Procedure (MPLS APS)

When MPLS APS is configured, OAM is configured simultaneously.
NOTE
Table 6-4 Flow for configuring MPLS APS

1 Changing Required.
the OAM l If MPLS OAM (Y1.711) is used to detect faults for
Standard MPLS APS, change tunnel OAM to be compliant with
Y.1711 (the default setting).
l If MPLS-TP tunnel OAM is used to detect faults for
MPLS APS, change tunnel OAM to be compliant with
Y.1731.

2 A.11.2.9 Required if MPLS OAM (Y.1711) is used to check the

Setting availability of a tunnel. Set the major parameters as follows:
MPLS l Set OAM Status on the ingress/egress node of the
OAM (Y. required tunnel to Enabled.
1711)
Parameters l Regarding a unidirectional tunnel, set Detection Packet
Type of the ingress node of the required tunnel to FFD;
regarding a bidirectional tunnel, set Detection Packet
Type of the ingress/egress node to FFD. It is
recommended that you set Packet Detection
Interval(ms) to 3.3 ms. If this parameter of an MPLS
tunnel exceeds 3.3 ms, set the packet transmission
interval to a value greater than the delay.
l It is recommended that you set Detection Mode of the
ingress node to Auto-Sensing.
l Regarding a unidirectional tunnel, set Reverse Tunnel
ID.
l It is recommended that you set SD Threshold(%) and
SF Threshold(%) to 0 (default value).
NOTE

Configuring Required if MPLS-TP tunnel OAM is used to check the

MPLS-TP availability of an MPLS tunnel. Set the parameters as
Tunnel follows:
OAM l Set OAM Status to Enabled.
Parameters
l If the MPLS tunnels involve only Huawei equipment
that supports IP-based MPLS-TP OAM, it is
recommended that you set MEG ID Type to IP Based,
to avoid planning MEG IDs, MP IDs, RMEP IDs, and
MIPs.
l If some MPLS-TP OAM components cannot be set to
IP Based or have special requirements, it is
recommended that you set MEG ID Type to ICC
Based. In this case, plan MEGs and MPs according to
the following principles:
– All MPs on an MPLS tunnel must belong to the same
MEG. Each MPLS tunnel must belong to a unique
MEG.
– Each MEG of an operator must have a unique name
and the MEG parameters for all NEs in the MEG
must be set consistently.
– Each MP in an MEG must have a unique MP ID.
l Set MEG Level to 7.
l Detection Mode can be set only for ingress nodes on
bidirectional tunnels and egress nodes. Generally, it is
recommended that you set this parameter to the default
value Adaptive.
l It is recommended that you set SD Threshold (%) and
SF Threshold (%) to the default value 0.
l If an NE is the S-PE of an MS-PW and alarms triggered
by PW faults caused by MPLS tunnel faults need to be
suppressed, set AIS Status to Enabled.
l If the MPLS-TP OAM CC function is used to trigger
MPLS APS, it is recommended that you set CC Packet
Interval (ms) to 3.3 ms. If the frame delay variation on
a tunnel exceeds 3.3 ms, set the CCM transmit interval
to a value greater than the frame delay variation. If the
MPLS-TP OAM CC function is used for only continuity
check, it is recommended that you set CC Packet
Interval (ms) to the default value 1000. This parameter
is valid for only egress nodes on bidirectional tunnels
and ingress nodes.
l It is recommended that you set CC Packet Priority to 7
to ensure that CC packets are forwarded with priority.
This parameter is valid for only egress nodes on
bidirectional tunnels and ingress nodes.

l It is recommended that you set LM Packet Mode to

Standard.
Enabling/ Enable FDI is enabled by default. Therefore, the FDI
Disabling packet is transmitted to the downstream when the port
FDI detects a fault. Then, switching will be performed on the
egress node after the FDI packet arrives at the egress node.
4 A.8.8.5 Optional.
Setting the l To enable the function of triggering switching by bit
Advanced errors, set Enable Switching Triggered by Bit Error to
Attributes Enabled and set Switching Mode Triggered by Bit
of Ethernet Error (SF by default) according to the plan.
Ports
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.
5 A.11.3.1 Required. The parameters of the ingress node and egress

Creating an node must be set to the same values. Set the major
MPLS APS parameters as follows:
Protection l Set Protection Type to 1:1.
Group
l Set Switching Mode to Dual-Ended.
l Set Working Ingress Tunnel ID and Working Egress
Tunnel ID for the working tunnel according to the
planning information.
NOTE
Regarding a bidirectional tunnel, Working Ingress Tunnel ID
and Protection Ingress Tunnel ID need to be set, but Working
Egress Tunnel ID and Protection Egress Tunnel ID do not
need to be set.
l Set Protection Ingress Tunnel ID and Protection
Egress Tunnel ID for the protection tunnel according to
the network planning.
l It is recommended that you set Revertive Mode to
Revertive.
l It is recommended that you set WTR Time(min) to 5.
l It is recommended that you set Hold-off Time(100ms)
to 0.
l Set Protocol Status to Disabled.
5 A.11.3.4 After the ingress node and egress node are configured, set
Enabling/ Protocol Status of the APS protection groups on the two
Disabling nodes to Enabled.
MPLS APS
Protection

6.4 Configuration Procedure (PW OAM_Y.1711)

The OAM configurations of PW APS are different from those of the PW long-term
monitoring.
NOTE
OptiX RTN 910A does not support Y1711-compliant PW OAM.

This section describes only the OAM configurations for PW long-term monitoring. The OAM
parameters for PW APS are configured during the Configuration of PW APS.
Table 6-5 Flow for configuring PW OAM (Y.1711)

1 Changing Required if PW OAM is not compliant with Y.1711.

the OAM Change PW OAM to be compliant with Y.1711 (the default
Standard setting).
2 A.11.4.3 Required. Set the major parameters as follows:

Setting PW l Set OAM Status of the required PW to Enabled.
OAM (Y.
1711) l Set Detection Packet Type of the required PW to CV.
Parameters l Set Detection Mode of the required PW to Auto-
Sensing.
NOTE
6.5 Configuration Procedure (PW Ping/Traceroute)

The configuration procedure of PW ping/traceroute contains only one configuration task.
NOTE
OptiX RTN 910A does not support PW ping/traceroute.
NOTICE
Prior to PW ping/traceroute operations, set the control channel types of VCCV to the same at
both ends. Otherwise, PW ping/traceroute operations will fail.

Table 6-6 Flow for configuring PW ping
1 A.11.4.4 Performing a Required. Set the major parameters as follows:

PW Ping Test l Set Packet Count and EXP Value to the
default values.
l Set Packet Length as required.
l Set Response Mode based on the support
capability of the remote PE:
– If the remote PE supports the reverse
channel response, set Response Mode to
Application Control Channel.
– If the remote PE does not support the
reverse channel response but supports DCN
channel response by using IP protocols, set
Response.
Table 6-7 Flow for configuring PW traceroute
1 A.11.4.5 Performing a Required. Set the major parameters as follows:

PW Traceroute Test l Set Packet Length as required.
l Set EXP Value to the default value.
l Set Response Mode based on the support
capability of the remote PE:
– If the remote PE supports the reverse
channel response, set Response Mode to
Application Control Channel.
– If the remote PE does not support the
reverse channel response but supports DCN
channel response by using IP protocols, set
Response.
6.6 Configuration Procedure (PW APS)

When PW APS is configured, OAM is configured simultaneously.
NOTE
OptiX RTN 910A does not support Y.1711-compliant PW OAM.

Table 6-8 Flow for configuring PW APS

1 Changing Required.
the OAM l If PW OAM (Y.1711) is used to detect faults for PW
Standard APS, change PW OAM to be compliant with Y.1711
(the default setting).
l If MPLS-TP PW OAM is used to detect faults for PW
APS, change PW OAM to be compliant with Y.1731.
2 A.11.5.1 Required.
Creating a Select one PWE3 service from the required ones to create a
PW APS PW APS protection group.
Protection
Group l Set the major parameters in the General Attributes tab
as follows.
– Set PW Incoming Label and PW Outgoing Label
according to the planning information.
l Set the major parameters in the Protect Group tab as
follows.
– Set Protection Group ID to a protection group ID
that is planned.
– Set Enabling Status to Disabled.
– Set Revertive Mode to Revertive.
– Set Switchover Restoration Time (min) to 5.
– Set Switchover Delay Time (100 ms) to 0.
l Set the major parameters in the PW OAM tab as
follows.
– Set Detection Mode to Auto-Sensing.
– Set Detection Packet Type to FFD.
– Set Packet Detection Interval(ms) to 3.3.
– Set Transmitted PW ID according to the planning
information.

Configuring Required if MPLS-TP PW OAM is used to check the

MPLS-TP availability of an MPLS tunnel. Set the parameters as
PW OAM follows:
Parameters l Set OAM Status to Enabled.
l If the PWs involve only Huawei equipment that supports
IP-based MPLS-TP OAM, it is recommended that you
set MEG ID Type to IP Based, to avoid planning MEG
IDs, MP IDs, RMEP IDs, and MIPs.
l If some MPLS-TP PW OAM components cannot be set
to IP Based or have special requirements, it is
– All MPs on a PW must belong to the same MEG.
Each PW must belong to a unique MEG.
l Detection Mode can be set only for a T-PE. Generally, it
is recommended that you set this parameter to the
default value Adaptive.
l Set GAL Enable Status to the default value Disabled if
MPLS-TP PW OAM is implemented on PWE3 services
whose control words are enabled. In other cases, set
GAL Enable Status to Enabled and set GAL Mode
according to the plan. When GAL Mode is set to
RFC5586, the GAL is 13. When GAL Mode is set to Y.
1711, the GAL is 14.
l For an MS-PW, LSR ID to be Received and PW ID to
be Received need to be manually specified.
l If the MPLS-TP PW OAM CC function is used to
trigger PW APS, it is recommended that you set CC
Packet Interval (ms) to 3.3 ms. If the frame delay
variation on a tunnel exceeds 3.3 ms, set the CCM
transmit interval to a value greater than the frame delay
variation. If the MPLS-TP PW OAM CC function is
used for only continuity check, it is recommended that
you set CC Packet Interval (ms) to the default value
1000. This parameter is valid for only egress nodes on


Standard.
Configuring Create slave protection pairs for the other PWE3 services
Slave that need to be bound to the PW APS protection group.
Protection
Pairs of PW Set Protection Group ID of the slave protection pairs to a
APS protection group ID that is planned.
Enabling/ In the Protect Group tab, set Enabling Status to Enabled
Disabling for the APS protection groups on the two nodes.
PW APS
Protection
6.7 Configuration Process (MPLS-TP OAM)

Set MEG IDs/MP IDs before using MPLS-TP OAM functions. If MEG IDs/MP IDs are set to
be IP-based, an NE can automatically generate MEG IDs/MP IDs and no configuration is
required.
Figure 6-1 provides the process of configuring MPLS-TP OAM.
Figure 6-1 MPLS-TP OAM configuration process
Required Start
Optional
Configure basic attributes for
MPLS-TP OAM.
Configure MPLS-TP tunnel

OAM. Configure MPLS-TP PW OAM.
End

NOTE
Some products of OptiX RTN 900 series do not support some OAM operations. For details, see
Specifications of MPLS-TP OAM in the Feature Description.
Table 6-9 Configuring basic attributes for MPLS-TP OAM


Configuring l Set Carrier ID according to the network plan if MPLS-
Global TP OAM uses the ICC-based format. Carrier ID must
OAM be set to the same value for all NEs on a network.
Parameters
l Set Port AIS Status to Enabled if you want to suppress
alarms triggered by MPLS tunnel faults that are caused
by port faults.
l When AC link failures must be notified to its peer end in
real time, set CSF Status to Enabled.
l Channel Type must be set to the same value for all NEs
on a network. It is recommended that you set this
parameter to the default value.
Changing Change the OAM standard to Y.1731 for a tunnel/PW that
the MPLS requires the MPLS-TP OAM functions. By default, OAM
Tunnel/PW complies with Y.1711.
OAM
Standard

Table 6-10 Configuring MPLS-TP tunnel OAM

1 A.11.2.16 Required for ingress/egress nodes. Set parameters as

Configuring follows:
MEP l Set OAM Status to Enabled.
Parameters
for MPLS- l If the MPLS tunnels involve only Huawei equipment
TP Tunnel that supports IP-based MPLS-TP OAM, it is
OAM recommended that you set MEG ID Type to IP Based,
to avoid planning MEG IDs, MP IDs, RMEP IDs, and
MIPs.
l If some MPLS-TP OAM components cannot be set to
IP Based or have special requirements, it is
– All MPs on an MPLS tunnel must belong to the same
MEG. Each MPLS tunnel must belong to a unique
MEG.
l Detection Mode can be set only for ingress nodes on
bidirectional tunnels and egress nodes. Generally, it is
recommended that you set this parameter to the default
value Adaptive.
l If an NE is the S-PE of an MS-PW and alarms triggered
by PW faults caused by MPLS tunnel faults need to be
suppressed, set AIS Status to Enabled.
l If the MPLS-TP OAM CC function is used to trigger
MPLS APS, it is recommended that you set CC Packet
Interval (ms) to 3.3 ms. If the frame delay variation on
a tunnel exceeds 3.3 ms, set the CCM transmit interval
to a value greater than the frame delay variation. If the
MPLS-TP OAM CC function is used for only continuity
check, it is recommended that you set CC Packet
Interval (ms) to the default value 1000. This parameter
is valid for only egress nodes on bidirectional tunnels
and ingress nodes.


Standard.
2 A.11.2.16 If the value of MEG ID Type is not IP Based and LT tests

Configuring need to be performed, configure an MIP creation task for
MEP every transmit node. Set parameters as follows:
Parameters l It is recommended that you set MEG ID Type to ICC
for MPLS- Based.
TP Tunnel
OAM l All MIPs and MEPs on an MPLS tunnel must belong to
the same MEG and have the same MEG ID.
l Each MP on an MPLS tunnel must have a unique MP
ID.
3 A.11.2.18 If MPLS-TP tunnel OAM is used to check the continuity of

Starting a MPLS APS or the CC function is used to monitor the
CC Test of connectivity of a tunnel in real time, start a CC test on
MPLS-TP egress nodes on bidirectional tunnels or ingress nodes.
Tunnel
OAM
A.11.2.19 To perform LB tests, start an LB test on egress nodes on

Starting an bidirectional tunnels or ingress nodes. Set parameters as
LB Test of follows:
MPLS-TP l If Node Type is set to MIP, set TTL correctly
Tunnel according to the number of hops between the MEP and
OAM the MIP. If Node Type is set to MEP, set TTL to a
value greater than or equal to the number of hops
between the MIP and the remote MEP. It is
recommended that you set TTL to the default value.
l Set Remote MEP/MIP ID or IP Address according to
the termination node of an LB/LT test. 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. If MEG ID Type is set to ICC Based
for the termination node, set Remote MEP/MIP ID or
IP Address to the MP ID of the termination node.
l It is recommended that you set Packet Count, Packet
Priority, Transmit Interval (ms), and Packet Length
to their default values.
A.11.2.20 Perform this task when you need to perform an LT test. Set
Starting an parameters as follows:
LT Test It is recommended that you retain the default values for
Provided by Packet Sending Interval, Packet Sending Priority, and
MPLS-TP Length of Sending Packet.
Tunnel
NOTE
OAM This task is supported only when the configuration is performed in
end-to-end mode on the U2000.

A.11.2.21 Perform this task when you need to query the delay and
Testing the delay variation.
Delay and NOTE
Delay This task is supported only when the configuration is performed in
Variation of end-to-end mode on the U2000.
an MPLS
Tunnel
Setting the Perform this task when you need to lock the MPLS tunnel.
enabling Set Lock Status to Lock.
status of
LCK for
MPLS-TP
tunnel
OAM
Starting a Perform this task when you need to test the packet loss
TST Test situation.
Provided by NOTE
MPLS-TP This task is supported only when the configuration is performed in
Tunnel end-to-end mode on the U2000.
OAM

Table 6-11 Configuring MPLS-TP PW OAM

1 A.11.4.6 Required for the T-PE. Set parameters as follows:

Configuring l Set OAM Status to Enabled.
MEP
Parameters l If the PWs involve only Huawei equipment that supports
for MPLS- IP-based MPLS-TP OAM, it is recommended that you
TP PW set MEG ID Type to IP Based, to avoid planning MEG
OAM IDs, MP IDs, RMEP IDs, and MIPs.
l If some MPLS-TP PW OAM components cannot be set
to IP Based or have special requirements, it is
– All MPs on a PW must belong to the same MEG.
Each PW must belong to a unique MEG.
l Detection Mode can be set only for a T-PE. Generally, it
is recommended that you set this parameter to the
default value Adaptive.
l Set GAL Enable Status to the default value Disabled if
MPLS-TP PW OAM is implemented on PWE3 services
whose control words are enabled. In other cases, set
GAL Enable Status to Enabled and set GAL Mode
according to the plan. When GAL Mode is set to
RFC5586, the GAL is 13. When GAL Mode is set to Y.
1711, the GAL is 14.
l For an MS-PW, LSR ID to be Received and PW ID to
be Received need to be manually specified.
l If the MPLS-TP PW OAM CC function is used to
trigger PW APS, it is recommended that you set CC
Packet Interval (ms) to 3.3 ms. If the frame delay
variation on a tunnel exceeds 3.3 ms, set the CCM
transmit interval to a value greater than the frame delay
variation. If the MPLS-TP PW OAM CC function is
used for only continuity check, it is recommended that
you set CC Packet Interval (ms) to the default value
1000. This parameter is valid for only egress nodes on


Standard.
2 A.11.4.7 If the value of MEG ID Type is not IP Based and LT tests

Creating need to be performed, configure an MIP creation task for
MIPs of every S-PE. Set parameters as follows:
MPLS-TP l It is recommended that you set MEG ID Type to ICC
PW OAM Based.
l All MIPs and MEPs on a PW must belong to the same
MEG and they have the same MEG ID.
l Each MP on a PW must have a unique MP ID.
3 A.11.4.8 If MPLS-TP PW OAM is used to check the continuity of

Starting a PW APS or the CC function is used to monitor the
CC Test of connectivity of a PW in real time, start a CC test on each T-
MPLS-TP PE.
PW OAM
A.11.4.9 To perform LB tests, start an LB test on a T-PE. Set

LB Test of l If Node Type is set to MIP, set TTL correctly
MPLS-TP according to the number of hops between the MEP and
PW OAM the MIP. If Node Type is set to MEP, set TTL to a
value greater than or equal to the number of hops
between the MIP and the remote MEP. It is
recommended that you set TTL to the default value.
l Set Remote MEP/MIP ID or IP Address according to
the termination node of an LB/LT test. 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. If MEG ID Type is set to ICC Based
for the termination node, set Remote MEP/MIP ID or
IP Address to the MP ID of the termination node.
l It is recommended that you set Packet Count, Packet
Priority, Transmit Interval (ms), and Packet Length
to their default values.
A.11.4.10 Perform this task when you need to perform an LT test. Set
LT Test It is recommended that you retain the default values for
Provided by Packet Sending Interval, Packet Sending Priority, and
MPLS-TP Length of Sending Packet.
PW OAM
NOTE
This task is supported only when the configuration is performed in

A.11.4.11 Perform this task when you need to query the packet loss
Testing the ratio, delay, and delay variation.
Packet Loss NOTE
Ratio, This task is supported only when the configuration is performed in
Delay, and end-to-end mode on the U2000.
Delay
Variation of
a PW
Setting the Perform this task when you need to lock the PW.
enabling Set Lock Status to Lock.
status of
LCK for
MPLS-TP
tunnel
OAM
Starting an Perform this task when you need to test the packet loss
LT test of situation.
MPLS-TP NOTE
PW OAM This task is supported only when the configuration is performed in
6.8 Configuration Procedure (IMA)

On an OptiX RTN 950, an ATM trunk is used to describe an IMA group. Therefore, the key to
configuring IMA is to configuring an ATM trunk.
NOTE
OptiX RTN 905 does not support IMA.
Information About Configuring an IMA Group

Information about configuring an IMA group involves binding an ATM trunk, configuring an
IMA group, and configuring an ATM port.
Table 6-12 Information about configuring an IMA group

A.11.7.1 Binding ATM TRUNKs Required.

l For ATM/IMA services, set Level to E1.
For Fractional E1 services, set Level to
Fractional E1.
l Set the other parameters according to
the planning information.
NOTE
When the E1 frame mode is PCM 30, timeslot
16 cannot be bound.

A.11.7.2 Configuring an IMA group Required.

l For an ATM trunk requiring the IMA
function, set IMA Protocol Status to
Enabled.
l Set Clock Mode of the local NE and the
NE at the opposite end of the IMA trunk
to be the same as Clock Mode of the
interconnected NodeB.
l The other parameters are only valid for
IMA E1 and Fractional IMA. The
parameters at both ends of an IMA link
must be set to the same, which are
recommended to set to default values.
A.11.7.3 Setting ATM Port Parameters Optional.

l It is recommended that you set Port
Type and ATM Cell Payload
Scrambling by default based on the
type of access equipment. The
parameter values must be the same for
both ends of a link.
l The other parameters take the default
values.
6.9 Configuration Procedure (ATM OAM)

The ATM OAM configurations of an F4 flow are the same as those of an F5 flow.
NOTE
OptiX RTN 905 does not support ATM OAM.

Figure 6-2 Configuration flowchart
Start
Query and set a mark

for a loopback point
Setting segment and end Conduct an LB test

Conduct a CC
attributes of AIS/RDI
End
Required
Optional
Setting Segment and End Attributes of AIS/RDI

A.11.10.2 Setting Segment and End Required. Set the parameters as follows:
Attributes of AIS/RDI Set AIS/RDI Segment and End Attribute
of each connection direction according to
NOTE
When the segment and end attributes of connection points are set, the AIS/RDI OAM is automatically
enabled.

Flow for configuring a CC

A.11.10.3 Performing a Continuity Check Required.

Test A CC is used to continuously test link
connectivity, but not to locate a fault. Set
the parameters as follows:
l Set Segment and End Attribute of the
node. This parameter specifies the
termination point of CC cells,
determining the range of test link.
l Set CC Activate Flag of the node. This
parameter specifies the functions of the
node for receiving and transmitting CC
cells.
Flow for configuring an LB test

A.11.10.4 Querying or Setting LLIDs Required by an NE responding to an LB

packet.
Set the LLID of an NE to the default value
if it is unique on the network. Otherwise,
reset the LLID as required.

A.11.10.5 Performing an LB Test Required by an NE transmits an LB packet.

Set the parameters as follows:
l Set Segment and End Attribute of the
node.
Before an end-to-end LB test, you need
to set end points in the test domain.
Before a segment-to-segment LB test,
you need to set segment points in the test
domain.
Segment LB cells are looped back only
at a Segment point, Segment and
Endpoint, or Non segment and
Endpoint. End-to-end LB cells are
looped back only at an Endpoint or
Segment and Endpoint.
l Set Loopback Point NE of the LB test
to specify the NE whether the LB cell is
looped back.
l Test result
It should be Success.
l After the LB test, cancel the setting of
Segment and End Attribute on both
ends. The entire link is restored to the
status before test.
6.10 Configuration Procedure (ATM Traffic Management)

ATM traffic management is configured based on ATM connections.
NOTE
OptiX RTN 905 does not support ATM traffic management.

Figure 6-3 Configuration flowchart

Required Start
Optional
Create an ATM
policy
Configure an ATM
service
End
Configuration procedure
A.11.9.3 Creating an ATM Policy Required if the ATM service is based on

ATM connections
Set the parameters according to the planning
information.
l Set Policy ID, or select Automatically
Assign.
l Select or assign a value for Policy
Name.
l Set Service Type according to the
l Set Traffic Type and corresponding
traffic parameters based on Service
Type.
l Set the enabled status of Discard Traffic
Frame and UPC/NPC according to
A.11.8.1 Creating ATM Services Required.

Set the service parameters according to the
planning information, and bind a
corresponding ATM policy for each
connection of the ATM service.
6.11 Configuration Procedure (ML-PPP)

Configure PPP links and then MP groups.

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.
Configuring ML-PPP (Smart E1s Are MP Group Members)
Table 6-13 Configuring ML-PPP (Smart E1s are MP group members)

Setting the A.8.6.1 Required. Set the parameters as follows:

attributes of Setting l Set Name according to service planning information.
Smart E1 Basic
ports Attributes l Set Port Mode to Layer 3.
of Smart E1
Ports
A.8.6.2 Optional. Set the parameters as follows:

Setting Set Frame Format and Frame Mode according to service
Advanced planning information. Ensure that the same frame mode is
Attributes used at both ends.
of Smart E1
Ports Normally, the port that services uses the CRC-4 multi-frame
format and the PCM31 frame mode.
A.11.11.1 Creating MP Required.

Groups
Configuring ML-PPP (E1s in Channelized STM-1s Are MP Group Members)
Table 6-14 Configuring ML-PPP (E1s in channelized STM-1s are MP group members)
A.8.5 Changing the E1 Optional. Set the parameters as follows:

Frame Format and Frame Set Frame Format and Frame Mode according to service
Mode for a Channelized planning information. Ensure that the same frame mode is
STM-1 used at both ends.
Normally, the port that services uses the CRC-4 multi-frame
format and the PCM31 frame mode.
Creating and A.8.7.1 Required.

configuring Creating
serial ports Serial Ports

A.8.7.2 Required.
Setting
Basic
Attributes
of Serial
Ports
A.11.11.1 Creating MP Required.

Groups
6.12 Configuration Example (MPLS OAM_Y.1711)

This section uses an example to describe how to plan and configure MPLS OAM (Y.1711) for
long-term LSP monitoring according to network conditions.
NOTE

On a PSN shown in Figure 6-4, CV packets are used to continuously test the connectivity of
the bidirectional MPLS tunnel (ID = 1501) between NE1 and NE3.
Figure 6-4 Network diagram of the MPLS OAM (Y.1711) function
NE1 NE2 NE3
LSP
Bidirectional Tunnel (ID=1501)
Ingress Egress

This section describes the procedure for configuring MPLS OAM (Y.1711).

Data Preparation
OAM status Enabled -
Detection packet type CV LSP connectivity needs to

CVCV be verified and the detection
interval is not specified, so
CV packets are used.
Detection mode Adaptive -
SD threshold (%) 0 -
SF threshold (%) 0 -
Procedure
Step 1 Configure MPLS OAM (Y.1711) parameters.
----End
6.13 Configuration Example (LSP Ping/Traceroute)

This section uses an example to describe how to plan and configure LSP ping/traceroute
NOTE
This example describes only the application of LSP ping. The application of LSP traceroute is similar,
and therefore is not described.
OptiX RTN 910A does not support LSP ping/traceroute.


On a PSN as shown in Figure 6-5, LSP ping is used to test the connectivity of a bidirectional
tunnel (ID = 1501) between NE1 and NE3.
Figure 6-5 Network diagram of the LSP ping function
NE1 NE2 NE3
LSP

Ingress Egress

This section describes the procedure for configuring LSP ping.
Data Preparation
Packet test LSP ping The LSP ping function is

used to check LSP
connectivity, instead of
locating a fault.
EXP value 7 In this example, the MPLS

EXP value is not specified
for MPLS tunnels and only
LSP connectivity is
checked, so the EXP value
is set to 7 to prevent
detection packets from
being affected by QoS
settings.

Packet length 64 (short packet test) MPLS tunnels transmit

1400 (long packet test) packets of variable lengths.
Set the test packets to
different lengths to verify
the connectivity of an MPLS
tunnel when it transmits
short and long packets.
Response mode Application control channel NE3 can respond to LSP

ping/traceroute request
packets through the reverse
tunnel. Therefore, set the
response mode to
application control channel
when a test is initiated at
NE1.
Procedure
Step 1 Perform an LSP ping test (transmitting short packets) at NE1.
----End

6.14 Configuration Example (MPLS APS)

This section uses an example to describe how to plan and configure MPLS APS according to
network conditions.
NOTE

On a PSN shown in Figure 6-6, the two bidirectional tunnels between NE1 and NE4 are
configured with MPLS APS to improve service transmission reliability. MPLS OAM (Y.1711)
is used to check the availability of MPLS tunnels.
Figure 6-6 Network diagram of MPLS APS

NE2
Working Tunnel ID: 1501
NE1 NE4
Protection Tunnel ID: 1502

NE3

This section describes the procedure for configuring MPLS APS.
Data Preparation
Item Value in This Planning
Example Principle
Basic information Detection packet FFD -

Type
Detection mode Adaptive


Example Principle
Information about Protection type 1:1 Disable the protocol

the protection PW before configuring
Mode Dual-ended the protection PW.
revertive
Working ingress 1501

tunnel ID
Protection ingress 1502

tunnel ID
Protocol status Disabled
WTR time (min) 5
Hold-off time (100 0

ms)
MPLS APS Protocol status Enabled -
Procedure
Step 1 Configure MPLS OAM parameters.
Working tunnel 1501 on NE1 is used as an example.
Step 2 Create an MPLS APS protection group.


Step 3 Enable MPLS APS protection.


----End
6.15 Configuration Example (PW OAM_Y.1711)

This section uses an example to describe how to plan and configure PW OAM (Y.1711) for
long-term PW monitoring according to network conditions.
NOTE
OptiX RTN 910A does not support Y1711-compliant PW OAM.

On a PSN shown in Figure 6-7, CV packets in the PW OAM (Y.1711) mechanism are used to
continuously test the connectivity of the PW between NE1 and NE3.
Figure 6-7 Network diagram of the PW OAM (Y.1711) function
NE1 NE2 NE3
LSP
PW (ID=1501)
Ingress Egress


This section describes the procedure for configuring PW OAM (Y.1711).
Data Preparation
Detection packet type CV PW connectivity needs to be

verified and the detection
interval is not specified, so
CV packets are used.
Detection mode Adaptive -
Procedure
Step 1 Start or cancel a CV/FFD packet detection.
----End
6.16 Configuration Example (PW Ping/Traceroute)

This section uses an example to describe how to plan and configure PW ping/traceroute

NOTE
This example describes the application of PW ping. The application of PW traceroute is similar, and
therefore is not described.
OptiX RTN 910A does not support PW ping/traceroute.

On a PSN as shown in Figure 6-8, PW ping is used to test the connectivity of a PW between
NE1 and NE3.
Figure 6-8 Network diagram of the PW ping function
NE1 NE2 NE3
LSP
PW (ID=1501)
Ingress Egress

This section describes the procedure for configuring PW ping.
Data Preparation
Packet test PW ping The PW ping function is

used to check PW
connectivity, instead of
locating a fault.
Packet length 64 (short packet test) PWPWs transmit packets of

1400 (long packet test) variable lengths. Set the test
packets to different lengths
to verify the connectivity of
a PW when it transmits
short and long packets.

Response mode Application control channel NE3 can respond to PW

ping/traceroute request
packets through the reverse
tunnel. Therefore, set the
response mode to
application control channel
when a test is initiated at
NE1.
Procedure
Step 1 Perform a PW ping test (transmitting short packets) at NE1.
----End
6.17 Configuration Example (PW APS)

This section uses an example to describe how to plan and configure PW APS according to
network conditions.
NOTE


In Figure 6-9, NE1 is an RTN 900 NE. PW APS is configured for NE1 to achieve RNC dual-
homing. PW OAM (Y.1711) is used to check the availability of PWs.
Figure 6-9 Network diagram of PW APS
MC-PW APS
Working Tunnel ID:

1501 NE2
DNI-PW
NodeB NE1 RNC
Protection Tunnel ID: NE3

1502
Packet equipment that supports MC-PW APS
NOTE
In this figure, the working tunnel is the tunnel that carries the working PW, and the protection tunnel is
the tunnel that carries the protection PW. MPLS APS is not configured between the two tunnels.
The service requirements are as follows:
l A working tunnel is configured with an ID of 1501, and a protection tunnel is configured

with an ID of 1502.
l Three unprotected PWE3 services are created on the working tunnel. Table 6-15
provides the service planning information.
l To save resources, only one PWE3 service is configured into a PW APS protection
group. The other two services are configured into its slave protection pairs. This means
that the two services will be switched if the PWE3 service in the PW APS protection
group is switched.
Table 6-15 Planning information about PW APS
Parameter CES Service Ethernet Service ATM Service
Service ID 201 202 203
Protection type PW APS protection Slave protection pair Slave protection pair


This section describes the procedure for configuring PW APS.
Data Preparation
Example Principle
Basic attributes Detection packet FFD -

type
detection mode Adaptive
Information about the protection PW See the following Disable the protocol
figure. before you
configuring the
protection PW.
MPLS APS Protocol status Enabled -
PW1
Sevice ID: 201
PW ID: 801
PW Incoming Label: 801
PW Outgoing Label: 801
Protection Group parameters

Protection Group ID: 1
Enabling Status: Disabled
Switching Mode: Dual-ended switching
Revertive Mode: Revertive
Switchover Restoration Time (min): 5
Switchover Delay Time (100 ms): 0
PW2 PW OAM parameters

Sevice ID: 202 Detection Mode : Adaptive
PW ID: 802 Detection Packet Type: FFD
PW Incoming Label: 802 Packet Detection Interval(ms): 3.3ms
PW Outgoing Label：802 Transmitted PW ID: 201(Working PW)
801(Protection PW)
Protection Group ID of Slave
protection pairs: 1
Protection Tunnel ID: 1502
PW3
Sevice ID: 203
PW ID：803
PW Incoming Label: 803
PW Outgoing Label: 803
Protection Group ID of Slave protection pairs: 1

Procedure
Step 1 Create a PW APS protection group for the Ethernet Service (ID = 201).
Step 2 Create a PW APS group for Ethernet service (ID = 202) and ATM service (ID = 203).
Ethernet service (ID = 202) is used as an example.

4
2
5
7
8
Step 3 Configure slave protection pairs for the Ethernet service (ID = 202) and Ethernet Service (ID
= 203).
Ethernet service (ID = 202) is used as an example.

4
2
7 9
10
11
Step 4 Enable PW APS protection.
----End
6.18 Configuration Example (PW FPS)

This configuration example describes how to configure PW FPS for RTN devices when the
RTN devices form a Mixed VPN with CX devices.
NOTE

On the network, the OptiX RTN 900 NEs are configured with PW FPS to implement dual-
homing protection of services.
In Figure 6-10, NE1 is an OptiX RTN 900 NE. PW FPS is configured for NE1 to achieve
RNC dual-homing. Y.1731-compliant MPLS-TP OAM is used to check the PW availability.

Figure 6-10 Networking diagram of PW FPS
Working Tunnel ID:

201
L3VPN network
NodeB NE1
PW FPS
Protection Tunnel ID:
801
Packet transmission equipment Router
NOTE
l A working tunnel is configured with an ID of 201, and a protection tunnel is configured with an ID
of 801.
l In the figure, the working tunnel bears the working PW and the protection tunnel bears the
protection tunnel. The two tunnels are not in one MPLS APS protection group.

A PW FPS protection group needs to be created and the ARP entry dually-transmitting and
buffering needs to be enabled.
Data Preparation
Example Principle
Information about PW ID 801 (Protection PW) -

the protection PW
PW Incoming 801 (Protection PW)
Label
PW Outgoing 801 (Protection PW)

Label
Information about Packet Detection 3.33 -

MPLS-TP OAM Interval(ms)
GAL Enable Status Enabled
ARP Dual Feed Enabled -
Procedure
Step 1 A.11.5.2 Creating a PW FPS Protection Group


----End Copyright © Huawei Technologies Co., Ltd.
6.19 Configuration Example (MPLS-TP OAM for Tunnels)

This section uses an example to describe how to plan and configure MPLS-TP tunnel OAM

On a PSN shown in Figure 6-11, two LB tests must be performed to locate the fault on the
bidirectional MPLS tunnel (ID = 1501) between NE1 and NE3.
Figure 6-11 Networking diagram for MPLS-TP tunnel OAM
NE1 NE2 NE3
LSP
Ingress Egress

Data Preparation
OAM standard MPLS-TP OAM An NE must be allocated a

unique carrier ID.

OAM configurations Figure 6-12 provides the l If all NEs that MPLS
details. tunnels/PWs traverse are
Huawei devices that
support IP-based MPLS-
TP OAM components,
IP-based MPLS-TP
OAM components are
recommended, to
facilitate planning of
MEG IDs and MP IDs.
l If not all NEs are
Huawei devices, not all
Huawei devices support
IP-based MPLS-TP
OAM components, or
there are other
requirements, ICC-based
MPLS-TP OAM
components are
recommended. In this
case, the guidelines for
planning MEGs and MPs
are as follows:
– Each MEG of the
same carrier must
have a unique MEG
ID code (UMC).
– All MPs on an MPLS
tunnel/PW must
belong to the same
MEG. MPs on
different MPLS
tunnels/PWs must
belong to different
MEGs.
– Each MP in an MEG
must have a unique
MP ID.
l The recommended
setting for the MEG level
is 7.
MEPs be created on
ingress and egress nodes
and MIPs be created on
transit nodes on each
MPLS tunnel.

Figure 6-12 OAM configurations

ICC Based
MEG1
201
ICC Based ICC Based
7
MEG1 MEG1
101 301
7 7
NE1 NE2 NE3 MEG ID Type

MEG ID
LSP MEP ID
MEG Level
Ingress Egress
Procedure
Step 1 Change the OAM standard to Y.1731 for NE1 and NE3.
3
1
Step 2 Set global OAM parameters.


Step 3 Configure MEP parameters for MPLS-TP Tunnel OAM.

2
3
Step 4 Start a CC test of MPLS-TP Tunnel OAM.


2
3
4
1. If MPLS tunnel APS or MPLS PW APS is triggered by MPLS-TP OAM CC

results, it is recommended that the interval for sending CCMs be set to 3.3 ms.
If the frame delay variation on a tunnel or PW exceeds 3.3 ms, set the interval
for sending CCMs to a value greater than the frame delay variation.
2. If MPLS-TP OAM CC only checks connectivity, it is recommended that the
interval for sending CCMs be set to 1s.
1 3. It is recommended that the CCM priority be set to 7 to ensure CCM
forwarding.
Step 5 Start an LB test of MPLS-TP Tunnel OAM.


2
3
5
1. If an LB test is performed to check bidirectional

connectivity between an MEP and an MIP, the TTL
must be set according to the number of hops from
the MEP to the MIP.
connectivity between an MEP and a remote MEP,
the TTL must be set to a value equal to or greater
than the number of hops from the MEP to the
remote MEP.
----End
6.20 Configuration Example (MPLS-TP OAM for PWs)

This section uses an example to describe how to plan and configure MPLS-TP PW OAM

On a PSN shown in Figure 6-13, LB tests are used to test the connectivity of the PW between
NE1 and NE3.

Figure 6-13 Networking diagram for MPLS-TP PW OAM
NE1 NE2 NE3
LSP
PW (ID=1501)
Ingress Egress
LSR ID: 130.0.0.2 LSR ID: 130.0.0.6

Data Preparation
OAM standard MPLS-TP OAM An NE must be allocated a

unique carrier ID.
OAM configurations Figure 6-14 provides the l If all NEs that MPLS
details. tunnels/PWs traverse are
Huawei devices that
support IP-based MPLS-
TP OAM components,
IP-based MPLS-TP
OAM components are
recommended, to
facilitate planning of
MEG IDs and MP IDs.
l The recommended
setting for the MEG level
is 7.
MEPs be created on
ingress and egress nodes
and MIPs be created on
transit nodes on each
MPLS tunnel.

GAL status Disabled If PWE3 services use

control words, MPLS-TP
PW OAM packets do not
necessarily carry generic
associated channel header
labels (GALs). Otherwise,
MPLS-TP PW OAM
packets must carry GALs.
Figure 6-14 OAM configurations

IP Based
MEG1
7
IP Based IP Based
MEG1 MEG1
7 7
NE1 NE2 NE3
LSP
PW(ID=1501)
MEG ID Type
MEG ID
Ingress Egress MEG Level
LSR ID: 130.0.0.2 LSR ID: 130.0.0.6
Procedure
Step 1 Change the OAM standard to Y.1731 for NE1 and NE3.


Step 3 Configure MEP parameters for MPLS-TP PW OAM.


2
3
4
Step 4 Start a CC test of MPLS-TP PW OAM.

2
3
1. If MPLS tunnel APS or MPLS PW APS is triggered by MPLS-TP OAM CC

results, it is recommended that the interval for sending CCMs be set to 3.3 ms.
If the frame delay variation on a tunnel or PW exceeds 3.3 ms, set the interval
for sending CCMs to a value greater than the frame delay variation.
2. If MPLS-TP OAM CC only checks connectivity, it is recommended that the
interval for sending CCMs be set to 1s.
3. It is recommended that the CCM priority be set to 7 to ensure CCM
forwarding.
Step 5 Start an LB test of MPLS-TP PW OAM.


2
3
1 6

connectivity between an MEP and an MIP, the TTL
must be set according to the number of hops from
the MEP to the MIP.
connectivity between an MEP and a remote MEP,
the TTL must be set to a value equal to or greater
than the number of hops from the MEP to the
remote MEP.
----End
6.21 Configuration Example (IMA)

This section uses an example to describe how to plan and configure IMA according to
network conditions.
NOTE
OptiX RTN 905 does not support IMA.

As shown in Figure 6-15, NE1 (an OptiX RTN 950) receives ATM services from the NodeB.
The IMA 1 group binds three E1 links to transmit services from the NodeB. IMA 1 connects
to port 1 to port 3 on an ML1 board. NE1 has been configured with E1 port parameters based
on E1 link conditions.

Figure 6-15 Network diagram of IMA
IMA 1
R99
NodeB NE1

Data Preparation
Bound port 4-ML1-1 to 4-ML1-3 -
IMA Protocol Status Enabled If carried over a single E1,

ATM services from a base
station are transmitted and
received through UNIs. In
this case, the IMA protocol
must be disabled. If carried
over multiple E1s, ATM
services from a base station
are transmitted and received
through IMA links.
GAL enabled status Disabled If PWE3 services use

control words, MPLS-TP
PW OAM packets do not
necessarily carry generic
associated channel header
labels (GALs). Otherwise,
MPLS-TP PW OAM
packets must carry GALs.
IMA protocol version 1.1 Normally, set the IMA

protocol version, IMA frame
IMA frame length 128 length, IMA symmetric
IMA symmetric mode Symmetrical mode and mode, and differential delay
symmetrical operation tolerance of an NE (with
IMA protocol enabled)
Differentiated delay 25 consistently as those of its
tolerance interconnected equipment.

Clock mode ITC The clock modes must be

the same at both ends of an
IMA link. The default clock
mode for a NodeB is ITC.
Therefore, the clock mode is
set to ITC for the NE that is
interconnected with the
NodeB and the NE at the
opposite end of the IMA
link.
Procedure
Step 1 Bind an ATM trunk.
6
When some timeslots of multiple E1s are used to carry
ATM services between a PE and a CE, IMA must be
enabled. Each member in an IMA group must be 3
bound to at least three timeslots and the number of
bound timeslots must be the same.
Step 2 Configure an IMA group.

2
3
1. When multiple E1s are used to carry ATM services between a PE and a CE, IMA
must be enabled.
2. When some timeslots of multiple E1s are used to carry ATM services between a PE
and a CE, IMA must be enabled.
3. If only one E1 or some timeslots in one E1 are used to carry ATM services between
a PE and a CE, it is recommended to disable IMA, because using IMA in this case
increases the delay and brings no benefit.
4. The IMA status and IMA parameters must be set consistently for the PE and CE. 4
1
Step 3 Set ATM port parameters.
1. UNI: indicates an interface connected to a device on the user side. For example,
the user-side interfaces of a common ATM network or the user-side interfaces of
PEs on a PSN that carries ATM PWE3 services must be configured as UNIs.
2. NNI: indicates an interface connecting network-side devices. For example, the
network-side interfaces of a common ATM network must be configured as NNIs.
3. According of the ITU-T G.804, the payload (48 bytes) of an ATM cell must be
scrambled before being mapped to E1 signals. Therefore, it is recommended to
enable ATM Cell Payload Scrambling for devices at both ends of an ATM link.
4. The status of ATM Cell Payload Scrambling must be consistent at both ends of an
ATM link; otherwise, packets will be discarded.
----End
6.22 Configuration Example (ATM OAM)

This section uses an example to describe how to plan and configure ATM OAM according to
network conditions.

NOTE
OptiX RTN 905 does not support ATM OAM.

As shown in Figure 6-16, one ATM service is present between the NodeB and the RNC. The
details are provided as follows.
l The 4-ML1-1(TRUNK1) port on NE1 (NE ID: 120-1) receives an ATM service from the
NodeB. VPI = 1, and VCI = 15.
l The 4-ML1-1(TRUNK1) port on NE2 (NE ID: 120-2) receives the ATM service from
the RNC. VPI = 1, and VCI = 15.
l The PW between NE1 and NE2 transmits the ATM service. PW ID = 101.
To test service connectivity between NE1 and NE2, perform an LB test on NE1.

UNI UNI
VPI VCI VPI VCI
1 15 1 15
IMA PSN IMA RNC
PW ID=101
NodeB
NE1 NE2

Data Preparation
Segment and End Segment point For ATM services, the

Attribute segment point attributes for
each connection point must
be set.
Procedure
Step 1 Set the segment point attributes for the AIS/RDI.

Step 2 Query the LLID of NE2.
Query the LLID of NE2. Generally, the default LLID value of an NE is retained.
Ensure that each LLID is unique on the network.
Step 3 Start an LB test on NE1.

2
3
Configure the attributes of the LB test for ATM OAM

according to the plan.
----End
6.23 Configuration Example (ATM Traffic Management)

This section uses an example to describe how to plan and configure ATM traffic management
This example describes the configurations of ATM traffic management. For a complete
configuration example, see Configuration Example (ATM Connection-based ATM Services).
NOTE
OptiX RTN 905 does not support ATM traffic management.

As shown in Figure 6-17, one ATM service is present between the NodeB and the RNC. The
details are provided as follows.
l The 4-ML1-1(TRUNK1) port on NE1 receives an ATM service from the NodeB.
l The 4-ML1-1(TRUNK1) port on NE2 receives the ATM service from the RNC.
l The PW between NE1 and NE2 transmits the ATM service in the N-to-one encapsulation
mode.
l Each NodeB transmits 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). To ensure the QoS of
different services, the RTN equipment specifies different ATM policies for the services.

IMA IMA
RNC
PSN
PW
NodeB
NE1 NE2

Data Preparation
ATM policy information Table 6-16 provides the l It is recommended to

details. configure the ATM
traffic management
policy for the PE
according to the traffic
management policy
configured for the CE.
l The ATM traffic
management policy must
match the ATM service
bandwidth between the
PE and CE.
Table 6-16 ATM policy information
Parameter NE1 and NE2
CBR Service rt-VBR nrt-VBR UBR Service

Service Service
Service Type CBR RT-VBR NRT-VBR UBR
Traffic Type ClpTransparent ClpTransparent NoClpScr NoClpNoScr

NoScr Scr
Clp01Pcr(cell/s 175 1859 1859 1859

)
Clp01Scr(cell/s - 1685 1685 -

)

Parameter NE1 and NE2
CBR Service rt-VBR nrt-VBR UBR Service

Service Service
Max. Cell - 1000 1000 -

Burst Size
(cell)
Cell Delay 102400 10240 - -

Variation
Tolerance
(0.1us)
Procedure
Step 1 Create ATM policies on NE1 and NE2.
Take CBR services of NE1 as an example.
Step 2 Create an ATM service, and bind a corresponding ATM policy to each connection of the ATM
service.
l Specify upstream and downstream ATM policy 1 for the ATM connections of real-time
voice services and signaling (CBR services).
l Specify upstream and downstream ATM policy 2 for the ATM connections of OM
services and HSDPA real-time services (rt-VBR services).

l Specify upstream and downstream ATM policy 3 for the ATM connections of R99 non-
real-time services (nrt-VBR services).
l Specify upstream and downstream ATM policy 4 for the ATM connections of HSDPA
data services (UBR services).
Take CBR services of NE1 as an example.
----End

Feature Configuration Guide 7 Configuring Clock Features
7 Configuring Clock Features
About This Chapter

various clock features.
7.1 Configuration Procedure (IEEE 1588v2)

During the configuration of a network-wide time synchronization solution, NE Clock Type of
each NE needs to be set to OC or BC.
7.2 Configuration Process (ITU-T G.8275.1)
If using the ITU-T G.8275.1 protocol to implement time synchronization, all NEs must work
in telecom boundary clock (T-BC) mode.
7.3 Configuration Procedure (CES ACR)
Configurations of CES ACR at master equipment are different from those at slave equipment.
7.4 Configuration Procedure (IEEE 1588 ACR)
Configuration of IEEE 1588 ACR at master equipment is totally different from that at slave
equipment.
7.5 Configuration Example (Network-wide Time Synchronization )
This section uses an example to describe how to plan and configure IEEE 1588v2 network-
wide time synchronization according to network conditions.
7.6 Configuration Example (Transparent Transmission of Time Signals)
This section uses an example to describe how to plan and configure transparent transmission
of IEEE 1588v2 time signals based on network conditions.
7.7 Configuration Example (ITU-T G.8275.1)
This section provides an example of how to plan and configure ITU-T G.8275.1-compliant
time synchronization based on network conditions.
7.8 Configuration Example (CES ACR)
This section uses an example to describe how to plan and configure CES ACR according to
network conditions.
7.9 Configuration Example (IEEE 1588 ACR)
This section uses an example to describe how to plan and configure IEEE 1588 ACR

7.1 Configuration Procedure (IEEE 1588v2)

During the configuration of a network-wide time synchronization solution, NE Clock Type of
each NE needs to be set to OC or BC.
NOTE
Frequency synchronization is a prerequisite for time synchronization. When configuring IEEE 1588v2,
ensure that the time and clock have the same source (the same BITS for example).
Table 7-1 Flow for configuring IEEE 1588v2

2 A.12.3.2 Changing the Optional.

Mode for Selecting the When frequency synchronization by means of IEEE 1588v2 is
Frequency Source required, set Select Frequency Source Mode to PTP
Synchronization.
3 A.12.3.4 Setting the PTP Required.

NE Attributes l Set NE Clock Type according to the network plan. For the
OptiX RTN 950:
– If the NE is used for networkwide synchronization and only
one PTP port is required, set NE Clock Type to OC.
– If the NE is used for networkwide synchronization and
multiple PTP ports are required, set NE Clock Type to BC.
– If IEEE 1588v2 time signals need to be transparently
transmitted only between Ethernet ports, set this parameter
to TC.
– If IEEE 1588v2 time signals need to be transparently
transmitted across a radio link, set NE Clock Type to TC
+BC.
– If both time synchronization and transparent transmission of
IEEE 1588v2 time signals are required, set NE Clock Type
to TC+BC.
l Time synchronization can be achieved only when PTP Time
Adjustment is set to Enabled.
l It is recommended that you set Packet Multicast Mode to
Fully Multicasted.
l When Static BMC is Disabled, the NE uses the BMC
algorithm to establish the master-slave clock hierarchy. When
Static BMC is Enabled, static PTP clock selection method is
used. In this case, PTP port statuses need to be manually
specified.
NOTE
If Static BMC is set to Enabled for an NE, PTP clock ports on the NE
are in the INITIALIZING state by default and do not participate in
source selection. If a PTP clock port needs to participate in source
selection, you must set its status to MASTER, SLAVE, or PASSIVE
according to the clock network plan.

4 A.12.3.3 Querying or Optional.

Modifying the PTP l The PTP system clock must be set only when the NE functions
System Time as the grandmaster clock and the local real-time clock functions
as the timestamp.
In actual application, a PTP system clock should be introduced
from external time equipment. The clock is manually
configured to facilitate functionality tests.
l When the PTP time adjustment function is enabled, the system
clock will be automatically synchronized to an external time
signal or PTP time source.
5 A.12.3.5 Creating PTP Required.

Clock Ports Set an FE/GE/IF port that is used to transmit/receive IEEE 1588v2
packets as a PTP port.
l When NE Clock Type is set to OC, only one PTP port can be
created.
l When NE Clock Type is set to BC, multiple PTP ports working
in BC mode can be created.
l When Work Mode is TC, the Ethernet port can be created as a
PTP port whose working mode is TC.
l When NE Clock Type is set to TC+BC, multiple PTP ports can
be created. In this case, Clock Type of an IF port is always BC
and cannot be changed. Clock Type of an Ethernet port can be
set to TC or BC. A TC port transparently transmits IEEE
1588v2 time messages, and a BC port obtains time
synchronization or externally provides time through IEEE
1588v2 time messages.
6 A.12.3.6 Setting PTP Required.

Clock Port Attributes Associated attributes must be set for each PTP port.
l Set a VLAN ID for PTP packets according to a related plan.
l Set PTP Packet Encapsulation Format for PTP packets
according to a related plan. If a network comprises only Huawei
OptiX RTN equipment, it is recommended that you set PTP
Packet Encapsulation Format to PTPETH (L2
encapsulation).
l In the case of dynamic BMC-based source selection, the Port
Status value is the pre-selected PTP port status. In the case of
static source selection, the Port Status value is a manually
specified PTP port status.
NOTE
The IF port does not support setting PTP packet encapsulation format and
VLAN ID.


Parameters for PTP Clock Associated PTP packet parameters must be set for each PTP port.
Packets
l P/E Mode specifies the delay measurement mode of a port.
l The P/E Mode at both ends of a PTP link must be set to the
same.
l For an IF port, P/E Mode can only be set to P2P.
l For an Ethernet port, P/E Mode can be set to E2E or P2P.
– If the port is connected to an OC or BC NE, set this
parameter to E2E.
– If the port is connected to a P2P TC NE, set this parameter to
P2P. If the port is connected to an E2E TC NE, set this
parameter to E2E. However, P2P is recommended if both
modes are supported.
l Set periods for PTP packets according to a related plan.
8 A.12.3.8 Configuring the Optional.

Cable Transmission Offset l When propagation delay of a PTP link in Tx direction is
Between NEs different from that in Rx direction, set Cable Transmitting
Distance parameters to compensate for the time difference.
l Measure the time difference between an NE and the reference
time source, or the cable length difference between the Tx
direction and the Rx direction. Then, compensate for the
propagation delay on the cables at associated ports, at both ends
of the PTP link.
l Set Warp Direction. The value Positive indicates that the
receive link distance is longer than the transmit link distance
(that is, the transmission time over the receive link is longer
than that over the transmit link, and therefore the PTP time on
the slave NE is later than that on the master NE). The value
Negative indicates that the receive link distance is shorter than
the transmit link distance (that is, the transmission time over the
receive link is shorter than that over the transmit link, and
therefore the PTP time on the slave NE is earlier than that on
the master NE).
l Compensation for propagation asymmetry takes effect only for
slave ports.
9 A.12.3.9 Configuring a Optional.

PTP Clock Subnet Time synchronization by means of IEEE 1588v2 is only available
to the PTP equipment within a same clock subnet. When a physical
PSN needs to be divided into several clock domains, clock subnets
need to be configured. Otherwise, take the default value 0 for clock
domain ID.
10 A.12.3.10 Modifying the Optional.

BMC Algorithm When the internal clock of an NE is used as a BMC clock source,
Parameters for NE Clocks you can modify the BMC algorithm parameters.

11 A.12.3.11 Setting Basic Required when an NE needs to receive or transmit external time
Attributes of External signals.
Time Ports l Set Interface Mode to External Time Interface.
l When an NE needs to synchronize with an external clock, set
Direction to Ingress for the NE. When an NE needs to provide
an external clock with time synchronization information, set
Direction to Egress.
l Set Cable Transmitting Distance parameters based on actual
situations to compensate for propagation delay on the cable
connected to an external time port. It is recommended that you
set the parameters only on Rx equipment.
12 A.12.3.12 Setting BMC Required when an NE receives time synchronization signals

Algorithm Parameters for through an external time port.
External Time Ports Set BMC parameters required for clock source selection based on
the type of an external time signal source.
13 A.12.3.13 Setting the Required when an NE needs to receive or transmit external time
Cable Transmission Offset signals.
for External Time Ports l Set Cable Transmitting Distance parameters based on actual
situations to compensate for propagation delay on the cable
connected to an external time port.
l It is recommended that you set the parameters only on Rx
equipment. Set the parameters on Tx equipment only when Rx
equipment does not support compensation for propagation delay
on cables.
14 A.8.10.1 Setting IF Required when an IF port functions as a PTP port.

Attributes When air-interface synchronization or transparent transmission of
IEEE 1588v2 time signals is used, set Enable IEEE-1588
Timeslot to Enabled.
15 Configuring Ethernet Optional.

services l When the NE works in TC or TC+BC mode, IEEE 1588v2
packets are transparently transmitted as services.
Configure the transparent transmission of IEEE 1588v2 packets
during the configuration of Ethernet services. If the PTP clock
is deployed after the configuration of Ethernet services, you
need to especially configure forwarding services for PTP
packets.
7.2 Configuration Process (ITU-T G.8275.1)

If using the ITU-T G.8275.1 protocol to implement time synchronization, all NEs must work
in telecom boundary clock (T-BC) mode.

NOTE
Time synchronization is implemented based on frequency (clock) synchronization. If ITU-T G.8275.1 is

used, time and clock signals must be from the same source (such as the same BITS), and only physical-
layer frequency synchronization can be used.
Table 7-2 Process of configuring ITU-T G.8275.1

2 A.12.3.1 Configuring the PTP Profile Required.

Set PTP Profile to G.8275.1.
3 A.12.3.4 Setting the PTP NE Attributes Optional.

l Time synchronization is possible only
when PTP Time Adjustment is set to
Enabled.
l If Static BMC is Disabled, an NE
uses the best master clock (BMC)
algorithm to establish the master-slave
clock hierarchy. If Static BMC is
Enabled, the static PTP clock
selection method is used. In this case,
PTP port status must be manually
specified.
4 A.12.3.3 Querying or Modifying the PTP System Optional.

Time l Set the PTP system clock for an NE
only when the NE functions as the
grandmaster clock and uses the local
real-time clock as a timescale.
On the live network, a PTP system
clock is introduced from an external
time device. Manually configuring a
PTP system clock is often for the
function test purpose.
l If time calibration is enabled, a system
clock is automatically synchronized
with external time signals or a PTP
time source.
5 A.12.3.5 Creating PTP Clock Ports Required.

l Only a PTP port can transmit, receive,
and process PTP packets, thereby
obtaining and providing time
synchronization information.
l An FE, GE, or IF port can be
configured as a PTP port.
l Multiple PTP ports can be configured
on an NE that works in T-BC mode.

6 A.12.3.6 Setting PTP Clock Port Attributes Required.

l Set Not Slave to Enable.
l For an IF port, ensure that Enable
IEEE-1588 Timeslot is Enable.
NOTICE
Enable IEEE 1588 timeslots for IF ports
during microwave link commissioning. If
Enable IEEE-1588 Timeslot is
inconsistently configured for IF ports at
two ends of a microwave link, microwave
link configurations do not take effect or
services on the microwave link are
interrupted.
l It is advised to retain the default
values for the other parameters.
Local Priority indicates the local
priority of a clock source. If this
parameter is incorrectly configured,
clock tracing may be incorrect or even
a clock loop is formed. This parameter
can be modified only according to a
proper plan.
7 A.12.3.7 Setting Parameters for PTP Clock Packets Optional.

l It is advised to retain the default
values of PTP packet parameters.
l If necessary, modify PTP packet
parameters according to the network
plan and ensure that they are
consistently configured for
interconnected PTP ports.
l If using the ITU-T G.8275.1 protocol,
an Ethernet port supports only the
E2E mode. an IF port supports only
the P2P mode.

8 A.12.3.8 Configuring the Cable Transmission Offset Optional.

Between NEs l When propagation delay of a PTP link
in the transmit direction is different
from that in the receive direction, set
parameters on Cable Transmitting
Warp parameters to compensate for
the time difference.
l Measure the time difference between
an NE and the reference time source,
or the cable length difference between
the transmit direction and the receive
direction. Then, compensate for the
propagation delay on the cables at
associated ports, at both ends of the
PTP link.
l Set Warp Direction. The value
Positive indicates that the receive link
distance is longer than the transmit
link distance (that is, the transmission
time over the receive link is longer
than that over the transmit link, and
therefore the PTP time on the slave
NE is later than that on the master
NE). The value Negative indicates
that the receive link distance is shorter
than the transmit link distance (that is,
the transmission time over the receive
link is shorter than that over the
transmit link, and therefore the PTP
time on the slave NE is earlier than
that on the master NE).
l Compensation for propagation
asymmetry takes effect only for slave
ports.
9 A.12.3.9 Configuring a PTP Clock Subnet Optional.

l PTP time synchronization is only
available to PTP devices within a
same clock subnet. When a physical
PSN needs to be divided into several
clock domains, clock subnets must be
configured.
l If ITU-T G.8275.1 is used, Clock
Subnet No. must not be 0.

10 A.12.3.10 Modifying the BMC Algorithm Optional.

Parameters for NE Clocks When an internal clock on an NE is used
as a BMC clock source candidate, you
can modify the BMC algorithm
parameters for the internal clock.
NOTE
If static BMC is enabled, Not Slave, Local
Priority, and the other dynamical BMC
parameters do not take effect.
11 A.12.3.11 Setting Basic Attributes of External Time Required when an NE needs to receive or
Ports transmit external time signals.
l Set Interface Mode to External Time
Interface.
l If an NE needs to synchronize with an
external clock, set Direction to
Ingress. If an NE needs to provide
time synchronization information for
an external clock device, set Direction
to Egress.
l Set Cable Transmitting Distance
parameters based on actual situations
to compensate for propagation delay
on the cable connected to an external
time port. It is recommended that you
set the parameters only on Rx
equipment.
12 A.12.3.12 Setting BMC Algorithm Parameters for Required when an NE receives time
External Time Ports synchronization signals through an
external time port.
Set BMC parameters required for clock
source selection based on the type of an
external time signal source.
13 A.12.3.13 Setting the Cable Transmission Offset for Required when an NE needs to receive or
External Time Ports transmit external time signals.
l Set Cable Transmitting Distance
parameters based on actual situations
to compensate for propagation delay
on the cable connected to an external
time port.
l It is recommended that you set the
parameters only on Rx equipment. Set
the parameters on Tx equipment only
when Rx equipment does not support
compensation for propagation delay
on cables.

7.3 Configuration Procedure (CES ACR)

Configurations of CES ACR at master equipment are different from those at slave equipment.
Table 7-3 Flow for configuring CES ACR (Master)

1 A.12.2.1 Configuring a Required.

CES Transmit Clock NOTE
When master PEs use channelized STM-1 ports to
extract E1 clocks, the system extracts E1 line clocks
from peer CEs as output clocks by default. Therefore,
you do not need to set CES Encapsulation Clock Mode
for a channelized STM-1 port inputting E1 clocks.
Table 7-4 Flow for configuring CES ACR (Slave)

1 A.12.2.2 Configuring Configure the primary clock for an ACR clock

the Primary Clock for domain. Set the major parameters as follows.
an ACR Clock Set CES Service corresponding to ACR Clock
Domain Source.
2 A.12.2.3 Configuring Group the E1 ports with the same clock source and
Ports Using the Clock from the same Master into one clock domain.
Domain
3 A.8.6.2 Setting Required when slave PEs use Smart E1 ports to

Advanced Attributes restore E1 clocks.
of Smart E1 Ports Set Re-timing Mode of a Smart E1 port restoring
E1 clocks to Slave Mode.
NOTE
Only OptiX RTN 905 can use channelized STM-1 ports
to restore E1 clocks.
7.4 Configuration Procedure (IEEE 1588 ACR)

Configuration of IEEE 1588 ACR at master equipment is totally different from that at slave
equipment.

Table 7-5 Flow for configuring IEEE 1588 ACR

1 A.12.3.2 Changing Optional.

the Mode for l Regarding master equipment, set Select Frequency
Selecting the Source Mode to Physical Synchronization.
Frequency Source
l Regarding slave equipment, set Select Frequency
Source Mode to PTP Synchronization.
2 A.12.3.11 Setting Required when an NE needs to receive or transmit

Basic Attributes of external clock signals.
External Time Ports l Set Interface Mode to External Time Interface.
l When master equipment needs to synchronize with
an external clock, set Direction to Ingress.
l When slave equipment needs to provide its
interconnected equipment with external clock
signals, set Direction to Egress.
3 A.12.3.9 Configuring Optional.

a PTP Clock Subnet l Frequency synchronization by means of IEEE 1588
ACR is only available to the PTP equipment within
a same clock subnet. Therefore, master equipment
and slave equipment must be configured into a
same clock subnet.
l When a physical network needs to be divided into
several clock domains, clock subnets need to be
configured. Otherwise, take the default value 0 for
clock domain ID.
4 A.12.3.4 Setting the Required.

PTP NE Attributes It is recommended that you set this parameter to BC
for both master equipment and slave equipment.
It is recommended that you set Static BMC to
Disabled, wherein BMC algorithms determine the
master-slave clock hierarchy of the PTP network.
5 A.12.3.10 Modifying Required for master NEs.

the BMC Algorithm The clock source priority of the master NE must be
Parameters for NE higher than that of the slave NE. It is recommended
Clocks that you set Clock Source Priority 2 to 127 for the
master NE and retain the default value for the slave
NE.
6 A.12.3.5 Creating Required.

PTP Clock Ports Set an FE/GE/IF port that is used to transmit/receive
IEEE 1588v2 packets as a PTP port.
When NE Clock Type of an NE is set to OC, only one
PTP port can be created for the NE; when NE Clock
Type of an NE is set to BC, multiple PTP ports can be
created for the NE.

7 A.12.3.6 Setting PTP Required.

Clock Port Associated attributes must be set for each PTP port.
Attributes
l Set a VLAN ID for PTP packets according to a
related plan.
l Set PTP Packet Encapsulation Format for PTP
packets according to a related plan. If a network
comprises only Huawei OptiX RTN equipment, it is
recommended that you set PTP Packet
Encapsulation Format to PTPETH (L2
encapsulation).
l Set Enable ACR to Enabled for a PTP port on
slave equipment.

Parameters for PTP Set a same period for PTP packets from master and
Clock Packets slave equipment.
7.5 Configuration Example (Network-wide Time

Synchronization )
This section uses an example to describe how to plan and configure IEEE 1588v2 network-
wide time synchronization according to network conditions.

On the mobile backhaul network as shown in Figure 7-1, the OptiX RTN equipment provides
BTS101 (a CDMA base station) and BTS201 (a CDMA 2000 base station) with service
backhaul links, frequency synchronization signals, and time synchronization signals. The plan
for achieving frequency synchronization and time synchronization is provided as follows:
l NE11 achieves frequency synchronization with BSC2 by means of synchronous
Ethernet.
l NE11 achieves time synchronization with the BITS through its 1PPS+ToD time port.
l NE12 and NE13 achieve frequency synchronization with NE11 through air-interface
links.
l NE12 and NE13 achieve time synchronization with NE11 by means of IEEE 1588v2.
l BTS201 achieves frequency synchronization with NE13 by means of synchronous
Ethernet (because BTS201 is connected to NE13 through its FE port), and time
synchronization with NE13 by means of IEEE 1588v2 (because BTS201 supports the
IEEE 1588v2 protocol).
l BTS101 achieves frequency synchronization with NE13 by means of E1 signals
(because BTS101 is connected to NE13 through its IMA E1 port), and time
synchronization with NE13 through its 1PPS+ToD time port.

Figure 7-1 Network diagram of IEEE 1588v2

BSC2
GE 1PPS+TOD
FE
BTS 201 1PPS+TOD
ATM/IMA
NE13 NE12 NE11 BITS
1PPS+TOD
1PPS+TOD ATM/IMA
BTS 101
BSC1

This section describes the procedure for configuring network-wide time synchronization.
Data Preparation
Example Principle
Select frequency source mode Physical -

synchronization
(default value)
PTP NE attributes NE clock type BC -
Static BMC Disabled
PTP time adjustment Enabled (default

value)
Packet multicast Fully multicasted

mode (default value)
PTP clock port parameters See the following -

figure.
IEEE 1588v2 packet P/E Mode IF board: P2P -

parameters Ethernet board: E2E
SYNC packet period 8/1024

(s)
PDELAY packet -
period (s)


Example Principle
ANNOUNCE 128/1024
packet period (s)
ANNOUNCE 128/1024
packet period (s)
ANNOUNCE 3
packet timeout
coefficient
Basic attributes of external time ports See the following -

figure.
IF attributes Enable IEEE-1588 Enabled -

timeslot
Figure 7-2 Parameters for configuring PTP clock ports

Basic Attributes of External Time Ports:
Interface Mode: External Time Interface
Direction: Ingress
Interface Protocol Type: 1PPS+ToD
Interface Level: RS-422
BMC Algorithm Parameters for External Time Port:

Time Quality Level: 187
Time Precision: 254
Clock Source Type: GPS
Clock Source Priority 1: 128
Clock Source Priority 2: 127
Cable Transmission Offset for External Time Port:

Transmitting Length(m): 10.5m BSC2
Basic Attributes of External Time Ports:
Interface Mode: External Time Interface
Direction: Egress
Interface Protocol Type: 1PPS+ToD
Interface Level: RS-422 GE 1PPS+TOD
FE
BTS 201 1PPS+TOD
ATM/IMA
NE13 NE12 NE11 BITS
1PPS+TOD
1PPS+TOD 3-ISV3-1 ATM/IMA
BTS 101
4-ISV3-1
3-ISV3-1
4-ISV3-1
1-EM6FA-1 BSC1
PTP Clock Port Attributes:

PTP Packet VLAN: 4093
PTP Packet Encapsulation Format: E2E ETH
Procedure
Step 1 Change the mode for selecting the frequency source.

Step 2 Set PTP system time.

Step 3 Creating PTP clock ports.


Step 4 Set PTP clock port attributes.
Step 5 Set IEEE 1588v2 packet parameters.

Step 6 Set basic attributes of external time ports.

Step 7 Modify BMC algorithm parameters for external time ports.

Step 8 Set the cable transmission offset for external time ports.
Step 9 Set IF attributes.


----End
7.6 Configuration Example (Transparent Transmission of

Time Signals)
This section uses an example to describe how to plan and configure transparent transmission
of IEEE 1588v2 time signals based on network conditions.

Figure 7-3 shows a mobile backhaul network commonly used by multiple carriers.
l A mobile backhaul network needs to provide service backhaul links for base stations, as
well as frequency synchronization signals and time synchronization signals.
l RNC1, NodeB 101, NodeB 102, and BITS1 belong to carrier A.
l RNC2, NodeB 201, NodeB 202, and BITS2 belong to carrier B.
l Carrier A and carrier B use their own time sources, so the backhaul network needs to
transparently transmit IEEE 1588v2 time signals.
NOTE
In this example, carrier A and carrier B agree to frequency synchronization between their base stations.
Therefore, base stations can achieve frequency synchronization through the synchronous Ethernet, and
achieve time synchronization by means of IEEE 1588v2 transparent transmission.
If the base stations of carrier A and carrier B are not frequency synchronized, packet clocks such as the
ACR clock are used for synchronized to their own BITS clocks. When base stations are frequency
synchronized by means of ACR, packet clocks are transmitted as services by transmission equipment.

Figure 7-3 Networking diagram of IEEE 1588v2

BITS1
RNC1
NE31 NE21 NE11
PTP network
GE
GE GE GE GE
RNC2
NodeB NodeB NodeB NodeB BITS2

202 102 201 101
RTN 900 Radio link Ethernet link

This section describes the procedure for configuring transparent transmission of 1588v2 time
in TC+BC mode.
Data Preparation
Example Principle

synchronization
(default value)
PTP NE attributes NE clock type TC+BC -
Static BMC Disabled

value)


figure.
IEEE 1588v2 packet P/E Mode IF board: P2P -

parameters Ethernet board: E2E


Example Principle
PDELAY packet 1
period (s)
IF attributes Enable IEEE-1588 Enabled -

timeslot
Figure 7-4 Parameters for configuring PTP clock ports

Clock Type: BC
PTP Packet Encapsulation: PTP ETH
Clock Type: TC Clock Type: BC
PTP Packet VLAN: /
PTP Packet Encapsulation: PTP ETH PTP Packet Encapsulation: PTP ETH
PTP Packet VLAN: 4093 PTP Packet VLAN: /
4-ISV3-1
1-EM6FA-1 3-ISV3-1
1-EM6FA-2 1-EM6FA-1
RNC1
Clock Type: TC
PTP Packet Encapsulation: PTP ETH NE31 NE21 NE11
PTP network
Clock Type: BC
PTP Packet VLAN: /
3-ISV3-1
4-ISV3-1
RNC2
1-EM6FA-1
1-EM6FA-2
Clock Type: TC
RTN 900 Radio link Ethernet link
Procedure

Step 2 Set the PTP NE attributes.

Step 3 Create PTP clock ports.



The IF board of NE11 is used as an example.


The IF board of NE11 is used as an example.
Step 6 Set IF attributes.

Step 7 To configure Ethernet services for PTP messages, see theConfiguration Guide.
----End

7.7 Configuration Example (ITU-T G.8275.1)

This section provides an example of how to plan and configure ITU-T G.8275.1-compliant
time synchronization based on network conditions.

On the mobile backhaul network as shown in Figure 7-5, the OptiX RTN equipment provides
BTS101 (a CDMA base station) and BTS201 (a CDMA 2000 base station) with service
backhaul links, frequency synchronization signals, and time synchronization signals.
Wherein:
l NE11 implements frequency synchronization with BSC2 through synchronous Ethernet.
l NE11 implements time synchronization with the BITS through its 1PPS+ToD time port.
l NE12 and NE13 implement frequency synchronization with NE11 through air-interface
links.
l NE12 and NE13 implement time synchronization with NE11 through ITU-TG.8257.1.
l BTS201 implements frequency synchronization with NE13 through synchronous
Ethernet over FE ports, and time synchronization with NE13 through ITU-T G.8257.1.
l BTS101 implements frequency synchronization with NE13 through E1 signals over its
IMA E1 port, and time synchronization with NE13 through its 1PPS+ToD time port.
Figure 7-5 Networking diagram for ITU-T G.8257.1-compliant time synchronization

BSC2
GE 1PPS+TOD
FE
BTS 201 1PPS+TOD
ATM/IMA
NE13 NE12 NE11 BITS
1PPS+TOD
1PPS+TOD ATM/IMA
BTS 101
BSC1

This section describes the procedure for configuring ITU-TG.8257.1-compliant time
synchronization.

Data Preparation
Parameter Value in This Planning
Example Principle

synchronization
(default value)
PTP system clock NE clock type T-BC -

information
Static BMC Disabled

value)


figure.
G.8275.1 packet P/E Mode Ethernet board: E2E -

parameters
SYNC packet period 64/1024
(s)
PDELAY packet -
period (s)
ANNOUNCE 128/1024
packet period (s)
ANNOUNCE 128/1024
packet period (s)
ANNOUNCE 3
packet timeout
coefficient
Basic attributes of external time ports See the following -

figure.
IF attributes Enable G.8275.1 Enabled -

timeslot

Figure 7-6 PTP ports
Procedure
Step 1 Change Frequency Source Mode.

Step 2 Create a PTP clock port.

Step 3 Set the attribute for a PTP port on NE13.

Step 4 Set parameters for ITU-T G.8275.1 clock packets.
NOTE
In P/E mode, an Ethernet port supports only the E2E mode and an IF port supports only the P2P mode.
Step 5 Configure external time ports on NE11 and NE13.


Step 6 Set BMC algorithm parameters for the external time port on NE11.
Step 7 Set the cable transmission distance for external time ports.

----End
7.8 Configuration Example (CES ACR)

This section uses an example to describe how to plan and configure CES ACR according to
network conditions.

As shown in Figure 7-7, CES services need to transparently transmit clocks from the BSC to
BTS1 and BTS2, but the clocks of NE1 and NE2 are not synchronous. Therefore, NE1 and
NE2 need to be configured with CES ACR.
As a Slave, NE1 recovers clocks based on the SN information in the CES packets that are
received by port 1 on the ML1 board in slot 4, and transmits the clocks to port 2 on the ML1
board in slot 4. In this way, the clocks of BTS1 and BTS2 are synchronized with the clock of
the BSC.
Figure 7-7 Network diagram of CES ACR

CES service: CES_BTS1 CES service: CES_BSC1
E1
PSN E1
BTS1 CES
E1
E1
NE1 NE2 BSC
(Slave) (Master)
BTS2 4-ML1-1(to BTS1) 4-ML1-1(to BSC)
CES service: CES_BTS2 4-ML1-2(to BTS2) 4-ML1-2(to BSC) CES service: CES_BSC2


This section describes the procedure for configuring CES ACR.
Data Preparation
Figure 7-8 Parameters for configuring CES ACR

ACR Clock Source: 1-ML1-1
CES Service: CES_BTS1
Clock Domain: CES ACR1 Clock Domain
Retiming Mode: Slave Mode Retiming Mode: System Clock Mode
PSN
BTS1 CES
NE1 NE2 BSC

(Slave) (Master)
BTS2 4-ML1-1(CES_BTS1)
4-ML1-2(CES_BTS2)
Procedure
Step 1 On NE1 (Slave), configure the ports that use the CES ACR clock domain.
Step 2 On NE1 (Slave), configure the ports that use the CES ACR clock domain.

Step 3 Set advanced attributes of the ports inputting E1 clocks on NE2 (Master) and NE1 (Slave).
----End

7.9 Configuration Example (IEEE 1588 ACR)

This section uses an example to describe how to plan and configure IEEE 1588 ACR

On the mobile backhaul network as shown in Figure 7-9, NodeBs need to be clock-
synchronized with the RNC. The plan for achieving clock synchronization is provided as
follows:
l The OptiX RTN equipment achieves clock synchronization with the RNC/NodeBs by
means of synchronous Ethernet.
l The OptiX RTN equipment with microwave links in between achieves clock
synchronization with each other through air-interface links.
l NE13 and NE12 are interconnected through an asynchronous PSN, and therefore
physical-layer clock synchronization between them is impossible. Clock synchronization
by means of IEEE 1588 ACR, however, is available, because both NE12 and NE13
support the IEEE 1588v2 protocol.
Figure 7-9 Network diagram of IEEE 1588 ACR
FE
NodeB 1
NE14 PSN GE
NE13 NE12 NE11 RNC

(Slave) (Master)
FE
NodeB 2 NE15
Synchronous Radio link Radio link Synchronous

1588 ACR clock
Ethenet clock clock clock Ethenet clock

This section describes the procedure for configuring 1588 ACR.

Data Preparation
Figure 7-10 Parameters for configuring 1588 ACR

Select Frequency Source Mode: PTP Synchronization
Select Frequency Source Mode: Physical Synchronization
NE Clock Type: BC
NE Clock Type: BC
Static BMC: Disabled
Static BMC: Disabled
PTP Time Adjustment: Disabled
PTP Time Adjustment: Disabled
Packet Multicast Mode: Fully Multicasted
Packet Multicast Mode: Fully Multicasted
Protocol Packet Format: UBX
Protocol Packet Format: UBX
Clock Source Priority 2：128
Clock Source Priority 2：127
P/E Mode：E2E
P/E Mode：E2E
SYNC Packet Period (s): 8/1024
SYNC Packet Period (s): 8/1024
DELAY Packet Period (s): 128/1024
DELAY Packet Period (s): 128/1024
ANNOUNCE Packet Period (s): 128/1024
ANNOUNCE Packet Period (s): 128/1024
ANNOUNCE Packet Timeout Coefficient: 3
ANNOUNCE Packet Timeout Coefficient: 3
FE
NodeB 1
NE14 PSN GE
NE13 NE12 NE11 RNC

(Slave) (Master)
FE
NodeB 2 NE15
Synchronous Radio link Radio link Synchronous

1588 ACR clock
Ethenet clock clock clock Ethenet clock
1-EM6FA-1 1-EM6FA-1

Enable ACR: Enabled
Enable ACR: Enabled
Procedure

Step 2 Set PTP NE attributes.

Step 3 Modify the BMC algorithm parameters for NE clocks.


Step 4 Create PTP clock ports.


----End

Feature Configuration Guide 8 Configuring Maintenance Features
8 Configuring Maintenance Features
About This Chapter
This section provides hyperlinks to the configuration processes and examples for maintenance
features.
8.1 Configuration Procedure (RMON)

When applying the RMON, you need to perform different operations as required.
8.2 Configuration Process (IP Packet Coloring and Statistics Collection)
This section describes the process of configuring IP packet coloring and statistics collection,
including configuring roles for measurement points and service flow characteristics.
8.3 Configuration Example (RMON)
By using an example, this topic describes how to plan and configure the RMON according to
8.4 Configuration Example (IP Packet Coloring and Statistics Collection)
This section provides an example of how to plan and configure IP packet coloring and
statistics collection based on network conditions.
8.1 Configuration Procedure (RMON)

When applying the RMON, you need to perform different operations as required.

Table 8-1 Procedure of configuring the RMON

1 A.13.1 Browsing Required if the current performance events of the Ethernet

Current Ethernet port need to be browsed.
Performance l Select the Ethernet port and performance events for the
browsing operation.
l Set Sampling Period as required.
l If you need to browse over 10 performance events, set
Display Mode to List.
2 A.13.4 Browsing Required if the history performance events of the Ethernet

Historical port need to be browsed.
Ethernet l Set History Table Type as required.
Performance
Data l If you need to browse over 10 performance events, set
Display Mode to List.
3 A.13.3 Setting Optional.

Parameters for If you need to browse the history performance events or
Monitoring history alarm group in a self-defined period, set the history
Historical control group with a self-defined period.
Ethernet
Performance
A.13.2 Required if you need to specify certain alarms to be

Configuring monitored.
Ethernet Set the parameters according to the requirement.
Performance
Threshold-
Crossing
Parameters
8.2 Configuration Process (IP Packet Coloring and

Statistics Collection)
This section describes the process of configuring IP packet coloring and statistics collection,
including configuring roles for measurement points and service flow characteristics.
NOTE
Only OptiX RTN 950(CSHU/CSHUA), OptiX RTN 950A, OptiX RTN 905 1E/2E and OptiX RTN 910A
support this operation.

Table 8-2 Process of configuring IP packet coloring and statistics collection
1 A.9.12 Required.
Configuring IP l Ensure that service flow characteristics are
Packet Coloring consistently configured on upstream, intermediate,
and Statistics and downstream nodes.
Collection
l Verify that coloring bits are available before starting
IP packet coloring and statistics collection.
l The mark bit on the intermediate and downstream
nodes must be the same as that on the upstream
node.
l It is recommended that Auto Stop After (minutes)
for a downstream node be greater than that for an
intermediate node. Auto Stop After (minutes) for
an intermediate node is greater than that for the
upstream node.
8.3 Configuration Example (RMON)

By using an example, this topic describes how to plan and configure the RMON according to

As shown in Figure 8-1, the point-to-point private line service between NE2 and the RNC is
configured on the NE1. In the service transmission process, the RNC receives less traffic than
expected. If the regular alarm analysis fails to locate the problem, you need to use the RMON
function to locate the fault of the data service.

Tranparent transmission
E-LINE service
4-ISU2-1(to NE1) 4-ISU2-1(to NE2)
1-EM6F-5(to NodeB1) 1-EM6F-5(to RNC)
1-EM6F-6(to NodeB2)
NE2 NE1 RNC
NodeB1
NodeB2

8.3.2 Troubleshooting Analysis

This topic describes the basic thoughts when you use the RMON function to rectify Ethernet
faults.
Procedure
Step 1 Check the traffic of each Ethernet port and IF board along the signal flow of the faulty
service, to determine the port where the fault occurs.
l If the traffic transmitted from the transmit port is almost equal to the traffic received at
the receive port, it indicates that no anomalies occur.
l If the traffic transmitted from the transmit port is largely different from the traffic
received at the receive port, it indicates that an anomaly occurs.
Step 2 Browse the count of the performance threshold-crossing events at the faulty port, and
determine the cause of the fault. For details on operations, see the description of the RMON
alarms and performance events in the Alarms and Performance Events References.
Step 3 Rectify the fault. For details on operations, see the description of the RMON alarms and
performance events in the Alarms and Performance Events References.
----End
8.3.3 Troubleshooting Flow

This topic describes how to rectify service faults.
Procedure
Step 1 Count the received packets and transmitted packets of each Ethernet port and IF board during
the same period. For details on operations, see Browsing the Performance Data in the
History Group of an Ethernet Port.
The result is as follows:
l The traffic transmitted from NodeB1 is almost equal to the traffic received at 1-EM6F-5
on NE2. The traffic transmitted from NodeB2 is almost equal to the traffic received at 1-
EM6F-6 on NE2.
l The sum of traffic transmitted from 1-EM6F-5 and 1-EM6F-6 on NE 2 is almost equal to
the traffic received at 4–ISU2–1 on NE2.
l The traffic transmitted from 4–ISU2–1 on NE2 is almost equal to the traffic received at
4–ISU2–1 on the opposite NE1.
l The traffic transmitted from 4–ISU2–1 on NE1 is almost equal to the traffic received at
1-EM6F-5 on NE1.
l The traffic received at the RNC is largely different from the traffic transmitted from 1-
EM6F-5.
Thus, it can be inferred that the link between NE1 and the RNC is faulty.
Step 2 Browse the abnormal events of the RNC and NE1.
It is found that the RNC and NE1 report the abnormal event indicating the RMON module
performance higher than the upper threshold for many times. The abnormal event is caused by
an RMON entry, namely, the received fragmented packet (ETHFRG). See the Alarms and
Performance Events References, and the possible causes of the fault are as follows:

l The devices at both ends work in different modes.

l A hardware fault occurs at the local end.
Step 3 See the Alarms and Performance Events References for handling the fault.
1. Query the Ethernet working mode of the 1-EM6F-5 port on NE1 and the Ethernet port
on the RNC. For details on operations, see A.8.8.1 Setting the Basic Attributes of
Ethernet Ports in the Configuration Guide.
The Ethernet ports on NE1 and the RNC work in different modes.
2. Change the working mode of the 1-EM6F-5 port on NE1 so that it can work in the same
mode as the Ethernet port on the RNC. For details on operations, see A.8.8.1 Setting the
Basic Attributes of Ethernet Ports in the Configuration Guide.
----End
8.4 Configuration Example (IP Packet Coloring and

Statistics Collection)
This section provides an example of how to plan and configure IP packet coloring and
statistics collection based on network conditions.
NOTE
Only OptiX RTN 950(CSHU/CSHUA), OptiX RTN 950A, OptiX RTN 905 1E/2E and OptiX RTN 910A
support this operation.

The network shown in Figure 8-2 contains NE1, NE2, and NE3. Two services are configured:
QinQ-based E-Line service (service flow 1) and VLAN-based E-Line service (service flow 2).
The packet loss ratios of service flows 1 and 2 need to be tested using the IP packet coloring
and statistics collection function.
IP packet coloring and statistics collection must be separately configured for service flows 1
and 2. Coloring instances and statistics collection can be configured at points A, B, and C.
Specifically:
l For service flow 1, VUNI packet coloring and statistics collection needs to be configured
at point A (upstream), QinQ packet c statistics collection needs to be configured at point
B (intermediate), and VUNI packet restore and statistics collection needs to be
configured at point C (downstream).
l For service flow 2, VUNI packet coloring and statistics collection needs to be configured
at points A (upstream), VUNI packet statistics collection needs to be configured at points
B (intermediate), and VUNI packet restore and statistics collection needs to be
configured at point F (downstream).

Figure 8-2 Networking diagram for IP packet coloring and statistics collection

This section describes the procedure for configuring IP packet coloring and statistics
collection.
Data Preparation
The following tables provide parameter settings planned for service flow 1 based on service
requirements.
Table 8-3 Parameter settings planned for service flow 1

Parameter Point A Point B Point C
Name Test1 Test1 Test1
Set IP mark bits IP FLAG BIT0 IP FLAG BIT0 IP FLAG BIT0
Role Upstream Intermediate Downstream
Action Mark and collect Collect only Restore and collect
Logical Relation And And And

Between Matched
Rules
Match Type Outer VLAN Outer VLAN Outer VLAN
Auto Stop After 5 6 7

(minutes)
VUNI measurement point
Direction Receive - Transmit
Service 1-service-1 - 1-service-1
Port 2-ISM6-2(RTNIF-2) - 2-
ISM6-2(RTNIF-2)

VLAN 100 - 100
QinQ measurement point
Direction - Receive -
Service - 1-service-1 -
QinQ Link - 2- -
ISM6-2(RTNIF-2):
VLAN:100
The following tables provide parameter settings planned for service flow 2 based on service
requirements.
Table 8-4 Parameter settings planned for service flow 2

Name Test2 Test2 Test2
Set IP mark bits IP FLAG BIT0 IP FLAG BIT0 IP FLAG BIT0
Role Upstream Intermediate Downstream
Action Mark and collect Collect only Restore and collect
Logical Relation And And And

Between Matched
Rules
Match Type Outer VLAN Outer VLAN Outer VLAN
Auto Stop After 5 6 7

(minutes)
VUNI measurement point
Direction Receive Receive Transmit
Service 1-service-2 1-service-2 1-service-2
Port 3-ISV3-1(RTNIF-1) 3-ISV3-1(RTNIF-1) 3-

ISV3-1(RTNIF-1)
VLAN 110 110 110
Procedure
Step 1 Set parameters for IP packet coloring and statistics collection.
The following uses configurations for service flow 1 on node C as an example.

NOTICE
Do not start IP packet coloring and statistics collection immediately after setting the
parameters. Verify that coloring bits are available before starting IP packet coloring and
statistics collection.
Step 2 Check whether coloring bits are available.

1. Set Action to Collect Only for each node. Click Apply and Start. An upstream node is
used as an example.

2. If Number of Market Packets for each node is 0, the coloring bit is available.
Otherwise, the coloring bit must be re-configured consistently for the upstream,
intermediate, and downstream nodes.
Step 3 Start IP packet coloring and statistics collection.

Set Action to Mark and collect for the upstream node, and to Restore and collect for the
downstream node. Click Apply and Start. An upstream node is used as an example.
NOTICE
IP packet marking and statistics collection must be enabled for downstream, intermediate, and
upstream nodes sequentially within one minute.
Step 4 Check the result and calculate the packet loss ratio for the service flow.
After the time specified by Auto Stop After (minutes) expires or a test is manually stopped,
Status changes to Stop. This indicates that IP packet coloring and statistics collection ends,
and you can check the result. The following uses the query of the result for service flow 1 on
node C as an example.

NOTE
You can calculate the packet loss ratio for the tested service flow on the entire or segment link.
Packet loss ratio on the link between the upstream node and downstream node = (Number of Market
Packets for the upstream node - Number of Market Packets for the downstream node)/Number of
Market Packets for the upstream node You can calculate the packet loss ratio for the link between the
upstream node and the intermediate node, and that for the link between the intermediate node and the
downstream node in a similar way.
----End

Feature Configuration Guide A Task Collection
A Task Collection
This document describes various tasks involved in this document.

A.1 U2000 Quick Start
The U2000 quick start guide helps to learn about basic operations on the U2000client.
A.2 Web LCT Quick Start
The Web LCT quick start guide helps to learn about basic operations on theWeb LCT.
A.3 Network Management
Network management involves topology management, communication management, and
security management.
A.4 Security Management
Security management is important in network management.
A.5 Managing Radio Links
Before you configure the radio link between two microwave sites, configure the information
about the radio link.
A.6 Managing the MSP
This section provides the operation tasks associated with MSP. Only the OptiX RTN 980
supports the Two-Fiber Bidirectional Ring MSP.
A.7 Managing TDM Services
The TDM services involve the SDH service and the PDH service.
A.8 Managing Ports
Setting correct port parameter is the basis of configuring ports that transmit services.
A.9 Configuring Native Ethernet Services and Features
Configurations of Native Ethernet services and features include Ethernet port, protection,
service, protocol, and OAM configurations.
A.10 Configuring Ethernet Services and Features on the EoS/EoPDH Boards
Configurations of Ethernet services and features on the EoS/EoPDH boards include relevant
Ethernet port configuration, protection configuration, service configuration, protocol
configuration, and OAM configuration.
A.11 Managing MPLS/PWE3 Services and Features
The OptiX RTN 900 supports multiple MPLS/PWE3 services and features.
A.12 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you
need to manage the NE clock.
A.13 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.
A.1 U2000 Quick Start

The U2000 quick start guide helps to learn about basic operations on the U2000client.
A.1.1 Logging in to a U2000 Client

The U2000 uses the client/server architecture and allows multiple clients; you can log in to
the U2000 server by means of a U2000 client to manage OptiX RTN NEs.
Prerequisites
l The U2000 system has been started on the U2000 server.
l The IP address of the U2000 client is in the access control list (ACL) configured in the
U2000 system.
l The U2000 client has proper communication with the U2000 server.
Tools, Equipment, and Materials

U2000
NOTE
The Web LCT does not support this operation.
Procedure
Step 1 Double-click the U2000 client icon on the desktop.
Step 2 In the Login dialog box, set User Name and Password.
Step 3 Select the desired U2000 server from the Server drop-down list.
Step 4 Click Login.

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
NOTE
Procedure
Step 1 Choose File > Exit from the Main Menu.
The Confirm dialog box is displayed.
Step 2 Click OK to shut down the U2000 client.
NOTE
If the main topology has changed but the changes have not been stored, a dialog box will be displayed
asking whether to update the main topology. The U2000 client is shut down after you determine whether
to update the main topology.
----End
A.1.3 Using Online Help

Online Help provides help information about the U2000.
Prerequisites

U2000
NOTE

Procedure
Step 1 Choose Help > Help Topics from the Main Menu.
The Online Help page is displayed.
NOTE
When using the U2000client, press the F1 key to quickly display the related Online Help page.
----End
A.1.4 Navigating to Common Views

This section describes the main views on the U2000 and their functions.
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
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.
A.2.1 Using Online Help

Online Help provides help information about the Web LCT.
Prerequisites

Web LCT
NOTE
The U2000 does not support this operation.
Procedure
Step 1 In NE List, click .

The Online Help page is displayed.
NOTE
When using the Web LCT, press the F1 key to quickly display the related Online Help page.
----End
A.2.2 Navigating to the NE Explorer

The Web LCT provides the NE Explorer view to support users' management on equipment.
The NE Explorer view consists of the Function Tree pane, the Object Tree pane, and the
configuration interface.
Prerequisites

Web LCT

NOTE
The U2000 does not support this operation.
Procedure
Step 1 In NE List, select the NE to which you are logged in and click NE Explorer at the lower
right corner.
The NE Explorer view is displayed.
NOTE
l To quickly navigate to the view displaying current alarms, click .
l To quickly navigate to the NE List view, click .
l To quickly navigate to Online Help, click .

NOTE
You can also navigate to the NE Explorer view using the following methods:
l In NE List, right-click the NE to which you are logged in and choose NE Explorer from the shortcut
menu.
l In NE List, double-click the NE to which you are logged in.
----End
A.3 Network Management

Network management involves topology management, communication management, and
security management.
A.3.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS.
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.
l You must be an NM user with NE operator authority or higher.

U2000

Procedure
Step 1 Choose File > Discovery > NE from the Main Menu.
Step 2 Select Transport NE Search tab.
Step 3 Select Search Mode.

NOTE
l If the U2000 server and the gateway NE are in the same network segment, it is recommended that you set
Search Mode to IP auto discovery.
l In other scenarios, it is recommended that you set Search Mode to Search for NE.
If... Then...
Search Mode is set to Search for NE Perform Step 4 to Step 7.
Search Mode is set to IP auto discovery Perform Step 8 to Step 10.
Step 4 If Search Mode is set to Search for NE, you need to add a search domain.
1. Click Add, and then the Input Search Domain dialog box is displayed.
2. Select an address type and enter the search address.
NOTE
– When Address Type is set to IP Address of GNE or IP Address Range of GNE, and the U2000
server and gateway NE are not in the same network segment, ensure that the IP routes of the
network segments to which the U2000 server and gateway NE belong are configured on the U2000
and related routers.
– 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.
3. Click OK.
Step 5 Repeat Step 4 to add several search domains.
Step 6 In the Search for NE dialog box, perform the operations described in the Note part.
NOTE
l If Create NE after search is selected, you need to specify NE User and Password.
l You can select either Create NE after search or Upload after Create or both Create NE after search
and Upload after Create. In this manner, after the NE searching is complete, the system automatically
creates an NE and uploads the NE.
Step 7 Click Next, and then the Transport NE Search dialog box is displayed.
After the search is complete, all the NEs that are found are displayed in the Result list.

Step 8 If Search Mode is set to IP auto discovery, enter NE User and Password.
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.


Web LCT
Procedure
Step 1 Click NE Search in NE List and select a desired search type.
If... Then...
All NEs are directly connected to the NMS server through Perform Step 2 to Step 5.
Ethernet cables
Not all NEs are directly connected to the NMS server Perform Step 6 to Step 11.
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. Click Search.

2. After the Web LCT finds the NEs to be managed, click End Search.
NOTE
In the IP auto discovery mode, the Web LCT searches for the gateway NE and non-gateway NEs that are
managed by the gateway NE in the network segment where the server resides.
Step 8 Optional: If you select Search NE, then:

1. Click Manage Domain.
The Manage Domain Search dialog box is displayed.
2. Optional: Click Add to add a network segment. Then, set Domain Type and Domain
Address.
3. Optional: Select an existing network segment and click Modify to modify the network
segment.
4. Optional: Select an existing network segment and click Delete to delete the network
segment.
5. Click Search.
6. After the WebLCT finds the NEs, click End Search.
NOTE
During initial configuration, Manage Domain takes the default value of 129.9.255.255. After the IP
address of the gateway NE is changed, the value of Manage Domain also needs to be changed. The
default network segment cannot be modified or deleted.
Step 9 Select the NE that needs to be added and click Add NE.
A dialog box is displayed, indicating that the NE is added successfully.
Step 10 Click OK.
A new NE has been added to the NE list.
Step 11 Click Cancel.
----End
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.

l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be

created belongs must be created.

U2000
Procedure
Step 1 Choose File > 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 Proceed to the next step.
Gateway
The Gateway Type parameter is set to Non- Select the gateway to which the NE
Gateway 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.

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.
l If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be
created belongs must be created.

Web LCT
Procedure
Step 1 In NE List, click Add NE. Then, select Europe.
Step 2 Set the NE parameters.
NOTE
l The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.

l ID indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique on the
networks that are managed by the same NMS.
l Do not change the Extended ID when the number of actual NEs does not exceed the range permitted by
the basic NE ID.
l Set the parameters according to the network plan.
l The default user name is lct, and its corresponding password is Changeme_123.

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.

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.

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

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


GE optical module
CD1 STM-1 optical module


GE optical module
Table A-3 RTN 950

EM6F/EM6FA FE optical module

GE optical module
EMS6 GE optical module

SL1D/SL1DA/CQ1 STM-1 optical module


EG4/EG4P/EM6D FE optical module

GE optical module
EM6 FE optical module

FE electrical module
GE optical module
Table A-4 RTN 950A


GE optical module


EG4/EG4P/EM6D FE optical module

GE optical module

GE optical module
Table A-5 RTN 980


GE optical module

SL1D/SL1DA/CQ1 STM-1 optical module


GE optical module

SL4D STM-1 optical module

STM-4 optical module
EG2D GE optical module
EX1 10GE optical module

NOTE
Only RTN 980 housing CSHNA boards support
EX1 boards.
EX1(logical board) 10GE optical module
Table A-6 RTN 980L
EM6F FE optical module

GE optical module



GE optical module
SL4D STM-1 optical module

STM-4 optical module
EX1(logical board) 10GE optical module
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.
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 are used as system control, timing, and switching boards, the
backplane bus rate can be increased to 2.5 Gbit/s.
Prerequisites
l Only the RTN 950 using SL92CSH as the system control, timing, and switching board
supports this operation. For the RTN 950 using CSHU/CSHUA, the default backplane
bus rate is 2.5 Gbit/s.
l All the boards have been installed correctly.

U2000

NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and then choose
Configuration > NE 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.
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
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
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.
l When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.


U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the
Main Menu.
Step 2 Click the NE Time Synchronization tab.
Step 3 In the physical view, select the NE whose time needs to be synchronized, and then click
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is
successful. Click Close.
Step 5 When you need to synchronize the NE time with the NMS time, set the time synchronization
mode and the related parameters.
1. Optional: The NE time is synchronized with the NMS time immediately.
a. Right-click the NE whose time needs to be synchronized, and then choose
Synchronize with NM Time from the shortcut menu.
b. In the displayed confirmation dialog box, click Yes.

c. Close the displayed operation result dialog box.
2. Set Synchronous Mode to NM.
3. Click Apply.
4. Optional: Set auto synchronization parameters.
a. Set auto synchronization parameters.
b. Click Apply.
c. In the displayed confirmation dialog box, click Yes.
d. Close the displayed operation result dialog box.
NOTE
l When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM.
l When you need to synchronize the NE time with the time on the NTP server, set Synchronous Mode to
Standard NTP. Configure Standard NTP Authentication according to the requirements of the NTP
server.
Step 6 When you need to synchronize the NE time with the time on the NTP server, set the time
synchronization mode and the related parameters.

1. Set Synchronous Mode to Standard NTP.

2. Configure Standard NTP Authentication according to the requirements of the NTP
server.
3. Click Apply.
4. Click Close. The dialog box that is displayed indicating the operation result is closed.
5. Configure the upper-layer NTP server.
a. Select the NE, right-click in the configuration box where the standard NTP server is
configured, and then choose New.
b. Configure the parameters related to the NTP server.
c. Click Apply.
6. Optional: Copy the configuration of the upper-layer NTP server.
NOTE
Before the copy operation, set Synchronous Mode to Standard NTP for the source NE and the target
NE.
a. Select the NE to be copied, right-click, and then choose Copy Standard NTP
Server.

b. Select the NE to be pasted, right-click, and then choose Paste Standard NTP
Server.
c. In the displayed confirmation dialog box, click Yes.
----End
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.
l When you need to synchronize the NE time with the time on the NTP server, the time on
the NTP server must be set correctly and the NTP protocol must be normal.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE
Time Synchronization from the Function Tree.
Step 2 Set the synchronous mode.
If... Then...
You set Synchronous Mode to NULL Set the relevant parameters, and then click Apply.
You set Synchronous Mode to NM Set the relevant parameters, and then click Apply
to perform Step 5.
You set Synchronous Mode to Set the related parameters, and then click Apply to
Standard NTP perform Step 3.
NOTE
If you only need to synchronize the NE time and do not need to change the type of synchronization or
parameters, select the synchronization option corresponding to the NE, right-click, and choose Synchronize
with NM Time.
Step 3 Configure the upper-layer standard NTP server of the NE.

1. Click the Standard NTP Server tab. In the Standard NTP Server tab page, click Add.
2. After setting the parameters of the standard NTP server, click OK.

NOTE
l If the NE is a gateway NE, set the external NTP server as the standard NTP server.
l If the NE is a non-gateway NE, set the gateway NE as the standard NTP server.
Step 4 Optional: Configure standard NTP keys.

1. Click the Standard NTP Key Management tab.
2. Click Add.
The Add Key dialog box is displayed.
3. After the related parameters are configured, click OK.
Step 5 Optional: Set Start Time and click Apply.
----End
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
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.
l Synchronous Mode must be set to Standard NTP and Standard NTP Authentication
must be set to Enabled.
l The NTP protocol must be running properly and the NTP identity authentication must be
enabled on the NTP server.

U2000
NOTE
Configuring standard NTP keys using the Web LCT is performed during 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.

Step 5 After the related parameters are configured, click OK.
----End
A.3.1.16 Configuring NE Anti-Theft

To prevent use of boards of an NE after they are stolen, configure NE anti-theft.
Prerequisites
l The NE supports anti-theft. For details, see Availability.
Tools, Instruments, and Materials

U2000
NOTE

Context
l The RTN 950 housing CST/CSH boards, the RTN 980 housing CSHN/CSHNA boards
and the RTN 905 1A/2A/1C do not support this operation.
Procedure
Step 1 Choose Administration > NE Security Management > NE Anti-theft from the main menu.
NOTE
In the NE Explorer, select the NE from the Object Tree and then choose Security > NE Anti-theft
Management from the Function Tree.
Step 2 In the Add RSA Keypair dialog box that appears, configure a user name.
NOTE
After the user name is configured, it cannot be modified.
NOTE
Step 3 Click Export RSA Key to back up the stored RSA key.

NOTE
Step 4 Click Export Public Key to back up the public key.
NOTE
Step 5 In the physical view, select the NE that requires anti-theft, and then click .
NOTE
Step 6 Enable anti-theft and configure anti-theft policies.
NOTE
Before performing Web LCT operations, import the temporary certificate exported from the U2000 to the NE.
Step 7 Click Apply.
----End

A.3.1.17 Querying the Anti-Theft Status of Boards

You can query the anti-theft status of an NE or boards of an NE.
Prerequisites

U2000
NOTE
Context
l The RTN 950 housing CST/CSH boards, the RTN 980 housing CSHN/CSHNA boards
and the RTN 905 1A/2A/1C do not support this operation.
Procedure
Step 1 Choose Administration > NE Security Management > NE Anti-theft from the main menu.
NOTE
In the NE Explorer, select the NE from the Object Tree and then choose Security > NE Anti-theft
Step 2 Click Query Board Anti-theft State.
Step 3 In the physical view, select the required NE and click .

NOTE
Step 4 Click Query.
----End
Result
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.

U2000
NOTE
Procedure
Step 1 Select the corresponding operation steps according to the NE status.
If... Then...
An NE is not configured and the NE data In the Main Topology, double-click the NE
needs to be uploaded. that is not configured, and then perform Step
2 through Step 4.
An NE is configured with data and NE Perform Step 5 through Step 8.
data needs to be uploaded.
Step 2 In the displayed NE Configuration Wizard dialog box, select Upload, and then click Next.
A dialog box is displayed for confirmation.
Step 3 Click OK.
Step 4 Click Close.
Step 5 Choose Configuration > NE Configuration Data Management from the Main Menu.
Step 6 Select the NE whose data needs to be uploaded from the Object Tree, and then click
.
Step 7 Select the NE, click Upload. In the displayed confirmation dialog box, click OK.
The uploading is started. After the uploading is complete, the Operation Result dialog box is
displayed.
Step 8 Click Close.
----End
A.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 You must be an NM user with NE maintainer authority or higher.
l The NE is created.
l The NE is in unsynchronized state.
NOTE
When an NE is in unsynchronized state, it carries the mark.

U2000
NOTE
Procedure
Step 1 Method 1:
1. Choose Configuration > Synchronize NE 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
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
– 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.
4. Click Apply. Close the displayed dialog box.
----End

A.3.4 Suppressing Alarms for Monitored Objects

This section describes how to suppress specific alarms for a specific monitored object.
Prerequisites
Tools, Instruments and Materials

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
Step 3 Set Monitored Object and click Query.

Step 4 Set Status in Alarm Suppression.
Step 5 Click Apply.
Step 6 Close the dialog box that is displayed.
NOTE
----End
A.3.5 Connecting Fibers or Cables

To implement the end-to-end management on the NMS, you need to connect fibers or cables.

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 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.
Prerequisites
l The relevant boards of various NEs must be created on the NMS.
l The resources of port IP addresses must be created if the automatic allocation of port IP
addresses is enabled.

U2000
NOTE
Procedure
Step 1 In the Main Topology, select the icon . Then, the cursor is displayed as "+".
Step 2 Click the source NE of a fiber in the Main Topology.
Step 3 In the Select Fiber/Cable Source dialog box, select the source board and source port.
Step 4 Click OK. In the Main Topology, the cursor is displayed as "+".
Step 5 Click the sink NE of the fiber in the Main Topology.
Step 6 In the Select Fiber/Cable Sink dialog box, select the sink board and sink port.
Step 7 Click OK. Set the attributes of the fiber in the Create Fiber/Cable dialog box.
Step 8 Click OK. Then, the created fiber is displayed between the source NE and the sink NE in the
Main Topology.
----End
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.

l All Ethernet links are functioning properly.
l Port Mode at both ends of each Ethernet link is Layer 2 or Layer 3.

U2000
NOTE
Context
A microwave link is generally not imported to fibers/cables unless IP addresses need to be
automatically assigned at both ends of the microwave link. After IP addresses are assigned,
you need to delete the fibers/cables that the microwave link is imported by choosing File >
Discovery > Fiber/Cable/Microwave Link from the main menu.
Procedure
Step 1 Choose File > Discovery > Link from the main menu.
Step 2 Select the NE for which Ethernet links need to be searched from the Function Tree on the left
pane and click .

Step 3 Select one or multiple types of links to be searched for from three types: Links note exist in
the NMS, Links exist in the NMS, 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
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.
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.
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.
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.
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
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

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Step 2 Click the DCC Rate Configuration tab.
Step 3 Optional: Change the enable status of the DCC.

1. Double-click the cell in the Enabled/Disabled column to which the DCC corresponds.
Select the required state from the drop-down list.
2. Click Apply.

Step 4 Optional: Change the protocol type of the DCC.

1. Double-click the cell in the Protocol Type column to which the DCC corresponds.
Select the required protocol type from the drop-down list.
2. Click Apply.
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.
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
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.
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
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

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
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.
3. Click Apply.
4. Click OK.
----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
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.

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.
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
You must be an NM user with NE administrator authority or higher.

U2000
NOTE
Procedure
Step 2 Click the Multi-area OSPF Management tab.
Step 3 Optional: Add a Network to an OSPF area.

1. Select the OSPF area to add a Network.
2. In Network Segment, click Add.
The Add dialog box is displayed.

3. Set the IP address and subnet mask of the new Network.
NOTE
4. Click OK.
Step 4 Optional: Change a Network of an OSPF area.
1. In Network Segment, change the IP address and subnet mask of the target Network.
2. Click Apply.
----End
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. In OSPF Area, select the area where routes need to be manually aggregated and set
Automatic Route Aggregation to Disabled.
2. Click Apply.
Step 4 In Manual Route Aggregation, click Add.
The Add dialog box is displayed.
Step 5 Set the IP address and subnet mask of the Network where routes are manually aggregated.

NOTE
Step 6 Click OK.
----End
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.
1. Click the OSPF Parameter Settings tab.
2. Set Authentication Type and Authentication Password.
NOTE
l If Authentication Type is set to none, all preset authentication passwords are cleared.
l MD5 Key is available only when Authentication Type is MD5.

Step 4 Click Apply.
----End
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.
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.

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

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

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.

NOTE
l Alternatively, you can select the NE for which a standby gateway NE needs to be configured, right-
click the NE, and select the desired gateway NE from the drop-down list.
l You can select several NEs for which a standby gateway NE needs to be configured, right-click the
NE, and select the desired gateway NE from the drop-down list.
NOTE
l If more than one standby gateway NE is required, set GNE3 and GNE4.
l If the main gateway NE fails, GNE2 takes over. If GNE2 fails, GNE3 takes over. If GNE3 fails,
GNE4 takes over.
l During a switch between gateway NEs, communication may be interrupted but services are not
affected.
Step 5 Click Apply. Then, close the operation result dialog box that is displayed.
----End
A.3.8 Configuring the NMS Port

This section describes how to configure the NMS port, therefore ensuring normal NMS port
functioning and network security.
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.
l If you need to initialize an NE or perform software loading by using the LCT, the LCT
needs to access the NE through Ethernet ports.
l 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.

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 E-
LAN 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.

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 third-
party 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.

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

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/CSHNU), 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.

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.
l For security of NE data, NE users are assigned operation rights based on their
responsibilities.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User
Management from the Function Tree.A dialog box is displayed, indicating that the operation
is successful.
Step 2 Close the dialog box.
NOTE
Step 3 Click Add.

The Add NE User Attribute/Value dialog box is displayed.
Step 4 Set the parameters of the NE user according to the network plan.

NOTE
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.
l An online user can change the password of a user at a lower level.


U2000
NOTE
NOTE
Periodically change the password of an NE user to avoid password leaks.
Procedure
is successful.

NOTE
Step 3 Select the required NE user from the NE user management list, and click Set Password.
The Set Password of NE User dialog box is displayed.
Step 4 Input New Password, and input it again in Confirm Password.
----End
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.

Prerequisites
l An NE user has been created.
l The current online NE user is of a higher level than the NE user whose additional user
information will be configured.

U2000
NOTE
Procedure
is successful.

NOTE
Step 3 Click View Additional User Info.

The Additional User Info List dialog box is displayed.
Step 4 Select the desired NE user and configure additional information for the NE user.
Step 5 Click OK and close the dialog box that is displayed.
----End
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

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.

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

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

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/CSHNU), 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


U2000
NOTE
Context
l If the LCT requests to log in to an NE to which the NMS has logged in, the NE
determines whether to permit the login of the LCT according to the status of LCT
Access Control Switch.
l If the LCT requests to log in to an NE to which the NMS has not logged in, the NE
permits the login of the LCT regardless of the status of LCT Access Control Switch.
The NMS, however, can log in to an NE to which the LCT has logged in. That is, the
login of the LCT does not affect the login of the NMS. After the NMS user logs in to the
NE successfully, the logged LCT user is not affected. If LCT Access Control Switch is
set to Disable Access, the logged LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT
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.


U2000
NOTE
l Two connection modes are supported, which are Common and Security(SSL) and
which can be queried on the U2000 server by running a query command.
l The default connection mode is Common.
NOTE
l When the U2000 server and its client are deployed on the same host and the U2000 server uses the
SSL connection mode, the client can log in to the server by using the common or SSL connection
mode. When the U2000 server and its client are deployed on the same host and the U2000 server
uses the common connection mode, the client can log in to the server only by using the common
connection mode.
l When the U2000 server and its client are deployed on different hosts, the client can log in to the
U2000 server only by using the same connection mode as the U2000 server.
l Security SSL is recommended for communication.
Procedure
Step 1 Start the U2000 client.
Step 2 In the Login interface, click .

The Server List dialog box is displayed.
Step 3 Select the required U2000 server and click Modify.
The Modify Server Information dialog box is displayed.
Step 4 Set Mode to Security(SSL).

Step 5 Click OK.
Step 6 Click OK.
----End
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.

Prerequisites
l You must be an NM user with NE maintainer authority or higher.
l SSL licenses have been deployed on the gateway NE and the U2000 client according to
the SSL loading guide.

U2000
NOTE
Procedure
Step 1 Configure the connection mode of the U2000 client.
1. Choose Administration > DCN Management from Main Menu.
The Filter dialog box is displayed.
2. Click Cancel and then click the GNE tab.
The Filter GNE dialog box is displayed.
3. Click , choose the required gateway NE, and then click OK.
4. Click OK.
5. Select the required NE, right-click the NE, and choose Modify GNE from the shortcut
menu.
The Modify GNE dialog box is displayed.
6. Change the value of Connection Mode to Security SSL.
NOTE
If Connection Mode is set to Common or Common + Security SSL and the U2000 logs in to an NE
in common mode, data is transmitted between the U2000 and NE in plaintext and there are security
risks. Security SSL is recommended for communication.

7. Click OK.
A warning dialog box is displayed.
8. Click OK. Close the displayed dialog box.
Step 2 Configure the connection mode of the gateway NE.

1. Select the NE from the Object Tree in the NE Explorer. Choose Communication >
2. Set Connection Mode to Security SSL or Common + Security SSL.
NOTE
If Connection Mode of a gateway NE is Security SSL, tools (such as the Web LCT and DC) that use
the common connection mode cannot communicate with the gateway NE.
3. Click Apply.
----End
A.4.5 Configuring RADIUS Authentication

The RADIUS authentication function allows a RADIUS server to implement centralized
management over all users that log in to an NE.
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


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
– 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.
2. 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

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
– 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.
l If an NE uses RADIUS authentication in the proxy NAS mode, set the parameters as
follows:

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 The RADIUS server or RADIUS proxy server have been configured for the NE.

U2000
NOTE
Procedure
Step 2 Click New.
The New RADIUS Server Information dialog box is displayed.
Step 3 Click .
The Select Server dialog box is displayed.
Step 4 Select a configured server and click OK. Then, the system automatically associates out the
values of Function, Server ID, and Server Type.
Step 5 Configure the RADIUS parameters.
l If an NE uses RADIUS authentication in the NAS mode or functions as a proxy server:

l If an NE uses RADIUS authentication in the proxy NAS mode:
NOTE
l If no standby server is required, set Server Status to Active.

l The NE supports one active server and 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
their default values.
----End
A.4.5.4 Configuring a KMC Key

A KMC key can enhance NE data security.
Prerequisites

U2000
Procedure
Step 1 Configure a KMC key.

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

l 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.
l 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.
l Link ID, IF Channel Bandwidth, AM, Modulation Mode of the Guaranteed AM
Capacity, Modulation Mode of the Full AM Capacity, and T/R Spacing(MHz) of the
NEs on a hop of radio link are automatically synchronized. That is, if one of the
preceding parameters is modified on an NE, the modification is automatically duplicated
on the peer NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Radio Link
Configuration from the Function Tree.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select an NE from the Object Tree in the NE Explorer. Click the Radio Link Configuration tab.
Step 2 Select 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.
l To configure 1+1 protected radio links:

a. Select 1+1.
c. Optional: Click Advanced, and configure the advanced attributes of the radio
links.
l To configure XPIC radio links for OptiX RTN 905 1E:
a. Select XPIC.
c. After the configuration is complete on the local NE, click Synchronize to

synchronize the radio link configurations to the adjacent NE.
l To configure XPIC radio links for other OptiX RTN 900 products:
a. Select 1+0 and XPIC.
NOTE
To configure XPIC radio links under 1+1 protection, first configure two XPIC radio links,
and then configure IF 1+1 protection by following the instructions in A.5.2 Creating an IF
1+1 Protection Group.
Step 4 Configure IF attributes for the local NE and the peer NE on the radio link.
NOTE
If two XPIC links in an XPIC group are in the same N+1 protection group, configure the E1 capacity
consistently for the two XPIC links.

Step 5 Configure RF attributes for the local NE and the peer NE on the radio link.
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.
l Configure a 1+0 non-protected radio link.
l Configure 1+1 protected radio links.
l Configure XPIC radio links.
Step 6 Click Apply.
----End
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.
l The IF boards of an IF 1+1 FD/SD protection group have been configured in two paired
slots.

l The two RTN 905 1Es are connected using a service cascade cable.

U2000
NOTE
When a 1+0 service is converted into a 1+1 HSB protection configuration by configuring the
IF 1+1 protection group, the original E1 service is not interrupted. The board that carries the
original service, however, needs to be set as the working board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
NOTE
If you create an IF 1+1 protection group using the Web LCT, perform the following operations:
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from
the Function Tree. Click the IF 1+1 Protection tab.

The Create IF 1+1 Protection dialog box is displayed.
Step 3 Configure the parameters of the IF 1+1 protection group.
OptiX RTN 905 1E
Other OptiX RTN 900 products

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

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-to-
point mode, you can adopt the N+1 protection configuration.
Prerequisites
the NE Panel.
l The IF board works in SDH, Hybrid (Native E1 + Ethernet) or Hybrid (STM-1 +
Ethernet) mode.

U2000
NOTE

l OptiX RTN 905 does not support this operation.
l When an N+0 service is converted into an N+1 service through the configuration of the
N+1 protection group, the original service is not interrupted.
l N+1 protection for OptiX RTN 980 using CSHNA/CSHNU 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.
l 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.
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
A.5.5 Querying the IF 1+1 Protection Status

You can learn about the current information about the IF 1+1 protection by querying the IF
1+1 protection status.
Prerequisites
l The IF 1+1 protection must be configured.

U2000
NOTE
Procedure
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Step 2 Click Query.Close the displayed operation result dialog box. In Protection Group, check the
IF 1+1 protection groups.

Step 3 Select the IF 1+1 protection group whose protection status needs to be queried. Click Query
Switch Status, and then close the displayed prompt dialog box. In Slot Mapping Relation,
check the protection status of the IF 1+1 protection group.
NOTE
If you query the IF 1+1 protection status using the Web LCT, perform the following operations:
Select the board from Slot Mapping Relation. Right-click on the selected board and choose Query
Switching Status from the shortcut menu to check the protection status of the IF 1+1 protection group.
----End
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.

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
Prerequisites
l The N+1 protection protocol is enabled.

U2000
NOTE
Procedure
NOTE
If you perform IF N+1 protection switching using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection
group, and then right-click the selected unit.
Step 4 Choose the desired switching mode from the shortcut menu.
Step 5 In the dialog box that is displayed, click OK.
The system displays the dialog box that indicates the successful operation.
Step 6 Click Close.
Step 7 Click Query Switch Status to check whether the switching operation is successful.
----End

A.5.9 Starting/Stopping the N+1 Protection Protocol

If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be
restored to the initial state.
Prerequisites

U2000
NOTE
Precautions
l Stopping the N+1 protection protocol causes a failure of the N+1 protection.
l When services are switched onto the protection channel, stopping the N+1 protection
protocol causes switchover of the services back to the working tunnel. At this time, if the
working channel is normal, the services are transiently interrupted. If the working
channel is faulty, the services are interrupted until the working channel is restored to
normal or the N+1 protection protocol is started.
Procedure
NOTE
If you start/stop the N+1 protection protocol using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group whose N+1 protection protocol needs to be
started.
Step 3 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box.
Step 4 Click Query to check the protocol status.
----End
A.5.10 Creating a PLA/EPLA/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
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/CSHNU boards support EPLA.
l Only OptiX RTN 910A, OptiX RTN 950A, and OptiX RTN 950 using CSHU/CSHUA
boards support EPLA+.
l Only RTN 950s housing CSHU/CSHUA and RTN 950As housing SLF2CSHO support
super EPLA.
l Only cascaded OptiX RTN 905 1E NEs support PLA.
l For the limitations of PLA/EPLA/EPLA+, see Feature Dependencies and Limitations of
PLA/EPLA/EPLA+ in the Feature Description.
l When you create or delete a PLA group on an ISU2 or ISX2 board, the board is cold
reset.
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration >
Physical Link Aggregation from the Function Tree.
Step 2 Click New.
The Create Physical LAG dialog box is displayed. The Create Physical LAG dialog box is
displayed.
l OptiX RTN 910A

l OptiX RTN 950A and OptiX RTN 950

PLA/EPLA/EPLA+:

Super EPLA

NOTE
– 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.
– 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 inter-
frequency 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.
l OptiX RTN 980L

l OptiX RTN 980

l OptiX RTN 905 1E\2E

NOTE
– 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.

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

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.
l RTN 950: AES-based encryption at air interfaces is supported only when CSHU/
CSHUA boards work with ISV3 boards in IS3 mode.
l RTN 980L: AES-based encryption at air interfaces is supported only by ISV3 boards in
IS3 mode or LH ACCP mode.
l RTN 905 does not support AES-based encryption at air interfaces.
l AES-based encryption at air interfaces cannot be enabled when an ISV3 interconnects
with an ISM6 board or an RTN 905.

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
l 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

NOTE
When an unprotected service is converted into a linear MSP service by configuring the linear
MSP, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS
from the Function Tree.

The system displays the Create a Linear Multiplex Section dialog box.
Step 3 Set the parameters of the linear MSP group.
Step 4 Click OK, and then close the dialog box that is displayed.
----End

Follow-up Procedure
l In the case of the 1:N linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later. If extra services need to be
transmitted, it is necessary to configure bidirectional cross-connections between the extra
services and the protection channels.
l In the case of the 1+1 linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later.
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

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

U2000
NOTE
Precautions
l Stopping the ring MSP protocol causes failure of ring MSP.

l When services are switched onto the protection channel, stopping the ring MSP protocol
causes the services to switch back to the working channel. At this time, if the working
channel is normal, the services are transiently interrupted; if the working channel is
faulty, the services are interrupted until the working channel is restored to normal or the
protocol is started.
Procedure
Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be
stopped.
Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that is
displayed.
Step 4 Click Query > Query Protection Group, close the dialog box that is displayed, and check
Protocol Status.
----End
A.6.5 Configuring Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you
can configure ring MSP to provide protection for the ring network.
Prerequisites

U2000
NOTE
l Only OptiX RTN 980 support this operation.
l The number of nodes on an MSP ring should not exceed 16.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration >
Ring MS from the Function Tree.

Step 3 Click Yes.

The Create a Multiplex Section Ring dialog box is displayed.

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

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.
l The MSP ring protocol has been enabled.

U2000
NOTE
NOTICE
All switching operations except exercise switching may interrupt services.
Procedure
Step 2 Select the required service, right-click the service, and select a switching mode from the drop-
down list.
Then, a confirmation dialog box is displayed.
Step 3 Click Yes. Then, close the dialog box that is displayed.

Step 4 Click Query.
displayed.
Step 6 Check whether the service is already switched to the protection channel.
----End
A.6.8 Starting/Stopping the MSP Ring Protocol

If you first stop the MSP ring protocol and then start it, the MSP ring protocol is restored to
its initial state.
Prerequisites
l MSP Ring has been configured for a service.

U2000
Procedure
Step 2 Stop the MSP ring protocol.
1. Select the required protection group and click Stop Protocol.
NOTICE
After the MSP ring protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the MSP ring protocol is
restarted, if services have been switched to the protection channel.

2. Click Yes. Then, close the dialog box that is displayed.
Step 3 Start the MSP ring protocol.
1. Select the required protection group. Click Start Protocol. Then, close the dialog box
that is displayed.
----End
A.6.9 Creating a Packet-based Linear MSP Group

This section describes how to add channelized STM-1 ports into a packet-based linear MSP
group.

Prerequisites
l The corresponding boards have been added in the NE Panel.

U2000
NOTE
l When an unprotected service is converted into a linear MSP service by configuring the
packet-based linear MSP, the service is not interrupted.
l Only the 1:1 packet-based linear MSP can be created.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration > Packet-
based linear MS from the Function Tree.

The Create a Packet-based Linear Multiplex Section dialog box is displayed.
Step 3 Configure the parameters for the new linear MSP group.

Step 4 Click OK to close the displayed dialog box.
----End
Follow-up Procedure
In the case of the 1:1 linear MSP, you need to configure bidirectional cross-connections
between the services and the working channel. If extra services need to be transmitted, you
need to configure bidirectional cross-connections between the extra services and the
protection channel.
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.


U2000
NOTE
Procedure
Step 2 Select the MSP group on which the switching is to be performed in Protection Group and
right-click the working or protection unit in Slot Mapping Relation.
Step 3 Choose the desired switching mode from the shortcut menu.
NOTE
If switching of a higher priority has occurred on the working or protection channel, the configured
switching will not be triggered.
----End
A.6.12 Enabling/Disabling the Linear MSP Protocol

This section describes how to restore the linear MSP protocol to the initial state by first
disabling the protocol and then enabling the protocol.
Prerequisites

U2000
NOTE

Precautions
l Disabling the linear MSP protocol causes the failure of the linear MSP.
l When services are switched to the protection channel, disabling the linear MSP protocol
switches the services back to the working channel. At this time, if the working channel is
normal, the services are transiently interrupted. If the working channel is faulty, the
services are interrupted until the working channel is restored to normal or the linear MSP
protocol is started.
Procedure
Step 2 Select the protection group for which the linear MSP protocol needs to be disabled in
Protection Group.
Step 3 Click Start Protocol or Stop Protocol and close the dialog box displayed.
Step 4 Choose Query > Query Protection Group and close the dialog box displayed. View
Protocol Status.
----End
A.7 Managing TDM Services

The TDM services involve the SDH service and the PDH service.
A.7.1 Creating the Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service
sink.
Prerequisites
l The corresponding source and sink boards must be added on NE Panel.

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH
Service Management from the Function Tree.
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 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

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.
l The E1 cross-connections must be created. The IF boards in the cross-connections must
support the E1 priority function. The E1 priorities must be set already and need to be
modified.


U2000
NOTE
Procedure
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.

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

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.
Step 3 Deactivate the service.

NOTE
1. Right-click the service and choose Deactivate from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to deactivate the selected
service.
2. Click Yes.
Then, a dialog box is displayed, indicating that this operation will clear the
corresponding service data on the NE side.
Step 4 Delete the service.

1. Right-click the service and choose Delete from the shortcut menu.
Then, a dialog box is displayed, querying whether you need to delete the selected
service.
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.

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

A.7.8 Converting an SNCP Service to a Normal Service

By converting an SNCP service to a normal service, you can convert the SNCP cross-
connection in the receive direction into the unidirectional cross-connection of the normal
service.
Prerequisites
l The SNCP cross-connection in the receive direction must be configured.
l The current service must be transmitted on the working path.

U2000
NOTE
When this task is performed to convert an SNCP service into a normal service, the original
services are not interrupted.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > SDH Service Configuration from the Function Tree.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Cross-
Connection Configuration from the Function Tree.
Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and choose
Convert to Non-Protection Service from the shortcut menu.
NOTE
If you convert an SNCP service into a normal service using the Web LCT, perform the following operations:
In Auto-Created Cross-Connection, select the configured service and click Service Convert. Choose
SNCP Protection Service Convert to Non-Protection Service or SNCP Working Service Convert to
Non-Protection Service from the displayed menu.
To convert the cross-connection into a cross-connection between the working source and the service sink,
choose SNCP Working Service Convert to Non-Protection Service. To convert the cross-connection into a
cross-connection between the protection source and the service sink, choose SNCP Protection Service
Convert to Non-Protection Service.
Then, a dialog box is displayed, querying whether you need to perform this operation.
Step 3 Click OK.
----End

Follow-up Procedure
You also need to delete the unidirectional cross-connection between the service source and the
working path or the unidirectional cross-connection between the service source and the
protection path. The SNCP service can be converted into the normal service both in the
receive direction and the transmit direction only after the deletion.
A.7.9 Querying TDM Services

You can learn 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 > Cross-
Connection 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

U2000

NOTE
Procedure
Step 2 Select the SNCP protection group for SNCP service switching.
Step 3 Click Function. Select the required switching mode from the displayed menu.
Step 4 In the displayed dialog box for confirmation, click OK.
Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then,
close the displayed prompt dialog box.
Step 6 Choose Function > Query Switch Status to check whether the switching operation is
successful.
----End
A.7.11 Querying the Protection Status of SNCP Services

You can know the current information of an SNCP service by querying the protection status
of SNCP services.
Prerequisites

U2000
NOTE
Procedure
Step 2 Select the SNCP protection group whose service protection status needs to be queried.
Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box.
----End
A.8 Managing Ports

Setting correct port parameter is the basis of configuring ports that transmit services.

A.8.1 Setting the Parameters of SDH Ports

The parameters of SDH ports are used to configure the loopback on the SDH interface board
and the laser status.
Prerequisites

U2000
NOTE
Procedure
Configuration > 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.
----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.

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


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

U2000

NOTE
Procedure
Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > Overhead
Management > Regenerator Section Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Configure the J0 byte.

1. Double-click the parameter whose value needs to be changed.
The Please Input the Overhead Byte dialog box is displayed.
2. Configure overhead bytes.
3. Click OK.
Step 4 Click Apply.

Step 5 Click 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).

Prerequisites

U2000
NOTE
Procedure
Step 1 Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration
> Overhead Management > VC4 Path Overhead from the Function Tree.
Step 2 Choose Display in Text Format or Display in Hexadecimal.
Step 3 Optional: Configure the J1 byte.

1. Click the Trace Byte J1 tab.
The Please Input Overhead Byte dialog box is displayed.
4. Click OK.
5. Click Apply.
Step 4 Optional: Configure the C2 byte.
1. Click the Signal Flag C2 tab.
2. Configure the required parameters.
3. Click Apply.

4. Click OK. Close the dialog box that is displayed indicating the operation result.
Step 5 Optional: Configure the termination mode of the VC-4 overhead.
1. Click the Overhead Termination tab.
2. Configure VC4 Overhead Termination.
3. Click Apply.
----End
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

U2000
NOTE
Procedure
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.
Step 2 Configure the J2 byte.
1. Click the Trace Byte J2 tab.
2. Choose Display in Text Format or Display in Hexadecimal.
The Please input the overhead byte dialog box is displayed.

5. Click OK.
6. Click Apply.
7. Click OK, and then close the dialog box that is displayed.
Step 3 Configure the signal flag.
1. Click the Signal Flag V5 tab.
2. Click Options.
The Options dialog box is displayed.
3. Click Extended Mode.
4. Click OK.
5. Configure the signal flag in the V5 byte.
6. Click Apply.
7. Click OK, and then close the dialog box that is displayed.
----End

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

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

Prerequisites
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.
l 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.


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

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
mode, encapsulation type, and maximum frame length.
Prerequisites
l The Ethernet board must be added on the NE Panel.

U2000
NOTE
Procedure
Management > Ethernet Interface from the Function Tree.
Step 3 Set basic Ethernet port attributes.

NOTE
l Specifies the level of services that a port carries.

l If Port Mode is Layer 2, the port can carry native Ethernet services.
l If Port Mode is Layer 3, the port can carry MPLS tunnels.
l If Port Mode is Layer Mix, the port can carry both native Ethernet services and MPLS tunnels.
l This parameter specifies the method of the port to process the received packets.
l This parameter is valid only when Port Mode is Layer 2.
l If you set Encapsulation Type to Null, the port transparently transmits the received packets.
l If you set Encapsulation Type to 802.1Q, the port identifies the packets that comply with the IEEE
802.1q standard.
l If you set Encapsulation Type to QinQ, the port identifies the packets that comply with the IEEE
802.1ad QinQ standard.
l The Ethernet ports of different types support different Working Mode. For details, see the IDU
Hardware Description.
l When the equipment on the opposite side works in auto-negotiation mode, set the Working Mode of
the equipment on the local side to Auto-Negotiation.
l When the equipment on the opposite side works in full-duplex mode, set the Working Mode of the
equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex
depending on the port rate of the equipment on the opposite side.
l When the equipment on the opposite side works in half-duplex mode, set the Working Mode of the
equipment on the local side to 10M Half-Duplex, 100M Half-Duplex.
l The value of Max Frame Length(byte) should be greater than the length of any frame to be
transported.
Step 4 Click Apply and close the displayed dialog box.
----End
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

U2000
NOTE
Procedure
Step 2 Click the Flow Control tab.

Step 3 Configure the Ethernet port traffic control.
NOTE
l Auto-Negotiation Flow Control Mode is valid only when Working Mode is set to Auto-
Negotiation.
l Auto-Negotiation Flow Control Mode of the equipment on the local side must be consistent with
the auto-negotiation flow control mode of the equipment on the opposite side
l OptiX RTN 900 supports only two auto-negotiation flow control modes, namely, Disabled mode
and Enable Symmetric Flow Control mode.
l An EM6D board supports only two auto-negotiation flow control modes, namely, Disabled mode
and Enable Symmetric/Dissymmetric Flow Control mode.
l Non-Autonegotiation Flow Control Mode is valid only when Working Mode is not set to Auto-
Negotiation.
l Non-Autonegotiation Flow Control Mode of the equipment on the local side must be consistent
with the non-autonegotiation flow control mode of the equipment on the opposite side
l OptiX RTN 900 supports only two non-auto-negotiation flow control modes, namely, Disabled
mode and Enable Symmetric Flow Control mode.
l An EM6D board supports only two non-auto-negotiation flow control modes, namely, Disabled
mode and Receive Only mode.
----End
A.8.8.3 Setting the Layer 2 Attributes of Ethernet Ports

Ethernet port Layer 2 attributes define link-layer information.
Prerequisites

U2000
NOTE
Procedure

Step 2 Click the Layer 2 Attributes tab.
Step 3 Set Ethernet port Layer 2 attributes.
NOTE
l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set
QinQ Type Domain. The default value is 88A8.
l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot
set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be
changed.
l If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to Tag Aware.
l If all the accessed services are frames without the VLAN tag (untagged frames), set TAG to Access.
l If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid.
l Default VLAN ID is valid only when TAG is set to Access or Hybrid.
l VLAN Priority is valid only when TAG is set to Access or Hybrid.
Step 4 Click Apply.
----End
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.

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

U2000
NOTE
Procedure
Step 3 Set Ethernet port advanced attributes.
----End

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

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

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.

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

U2000
NOTE
Procedure

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

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.

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

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
Precautions
l For the IF boards that are configured with 1+1 protection, configure only the ATPC
attributes of the main IF board.
l The following procedure describes the ATPC parameter configurations in the IF port
configuration dialog box for the IF board. You can also configure ATPC parameters in
the Create XPIC Protection Group window.

U2000
NOTE
Procedure
Step 2 Click the ATPC Attributes tab.
Step 3 Set the parameters of ATPC attributes.

NOTE
l The settings of the ATPC attributes must be consistent at both ends of a radio link.
l In the case of areas where fast fading severely affects the radio transmission, it is recommended that
you set ATPC Enable Status to Disabled.
l If ATPC Automatic Threshold Enable Status is set to Enabled, the equipment automatically uses
the preset ATPC upper and lower thresholds according to the work mode of the radio link.
l If ATPC Automatic Threshold Enable Status is set to Disabled, you need to manually set ATPC
Upper Automatic Threshold(dBm) and ATPC Lower Automatic Threshold(dBm).
l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central
value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the difference between the planned central value between the ATPC
upper threshold and the ATPC lower threshold and 10 dB.
Step 4 Click Apply.
----End
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.

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

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

U2000
NOTE
Context
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 Only RTN 980L 10GHz long haul can work in LH ACCP mode.
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.

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.
l The AM function has been enabled by A.5.1 Configuring a Single-Hop Radio Link.

U2000
NOTE
Only ISX2 boards support the AM Booster function.
Procedure
Step 3 Enable or disable the AM Booster function.
Step 4 Click Apply.
----End
A.8.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


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 1. Perform Step 5 to disable the AM function, and change
Modulation Mode of Manually Specified Modulation Mode to the lowered
the Guarantee AM Modulation Mode of the Guarantee AM Capacity.
Capacity 2. Perform Step 6 to enable the AM function.
In other cases 1. Set Modulation Mode of the Guarantee AM Capacity and
Modulation Mode of the Full AM Capacity to their planned
values.
2. Click Apply.
Step 8 Optional: Change the number of high-priority E1 services (namely, Guarantee E1

Capacity) in a radio link.

If... Then...
You need to reduce 1. Perform A.7.6 Deleting Cross-Connections to delete
the number of high- unnecessary 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-to-
Point 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 low- unnecessary 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 low- 2. Increase Full E1 Capacity.
priority E1 services
3. Click Apply.
4. Perform A.7.1 Creating the Cross-Connections of Point-to-
Point 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.

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


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 Perform steps 6 to 9.
Step 3 Click the Power Attributes tab.
Step 4 Set the parameters of ODU power attributes.

NOTE
l Maximum Transmit Power(dBm) is set according to the network plan. This parameter cannot be
set to a value that exceeds the nominal power rang of the 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.

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.
l Port Mode has been set to Layer Mix for Ethernet boards and IF boards.

U2000
NOTE
Context
VLAN sub-interfaces are similar to Layer 3 ports. By configuring Layer 3 port attributes for
VLAN sub-interfaces, you can create MPLS tunnel-based services. After being received by
access-layer RTN equipment and then mapped into an MPLS tunnel, services are allocated
different VLAN IDs at VLAN sub-interfaces in compliance with configuration requirements
for the third-party network that the services need to traverse. In this manner, services are
differentiated and therefore correctly forwarded on the third-party network.
Procedure
Interface Management > Ethernet Virtual Interface from the Function Tree.
Step 3 Choose New > Create Ethernet Virtual Interface.

The Create Ethernet Virtual Interface dialog box is displayed.
Step 4 Set VLAN sub-interface parameters.

Step 5 Click OK.
----End
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

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

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

Procedure
Step 2 Set the parameters for the ERPS instance.
NOTE
In this step, you can set Compatible_Version, Virtual Channel Status, Virtual Channel VLANs, and
Major ERPS Ring ID, and query or modify other ERPS instance protocol parameters.
l For multi-ring networks, Compatible_Version for all ring nodes must be ver2.
l For details about values of Virtual Channel Status and Virtual Channel VLANs, refer to Planning
Guidelines for R-APS Virtual Channels in the Feature Description.
l Set this parameter only for the sub-ring ERPS instance on an interconnection node to associate the sub-
ring ERPS instance with the major ring 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.

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.
l It is advised to configure a bound MEP for an interconnection node sub-ring port when
the network is normal.
l Modify Interconnected Node and Multi-point Failure only after multiple failures
occur. Restore the two parameters to default values immediately after faults are rectified.

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.

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.

A.9.2.1 Creating a LAG

Between two NEs, if the bandwidth and availability of the Ethernet links need to be
improved, the new LAG must be created.
Prerequisites
l The board on which the LAG port to be created must be added to the NE Panel.

U2000
NOTE
Procedure
Management > Link Aggregation Group Management from the Function Tree.
Step 2 Click the Link Aggregation Group Management tab.
Step 3 Click New.

The system displays the Create Link Aggregation Group dialog box.
Step 4 Set the LAG attributes in Attribute Settings.

NOTE
l When Automatically Assign is selected, LAG No. cannot be set.

l Revertive Mode can be set only when Load Sharing is set to Non-Sharing.
l When Revertive Mode is set to Revertive Mode, the services are switched back to the former working
channel after this channel is restored to normal.
l Set Load Sharing to the same value as the peer equipment. It is recommended that you set Load
Sharing to Non-Sharing at both ends if the LAGs are used for protection and set Load Sharing to
Sharing at both ends if the LAGs are used for increasing bandwidths.
l System Priority indicates the priority of a LAG. The smaller the value of System Priority, the higher the
priority.
l WTR Time(min) takes effect only when Revertive Mode is Revertive Mode.
l If Switch LAG upon Air Interface SD is set to Enabled, the MW_BER_SD 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.
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:
– 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.

4. Click OK. A dialog box is displayed for confirmation. Click OK. A dialog box is
displayed, indicating that the operation is successful. Close this dialog box.
----End
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.

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.
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.
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
Context
The intra-board Native E-Line services on an EM6T, EM6TA, EM6F, or EM6FA board can be
forwarded in two modes: Center and Local.

l When the centralized forwarding mode is used, intra-board Native E-Line services must
be forwarded through the packet switching unit of a system control board. Therefore,
double backplane bandwidth resources of the system control board are consumed.
l When the distributed forwarding mode is used, intra-board Native E-Line services are
directly forwarded by the switching units of the board. However, this will restrict the
functions of some packet switching units that depend on system control boards. The
restrictions include:
– Intra-board Native E-Line services do not support the LM function of ETH-OAM.
Therefore, the packet loss rate of the Native E-Line services could not be tested
using meter-free tests.
– The source and sink ports of intra-board Native E-Line services do not support the
LAG function. If the source or sink ports are configured with the LAG function, the
forwarding mode is automatically switched to centralized mode.
l The default forwarding mode configured for an EM6T, EM6TA, EM6F, or EM6FA board
is centralized forwarding.
Other types of Ethernet services on an EM6T, EM6TA, EM6F, or EM6FA board and all types
of Ethernet services on other types of Ethernet boards are forwarded in centralized mode.
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration > Ethernet
Service Forwarding Mode Management from the function tree.
Step 2 Modify the value of Ethernet Service Forwarding Mode.
Step 3 Click Apply.
----End
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

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.


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

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.
l For ports that carry services, Port Mode has been set to Layer 2 and Encapsulation
Type has been set to QinQ.

U2000
Context
NOTE
exceed 1024.
Procedure
Step 2 Click New.
Step 3 Set Direction to NNI-NNI.
Step 4 Set relevant attributes of the E-Line service.

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

Step 5 Optional: Click New to configure the source and sink ends.
NOTE
In this manner, you do not need to configure the QinQ links used at the source and sink ends according to the
network planning information ahead of time. However, you need to set Encapsulation Type of ports
corresponding to the QinQ links to QinQ ahead of time.
1. Click New.
2. Set the attributes of the QinQ link at the source end.
3. Click Configure QinQ Link.
4. Repeat Step 5.2 and Step 5.3 to set the attributes of the QinQ link at the sink end.
5. Select Use existing resource.
6. Click to add QinQ links to Source and Sink.
Step 6 Optional: Select Use existing resource and select created QinQ links as the QinQ links used
at the source and sink ends.
NOTE
In this manner, you need to configure the QinQ links used at the source and sink ends according to the
network planning information ahead of time.
2. Click to add QinQ links to Source and Sink.
Step 7 Click OK.
----End
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

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.

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.

Step 8 Click QinQ Link.
Step 9 Optional: Click New and create the QinQ link used at the sink end.
NOTE
In this manner, you do not need to configure the QinQ link used at the sink end according to the network
planning information ahead of time. However, you need to set Encapsulation Type of ports corresponding to
the QinQ links to QinQ ahead of time.
1. Click New.
2. Set the attributes of the QinQ link at the sink end.

5. Click to add the QinQ link to Sink.
Step 10 Optional: Select Use existing and select a created QinQ link as the QinQ link used at the sink
end.
NOTE
In this manner, you need to configure the QinQ link used at the sink end according to the network planning
information ahead of time.
2. Click to add the QinQ link to Sink.
Step 11 Click OK.
----End

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.
l For the UNI port that carries the service, Port Mode has been set to Layer 2. For the
NNI port that carries the service, Port Mode has been set to Layer 3.
l The tunnel that carries PWs is configured.

U2000
Context
NOTE
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by UNI-
carried 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 TAG-
mode 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.

Step 5 Click Configure PW.

The Configure PW dialog box is displayed.
Step 6 Click the General Attributes tab and set the basic parameters for PWs.
Step 7 Click the QoS tab and set the QoS parameters for PWs.
Step 8 Click the Advanced Attributes tab and set the advanced parameters for PWs.

Step 9 Click OK, and close the Configure PW dialog box.
----End
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.
l Port Mode is set to Layer 2 for the UNI ports that carry services.

Web LCT
Context
NOTE
l For RTN 950 housing CSH boards, RTN 980, and RTN 980L, the total number of VLANs used by UNI-
carried 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 TAG-
mode PW-carried and S-aware UNI-carried E-Aggr services must not exceed 256.
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.

Step 4 Set the basic attributes of E-Line services.
Step 6 Change the attributes of the source Ethernet port.
Step 7 Click Apply Port Attributes.
Step 8 Click PW and set the basic attributes of the PW.
Step 9 Click Apply.
Step 10 Click Advanced Attributes.

The Advanced Attributes dialog box is displayed.
Step 11 Set the advanced attributes of the PW.

Step 12 Click OK.
----End
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 E-
AGGR service.
Prerequisites
l For the UNI ports that carry the service, Port Mode has been set to Layer 2 and
Encapsulation Type has been set to 802.1Q or QinQ. For the NNI port that carries the
service, Port Mode has been set to Layer 3.
l The MPLS tunnels that carry PWs have been configured.

U2000
NOTE
Context
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN
forwarding table needs to be configured, specifying the source and sink VLAN IDs of
each VLAN service.
l If VLAN ID swapping is required for PW-based E-Line services, change the E-Line
services to an E-AGGR service.
l For an E-AGGR service aggregating services from multiple UNI ports to a PW, the NNI
port must be configured as the sink. For an E-AGGR service aggregating services from
multiple PWs to a UNI port, the UNI port must be configured as the sink.

Procedure
Ethernet Service Management > E-AGGR Service from the Function Tree.
Step 2 Click New.

The New E-AGGR Service dialog box is displayed.
Step 3 Set the basic attributes for the E-AGGR service.
Step 4 Configure the UNI ports required for the E-AGGR service.
1. Click the UNI tab. Click Configuration.
The Configure Port dialog box is displayed.
2. Select the desired port from the Available Port list and click to add the port
to the Selected Port list.
3. In the Selected Port area, set Location and VLANs according to planning information.
NOTE
You can set Location to Source or Sink. You can configure one or more source ports but only one
sink port for an E-AGGR service. Otherwise, configuration of the E-AGGR service will fail.
4. Click OK.
Step 5 Configure the NNI port required for the E-AGGR service.
1. Click the NNI tab. Click the PW tab. Click New.
2. Set parameters in Basic Attributes according to planning information.

3. Set parameters in Advanced Attributes according to planning information.
4. Click OK.
Step 6 Set the attributes for the VLAN forwarding table.

1. Click VLAN Forwarding Table Item and click New.
The New VLAN Forwarding Table Item dialog box is displayed.
2. Set related parameters according to VLAN planning information.
3. Click OK.
Step 7 Optional: Click the Configure QoS tab and set QoS parameters.
1. Click the PW tab and set EXP and LSP Mode.
2. Click OK.
Step 8 Click OK.
----End
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.
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.
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-to-
multipoint mode by means of MAC addresses.
Prerequisites
l For ports carrying IEEE 802.1d bridge-based E-LAN services, Port Mode has been set
to Layer 2 and Encapsulation Type has been set to Null.

U2000

Context
An IEEE 802.1d bridge-based E-LAN service must be configured according to the service
model described in 802.1D Bridge-based E-LAN Service Models.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.

The New E-LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the E-LAN service according to the network plan.
Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration.
3. Configure the ports mounted to the bridge on the UNI side.
a. Select the port to be mounted to the bridge.
b. Click to mount the port to the bridge.

4. Click OK.
Step 5 Optional: Configure split horizon groups.

NOTE
l The port members that are added to the same split horizon group cannot communicate with each other.
l You are advised to configure split horizon groups when two PWs do not need to 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-to-
multipoint mode by means of MAC addresses.
Prerequisites

Web LCT
Procedure
Step 2 Click New.
The Create E-LAN Service dialog box is displayed.
Step 3 Click Configure the source and sink. Set the basic attributes of the E-LAN service
NOTE
Set Tag Type to Tag-Transparent.
1. Click Get UNI Port.
The Get UNI Port dialog box is displayed.
NOTE
Preset Encapsulation Type of the port to Null.

3. Click OK.

Step 5 Optional: Create split horizon groups.

NOTE
The port members that are added to the same split horizon group cannot communicate with each other.
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.
l 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
for all Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be used to
transmit other Ethernet services.
Procedure
Step 2 Click New.
Step 3 Set basic attributes of the E-LAN service as planned.

1. Click UNI.

c. Set the VLAN ID of the port mounted to the bridge according to the network plan.
4. Click OK.
NOTE
other.
3. Click .
4. Click OK.
----End
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.
NOTE
Preset Encapsulation Type of the port to 802.1Q.

3. Click OK.

NOTE
2. Click New.

NOTE
4. Click OK.
Step 6 Click OK.
----End
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 E-
LAN Services.
Procedure
Step 2 Click New.

Step 3 Set parameters of the E-LAN service as planned.

1. Click UNI.

c. If Encapsulation Type is set to 802.1Q for the port mounted to the bridge,
configure the VLAN ID for the port according to the network plan.
4. Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1. Click NNI.
3. Configure the ports mounted to the bridge on the NNI side.
4. Click OK.

NOTE
other.
3. Click .
4. 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 E-
LAN Services.
Procedure
Step 2 Click New.

Step 3 Click Configure the source and sink. Set parameters of the E-LAN service as planned.
NOTE
Set Tag Type to S-Aware.

NOTE
Preset Encapsulation Type of the port to 802.1Q.

3. Click OK.
Step 5 Configure the ports mounted to the bridge on the NNI side.
1. Click Get NNI Port.
The Get NNI Port dialog box is displayed.
2. Configure the ports mounted to the bridge on the NNI side.
NOTE
Preset Encapsulation Type of the NNI port to QinQ.

3. Click OK.
NOTE
2. Click New.

NOTE
4. Click OK.
Step 7 Click OK.
----End
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
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
l 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.
l 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 SLB2CSHN
l A VPLS must be configured according to the service model described in PW-Carried E-

LAN Services.
Procedure
Step 2 Click New.

Step 3 Set parameters for the E-LAN services according to the network plan.

Step 4 Configure the port mounted to the VSI on the UNI side.
1. Click the UNI tab.
2. For RTN 905/950A, when Tag Type is set to S-Aware, do not select PB-UNI.
4. Configure the port mounted to the VSI on the UNI side.
a. Select the port to be mounted to the VSI and configure VLAN information.
b. Click to mount the port to the VSI.
NOTE
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:
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.
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.
5. Click OK.
Step 5 Configure the PW mounted to the VSI on the NNI side.

1. Click NNI.
2. Click Add.
3. Configure the PW mounted to the VSI.
4. Click OK.

NOTE
other.
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
Maximum Number of VUNI Ports (X) Maximum Number of VLANs
X ≤ 32 4096
32 < X ≤ 64 2047
64 < X ≤ 128 1023
128 < X ≤ 256 511
256 < X ≤ 512 255
512 < X ≤ 1024 127

Procedure
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.
NOTE
l To add or delete ports connected to the VB on the UNI side, click the UNI tab.
l To add or delete ports connected to the VB on the NNI side, click the NNI tab.
1. Click Configuration. In the displayed Configure Port dialog box, select the port to be
added to or deleted from the list of ports connected to the VB.
2. Optional: Click to add ports to the list of ports connected to the VB.
3. Optional: Click to delete ports from the list of ports connected to the VB.
NOTE
4. In Selected Port List, set the attributes of the ports connected to the VB.

5. Click OK.
6. Click Yes.Close the displayed dialog box.
----End
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
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 950 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
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

U2000
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses
needs to be created.
Step 3 Click the Disabled MAC Address tab.
Step 4 Click New.

The Create Disabled MAC Address dialog box is displayed.
Step 5 Configure the blacklist entry of MAC addresses.
----End

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

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

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

U2000
NOTE
Procedure
Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown
frame needs to be set.
Step 3 Click the Unknown Frame Processing tab.
Step 4 Set the mode for processing an unknown frame of the E-LAN service.

----End
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. Set Protocol Type and Enable Protocol.
2. Select the board where the member port is located from the drop-down list of Board
under Apply Port.
3. Select the member port from Available Port List. Then, click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.

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

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

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

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.

Option Description
If... Then...
A member port needs to 1. Select the board where the member ports are located from
be added the drop-down list of Board.
2. Select the port to be added from Available Port List.
3. Click .
A member port needs to 1. Select the port to be deleted from Selected Port List.
be deleted
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.

Prerequisites
l OptiX RTN 950A does not support this operation.
l OptiX RTN 950 supports this operation only when housing the system control board
CSH.

U2000
Procedure
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab.
Step 3 Set the attributes of the IGMP Snooping protocol.
Step 4 Click Apply.
----End
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

U2000
Procedure
Step 2 Click the Route Management tab.
Step 3 Click Query.
Step 4 Query the port information of the routers.
----End

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

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 .

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 and Multicast MAC Address.
2. Select the member ports from the drop-down list of Available Port. Click .
NOTE
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the
ports.

3. Click OK.
----End
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

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

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
A.9.8 Managing the QoS

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

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.

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

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


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 1. Select the board where the application port is located
uses the DS domain 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 1. Select the board where the application port is located
that uses the DS domain 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

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

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.

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

U2000
NOTE
Procedure
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Click New. The Create Port Policy dialog box is displayed.
Step 3 Set the ID and name of the port policy.
Step 4 Configure scheduling, packet dropping policies, and shaping for egress queues.

NOTE
l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic
of the key services is that higher priorities are required to minimize the response delay in the case of
congestion events.
l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output sub-
queues. The polling scheduling is performed among the output sub-queues to ensure that each sub-queue
has a certain period of service time.
l The OptiX RTN 900 supports the setting of the SP+WRR scheduling algorithm of the CoS queue
according to the requirement, and provides one or more queues that comply with the SP algorithm.
Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP
scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After
Reloading can be changed from SP to WRR according to the queue priorities in a descending order
(CS7-BE).
----End
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
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

U2000
NOTE
Procedure
Step 2 Click New.

Step 3 Click the Traffic Classification Configuration tab.

Step 4 Click New.
The Create Traffic Classification dialog box is displayed.
Step 5 Set the attributes.
NOTE
Set the parameters according to the network plan.
Step 6 Click Apply.

----End

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

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

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
A.9.8.11 Creating a WRR Policy

This section describes how to create a WRR policy.

Prerequisites

U2000
NOTE
Context
In the default WRR scheduling policy for OptiX RTN 900, AF4, AF3, AF2, and AF1 occupy
the same weight of 25% and other queues occupy the weight of 0%.
Procedure
Management > Policy Management > WRR Scheduling Policy from the Function Tree.
Step 2 Click 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.
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

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.
1. Select the port to be deleted from Selected Ports and click .

NOTE

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

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.

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.

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

U2000

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.

Prerequisites

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

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.
l 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.
l Apply the QinQ policy.
l 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.

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

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.

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

U2000
NOTE
Procedure
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 2 Click the Maintenance Association tab.
Step 3 Choose New > New Maintenance Domain.
The system displays the New Maintenance Domain dialog box.

Step 4 Set the MD parameters.
NOTE
l Maintenance Domain Level specifies the level of the maintenance domain.

l The values 0 to 7 indicates maintenance domain levels in an ascending order.
l MEPs transparently transmit OAM protocol packets if the packets have a higher level than the
parameter value.
l MEPs discard OAM protocol packets if the packets have a lower level than the parameter value.
l MEPs respond to or terminate OAM protocol packets based on the packet type if the packets have
the same level as the parameter value.
----End
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.
l The Ethernet service must be created.

U2000
NOTE
Procedure
Step 3 Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.
The system displays the New Maintenance Association dialog box.
Step 4 Set the MA parameters.

NOTE
Click in Relevant Service. Select the corresponding services in the displayed Select
Service dialog box.
Step 6 Optional: When Y.1731–based 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.

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

U2000
NOTE
Procedure
Step 3 Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog box
is displayed.
Step 4 Click New.

The Add Maintenance Association Remote Maintenance Point dialog box is displayed.
Step 5 Set the parameters of the new remote MEP.
NOTE
If other MEPs will initiate OAM operations to an MEP in the same MA, set these MEPs as remote
MEPs.
----End
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

U2000
NOTE
Procedure
Step 2 Click the MIP Point tab.
Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New.
The New MIP Maintenance Point dialog box is displayed.
Step 4 Set the parameters of the new MIP.

NOTE
l Each MIP needs to be configured with an MP ID, which is unique in the maintenance domain. The
MP ID is required in the OAM operation.
l To create MEPs and MIPs in a service at a port, ensure that only one MIP can be created and the
level of the MIP must be higher than the level of the MEP.
----End
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.
l The remote MEPs must be created.

U2000
NOTE
l Only the MEP can enable the CC test and function as the receiving and responding end
in the test.
l During the CC check, the source MEP constructs and transmits continuity check
message (CCM) packets periodically. After receiving the CCM packets from the source
MEP, the sink MEP directly enables the CC function for this source MEP. If the sink
MEP fails to receive the CCM packets from the source MEP within the check period
(that is, 3.5 times of the transmit period), it reports the alarm automatically.
l Performing a CC test does not affect the services.
Procedure
Step 3 Select the MEP where you need to perform the CC test and then choose OAM > Activate
CC.
A dialog box is displayed, indicating that the operation is successful.

NOTE
l Before the CC test, you can set CC Test Transmit Period according to the actual requirements.
l To disable a CC test, select the MEP where the CC test is performed and then choose OAM >
Deactivate.
NOTE
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC
from the shortcut menu.
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Deactivate CC
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.
l The CC function must be enabled.

U2000
NOTE
l Only MEPs can initiate the LB test and function as the receive end in the test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the
source MEP. This indicates that the loopback is successful. If the source MEP timer
times out, it indicates that the loopback fails.
l Performing an LB test does not affect the services.
Procedure
Step 3 Select the maintenance domain and maintenance association for the LB test.
Step 4 Choose OAM > Start LB.

The LB Test dialog box is displayed.

NOTE
To enable an LB test, you can also right-click an MEP and then choose Start LB from the shortcut
menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the
LB test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set
to the Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address. Only the MAC address of the MEP can be set to the MAC address of the Destination
Maintenance Point MAC Address.
Step 6 Click Start Test. Then, the LB test result is displayed in the Detection Result window.
----End
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.
l The CC function must be enabled.

U2000
NOTE
l Only MEPs can initiate the LT test and work as the termination point in the test.
l During the LT test, the source MEP constructs and transmits the LTM frames and starts
the timer. All the MPs that receive the LTM frames send the LTR frame response.
According to the LTR frame response, you can verify all the MIPs that pass from the
source MEP to the sink MEP.

l Performing an LT test does not affect services.
Procedure
Step 3 Select the maintenance domain and maintenance association for the LT test.
Step 4 Choose OAM > Start LT.

The LT Test dialog box is displayed.
NOTE
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the
LT test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. Only the MEP ID can be set
to the Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Maintenance Point MAC
Address. Only the MAC address of the MEP can be set to the MAC address of the Destination
Step 6 Click Start Test. Then, the LT test result is displayed in the Detection Result window.
----End
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

U2000
NOTE

Procedure
Step 3 Select the MD and MA where the MEP is located.
Step 4 Select the node to be monitored. Double-click or right-click AIS Active Status and then
select Active or Inactive.
Step 5 Click Apply.
----End
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.

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, Click the Statistics Group tab and
delay, or delay variation set required parameters.
You want to query the historical packet loss ratio, Click the History Group tab and set
delay, or delay variation required parameters.
NOTE
Ensure that historical performance monitoring for
associated periods has been enabled before querying the
historical packet loss ratio, delay, or delay variation.
You want to set alarming thresholds for the Click the RMON Setting tab. Then
packet loss ratio, delay, or delay variation 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.


U2000
NOTE
Context
l Creation of MEPs is not a prerequisite for service loopback detection.
l During an E-LAN service loopback test, if a node on the network to which the tested
port is connected reports a loopback packet threshold-crossing event, there is an E-LAN
service loop on this node.
l This task can also be completed by choosing Service > Service Path View from the
main menu.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 Click 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

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 Setting the Enabling Status of Automatic Service Loop Detection for NEs
When the NE supports E-LAN service mounting and the port status changes from down to
up, service loop detection is automatically initiated and looped services are disabled.
Prerequisites

U2000
NOTE
Context
l Principle of E-LAN service loop detection: Special LD packets are sent (DA is a special
unicast packet, and SA indicates source MAC address. VLAN tags are encapsulated
based on the port that initiates the detection, and service information is encapsulated into
the payload of LD packets). The VLAN ID of LD packets is the same as that of service
packets, and the intermediate NE may forward LD packets as service packets. If the NE
receives the LD packets sent by itself from the same VPN (the SVL bridge is determined
according to the DA and SA, and the IVL bridge is determined according to the DA, SA,
and VLAN), the system considers that a loop exists.
l Automatic loop detection is enabled by default upon service creation and the port status
change.
l If automatic loop detection is enabled upon service creation: service loop detection will
be automatically initiated on the first and last VLANs in the VLAN list after a logical
port is added to the E-LAN. If a loop is detected on either of the two VLANs, the logical
port is disabled. If new VLANs are added on a logical port, service loop detection will be
automatically initiated on the first and last VLANs among the new VLANs. If a loop is
detected on either of the two VLANs, all the newly added VLANs are disabled.

l If automatic loop detection is enabled upon the port status change, service loop detection
will be automatically initiated on all logical ports on a physical port after the physical
port changes from down to up. If multiple VLANs are accessed to a logical port, service
loop detection will be initiated on any two VLANs. If a loop is detected, the logical port
is disabled and the SRV_SHUTDOWN_LD alarm is reported.
NOTE
Limitation and Impact

l After the function is enabled, loop detection will be initiated only when new services are created or
the physical port changes from down to up. If a loop occurs when neither of the preceding
conditions is met (such as a third-party network loop), it cannot be detected automatically or
disabled.
l If the LD packets sent by an NE are discarded during transmission (including but not limited to link
congestion, link bit error, transient link interruption, and board reset), the service loop cannot be
detected.
l If service loop detection is automatically initiated, after a loop is detected and the service is disabled,
the disabled service cannot be automatically enabled after the loop is eliminated. The disabled
service can only be enabled manually by the user. For details, see Operation Procedure.
l After automatic service loop detection is enabled, an LD packet is sent every second. If a loop is
detected within three consecutive detection periods (a period of five seconds), the system considers
that a loop exists and the service is disabled. If no loop is detected within three consecutive detection
periods (a period of five seconds), the system considers that no loop exists and the detection stops.
l Two VLANs on a logical port are randomly selected for automatic service loop detection. When
loops occur on some VLANs on the logical port: if no loop occurs on the selected VLANs but loops
occur on the other VLANs on the logical port, the loop cannot be detected and the service cannot be
disabled. If loops occur on the selected VLANs but no loop occurs on the other VLANs on the
logical port, the VLANs where no loop occurs are disabled.
l When services are disabled, the NNI of the S-Aware bridge disables all NNIs on the physical port
where the NNI of the S-Aware bridge is configured, and the E-LAN services of other types only
disable the logical port where a loop is detected.
l For VPLSs in IVL mode, when no UNI is configured, the NNI does not support automatic service
loop detection.
l When a loop occurs in a network but no broadcast storm occurs, automatic loop detection may cause
services to be disabled.
Precautions
When a loop occurs in a network but no broadcast storm occurs, automatic loop detection
may cause services to be disabled. If this occurs in a live network, disable the function of
automatic loop detection on the NE and re-enable the disabled service. After that, eliminate
the loop and enable the function again.
Procedure
Step 1 In the NE Explorer, select an NE from the object tree. Choose Diagnosis & Maintenance >
E-LAN LD Test Management from the function tree.
Step 2 Select Auto or Disabled.

Step 3 Click Apply.
----End
Procedure
1. Synchronize NE alarms, and check whether the SRV_SHUTDOWN_LD alarm occurs
on the NE. If the alarm occurs, find the service that is disabled according to alarm
details.
a. If the VUNI is disabled, the format of alarm location information is L2VPN(Service
ID)_VUNI(VUNI ID)_Port. As shown in Figure A-1, the alarm location
information indicates that the VUNI on port 5 on board 3 in E-LAN 3956 on NEs
(55–66) is disabled.
Figure A-1
b. If the VUNI is disabled, the format of alarm location information is L2VPN(Service

ID)_VUNI(VUNI ID)_PWID. As shown in Figure A-2, the alarm location
information indicates that the PW 4874 of E-LAN 4842 on NEs (35-211) is
disabled.

Figure A-2
2. In the NE Explorer located by the alarm information, select Configuration Ethernet

Service Management E-LAN Service from the function tree. Find and select the E-
LAN service according to the service ID reported by the SRV_SHUTDOWN_LD
alarm, and choose Manual Loop Detection.
3. Select UNI or NNI information, and click Service Status List. After the Service Status
List is displayed, check the service status. Enable indicates that the service is not
blocked, and Disable indicates that the service is blocked by loop detection. Select the
blocked service, and click Enable to re-enable the service.

NOTE
l Check the services before re-enabling the blocked services. If a loop exists, disrupt the loop before
re-enabling the blocked service.
l Service interruption persisting after the service is re-enabled indicates that a loop exists. Delete the
service and check the physical loop.
A.9.9.14 Configuring Bandwidth Notification

This section describes how to configure bandwidth notification. Bandwidth notification
monitors air-interface bandwidth changes and informs the peer router of the changes.
Prerequisites
l An egress MEP has been created.

U2000
NOTE
Background
l Bandwidth notification can be configured only on an egress MEP.
l Bandwidth notification packets do not affect services.
Procedure
Ethernet OAM Management > Ethernet Service OAM Management from the Function
Tree.

Step 2 Select the desired maintenance domain (MD).

Step 3 Select the desired maintenance association (MA).
Step 4 Select the desired MEP. Click OAM and choose Configure Bandwidth Advertisement.
Step 5 Configure bandwidth notification parameters.
Step 6 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 auto-
discovery succeeds, the equipment automatically monitors the fault and performance of the
link.
Prerequisites

U2000
NOTE
The OAM auto-discovery is realized based on the auto-negotiation between the local
equipment and the opposite equipment. If the negotiation fails, the local equipment reports an
alarm. After OAM auto-discovery is successfully completed, the link performance is
monitored according to the error frame threshold. You can set the error frame threshold on the
NMS.
Procedure
OAM Management > Ethernet Port OAM Management from the Function Tree.
Step 2 Click the OAM Parameter tab.
Step 3 Select the port, and set OAM Working Mode.

NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems,
the OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-
discovery fails.
l If both ends of a link are in passive OAM mode, a link fault occurs, or either end of a link does not
receive OAM protocol packets within 5 seconds, an alarm is reported, indicating that OAM auto-
discovery fails.
Step 4 Set Enable OAM Protocol to Enabled.
Step 6 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the
opposite end. Close the displayed dialog box.
----End

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.
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.
l On the equipment that initiates the loopback, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support the remote loopback.

U2000
NOTE
l If a port is capable of responding to loopbacks, it enters the loopback responding state
and reports the loopback responding alarm after receiving the command of enabling the
remote loopback function sent from the opposite OAM port. In this case, the equipment
that initiates the loopback enters the loopback initiation state and reports the loopback
initiation alarm.
l Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU, are looped back at the remote end.

l After using the remote loopback function to complete the fault locating and the link
performance detection, you need to disable the remote loopback function at the end
where the loopback is initiated and then restore the services. The alarm is automatically
cleared.
Procedure
Step 3 Select the port and set Remote Side Loopback Response to Enabled.
Step 5 Choose Enable Remote Loopback from the drop-down menu of OAM. Close the displayed
dialog box.
NOTE
To release remote loopbacks, select Disable Remote Loopback.
----End
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.
Prerequisites
l The required board is already added on the NE Panel.
l All the external physical ports on the Ethernet service processing board must be enabled.

U2000
NOTE
Procedure


Step 3 Set Loopback Check to Enabled.
----End
A.9.11 LPT Configuration

When you use LPT function, you need to configure the relationship between LPT ports and
the related information of LPT ports.
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
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.
l E-Line services carried by PWs exclusively occupying UNI ports have been configured.
NOTE
l For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and Model 2 in
QinQ-Based E-Line Service Models.
l For the service models of E-Line services carried by PWs exclusively occupying UNI ports, see Model 3
in PW-Carried E-Line Services.

U2000
NOTE
Procedure
Step 2 Click the Point-to-Point LPT tab.
Step 3 Select PW or QinQ services that require the LPT function.
Step 4 Click Bind in the lower right corner of the pane. Then, choose PW+QinQ from the shortcut
menu.
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-to-
multipoint manner.
l For the service models of QinQ services sharing UNI ports, see Model 3 in QinQ-Based E-Line Service
Models.
l For the service models of E-Line services carried by PWs sharing UNI ports, see Model 1 and Model 2 in
PW-Carried E-Line Services.

U2000
NOTE
Procedure
Step 2 Click the Point-to-Multipoint LPT tab.
Step 3 Click New in the lower right corner of the pane based on the type of service network.
Step 4 Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network.
The Create LPT dialog box is displayed.
Step 5 Set the parameters of the primary and secondary points of LPT.
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
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.
l You are an NMS user with administrator rights or higher rights.
l 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.
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.
l For a VUNI measurement point, set the following parameters: Direction, Service, Port,
VLAN, and Priority.
l For a QinQ measurement point, set Direction, Service, and QinQ Link.
l For a tunnel measurement point, set Direction, Tunnel ID, Port, PW Label, Service
Tag Role, and PW Type.

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/910Adoes 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

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 hold-
off time, WTR time, and guard time.
Prerequisites
l An ERPS instance has been created.

U2000
Procedure
ERPS Management from the Function Tree.
Step 2 Optional: Double-click Control VLAN, and then modify the control VLAN ID.
Step 3 Optional: Set the parameters of the ERPS protocol.

NOTE
Set the parameters according to the network plan. Default values are recommended.
Step 4 Click Apply.
----End
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.
A.10.2.1 Creating a LAG

To improve bandwidth and availability of Ethernet links between two NEs, you need to create
the corresponding LAG.
Prerequisites
l The EFP8/EMS6 board where the LAG ports are located must be added in the NE Panel.

U2000

Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Configuration > Ethernet Interface Management > Ethernet Link Aggregation
Step 3 Click New.

The Create Link Aggregation Group dialog box is displayed.
Step 4 In Attributes Settings, set the parameters of the LAG.
Step 5 In Port Settings, set the LAG ports.

1. Set Main Port.
2. Select a slave port from Available Standby Ports and then click .
NOTE
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the
ports.
Step 6 Click OK.

Step 7 Click OK.
----End

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

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.

Prerequisites

U2000
Procedure
Step 3 In the main interface, select the LAG to be queried.
Step 4 Click Query to check the working status of the main and slave ports in the LAG.
NOTE
The system automatically displays the working status of the slave port at the bottom of the main interface.
Step 5 Right-click the LAG and select an option from the drop-down list. A dialog box is displayed,
indicating the query result.
Step 6 Click Close.
Step 8 Click Query to check the parameters associated with the port priority and system priority.
----End
A.10.3 Configuring Ethernet Services

The EFP8/EMS6 board supports EPL, EVPL, EPLAN, and EPVLAN services.
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.


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.

Step 6 Optional: Set the bound path.

The Bound Path Configuration dialog box is displayed. Set the attributes of the bound
path.
2. In Configurable Ports, select a VCTRUNK as the configurable port.

3. In Available Bound Paths, set Direction of the bound path.
4. Select required items in Available Resources and Available Timeslots and click
.
5. Optional: Repeat Step 6.4 to bind other VC paths.
6. Click OK.
7. Click Yes.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the
result of directly setting the attributes of VCTRUNKs.
Step 7 Click OK.Then, close the dialog box that is displayed.
----End
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


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.
l Set the attributes of the IEEE 802.1d bridge.

Step 4 Set the ports to be connected to the bridge.

1. Click Configure Mount.
The Service Mount Configuration dialog box is displayed.
2. Select a port from the ports listed in Available Mounted Ports, and then click
.
3. Optional: Repeat Step 4.2 to mount other ports.

4. Click OK.
path.



6. Click OK.
7. Click Yes.
NOTE
----End
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.

Prerequisites
l The IEEE 802.1q/802.1ad bridge-based Ethernet LAN services must be created.
l In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of
the VB must be IVL.
Procedure
Step 2 Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
Step 3 Create the VLAN filtering table.

1. Click New.
The Create VLAN dialog box is displayed.
2. Set VLAN ID(e.g:1,3-6).
3. Select a port from the ports listed in Available forwarding ports, and then click
.
4. Optional: Repeat Step 3.3 to select other forwarding ports.
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.

Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.
The Create Ethernet Line Service dialog box is displayed.
Step 4 Set the attributes of the QinQ-based EVPL service.

Step 5 Optional: Set the port attributes.

NOTE
The result of setting the port attributes during the Ethernet private line service configuration process is the
same as the result of directly setting the Ethernet service port attributes.

path.

.
6. Click OK.
7. Click Yes.
NOTE
----End
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.

Prerequisites

U2000
Procedure
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the IEEE 802.1ad bridge.
Step 4 Set service mounting relationships.

1. Click Configure Mount.

The Service Mount Configuration dialog box is displayed.

2. Set the parameters for configuring mounted services.
3. Click Add Mount Port.
4. Repeat Step 4.2 and Step 4.3 to add the other mounted ports.
5. Click OK.
6. Optional: You can change the Ethernet port attributes of the mounted ports in the
Service Mount window.
path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
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

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.

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

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

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

U2000

Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
Step 2 Modify the aging time of the MAC address table entry.
1. Double-click MAC Address Aging Time corresponding to the EFP8 board.
The MAC Address Aging Time dialog box is displayed.
2. Set the duration and unit of the aging time.
3. Click OK.
Step 3 Click Apply.
----End
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

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.

Prerequisites

U2000
Precautions
l In the case of EVPLAN services, you can query the capacity of a MAC address table
where MAC addresses are queried based on VLAN IDs and the capacity of a MAC
address table where MAC addresses are queried based on VB logical ports.
l In the case of EPLAN services, you can query the capacity of a MAC address table
where MAC addresses are queried based on VB logical ports.
Procedure
Step 2 Select a created bridge.
Step 3 Query the actual number of dynamically learnt MAC addresses based on the VLAN IDs.
1. Click the VLAN MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of
the MAC address table.
Step 4 Query the actual number of dynamically learnt MAC addresses based on the VB ports.
1. Click the VB Port MAC Address Table Capacity tab.
2. Click Query. Then, close the dialog box that is displayed. Check the actual capacity of
the MAC address table.
----End
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


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.
Step 5 Set the TAG attribute of the port.

1. Click the TAG Attributes tab.
2. Set the TAG attribute of the port.
Step 6 Set the network attributes of the port.

1. Click the Network Attributes tab.
2. Set the network attributes of the port.

Step 7 Set the advanced attributes of the port.

1. Click the Advanced Attributes tab.
2. Set the advanced attributes of the port.
----End
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

U2000
Precautions
The EFP8 board supports VCTRUNKs 1-16. VCTRUNKs 1-16 determine the services to be
transmitted depending on information about the created Ethernet services.
The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be
transmitted depending on information about the created Ethernet services.
Procedure
Step 2 Select Internal Port.
Step 3 Optional: Set the TAG attribute of the VCTRUNK.

1. Click the TAG Attributes tab.
2. Set the TAG attribute of the VCTRUNK.

Step 4 Set the encapsulation and mapping protocol used by the VCTRUNK.
1. Click the Encapsulation/Mapping tab.
2. Set Mapping Protocol and the protocol parameters.

Step 5 Optional: Set the network attributes of the VCTRUNK.
1. Click the Network Attributes tab.
2. Set the network attributes of the VCTRUNK.

Step 6 Configure the LCAS function for the port.
1. Click the LCAS tab.
2. Set the Enabling LCAS parameter and other LCAS parameters.

Step 7 Click Bound Path.

path.


.
6. Click OK.
7. Click Yes.
NOTE
----End
A.10.5.3 Modifying the Type Field of QinQ Frames

The default type field of QinQ frames is 0x8100.
Prerequisites

U2000
Procedure
Configuration > Advance Attribute > QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Step 3 Click Apply.
----End
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


U2000
Procedure
Step 2 Select Internal Port.
Step 3 Click the Bound Path tab.
Step 4 Click Configuration.

The Bound Path Configuration dialog box is displayed.
Step 5 Optional: Dynamically increase the VCTRUNK bandwidth.

2. In Available Bound Paths, set Level and Service Direction of the bound paths.
Step 6 Optional: Dynamically decrease the VCTRUNK bandwidth.

1. Deselect the Display in Combination check box.
2. Select the VC paths to be deleted in Selected Bound Paths, and then click .
3. Optional: Repeat Step 6.2 to delete other VC paths.

Step 7 Click OK.

Step 8 Click Yes.
----End
A.10.6 Managing the Spanning Tree Protocol

The OptiX RTN OptiX RTN 950 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

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



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 The STP or RSTP must be enabled for the bridge.

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
Step 2 Query the bridge running information.
1. Click the Bridge Running Information tab.
2. Click Query.
3. Check the bridge running information.
Step 3 Query the port running information.
1. Click the Port Running Information tab.
2. Click Query.
3. Check the port running information.
----End
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.

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.
l The IGMP Snooping protocol must be enabled for the bridge.

U2000
Procedure
Function Tree.
Step 2 Click the Static Multicast Table tab.
Step 3 Click New.

The Create Static Multicast Item dialog box is displayed.
Step 4 Set the attributes of static multicast entries.
1. Set VB ID, VLAN ID, and MAC Address.
2. In Multicast Port, select the member ports corresponding to the static multicast entries.
Click .
NOTE
To select more than one port at a time, press and hold the Ctrl or Shift key when selecting the
ports.

3. Click OK.
----End
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

U2000
Procedure
Function Tree.
Step 2 Click the Multicast Aging Time tab.
Step 3 Modify the aging time of the multicast table entries.

Step 4 Click Apply.
----End
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

U2000
Procedure
Function Tree.
Step 2 Query the information about the router port.

1. Click the Multicast Router Port Management tab.
2. Click Query. Check the information about the router port.
Step 3 Query the information about the multicast table entries.

1. Click the Multicast Table Item tab.
2. Click Query. Check the information about the multicast table entries.
----End
A.10.8 Managing the QoS

By managing the QoS, you can provide differentiated services for different service types.
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.


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

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the CAR Configuration.
Step 3 Click New.

The New CAR dialog box is displayed.
Step 4 Set the CAR parameters.
Step 5 Click OK.
----End
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

U2000
Procedure
Step 2 Click the CoS Configuration tab.
Step 3 Click New.

The New CoS dialog box is displayed.
Step 4 Set the CoS parameters.


Step 5 Click OK.
----End
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.
l The CAR/CoS must be created.

U2000
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration > QoS
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.

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 shaping-
associated parameters.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object Tree and
choose Configuration > QoS Management > Port Shaping Management from the
Function Tree.
Step 2 In Port List, select a port. In Port Queue Shaping Information, set the traffic shaping
information about the egress queues.
Step 3 Click Apply.
----End
A.10.8.6 Configuring Port Shaping

This section describes how to configure the traffic shaping for an egress port.
Prerequisites

U2000
Procedure
Step 1 In the NE Explorer, select the EMS6 board from the Object Tree and choose Configuration >
QoS Management > Port Shaping Management from the Function Tree.

Step 2 Click the Port Shaping tab.
Step 3 Set the port shaping parameters for a port.
Step 4 Click Apply.
----End
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

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.

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

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

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 The Ethernet services must be created and activated.
l The MD and MA must be created.

U2000
Precautions
In an OAM test, all MPs that are involved in the operation of the same service flow must be in
the same MD. In an existing MD involved in the same service flow, creating an MP of the
same level or a higher level may damage the existing MD. As a result, the OAM test fails.
Procedure
Step 2 Click New.

The Create MP dialog box is displayed.
Step 3 Set the parameters of the new MP.
Step 4 Optional: Click Advanced. In the displayed dialog box, set the corresponding parameters
and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configurations:
l Activate the CC and set the sending period of the CC test.
l Set the timeout time for the LB or LT test.

Step 5 Click OK.
----End
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.
l The MD and MA must be created.
l The MEPs must be created.

U2000
l Only the MEP can enable the continuity test and function as the receive respond end for
the test.
l The source MEP constructs CCM packets and transmits them periodically. After
receiving the CCM packet from the source MEP, the sink MEP directly enables the CC
function for this source MEP. If the sink MEP fails to receive the CCM packet from the
source MEP within the check period (that is, 3.5 times of the transmission interval), it
reports the specific alarm automatically.
l Performing a CC test does not affect the services.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Activate CC.
NOTE
l Before the CC test, you can set CCM Sending Period(ms) according to the actual requirements.
l To disable a CC test, right-click the MEP where the CC test is performed and then choose Activate
CC from the shortcut menu.
NOTE
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC
l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Inactivate CC
----End


MEP and any MP in the same maintenance association (MA).
Prerequisites
l In the case of a standard MP, you must activate CC before an LB test.

U2000
l Only an MEP can initiate an LB test.
l During the LB test, the source MEP constructs and transmits the LBM frames and starts
the timer. If the sink MP receives the LBM frames, it sends the LBR frames back to the
source MEP. This indicates that the loopback is successful. If the source MEP timer
times out, it indicates that the loopback fails.
l Performing an LB test does not affect the services.
Procedure
Step 2 Select the node that requires an LB test, click OAM Operation, and select Start LB.
Step 3 Set the parameters involved in the LB test.

NOTE
l In the case of standard MPs, when an MIP functions as the receive end in the LB test, you need to select
Test based on the MAC Address and set LB Sink MP MAC Address.
l Before the LB test, you can set LB Timeout(ms) according to the actual requirements.
Step 4 Click Start LB. Then, the test result is displayed.

NOTE
To enable an LB test, you can also right-click an MEP and then choose Start LB from the shortcut
menu.
----End

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.
l During the LT test, the source MEP constructs and transmits the LTM frames and starts
the timer. All the MPs that receive the LTM frames send the LTR frame response.
According to the LTR frame response, you can verify all the MIPs that pass from the
source MEP to the sink MEP.
l Performing an LT test does not affect the services.
Procedure
Step 2 Select the node that requires an LT test, click OAM Operation, and select Start LT.
Step 3 Set the parameters involved in the LT test.

NOTE
Before the test, you can set LT Timeout(ms) according to the actual requirements.
Step 4 Click Start LT. Then, the test result is displayed.

NOTE
To enable an LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
----End

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.


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

U2000

The performance check method provides an in-service test of packet loss ratio and delay
based on the check of the connectivity between the MPs on the Ethernet service processing
unit.
A performance check is implemented as follows: The source MP initiates several LB tests and
counts different packet loss ratio and delay values.
Procedure
Step 2 Select the node to be monitored, click OAM Operation, and select Performance Detect.
The Performance Detect dialog box is displayed.
Step 3 Select Send Mode. Then, set Frame Length, Timeout, and Detect Attempts for the test
packet.
Step 4 Set Source MP ID and Destination MP ID.
Step 5 Click Start Detect. Then, the check result is displayed.
----End
A.10.10 Using the Ethernet port OAM

By using the Ethernet port OAM, you can maintain the point-to-point Ethernet links.
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

U2000
The OAM auto-discovery is achieved based on auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm.
After OAM auto-discovery is successful, the link performance is monitored according to the
error frame threshold. You can set the error frame threshold on the NMS.

Procedure
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree.
Step 3 Select the port and set OAM Working Mode.
NOTE
l The OAM mode includes the active mode and the passive mode. For two interconnected systems,
the OAM mode of either or both systems must be the active mode. Otherwise, OAM auto-discovery
fails.
l If the OAM modes of the two systems are passive modes, if a fault occurs on the link, or if one
system fails to receive the OAM protocol message within five consecutive seconds, an alarm is
reported, indicating that OAM auto-discovery fails.
Step 4 Select Enabled from the Enable OAM Protocol drop-down list.
Step 5 Click Apply.
Step 6 Click the Remote OAM Parameter tab. Click Query to check the OAM capability of the
opposite end.
----End
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.

l The local end can notify the opposite end of link fault events only if Remote Alarm
Support for Link Event is set to Enabled at the local end.
l The local end can notify the opposite end of link performance events only if Remote
Alarm Support for Link Event is set to Enabled and if the monitoring time and error
frame thresholds are configured at the local end.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite end detects link performance degradation, you can query the
ETHOAM_RMT_SD alarm, which is reported on the local end, by using the NMS.
According to the alarm, you can determine the type of the link performance event.
l After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite equipment detects a link fault event or encounters a fault that makes the
equipment fail to be restored (such as a power failure), you can query the
ETHOAM_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the
NMS. Based on the alarm, you can determine the fault type.
Procedure
Step 3 Select the corresponding port and set Link Event Notification to Enabled.
Step 4 Click Apply.
----End
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:

l The OAM auto-discovery operation is successful.

l Remote Alarm Support for Link Event is set to Enabled and the monitoring time and
error frame thresholds have been configured at the local end.
If Remote Alarm Support for Link Event is also set to Enabled at the opposite end, the
opposite end notifies the local end after detecting a link event, and then the local end
generates the corresponding alarm.
Procedure
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
Step 4 Click Apply.
----End
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.
l On the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
l The equipment that responds to the loopback must support remote loopbacks.

U2000
l If a port is capable of responding to loopbacks, it enters the Respond Loopback of
Remote state and reports the loopback responding alarm when receiving the command
of enabling the remote loopback function sent from the opposite OAM port. In this case,
the equipment that initiates the loopback enters the loopback initiating state and reports
the loopback initiating alarm.
l Generally, after the remote loopback function is enabled, service packets, except the
OAMPDU packets, are looped back at the remote end.
l After using the remote loopback function to locate faults and test link performance, you
should disable the remote loopback function at the end where the loopback is initiated
and then restore the services. At this time, the alarm clears automatically.

Procedure
Step 3 Choose Enable Remote Loopback from the OAM drop-down menu. Then, close the dialog
box that is displayed.
----End
A.10.11 Configuring LPT

After enabling the LPT function for an Ethernet service, you need to configure the LPT port
and the relevant information.
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.
l The data services must be configured as EPL services that are transmitted from PORTs to
VCTRUNKs and do not carry any VLAN tags.
l An Ethernet port on which the LPT function is enabled must be in auto-negotiation
mode.

U2000
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can
select only one configuration mode to implement the LPT function.
Procedure
Configuration > Ethernet Interface Management > LPT Management from the Function
Tree.

Step 2 Click Query.
Step 3 Select a PORT and a VCTRUNK, and then set the following parameters.
NOTE
If LPT is enabled, you can set PORT-Type Port Hold-Off Time(ms) and VCTRUNK Port Hold-Off
Time(ms) according to actual requirements.
Step 4 Click Apply.
----End
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.
l An Ethernet port on which the LPT function is enabled must be in auto-negotiation
mode.

U2000
Precautions
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can
select only one configuration mode to implement the LPT function.
NOTICE
Before configuring the point-to-multipoint LPT function, make sure that the following two
conditions are met. Otherwise, the services may be interrupted.
l The data services are displayed in the tree topology.
l The data service topology is consistent with the topology of the LPT.

Procedure
Configuration > Ethernet Interface Management > LPT Management from the Function
Tree.
Step 2 Click PtoMP LPT. Then, the LPT Management dialog box appears.
Step 3 Click New.
Step 4 Set the parameters in Convergence Point.

Step 5 Set the parameters in Access Point.
1. Select the ports from Port and then click .

2. If you select a VCTRUNK, set Bearer Mode.
Step 6 Click OK.
----End
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.

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

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.

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

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.


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

If... Then...
The MPLS tunnel OAM 1. In the NE Explorer, select the required NE from the Object
standard needs to be Tree and choose Configuration > MPLS Management >
changed Unicast Tunnel Management from the Function Tree.
2. Click the Static Tunnel tab.
The MPLS PW OAM 1. In the NE Explorer, select the required NE from the Object
standard needs to be Tree and choose Configuration > MPLS Management >
changed 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 MPLS-
TP OAM does not support the original transmission interval of CC packets, the transmission interval will
change to a value closest to the original value and there is a possibility that related switching is triggered.
Step 3 Close the operation result dialog box that is displayed.

NOTE
----End
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.
l The LSR ID of each NE is set correctly.

U2000

NOTE
Procedure
Step 3 Click New and choose Unidirectional Tunnel from the drop-down list.
Step 4 Select New Reverse Tunnel.
Step 5 Set parameters for the new MPLS tunnel.
----End

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.
l The LSR ID of each NE has been correctly configured.

U2000
NOTE
Procedure
Step 3 Click New and choose Bidirectional Tunnel from the drop-down list.
The New Unicast Bidirectional Tunnel dialog box is displayed.
Step 4 Set parameters for the bidirectional MPLS tunnel.

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

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.

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

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.
l Node Type is set to Ingress or Egress for tunnels.

U2000
NOTE
Procedure
Step 3 Select the required MPLS tunnel and set MPLS OAM (Y.1711) parameters.
----End
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.

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.

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..
l If the tunnel uses MPLS-TP OAM, click the MPLS-TP OAM tab page.

Step 3 Select the desired tunnel and click OAM Operation at lower right of the main interface.
Step 4 Select Query LSP Status from the drop-down list. Then, close the dialog box that is
displayed.
Step 5 Check the tunnel status according to the LSP Status parameter value in the main interface.
NOTE
For OptiX RTN 950, if MPLS-TP OAM is used, the queried information about LSP status, defect position,
and unavailable duration is invalid.
NOTE
l Alternatively, you can select a tunnel, right-click the tunnel, and select LSP Status from the drop-
down list.
----End
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.
l The tunnel is not configured in any protection group.

U2000
NOTE
Procedure
Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface.
Step 4 Select Clear OAM from the drop-down list. Then, close the dialog box that is displayed.
NOTE
After this step is performed, OAM parameters for the tunnel are restored to default values. If OAM
operations need to be performed, you need to re-enable and configure the OAM functions.
NOTE
l Alternatively, you can select a tunnel, right-click the tunnel, and select Clear OAM from the drop-
down list.
----End

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

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 drop-
down list.
The Traceroute Test dialog box is displayed.
Step 5 Set parameters for the traceroute test.

NOTE
l If LSP traceroute uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN
----End
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.

Prerequisites
l The MPLS tunnel has been configured, with its ingress/egress node as an MEP.
l The MPLS-TP tunnel OAM standard has been changed to Y.1731.

U2000
NOTE
Procedure
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.
l The MPLS-TP tunnel OAM standard has been changed to Y.1731.
l Global OAM parameters have been configured.

U2000
NOTE
Procedure

Step 3 Click the MIP tab.
Step 4 Click New.

The Create Tunnel MIP dialog box is displayed.
Step 5 Set parameters for the newly configured MIP.

NOTE
l An NE allows for only one MIP for one tunnel.

l If MEG ID Type of the MEP on a tunnel is IP Based, you do not need to create an MIP.
----End
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.

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.

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.

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

U2000
This task is supported only when the configuration is performed in end-to-end mode on the
U2000.

NOTE
l It is recommended that you measure the performance of MPLS tunnels deployed in end-to-end manner by
performing the preceding procedure. For MPLS tunnels deployed on a per-NE basis, it is recommended
that you convert the MPLS tunnels to end-to-end ones by referring to A.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

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.
l OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support this
operation.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all MPLS
tunnels that meet the filter conditions.
menu.
Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.

Step 5 Select the NE to initiate the TST test and click Run.
Step 6 View the test result in Test Statistics.
----End
A.11.3 Managing MPLS APS Protection Groups

MPLS APS is the commonest protection mode for MPLS tunnels.
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.

Prerequisites
l The working and protection MPLS tunnels have been created.
l MPLS OAM as been enabled for both working and protection MPLS tunnel in the
protection group.
l The protection tunnel cannot carry extra services.
l PW APS protection is not configured for the service.

U2000
NOTE
MPLS OAM needs to be enabled for working and protection tunnels. The detection packets
used by MPLS OAM are FFD packets. FFD packets are usually sent at an interval of 3.3 ms.
If the packet transmission delay time of an MPLS tunnel exceeds 3.3 ms, the transmission
interval of FFD packets needs to be a value greater than the delay time.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click the Tunnel APS Management tab.
Step 3 Click New.

The New Tunnel Protection Group dialog box is displayed.
Step 4 Set parameters for the MPLS APS protection group.
NOTE
When creating an MPLS APS protection group, set Protocol Status to Disabled. Start the protocol only
when the MPLS APS protection group is successfully created on nodes at both ends.

----End
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.
l The MPLS APS protocol has been enabled.

U2000
NOTE
Procedure
APS Protection Management from the Function Tree.

Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about
the protection group.
Step 4 Select the required protection group and click Function.
displayed. Check the status of the protection group.
----End
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.

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

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


3. Click Yes.Then, close the dialog box that is displayed.
Step 4 Start the MPLS APS protocol.
2. Select Start Protocol from the drop-down list. Then, close the dialog box that is
displayed.
NOTE
Alternatively, you can select the required protection group, right-click the protection group, and choose
Start Protocol or Stop Protocol from the shortcut menu.
----End
A.11.4 Managing PWs

All types of PWE3 services are carried by PWs.
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.

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
A.11.4.2 Creating an MS-PW

This topic describes how to configure cross-connections for front-end and rear-end PWs at an
S-PE node and create an MS-PW.
Prerequisites

U2000
NOTE
The steps for creating MS-PWs vary according to service types. This topic uses an Ethernet
service as an example to describe how to create MS-PWs.
Procedure
Step 2 Click the MS PW tab.
NOTE
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW Management tab and click the MS PW tab.
Step 3 Click New.

The Create MS PW dialog box is displayed.
Step 4 In the main interface, configure basic service information.

Step 5 Click the PW Basic Attributes tab and set PW parameters.

NOTE
If you create an MS-PW using the Web LCT, perform the following operations:
Click the PW General Attributes tab and set PW parameters.
Step 6 Click the QoS tab and set QoS parameters.
Step 7 Click the Advanced Attributes tab and set advanced attributes.
----End
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.

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.

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
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.
l The MPLS-TP PW OAM standard has been changed to Y.1731.

U2000
NOTE
Procedure


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.
l The MPLS-TP PW OAM standard has been changed to Y.1731.
l Global OAM parameters have been configured.

U2000
NOTE
Procedure
Step 3 Click the MIP tab.
Step 4 Click New.
The Create MS PW MIP dialog box is displayed.
Step 5 Set parameters for the newly configured MIP.
NOTE
l An NE allows for only one MIP for one MS-PW.

l If MEG ID Type of the MEP on an MS-PW is IP Based, you do not need to create an MIP.
----End

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.

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

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.

Prerequisites

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

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

----End
A.11.5 Managing a PW APS/PW FPS Protection Group

PW APS and PW FPS are two modes for protecting PWs.

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.
l The tunnel carrying the working and protection PWs has been created.

U2000
NOTE
PW OAM needs to be enabled for the working and protection PWs of a PW APS protection
group. The detection packets used by PW OAM are FFD packets. FFD packets are usually
sent at an interval of 3.3 ms. If the packet transmission delay time of a PW exceeds 3.3 ms,
the transmission interval of FFD packets needs to be a value greater than the delay time.
You can create a PW APS protection group during initial service configuration or after service
configuration.
l During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW APS protection group.
l If services are already configured, create the PW APS protection group in the Protection
Group tab page.
l For SS-PWs and MS-PWs, configuration of the PW APS protection group needs to be
done on both source NE and sink NE.
NOTE
l This topic describes how to configure PW APS after services are configured.
l This topic uses a PW-carried E-Line service as an example to describe how to configure PW APS
protection. The methods of configuring PW APS protection for other types of service are similar.
Procedure
Step 2 Select the required services and click the Protection Group tab.
Step 3 Click PW APS.
Step 4 Click New.

Step 5 Click the Basic Attributes tab and set the basic attributes of the protection PW.

NOTE
If you create a PW APS protection group using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.
Step 6 Click the Protection Group tab and set information about the PW APS protection group.
NOTE
When creating a PW APS protection group, set Enabling Status to Disabled. Start the protocol only when
the PW APS protection group is successfully created on nodes at both ends.
Step 7 Click PW OAM and configure OAM information.

NOTE
l When the PW APS protection group is created, the PW OAM function is automatically enabled to
detect the PW status.
l You can also configure OAM information by choosing Configuration > MPLS Management >
PW Management > PW OAM Parameter.

----End
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.
l The tunnels carrying the working and protection PWs have been created.

U2000
Background
Enable MPLS-TP OAM for both the working and protection PWs in the PW FPS protection
group. The packet transmission interval is often set to 3.3 ms for the enabled MPLS-TP
OAM. If the packet transmitting delay jitter in a PW exceeds 3.3 ms, set the packet
transmission interval to a value greater than the delay.
PW APS protection groups can be created when services are initially configured or after
services are configured.
l During initial service configuration, set Protection Type to PW APS, create the working
and protection PWs, use the PWs to configure a PW FPS protection group.
l If services are already configured, create the PW FPS protection group on the Protect
Group tab page.
l For SS-PWs and MS-PWs, configuration of the PW FPS protection group needs to be
done on the both source NE and sink NE.
NOTE
l This topic only describes how to configure PW FPS after services are configured.
l A PW-carried E-Line service is used as an example to describe how to configure PW FPS protection. The
methods of configuring PW FPS protection for other types of service are similar.

Procedure
Step 2 Select the desired service and click the Protect Group tab.
Step 3 Click PW FPS.
Step 4 Click New.

NOTE
If you configure the PW using the Web LCT, perform the following operations:
Click the PW tab and set the basic attributes of the protection PW.
Step 6 Click the Protect Group tab and set information about the PW FPS protection group.
Step 7 Click MPLS-TP OAM and configure the OAM information.

NOTE
l When the PW FPS protection group is created, the MPLS-TP OAM function is automatically
enabled to detect the PW status.
l You can also choose Configuration > MPLS Management > PW Management > MPLS-TP
OAM to configure the OAM information.

Step 9 Select the service configured with the PW FPS configuration, and set ARP Dual Feed to
Enabled.
----End
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.
l MPLS APS protection is not configured for the service.
l The tunnel carrying the working and protection PWs has been created.

U2000
NOTE
The slave protection pairs are bound with a PW APS protection group. You can create a slave
protection pair during initial service configuration or after service configuration.

l During initial service configuration, set Protection Type to Slave Protection Pair,
create the working and protection PWs, use the PWs to configure a slave protection pair.
l If services are already configured, create the slave protection pair in the Protection
Group tab page.
l For SS-PWs and MS-PWs, binding of a slave protection pair to a PW APS protection
group requires that the slave protection pair is added on both the source NE and sink NE.
NOTE
l This topic describes how to configure a slave protection pair after services are configured.
l This topic uses a PW-carried E-Line service as an example to describe how to configure a slave protection
pair. The methods of configuring slave protection pairs for other types of service are similar.
Procedure
Step 2 Select the required services and click the Protection Group tab.
Step 3 Click Slave Protection Pair.
Step 4 Click New.
Step 6 Click the Protect Group tab and set the ID of the PW APS protection group to which the
slave protection pair is bound.
NOTE
You can manually enter an ID, or double-click the ID parameter and select from the drop-down list.

----End
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.
l The PW APS protocol has been enabled.

U2000
NOTE
Procedure
Step 2 Click the PW APS Management tab.
Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about
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

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

U2000
NOTE

Procedure
Step 3 Stop the PW APS protocol.

2. Select Stop Protocol from the drop-down list.
NOTICE
After the PW APS protocol is stopped, the protection group fails. In addition, services
are unavailable until the working channel is restored or the PW APS protocol is

Step 4 Start the PW APS protocol.

2. Select Start Protocol from the drop-down list. Then, close the dialog box that is
displayed.
NOTE
You can enable or disable the PW APS protocol by using either of the following methods:
l Select the required protection group, right-click the protection group, and choose Start Protocol or
Stop Protocol from the short-cut menu.
l Set Enabling Status to Enabled or Disabled.
----End
A.11.6 Managing CES Services
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.
l The MPLS tunnel that carries the PW has been configured.


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.
l It is recommended that you create protection information before creating a CES service.
In this configuration example, Protection Type is set to No Protection. For details on
how to configure protection information, see 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.

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

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.

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 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.
l No ACR clock has been configured for the CES service.

U2000
NOTE
Procedure
Step 2 Select the required CES service and click Delete.

Step 4 Click Query, and then close the dialog box that is displayed to check whether the CES
service is successfully deleted.
----End
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.

----End
A.11.7 Managing ATM/IMA Ports

The OptiX RTN 905 does not support ATM/IMA services.
A.11.7.1 Binding ATM TRUNKs

An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial
ports (SPs) that transmit ATM/IMA services.
Prerequisites
l For ATM/IMA E1 services, set Port Mode in PDH Interface to Layer 2.
l For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and
configure A.8.7 Setting Serial Port Parameters.

U2000
NOTE

Context
NOTE
Procedure
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 to bind the
required E1 ports or SPs to the ATM TRUNK.
NOTE
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports,
select E1 in Level.
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports,
select Fractional E1 in Level.
----End
Follow-up Procedure
If the IMA group is required, you need to bind the member links of the IMA group with the
ATM TRUNK, enable the IMA protocol for the ATM TRUNK, and then configure the
parameters of the IMA group.

A.11.7.2 Configuring an IMA group

If the ATM TRUNK binds IMA E1 links or Fractional IMA links, you need to configure the
parameters of the IMA group.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the IMA Group Management tab.
Step 3 Configure the parameters of the IMA group according to the network plan.
NOTE
l Set IMA Protocol Enable Status to Enabled if the links bound in the ATM TRUNK require the
IMA protocol; otherwise, set this parameter to Disabled.
l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound
in the ATM TRUNK start running the IMA protocol.
l The values of Minimum Number of Active Transmitting Links and Minimum Number of
Active Receiving Links must be the same because the OptiX RTN 950 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
A.11.7.3 Setting ATM Port Parameters

This topic describes how to configure ATM port parameters.

Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the ATM Interface Management tab.
Step 3 Configure and adjust the ATM port attributes.
NOTE
l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface
on the common ATM network or to the user-side interface of the PE on the PSN network that transmits
ATM PWE3 services.
l NNI: the port connecting network-side devices. For example, the NNI port applies to the network-side
interface on the common ATM network.
l The ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is
mapped into E1 signals. Therefore, it is recommended that you set ATM Cell Payload Scrambling to
Enabled.
l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link.
Otherwise, packet loss will occur.
Step 4 Click Apply, and close the dialog box that is displayed.
----End
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

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

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.
l Before creating ATM PWE3 services, you need to bind member links to the ATM
TRUNK, set the parameters of the IMA group, and create the MPLS tunnels that carries
PWs.

U2000
NOTE
l The OptiX RTN 905 does not support ATM/IMA services.
l To create ATM PWE3 services (UNIs-NNI), it is recommended that you create services
before configuring PW protection. Configuration will be simplified in this manner.
l In this configuration example, Protection Type is set to No Protection. For details on
how to configure PW protection, see 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.

Step 4 Click the Connection tab and configure the attributes of the ATM connection.
Step 5 Click PW, and click Add to configure the attributes of PWs.
1. Click the General Attributes tab and set the basic attributes of PWs.
NOTE
If you create ATM services using the Web LCT, click Use existing resource or New to select a tunnel.
It is recommended that you create tunnels in advance and click Use existing resource to select a
created tunnel.
2. Click the QoS tab and enable the PW bandwidth restriction.

3. Click the Advanced Attributes tab to configure the advanced attributes of PWs.
Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.
----End
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

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click Query, and close the dialog box that is displayed.
Step 3 Select the required ATM service and modify the parameters of the ATM service.

----End
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

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.

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

Context
NOTE
Procedure
the Function Tree.
Step 3 Select the required ATM-Diffserv domain and modify its parameters according to the

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.

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

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


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

U2000
NOTE
Context
NOTE

Procedure
Step 2 Click the CC Activation Status tab.
Step 3 Configure the parameters of the CC test according to the planning information.
----End
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


This topic describes how to perform a loopback (LB) test. An LB test can be performed to
continuously check the bidirectional connectivity of an ATM link.
Prerequisites

U2000
NOTE
Context
NOTE
Procedure
Step 2 Click the Remote Loopback Test tab.
Step 3 Configure the attributes of the LB test according to the planning information.
Step 4 Select an ATM connection for which an LB test needs to be performed.

NOTE
By pressing the Ctrl key on the keyboard, you can select multiple ATM connections at one time.
Step 5 Click Test, and close the dialog box that is displayed.
Step 6 Check Test Result.
----End
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.

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.

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

Procedure
Interface Management > MP Group Management from the Function Tree.
Step 3 Click Running Status. Check Link Status. Then, close the dialog box that is displayed.
----End
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.

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.

Prerequisites

U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Physical Clock > Clock Source Priority.
Step 2 Click the System Clock Source Priority List tab.

The Add Clock Source dialog box is displayed.
Step 4 Select the clock sources.

NOTE
Hold the Ctrl key on the keyboard to select multiple clock sources.
Step 5 Click OK.
Step 6 Optional: Repeat Step 3 to Step 5 to add other clock sources.
Step 7 Optional: Select a clock source and click or to adjust the priority of
this clock source.
NOTE
The clock priorities levels are arranged in a descending order from the first row to the last row. The internal
clock source is always of the lowest priority.
Step 8 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external
clock sources.

Step 9 Click Apply.
----End
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.


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 a Clock Source Group

On a ring network, a clock source group must be configured to avoid clock loops.
Prerequisites
l Clock sources have been configured.
l SSM protocols have been configured.


U2000
NOTE
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose ConfigurationClockPhysical
ClockClock Source Group from the Function Tree.
Step 2 Click New in the right pane. The Create Clock Source dialog box is displayed.
Step 3 Select the desired port and click
to add it into the clock group.

NOTE
You can press and hold the Ctrl key to select multiple ports at a time.
To delete a port, select the port and click .

Step 4 Click OK.
----End
A.12.1.7 Configuring the SSM Output Status

After the standard SSM protocol or extended synchronization status message (SSM) protocol
is enabled, the NE transmits the SSM to other NEs through the SDH radio link or optical line
by default. To prevent two clock subnets from affecting each other, the NE needs to forbid the
SSM bytes from being transmitted on the link that is connected to other clock subnets.
Prerequisites
l The standard SSM or extended SSM protocol is enabled.

U2000
NOTE
Procedure
Step 2 Click the SSM Output tab.
Step 3 Set the SSM control status.
NOTE
l Output S1 Byte Info is valid only when the SSM protocol or the extended SSM protocol is started.
l Output S1 Byte Info indicates whether the SSM is output at the line port.
l When the line port is connected to an NE in the same clock subnet, set Output S1 Byte Info to Enabled.
Otherwise, set this parameter to Disabled.
Step 4 Click Apply.
----End
A.12.1.8 Configuring the Clock ID Output Status

After the extended synchronization status message (SSM) protocol is enabled, the NE
transmits the clock ID to other NEs through the radio link or optical line by default. To
prevent two clock subnets from affecting each other, the NE needs to forbid the clock ID from
being transmitted on the link that is connected to other clock subnets.

Prerequisites
l The extended SSM protocol must be enabled.

U2000
NOTE
Procedure
Step 2 Click the Clock ID Output tab.
Step 3 Set the clock ID control status.
NOTE
l Output Clock ID is valid only when the extended SSM protocol is started.
l Output Clock ID indicates whether the clock source ID is output at the line port.
l If the line ports are connected to the NEs in the same clock subnet and if the extended SSM protocol is
started on the opposite NE, Output Clock ID is set to Enabled. Otherwise, this parameter is set to
Disabled.
Step 4 Click Apply.
----End
A.12.1.9 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.10 Configuring Clock Sources for External Clock Output

By default, OptiX RTN 900 allows output of the system clock source through the external
clock port. If the external clock port needs to transmit other clock sources, such as a clock
from a radio link or a synchronous Ethernet clock, you need to configure the priority table for
the PLL clock source of the external port.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
Clock > Physical Clock > Clock Source Priority from the Function Tree.
Step 2 Click the Priority for PLL Clock Sources of 1st External Output tab.

The Add Clock Source dialog box is displayed.
Step 4 Configure the clock sources for external clock output based on network planning information.

NOTE
To select more than one clock source at a time, press and hold the Ctrl key when selecting the clock
sources.
NOTE
l When the PLL clock source of the external clock port extracts the system clock (namely, the local clock
of the NE), Clock Source takes its default value Internal Clock Source. In this case, no manual
configuration is required.
l When the PLL clock source of the external clock port needs to extract the clock from an SDH line board,
clock from a radio link, clock from a PDH tributary board, or synchronous Ethernet clock, set Clock
Source to the corresponding clock source according to the network planning information.
Step 5 Click OK.
Step 6 Select Internal Clock Source and click Delete.
----End
A.12.1.11 Changing the Conditions for Clock Source Switching

You can change the default conditions for clock source switching of the NE for special
purposes.
Prerequisites

U2000
NOTE
Procedure
Physical Clock > Clock Source Switching.
Step 2 Click the Clock Source Switching Condition tab.
Step 3 Change the conditions for clock source switching.
Step 4 Click Apply.
----End

A.12.1.12 Modifying the Recovery Parameter of the Clock Source

In the case of the special requirements, you can modify the recovery parameter of the clock
source.
Prerequisites

U2000
NOTE
Procedure
Physical Clock > Clock Source Switching.
Step 2 Click the Clock Source Reversion tab.
Step 3 Set the recovery parameter of the clock source.
Step 4 Click Apply.
----End
A.12.1.13 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.
Step 3 Query the clock synchronization status.

NOTE
This operation is for querying the synchronization state of physical clocks and cannot be used to query the
synchronization status of CES ACR clocks and 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.
Prerequisites
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, Perform steps 2 to 6.
A port on a CQ1 board or of an OptiX RTN 905, Perform steps 7 to 9.
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.
3. 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.

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

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
Clock > ACR Clock from the Function Tree.
Step 2 Click Query, and close the dialog box displayed.
Step 3 Query the CES ACR clock status.
----End
A.12.3 Managing the PTP Clock

On a transmission network, the IEEE PTP protocol can be used to synchronize network-wide
high-precision time or transparently transmit high-precision time signals. As a result, the
IEEE PTP protocol can substitute timing equipment such as GPS to provide high-precision
timing signals for 3G base stations.

A.12.3.1 Configuring the PTP Profile

Configure an IEEE 1588v2 or ITU-T G.8257.1 profile for an NE as required. All NEs in a
clock domain must use the same PTP profile.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE and choose ConfigurationClockPTP Clock PTP
Profile from the Function Tree.
Step 2 Select IEEE-1555v2 or G.8275.1 from PTP Profile.
Step 3 Click Apply.
----End
A.12.3.2 Changing the Mode for Selecting the Frequency Source

The default mode for selecting a frequency on an NE is the physical synchronization mode.
When an NE adopts the IEEE 1588v2 clock for frequency synchronization, you need to
change the physical synchronization mode to the PTP synchronization mode.
Prerequisites

U2000
NOTE
Procedure
Clock > Frequency Selection Mode from the Function Tree.

Step 2 In Select Frequency Source Mode, select different clock synchronization modes.
Step 3 Click Apply.
----End
A.12.3.3 Querying or Modifying the PTP System Time

If the PTP protocol is adopted for time synchronization, the PTP system time displayed on
different NEs at a moment is the same. If the PTP system time of the primary time source in
the clock subnet is changed, the PTP system time of other NEs on the clock subnet changes
accordingly.
Prerequisites

U2000
NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute.
Step 2 Click Query to query the PTP system time.
Step 3 In PTP System Time, click , and then set the system time.
NOTE
Set this parameter for the grandmaster only when it uses local real-time clock as a timescale.

Step 4 Click Apply.
----End
A.12.3.4 Setting the PTP NE Attributes

PTP NE attributes involve parameters such as the working mode, packet multicast mode, and
time adjusting function.
Prerequisites

U2000
NOTE
Procedure
Step 2 Set parameters for a PTP clock according to the planning information.
NOTE
If a PTP clock or a clock source priority table is configured, the working mode cannot be changed.
Figure A-3 PTP NE attributes if IEEE 1588v2 is used
Figure A-4 PTP NE attributes if ITU-T G.8275.1 is used
Step 3 Click Apply.
----End
A.12.3.5 Creating PTP Clock Ports

PTP clock ports refer to the ports that are located on NEs and transmit or receive PTP packets.
Prerequisites


U2000
NOTE
Procedure
Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree.
Step 2 Click the Port Status tab.
Step 3 Click New.

The Create PTP Clock Port dialog box is displayed.
Step 4 Select the required board, select the corresponding port in Available Port, and then click
.
Step 5 Click OK.
----End
A.12.3.6 Setting PTP Clock Port Attributes

PTP clock port attributes involve parameters such as the VLAN ID and encapsulation format
carried in the PTP packets transmitted or received at a port, reference clock source, and IEEE
1588 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.
Figure A-5 PTP clock port attributes if IEEE 1588v2 is used
Figure A-6 PTP clock port attributes if ITU-T G.8275.1 is used
Step 4 Click Apply.
----End
A.12.3.7 Setting Parameters for PTP Clock Packets

The parameters for IEEE 1588v2 clock packets include P/E mode, packet transmission period,
and announce packet timeout coefficient.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the Port message tab.

Step 3 Set parameters for PTP clock packets according to the planning information.
Step 4 Click Apply.
----End
A.12.3.8 Configuring the Cable Transmission Offset Between NEs

This section describes how to compensate the delay that results from asynchronous PTP clock
signal transmission between NEs.
Prerequisites

U2000
NOTE
Procedure
Step 2 Click the Cable Transmitting Warp tab.
Step 3 Set parameters for configuring the cable transmission offset of PTP clock signals according to
Step 4 Click Apply.
----End
A.12.3.9 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 If IEEE 1588v2 is used, NE Clock Type is OC, BC, or TC+BC.
l If ITU-T G.8275.1 is used, NE Clock Type is T-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.10 Modifying the BMC Algorithm Parameters for NE Clocks

When the internal clock of an NE is used as a BMC clock source, you can modify the BMC
algorithm parameters for the internal clock of the NE.
Prerequisites
l If IEEE 1588v2 is used, NE Clock Type 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.
Figure A-7 BMC algorithm parameters if IEEE 1588v2 is used

Figure A-8 BMC algorithm parameters if ITU-T G.8275.1 is used
Step 4 Click Apply.
----End
A.12.3.11 Setting Basic Attributes of External Time Ports

The basic attributes of external time ports include parameters such as the transmission
direction, port type, and port level.
Prerequisites

U2000
NOTE
Procedure
Clock > PTP Clock > External Time Interface from the Function Tree.
Step 2 Click the Basic Attribute tab.
Step 3 Set parameters for the basic attributes of external time ports according to the planning
information.
Step 4 Click Apply.
----End
A.12.3.12 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.

NOTE
l If IEEE 1588v2 is used, NE Clock Type is BC, OC, or TC+BC.


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.
Figure A-9 BMC algorithm parameters if IEEE 1588v2 is used
Figure A-10 BMC algorithm parameters if ITU-T G.8275.1 is used
Step 4 Click Apply.
----End
A.12.3.13 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.
NOTE
l If IEEE 1588v2 is used, NE Clock Type is BC, OC, or TC+BC.



U2000
NOTE
Procedure
Step 2 Click the Cable Transmitting Distance tab.
Step 3 Set parameters for the cable transmission distance according to the planning information.
Step 4 Click Apply.
----End
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.
Table A-9 Packet plane

Performa Browsed Navigation Path
nce Object
Object
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended NOTE
performan a: Packet Ethernet ports include FE/GE ports, Integrated IP microwave
ce ports, PORT8 on the EMS6 board, and PORT10 on the EFP8 board.
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
1+1 group 1+1 group 1. In the NE Explorer, select the required NE from the Object
performan Tree and choose Configuration > IF 1+1 Protection.
ce 2. Select the desired 1+1 protection group, right-click, and
choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.


nce Object
Object
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
shortcut menu.
CES-PW CES 1. In the NE Explorer, select the NE from the Object Tree and
performan service choose Configuration > CES Service Management from
ce the Function Tree.
CES 2. Select one or more CES services, right-click the service(s),
performan and choose Browse Performance from the shortcut menu.
ce
ATM/IMA Smart E1 Select the corresponding board from the Object Tree in the NE
(access port Explorer. Choose Performance > RMON Performance from
side) the Function Tree.
performan
ce
ATM-PW ATM 1. In the NE Explorer, select the NE from the Object Tree and
performan PWE3 choose Configuration > ATM Service Management from
ce service the Function Tree.
ATM 2. Select one or more ATM PWE3 services, right-click the
PWE3 service(s), and choose Browse Performance from the
performan shortcut menu.
ce
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
NOTE
Complete the operation A.9.8.8 Creating Traffic before monitoring the
port traffic classification performance.


nce Object
Object
Port Egress For FE/GE ports:

priority queues 1. Select the NE from the Object Tree in the NE Explorer.
performan Choose Configuration > Interface Management >
ce Ethernet Interface from the Function Tree.
3. Select one or multiple ports, right-click and choose Browse
4. Select the desired egress queue in the Object drop-down list.
For Integrated IP microwave ports:
1. Select the NE from the Object Tree in the NE Explorer.
Choose Configuration > Interface Management >
Microwave Interface from the Function Tree.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
ETH OAM E-LAN 1. In the NE Explorer, select the required NE from the Object
E-LAN service Tree and choose Configuration > Ethernet OAM
performan 2. Select the desired test ID, right-click, and choose Browse
cec Performance from the shortcut menu.
NOTE
c: Only an NE housing CSHU or CSHUA boards supports ETH OAM
E-LAN service performance.


nce Object
Object
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse
PW 1. In the NE Explorer, select the required NE from the Object

Tree and choose Configuration > MPLS Management >
PW Management.
Table A-10 EoS/EoPDH plane
Performa Browse Navigation Path

nce Object
Object
Basic Ethernet In the NE Explorer, select the EFP8 or EMS6 board from the
performan portb Object Tree and choose Performance > RMON Performance
NOTE
Extended b:
performan EoPDH Ethernet ports include PORT1 to PORT9 on the EFP8 board.
ce
EoS Ethernet ports include PORT1 to PORT7 on the EMS6 board.
VCG-other VCTRUN
performan K port
ce
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

U2000
NOTE
Procedure

nce Object
Object
Extended NOTE
ce Aggregation.


nce Object
Object
shortcut menu.
shortcut menu.
ce
performan
ce
ce


nce Object
Object
ce classificati
NOTE



nce Object
Object
NOTE

PW Management.

nce Object
Object
NOTE
Extended b:
ce
VCG-other VCTRUN
performan K port
ce
NOTE

Step 2 Click the RMON Setting tab.
Step 3 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.
Prerequisites

U2000
NOTE
Context
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

nce Object
Object
Extended NOTE
ce Aggregation.


nce Object
Object
shortcut menu.
shortcut menu.
ce
performan
ce
ce
ce classificati
NOTE


nce Object
Object

NOTE


nce Object
Object

PW Management.

nce Object
Object
NOTE
Extended b:
ce
VCG-other VCTRUN
performan K port
ce
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 The RTN 980 housing CSHNU boards,The RTN 980L housing CSHLU boards and
OptiX RTN 905 do not support this operation.

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.
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 in the STM-N frame. Such a service is also called
broadcast data port service.
Prerequisites
l The AUX board exists on the NE Panel.

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.
l The DCC channels corresponding to external clocks must be disabled.

U2000
NOTE
Procedure
Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.
Step 4 Click Apply.
----End
A.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 The AUX,CSHL,CSHNA board exists on the NE Panel.

U2000
NOTE

Context
The external alarms of OptiX RTN 900 are also considered as housekeeping alarms. The
external alarm port of the NE is a relay port. This port can be either in the "on" state or in the
"off" state.
Procedure
Step 1 Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
Step 2 Configure the input alarm.

1. Select Input Relay from the drop-down list.
2. Configure the parameters of the input alarm.
3. Click Apply, and then close the dialog box that is displayed.
Step 3 Configure the output alarm.

1. Select Output Relay from the drop-down list.
2. Configure the parameters of the output alarm.
3. Click Apply, and then close the dialog box that is displayed.
----End
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.
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.
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.

1. Set Work mode.
2. Set other parameters according to the value of Work mode.
– 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).
3. Click Apply.
NOTE
It is recommended that the parameters take their default values, unless otherwise specified.
Step 5 Optional: Set the temperature alarm thresholds.

1. Set High temperature threshold(°C).
2. Set Low temperature threshold(°C).
3. Click Apply.
NOTE
----End
A.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.
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

U2000
NOTE

Context
NOTE
Procedure
Step 1 In the NE Explorer, select PMU from the Object Tree and choose Configuration >
Function Tree.
Step 2 Query the ambient humidity.

1. Select Outdoor cabinet interface from the drop-down list.
2. Click Query to obtain Relevant humidity(RH%).
Step 3 Query the ambient temperature.

1. Select Outdoor cabinet Ambient temperature from the drop-down list.
2. Click Query to obtain Ambient Temperature on Sensor1(°C) or Ambient
Temperature on Sensor2(°C).
----End
A.14.6.6 Setting Environment Alarm Parameters for Outdoor Cabinets

You can set environment alarm parameters for outdoor cabinets, including temperature and
humidity as well as smoke, lightning, water intrusion, and door access control.When the
temperature or humidity exceeds the preset threshold, the PMU/TCU reports the
ODC_TEMP_ABN or ODC_HUMI_ABN alarm.
Prerequisites
l The TCU has been added to the NE Panel.

U2000
NOTE
Context
NOTE
Procedure
Step 1 In the NE Explorer, select TCU from the Object Tree and choose Configuration >
Function Tree.

Step 2 Select Operation Object, and set Upper Threshold and Lower Threshold for temperature
and humidity alarms. Set Speed of internal circulation fan(RPM), Speed of external
circulation fan(RPM), High temperature threshold(°C), Low temperature threshold(°C),
Smoke Alarm Level, Water Alarm Level, Door Status Alarm Level, Lighting Alarm
Level, Smoke State, Water State, Door State, Lightning State.
Step 3 Click Apply.

NOTE
----End
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
950. 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.
l Configuration data on the U2000 is the same as that on NEs.
Context
NOTE
This section uses Create 1+1 Linear MSP as an example. You can create other types of linear MSP
protection subnets in a similar way.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 1+1 Linear MSP from the main menu.
Step 2 Set parameters for the protection subnet to be created.
Step 3 Click Next.

Working Link and Protection Link are displayed.
----End
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
Context
NOTE
This section uses Create 2f_MS_SPRing as an example. You can create other types of ring MSP protection
subnets in a similar way.
Procedure
Step 1 Choose Service > SDH Protection Subnet > Create 2f_MS_SPRing from the main menu.
Step 2 Set parameters for the protection subnet to be created.
Step 3 Click Next.
----End
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.
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.
Prerequisites
l Port attributes have been correctly configured for boards on related NEs.
Context
l If a server trail to be created passes through intermediate NEs, create the server trail in
end-to-end mode. In this case, higher order VC-4s pass through intermediate NEs.
l If a server trail is created by creating trails between adjacent NEs, creating server trails
does not affect data on the NE side or the NE layer on the U2000 side. It only makes a
mark at the network layer on the U2000 side, which indicates that the VC-4 is used and
cannot be used by other VC-4 trails.
Procedure
Step 1 Choose Service > SDH Trail > Create SDH Trail from the main menu.
Step 2 Set Level to VC4 Server Trail.

Step 3 Double-click the desired NE in the physical topology to configure the source and sink of the
server trail.
Step 4 Optional: Select and right-click the desired node and set it to be an explicit node.
Step 5 In the Calculate Route area, select Auto-calculation.
Step 6 Optional: Select Copy after Creation.
Step 7 Click Apply.

The Operation Result dialog box is displayed, indicating that the operation is successful.
Step 8 Optional: Click Browse Trail. In the Manage SDH Trail window, you can view the created
server trail.
----End
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.
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.
l VC-4 server trails have been created.
Procedure
Step 2 Set Level.
NOTE
Set Level to VC12 for Native E1 services.
Step 3 Configure the source and sink of a point-to-point service trail.

1. Double-click the source NE in the physical topology.
The Select Board Port-Source dialog box is displayed.
2. Set the sink board and port according to the network plan.
3. Set the sink NE by referring to Step 3.1 and Step 3.2.
Step 5 Configure SNCP.

1. Click the SNCP Setting tab.

2. Right-click in the blank area and choose Add from the shortcut menu.
The Add the dual-fed and selective-receiving node dialog box is displayed.
3. Set Dual-Fed Point and Selective-Receiving Point.
4. Click OK.
Step 8 Click Apply.

point-to-point SNCP service trail.
----End
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.
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.
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.
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.
l Data is synchronized between the NE and the NMS.
l Fiber connections between ports on the service path are correct.
Context
NOTE
This task searches for Native Ethernet services that have been configured on a per-NE basis but have not
formed a topology on the network layer of the NMS. If Native Ethernet services are configured in end-
to-end mode or have formed a topology on the network layer of the NMS, skip this task and follow
instructions in 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 Select All and go to Step 4.
the U2000
The search scope is specified Select Select NE and go to the next step.
Step 3 Add NEs to the search scope.

1. Click Add.
The Select NE dialog box is displayed.
2. Select the NE in the left area and click .

3. Optional: Repeat Step 3.2.
4. Click OK.
Step 4 Select the desired service types.
Step 5 Click Start.

The found Native Ethernet services are listed in Discovery Result.
Step 6 Optional: Select a service and click Jump Service to start service query and maintenance
operations.
----End

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.
l Fibers or cables for Ethernet links between NEs are on the main topology.
Procedure
Step 1 Choose Service > Native Ethernet Service > Create E-Line Service from the Main Menu.
Step 2 Set the basic attributes for the E-Line service.
The rules for setting these parameters are as follows:

l Service Name: This parameter is set based on the service plan or user preference.
l BPDU Private Service: This parameter takes a fixed value of No.
l Customer: This parameter is set as required by a user.
l Remarks: This parameter is set as required by a user.
Step 3 Configure the source and sink of the E-Line service.

1. Double-click the source NE in the Physical Topology tab page.
The Select Source dialog box is displayed.
2. Select the source board and source port.
3. Set C-VLAN and S-VLAN for the service source according to the planning rules.
Table A-15 E-Line service types

Service Type C-VLAN S-VLAN
Point-to-point transparently transmitted - -

E-Line service
VLAN-based E-Line service Set based on the -

service plan
QinQ-based E-Line PORT-based - -

service service flow whose
source port is a
UNI port

Service Type C-VLAN S-VLAN
PORT+C-VLAN- Set based on the -

based service flow service plan
whose source port
is a UNI port
Source port being - Set based on the

an NNI port service plan
4. Click OK.
5. Refer to Step 3 and configure the service sink of the E-Line service.
Step 4 Optional: Select 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-16 Source NE

Service Type Out C-VLAN Out S-VLAN
Point-to-point transparently transmitted E- Null Null

Line service

Service Type Out C-VLAN Out S-VLAN
VLAN-based E-Line VLAN switching is default value Null

service not performed on
Out Interface.
VLAN switching is Set based on the Null

performed on Out service plan
Interface.
QinQ-based E-Line Out Interface being Null Set based on the

service an NNI port service plan
Table A-17 Sink NE

Service Type In C-VLAN In S-VLAN

Line service

service not performed on In
Interface.

performed on In service plan
Interface.
QinQ-based E-Line In Interface being Null Set based on the

service an NNI port service plan
Table A-18 Intermediate NEs

Service Type Out C-VLAN and Out S-VLAN and
In C-VLAN In S-VLAN

Line service

service not performed on
Out Interface or In
Interface.

performed on Out service plan
Interface and In
Interface.
QinQ-based E-Line Out Interface and Null Set based on the

service In Interface being service plan
NNI ports

Step 8 Click OK.
----End
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.
l Ring Type: Set the ring type to major ring or sub-ring according to the service plan.
l 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.
l 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. Click OK.

Step 4 Set NE port information for the ERP ring.

l The following is an example of NE port information for a major ring.
l The following is an example of NE port information for a sub-ring.

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 Port attributes are configured for each board on an NE.

l Fibers or cables for Ethernet links between NEs are connected on the main topology.
Procedure
Step 1 Choose ServiceNative Ethernet ServiceCreate E-LAN Service from the Main Menu.
Step 2 Set the general attributes for E-LAN services.

l Service Type: This parameter takes a default value of E-LAN.
l Service Name: This parameter is set based on the service plan or user preference.
l Customer: This parameter is set as required by a user.
l Remarks: This parameter is set as required by a user.
Step 3 Configure bridge-mounted ports for E-LAN services.

1. Double-click the NE in the Physical Topology tab page.
The Select Node and Port dialog box is displayed.
2. See the following table to set the tag types.
Service Type Tag Type
IEEE 802.1d bridge-based E-LAN Tag-transparent

service
IEEE 802.1q bridge-based E-LAN C-Aware

service
IEEE 802.1ad bridge-based E-LAN S-Aware

service
3. Under Available Interface, select the port to be mounted to the bridge and click
.

NOTE
If Port Mode of a port is Layer 3, the port is not displayed under Available Interface. To change
its port mode, right-click the NE, choose NE Explorer from the shortcut menu. Then, follow
instructions in A.8.8.1 Setting the Basic Attributes of Ethernet Ports to change its port mode to
Layer 2.
4. See the following table to set C-VLAN, S-VLAN, and Encapsulation Type.
Table A-19 E-LAN service types
Service Type C-VLAN S-VLAN Encapsulatio

n Type
IEEE 802.1d bridge-based E-LAN - - Null

service
IEEE 802.1q bridge-based E-LAN Set based on - 802.1q

service the service
plan
IEEE PORT-based - Set based on Null

802.1ad service flow whose the service
bridge- bridge-mounted plan
based E- port is a UNI port
LAN
service PORT+C-VLAN- Set based on Set based on 802.1q
based service flow the service the service
whose bridge- plan plan
mounted port is a
UNI port
Bridge-mounted - Set based on QinQ

port being an NNI the service
port plan
5. Click OK.
Step 4 Repeat Step 3 to configure the bridge-mounted ports on other NEs in an E-LAN service
network.
Step 5 Set the general attributes for the bridge-mounted ports.
1. Click .
2. Click the Interface Information tab.
3. Set the general attributes for the bridge-mounted ports.
– Enable Port:
n If a port is in use, set this parameter to Enabled.
n 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.
n 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.
– 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.
n 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: For a microwave link for which 1+1 protection, N+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.
6. Click Apply.

Step 7 Optional: Configure Ethernet Ring Protection Switching (ERPS).
1. Click .
2. Click the ERPS tab. Then, click Add.
The Add ERPS dialog box is displayed.
3. Set the parameters for the ERPS protection instance.
4. Click OK.
5. Set the parameters for the ERPS protocol.
NOTE
– 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.
l The data on the NE and the NMS is synchronized.
Procedure
Step 1 Choose Service > Native Ethernet Service > Manage Native Ethernet Service from the
main menu.
Step 2 In the Set Filter Criteria dialog box, set filter conditions and click Filter.
The Native Ethernet services that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet service, and choose Ethernet OAM > Ethernet
OAM Test from the shortcut menu.
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.
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
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

U2000
U2000.
NOTE
For the restrictions on a service performance test, see ETH OAM in Feature Description.
Procedure
Main Menu.

The Native Ethernet Service that meet the criteria are listed in the query result.
Step 3 Right-click the desired Native Ethernet Service and choose Native Ethernet OAM > ETH
OAM Test from the shortcut menu.

Step 4 Set Measurement to LM or DM according to the network plan.
Step 5 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
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-to-
end 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 Go to Step 4.

network
Bridge-mounted ports are to be added to the Go to Step 5.

nodes in the E-LAN service network
A split horizon group is to be configured Go to Step 6.
Step 4 Add a node to the E-LAN service network.

1. Click the NE tab.
2. Click Add.
The Select Node and Port dialog box is displayed.
3. Select the NE in the left area and click .

4. See the following table to set the tag types.
Service Type Tag Type
IEEE 802.1d bridge-based E-LAN Tag-transparent

service
IEEE 802.1q bridge-based E-LAN C-Aware

service
IEEE 802.1ad bridge-based E-LAN S-Aware

service
.

n Type

service


n Type

service the service
plan

LAN
mounted port is a
UNI port

port plan
7. Click OK.
8. Click the Interface tab. Set the general attributes for the bridge-mounted ports.
Step 5 Add bridge-mounted ports to the nodes in the E-LAN service network.
1. Click the Interface tab.
2. Click Add.
The Select Port dialog box is displayed.
3. Select the desired nodes for adding bridge-mounted ports.
.


n Type

service

service the service
plan

LAN
mounted port is a
UNI port

port plan
6. Click OK.
7. Set the general attributes for the bridge-mounted ports.
Step 6 Configure a split horizon group.

NOTE
1. Click the Split Horizon tab. Then, click Add.
The Add Split Horizon Group dialog box is displayed.
2. Select the desired ports based on the plan, and click .

3. Click OK.
----End
A.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.
l The configuration data on the U2000 side is the same as the configuration data on the NE
side.
Procedure
Step 1 Choose Service > Search for 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.
Step 5 Click the Add Service, Modify Service, and Discrete Service tabs to view the found
services.
l Add Service refers to a service that is not in the configuration data at the network layer
of the U2000.
l Modify Service refers to a service that is in the configuration data at the network layer
of the U2000 but some service parameters differ between the network layer and the NE
layer of the U2000. For MPLS tunnels, the U2000 does not support the search of
modified services.
l Discrete Service refers to a service that is only in the configuration data at the NE layer
of the U2000.
Step 6 Optional: Select a service and click Jump Service to start related service query and
maintenance operations.
----End
Follow-up Procedure
l Follow the instructions in A.15.5.6 Managing MPLS Tunnels in an End-to-End Mode
to query and maintain the found MPLS tunnels.
l Follow the instructions in A.15.6.11 Managing and Maintaining PWE3 Services to
query and maintain the found PWE3 services.
l Follow the instructions in A.15.5.7 Managing Discrete MPLS Tunnels to query and
maintain the found discrete MPLS tunnels.
l 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.

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.
l If the IP addresses to be configured are discontinuous, many IP address resources can be
configured.
l The IP address resources should not contain IP addresses in the 192.168.0.0/16 network
segment, 192.169.0.0/16 network segment, or the network segments to which LSR IDs
and NE IP addresses belong.
Procedure
Step 1 Choose Configuration > IP Address Management from the Main Menu.
Step 2 Click New.
Step 3 Configure port IP address resources.
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.
Step 3 Click New.
Step 4 Set Source NE, Source Port, Sink NE, and Sink Port for the L2 link.
----End
Follow-up Procedure
If alarms are reported on the created L2 link, verify the following items.
l Fibers/cables are correctly connected.

l The port IP addresses at both ends of the L2 link are in the same network segment.
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.
l Parameters related to MPLS ports have been correctly configured.
l Links between MPLS nodes are proper.
l Ingress nodes and egress nodes can be managed on the U2000.
Context
l If any ingress node or egress node cannot be managed on the U2000, create MPLS
tunnels when creating PWE3 services.
l It is recommended that you use the automatic route computation function to create
MPLS tunnels. Before you use the automatic route computation function, ensure that L2
links have been created between MPLS nodes.

Precautions
In each step, two snapshots are provided. The first one shows how to create bidirectional
tunnels, whereas the second one shows how to create unidirectional tunnels.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu.
Step 2 Set attributes for MPLS tunnels.

l Tunnel Name: Unless otherwise specified, this parameter takes its default value, which
is automatically generated by the U2000 according to the naming rules.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: Set this parameter to Bidirectional with priority. On MPLS nodes
that only support unidirectional tunnels, you need to set this parameter to
Unidirectional.
l Create Reverse Tunnel: During the creation of unidirectional tunnels, if routes for
forward tunnels and backward tunnels are the same, you can configure forward and
backward tunnels synchronously.
l Protection Type: Protection-Free
Step 3 Configure on the nodes at both ends of an MPLS tunnel.

1. Click Add > NE.
2. In the Select NE dialog box that is displayed, select one or more NEs, and click .
3. Click OK.
4. Double-click NE Role to set an NE node type.
Step 4 Optional: Configure a route for the tunnel using the automatic route computation function.
1. Select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s) to No Limit.
To use the CES CAC verification function or to restrict the PW bandwidth, you need to
set this parameter according to the planned tunnel bandwidth.
3. Double-click the ingress NE, and then the egress NE in the Physical Topology tab page
on the right.
The U2000 will compute a tunnel between the ingress NE and the egress NE, and display
the tunnel in the Physical Topology tab page.
4. If the computed route is not the desired one, right-click the explicit or excluded NE in
the Physical Topology tab page, set restrictions from the shortcut menu, and click
Calculate route.
Step 5 Optional: Manually specify a route for a tunnel.

1. Do not select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s).
It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this
parameter according to the planned tunnel bandwidth.
3. In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology
tab page.

NOTE
The NEs marked by are ingress NEs, and the NEs marked by are egress NEs.
4. If the generated route is not the desired one, you can modify it in the NE lists on the left.
Step 6 Set information about the tunnels and the MPLS OAM.
1. Click Details.
2. Set information about the working tunnel in the Working Tunnel tab on the right.
– 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.

3. Optional: Click Configure MPLS-TP OAM to configure MPLS-TP OAM complying

with ITU-T Y.1731. Click Add in the dialog box that is displayed, set the required
parameters, and click OK.
The values for the related parameters are provided as follows:
– 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.
4. Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
– 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.

5. Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Reverse Working Tunnel tabs.
Step 7 Choose Deploy and then Enable.
l After Deploy is selected, the tunnel configuration data is saved on the U2000 side and
deployed to the NE side. Otherwise, the service configuration data is saved on the U2000
side but is not deployed to the NE side.
l The OptiX RTN 950 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.
l Parameters related to MPLS ports have been correctly configured.
l Links between MPLS nodes are proper.
l Ingress nodes and egress nodes can be managed on the U2000.
Context
l If any ingress node or egress node cannot be managed on the U2000, create MPLS
tunnels when creating PWE3 services.
l It is recommended that you use the automatic route computation function to create
MPLS tunnels. Before you use the automatic route computation function, ensure that L2
links have been created between MPLS nodes.
Precautions
In each step, two snapshots are provided. The first one shows how to create bidirectional
tunnels, whereas the second one shows how to create unidirectional tunnels.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu.
Step 2 Set attributes for MPLS tunnels.

l Tunnel Name: Unless otherwise specified, this parameter takes its default value, which
is automatically generated by the U2000 according to the naming rules.
l Protocol Type: MPLS
l Signaling Type: Static CR
l Service Direction: Set this parameter to Bidirectional with priority. On MPLS nodes
that only support unidirectional tunnels, you need to set this parameter to
Unidirectional.
l Create Reverse Tunnel: During the creation of unidirectional tunnels, if routes for
forward tunnels and backward tunnels are the same, you can configure forward and
backward tunnels synchronously.
l Protection Type: 1:1

l Switching Mode: Unless otherwise specified, it is recommended that you set this
parameter to Double-Ended.
Step 3 Configure on the nodes at both ends of an MPLS tunnel.

1. Click Add > NE.
2. In the Select NE dialog box that is displayed, select one or more NEs, and click .
3. Click OK.
4. Double-click NE Role to set an NE node type.
Step 4 Optional: Configure a route for the tunnel using the automatic route computation function.
1. Select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s) to No Limit.
To use the CES CAC verification function or to restrict the PW bandwidth, you need to
set this parameter according to the planned tunnel bandwidth.
3. Double-click the ingress NE, and then the egress NE in the Physical Topology tab page
on the right.
The U2000 will automatically computes a working tunnel and a protection tunnel
between the ingress NE and the egress NE, and display the tunnels in the Physical
Topology tab page.

4. If the computed working or protection route is not the desired one, you can right-click
the explicit or excluded NE in the Physical Topology tab page, set restrictions in the
dialog box displayed, and click Calculate route.
Step 5 Optional: Manually specify a route for a tunnel.
1. Do not select Auto-Calculate route.
2. Optional: Set Restriction Bandwidth(kbit/s).
It is recommended that this parameter takes its default value, No Limit. To use the CES
CAC verification function or to restrict the PW bandwidth, you need to set this
parameter according to the planned tunnel bandwidth.
3. In the Physical Topology tab page on the right, double-click the ingress NE, egress NE,
and the transit NEs between them one by one.
A tunnel route will be generated on the U2000 and displayed in the Physical Topology
tab page.

NOTE
The NEs marked by are ingress NEs, and the NEs marked by are egress NEs.
4. If the generated route is not the desired one, you can modify it in the NE lists on the left.
Step 6 Set information about the tunnels and the MPLS OAM used for MPLS APS protection.
1. Click Details.
2. Set information about the working tunnel in the Working Tunnel or the Forward
Working Tunnel tab on the right.
– 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.

3. Optional: Click Configure MPLS-TP OAM to configure MPLS-TP OAM complying

with ITU-T Y.1731. Click Add in the dialog box that is displayed, set the required
parameters, and click OK.
The values for the related parameters are provided as follows:
– 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.
4. Optional: Click Configure OAM to configure MPLS OAM complying with ITU-T Y.
1711. In the dialog box that is displayed, set OAM parameters and click OK.
– 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.

5. Repeat steps Step 6.2 and Step 6.4, to set information about tunnels and OAM on the
Protection Tunnel tab, or the Reverse Working Tunnel, Forward Protection Tunnel,
and Reverse Protection Tunnel tabs.
Step 7 Click Configure Protection Group. In the dialog box displayed, set attributes about MPLS
APS protection groups and click OK.
l Revertive Mode: Unless otherwise specified, it is recommended that you set this
parameter to Revertive.
l Other parameters: Unless otherwise specified, it is recommended that the parameters
take their default value.

Step 8 Choose Deploy and then Enable.

deployed to the NE side. Otherwise, the service configuration data is saved on the U2000
side but is not deployed to the NE side.
l The OptiX RTN 950 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.
l 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.
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.
Step 5 Optional: Click the on the right and set parameters about the LSP ping/LSP
traceroute test in the dialog box that is displayed.
l Packet Size: Set this parameter according to requirements.
l Response Mode: Set this parameter to Application Control Channel if the tunnel is
bidirectional and its egress node supports reverse channel response. Set this parameter to
IPv4 UDP Response if the egress node does not support reverse channel response, but
support DCN channel response based on IP protocols. In other scenarios, set this
parameter to No Response.
l Other parameters: Other parameters take their default values.

Step 6 Click Run.

Step 7 After the verification, query the verification result of each MPLS tunnel.
----End
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

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.
l The configuration data on the U2000 side is the same as the configuration data on the NE
side.
Procedure
Step 1 Choose Service > Tunnel > Search for Protection Group from the Main Menu.
The Searching for Protection Groups dialog box is displayed.
Step 2 Set the search domain.

1. Click Add.
The Equipment Selection dialog box is displayed.
2. Set the NEs to search for and click OK.
The NEs are displayed in the NE list.
Step 3 Click OK.
----End
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

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

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.

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

----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 950 does not support
default parameter values in the service template, the U2000 displays parameter values
defaulted to the OptiX RTN 950.
l To configure a PWE3 service, you can use a default service template that is exported
from the U2000 or customize a service template by making related modifications to the
exported service template. This section describes how to customize a service template by
making related modifications to a default service template.
Procedure
Step 1 Choose Service > Service Template from the Main Menu.

The templates that meet the criteria are listed in the query result.
Step 3 Select the desired template and click Clone.
Step 4 In the Clone dialog box that is displayed, modify the template name and parameter values,
and select/deselect Set as Default Template.
NOTE
Parameters whose default values have been changed must be selected.
Step 5 Click OK.
----End
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.
Step 2 Set basic attributes of the CES services.
l Service template: If no service template has been specified, set this parameter to
DEFAULT_PWE3_CES_PTN/ATN.
l Service Type: CES
l Service ID and Service Name: Unless otherwise specified, these two parameters take
their default values. The U2000 automatically generates the parameter values according
to the service naming rules.
Step 3 Configure the NEs and service ports on the NEs that are involved in the PWE3 services.
2. Select the service port on the source NE, configure its SAI information, and click OK.
– 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.
l Forward Tunnel and Reverse Tunnel: If there are end-to-end working MPLS tunnels
between PEs, the U2000 automatically generates the parameter values. If the tunnels
generated by the U2000 are different from the planned tunnels, select correct tunnels if
the tunnels have already been created or create the desired tunnels.
l PW ID, Forward Label, and Reverse Label: Set these parameters according to the
service planning information. If the parameter values are not specified in the service
planning information and the entire network is managed by the U2000, the U2000
automatically allocates values for these parameters.
NOTE
If these parameters need to be set according to planning information when multiple pairs of source and
sink ports have configured, you need to set the parameters separately for each pair of source and sink
ports.
Step 5 Optional: Set the advanced attributes of the PW.

1. Click Detail.
2. In the Advanced PW Attribute tab page, set the advanced attributes of the PW.
Unless otherwise specified, it is recommended that all parameters in the tab take their
default values.
Step 6 Select Deploy and Enable at the lower left corner.

deployed to the NE side. If you do not select Deploy, the service configuration data is
saved on the U2000 side but is not deployed to the NE side.
l The OptiX RTN 950 only supports enabling PWE3 services.
Step 7 Click OK.
Step 8 In the Operation Result dialog box that is displayed, select Browse Trail.
The new CES service is displayed in the PWE3 service list.

NOTE
If multiple pairs of source and sink service ports have been configured, you need to create a CES service for
each pair of the source and sink ports.
----End
Follow-up Procedure
Follow the instructions in 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.

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 Perform Step 3 and Step 5.
profile
You need to create a global ATM CoS mapping profile Perform Step 6 and Step 8.
Step 3 Double-click the Default ATMCosMap profile.

The Modify ATM CoS Mapping Profile dialog box is displayed.
Step 4 Modify the global ATM CoS mapping profile according to network planning information.
NOTE
Step 5 Click OK.
Step 6 Right-click in ATM CoS Mapping Profile and choose Add Global Profile from the shortcut
menu.
The Create ATM CoS Mapping Profile dialog box is displayed.

Step 7 Create a global ATM CoS mapping profile according to network planning information.

NOTE
Step 8 Click OK.
----End
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.
l 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.
2. Select the service port on the NE.
3. Click OK.
4. Repeat Step 3.1 and Step 3.3 to configure the service port on the sink NE.
NOTE
the service in the physical topology and choose related options from the shortcut menu to create the service
source or sink (a virtual node).
Step 4 Optional: Set the basic attributes of the PW.

Set Forward Tunnel, Reverse Tunnel, PW ID, Forward Label, and Reverse Label.
Step 5 Optional: Configure the QoS information of the PW.
1. Click Detail.
2. In the PW QoS tab page, configure the QoS information of the PW.
default values.
Step 6 Optional: Set the advanced attributes of the PW.

1. Click Detail.
2. In the Advanced PW Attribute tab page, set the advanced attributes of the PW.
default values.

Step 7 Configure ATM connections.

1. Click ATM Link.
The Configure Link dialog box is displayed.
2. Click Add Link.
3. Set the ATM connection attributes according to network planning information.
NOTE
If multiple ATM connections have been planned, configure all the planned ATM connections.
4. Click OK.
Step 8 Select Deploy and Enable at the lower left corner.
deployed to the NE side. If you do not select Deploy, the service configuration data is
saved on the U2000 side but is not deployed to the NE side.
l For the OptiX RTN 950, 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
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.
l Service Type: ETH

Step 3 Configure the NEs and service ports on the NEs that are involved in the PW-carried E-Line
service.
2. Select the service port on the source NE, configure its VLAN ID, and click OK.
– 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.
3. Repeat Step 3.1 and Step 3.2 to configure the service port on the sink NE.
The information about the source and sink NEs is displayed in Node List.

NOTE
the service in the physical topology and choose corresponding options from the shortcut menu to create the
service source or sink (a virtual node).
Step 4 Set the basic attributes of PWs.

l Forward Tunnel and Reverse Tunnel: If there are end-to-end working MPLS tunnels
between PEs, the U2000 automatically generates the parameter values. If the tunnels
generated by the U2000 are different from the planned tunnels, select correct tunnels if
the tunnels have already been created or create the desired tunnels.
l PW ID, Forward Label, and Reverse Label: Set these parameters according to the
service planning information. If the parameter values are not specified in the service
planning information and the entire network is managed by the U2000, the U2000
automatically allocates values for these parameters.
Step 5 Optional: Set the advanced attributes of PWs.

1. Click Detail.

2. In the PW QoS tab, configure QoS of the PWs.
default values.
3. In the Advanced PW Attribute tab, set advanced attributes of the PWs.

– 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 PW-
Based 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.
l The Tunnels have been configured correctly.

Context
After planning and configuring MPLS tunnels, aggregate Ethernet services from BTSs to the
RNC by means of PWs. The service requirements are as follows:
l Ethernet services (VLAN ID: 100) at BTS11 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1501), which has a protection tunnel, is available
between NE11 and NE31.
l Ethernet services (VLAN ID: 100) at BTS21 need to be transmitted to the RNC. A
bidirectional working tunnel (ID: 1701), which has a protection tunnel, is available
between NE21 and NE31.
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 specified at the BTSs.
l GE ports on NE31, which are connected to the RNC, need to be protected in link
aggregation group (LAG) mode.
Figure A-11 Networking diagram (hybrid configuration of E-Line and E-LAN services
carried by PWs)
Working tunnel
(ID=1501)
NNI UNI
BTS11
NE32
VLAN 100
GE
NE31
NE11 RTN 950
RTN 980 NE21
R4 E-Line RTN 980 VPLS RNC
E-Line
Working tunnel
(ID=1701)
R4
BTS21
VLAN 100
Procedure
Step 1 Configure hybrid E-Line services and E-LAN services carried by PWs in end-to-end mode.

Figure A-12 Configuring hybrid E-Line services and E-LAN services carried by PWs in end-
to-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-13 Configuring a split horizon group on the VPLS node
----End

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 Perform Step 5 and Step 9.
You perform a PW traceroute Perform Step 10 and Step 14.
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.

l Response Mode: Application Control Channel
l Unless otherwise specified, it is recommended that other parameters take their default
values.
Step 8 Click OK.
Step 9 Click Run.
Step 10 Select VCCV Traceroute from the Diagnosis Option list.
Step 11 Click on the right of VCCV Traceroute.

The VCCV Traceroute dialog box is displayed.
Step 12 Set the connectivity test parameters.
l Response Mode: Application Control Channel

l Unless otherwise specified, it is recommended that other parameters take their default
values.
Step 13 Click OK.
Step 14 Click Run.
----End
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.
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.
– 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.
n Before a loopback test between two section points, set the remote section point
to the loopback NE. After the loopback test, release the loopback on the
remote section point to restore the entire link.
3. Click Start.
In the dialog box that is displayed asking you to confirm the operation, click Yes.
----End
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.

Step 3 Right-click the PWE3 service to verify, and choose Ethernet OAM > LB Test... from the
shortcut menu.
Step 4 In the Eth Oam LB Test dialog box that is displayed, select the source NE for initiating an
LB test.
NOTE
l An LB test detects whether a service is bidirectionally available. For a bidirectional service, it is

recommended that you select either end of a PW as the source NE for initiating the LB test.
l If a PW carries Ethernet services from different VLANs, the U2000 automatically select the service
of a VLAN for the LB test.
Step 5 Optional: Right-click the service that is selected for an LB test, and choose Configure...
from the shortcut menu. In the Config Eth Oam LB Test Parameter dialog box that is

displayed, set Sent Packets, Sent Packets Length, and Sent Packets Priority. Then, click
OK.
Step 6 Right-click the service that is selected for an LB test, and choose Run from the shortcut
menu.
Step 7 Click the LB Statistic Information tab and determines whether the service is available based
on the displayed information.
If Test Result displays Test Succeeded, the service is available.
If Packet Loss Ratio(%) displays 100 and Test Result displays Test Failed, the service is
unavailable. If the service is unavailable, check whether the service configurations are
incorrect.

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

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

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.15.6.14 Starting a TST Test of MPLS-TP PW OAM

OptiX RTN 950 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
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.

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

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

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.

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

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

Procedure
Step 1 Search for services.
Step 2 Select a service to be diagnosed by specifying a service port.
Step 3 Diagnose the service and display the result.

----End
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

Step 2 Perform E-LAN service loopback detection.
NOTE
l If a service is looped back, can be seen from the icons.

l To remove a loopback, you must disable the E-LAN service. After the loopback is removed, you can
manually enable the E-LAN service.
----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
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.

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

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.
l Details about the clock link are displayed in the lower part of the window.
Step 3 Optional: Modify the information displayed in the clock view.

1. Choose View > Display Setting > Filter from the main menu and set the filter criteria to
filter information displayed in the clock view.

2. Choose View > Display Setting > Legend from the main menu to browse meanings of
the icons and colors in the clock view.
----End

Feature Configuration Guide B Parameters Description
B Parameters Description
This chapter describes the parameters used in this document.
B.1 Parameters for Network Management

This topic describes the parameters that are related to network management.
B.2 Radio Link Parameters
This topic describes the parameters that are related to radio links.
B.3 Multiplex Section Protection Parameters
This topic describes the parameters that are related to multiplex section protection (MSP).
B.4 TDM Service Parameters
This section describes the parameters related to TDM services.
B.5 Parameters for Board Interfaces
This topic describes the parameters that are related to board interfaces.
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the
packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet
port parameters, and QoS parameters.
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane
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.
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 l If the IP protocol is

IP Address Range of GNE used on the DCN, you
GNE can search for an NE
based on IP Address
of GNE or IP
Address Range of
GNE.
l To search for all the
NEs that
communicate with the
gateway NE, select IP
Address Range of
GNE.
l To select the gateway
NE only, select IP
Address of GNE.
NOTE
If Address Type is set to
IP Address of GNE or IP
Address Range of GNE,
and if the U2000 (server)
and the gateway NE are
located in different
network segments, ensure
that the U2000 and
relevant routers are
configured with the IP
routes for the network
segment in which the
U2000 and gateway NE are
located.

Search Address - - l If Address Type is

set to IP Address of
GNE, enter the IP
address of the
gateway NE, such as
129.9.x.x.
l If Address Type is
set to IP Address
Range of GNE, enter
the number of the IP
network segment in
which the gateway
NE is located, such as
129.9.255.255.
l If Address Type is
set to NSAP Address,
enter the NSAP
address of the
gateway NE.
User Name - - This parameter specifies

the user name of the
gateway NE.
Password - - This parameter specifies

the password of the
gateway NE.

Parameter for Searching for NEs

Create NE after search Selected Deselected l To create NEs in

Deselected batches, it is
recommended that
you select Create NE
after search. The
NEs are automatically
created after they are
found.
l After Create NE
after search is
selected, enter NE
User and Password
that are used for
creating an NE.
NOTE
If only Create NE after
search is selected, Search
for NE is selected
automatically.
NE User - - l This parameter

specifies the user
name to be entered
when an NE is
created.
l This parameter is
valid only when
Create NE after
search is selected.
Password - - l This parameter

specifies the password
to be entered when an
NE is created.
l This parameter is
valid only when
Create NE after
search is selected.

Upload after create Selected Deselected l This parameter

Deselected specifies whether to
automatically upload
the NE data after the
NE is found and
created.
l If only Upload after
create is selected,
Search for NE and
Create NE after
search are selected
automatically.
Parameter for the Found NEs

NE ID - - This parameter indicates

the ID of the found NE,
which consists of
extended ID and NE ID.
GNE Address - - This parameter indicates

the address of the
gateway NE that is
connected to the found
NE.
GNE ID - - This parameter indicates

the ID of the gateway NE
that is connected to the
found NE.
Created As GNE Yes Yes l This parameter

No specifies the password
to be entered when an
NE is created.
l This parameter is
valid only when
Create NE after
search is selected.
Connection Mode Common Security SSL The communication

Security SSL between the client and
the server is encrypted if
this parameter is set to
Security SSL.

Port - 5432 This parameter specifies

the communication port.
NE Status Created - This parameter indicates

Uncreated whether the found NE is
created.
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

Domain - - This parameter specifies

the network segment to
be searched.
NE Name - - This parameter displays

the name of the found
NE.
NE ID - - This parameter displays

the ID of the found NE.
Gateway GNE - This parameter displays

Non-GNE whether the found NE is
a GNE or non-GNE.
Gateway IP Address - - This parameter displays

the gateway IP address of
the found NE.
Port No. 1400 1400 This parameter displays

the communication port
number of the found NE.
Gateway Type IP Gateway IP Gateway This parameter displays

the gateway type of the
found NE.

Parameters for Managing a Network Segment

Domain Type GNE IP Domain GNE IP Domain l To search for all the
GNE IP Address NEs that
communicate with the
GNE, select GNE IP
Domain.
l To search for the
GNE only, select
GNE IP Address.
Domain Address - - l When Domain Type

is GNE IP Domain,
enter the IP network
segment where the
GNE is located, for
example,
129.9.255.255.
l When Domain Type
is GNE IP Address,
enter the IP address of
the GNE, for
example, 129.9.x.x.
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

Type - - This parameter

indicates the
type of the NE
to be created.

ID 1 to 49151 - l The ID refers

to the basic
ID. If the
extended ID
is not used,
the basic ID
of an NE
must be
unique on the
networks that
are managed
by the same
NMS.
l This
parameter is
set according
to the
planning
information.
l The NE ID
consisting of
the basic ID
and extended
ID identifies
an NE on the
NMS.
Extended ID 1 to 254 9 If the number of

existing NEs
does not exceed
the range
represented by
the basic ID, do
not change
Extended ID.

Name - - l This
parameter
specifies the
name of the
NE.
l After you
have
specified the
name of the
NE, the
name is
displayed
under the
icon of the
NE.
Remarks - - This parameter

specifies the
remarks of the
NE.
Gateway Type Non-Gateway Non-Gateway l This

Gateway parameter is
set to
Gateway if
the new NE
is a gateway
NE.
l This
parameter is
set to Non-
Gateway if
the new NE
is a non-
gateway NE.
l This
parameter is
set according
to the DCN
planning if
the new NE
can function
as a gateway
NE or a non-
gateway NE.

Gateway - - This parameter

indicates the
gateway NE of
the new NE
when Gateway
Type is set to
Non-Gateway.
Protocol IP IP l This
parameter
needs to be
set when
Gateway
Type is set to
Gateway.
l In other
cases, this
parameter is
set to IP.
IP Address - - This parameter

indicates the IP
address of the
new NE. This
parameter needs
to be set when
Affiliated
Gateway
Protocol is set
to IP.
Connection Mode Common Security SSL The

Security SSL communication
between the
client and the
server is
encrypted if this
parameter is set
to 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.

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.

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 9 l Do not change the Extended ID when

the number of actual NEs does not
exceed the range permitted by the basic
NE ID.
l It is recommended that this parameter
takes the default value.
Gateway Type IP Gateway IP Gateway This parameter specifies the type of the
Serial Port gateway that is used for the
communication between the Web LCT and
SSL Gateway the NEs.
USB

IP Address - This parameter is This parameter specifies the IP address of

set to 129.9.0.x the gateway NE to which the NE to be
when the NE is created belongs. This parameter is
delivered from the displayed only when Gateway Type is set
factory. "x" to IP Gateway.
indicates the basic
NE ID that is set
when the NE is
delivered from the
factory.
Port l 1400 (when l 1400 (when This parameter specifies the port
Gateway Type Gateway Type corresponding to the gateway NE to which
is set to IP is set to IP the NE to be created belongs.
Gateway) Gateway)
l COM1-COM32 l COM1 (when
(when Gateway Gateway Type
Type is set to is set to Serial
Serial Port) Port)
Baud Rate 1200bps 115200bps This parameter specifies the

2400bps communication rate between the NE to be
created and the corresponding gateway
4800bps NE. This parameter is displayed only when
9600bps Gateway Type is set to Serial Port.
19200bps
38400bps
57600bps
115200bps
User Name - lct This parameter specifies the name of the

user. This parameter can take the default
value in the case of initial login.
Password - - The default password of user lct is

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

Parameters
User Name - lct This parameter specifies the name of the

user. This parameter can take the default
value in the case of initial login.
Password - - The default password of user lct is

Changeme_123.
Use same user Selected Deselected When this parameter is selected, enter
name and Deselected User Name and Password to log in to all
password to login the selected NEs.
Use the user name Selected Deselected When this parameter is selected, enter
and password that Deselected User Name and Password that were used
was used last time for the latest login to log in to the NE.
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.

Parameters for Changing NE IDs

New ID 1-49135 - l The new ID refers to

the basic ID. If the
extended ID is not
used, the basic ID of
an NE must be unique
on the networks that
are managed by the
same NMS.
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 9 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

NE Name - - This parameter indicates

the name of the NE.

the ID of the NE.

Synchronous Mode Standard NTP Null l If this parameter is set

NM to NM, the NE
synchronizes the time
Null of the NMS server.
l If this parameter is set
to Standard NTP, the
NE synchronizes the
Network Time
Protocol (NTP) server
through the standard
NTP.
Standard NTP Enabled Disabled This parameter is valid

Authentication Disabled only when Synchronous
Mode is set to Standard
NTP.
Parameters for the Standard NTP Server

Standard NTP Server NE ID NE ID l If the NE functions as

Identifier IP the gateway NE, this
parameter is set to IP.
l If the NE functions as
a non-gateway NE
and communicates
with the gateway NE
through the HWECC
protocol, this
parameter is set to NE
ID.
a non-gateway NE
and communicates
with the gateway NE
through the IP
protocol, this

Standard NTP Server - - l If the NE functions as

the gateway NE, this
parameter is set to the
IP address of the
external NTP server.
a non-gateway NE,
the ID or IP address
of the gateway NE.
Standard NTP Server 0 to 1024 0 l If the NTP server

Key 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).

Parameters for Setting Automatic Synchronization

Start Time - - l This parameter

specifies the start time
of the synchronization
period. After this
parameter is
specified, the NMS
and the NE
synchronize the time
once at the intervals
of Synchronization
Period(days).
l It is recommended
that you use the
default value.
DST Selected Deselected l This parameter

Deselected indicates whether
Synchronization
Starting Time is the
daylight saving time.
according to the
actual situation.
Synchronization 1 to 300 1 l This parameter

Period(days) 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.

Parameters for NE Time Synchronization

NE Name - - This parameter indicates

the name of the NE.

the ID of the NE.
Synchronous Mode Standard NTP Null l If this parameter is set

NM to NM, the NE
synchronizes the time
Null of the NMS server.
to Standard NTP, the
NE synchronizes the
Network Time
Protocol (NTP) server
through the standard
NTP.
Standard NTP Enabled Disabled This parameter is valid

Authentication Disabled only when Synchronous
Mode is set to Standard
NTP.
Parameters for the Standard NTP Server

Standard NTP Server NE ID NE ID l If the NE functions as

Flag IP the gateway NE, this
NE IP
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

Standard NTP Server - - l If the NE functions as

the gateway NE, this
IP address of the
external NTP server.
a non-gateway NE,
the ID or IP address
of the gateway NE.
Standard NTP Server 0 to 1024 0 l If the NTP server

Key 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 2 2 Set this parameter

3 according to the settings
for the standard NTP
protocol version used at
the peer end.
Used First Yes No This parameter specifies

No whether to select a server
preferentially when
multiple NTP servers are
available.

Parameters of the access control rights

ACL No. 1 to 250 1 This parameter specifies the number of the

ACL.
NE Flag NE ID NE ID l When ECC is used to communicate

NE IP with the standard NTP server, set the
parameter to NE ID.
l When the IP protocol is used to
communicate with the standard NTP
server, set the parameter to NE IP.
NE - - This parameter specifies the ID or IP

address of an NE.
Whether to Yes Yes This parameter specifies whether to

Receive Data No receive packets from an NE.
Packet
Right Level query query The equipment provides four levels of

synchronize access control. When an NTP access
request is received on the local equipment,
server the request is matched with the levels from
peer the minimum access limit to the maximum
access limit, and the first matched level
prevails. The matching order is as follows:
l Peer (minimum access limit): The time
request and the control query can be
carried out for the NTP service of the
local equipment. The local clock can
also be synchronized with the remote
server.
l Server: The time request and the
control query can be carried out for the
NTP service of the local equipment, but
the local clock is not synchronized to
the remote server.
l Synchronization: The time query is
allowed for only the NTP service of the
local equipment.
l Query (maximum access limit): The
control query can be carried out only
for the NTP service of the local
equipment.

Parameters of the NTP key management

Encryption Type MD5 MD5 This parameter specifies the MD5 key
algorithm.
Key 1 to 1024 1 This parameter specifies the number of the

key.
Password - - This parameter specifies the password of

the key.
Trusted Yes No If you set this parameter to No, the key is

No verified but cannot be trusted during the
clock synchronization. Therefore, the
clock of the NE cannot be synchronized.
Parameters for Setting Automatic Synchronization

Start Time - - l This parameter

specifies the start time
of the synchronization
period. After this
parameter is
specified, the NMS
and the NE
synchronize the time
once at the intervals
of Synchronization
Period(days)Period(
days).
l It is recommended
that you use the
default value.
DST Selected Deselected l This parameter

Synchronization
Starting Time is the
daylight saving time.
according to the
actual situation.

Period(days) 1 to 300 1 l This parameter

indicates the period of
synchronizing the
time of the NE with
the time of the NMS.
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

NE - - This parameter indicates the name of the

NE.
TimeZone - - This parameter indicates the time zone.
DST - - This parameter indicates whether DST is

enabled.
Parameters for Time Zone

Time Zone - - l After the time zone is changed, the

current time of the NE is changed
accordingly.
l This parameter is set according to the
place where the NE is located.

DST Selected Deselected l The parameters related to daylight

Deselected saving time can be valid only when this
parameter is selected.
situation whether daylight saving time
is used in the place where the NE is
located.
Offset 1 to 120 - This parameter specifies the offset value of

Unit: minute(s) the daylight saving time.
Start Rule WEEK WEEK This parameter specifies the method of

DATE adjusting the daylight saving time.
Start Time - - This parameter specifies the start daylight

saving time.
End Rule WEEK WEEK This parameter specifies the method of

DATE adjusting the daylight saving time.
End Time - - This parameter specifies the end daylight

saving time.
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.

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.

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 - - This parameter

indicates the
password that
corresponds to
Key ID again.

Trusted Yes Yes l When this

No parameter is
set to No, the
key
verification is
not trusted.
After
receiving the
key, the NE
rejects the
clock
synchronizatio
n service.
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.

Parameters for Managing Licenses

Board - - Specifies the objects to which licenses are

applied.
License File Type - - Specifies the license type corresponding to

each board.
Capability - - Specifies the capacity of a license file.
Loaded - - Specifies whether a license is loaded to an

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

NE Name - - This parameter indicates the name of the

NE.
NE Type - - This parameter indicates the type of the

NE.
Operation Type - - This parameter indicates the type of the

operation, such as loopback, and shutdown
of the laser.
Auto Disabling Disabled Enabled This parameter specifies whether to

Enabled automatically disable the operations such
as loopback, and shutdown of the laser.
Auto Disabling 1 to 2880 5 This parameter specifies the time of

Time(min) automatically disabling the operations such
as loopback, and shutdown of the laser.

B.1.2 Parameters for Communications Management

This topic describes the parameters that are used for communications management.
B.1.2.1 Parameter Description: NE Communication Parameter Setting

This topic describes the parameters that are used for NE communication setting.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication >
Parameters for NE Communication Setting

IP Address - Before delivery, the In the HWECC solution, an IP address is

IP address of the set according to the following rules:
NE is set to l The IP address, subnet mask, and
129.9.0.x. The letter default gateway of the gateway NE
x indicates the basic should meet the planning requirements
ID. of the external DCN.
Gateway IP - 0.0.0.0 l If an NE uses the extended ECC, the IP
Address address must be in the same network
segment.
Subnet Mask - 255.255.0.0 l The IP address of other NEs should be
set according to the NE ID. In this
case, the IP address of an NE should be
set in the format of 0x81000000+ID.
That is, if the ID is 0x090001, the IP
address should be set to 129.9.0.1.
l The IP address of an NE cannot be a
broadcast address, a network address,
or an IP address on network segments
127.0.0.0/8, 192.168.0.0/16, and
192.169.0.0/16.
Extended ID 1 to 254 9 l Do not change the extended ID when

the number of actual NEs does not
exceed the range permitted by the basic
NE ID.

Connection Mode Common + Security Common + Security l Specifies the connection mode that the
SSL SSL gateway NE allows the NMS to use for
Common connecting to the gateway NE.
Security SSL l If the gateway NE has no special
security requirement for connection to
the NMS, Connection Mode can be
set to Common.
l If the gateway NE requests secure
connection to the NMS for preventing
information interception and cracking,
Connection Mode needs to be set to
Security SSL.
l If NE communication security level
needs to be the same as NMS
communication security level,
Connection Mode needs to be set to
Common + Security SSL.
l The default parameter value is
recommended unless the gateway NE
requires that the NMS use the SSL
connection mode.
l The parameter value takes effect only
when it is set for a gateway NE and the
gateway NE is connected to the NMS
by means of the IP protocol.
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
DCC Management from the Function Tree.
2. Click the DCC Rate Configuration tab.
Parameters for DCC Rate Configuration

Port - - This parameter indicates the port that is

connected to the DCC channel.

Enabled/Disabled Enabled Enabled It is recommended that you use the default

Disabled value, except for the following cases:
l If the port is connected to the other
ECC subnet, Enabled/Disabled is set
to Disabled.
l If the port is connected to a third-party
network and does not exchange the
network management information with
other ports, Enabled/Disabled is set to
Disabled.
Channel D1-D3 D1-D1 (for the It is recommended that you use the default
D4-D12 PDH radio whose value, except for the following cases:
transmission l If the IP DCN solution is adopted,
D1-D12 capacity is less than Channel for the SDH line ports is set
D1-D1 16xE1) to a value that is the same as the value
D1-D3 (for other for third-party network.
cases) l If the DCC transparent transmission
solution is adopted, the value of
Channel for the SDH line ports should
not conflict with the value that is set for
the third-party network.
DCC Resources - - This parameter indicates the DCC

resources.
Communication - - This parameter indicates the

Status communication status.
Protocol Type HWECC AUTO l An established microwave link uses

TCP/IP TCP/IP if Protocol Type retains the
default value AUTO at both ends of the
L2DCN link. If Protocol Type is set to TCP/IP
AUTO or HWECC at one end of the link and
AUTO at the other end, the link uses
TCP/IP or HWECC.
l If the IP DCN solution is adopted,
Protocol Type is set to TCP/IP.
l When the L2 DCN solution is used, set
Protocol Type to L2DCN.

IP Address - - l IP Address is available only if

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 1 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
DCC Management from the Function Tree.
2. Click the DCC Transparent Transmission Management tab.
3. Click Create.

Parameters for DCC Transparent Transmission Management

Source Timeslot/ - - This parameter specifies the source

Porta timeslot or port.
Transparent D1 - l Only one overhead byte can be selected

Transmission of D2 each time.
Overhead Bytes at l X1, X2, X3, and X4 indicate the
Source Port D3
customized overhead bytes that are
D4 used for transmitting asynchronous
D5 data services.
D6 l An overhead byte cannot be a byte that
D7 is used. For example, an overhead byte
cannot be a byte in the used DCC
D8
channel.
D9 NOTE
D10 Only the ISU2/ISX2/ISV3/SL1DA /CD1/
ISM6board supports transparent transmission
D11 of the K1/K2 byte.
D12
E1
E2
F1
K1
K2
X1
X2
X3
X4
Sink Timeslot/ - - This parameter specifies the sink timeslot

Porta or port.

Transparent D1 - l Only one overhead byte can be selected

Transmission of D2 each time.
Overhead Bytes at l An overhead byte cannot be a byte that
Sink Port D3
is used. For example, an overhead byte
D4 cannot be a byte in the used DCC
D5 channel.
D6 l Generally, Transparent Transmission
D7 of Overhead Bytes at Sink Port can
be set to a value that is the same as or
D8
different from the value in the case of
D9 Transparent Transmission of
D10 Overhead Bytes at Source Port.
D11 NOTE
Only the ISU2/ISX2/ISV3/SL1DA /CD1/
D12 ISM6board supports transparent transmission
of the K1/K2 byte.
E1
E2
F1
K1
K2
X1
X2
X3
X4
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functions
the same regardless of the source port or sink port.
b. The function of transparently transmitting the K1/K2 byte conflicts with some certain higher-priority
functions. When higher-priority functions are configured, the function of transparently transmitting the
K1/K2 byte is automatically deleted. Higher-priority functions include linear multiplex section protection
(MSP), ring MSP, 1+1 protection, N+1 protection, and IF port service mode switchover.
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.

Parameters for the ECC Extended Mode

ECC Extended Auto mode Autosensing mode It is recommended that you use the default
Mode Specified mode value.
NOTE
Autosensing mode
By default, the adaptive mode is enabled for the
extended ECC on an NE. That is, when the
NMS port on an NE finds that the automatic
extended ECC is enabled on another NE in the
same network segment, the automatic extended
ECC is enabled on this NE. Otherwise, the
extended ECC is not enabled on this NE.
Parameters for Setting the Server

IP - - This parameter indicates the IP address of

the server.
Port 1601 to 1699 0 l This parameter is valid only when

ECC Extended Mode is set to
Specified mode.
l This parameter can be set only when
the NE functions as the server of the
extended ECC. In normal cases, the NE
that is close to the NMS functions as
the server.
l This parameter can be set to any value
from 1601 to 1699.
Parameters for Setting the Client

Opposite IP - 0.0.0.0 l This parameter is valid only when

ECC Extended Mode is set to
Port 1601 to 1699 0 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.

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

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.

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
Target NE - - Specifies the NE for which a ping test will

be performed.
Packet Length 0-800 64 l Specifies the test packet length.

(Byte) l It is recommended that this parameter
take its default value.
Packet Quantity 1-65535 3 l Specifies the number of test packets.

Sending 0-65535 0 l Specifies the test packet transmission

Interval(ms) interval.
To Be 1-65535 1000 l Specifies the maximum time for test

Translated(ms) packet to wait until being responded to.
Traceroute Parameters
Target NE - - Specifies the NE for which a traceroute

test will be performed.

Forwarding NEs 0-255 64 Specifies the number of NEs that test

packets will traverse during the forwarding
process.

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

Destination - - This parameter indicates the destination

Address address of the packets. This parameter can
be set to a valid IP address of class A, B,
or C only, but cannot be set to the IP
address of the local host or the loopback
address with the 127 field.
Mask - - This parameter indicates the subnet mask

of the destination address of the packets.
Gateway - - This parameter indicates the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of
the next hop of the packets.
Protocol - - l DIRECT: indicates the route between

the local NE and an adjacent NE.
l STATIC: indicates the route that is
created manually.
l OSPF: indicates the route between the
local NE and a non-adjacent NE.
l OSPF_ASE: indicates the route whose
Destination Address is beyond the
OSPF domain.
l OSPF_NSSA: indicates the route
whose Destination Address is in a not
so stubby area (NSSA).
l A route can be deleted in the case of
STATIC only, but cannot be edited in
the other cases.
l Compared with a dynamic route, a
static route has a higher priority. If any
conflict occurs, the static route is
preferred.

Interface - - This parameter indicates the interface that

is used on the route. Interface is a concept
specified in the TCP/IP protocol stack. In
the TCP/IP protocol stack, you can create
multiple types of interface, such as a
loopback interface (namely, the interface
whose IP address is 127.0.0.1), an Ethernet
interface, and PPP interface. Each
interface must have a unique interface
name.
Metric - - This parameter indicates the maximum

number of routers through which the
packets are transmitted. Metric is used to
indicate the overhead bytes that are
transmitted to the destination address. The
smaller the value, the less the overhead
bytes. If multiple routes can reach the
same destination address, a route whose
overhead is less is preferred to transmit the
packets.
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
2. Click the IP Route Management tab.
3. Click New.
Parameters for Creating IP Routes

Destination - - This parameter specifies the destination

Address address of the packets. This parameter can
be set to a valid IP address of class A, B,
or C only, but cannot be set to the IP
address of the local host or the loopback
address with the 127 field.
Subnet Mask - - This parameter indicates the subnet mask

of the destination address of the packets.

Gateway - - This parameter specifies the IP address of

the gateway on the subnetwork where the
NE is located, namely, the IP address of
the next hop of the packets.
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
Communication > IP Protocol Stack Management from the Function Tree.
2. Click Reachability Test and choose Ping Test or Trace Route from the drop-down
menu.
Ping Test Parameters

Target NE IP - - Specifies the NE for which a ping test will

be performed.
Packet Length 0-800 64 l Specifies the test packet length.

(Byte) l It is recommended that this parameter
Packet Quantity 1-65535 3 l Specifies the number of test packets.

Sending 0-65535 0 l Specifies the test packet transmission

Interval(ms) interval.


Traceroute Parameters
Target NE IP - - Specifies the NE for which a traceroute

test will be performed.
Max Hops 1-30 10 Specifies the number of hops which test

packets traverse during the packet
transmission process.
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
2. Click the OSPF Parameter Settings tab.
OSPF Parameters
Area - 0.0.0.0 l If only an OSPF area is configured on

an NE, set this parameter according to
l If multiple OSPF areas are configured
on an NE, this parameter takes its
default value 0.0.0.0.

DCC Hello 1 to 255 10 l DCC Hello Timer(s) specifies the

Timer(s) 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 1 to 65535 40 l DCC Neighbor Dead Time(s)

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.

DCC 1 to 65535 5 l DCC Retransmission Timer(s)

Retransmission specifies the interval for transmitting a
Timer(s) request through the DCC channel or
inband DCN to retransmit the link state
advertisement (LSA) packets.
its default value.
DCC Delay(s) 1 to 3600 1 l DCC Delay(s) specifies the delay time

to transmit the LSA packets through
the DCC channel or inband DCN.
l The LSA packets in the LSA database
of the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the
age of the LSA packets based on the
value of DCC Delay(s).
its default value.
LAN Hello 1 to 255 10 l DCC Hello Timer(s) specifies the

Timer(s) 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.

LAN Neighbor 1 to 65535 40 l LAN Neighbor Dead Time(s)

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 1 to 65535 5 l LAN Retransmission Timer(s)

Retransmission specifies the time for transmitting a
Timer(s) request for retransmission of the LSA
packets through the Ethernet network
management port or NE cascading port.
its default value.
LAN Delay(s) 1 to 3600 1 l LAN Delay(s) specifies the delay time

to transmit the LSA packets through
the Ethernet network management port
or NE cascading port.
l The LSA packets in the LSA database
of the local router are aged as the time
elapses, but are not aged when they are
being transmitted on the network.
Hence, before the LSA packets are
transmitted, you need to increase the
age of the LSA packets based on the
value of LAN Delay(s).
its default value.

OSPF Status Enabled Enabled Specifies whether the OSPF protocol is

Disabled enabled. If an NE uses only static routes
with OSPF disabled, set this parameter to
Disabled.
STUB Area Enabled Disabled l Specifies whether to enable the STUB

Disabled Area.
l Set this parameter as required.
l A backbone area cannot be a STUB
area.
NSSA Area Enabled Disabled l Specifies whether to enable the NSSA

Disabled Area.
l A backbone area cannot be an NSSA
area.
Direct route Enabled Disabled l Specifies whether the direct route

Disabled automatic flooding function is enabled.
l Direct route: the route detected by the
link layer protocol.
Static route Enabled Disabled l Specifies whether the static route

Disabled automatic flooding function is enabled.
l Static route: the route manually
configured by the network
administrator.
Default route Enabled Disabled l Specifies whether the default route

Disabled automatic flooding function is enabled
for ASBRs.
l Default OSPF routes are routes whose
destination addresses and subnet masks
are 0s.
Router ID - - The Router IP address is always the NE IP

address.

Opaque LSA of Enabled Enabled l Specifies whether the Ethernet network

External Network Disabled management port or NE cascading port
Port transmits Type-10 LSAs.
l If this parameter is set to Disabled, the
Ethernet network management port or
NE cascading port transmits network
management information.
LAN Interface Enabled Disabled l Specifies whether the OSPF protocol is

Disabled enabled for the Ethernet network
l If this parameter is set to Enabled, the
OSPF protocol is communicated with
other equipment through the Ethernet
network management port or NE
cascading port.
OSPF authentication parameters

Interface Type - - l Displays the DCN port types that allow

the OSPF authentication key to be
specified.
l LAN indicates the Ethernet network
l DCC indicates the DCC channels or
inband DCN port.
Authentication none none l Specifies the OSPF authentication

Type MD5 mode for which a key needs to be set.
simple l If Authentication Type is MD5, a key
needs to be set for the MD5
authentication mode.
l If Authentication Type is simple, a
key needs to be set for the simple
authentication mode.
l If Authentication Type is none, all
preset keys for the related port type are
cleared.
Authentication - - Specifies the OSPF authentication

Password password for each port type.
MD5 Key 1-255 - MD5 Key is available only when

Authentication Type is MD5.

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
2. Click the Proxy ARP tab.
Parameters for configuring the proxy ARP

Proxy ARP Disabled Disabled l The proxy ARP enables the NEs in the
Enabled same network segment but different
domains to communicate with each
other.
l To realize communication between
such NEs, the source NE sends the
ARP broadcast packet to address the
route to the destination NE. The NE
with the proxy ARP function enabled
checks the routing table after sensing
the ARP broadcast packet. If the
routing table contains the destination
address that the ARP broadcast packet
looks for, the NE returns an ARP
spoofing packet, which enables the NE
that sends the ARP broadcast packet to
consider that the MAC address of the
NE that returns the ARP spoofing
packet is the MAC address of the
destination NE. In this manner, the
packet that is to be sent to the
destination NE is first sent to the NE
with the proxy ARP function enabled
and then forwarded to the destination
NE.
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.

Parameters Required for Configuring Multiple OSPF Areas

ID - - Displays the area ID.
Default Area - - Displays whether an area is the default

area.
Authentication none none l Specifies the OSPF authentication type

Type MD5 used by an area.
simple l none indicates no authentication.
Automatic Route Enabled Disabled l Specifies whether automatic route

Aggregation Disabled aggregation is enabled for an area.
l The number of routes after automatic
route aggregation is the same as the
number of Networks.
Stub Type - - Displays the STUB type of an area.
Network Parameters
IP Address - - Displays the IP addresses of the Networks

in an area.
Subnet Mask - - Displays the subnet masks of the Networks

in an area.
Parameters for Configuring Manual Route Aggregation

IP Address - - Displays the IP address of the Network

where route aggregation is manually
enabled.
Subnet Mask - - Displays the subnet mask of the Network

where route aggregation is manually
enabled.
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.

Navigation Path
3. Click New.
Parameters Required for Creating OSPF Areas

ID - - l Set the area ID of a new OSPF area

l An NE can be configured with a
maximum of four OSPF areas.
IP Address - - l Set the IP addresses of the Networks in

an area according to planning
information.
l An area supports a maximum of four
Networks.
Subnet Mask - - Set the subnet masks of the Networks in an

area according to planning information. A
subnet mask can contain a maximum of 30
bits.
Authentication none none Specifies the OSPF authentication type

Type MD5 used by an area according to planning
information.
simple
l none indicates no authentication.
l MD5 indicates that authentication is
performed based on the preset
password, with the password encrypted
in MD5 mode.
l simple: indicates that authentication is
performed based on the preset
password, with the password not
encrypted.
Automatic Route Enabled Disabled l Specifies whether automatic route

Aggregation Disabled aggregation is enabled for an area.
l The number of routes after automatic
route aggregation is the same as the
number of Networks.

Stub Type NON-STUB NON-STUB Set the STUB type of an area according to
STUB planning information.
NSSA l For the backbone area, this parameter
must be set to NON-STUB.
l For other areas, it is recommended that
you set this parameter to NON-STUB.
If required, this parameter can also be
set to STUB or NSSA.
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
2. Click the Multi-OSPF Management tab.
3. In Manual Route Aggregation, click Add.
Parameters for Configuring Manual Route Aggregation

IP Address - - Specifies the IP address of the Network

where routes need to be aggregated
manually.
Subnet Mask - - Specifies the subnet mask of the Network

where routes need to be aggregated
manually.
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.

Port OSPF Parameters

Port - - Displays the ports that allow OSPF

parameters to be set.
Path Type - - Displays the current DCC channel type.
OSPF Status Enabled Enabled l Specifies whether to enable the OSPF.

Disabled l Set this parameter as required.
Opaque LSA of Enabled Enabled l Specifies whether DCCs support

External Network Disabled Type10 LSA.
Port l Set this parameter as required.
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
Destination NE — - This parameter specifies the Name of the

Name destination NE.
Destination NE ID - - This parameter specifies the ID of the

destination NE.
Protocol Type - - Only IP protocols are supported.
Next Hop Address - - This parameter specifies the IP address of

the destination NE.
Routing - - This parameter specifies the number of

Distance(hop) 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.

Navigation Path
DCN Management from the Function Tree.
2. Click the Bandwidth Management tab.
Parameters for Bandwidth Management

Ethernet Board 2 to 4094 4094 Specifies the VLAN ID used by inband

VLAN ID DCN channels.
l The equipment on the traditional DCN
can be connected to the NMS through
the SCC board, but an OptiX RTN 900
can also be connected to the NMS
through an Ethernet port. If an Ethernet
port is used to carry the network
management information, the OptiX
RTN 900 differentiates the network
management information and Ethernet
service information according to the
VLAN ID.
l If the default VLAN ID of the inband
DCN conflicts with the VLAN ID in
the service, the Ethernet Board VLAN
ID of the inband DCN can be changed
manually.
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 - - For OptiX RTN 900 products, this

Bandwidth(kbit/s) parameter specifies the inband DCN
bandwidth for a Smart E1 port. This
parameter also takes effect to E1s in an
STM-1.
Tunnel - - OptiX RTN 900 does not support this

Bandwidth(kbit/s) parameter.

IF Port 64 to 5000 512 IF Port Bandwidth(kbit/s) specifies the

Bandwidth(kbit/s) 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 2 to 4094 - NMS Port VLAN ID indicates the VLAN
ID ID of Huawei NMS and is used to
distinguish Huawei DCN packets from
third-party DCN packets on NMS ports.
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
DCN Management from the Function Tree.
2. Click the Port Settings tab.
Parameters for Setting Ports

Port Name - - This parameter indicates the port name.
Enabled Status Enabled - l Enabled Status specifies the enabling

Disabled status of the port.
l The network management information
can be transmitted over the inband
DCN when the DCN function is
enabled for the ports at both ends of a
link.

Protocol Type IP IP l Specifies the DCN protocol used by the

HWECC inband DCN.
L2DCN l If Protocol Type is set to different
values for two interconnected sets of
equipment, equipment interconnection
fails. Therefore, set Protocol Type to
the same value for both ends of a link.
IP Address - - l This parameter is available only when

Protocol Type is set to IP.
parameter specifies the interface IP
address of the non-backbone area port
on the ABR.
NE, this parameter specifies the IP
address for a port that does not belong
to the default process.
Subnet Mask - - l This parameter is available only when

Protocol Type is set to IP.
parameter specifies the subnet mask of
the non-backbone area port on the
ABR.
NE, this parameter specifies the subnet
mask for a port that does not belong to
the default process.
ATN Enabled Disabled This parameter enables or disables the

Compatibility Disabled ATN compatibility mode for an NE. When
Mode 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.
VLAN 0 to 4094 0 This parameter 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.

OSPF Subnet 1 to 4 1 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 Enabled Enabled This parameter enables or disables OSPF

Status Disabled for a port.
B.1.2.19 Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Navigation Path
l In the NE Explorer, select the desired NE from the Object Tree and then choose
l Click the Access Control tab.
Parameters
Parameter Value Default Description
Range Value
Port Name - - Displays the Ethernet ports

that support this function.
Enabled Status Disabled Disabled l Specifies the enabling

Enabled status of the port.
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 - 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.


Range Value
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.

Packet Type - - Displays the packet type for which the

packet priority can be manually specified.
Supported - - This parameter cannot be specified

Application manually.
Packet Priority CS6 CS6 (Packet Type Specifies the VLAN priorities of inband
EF is VLAN) DCN packets or the PHBs corresponding
BE (Packet Type is to the DSCP values of the inband DCN
AF4 packets.
DSCP)
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
Communication > L2DCN Management from the Function Tree.
l Click Query.


Configuration Auto Auto When an OptiX RTN 900 uses the L2

Status Disabled 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

Enabled in the following scenarios:
– 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

Enable Ethernet Selected - After The First Network Port is set to

Access Deselected Enabled for Ethernet access, the NE can
access the NMS through the Ethernet port.
PORT - - This parameter displays the NMS port and

the NE cascading port on the system
control, switching, and timing board.

Work Mode adapt - This parameter specifies the working

10M Half_Duplex modes of the NMS port and the NE
cascading port on the system control,
10M Full_Duplex switching, and timing board.
100M Half_Duplex
100M Full_Duplex
Actual Work - - This parameter displays the working

Mode modes of the NMS port and the NE
cascading port on the system control,
switching, and timing board.
Enabled/Disabled Enabled Specifies whether the Ethernet network

Disabled management port or NE cascading port is
enabled.
Parameters for Access Control over Serial Ports

Enable Serial Port Selected Selected After Enable Serial Port Access is
Access Deselected selected, the NE can access the NMS or
command lines through the serial port.
Access Command Selected Deselected If Access Command Line is selected, the

Line Deselected serial interface can be used to access the
command line terminal.
Access NM Selected Deselected If Access NM is selected, the serial

Deselected interface can be used to access the NMS.
Baud Rate 1200 9600 l This parameter specifies the data

2400 transmission rate in the
communications through serial ports.
4800
9600 rate of the serial port at the opposite
end, and the rates at both ends must be
the same.
Parameters for OAM Access Control

Enable OAM Selected Selected After Enable OAM Access is selected, the
Access Deselected NE can access the NMS or command lines
through the mini USB port.

Access Command Selected Deselected If Access Command Line is selected, the

Line Deselected serial interface can be used to access the
command line terminal.
Access NM Selected Selected If Access NM is selected, the serial

Deselected interface can be used to access the NMS.
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
Community Enabled Enabled Set whether to verify the complexity of a

Complexity Verify Disabled community name.
If this parameter is set to Enabled, the
community name must meet the following
rules:
l The community name is a character
string consisting of at least six
characters.
l The community name is a combination
of at least two types of the following
characters:
– Lowercase letters: a to z
– Uppercase letters: A to Z
– Digits: 0 to 9
– Special characters: ` ~ ! @ # $ % ^
&*()-_=+\|[{}];:'",<.
> / ? or space

NMS IP Address - 0.0.0.0 Set NMS IP Address to the IP address of

the SNMP server that uses these
communications parameters. If there are
no restrictions on the IP address of the
SNMP server that accesses the NE, set this
parameter to 0.0.0.0. However, setting the
NMS IP address to 0.0.0.0 causes certain
security risks. Therefore, make sure that
you know the security risks when setting
the NMS IP address to 0.0.0.0.
If the NMS IP Address is set to 0.0.0.0,
the NE does not support the Trap function.
Read/Write Read Only Read Only Verify Read/Write Permissions of the

Permissions Read/Write SNMP server based on the network plan.
Read/Write Permissions must take the
same values as the right parameters set on
the SNMP server.
Report SDH - - Set Report SDH Performance Trap to

Performance Trap Report if an SNMP server is required to
automatically report trap packets when the
SDH performance crosses the threshold,
the data performance crosses the threshold,
or an alarm is generated on the NE.
Report IP - - Set Report IP Performance Trap to

Performance Trap Report if an SNMP server is required to
automatically report trap packets when the
SDH performance crosses the threshold,
the data performance crosses the threshold,
or an alarm is generated on the NE.
Report Alarm - - Set Report Alarm Trap to Report if an

Trap SNMP server is required to automatically
report trap packets when the SDH
performance crosses the threshold, the data
performance crosses the threshold, or an
alarm is generated on the NE.
Trap Port - - It is recommended that Port take the

default value.
Read Community - - Verify Read Community Name of the

Name SNMP server based on the network plan.
Read Community Name must take the
the SNMP server.

Write Community - - Verify Write Community Name of the

Name SNMP server based on the network plan.
Write Community Name must take the
the SNMP server.
Report Trap SNMPV1 SNMPV3 Set the Report Traps Version parameter
Version SNMPV2C based on the SNMP protocol version
running on the SNMP server.
SNMPV3
Report Trap - - Set Report Trap Community Name

Community Name according to the network plan.
Report Trap User - - Set Report Trap User Name according to

Name 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

Packet 1 to 3600 30 l Set the transmission interval for LLDP

Transmission packets.
Interval(s) l It is recommended that you retain the
default value for this parameter.
TTL Multiplier 4 to 100 4 l Set the TTL multiplier.

l If no information is received from a
neighbor in the TTL multiplier time,
delete all information about the neighbor.
l It is recommended that you retain the
Re-initialization 1 to 10 2 l Set the re-initialization delay time, that is

Delay(s) the time before a port can change from
disabled to other status.
l It is recommended that you retain the

Packets 1 to 8 4 l Set the number of packets that are

Transmitted in continuously transmitted in Fast mode.
Fast Mode l It is recommended that you retain the
Port Parameter Description

Port - - Displays port information.
Mode Disable Disable l Generally, set Mode to

Transmit Transmit&Receive for a port for which
the LLDP has been enabled.
Receive
l If unidirectional Ethernet connection is set
Transmit&Receive up between a port for which the LLDP
has been enabled and its neighbor
equipment, set Mode to Transmit or
Receive based on the service direction.
l Set Mode to Disable for a port for which
the LLDP is disabled.
VLAN 1 to 4094 1 Set VLAN IDs and priorities based on the

network plan.
VLAN Priority 0 to 7 0
Multicast Mode Nearest bridge Nearest bridge This parameter can only be set to Nearest
bridge.
Neighbor No. - - Displays the number of a neighbor.
Neighbor Holding - - Displays the latest update time of a neighbor,

Time(s) that is the latest time a device receives
information from its neighbor.
Neighbor - - Displays the remaining survival time of a

Remaining neighbor.
Time(s)
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.

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
Function - - Specifies the desired RADIUS function, the

authentication server ID, and the server type.
Server ID - -
l Function, Server ID, and Server Type
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 Specifies the active/standby status of the

Standby RADIUS server or proxy server.
l If no standby server is required, set
Server Status to Active.
l The NE supports one active server and
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 3-10 5 Specifies the number of packet

Transmission retransmission attempts and the interval
between the attempts.
Packet 1-5 3
Retransmission l If an NE does not receive the response
Attempts 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.

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
Function Authentication Authentication Specifies the RADIUS function that an NE

Accounting needs to use.
Authentication + l For NE RADIUS authentication, select
Accounting Authentication.
l For both NE RADIUS authentication and
NE usage accounting, set this parameter
to Authentication + Accounting or
Accounting (when the Authentication
function has been enabled).
Server Type RADIUS Server RADIUS Server Specifies the server type used for NE
Proxy Server 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.

Server ID IP Address IP Address Specifies the address of the server that is

NE ID used for NE RADIUS authentication.
l If Server Type is RADIUS Server, set
Server ID to IP Address and specify the
IP address of the RADIUS server.
l If Server Type is Proxy Server, it is
recommended that you set Server ID to
NE ID and set the gateway NE as the
proxy server.
l If Server Type is Proxy Server and there
is no IP route between the NE and the
proxy server, Server ID can be set to
only NE ID. If Server Type is Proxy
Server and there is an IP route between
the NE and the proxy server, Server ID
can be set to NE ID or IP Address.
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
NE - - Displays the NE name.
RADIUS Client Open Close Specifies whether an NE has the ability to be

Close a RADIUS client. The RADIUS function can
be enabled on an NE only if RADIUS Client
is set to Open for the NE.

Proxy Server Open Close Specifies whether an NE has the ability to be

Close a proxy server.
l If an NE needs to function as a proxy
server, set Proxy Server to Open for the
NE.
l Proxy Server can be set to Open only if
RADIUS Client is set to Open.
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.

WTR time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
l When the time after the former
working channel is restored to normal
reaches the set WTR time, a revertive
switching occurs.

SD Switching Enabled Enabled l This parameter specifies whether the

Disabled signal degradation switching function
of N+1 protection is enabled.
l When this parameter is set to Enabled,
the signal degradation condition is
considered as a trigger condition of
l It is recommended that you set this
parameter to Enabled.
Protect Group Enhanced N+1 Standard N+1 l Only OptiX RTN 980L supports this
Type Standard N+1 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 Description
Value
Select Mapping Direction Work Unit Work This parameter

Protection Unit Unit specifies the mapping
direction of N+1
protection.


Value
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

Protection Group - - This parameter indicates the ID of the

ID protection group.

Protect Group Enhanced N+1 Standard N+1 l Only OptiX RTN 980L supports this
Type Standard N+1 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
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 - l This parameter indicates or specifies

Disabled whether the SD switching function of
N+1 protection is enabled.
the SD condition is considered as a
trigger condition of protection
switching.
Protocol Status - - This parameter indicates the status of the

switching control protocol.

Slot Mapping Settings Parameters

Unit Type - - This parameter indicates the type of the

unit.
Line-Side Port - - This parameter indicates the information

about the working board or protection
board.
Switching Status - - This parameter indicates the switching

state.
Protected Unit - - This parameter indicates the protected unit.
Remote/Local End - - This parameter indicates the local end or

Indication remote end.
B.2.3 Parameter Description: IF 1+1 Protection_Create

This topic describes the parameters for creating an IF 1+1 protection group.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
2. Click Create.

Parameters
Working Mode HSB HSB l This parameter specifies the

FD working mode of the IF 1+1
protection.
SD
l When Working Mode is set to
HSB, the equipment provides a 1+1
hot standby configuration for the IF
board and ODU at both ends of each
hop of a radio link to realize the
protection.
l When Working Mode is set to FD,
the system uses two channels that
have a frequency spacing between
them, to transmit and receive the
same signal. The remote end selects
signals from the two received
signals. With FD protection, the
impact of the fading on signal
transmission is reduced.
l When Working Mode is set to SD,
the system uses two antennas that
have a space distance between them,
to receive the same signal. The
equipment selects signals from the
two received signals. With SD
protection, the impact of the fading
on signal transmission is reduced.
l The FD mode and SD mode are
compatible with the HSB switching
function.

Revertive Mode Revertive Mode Revertive Mode l This parameter specifies the
Non-Revertive revertive mode of the IF 1+1
protection.
l When Revertive Mode is set to
Revertive Mode, the NE that is in
the switching state releases the
switching and enables the former
working channel to return to the
normal state some time after the
former working channel is restored
to normal. It is recommended that
you set this parameter to Revertive
Mode.
l When Revertive Mode is set to
Non-Revertive, the NE that is in the
switching state keeps the current
state unchanged unless another
switching occurs even though the
former working channel is restored
to normal.
WTR Time(s) 300 to 720 600 l This parameter specifies the wait-to-
restore (WTR) time.
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
default value.

Enable Reverse Enabled Enabled l This parameter indicates whether

Switching Disabled 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 Enable
Reverse Switching at the source
end is set to Enabled and the
reverse switching conditions are
met, the IF 1+1 protection switching
occurs at the source end.
l Enable Reverse Switching is valid
only when Working Mode is set to
HSB or SD.
l Generally, it is recommended that
you set Enable Reverse Switching
to Enabled.
Working/ Work Unit - For RTN 905 1E:

Protection Unit Protection Unit Set Working/Protection Unit Type to
Type Work Unit for the main RTN 905 1E
and to Protection Unit for the standby
RTN 905 1E.
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.
NOTE
Only the OptiX RTN 905 1E supports this
parameter.

Alarm Report Only board alarms Only board alarms l When Alarm Report Mode is set to
Mode Only protection group Only board alarms, only IF board
alarms alarms are reported.
Protection group and l When Alarm Report Mode is set to
board alarms Only protection group alarms,
protection group alarms are reported
if a protection group fails or
degrades. Service alarms on IF
boards and radio links are
suppressed.
l When Alarm Report Mode is set to
Protection group and board
alarms, IF board alarms and
protection group alarms are
reported.
l It is recommended that you set
Alarm Report Mode to Only
protection group alarms. In this
case, protection group alarms are
reported to indicate radio link faults.
NOTE
The faulty board reports related fault alarms
regardless of parameter settings.
Anti-jitter Time(s) 0 to 600 300 l When Anti-jitter Time(s) is not set

to 0, a protection group does not
report an alarm immediately after it
is degraded, but reports the alarm
after the specified anti-jitter time
expires.
l It is recommended that Anti-jitter
Time(s) take its default value.
NOTE
Anti-jitter Time(s) is valid only for alarms
reported when a protection group degrades.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter Time(s), and
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. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1



Working Mode HSB - l This parameter indicates the working

FD mode of the created IF 1+1 protection
group.
SD
l In HSB mode, the equipment provides
a 1+1 hot standby configuration for the
IF board and ODU at both ends of each
hop of a radio link to realize the
protection.
l In FD mode, the system uses two
channels that have a frequency spacing
between them, to transmit and receive
the same signal. The remote end selects
signals from the two received signals.
With FD protection, the impact of the
fading on signal transmission is
reduced.
l In SD mode, the system uses two
antennas that have a space distance
between them, to receive the same
signal. The equipment selects signals
from the two received signals. With SD
protection, the impact of the fading on
signal transmission is reduced.
l The FD mode and SD mode are
compatible with the HSB switching
function.

Revertive Mode Revertive Mode - l This parameter indicates or specifies

Non-Revertive the revertive mode of the protection
Mode group.
l When this parameter is set to Revertive
Mode, the NE that is in the switching
state releases the switching and enables
the former working channel to return to
the normal state some time after the
former working channel is restored to
normal.
l When this parameter is set to Non-
Revertive Mode, the NE that is in the
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.

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 Enabled - l This parameter indicates or specifies

Switching Disabled whether the reverse switching function
is enabled.
l When both the main IF board and the
standby IF board at the sink end report
service alarms, they send the alarms to
the source end by using the MWRDI
overhead in the microwave frame.
When this parameter at the source end
is set to Enabled and the reverse
switching conditions are met, the IF
1+1 protection switching occurs at the
source end.
l This parameter is valid only when
Working Mode is set to HSB or SD.

NE Switching - - l This parameter indicates the switching

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

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

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

Port working board on the channel side.
Alarm Report Only board alarms - l When Alarm Report Mode is set to
Mode Only Protection Only board alarms, only IF board
group alarms alarms are reported.
Protection group l When Alarm Report Mode is set to
and board alarms Only protection group alarms,
protection group alarms are reported if
a protection group fails or degrades.
Service alarms on IF boards and radio
links are suppressed.
l When Alarm Report Mode is set to
Protection group and board alarms,
IF board alarms and protection group
alarms are reported.
l It is recommended that you set Alarm
Report Mode to Only protection
group alarms. In this case, protection
group alarms are reported to indicate
radio link faults.
NOTE
The faulty board reports related fault alarms
regardless of parameter settings.
Anti-jitter Time (s) 0 to 600 - l When Anti-jitter Time(s) is not set to

0, a protection group does not report an
alarm immediately after it is degraded,
but reports the alarm after the specified
anti-jitter time expires.
l It is recommended that Anti-jitter
Time(s) take its default value.

Alarm Deselected (no Deselected (no l This parameter specifies whether to

Suppression suppression) suppression) suppress the MW_BER_SD,
Selected MW_BER_EXC, MW_RDI,
(suppression) RADIO_RSL_LOW,
MAC_EXT_EXC, and
MAC_FCS_EXC alarms.
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

Unit - - This parameter indicates the working

board and protection board.
Slot Mapping - - This parameter indicates the names and

Relation ports of the working board and protection
board.
Working Status of - - This parameter indicates the working state

Device on the equipment side.
Signal Status of - - This parameter indicates the status of the

Channel link signal.
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.
l Only RTN 950s housing CSHU/CSHUA and RTN 950As housing SLF2CSHO support super EPLA.

Navigation Path
1. In the NE Explorer, select the desired NE from the Object Tree. Choose Configuration
> Physical Link Aggregation from the Function Tree.
2. Click New.
Parameters for Creating a PLA/EPLA Group (for OptiX RTN 905 1E/2E)
Cascading Status Cascaded Cascade This parameter specifies the cascading

Not Cascaded status.
PLA ID - 1 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 - This parameter is not supported.

protection
NE Role Master NE Master NE This parameter is valid only when

Slave NE Cascading Status is set to Cascaded, and
specifies whether an NE is the master or
slave NE in a PLA group.
PLA Type PLA PLA This parameter specifies the type of a

EPLA physical link aggregation group.
Main Board - - This parameter specifies the main IF board

in a physical link aggregation group.
Main Port - - This parameter specifies the main port in a

physical link aggregation group.
Available Cascade - - This parameter is valid only when

Ports Cascading Status is set to Cascaded, and
lists all available cascade ports.
Selected Cascade - - This parameter is valid only when

Ports Cascading Status is set to Cascaded, and
displays selected cascade ports.
Available Slave - - This parameter lists all available slave

Ports ports.
Selected Slave - - This parameter displays selected slave

Ports ports.

Parameters for Creating a PLA/EPLA Group (for OptiX RTN 980L/OptiX RTN
980)
Cascading Status Not Cascaded Not Cascaded This parameter specifies the cascading
status.

group.

a PLA group.




Ports ports.

Ports ports.
Parameters for Creating a PLA/EPLA/EPLA+ Group (for OptiX RTN 910A)


group.

EPLA+



Ports ports.

Ports ports.

Parameters for Creating a PLA/EPLA/EPLA+/Super EPLA Group (for OptiX RTN

950/OptiX RTN 950A)

group.

EPLA+
S-EPLA
Scheduling Mode Mode A Mode A This parameter can be specified only when
Mode B PLA Type is S-EPLA.
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 low-
priority services are distributed to
common-band and E-band links based
on their link bandwidths, implementing
inter-frequency AM.
High-Priority BE EF l When Scheduling Mode is Mode B,

Service Threshold AF1 This threshold can be specified for a
Super EPLA group in hitless mode.
AF2 Only an SP queue can be configured
AF3 with a PHB. Services in this SP queue
AF4 and other queues with higher-priorities
are high-priority services.
EF
CS6
CS7
Main Port Priority Auto Auto l This parameter specifies the priority for
Low a super EPLA group's member link.
This parameter generally takes the
High default value.
l This parameter can be specified only
when Scheduling Mode is Mode B.




Ports ports.

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.
l Only RTN 950s housing CSHU/CSHUA and RTN 950As housing SLF2CSHO support super EPLA.
Navigation Path
Configuration > Physical Link Aggregation from the Function Tree.
PLA/EPLA Parameters (for OptiX RTN 905 1E/2E,RTN 980 and RTN 980L)
Cascading Status - - This parameter displays the cascading

status.
PLA ID - - This parameter displays the ID of a PLA

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.

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 - - This parameter displays the working status

Status of the local NE.
Minimum Active - - This parameter specifies the minimum

Links number of available links in a PLA group
and helps to trigger Ethernet ring
protection switching (ERPS) switching
even if not all members in the PLA group
fail.
For example, if you set Minimum Active
Links to 2, ERPS switching is triggered
when either PLA member link fails.

a PLA group.
Extendable - - This parameter displays the Extendable

Bandwidth(M) 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
Disabled RTN 980L working as long-haul
microwave.

PLA/EPLA/EPLA+ Parameters (OptiX RTN 910A)


status.

group.

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 - - This parameter displays the hardware

of Main Port status of the main port in a PLA group.
Link Status of - - This parameter displays the link status of

Main Port the main port in a PLA group.
Work Status of - - This parameter displays the work status of


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.

of Slave Port status of the slave port in a PLA group.

Slave Port the slave port in a PLA group.


PLA/EPLA/EPLA+ Parameters (for OptiX RTN 950/RTN 950A)


status.

group.

group.
Scheduling Mode Hitless Hitless l When Scheduling Mode is Mode B, In

Common 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 low-
priority services are distributed to
common-band and E-band links based
on their link bandwidths, implementing
inter-frequency AM.
High-Priority 0-7 5 l When Scheduling Mode is Mode B,

Service Threshold 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
Low a super EPLA group's member link.
This parameter generally takes the
High default value.
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.

of Main Port status of the main port in a PLA group.




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.

of Slave Port status of the slave port in a PLA group.


B.2.7 Parameter Description: Radio Link Management

This topic describes parameters related to radio link management.
Navigation Path
> Radio Link Configuration from the Function Tree.
Basic Parameters
Protection 1+0 1+0 This parameter specifies the link protection

1+1 scheme.
OptiX RTN 905 1E does not support this
parameter.

XPIC Selected Deselected This parameter specifies whether cross

Deselected polarization interference cancellation
(XPIC) needs to be enabled on an IF board
that supports XPIC.
Link ID 1 to 4094 1 l This parameter specifies the radio link

ID.
l If the value of Received Link ID is
different from the value of this
parameter, the local end inserts an
alarm indication signal (AIS) to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the
received link ID is different from the
preset link ID.
l This parameter has an invalid random
value when a radio link fails.
Received Link ID - - l This parameter displays the received

link ID.
l If the value of this parameter is
different from the value of Link ID, the
local end inserts an AIS to the
downstream direction of the service. At
the same time, the local end reports an
alarm to the NMS, indicating that the
received link ID is different from the
preset link ID.
l This parameter has an invalid random
value when a radio link fails.
IF Parameters
IF Service Type Hybrid(Native Hybrid(Native This parameter specifies the type of

E1+ETH) E1+ETH) services carried by an IF board.
Hybrid(Native NOTE
STM-1+ETH) For details about services that different types of
IF boards support, see the IDU Hardware
SDH Description.
Channel Space - - This parameter specifies the channel

spacing of a radio link. Set this parameter

AM Status Selected Deselected l When this parameter is deselected, the

Deselected radio link uses the specified modulation
scheme. In this case, you need to
configure Modulation Mode.
l When this parameter is selected, the
radio link uses the corresponding
modulation scheme according to the
channel conditions.
l Only Integrated IP 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 - - l This parameter is valid only when AM

Capacity is selected.
Modulation l This parameter specifies the lowest-
order modulation scheme that the AM
function supports. Set this parameter
Generally, the value of this parameter is
determined by the service transmission
bandwidth that the radio must ensure
and the availability of the radio link
that corresponds to this modulation
scheme.
Full Capacity - - l This parameter is valid only when AM

Modulation is selected.
l This parameter specifies the highest-
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.

Guaranteed E1 - - l When Enable E1 Priority is set to

Capacity Disabled, this parameter specifies the
E1 service capacity of an IF port.
l When Enable E1 Priority is set to
Enabled, this parameter specifies the
E1 service capacity in Modulation
Mode of the Guaranteed AM
Capacity.
l This parameter is configurable when IF
Service Type is set to Hybrid(Native
E1+ETH).
STM-1 Capacity - - l This parameter specifies the STM-1

service capacity of an IF port.
l This parameter is configurable when IF
STM-1+ETH) or SDH.
Data Service - - This parameter displays the IF bandwidth

Bandwidth(Mbit/s occupied by data services on an IF board.
)
Enable E1 Priority Disabled Disabled l This parameter specifies whether the

Enabled E1 priority function needs to be
enabled.
l This parameter is configurable when
AM is selected and IF Service Type is
set to Hybrid(Native E1+ETH).

RF Parameters
TX Frequency - - l This parameter specifies the transmit

(MHz) frequency of an ODU/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 - - This parameter displays the receive

Frequency (MHz) frequency of an ODU/RFU.
T/R Spacing - - l This parameter specifies the spacing

(MHz) between the transmit and receive
frequencies of an ODU to prevent
interference between them.
l If Station Type of an ODU is TX high,
the transmit frequency is one T/R
spacing higher than the receive power.
If Station Type of an ODU is TX low,
the transmit frequency is one T/R
spacing lower than the receive power.
l If an ODU supports only one T/R
spacing, set this parameter to 0,
indicating that the T/R spacing
supported by the ODU is used.
l A valid T/R spacing value is
determined by an ODU itself. Set T/R
Spacing (MHz) according to the
technical specifications of an ODU.
l Set T/R Spacing (MHz) consistently
for ODUs at both ends of a radio link.

ATPC Selected Deselected l This parameter specifies whether

Deselected automatic transmit power control
(ATPC) needs to be enabled.
l When ATPC is selected, if the RSL is 2
dB or more than 2 dB less than the
value halfway between the upper and
lower ATPC thresholds, the receiver
instructs the transmitter to increase
transmit power so that the RSL does
not deviate more than 2 dB from the
halfway value; if the RSL is 2 dB or
more than 2 dB greater than the value
halfway between the upper and lower
ATPC thresholds, the receiver instructs
the transmitter to decrease transmit
power so that the RSL does not deviate
more than 2 dB from the halfway value.
l Set ATPC consistently at both ends of a
radio link.
l It is recommended that you deselect
ATPC for NEs in areas where fast
fading is severe.
l During the commissioning process,
deselected this parameter to ensure that
the transmit power is not changed.
After commissioning, reset this
parameter.
ATPC Upper - -45.0 l Set the central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold to the expected receive
ATPC Lower - -70.0 power.
Threshold(dBm)
l It is recommended that you set ATPC
Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
value between the ATPC upper
threshold and the ATPC lower
threshold and 10 dB.
TX Power (dBm) - - This parameter displays the transmit power

of an ODU/RFU.

Actual TX Power - - l This parameter displays the actual

(dBm) 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 - - This parameter specifies the receive power

Received (dBm) of an ODU/RFU.
Actual RX Power - - This parameter displays the actual receive

(dBm) power of an ODU/RFU.
TX Status - - This parameter displays the transmit status

of an ODU/RFU.
Equipment Information Parameters

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.

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.

Protection Type 1+1 Protection 1+1 Protection l This parameter specifies the
1:N Protection protection type of the linear MSP
group.
l In the case of 1+1 linear MSP, one
working channel and one protection
channel are required. When the
working channel fails, the service is
switched from the working channel to
the protection channel.
l In the case of 1:N linear MSP, N
working channels and one protection
channel are required. Normal services
are transmitted on the working
channels and extra services are
transmitted on the protection channel.
When one working channel fails, the
services are switched from this
working channel to the protection
channel, and the extra services are
interrupted.
l If extra services need to be transmitted
or several working channels are
required, select 1:N Protection.
Switching Mode Single-Ended Single-Ended l This parameter specifies the switching

Switching Switching (1+1 mode of the linear MSP.
Dual-Ended Protection) l In single-ended mode, the switching
Switching Dual-Ended occurs only at one end and the state of
Switching (1:N the other end remains unchanged.
Protection) l In dual-ended mode, the switching
occurs at both ends at the same time.
l If the linear MSP type is set to 1:N
Protection, Switching Mode can be
set to Dual-Ended Switching only.

Revertive Mode Non-Revertive Non-Revertive (1+1 l This parameter specifies the revertive
Revertive Protection) mode of the linear MSP.
Revertive (1:N l When this parameter is set to
Protection) Revertive, the NE that is in the
switching state releases the switching
and enables the former working
channel to return to the normal state
some time after the former working
Revertive, 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.
l It is recommended that you use the
default value.
SD Switching Enabled Enabled l This parameter indicates or specifies

Disabled whether the switching at the SD alarm
of the linear MSP is enabled.
l When this parameter is set to
Enabled, the B2_SD alarm is
considered as a switching condition.
Protocol Type New Protocol New Protocol l The new protocol is more mature, and
Restructure the restructure protocol complies with
Protocol the standard. It is recommended that
you use the new protocol.
l You must ensure that the
interconnected NEs run the protocols
of the same type.


Select Mapping Direction West Working Unit West Working Unit This parameter
West Protection Unit specifies the
mapping direction of
the linear MSP.
Available Boards - - l This parameter

specifies the
mapping board
and port in the
mapping
direction.
l If the protection
type is set to 1+1
Protection, only
one line port can
be mapped as
West Working
Unit.
l Only one line
port can be
mapped as West
Protection Unit.
l The line port
mapped as West
Protection Unit
and the line port
mapped as West
Working Unit
should be
configured for
different boards if
possible.
Mapped 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.

Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS


Protection Type - - This parameter indicates the protection

type of the linear MSP group.
Switching Mode Single-Ended - l This parameter indicates or specifies

Switching the switching mode of the linear MSP.
Dual-Ended l In single-ended mode, the switching
Switching occurs only at one end and the state of
the other end remains unchanged.
l In dual-ended mode, the switching
Protection, Switching Mode can be
set to Dual-Ended Switching only.
Revertive Mode Non-Revertive - l This parameter indicates or specifies

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
occurs even though the former working
Protection, Revertive Mode can be set
to Revertive only.


the WTR time.
default value.
SD Switching Enabled - l This parameter indicates or specifies

Disabled whether the reverse switching function
is enabled.
the B2_SD alarm is considered as a
Protocol Type New Protocol - l You must ensure that the

Restructure interconnected NEs run the protocols of
Protocol the same type.
l The new protocol is more mature, and
the restructure protocol complies with
the standard. It is recommended that
Protocol Status - - This parameter indicates the protocol

status of the linear MSP.
Protection Subnet - - This parameter displays the protection

subnet where the MS protection is
configured.

Unit Type - - This parameter indicates that which of the

units, namely, the west protection unit or
the west working unit, is currently in the
protection status.
Unit Name-West - - This parameter indicates the west

protection unit and the west working unit
of the linear MSP.

Switching Status- - - This parameter indicates the switching

West status of the line.
Protected Unit - - This parameter indicates the working

channel protected by the current protection
channel.
Remote End/Local - - When Switching Mode is set to Dual-

End Ended Switching, the central office end
that issues the switching command is
displayed.
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.

Protection Type 1:N Protection 1:N Protection Specifies the protection type of a packet-
based linear MSP group. Packet-based
linear MSP groups support only 1:1
protection.
Switching Mode Dual-Ended Dual-Ended l Specifies the switching mode of the

Switching Switching packet-based linear MSP.
occurs at both ends simultaneously.
Revertive Mode Revertive Revertive l Specifies the revertive mode of the

packet-based linear MSP.
and enables the original working
channel to change to the normal state
some time after the original working

WTR Time(s) 300-720 600 l Specifies the WTR time.

l When the time after the original
SD Switching Enabled Enabled l Specifies whether an SD alarm of the

Disabled packet-based linear MSP can trigger
switching. You can set the parameter
value manually.
a B2_SD alarm is considered as a
Protocol Type New Protocol New Protocol l The new protocol is more mature, and
Restructure the restructured protocol complies with
Protocol the standard. It is recommended that
l Ensure that the interconnected NEs run
the protocols of the same type.
SD/SF PRI Low priority Low priority l Specifies whether an SD/SF alarm is a
Switching Tag High priority high-priority or low-priority switching
condition. You can set the parameter
value manually.
l When this parameter is set to High
priority, bits 1 to 4 of the K1 byte uses
1101 to indicate a high-priority SF
switching request and 1011 to indicates
a high-priority SD switching request.
l When this parameter is set to Low
priority, bits 1 to 4 of the K1 byte uses
1100 to indicate a low-priority SF
switching request and 1010 to indicates
a low-priority SD switching request.
Switching Mode Indication Indication Specifies whether the switching mode

Indication Not indication indication function is enabled for packet-
based linear MSP. You can set the
parameter value manually.

Slot Mapping Parameters

Select Mapping West Working Unit West Working Unit Specifies the mapping direction of the
Direction West Protection linear MSP. You can set the parameter
Unit value manually.
Available Boards - - l Specifies the mapping board and port

in the mapping direction. You can set
the parameter value manually.
l Only one line port can be mapped as
West Protection Unit.
l The line port mapped as West
Protection Unit and the line port
mapped as West Working Unit need to
be configured on different boards if
possible.
Mapped 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 > Packet-

Protection Group - - Specifies the ID of the protection group.

ID
Protection Type - - Specifies the protection type of a packet-

based linear MSP group.
Switching Mode Dual-Ended - l Specifies the switching mode of the

Switching packet-based linear MSP. You can set

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 - l Specifies whether the reverse switching

Disabled function is enabled. You can set the
a B2_SD alarm is considered as a
Protocol Type New Protocol - l You must ensure that the

Restructure interconnected NEs run the protocols of
Protocol the same type.
l The new protocol is more mature, and
the restructured protocol complies with
the standard. It is recommended that
Protocol Status - - Specifies the protocol status of a packet-

based linear MSP.

SD/SF PRI High priority Low priority l Specifies whether an SD/SF alarm is a
Switching Tag Low priority high-priority or low-priority switching
condition. You can set the parameter
value manually.
l When SD/SF PRI Switching Tag is set
to High priority, bits 1 to 4 of the K1
byte uses 1101 to indicate a high-
priority SF switching request and 1011
to indicates a high-priority SD
switching request.
l When SD/SF PRI Switching Tag is set
to Low priority, bits 1 to 4 of the K1
byte uses 1100 to indicate a low-
priority SF switching request and 1010
to indicates a low-priority SD
switching request.
Switching Mode Indication Indication Specifies whether the switching mode

Indication Non-indication indication function is enabled for packet-
based linear MSP. You can set the
Slot Mapping Parameters

Unit Type - - Specifies which of the units, namely, the

west protection unit or the west working
unit, is currently in the protection status.
Unit Name-West - - Specifies the west protection unit and the

west working unit of a packet-based linear
MSP.
Switching Status- - - Specifies the switching status of the line.

West
Protected Unit - - Specifies the working channel protected by

the current protection channel.
Remote End/Local - - When Switching Mode is set to Dual-

End Ended Switching, the central office end
that issues the switching command is
displayed.

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.

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 2-fiber Specifies the ring MSP protection

Bidirectional Bidirectional type. The parameter value is always
Multiplex Multiplex 2-fiber Bidirectional Multiplex
Section Section Section.
Local Node ID 0-15 0 Specifies the node ID that the local

NE uses on the MSP ring. Node IDs
of NEs on the ring must be different
from each other.
West Node ID 0-15 0 Specifies the node ID of the NE that

is connected to the west line board on
the local NE. The parameter value
must be different from Local Node.
East Node ID 0-15 0 Specifies the node ID of the NE that

is connected to the east line board on
the local NE. The parameter value
must be different from Local Node.

WTR Time(s) 300-720 600 l Specifies the WTR time for the
local NE. After the working
channel recovers, services are
switched back from the protection
channel to the working channel
when the WTR time expires.
l Prevents frequent service
switches. The default value is
recommended.
SD Switching Enabled Enabled l Specifies whether the B2_SD

Disabled 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 New Protocol l The new MSP protocol is
Restructure supported from an early stage,
Protocol and is still widely used.
l Compared with the new MSP
protocol, the restructure MSP
protocol is optimized and more
stable, incorporating better
protection measures.
l The new MSP protocol has higher
technology maturity than the
restructure MSP protocol, and
therefore is generally
recommended. The restructure
MSP protocol, however, features
higher standard compliance than
the new MSP protocol. Therefore,
the restructure MSP protocol is
used when the new MSP protocol
fails to support interconnection
between Huawei RTN equipment
and third-party equipment.
l Two interconnected NEs must use
the same MSP protocol type.

Parameters for Slot Mapping Settings

Select Mapping West Line 1 West Line 1 Specifies the mapping direction of a
Direction East Line 1 member in a ring MSP protection group.
Available Boards - - l Specifies the mapping board and port

in the mapping direction.
l It is recommended that you map the
SL4D-1 port to West Line 1 and map
the SL4D-2 port to East Line 1.
Mapped 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 >

Protection Group - - Displays the ID of a ring MSP protection

ID group.
Level - - Displays the transmission level of ring

MSP services. The parameter value is
always STM-4.
Protection Type - - Displays the ring MSP protection type.

The parameter value is always 2-fiber
Bidirectional Multiplex Section.
Local Node - - Displays the node ID that the local NE

uses on the MSP ring.
West Node - - Displays the node ID of the NE that is

connected to the west line board on the
local NE.

East Node - - Displays the node ID of the NE that is

connected to the east line board on the
local NE.
WTR Time(s) - - Displays the wait-to-restore (WTR) time

- of the local NE. After the working channel
is restored, revertive switching occurs
when the WTR time expires.
SD Enable - - Displays whether SD Enable is Enabled

for the local NE. If SD Enable is Enabled,
the B2_SD alarm is regarded as a
switching trigger condition.
Protocol Type - - l Displays the protocol type used by the

local NE.
l The new MSP protocol is supported
from an early stage, and is still widely
used.
l Compared with the new MSP protocol,
the restructure MSP protocol is
optimized and more stable,
incorporating better protection
measures.
Protocol Status - - Displays the current protocol status of the

local NE.
Protection Subnet - - Displays the current protection subnet.
Parameters for Slot Mapping Relationships

Mapping Direction - - Displays the direction of an MSP ring.
Slot Mapping - - Displays the slot mapping relationship in a

ring MSP protection group.
Switching Status - - Displays the current switching status of the

local NE.
B.4 TDM Service Parameters

This section describes the parameters related to TDM services.

B.4.1 Parameter Description: SDH/PDH Service

Configuration_Creation
This parameter describes the parameters that are used for creating point-to-point cross-
connections.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
SDH/PDH Service Management from the Function Tree.
2. Click Options to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click Create.
Parameters
Level VC12 VC12 l This parameter specifies the level of the

VC3 service to be created.
VC4 l If the service is an E1 service or a data
service that is bound with VC-12
channels, set this parameter to VC12.
l If the service is a data service that is
bound with VC-3 channels, set this
parameter to VC3.
l If all the services on a VC-4 channel
pass through the NE, set this parameter
to VC4.
Direction Bidirectional Bidirectional l When this parameter is set to

Unidirectional Unidirectional, create only the cross-
connections from the service source to
the service sink.
Bidirectional, create the cross-
connections from the service source to
the service sink and the cross-
connections from the service sink to the
service source.
l In normal cases, it is recommended that
you set this parameter to Bidirectional.
Source Slot - - This parameter specifies the slot of the

service source.

Source VC4 VC4–1 VC4–1 l This parameter specifies the number of

VC4–2 the VC-4 channel where the service
source is located.
l This parameter cannot be set when
Source Slot is set to the slot of the
tributary board.
Source Timeslot - - l This parameter indicates the timeslot

Range(e.g.1,3-6) range of the service source.
l This parameter can be set to a number
or several numbers. When setting this
parameter to several numbers, use the
comma (,) to separate the discrete
numbers, or use the endash (-) to
represent a consecutive number. For
example, the numbers 1, and 3-6
indicate 1, 3, 4, 5, and 6.
Sink Slot - - This parameter specifies the slot of the

service sink.
Sink VC4 VC4–1 VC4–1 l This parameter specifies the number of

sink is located.
Sink Slot is set to the slot of the
tributary board.
Sink Timeslot - - l This parameter specifies the timeslot

Range(e.g.1,3-6) range of the service sink.

E1 Priority High - l This parameter specifies the priority of

Low an E1 service. This parameter is
available only if the E1 priority
None function is enabled for the ports
configured in the cross-connections.
l If E1 Priority is set to High,
transmission of the E1 service is
ensured in any modulation scheme.
l If E1 Priority is set to Low,
ensured only in full-capacity
modulation scheme
l If the service priority is not specified
during service creation, E1 Priority is
None. In this case, the E1 priority of a
service needs to be changed after the
service is created.
Activate Yes Yes l This parameter specifies whether to

Immediately No immediately activate the configured
service.
l To immediately deliver the configured
SDH service to the NE, set this
parameter to Yes.

Configuration_SNCP Service Creation
This topic describes the parameters that are used for creating SNCP services.
Navigation Path
SDH/PDH Service Management from the Function Tree.
2. Click Options to change the VC-12 timeslot numbering policy used by the cross-
connection.
3. Click Create SNCP Service.

Service Type SNCP SNCP This parameter indicates that the type of
the service to be created is SNCP.

Direction Bidirectional Bidirectional l When this parameter is set to

Unidirectional Unidirectional, create only the cross-
connections from the SNCP service
source to the SNCP service sink.
Bidirectional, create the cross-
source to the service sink and the cross-
sink to the service source.
Level VC12 VC12 l This parameter specifies the level of the

VC3 SCNP service to be created.
VC4 l If the service is an E1 service or a data
service that is bound with VC-12
channels, set this parameter to VC12.
l If the service is a data service that is
bound with VC-3 channels, set this
parameter to VC3.
l If all the services on a VC-4 channel
pass through the NE, set this parameter
to VC4.

Hold-off 0 to 100 0 l This parameter specifies the duration of

Time(100ms) the hold-off time.
l When a line is faulty, SNCP switching
can be performed on the NE after a
delay of time to prevent the situation
where the NE performs SNCP
switching and other protection
switching at the same time.
l Hold-off Time(100ms) is generally set
to prevent SNCP protection switching,
when SNCP works with N+1
protection. Hold-off Time(100ms)
must be longer than the switching time
of any protection mode that works with
SNCP. Generally, Hold-off
Time(100ms) is set to 200 ms.
l When SNCP works with 1+1 FD/SD,
trigger conditions for HSM switching
or SNCP switching trigger HSM
switching but do not trigger SNCP
switching. Therefore, Hold-off
Time(100ms) does not need to be set in
this case.
l The switching time of 1+1 HSB/FD/SD
protection is much longer than that of
SNCP. Therefore, to shorten service
interruptions, it is recommended that
you do not set Hold-off Time(100ms)
when SNCP works with 1+1
HSB/FD/SD protection.
l If only the SNCP scheme is available, it
is recommended that you set the hold-
off time to 0.
Revertive Mode Non-Revertive Non-Revertive l This parameter specifies whether to

Revertive switch the service to the original
working channel after the fault is
rectified.
l If this parameter is set to Revertive, the
service is switched from the protection
channel to the original working
channel. If this parameter is set to Non-
Revertive, the service is not switched
from the protection channel to the
original working channel.

WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
default value.

service source.
Source VC4 VC4–1 VC4–1 l This parameter specifies the number of

source is located.
tributary board.


service sink.
Sink VC4 VC4–1 VC4–1 l This parameter specifies the number of

sink is located.
tributary board.


Configure SNCP Selected Deselected l After the Configure SNCP Tangent

Tangent Ring Deselected Ring checkbox is selected, you can
quickly configure the SNCP service for
the SNCP ring tangent point.
you do not select this checkbox.
Activate Selected Selected l This parameter specifies whether to

Immediately Deselected immediately activate the configured
SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.

Configuration_Converting Normal Services Into SNCP Services
This topic describes the parameters that are used for converting normal services into SNCP
services.
Navigation Path
SDH/PDH Service Configuration from the Function Tree.
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
3. Select the unidirectional service. Right-click the selected service and choose Convert to
SNCP Service from the shortcut menu.


Service Type SNCP SNCP This parameter indicates that the type of
the service to be created is SNCP.
Direction Unidirectional - This parameter indicates the direction of

the SNCP service.
Level - - This parameter indicates the level of the

SNCP service.
Hold-off 0 to 100 0 l This parameter specifies the duration of

Time(100ms) the hold-off time.
l When a line is faulty, SNCP switching
can be performed on the NE after a
delay of time to prevent the situation
where the NE performs SNCP
switching and other protection
switching at the same time.
l Hold-off Time(100ms) is generally set
to prevent SNCP protection switching,
when SNCP works with N+1
protection. Hold-off Time(100ms)
must be longer than the switching time
of any protection mode that works with
SNCP. Generally, Hold-off
Time(100ms) is set to 200 ms.
l When SNCP works with 1+1 FD/SD,
trigger conditions for HSM switching
or SNCP switching trigger HSM
switching but do not trigger SNCP
switching. Therefore, Hold-off
Time(100ms) does not need to be set in
this case.
l The switching time of 1+1 HSB/FD/SD
protection is much longer than that of
SNCP. Therefore, to shorten service
interruptions, it is recommended that
you do not set Hold-off Time(100ms)
l If only the SNCP scheme is available, it
is recommended that you set the hold-
off time to 0.

Revertive Mode Non-Revertive Non-Revertive l This parameter specifies whether to

Revertive switch the service to the original
working channel after the fault is
rectified. If this parameter is set to
"Revertive", the service is switched
l If this parameter is set to Revertive, the
service is switched from the protection
channel to the original working
channel. If this parameter is set to Non-
Revertive, the service is not switched
WTR Time(s) 300 to 720 600 l This parameter specifies the WTR time.
default value.

service source.
Source VC4 - - l This parameter specifies the number of

the VC-4 channel where the service
source is located.
tributary board.


service sink.

Sink VC4 - - l This parameter specifies the number of

the VC-4 channel where the service
sink is located.
tributary board.

Configure SNCP - - After the Configure SNCP Tangent Ring

Tangent Ring checkbox is selected, you can quickly
configure the SNCP service for the SNCP
ring tangent point.
Activate - - l This parameter specifies whether to

Immediately immediately activate the configured
SNCP service.
l After the Activate Immediately
checkbox is selected, you can
immediately activate the created SNCP
service.
B.4.4 Parameter Description: SDH/PDH Service Configuration

This topic describes the parameters that are used for configuring SDH services (namely,
configuring cross-connections).
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH/PDH

Cross-Connection Parameters
Parameter Value Range Def Description
ault
Val
ue
Level - - This parameter indicates the level of the service.
Source Slot - - This parameter indicates the slot of the service source.
Source Timeslot/ - - This parameter indicates the timeslot or timeslot range of the
Path service source.
Sink Slot - - This parameter indicates the slot of the source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or timeslot range of the
Path service sink.
Activation Yes - This parameter indicates whether to activate the service.

Status No
Bound Group - - OptiX RTN 900 does not support this parameter.
Number
Lockout Status - - OptiX RTN 900 does not support this parameter.
Trail Name - - OptiX RTN 900 does not support this parameter.
Schedule No. - - OptiX RTN 900 does not support this parameter.
E1 Priority High - l This parameter specifies the priority of an E1 service. This

Low parameter is available only if the E1 priority function is
enabled for the ports configured in the cross-connections.
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

Level - - This parameter indicates the level of the

service.
Source Slot - - This parameter indicates the slot of the

service source.

Source Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service source.
Sink Slot - - This parameter indicates the slot of the

source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or

Path timeslot range of the service sink.
Lockout Status - - OptiX RTN 900 does not support this

parameter.
Trail Name - - OptiX RTN 900 does not support this

parameter.
Schedule No. - - OptiX RTN 900 does not support this

parameter.
E1 Priority High - l This parameter specifies the priority of

Low an E1 service. This parameter is
available only if the E1 priority
None function is enabled for the ports
configured in the cross-connections.
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


Value
Service Type - - This parameter indicates the

service protection type of the
protection group.
Protection Group ID - - Displays the ID of the protection

group.
Source - - This parameter indicates the

timeslots where the working
service source and protection
service source of the protection
group are located.
Sink - - This parameter indicates the

timeslots where the working
service sink and protection service
sink of the protection group are
located.
Level - - Displays the service level.
Current Status - - This parameter indicates the

current switching mode and
switching status of the services of
Revertive Mode Revertive - l This parameter indicates or

Non-Revertive specifies the revertive mode of
the service.
l This parameter determines
whether to switch the service
from the protection channel to
the original working channel
after the fault is rectified.
l If this parameter is set to
Revertive, the service is
switched from the protection
channel to the original
working channel. If this
parameter is set to Non-
Revertive, the service is not
switched from the protection
channel to the original
working channel.
this parameter to Revertive.


Value
WTR Time(s) 300 to 720 - l This parameter indicates or

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.


Value
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 hold-off time
to 0.


Value
Switching Condition - Null l This parameter indicates or

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.

NOTE
when Integrated IP microwave links construct an E1 SNCP ring together with SDH/PDH microwave links
provided by IF1 boards, SDH microwave links provided by ISU2/ISX2/ISV3/ISM6 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

Port - - Displays the slot ID of the IF board and

the ID of the IF port.
High Channel - - Displays the higher order path number of

the IF board.
Low Channel - - Displays the lower order path number of

the IF board.
Insert E1_AIS to Enable Auto l If Insert E1_AIS to TU_AIS is set to

TU_AIS Disable Enable, a TU_AIS alarm is inserted to
an E1 channel upon detection of an
Auto E1_AIS alarm in the channel.
l If Insert E1_AIS to TU_AIS is set to
Disable, a TU_AIS alarm is not
inserted to an E1 channel upon
detection of an E1_AIS alarm in the
channel.
l If Insert E1_AIS to TU_AIS is set to
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.
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
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.
Navigation Path
In the NE Explorer, select the MP1 logical board from the Object Tree and then choose
Configuration > Port Mode Configuration from the Function Tree.

Port Name - - Displays the port name.
Service Mode CES PDH Specifies the working

PDH mode of a PDH port.
l The value PDH
indicates that the port
transmits Native E1
services as a common
PDH port.
l The value CES
indicates that the port
transmits services as a
Smart E1 port.
B.5.2 PDH Port Parameters

This topic describes the parameters that are related to PDH ports supported by Smart E1
interface boards.
B.5.2.1 Parameter Description: PDH Ports_Basic Attributes

This topic describes the parameters that are related to the basic attributes of PDH ports.

Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration >

NOTE
Before changing Port Mode for a port enabled with inband DCN, disable inband DCN.
Port - - Displays the ID of a

service port.
Name - - Specifies or displays the

customized port name.
Port Mode Layer 1 Layer 3 l Specifies the working

Layer 2 mode of a PDH port.
Layer 3 l When this parameter
is set to Layer 1, the
port can transmit
TDM signals. A port
can transmit CES and
serial services only if
Layer 1.
l When this parameter
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.
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.

NOTE
Before changing Frame Format and Frame Mode for a port enabled with inband DCN, disable inband
DCN.
Port - - Displays the name of a

service port.

Frame Format Unframe CRC-4 Multiframe l Specifies the frame

Double Frame format.
CRC-4 Multiframe l If a CES service uses
the emulation mode of
CESoPSN, this
parameter can assume
the value CRC-4
Multiframe or
Double Frame. The
value CRC-4
Multiframe is
recommended.
l If a CES service uses
the emulation mode of
SAToP, this parameter
needs to assume the
value Unframe.
l The value of Frame
Format must be the
same at the local and
opposite ends.
Line Encoding Format - - Displays the line

encoding format. The
parameter value is always
HDB3.
Re-timing Mode Master Mode Master Mode l Master Mode: The

Slave Mode system clock is used
as the output clock of
Line Clock Mode services. The master
mode is the re-timing
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

Loopback Mode Non-Loopback Non-Loopback l Specifies the loopback

Inloop status for a port.
Outloop l Non-Loopback
indicates that
loopbacks are
canceled or not
performed.
l Inloop indicates that
the signals that need
to be transmitted to
the opposite end are
looped back.
l Outloop indicates that
the received signals
are looped back.
l This function is used
for fault locating for
the PDH ports. This
function affects
services over related
ports. Therefore,
exercise precautions
before starting this
function.
l Generally, this
parameter is set to
Non-Loopback.
Impedance - - Displays the port

impedance.

Frame Mode 30(ATM,ML-PPP) - l 30 timeslots: In an E1

31(ATM,CES,ML-PPP) frame format,
timeslots 1 to 15 and
17 to 31 are used to
transmit service data,
and timeslot 16 is
used to transmit
signaling.
l 31 timeslots: In an E1
frame format,
timeslots 1 to 31 are
used to transmit
service data.
l This parameter is
unavailable if Frame
Format is Unframe.
l The port frame modes
need to be the same at
the local and opposite
ends.
CES Encapsulation NULL NULL l This parameter

Clock Mode Line Clock Mode specifies the source of
clock signals
transmitted by CES
services.
l When CES services
do not transmit any
clock signals, set this
parameter to NULL.
l When an E1 port
functions as the
master in the CES
ACR solution, set this
parameter to Line
Clock Mode. The
CES services transmit
clock signals sourced
from the E1 line.
B.5.3 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the packet plane.

B.5.3.1 Parameter Description: Ethernet Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of an Ethernet
interface.
Navigation Path

Port - - Displays the port name.
Name - - Specifies the port name.
Enable Port Enabled Enabled l Specifies whether an

Disabled Ethernet port is
enabled. An Ethernet
port can receive,
process, and forward
Ethernet services only
if this parameter is set
to Enabled.
l Set this parameter
according to the
Port Mode Layer 2 Layer 2 l Specifies the level of

Layer 3 services that a port
carries.
Layer Mix
l If Port Mode is
Layer 2, the port can
carry native Ethernet
services.
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.

Encapsulation Type Null - l This parameter

802.1Q specifies the method
of the port to process
QinQ 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
IEEE 802.1ad QinQ
standard.

Working Mode Auto-Negotiation Auto-Negotiation l The Ethernet ports of

10M Half-Duplex different types
support different
10M Full-Duplex Working Mode. For
100M Half-Duplex details, see the IDU
100M Full-Duplex Hardware
Description.
1000M Full-Duplex
l When the equipment
1000M Half-Duplex
on the opposite side
works in auto-
negotiation mode, set
the Working Mode
of the equipment on
the local side to Auto-
Negotiation.
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 46 to 9600 1522 The value of Max Frame

(bytes) Length(byte) should be
greater than the length of
any frame to be
transported.
NOTE
This parameter does not
take effect for L3VPN
services.

Auto-Negotiation 10M Half-Duplex FE: 100M Full-Duplex l This parameter

Ability 10M Full-Duplex GE: 1000M Full-Duplex specifies the optimal
working mode that
100M Half-Duplex can be automatically
100M Full-Duplex negotiated.
1000M Full-Duplex l Auto-Negotiation
1000M Half-Duplex Ability is valid only
when Working Mode
is set to Auto-
Negotiation.
Logical Port Attribute Optical Port - l This parameter

Electrical Port specifies the type of
the SFP module that
an Ethernet port can
house.
l If the specified and
actual SFP module
types are different, the
LASER_MOD_ERR
alarm is reported.
l If an Ethernet port is
shared by an SFP
optical module and an
RJ45 electrical
connector, this
parameter specifies
the port type of the
Ethernet port.
Physical Port Attribute - - This parameter indicates

the physical type of an
Ethernet port.
Running Status - - This parameter indicates

the status of the Ethernet
link.
Traffic Policing Status Enabled Disabled Only after this parameter

Disabled is set to Enabled for an
Ethernet port, the
Ethernet port is able to
report the
ETH_NO_FLOW alarm.

Traffic Policing Period 1 to 30 15 An Ethernet port reports

(min) an ETH_NO_FLOW
alarm when the following
conditions are met:
l Both Enable Port
and Traffic
Monitoring Status
are set to Enabled.
l The Ethernet link is
working properly.
l The Ethernet port
bears no traffic for
Traffic Monitoring
Period (min).
B.5.3.2 Parameter Description: Ethernet Interface_Flow Control

This topic describes the parameters that are related to flow control.
Navigation Path
2. Click the Flow Control tab.

Port - - This parameter indicates

the port name.

Non-Autonegotiation Disabled Disabled l Non-Autonegotiation

Flow Control Mode Enable Symmetric Flow Flow Control Mode
Control is valid only when
Working Mode is not
Send Only set to Auto-
Receive Only Negotiation.
l Non-Autonegotiation
Flow Control Mode
of the equipment on
the local side must be
consistent with the
non-autonegotiation
flow control mode of
opposite side
l OptiX RTN 900
supports only two
non-auto-negotiation
flow control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
l An EM6D board
supports only two
non-auto-negotiation
flow control modes,
namely, Disabled
mode and Receive
Only mode.

Auto-Negotiation Flow Disabled Disabled l Auto-Negotiation

Control Mode Enable Symmetric Flow Flow Control Mode
Control is valid only when
Working Mode is set
Enable Dissymmetric to Auto-Negotiation.
Flow Control
l Auto-Negotiation
Enable Symmetric/ Flow Control Mode
Dissymmetric Flow of the equipment on
Control the local side must be
consistent with the
auto-negotiation flow
control mode of the
equipment on the
opposite side
l OptiX RTN 900
supports only two
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
l An EM6D board
supports only two
control modes,
namely, Disabled
mode and Enable
Symmetric/
Dissymmetric Flow
Control mode.
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
2. Click the Layer 2 Attributes tab.



the port name.
QinQ Type Domain - - l When Encapsulation

Type in the General
Attributes tab page is
set to QinQ, you need
to set QinQ Type
Domain. The default
value is 88A8.
l When Encapsulation
Type in the General
Attributes tab page is
set to Null or 802.1Q,
you cannot set QinQ
Type Domain. In this
case, QinQ Type
Domain is displayed
as FFFF and cannot
be changed.
TAG Tag Aware Tag Aware l If all the accessed

Access services are frames
with the VLAN tag
Hybrid (tagged frames), set
TAG to Tag Aware.
l If all the accessed
services are frames
without the VLAN
tag (untagged
frames), set TAG to
Access.
l If the accessed
services contain
tagged frames and
untagged frames, set
TAG to Hybrid.
Default VLAN ID 1 to 4094 1 l Default VLAN ID is

valid only when TAG
is set to Access or
Hybrid.
VLAN Priority 0 to 7 0 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

NOTE
Layer 3 Attributes is valid only if Port Mode is set to Layer 3.
Enable Tunnel Disabled Enabled l If Enable Tunnel is

Enabled set Enabled, a port
identifies and
processes MPLS
labels.
l Enable Tunnel is
available if you set
Port Mode to Layer 3
in the General
Attributes tab.
Specify IP Address Manually Unspecified l Specifies the method

Unspecified of setting the IP
address of a port.
l The value
Unspecified indicates
that the IP addresses
do not need to be
configured.
l The value Manually
indicates that the IP
address of the port can
be manually
configured.

IP Address - 0.0.0.0 l Specifies the IP

address of a port.
l This parameter is
available when
Specify IP Address is
Manually.
l The IP addresses of
different ports on the
NE cannot be in the
same network
segment, but the IP
addresses of the ports
at both ends of the
MPLS tunnel must be
in the same network
segment.
IP Mask - 255.255.255.252 l Specifies the subnet

mask of a port.
l This parameter is
available when
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

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

Inloop 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.
l In normal
cases, it is
recommended
that you use
the default
value.
PHY Loopback Non-Loopback Non-Loopback l This

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

Disabled specifies whether
to enable loop
detection, which
is used to check
whether a loop
exists on the
port.
Loopback Port Block Enabled Disabled This parameter

Disabled indicates whether
to enable the
loop port
shutdown
function.
Egress PIR Bandwidth(kbit/s) - - This parameter

indicates the
egress PIR
bandwidth.
The NE does not
support this
parameter.

Broadcast Packet Suppression Disabled Disabled l When this

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

POE Disabled Disabled l If the PoE

Enabled port supports
auto-
Auto- negotiation
Negotiation 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
Auto-
Negotiation.
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 auto-
negotiation,
set this
parameter to
Enabled.
l If the PoE
port does not
support auto-
negotiation
and needs to
supply power
to an FO
device, set

this
parameter to
Enabled;
otherwise, set
this
parameter to
Disabled.
l Only the PoE
port on OptiX
RTN 905 2E
supports
auto-
negotiation.
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
Configuration > Interface Management > Serial Interface from the Function Tree.

Port - - Displays the name of the

port where a serial port is
configured.


Level - - l Specifies the serial

port level.
l 64K Timeslot: 64
kbit/s timeslots of E1
signals can be bound.
l VC12: E1s in a
channelized STM-1
can be used as MLPPP
links.
Used Port - - Displays the physical port

that carries the serial port.
High Channel - - Displays the high channel

Low Channel - - Displays the low channel

64K Timeslot - - Displays the timeslots

that a serial port occupies.
The timeslots can be
consecutive or not.
Port Mode Layer 2 - l Displays or specifies

Layer 3 the port mode.
l When a serial port
carries ATM services,
set this parameter to
Layer 2.
carries Multi-Link
Point-to-Point
Protocol (ML-PPP)
links, set this
parameter to Layer 3.
Encapsulation Type - - l Displays or specifies

the encapsulation type
of a serial port.
carries ATM services,
ATM.
carries ML-PPP links,
PPP.

Max Data Packet - - l This parameter is

Size(byte) 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
Configuration > Interface Management > Serial Interface from the Function Tree.
2. Click the New tab.

Port Number(e.g:1,3-6) - - Specifies the port number

of the serial port.
Name - - Specifies the customized

port name.
Level 64K Timeslot VC12 l Specifies the serial

VC12 port level.
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.

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

Retiming Mode System Clock System Clock l When this parameter

Line 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 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 - The channelized STM-1

interface board provides
Timeslot VC12-1 to VC12-63 - 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.
Object - - Displays each VC-12

path over a channelized
STM-1 port.

VC12 Frame Format Unframe CRC-4 Multiframe l Specifies the E1 frame

Double Frame format encapsulated
in VC-12s.
CRC-4 Multiframe
l In CESoPSN
emulation mode,
VC12 Frame Format
can be set to CRC-4
Multiframe or
Double Frame. It is
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.

Frame Mode 31 31 l If Frame Mode is set

30 to 30, timeslots 1 to
15 and 17 to 31 are
used to transmit
services and timeslot
16 is transmitted to
transmit signaling.
l If Frame Mode is set
to 31, timeslots 1-31
are used to transmit
services.
l Frame Mode is
unavailable when
VC12 Frame Format
is set to Unframe.
l If E1s are members in
an MP group, it is
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.

Loopback Mode Non-Loopback Non-Loopback l Displays or specifies

Inloop the port loopback
status.
Outloop
l Non-Loopback
indicates that the
loopback is canceled
or not performed.
l Inloop indicates that
the service signals
transmitted to the
opposite end are
looped back.
l Outloop indicates that
the received service
signals are looped
back.
l This function is used
for port fault locating.
This function affects
services on the related
port.
l Normally, this
parameter is set to
Non-Loopback.
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

Parameters
Port - - This parameter indicates the corresponding

IF port.
Name - - This parameter indicates or specifies the

Port Mode Layer 2 Layer 2 l This parameter specifies the level of

Layer 3 services that a port carries.
Layer Mix l If Port Mode is Layer 2, the port can
carry native Ethernet services.
l If Port Mode is Layer 3, the port can
carry tunnels.
l If Port Mode is Layer Mix, the port
can carry both tunnels and Native
Ethernet services.
Encapsulation Null 802.1Q l Encapsulation Type specifies the

Type 802.1Q method of the port to process the
received packets.
QinQ
l This parameter is valid only when Port
Mode is Layer 2.
l If Encapsulation Type is set to Null,
the port transparently transmits the
received packets.
l If Encapsulation Type is set to
802.1Q, the port identifies the packets
that comply with the IEEE 802.1Q
standard.
l If Encapsulation Type is set to QinQ,
the port identifies the packets that
comply with the IEEE 802.1ad QinQ
standard.
Traffic Policing Enabled Disabled Parameter is set to Enabled, the port is

Status Disabled qualified for capability to report alarms
ETH_NO_FLOW.
Traffic Policing 1 to 30 15 When port the following conditions are

Period(min) met, Alarms will be reported
ETH_NO_FLOW.
l Traffic Policing Status and Port
Status are set to Enabled.
l Link connection is normal.
l Traffic Policing Period(min) port no
flow.

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
Parameters for Layer 2 Attributes


IF port.
QinQ Type - - l When Encapsulation Type in the

Domain General Attributes tab page is set to
QinQ, you need to set QinQ Type
Domain. The default value is 88A8.
l When Encapsulation Type in the
General Attributes tab page is set to
Null or 802.1Q, you cannot set QinQ
Type Domain. In this case, QinQ Type
Domain is displayed as FFFF and
cannot be changed.
Tag Tag Aware Tag Aware l If all the accessed services are frames
Access that contain the VLAN tag (tagged
frames), set Tag to "Tag Aware".
Hybrid
l If all the accessed services are frames
that do not contain the VLAN tag
(untagged frames), set Tag to "Access".
l If the accessed services contain tagged
frames and untagged frames, set Tag to
"Hybrid".
NOTE
Tag specifies the TAG flag of a port. For details
about the TAG flags and associated frame-
processing methods, see Table B-2.

Default VLAN ID 1 to 4094 1 l Default VLAN ID is valid only when

TAG is set to Access or Hybrid.
NOTE
For details about the functions of Default
VLAN ID, see Table B-2.
VLAN Priority 0 0 l VLAN Priority is valid only when

1 TAG is set to Access or Hybrid.
NOTE
2
For details about the functions of VLAN
3 Priority, see Table B-2.
4
5
6
7
Table B-2 Data frame processing

Status Type of Data Processing Method
Frame
Tag Aware Access Hybrid
Ingress Port Tagged frame The port receives The port discards The port receives
the frame. the frame. the frame.
Untagged frame The port discards The port receives The port receives
the frame. the frame after the the frame after the
VLAN tag that VLAN tag that
corresponds to corresponds to
"Default VLAN "Default VLAN
ID" and "VLAN ID" and "VLAN
Priority" is added to Priority" is added to
the frame. the frame.

Status Type of Data Processing Method

Frame
Tag Aware Access Hybrid
Egress Port Tagged frame The port transmits The port strips the l If the VLAN ID
the frame. VLAN tag from the in the frame is
frame and then "Default VLAN
transmits the frame. ID", the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not "Default
VLAN ID", the
port directly
transmits the
frame.
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
Configuration > Interface Management > Microwave Interface from the Function
Tree.

Port - - Displays the corresponding

IF port.
Enable Tunnel Disabled Enabled l A port identifies and

Enabled processes MPLS labels,
if its Enable Tunnel is
set Enabled.
l Enable Tunnel is
available if you set Port
Mode to Layer 3 in the
General Attributes tab.

Specify IP Address Manually Unspecified l Specifies the method of

Unspecified setting the IP address of
a port.
l The value Unspecified
addresses do not need to
be configured for a port.
address of a port can be
manually configured.
IP Address - 0.0.0.0 l Specifies the IP address

for a port.
l This parameter is
available when Specify
IP Address is
Manually.
different ports on the
NE cannot be in the
same network segment,
but the IP addresses of
the ports at both ends of
the MPLS tunnel must
be in the same network
segment.
IP Mask - 255.255.255.252 l Specifies the subnet

mask of a port.
l This parameter is
available when Specify
IP Address is
Manually.
MTU(bytes) 46 to 9600 1500 Configure the traffic

maximum transmission
unit.
NOTE
Only for an RTN 905, RTN
910A, RTN 950A, or RTN
950 housing a CSHU/
CSHUA board, RTN 980
housing a CSHUN board
supports this parameter.
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
Parameters for Advanced Attributes


IF port.
Error Frame - - An Ethernet frame which has a CRC error

Discard Enabled will be discarded.
MAC Address - - This parameter indicates the MAC address

of the port.
Jitter Adjustment Disabled Disabled This parameter indicates or specifies

Enabled whether the jitter adjustment function is
enabled for ISU2/ISX2 boards.
When this parameter is set to Enabled,
jitter of services carried by ISU2/ISX2
boards can be decreased, but weighted
round robin (WRR) may be inaccurate.
This parameter generally takes the default
value.
OptiX RTN 905 does not support this
parameter.
Speed Disabled Disabled l If Speed Transmission at L2 is set to

Transmission at Enabled Enabled, the Layer-2 Ethernet packets
L2 transmitted at microwave ports will be
compressed to improve transmission
efficiency.
l The settings of Speed Transmission at
L2 must be the same at both ends of a
radio link.
Speed Disabled Disabled l If Speed Transmission at L3 is set to

Transmission at Enabled Enabled, the IP packets transmitted at
L3 microwave ports will be compressed to
improve transmission efficiency.
l The settings of Speed Transmission at
L3 must be the same at both ends of a
radio link.
Loopback Check Disabled Disabled This parameter specifies whether to enable

Enabled loop detection, which is used to check
whether a loop exists on the port.

Loopback Port Disabled Disabled This parameter indicates whether to enable

Block Enabled the automatic shut-down of looped ports.
Broadcast Packet Disabled Disabled l This parameter specifies whether to

Suppression Enabled 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.
l If Ethernet services are E-LAN
services, the recommended value is
Enabled.
Broadcast Packet 0 to 100 30 When the proportion of the broadcast

Suppression packets in the port bandwidth exceeds the
Threshold(%) value of this parameter, the received
broadcast packets are discarded. The value
of this parameter should be more than the
proportion of the broadcast packets in the
port bandwidth before the broadcast storm
occurs. In normal cases, this parameter is
set to default value.
NOTE
Assume that the bandwidth of an IF port is 400
Mbit/s.
Enable Switching Disabled Disabled Specifies whether to enable switching

Triggered by Bit Enabled triggered by bit errors.
Error
Switching Mode SF SF Specifies the mode of switching triggered

Triggered by Bit SD by bit errors.
Error
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
l Click the IF Attributes tab.

Parameters

IF interface.
Power Switch Open Open This parameter specifies whether to turn on

Close or off the ODU power switch for an ISM6
board.
NOTE
Only ISM6 boards support this parameter.
Alarm and Enabled Enabled RTN 905, RTN 910A, and ISV3/ISM6
Performance Disabled boards on RTN 980/RTN 980L/RTN
Report 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 are not reported.
IF Service Type Hybrid(Native Hybrid(Native This parameter displays or specifies the

E1+ETH) E1+ETH) type of services carried by the IF board.
Hybrid(Native NOTE
STM-1+ETH) For details about services that different types of
IF boards support, see the IDU Hardware
SDH Description.
Microwave Link 1 to 4094 1 l Radio Link ID indicates or specifies

ID 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 - - This parameter indicates the received ID of

Microwave Link the radio link.
ID

IF Port Loopback Non-Loopback Non-Loopback l This parameter indicates or specifies

Inloop the loopback status of the IF interface.
Outloop l Non-Loopback indicates that the
loopback is canceled or not performed.
l Inloop indicates that the IF signals
transmitted to the opposite end are
looped back.
l Outloop indicates that the received IF
signals are looped back.
l Generally, this parameter is set to Non-
Loopback.
2M Wayside Disabled Disabled l This parameter indicates or specifies

Enable Status Enabled whether the radio link transmits the
wayside E1 service.
l Only SDH radio supports wayside E1
services.
2M Wayside Input - - l This parameter indicates or specifies

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 Stop Stop l This parameter indicates or specifies

Status Start whether an IF port outputs 350 MHz
consecutive waves without modulation
signals.
l Generally, this parameter is set to Stop.

XPIC Enabled Enabled Enabled l This parameter indicates or specifies

Disabled whether the XPIC function of the XPIC
IF board is enabled.
l If the XPIC IF board does not perform
the XPIC function, XPIC Enabled
should be set to Disabled.
Enable IEEE-1588 Enabled Disabled l Enable IEEE-1588 Timeslot needs to

Timeslot Disabled be set consistently between two ends of
a radio link.
l If the NE needs to transmit IEEE
1588v2 packets, set Enable
IEEE-1588 Timeslot to Enabled. If
the NE does not need to transmit IEEE
1588v2 packets, set Enable
IEEE-1588 Timeslot to Disabled.
Running Mode IS2 IS3 l An IF port on an ISU2/ISX2 board can

IS3 - interconnect only with an IF port that
supports the IS2 mode.
IS6
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.

Parameters for Hybrid/AM Configuration

NOTE
For RTN 950/980, the IF1 board does not support Hybrid/AM configuration.

IF port.
IF Channel - - IF Channel Bandwidth indicates the

Bandwidth channel spacing of the corresponding radio
link. This parameter is set according to the
network plan.
AM Boost Status Disabled Disabled The adaptive modulation (AM) Boost

Enabled function increases the transmit power of an
ODU by 1 to 3 dB when IF boards are
working in AM full capacity mode. As a
result, the fading margin and working time
of radio links also increase.
NOTE
Only ISX2 board supports AM Boost function.
AM Status Disabled Disabled l When AM Status is set to Disabled,

Enabled 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 - - l This parameter is valid only when AM

of the Guarantee Status is set to Enabled.
AM Capacity l Modulation Mode of the Guarantee
AM Capacity specifies the lowest-
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.

Modulation Mode - - l This parameter is valid only when AM

of the Full AM Status is set to Enabled.
Capacity l Modulation Mode of the Full AM
Capacity specifies the highest-order
modulation scheme that the AM
function supports. This parameter is set
determined by the bandwidth of full
services and the availability of the radio
link that corresponds to this modulation
scheme.
Manually - - l This parameter specifies the

Specified modulation mode that the radio link
Modulation Mode 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 Disabled Disabled l This parameter specifies whether to

Priority Enabled enable the E1 priority function.
Status is set to Enabled and IF
E1+ETH).
Guarantee E1 - - l When Enable E1 Priority is set to

Capacity Disabled, this parameter specifies the
E1 service capacity of an IF port.
l When Enable E1 Priority is set to
Enabled, this parameter specifies the
E1 service capacity in Modulation
Mode of the Guarantee AM
Capacity.
l This parameter is valid when IF
Service Type is Hybrid(Native
E1+ETH).
Guarantee E1 - - Displays the E1 capacity range of the IF

Capacity Range board in guarantee capacity modulation
mode.

Data Service - - Displays the data service bandwidth of the

Bandwidth(Mbit/s IF board.
)
Full E1 Capacity - - l This parameter specifies the number of

transmitted E1 services in Modulation
Mode of the Full AM Capacity.
l This parameter is valid if Enable E1
Priority is set to Enabled.
l E1 service bandwidth in full capacity
mode ≤ Service bandwidth in full
capacity mode - Service bandwidth in
guarantee capacity mode + E1 service
bandwidth in guarantee capacity mode.
In addition, the number of E1 services
in full capacity modulation mode
should be 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 - - Displays the modulation mode at the

Modulation Mode transmit mode.
Receive-End - - Displays the modulation mode at the

Modulation Mode receive mode.
Guarantee AM - - Displays the guarantee AM service

Service capacity.
Capacity(Mbit/s)
Full AM Service - - Displays the full AM service capacity.

Capacity(Mbit/s)
Transmitted AM - - Displays the transmitted AM service

Service capacity.
Capacity(Mbit/s)
Received AM - - Displays the received AM service capacity.

Service
Capacity(Mbit/s)
E1 Capacity For - - Displays the number of configured high-

High Priority priority E1s.

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

IF interface.
ATPC Enable Disabled Disabled l This parameter specifies whether the

Status Enabled ATPC function is enabled.
l When this parameter is set to Enabled
and if the RSL at the receive end is 2
dB higher or lower than the central
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 - -45.0 l Set the central value between the ATPC
Threshold(dBm) upper threshold and the ATPC lower
threshold to a value for the expected
receive power.

ATPC Lower - -70.0 l It is recommended that you set ATPC

Threshold(dBm) Upper Threshold(dBm) to the sum of
the planned central value between the
ATPC upper threshold and the ATPC
lower threshold and 10 dB, and ATPC
Lower Threshold(dBm) to the
difference between the planned central
threshold and 10 dB.
l You can set the ATPC upper threshold
only when ATPC Automatic
Threshold(dBm) is set to Disabled.
ATPC Automatic Enabled Disabled l This parameter specifies whether the

Threshold Enable Disabled ATPC automatic threshold function is
Status enabled.
l If ATPC Automatic Threshold
Enable Status is set to Enabled, the
equipment automatically uses the preset
ATPC upper and lower thresholds
according to the work mode of the
radio link.
l If ATPC Automatic Threshold
Enable Status is set to Disabled, you
need to manually set ATPC Upper
Automatic Threshold(dBm) and
ATPC Lower Automatic
Threshold(dBm).
ATPC Upper - - l This parameter indicates that the

Automatic equipment automatically uses the preset
Threshold(dBm) ATPC upper and lower thresholds.
ATPC Lower - - l This parameter is valid only when

Automatic ATPC Automatic Threshold Enable
Threshold(dBm) Status is set to Enabled.
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
l Click the AM Advanced Attributes tab.

Parameters

IF interface.
Modulation Mode - - Displays the modulation schemes.
E1 Capacity/ - - l You can specify the number of E1s that

STM-1 Capacity can be transmitted in intermediate
modulation scheme, by setting the
advanced attributes correspondingly.
l Generally, it is recommended that this
parameter takes the default value. To
ensure that a specific number of E1s
can be transmitted in intermediate
modulation scheme, adjust the E1
capacity in each modulation scheme
according to the network planning
information.
l If the E1 priority function is enabled,
the maximum number of allowed E1
services in the current mode = Min
{[Bandwidth of the air interface in the
current mode - (Bandwidth for the
assured capacity - Assured E1 number
x 2Mbps)]/2Mbps, E1 number in the
highest-gain modulation mode}.
Data Service - - Displays the data service bandwidth.

Bandwidth(Mbit/s
)
B.5.7.4 Parameter Description: ATPC Adjustment Records

This topic describes the parameters that are related to ATPC adjustment records.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > ATPC Adjustment Records from the Function Tree.
Parameters
Port - - This parameter indicates the port for the

ATPC adjustment.

Event NO. - - This parameter indicates the number of the

ATPC adjustment event.
Adjustment Time - - This parameter indicates the time of the

ATPC adjustment.
Adjustment - - This parameter indicates the direction of

Direction the adjustment at the port.
Switchover - - This parameter indicates the switching

operation at the port.
Transmitted - - This parameter indicates the transmitted

Power(dBm) power of the port to be switched.
Received - - This parameter indicates the received

Power(dBm) 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.
l 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.
l Click the Radio Frequency Attributes tab.
Parameters
Board - - This parameter indicates the corresponding

RFU/RFU-SD/ODU.

Transmit - - l This parameter indicates or specifies

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/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/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 - - l This parameter indicates or specifies

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.

T/R - - l This parameter indicates or specifies

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 - - This parameter indicates the actual

Frequency(MHz) transmit frequency of the RFU/RFU-SD/
ODU.
Actual Receive - - This parameter indicates the actual receive

Frequency(MHz) frequency of the RFU/RFU-SD/ODU.
Actual T/R - - This parameter indicates the actual T/R

Spacing(MHz) spacing of the ODU.
NOTE
980L.
The range of - - This parameter indicates the working range

Transmit of the transmit frequency of the RFU/RFU-
frequency SD/ODU.
point(MHz)
The range of - - This parameter indicates the working range

Receive frequency of the receive frequency of the RFU/RFU-
point(MHz) SD.
NOTE
This parameter is supported by only OptiX
RTN 980L.

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.
l Click the Power Attributes tab.
Parameters

RFU/RFU-SD/ODU.
Maximum - - l Maximum Transmit Power(dBm) is

Transmit set according to the network plan. This
Power(dBm) 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).

Transmit - - l Transmit Power(dBm) is set

Power(dBm) 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/RFU-
SD/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.

Power to Be -90.0 to -20.0 -10.0 l Power to Be Received(dBm) is used to

Received(dBm) set the expected receive power of the
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/RFU-
SD/ODU is 3 dB lower than the power
expected to be received, the RFU/RFU-
SD/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 -90.0 to -20.0 - Specifies the SD power to be received of

Received(dBm) an RFU-SD.
NOTE
This parameter is supported only when the SD
combination function is enabled for OptiX RTN
980L.
TX High - - l If the value of the actual transmit power

Threshold(dBm) 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
of the RFU/RFU-SD/ODU is greater
than the preset value of TX High
Threshold(dBm) and the duration
when the value of the actual transmit
power of the RFU/RFU-SD/ODU is
greater than the preset value of TX

TX Low - - Low Threshold(dBm) in the

Threshold(dBm) performance events.
l If the value of the actual transmit power
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/RFU-
SD/ODU is greater than the preset
value of TX Low Threshold(dBm) in
the performance events.
l If the value of the actual transmit power
of the 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 - - l If the value of the actual receive power

Threshold(dBm) of the RFU/RFU-SD/ODU is lower
than the preset value of RX Low
SD/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/RFU-
SD/ODU is lower than the preset value
of RX High Threshold(dBm) in the
performance events.
l If the value of the actual receive power
than the preset value of RX Low
Threshold(dBm) and is lower than the
preset value of RX High
SD/ODU is Lower than the preset value
of RX High Threshold(dBm) in the
performance events.
l If the value of the actual receive power
than the preset value of RX High

RX Low - - Threshold(dBm), the system does not

Threshold(dBm) record it.
SD RX High -90.0 to -20.0 - Specifies the upper threshold of SD receive

Threshold(dBm) power of an RFU-SD.
NOTE
980L.
SD RX Low -90.0 to -20.0 - Specifies the lower threshold of SD receive

Threshold(dBm) power of an RFU-SD.
NOTE
980L.
Actual Transmit - - l This parameter indicates the actual

Power(dBm) 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 - - This parameter indicates the actual receive

Power(dBm) power of the RFU/RFU-SD/ODU.
Actual SD Receive - - Displays the actual SD receive power of an

Power(dBm) RFU-SD.
NOTE
980L.
Actual range of - - This parameter indicates the range of the

Power(dBm) actual transmit power of the RFU/RFU-
SD/ODU.
Transmission - - This parameter indicates the level of the

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.

Configuration > ODU Interface from the Function Tree.

l Click the Equipment Information tab.

Configuration > RF Interface from the Function Tree.
l Click the Equipment Information tab.
Parameters

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 - - This parameter indicates the T/R spacing

Spacing(MHz) of the ODU.
NOTE
980L.
Intermediate - - This parameter indicates the IF frequency

Frequency bandwidth of the RFU/RFU-SD/ODU.
Bandwidth (MHz)
IF Bandwidth - - Displays the IF bandwidth type.

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 - - This parameter indicates the level of the

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.

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 Click the Advanced Attributes tab.
Parameters
Board - - Indicates the corresponding ODU.
RF Loopback Non-Loopback Non-Loopback l This parameter indicates or specifies

Inloop the loopback status of the RF interface
of the ODU.
l Non-Loopback indicates that the
l Inloop indicates that the RF signals
looped back.
l RF Loopback function is used for fault
locating for the RF interfaces. The RF
Loopback function is used for
diagnosis and may affect the services
that are transmitted over the interfaces.
Hence, exercise caution before starting
this function.
l In normal cases, RF Loopback is set to
Non-Loopback.
Configure unmute unmute l Indicates or specifies the transmit status

Transmission mute of the ODU.
Status l If Configure Transmission Status is
set to mute, the transmitter of the ODU
does not work but can normally receive
microwave signals.
l If Configure Transmission Status is
set to unmute, the ODU can normally
transmit and receive microwave
signals.
l In normal cases, Configure
Transmission Status is set to unmute.
Actual - - Displays the ODU manufacturer

Transmission information.
Status

Factory - - Indicates the manufacturer information

Information about the ODU.
Alarm Threshold 10.0-35.0 - Specifies the alarm threshold for fade

for Fade Margin margin shortage for an ODU.
Shortage(dB)
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. Select the corresponding board from the Object Tree in the NE Explorer. Choose
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

SDH interface.
Optical Interface - - This parameter indicates or specifies the

Namea name of the optical interface.
Laser Switcha On On l This parameter indicates or specifies

Off the on/off state of the laser.
l This parameter is set for SDH optical
interfaces only.
l In normal cases, this parameter is set to
On.

Optical(Electrical) Non-Loopback Non-Loopback l This parameter indicates or specifies

Interface Inloop the loopback status on the SDH
Loopbacka interface.
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 Non-Loopback l This parameter indicates or specifies

Inloop the loopback status in the VC-4 path.
Outloop l Non-Loopback indicates that the
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.

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
Select the corresponding board from the Object Tree in the NE Explorer. Choose
Configuration > Automatic Laser Shutdown from the Function Tree.
Parameters
Optical Interface - - This parameter indicates the corresponding

optical interface.
Automatic Disabled Disabled l This parameter indicates or specifies

Shutdown Enabled whether the Automatic Laser
Shutdown function is enabled or
disabled for the laser.
l The ALS function allows the laser to
shut down automatically when an
optical port does not carry services, an
optical fiber is broken, or no optical
signal is received.
l You can set On Period(ms), Off
Period(ms), and Continuously On-
test Period(ms) only when this
parameter is set to Enabled.
On Period(ms) 1000 to 3000 2000 This parameter indicates or specifies the

period when a shutdown laser
automatically starts up and tests whether
the optical fiber is normal.
Off Period(ms) 2000 to 300000 60000 This parameter indicates or specifies the
period when the laser does not work (with
the ALS function being enabled).
Continuously On- 2000 to 300000 90000 This parameter indicates or specifies the
test Period(ms) period when a shutdown laser is manually
started up and tests whether the optical
fiber is normal.
B.5.10 Parameters for PDH Interface Boards

This topic describes parameters that are related to PDH interface boards.
B.5.10.1 Parameter Description: PDH Ports

This topic describes the parameters that are related to the PDH ports.

Navigation Path
Configuration > PDH Interface from the Function Tree.
2. Select By Board/Port(Channel).
3. Select Port from the list box.
Parameters

port.
Port Name - - This parameter indicates or specifies the

name of the port.
Tributary Non-Loopback Non-Loopback l This parameter indicates or specifies

Loopback Inloop the loopback status in the associated
path of the tributary unit.
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 - - This parameter indicates the impedance of

a path, which depends on the tributary unit.

Service Load Load Load l This parameter indicates or specifies

Indication Non-Loaded the service loading status in a specific
path.
l When this parameter is set to Load, the
board detects whether alarms exist in
the path.
Loaded, the board does not detect
whether there are alarms in the path.
l If a path does not carry any services,
you can set this parameter to Non-
Loaded for the path to mask all the
alarms. If a path carries services, you
need to set this parameter to Load for
the path.
Input Signal Unequalized Unequalized l This parameter indicates whether the

Equalization Equalized input signals are equalized.
parameter to default value.

Retiming Mode Normal Normal l This parameter indicates or specifies

Retiming Mode of the retiming mode of a specific path.
Tributary Clock l By using the retiming function, the
Retiming Mode of retiming reference signal from the SDH
Cross-Connect network and the service data signal are
Clock combined and then sent to the client
equipment, therefore decreasing the
output jitter in the signal. In this way,
the retiming function ensures that the
service code flow can normally transfer
the retiming reference signal.
l When this parameter is set to Normal,
the retiming function is not used.
l When this parameter is set to Retiming
Mode of Tributary Clock, the
retiming function is used with the clock
of the upstream tributary unit traced.
l When this parameter is set to Retiming
Mode of Cross-Connect Clock, the
retiming function is used with the clock
of the cross-connect unit traced.
l It is recommended that the external
clock, instead of the retiming function,
should be used to provide reference
clock signals for the equipment.
l If the retiming function is required, it is
recommended that you set this
parameter to Retiming Mode of Cross-
connect Clock.
Port Service Type E1 E1 If the system control board is SLF2CSHO,

T1 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.
Output Signal Unequalized Unequalized l This parameter indicates whether the

Equalization Equalized output signals are equalized.
default value.

E1 Frame Format Unframe Unframe Specifies the E1 frame format for E1 ports.
Double Frame l To detect E1 BER performance on an
CRC-4 Multiframe OptiX RTN 900, set E1 Frame Format
of the local E1 port to the same value as
that of the opposite E1 port. It is
recommended that E1 Frame Format
of both the local and opposite E1 ports
be CRC-4 Multiframe.
l In other scenarios wherein an OptiX
RTN 900 is used, it is recommended
that E1 Frame Format take its default
value Unframe. If E1 Frame Format
is Unframe, the OptiX RTN 900
transparently transmits E1 frames and
the local E1 port allows for
interconnection with another E1 port
whose E1 Frame Format is Double
Frame or CRC-4 Multiframe.
NOTE
E1 Frame Format needs to be set to the same
value at both ends of an E1 link.
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.
Parameters for Setting the Display Format

Display in Text Selected Selected This parameter specifies the display in the
Format Deselected text format.
Display in Selected Deselected This parameter specifies the display in the

Hexadecimal Deselected hexadecimal format.


Object - - This parameter indicates the object to be

set.
J0 to be - [16 Bytes]HuaWei If the NE at the opposite end reports the

Sent([Mode]Conte SBS J0_MM alarm, this parameter is set
nt) according to the J0 byte to be received at
the opposite end.
J0 to be - [Disabled] l This parameter specifies the J0 byte to

Received([Mode]C be received.
ontent) l If this parameter is set to [Disabled],
the board does not monitor the received
J0 byte.
default value.
J0 - - This parameter indicates the J0 byte that is

Received([Mode]C actually received.
ontent)
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.



Parameters for the Trace Byte J1


set.
J1 to be - [16 Bytes]HuaWei If the NE at the opposite end reports the

Sent([Mode]Conte SBS HP_TIM alarm, this parameter is set
nt) according to the J1 byte to be received at
the opposite end.
J1 to be - [Disabled] l If this parameter is set to [Disabled],

Received([Mode]C the board does not monitor the received
ontent) J1 byte.
default value.
J1 - - This parameter displays the J1 byte that is

Received([Mode]C actually received.
ontent)
Parameters for the Signal Flag C2


set.
C2 to be Sent - - If the NE at the opposite end reports the

HP_SLM alarm, this parameter is set
according to the C2 byte to be received at
the opposite end.
C2 to be Received - - If the NE at the local end reports the

HP_SLM alarm, this parameter is set
according to the C2 byte to be sent at the
opposite end.
C2 Received - - This parameter displays the C2 byte that is

actually received.
Parameters for Overhead Termination


set.

VC4 Overhead Termination Auto l If this parameter is set to Pass-

Termination Pass-Through Through, the NE forwards the original
overhead after monitoring the VC-4
Auto path overhead regardless of the C2
byte.
l If this parameter is set to Termination,
the NE generates the new VC-4 path
overhead according to the board setting
after monitoring the VC-4 path
overhead regardless of the C2 byte.
l If this parameter is set to Auto, the
VC-4 path overhead in the VC-4 pass-
through service is passed through, and
the VC-4 path overhead in the VC-12
service is terminated.
default value.
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
Configuration > Overhead Management > VC12 Path Overhead from the Function
Tree.


Parameters for the Trace Byte


set.

J2 to be Sent - [16 Bytes]HuaWei If the NE at the opposite end reports the

SBS LP_TIM or LP_TIM_VC12 alarm, this
parameter is set according to the J2 byte to
be received by the NE at the opposite end.
J2 to be Received - [Disabled] l If this parameter is set to [Disabled],

the board does not monitor the received
J2 byte.
default value.
NOTE
IF boards do not support this parameter.
J2 Received - - This parameter displays the J2 byte that is

actually received.
Parameters for the Signal Flag


set.
Signal - - If the NE at the opposite end reports the

Label(L1,L2,L3 of LP_SLM or LP_SLM_VC12 alarm, this
V5) to be Sent parameter is set according to the V5 byte
to be received at the opposite end.
Signal - - If the NE at the local end reports the

Label(L1,L2,L3 of LP_SLM or LP_SLM_VC12 alarm, this
V5) to be Received parameter is set according to the V5 byte
to be sent at the opposite end.
NOTE
IF boards do not support this parameter.
Signal - - This parameter displays the V5 byte that is

Label(L1,L2,L3 of actually received.
V5) Received
B.5.12 Parameter Description: Ethernet Virtual Interfaces

This topic describes the parameters of Ethernet virtual interfaces.
Navigation Path
Configuration > Interface Management > Ethernet Virtual Interface from the
Function Tree.


3. Choose New > Create Ethernet Virtual Interface.
Basic Attributes of Ethernet Virtual Interfaces

Range Value
Port 1 to 8191 - This parameter displays

or specifies the port
number of an Ethernet
virtual interface.
Name - - This parameter displays

name of an Ethernet
virtual interface.
Port Type EoA EoA This parameter displays

Virtual Virtual or specifies the port type
Interface Interface of an Ethernet virtual
VLAN Sub interface.
Interface OptiX RTN 900 allows
Port Type to be set to
VLAN Sub Interface
only.
Port Mode - Layer 3 This parameter displays

mode of an Ethernet
virtual interface.
Associated Board - - This parameter displays

or specifies the board
where an Ethernet virtual
interface is located.
Associated Port - - This parameter displays

where an Ethernet virtual
interface is located.
VPI - - Setting this parameter is

not available.
VCI - - Setting this parameter is

not available.
AAL5 Encapsulation Type - - Setting this parameter is

not available.


Range Value
VLAN - - This parameter specifies

the VLAN ID that an
Ethernet virtual interface
uses.
This parameter can be set
when Port Type is
VLAN Sub Interface.
Specify IP Address Manually Unspecifie This parameter specifies

Unspecifie d whether to set the IP
d 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 This parameter specifies

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
addresses of the ports
at both ends of an
MPLS tunnel must be
in the same network
segment.
IP Mask - 255.255.25 This parameter specifies

5.252 the subnet mask for a
port.
This parameter can be set
only when Specify IP
Address is Manually.


Range Value
Enable Tunnel Enabled Disabled This parameter specifies

Disabled whether to enable an
MPLS tunnel.
This parameter specifies
the MPLS enabled status
for a port. If you set
Enable Tunnel to
Enabled for a port, the
port identifies and
processes MPLS labels.
Layer 3 Attributes
Port - - This parameter displays an IF port.
Enable Tunnel Enabled Disabled This parameter displays or specifies

Disabled whether to enable an MPLS tunnel.
Set the MPLS enabled status for a port. If
you set Enable Tunnel to Enabled, the
port identifies and processes MPLS labels.
Specify IP Manually Unspecified This parameter displays or specifies

Address Unspecified 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.

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 (E-
Line) service.
Navigation Path
Ethernet Service Management > E-Line Service from the Function Tree.
2. Click New.
Table B-3 Service direction of UNI-UNI

Service ID 1 to 4294967294 - This parameter

specifies the ID of the
E-Line service.
Service Name - - This parameter

specifies the name of
the E-Line service.
Direction UNI-UNI UNI-UNI l This parameter

UNI-NNI specifies the
direction of the E-
NNI-NNI Line service.
to UNI-UNI.

BPDU Not Transparently Not Transparently l RTN NEs support

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

Source Port - - l Before setting this

parameter, ensure
that Port Mode is
Layer 2 or Layer
Mix.
l The value of this
parameter cannot
be the same as the
value of sink port.
l The value of this
parameter cannot
be used for the E-
LAN port.
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.

Sink 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 Source
Port.
l The value of this
parameter cannot
be used for the E-
LAN port.
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.

Table B-4 Service direction of UNI-NNI (carried by PWs)


E-Line service.

the E-Line service.

direction of the E-
NNI-NNI Line service.
to UNI-NNI.

Transparently Transparently
Transmitted 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 User User This parameter needs

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

PW PWE3 services, the
parameter value is
always PW.

Protection Type No Protection No Protection l If this parameter is

PW APS set to PW APS,
working and
Slave Protection Pair protection PWs
need to be
configured.
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)


specifies the ID of
the E-Line service.

the E-Line service.

direction of the
NNI-NNI E-Line service.
to UNI-NNI.


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.

Source Port - - l Before setting

this parameter,
ensure that Port
Mode is Layer 2
or Layer Mix.
l The value of this
parameter cannot
be the same as
the value of sink
port.
l The value of this
parameter cannot
be used for the E-
LAN port.
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.
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

PW services, the
parameter value is
always QinQ Link.
QinQ Link ID - - Selects or specifies

the ID of a QinQ
link. You can create
a QinQ link or select
an existing QinQ
link.

Table B-6 Service direction of NNI-NNI

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.

UNI-NNI specifies the direction
of the E-Line service.
NNI-NNI
l Set this parameter to
NNI-NNI.

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.

PRI - - OptiX RTN 900 does not

Bearer Type 1 QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line service.
QinQ Link ID 1 - - l Selects the QinQ link

ID of the first QinQ
link.
l The QinQ link ID is
preset in QinQ Link.
Bearer Type 2 QinQ Link QinQ Link Uses the QinQ link to
QinQ Link ID 2 - - l Selects the QinQ link

ID of the second
QinQ link.
l The QinQ link ID is
QinQ Link ID - - Selects or specifies the

ID of a QinQ link. You
can create a QinQ link or
select an existing QinQ
link.
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
l If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters
of working and protection PWs need to be configured. This section considers the parameters of the
working PW as an example.
PW ID - - Specifies the ID of the

PW that carries
services.
PW Signaling Type Static Static Labels for static PWs

need to be manually
assigned.

PW Type Ethernet Ethernet l Specifies the type of

Ethernet Tagged Mode the PW.
l PW Type indicates
whether P-TAG is
added to Ethernet
frames that are
encapsulated for
transmission on
PWs. If it is not
required to add
VLAN IDs, set this
parameter to
Ethernet. If it is
required to add
VLAN IDs, set this
parameter to
Ethernet Tagged
Mode and then set
Request VLAN in
the Advanced
Attributes tab.
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.

Peer LSR ID - - Specifies the LSR ID

of the PW at the remote
end. If an existing
tunnel is selected, the
LSR ID will be
automatically assigned.
QoS Parameters (PW)

NOTE
QoS parameters need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
Bandwidth Limit - - Specifies whether the

bandwidth limit function
is enabled.
l This function limits
the bandwidth of one
or more PWs in an
MPLS tunnel.
l An ETH PWE3
service corresponds to
a PW. Therefore, this
function can also limit
the bandwidth of ETH
PWE3 services in an
MPLS tunnel.
Policy - - OptiX RTN 900 does not

CIR (kbit/s) - - Specifies the committed

information rate (CIR) of
a PW.
It is recommended that
you set this parameter to
the same value as PIR.
CBS (byte) - - Specifies the committed

burst size (CBS) of a PW.
PIR (kbit/s) - - Specifies the peak

information rate (PIR) of
a PW.
the same value as CIR.

PBS (byte) - - Specifies the peak burst

size (PBS) of a PW.
EXP - - OptiX RTN 900 does not

LSP Mode Pipe Pipe Pipe: When stripping

MPLS tunnel labels from
packets, an egress node
does not update the
scheduling priority for
the packets.
Parameters of Advanced Attributes (PW)

Control Word Not in use Not in use Specifies whether a

Used First product uses control
words when
encapsulating ETH
PWE3 packets.
NOTE
For information about
whether a product uses
control words when
encapsulating ETH PWE3
packets, see the Feature
Description.
Control Channel Type None Alert Label l Specifies the mode of

Alert Label PW continuity check.
CW l None indicates that
VCCV is not used.
l Alert Label indicates
VCCV packets in
Alert Label
encapsulation mode.
l CW: indicates that
VCCV packets
encapsulated based on
the control word are
used.

VCCV Verification Ping Ping l Specifies the VCCV

Mode None verification mode.
The VCCV
verification is used for
PW continuity check.
l If the VCCV-Ping test
is required, do not set
this parameter to
None.
Request VLAN - - l Set this parameter

when PW Type is
Ethernet Tagged
Mode.
l If the received packets
do not carry any
VLAN IDs, the PW
will add VLAN IDs to
the packets as
required by the setting
of this parameter.
TPID - - OptiX RTN 900 does not

support request VLAN
TPID of the PW level.
Protection Group Parameters (PW APS)

NOTE
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set
to PW APS.
Protection Type - - Specifies the protection

type.
Protection Group ID - - Specifies the protection

group ID.

Enabling Status Disabled Disabled l Specifies the enabling

Enabled status of the PW
protection group.
l During the creation of
a protection group, set
Enabling Status to
Disabled. After the
APS protection group
is configured at both
ends, set Enabling
Status to Enabled.
Protection Mode - - Displays the protection

mode.
NOTE
The RTN 900 supports 1:1
protection mode.
Working PW ID - - Displays the ID of the

working PW.
Protection PW ID - - Displays the ID of the

protection PW.
Switching Mode - - Displays the switching

mode to be used when a
PW fails.
NOTE
The RTN 900 supports
dual-ended switching.
Revertive Mode Non-revertive Revertive l This parameter

Revertive specifies whether to
switch services back
to the original
working PW after it
recovers.
l The value Revertive
indicates that services
are switched to the
original working PW
and the value Non-
revertive indicates
that services are not
switched to the
original working PW.
is recommended.

Switchover Restoration 1 to 12 1 l Specifies the WTR

Time (min) time of the protection
group.
l When the preset WTR
time expires after the
original working PW
recovers, services are
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
l The default value is
recommended.
Switchover Delay Time 0 to 100 0 l Specifies the hold-off

(100 ms) time of the protection
group.
to a value other than
0, the protection
group does not trigger
switching once it
detects faults, but
waits until the hold-
off time expires, and
then detects whether
any faults persist. If
any faults persist, the
switching is triggered;
otherwise, no
switching is triggered.
recommended.
Detection mode - - Displays the detection

mode of the PW APS
protection group.
OAM Parameters
NOTE
l The OAM parameters of the PW APS protection group need to be configured if the Protection Type of
PWs is set to PW APS.
l To configure PW OAM parameters, choose Configuration > MPLS Management > PW Management
> PW OAM Parameter from the Function Tree.

OAM Status - - Displays the enabling

status of PW OAM.
Detection Mode Auto-Sensing Auto-Sensing l Specifies the detection

Manual mode of OAM
packets.
l Manual: The CC
packets are sent at the
interval specified by
the user.
l Auto-Sensing: The
CC packets are sent at
the interval of
receiving PW OAM
packets.
l If Detection Mode is
set to Manual, you
need to set the PW
OAM detection
packets to be received
and transmitted.
l The value Auto-
Sensing is
recommended.

Detection Packet Type CV CV l CV: The detection

FFD packets are sent at a
fixed interval.
l FFD: The detection
the user.
set to Auto-Sensing,
this parameter
specifies the PW
OAM detection
packets to be
transmitted.
set to Manual, this
parameter specifies
the PW OAM
detection 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 3.3 50 l Specifies the period of

Interval(ms) 10 detection packets.
20 l This parameter is
configurable when
50 Detection Packet
100 Type is FFD and
200 assumes the fixed
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.
LSR ID to be Received - - Specifies the LSR ID to

be received.
Transmitted PW ID - - Specifies the PW ID to be

received.

Protection Group Parameters (Slave Protection Pair)

NOTE
to Slave Protection Pair.

mode.
Protection Group ID - - Specifies the ID of the

slave protection pair. The
switching of the master
PW APS protection
group triggers the
switching of the slave
PW APS protection
group simultaneously.

working PW in the slave
protection pair.

protection PW in the
slave protection pair.
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 (E-
Line) service.
Navigation Path
2. Click Create.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Table B-7 Service direction of UNI-UNI


service.

service.


NNI-NNI
UNI-UNI.
BPDU Not Transparent Not Transparent l RTN NEs support

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

set here.
Service Tag Role - - This parameter is not

supported when
Direction is UNI-UNI.


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 - l This parameter can be

set to null, a number,
or several numbers.
When setting this
parameter to several
numbers, use the
comma (,) to separate
the discrete numbers,
or use the endash (-)
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
indicate 1, 3, 4, 5, and
6.
to null, all the
services at the source
service source.
the service that
contains the VLAN
ID at the source port
can be used as the
service source.

Sink Interface - - l Before setting this

Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of Source Port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the
Sink VLAN ID 1 to 4094 - l This parameter can be

or several numbers.
When setting this
numbers, use the
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.

Table B-8 Service direction of UNI-NNI (carried by PWs)


service.

service.

NNI-NNI
UNI-NNI.

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.

set here.
Service Tag Role User User This parameter needs to

Service be specified only when
Direction is UNI-NNI
and Bearer Type is PW.


Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the
Source VLANs 1 to 4094 - l This parameter can be

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 - - OptiX RTN 900 does not


Bearer Type QinQ Link PW For UNI-NNI ETH

PW PWE3 services, the
parameter value is
always PW.
Protection Type No Protection No Protection l If this parameter is set

PW APS to PW APS, working
and protection PWs
Slave Protection Pair need to be
configured.
to Slave Protection
Pair, you need to
bind the slave PW
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)


service.

service.

NNI-NNI
UNI-NNI.


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.

set here.

supported when
Direction is UNI-NNI
and Bearer Type is
QinQ Link.


Port Mode is Layer
2 or Layer Mix.
l The value of this
parameter cannot be
of sink port.
l The value of this
parameter cannot be
used for the E-LAN
port.
according to the
Source VLANs 1 to 4094 - l This parameter can be

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 - - OptiX RTN 900 does not


Bearer Type QinQ Link PW For NNI-NNI QinQ

PW services, the parameter
value is always QinQ
Link.
Table B-10 Service direction of NNI-NNI


service.

service.

NNI-NNI
NNI-NNI.


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.

set here.

supported when
Direction is NNI-NNI.
PRI - - OptiX RTN 900 does not

Bearer Type QinQ Link QinQ Link Uses the QinQ link to
Parameters for Port Attributes

Port Name - - This parameter displays

the UNI port.

Enable Port Enabled - l This parameter

Disabled displays or specifies
whether the port is
enabled.
l Ethernet services can
be received,
processed, and
forwarded normally
only if Port Enable is
set to Enabled.
l Port Enable is
already set in
Ethernet Interface.
Port Mode Layer 2 - l Specifies the working

Layer 3 mode of an Ethernet
port.
to Layer 2, the port
can be used to access
Ethernet services
from the user
equipment or to carry
Ethernet services that
exclusively occupy
the port.
is set to Layer 3,
Ethernet services over
the port can be carried
by PWs.


802.1Q displays or specifies
the method of the port
QinQ to process the
received packets.
l If you set this
parameter to Null, the
port transparently
packets.
l If you set this
parameter to 802.1Q,
the port identifies the
packets that comply
with the IEEE 802.1q
standard.
l If you set this
parameter to QinQ,
packets that comply
with the IEEE
802.1ad standard.

Working Mode Auto-Negotiation - l The Ethernet ports of

support different
10M Full-Duplex working modes.
100M Half-Duplex l When the equipment
100M Full-Duplex on the opposite side
1000M Full-Duplex works in auto-
the working mode of
local side to Auto-
Negotiation.
mode, set the working
mode of the
equipment on the
local side to 10M
Full-Duplex, 100M
Full-Duplex, or
1000M Full-Duplex
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.

Tag Tag Aware Tag Aware l If all the accessed

with the VLAN tag
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
TAG to Hybrid.
Specify IP Address Unspecified - l Displays or selects the

Manually method to configure
IP addresses of ports.
l The value
Unspecified indicates
that the IP addresses
do not need to be
configured for a port.
address of a port can
be manually
configured.
l This parameter is
available when Port
Mode is Layer 3.
IP Address - - l Displays or specifies

the IP address of the
port.
l This parameter is
available when
Manually.
IP Mask - - l Displays or specifies

the subnet mask of the
port.
l This parameter is
available when
Manually.

Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW.

PW that carries services.

need to be manually
assigned.

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.

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.


PW.
Tunnel New New A tunnel needs to be

Use existing PWs created or selected. If no
tunnel is available,
creation of a PW will fail.
Egress Tunnel New New For a bidirectional tunnel,

Use existing resource the system will configure
the egress tunnel
automatically.
Peer LSR ID - - Specifies the LSR ID of

the PW at the remote end.
If an existing tunnel is
selected, the LSR ID will
be automatically
assigned.
Parameters of Advanced Attributes (PW)


words when
encapsulating ETH
PWE3 packets.
NOTE
control words when
Description.


VCCV is not used.
VCCV packets in
Alert Label
encapsulation mode.
VCCV packets
used.

The VCCV
this parameter to
None.

when PW Type is
Ethernet Tagged
Mode.
do not carry any
VLAN IDs, the PW
the packets as
of this parameter.
QoS Parameters (PWs)

PW ID - - Displays the ID of a PW.
Direction - - Displays the direction of

a tunnel.
PW Type - - Displays the type of a

PW.


is enabled.
or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.


a PW.


a PW.

size (PBS) of a PW.


does not update the
the packets.


NOTE
to PW APS.

type.

group ID.

protection group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

mode.
NOTE
protection mode.

working PW.

protection PW.

PW fails.
NOTE


to the original
working PW after it
recovers.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.


group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.

mode of the PW APS
protection group.
OAM Parameters
NOTE

status of PW OAM.


Manual mode of OAM
packets.
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
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.

configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

be received.

received.


NOTE

mode.

PW APS protection
group triggers the
PW APS protection

protection pair.

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

Service ID 1 to 4294967294 - This parameter indicates

service.
Service Name - - This parameter indicates

or specifies the name of
the E-Line service.
Source Node - - This parameter indicates

the source node.

Sink Node - - This parameter indicates

the sink node.
Service Tag Role - - This parameter indicates

the service tag role.
MTU (byte) - - This parameter cannot be

queried here.
BPDU Not Transparently - l RTN NEs support

Transmitted only Not
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 - - This parameter indicates

whether E-Line service is
deployed.
Parameters Associated with UNI Ports


the UNI port.

VLANs 1 to 4094 - This parameter indicates

or specifies the VLAN
ID of the UNI port.
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 UNI-
NNI 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 - - Displays the priority of

each UNI port.

NNI Parameters (PW)

PW ID - - This parameter displays

the PW ID.
Working Status - - This parameter displays

the working status of a
PW.
PW Status - - This parameter displays

whether a PW is enabled.
PW Signaling Type - - This parameter displays

the PW signaling type.
NOTE
The OptiX RTN 900 uses
static PWs only.
PW Type - - This parameter displays

the configured PW type.
PW Direction - - This parameter displays

the direction of a PW.
PW Encapsulation Type - - This parameter displays

the PW encapsulation
type.
NOTE
MPLS only.
PW Incoming Label - - This parameter displays

the configured PW
ingress label.
PW Outgoing Label - - This parameter displays

the configured PW egress
label.
Tunnel Type MPLS MPLS This parameter displays

the type of the tunnel that
carries a PW.
Peer LSR ID - - This parameter displays

the opposite LSR ID.
Tunnel - - This parameter displays

the tunnel.
Control Word - - Displays whether the

ETH PWE3 service uses
Control Word.
Control Channel Type - - This parameter displays

the control channel type.

VCCV Verification - - This parameter displays

Mode the VCCV mode.
Local Operating Status - - Displays the working

status of the PW at the
local end.
Remote Operating - - This parameter displays

Status the working status of the
PW at the remote end.
Overall Operating - - This parameter displays

Status the comprehensive
working status of the PW.
Request VLAN - - This parameter displays

the request VLAN.
Deployment Status - - This parameter displays

the deployment status.
Tunnel for Auto - - This parameter displays

Selection the automatic tunnel
selection policy.
TPID - - The OptiX RTN 900 does

not support request
VLAN TPID of the PW
level.
Parameters Associated with NNI Ports

QinQ Link ID 1 to 4294967295 - l This parameter

indicates the QinQ
link ID of the QinQ
link connected to the
NNI port.
l This parameter is
valid only when
Direction is set to
UNI-UNI or UNI-
creating an E-Line
service.

Port - - l This parameter

indicates the NNI
port.
l This parameter is
valid only when
Direction is set to
UNI-UNI or UNI-
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 NNI-
creating an E-Line
service.
l This parameter is
QoS Parameters

the PW ID.
Direction - - l This parameter

displays the direction
of a PW.
l Egress: indicates the
egress direction of a
PW.
l Ingress: indicates the
ingress direction of a
PW.

Bandwidth Limit - - This parameter displays

or specifies whether the
is enabled for a PW to
prevent network
congestion.
l Regarding
transmission
channels, this
function can be used
to limit the bandwidth
of one or more PWs
in an MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.
Policy - - The OptiX RTN 900 does

not support this
parameter.
CIR (Kbit/s) - - This parameter displays

or specifies the
committed information
rate (CIR) for a PW.
CBS (kbyte) - - This parameter displays

or specifies the
committed burst size
(CBS) for a PW.
PIR (kbit/s) - - This parameter displays

or specifies the peak
information rate (PIR) for
a PW.
PBS (kbyte) - - This parameter displays

burst size (PBS) for a
PW.

EXP - - The OptiX RTN 900 does

not support this
parameter.

does not update the
the packets.
Parameters for the Port Attributes

Port - - Displays the port

information.
Enable Port - - l This parameter

indicates whether to
enable the port.
l This parameter is
preset in General
Attributes of
Ethernet Interface.


802.1Q indicates the
QinQ the port.
l This parameter is
valid only when
Direction is set to
UNI-UNI or UNI-
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 - l This parameter

Access displays the tag of the
port.
Hybrid
l This parameter is
preset in Layer 2
Attributes of
Ethernet Interface.

NOTE
The following parameters are available only after the PW APS protection group is configured.

Protection Group ID - - Displays the ID of the

protection group to be
created.

working PW.

protection PW.
Protection Type - - Displays the protection

mode.
Enabling Status Enabled - l Displays or specifies

Disabled the enabling status of
the PW protection
group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.
Switchover Mode - - Displays the switching

PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.
Revertive Mode Non-revertive - l Specifies whether to

Revertive switch services to the
original working PW
after the fault is
rectified.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.

Switchover WTR Time 1 to 12 - l Displays or specifies

(min) the WTR time of the
protection group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
Switchover Hold-off 0 to 100 - l Displays or specifies

Time (100 ms) the hold-off time of
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 - - Displays the enabling

status of the protocol.
Working Path Status - - Displays the status of the

current working path.
Protection Path Status - - Display the status of the

current protection path.


NOTE
The following parameters are available only after the slave protection pair is configured.

PW APS protection
group triggers the
PW APS protection

protection pair.

DNI PW ID - - Displays the DNI PW ID.
PW Type - - Displays the PW type.
Deployment Status - - Displays the deployment

status of the slave
protection pair.
B.6.1.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
2. Click the VLAN Forwarding Table Item tab.
3. Click New.
Parameters for VLAN Forwarding Table Item

Source Interface Type V-UNI V-UNI This parameter specifies

the network attribute of
the source interface.

Source Interface - - This parameter specifies

the source interface.
Source VLAN ID 1 to 4094 - This parameter specifies

the VLAN ID of the
source service.
Sink Interface Type V-UNI V-UNI This parameter specifies

the network attribute of
the sink interface.
Sink Interface - - This parameter specifies

the sink interface.
Sink VLAN ID 1 to 4094 - This parameter specifies

the VLAN ID of the sink
service.
NOTE
l The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table item is
created. In this case, a service from Source Interface to Sink Interface carries the VLAN ID specified in
Sink VLAN ID when the service is transmitted from Sink Interface.
l The VLAN ID in a VLAN forwarding table item is converted unidirectionally and can be converted from
Source VLAN ID to Sink VLAN ID only. The VLAN ID can be converted bidirectionally only when the
other VLAN forwarding table item is configured reversely.
l In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion of
VLAN IDs.
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.


Service ID 1 to 4294967294 - l This parameter

E-LAN service.
l OptiX RTN 900
supports simultaneous
creation of an E-LAN
service only.

the name of the E-LAN
service.

BPDU - - l In the case of an E-

LAN 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 bridge-
based services with
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.

Tag Type C-Aware C-Aware l C-Aware indicates

S-Aware that the packets are
learnt according to C-
Tag-Transparent Tag (the VLAN tag
on the client-side). To
create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
that the packets are
learnt according to S-
Tag (the VLAN tag at
the carrier service
layer). To create the
802.1ad bridge, set
this parameter to S-
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
transmitted. To create
the 802.1d bridge, set
this parameter to Tag-
Transparent.
according to the

Self-Learning MAC Enabled Enabled l This parameter

Address Disabled specifies whether to
enable the MAC
address self-learning
function.
l If the MAC self-
learning function of
an Ethernet LAN is
enabled, the Ethernet
LAN learns an MAC
address according to
the original MAC
address in the packet
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
an Ethernet LAN is
disabled, a static
MAC address
forwarding table is
recommended to be
configured.
MAC Address Learning IVL - l This parameter

Mode SVL indicates the mode
used to learn an MAC
address.
l When the bridge uses
the SVL mode, all the
VLANs share one
MAC address table. If
the bridge uses the
IVL mode, each
VLAN has an MAC
address table.

whether E-LAN service
is deployed.
MTU(byte) - - This parameter cannot be

set here.
Service Tag Role - - The NE does not support

this parameter.

Protection Mode No Protection No Protection l If this parameter is set

PW APS to PW APS, working
and protection PWs
Slave Protection Pair 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.
l When the working
PW in a PW APS
protection group is
faulty, protection
switching occurs on
the PW APS
protection group as
well as on all its slave
protection pairs.
Parameters for UNIs


the UNI port.
SVLAN/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 S-
Aware.
according to the

VLANs/CVLAN 1 to 4094 - l This parameter

specifies the VLAN
ID of the UNI port.
or several numbers.
When setting this
numbers, use the
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 1 to 4094 - If a virtual private line

service (VPLS) is
mounted to a UNI port
configured for PORT-
based flows, this
parameter needs to be
configured. Moreover, set
Tag Type to C-Aware or
S-Aware.

Parameters of NNIs (Port)


indicates the NNI
port.
l This parameter is
valid only when Tag
Type is set to S-
Aware.
SVLANs - - l This parameter

ID of the NNI port.
l This parameter is
valid only when Tag
Type is set to S-
Aware.
Parameters of NNIs (PW)

NOTE
l PW parameters need to be configured for only PW-carried E-LAN services.


PW that carries
services.

need to be manually
assigned.


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 Incoming Label 16 to 1048575 - Specifies the PW

Ingress label.
PW Outgoing Label 16 to 1048575 - Specifies the PW

Egress label.

select tunnels.

PW.

PW will fail.
Egress Tunnel - - For a bidirectional

tunnel, the system will
configure the egress
tunnel automatically.

Peer LSR ID - - Specifies the LSR ID

of the PW at the remote
end. If an existing
tunnel is selected, the
LSR ID will be
Parameters for the Split Horizon Group

Split Horizon Group ID - 1 l This parameter

indicates the ID of the
split horizon group.
l The default split
horizon group ID is 1
and cannot be set
manually.
Split Horizon Group - - l A split horizon group

Member member indicates the
logical port member
in the split horizon
group.
l The port members
that are added to the
same split horizon
group cannot
communicate with
each other.
l OptiX RTN 900
supports only the
division of the split
horizon group
members according to
the Ethernet physical
port.
l If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
member, the physical
port that is mounted
with the logical port is
automatically added
to the split horizon
group member.

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
Ethernet Service Management > E-LAN Service from the Function Tree.
2. Click New.
Parameters on the Main Interface (Configuring the Source and Sink Ports)
Service ID 1 to 4294967294 - l This parameter

E-LAN service.
l The NE supports
simultaneous creation
of an E-LAN service
only.

service.


LAN 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
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 bridge-
based services with
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.


create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
the carrier service
802.1ad bridge, set
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
Transparent.
according to the


Address Disabled specifies whether to
enable the MAC
function.
l If the MAC self-
an Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
an Ethernet LAN is
disabled, a static
MAC address
forwarding table is
recommended to be
configured.
MAC Address Learning IVL - l This parameter

Mode SVL indicates the mode
address.
VLANs share one
the bridge uses the
IVL mode, each
VLAN has an MAC
address table.
Port - - This parameter displays

the port name.

Port Type - - This parameter displays

the port type.
l When the parameter
value is UNI, the port
connected to the
bridge is a UNI port.
That is, this port
functions as the UNI
port connected to the
IEEE 802.1d bridge
or IEEE 802.1q
bridge.
value is NNI, the port
connected to the
bridge is an NNI port.
That is, this port
functions as the NNI
IEEE 802.1ad bridge.
value is UNI (PORT
+S-VLAN), a specific
S-VLAN ID is added
to all the traffic flows
that are received by
the UNI port
connected to the IEEE
802.1ad bridge.
value is UNI (PORT
+C-VLAN+S-
VLAN), a specific S-
VLAN ID is added to
all the traffic flows
that are received by
the UNI port
connected to the IEEE
802.1ad bridge and
contain the specific
C-VLAN ID.

VLAN 1 to 4094 - l This parameter is

valid only when Tag
Type is set to C-
Aware and Tag is set
to Access or Hybrid.
value is null, it
indicates that the
entire physical port is
connected to the
bridge.
l You need to set this
parameter according
to the planning
information.

C-VLAN 1 to 4094 - l This parameter is

valid only when Tag
Type is set to S-
Aware.
l This parameter
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 E-
LAN service
exclusively occupies
the corresponding
UNI port; that is, the
entire physical UNI
port is connected to
the bridge.
value is not null, a
specific S-VLAN ID
is added to only the
traffic flows that are
received by the UNI
port and contain this
VLAN ID.

S-VLAN 1 to 4094 - l This parameter is

valid only when Tag
Type is set to S-
Aware.
l This parameter
ID that needs to be
added to traffic flows
received by the UNI
port or the S-VLAN
ID that the NNI port
can identify.
l You need to set this
parameter according
to the planning
information.

displays whether the
port is enabled.
be received,
processed, and
forwarded normally
only if Enable Port is
set to Enabled.
l Enable Port is
already set in
Ethernet Interface.


support different
the working mode of
local side to Auto-
Negotiation.
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.


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.

with the VLAN tag
Hybrid (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.

Default VLAN 1 to 4094 1 l Default VLAN ID is

valid only when TAG
is set to Access or
Hybrid.
l Default VLAN ID is
actual situations.
Parameters on the Main Interface (Setting Service Parameters)

Split Horizon Group Selected Deselected This parameter specifies

Deselected whether to create a split
horizon group.
Split Horizon Group ID - - l This parameter

displays the ID of the
l The ID of the split
horizon group is 1 by
default and cannot be
specified manually.


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


the ID of the E-LAN
service.


service.

LAN 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
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 bridge-
based services with
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.


create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
the carrier service
802.1ad bridge, set
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
Transparent.


Address indicates whether to
enable the MAC
function.
l If the MAC self-
an Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
an Ethernet LAN is
disabled, a static
MAC address
forwarding table is
recommended to be
configured.
MAC Address Learning - - l This parameter

Mode indicates the mode
address.
VLANs share one
the bridge uses the
IVL mode, each
VLAN has an MAC
address table.
MTU(byte) - - This parameter cannot be

queried here.
Service Tag Role - - OptiX RTN 900 does not


whether E-LAN service
is deployed.

Parameters for UNIs


the UNI port.
SVLAN 1 to 4094 - l This parameter

ID of the UNI port.
l This parameter is
valid only when Tag
Type is set to S-
Aware.
according to the

VLANs/CVLAN 1 to 4094 - l This parameter

specifies the VLAN
ID of the UNI port.
or several numbers.
When setting this
numbers, use the
or use the en dash (-)
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
to null, the E-LAN
service exclusively
uses the
corresponding UNI
physical port. That is,
the entire port is
mounted to the
bridge.
to a non-null value,
only the
corresponding UNI
port whose service
packets contain this
VLAN ID works as
the logical port and is
mounted to the
bridge.

Parameters for NNIs (Port)


indicates the NNI
port.
l This parameter is
valid only when Tag
Type is set to S-
Aware.
SVLANs - - l This parameter

ID of the UNI port.
l This parameter is
valid only when Tag
Type is set to S-
Aware.
or several numbers.
When setting this
numbers, use the
or use the en dash (-)
to represent a
consecutive number.
For example, the
numbers 1, and 3-6
6.
NNI Parameters (PW)


the PW ID.
Working Status - - This parameter displays

the working status of a
PW.



the PW signaling type.
NOTE
static PWs only.

the configured PW type.


the PW encapsulation
type.
NOTE
MPLS only.

the configured PW
ingress label.

the configured PW egress
label.
Tunnel Type MPLS MPLS This parameter displays

the type of the tunnel that
carries a PW.

the opposite LSR ID.
Tunnel - - This parameter displays

the tunnel.

ETH PWE3 service uses
Control Word.


Mode the VCCV mode.

local end.




the request VLAN.

the deployment status.

selection policy.

not support request
VLAN TPID of the PW
level.
Parameters for Static MAC Addresses

VLAN ID - - l This parameter is

invalid if MAC
Address Learning
Mode is SVL. That
is, the preset static
MAC address entries
are valid for all
VLANs.
l If MAC Address
Learning Mode is set
to IVL, the preset
static MAC address
entries are valid for
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
according to the

MAC Address - - l This parameter

the static MAC
address.
l A static MAC address
is an address that is
set manually. It is not
aged automatically
and needs to be
deleted manually.
l Generally, a static
MAC address is used
for the port that
receives but does not
forward Ethernet
service packets or the
port whose MAC
address does not need
to be aged
automatically.
Egress Interface - - l This parameter

specifies the Ethernet
port that corresponds
to the MAC address.
according to the

Parameters for Self-Learning MAC Address


invalid if MAC
Address Learning
Mode is SVL. That
is, the preset self-
learning 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

the self-learning
MAC address. A self-
learning MAC
address is also called
a dynamic MAC
address.
l A self-learning MAC
address is an entry
obtained by a bridge
in SVL or IVL
learning mode. A self-
learning MAC
address can be aged.

to the MAC address.
according to the

Parameters Associated with MAC Address Learning Parameters

Aging Ability Enabled Enabled OptiX RTN 900 supports

Disabled enabling/disabling of the
aging function and aging
Aging Time(min) 1 to 640 5 time for the MAC
address table.
If one routing entry is not
updated in a certain
period, that is, if no new
packet from this MAC
address is received to
enable the re-learning of
this MAC address, this
routing entry is
automatically deleted.
This mechanism is called
aging, and this period is
called aging time. The
aging time of a MAC
address table is 5 minutes
by default.
Specified Address Table 0 to 65534 512 l This parameter is

Capacity supported only by the
OptiX RTN
950A/905/RTN910A
and the OptiX RTN
950 that houses
CSHU/CSHUA
boards.
l This parameter
specifies the MAC
address forwarding
table capacity for E-
LAN services.
Address Detection 80 to 100 95 l This parameter is

Upper Threshold (%) supported only by the
OptiX RTN 950A/
905/910A and the
OptiX RTN 950 that
houses CSHU/
CSHUA boards.
l When the MAC
address forwarding
LAN services is
greater than Address
Detection Upper

Address Detection 60 to 100 90 Threshold (%), an

Lower Threshold (%) FDBSIZEALM_ELA
N alarm is reported.
When the MAC
address forwarding
LAN services is less
than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELA
N alarm automatically
clears.
Parameters for Disabled MAC Addresses

VLAN ID - - This parameter indicates

ID of the service. A
disabled MAC address is
valid for the VLAN
whose VLAN ID is equal
to the preset VLAN ID.

specifies or indicates
the disabled MAC
address. A disabled
MAC address is also
called a blacklisted
MAC address.
l This parameter is
used for discarding an
entry, also called a
black hole entry,
whose data frame that
contains a specific
destination MAC
address. A disabled
MAC address needs
to be set manually and
cannot be aged.



l The default split
and cannot be set
manually.

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

Frame Type Unicast - This parameter indicates

Multicast the type of the received
unknown frame.

Handing Mode Discard Broadcast Selects the method of

Broadcast processing the unknown
frame. If this parameter is
set to Discard, the
unknown frame is
directly discarded. If this
parameter is set to
Broadcast, the unknown
frame is broadcast at the
forwarding port.
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


the ID of the E-LAN
service.

service.


LAN 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
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 bridge-
based services with
the encapsulation
attribute being
NULL) are
this case, protocol
when congestion
occurs.


create the 802.1q
bridge, set this
parameter to C-
Aware.
l S-Aware indicates
the carrier service
802.1ad bridge, set
Aware.
l Tag-Transparent
indicates that the
packets are
transparently
Transparent.


Address indicates whether to
enable the MAC
function.
l If the MAC self-
an Ethernet LAN is
LAN learns an MAC
the original MAC
and automatically
refreshes the MAC
address forwarding
table.
l If the MAC self-
an Ethernet LAN is
disabled, a static
MAC address
forwarding table is
recommended to be
configured.
MAC Address Learning - - l This parameter

Mode indicates the mode
address.
VLANs share one
the bridge uses the
IVL mode, each
VLAN has an MAC
address table.
Port Parameters

the port name.

Port Type - - This parameter displays

the port type.
value is UNI, the port
connected to the
bridge is a UNI port.
That is, this port
functions as the UNI
IEEE 802.1d bridge
or IEEE 802.1q
bridge.
l If the parameter value
is NNI, the port
connected to the
bridge is an NNI port.
That is, this port
functions as the NNI
is UNI (PORT+S-
VLAN), a specified
S-VLAN ID is added
to all the traffic flows
received by the UNI
is UNI (PORT+C-
VLAN+S-VLAN), a
specific S-VLAN ID
is added to all the
traffic flows that are
received by the UNI
IEEE 802.1ad bridge
and contain the
specific C-VLAN ID.
VLAN - - This parameter displays

the VLAN ID.
C-VLAN - - This parameter displays

the C-VLAN ID.
S-VLAN - - This parameter displays

the S-VLAN ID.


displays whether the
port is enabled.
be received,
processed, and
forwarded normally
only if Enable Port is
set to Enabled.
l Enable Port is
already set in
Ethernet Interface.


support different
the working mode of
local side to Auto-
Negotiation.
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.


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.

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

Default VLAN ID 1 to 4094 1 l Default VLAN ID is

valid only when Tag
is set to Access or
Hybrid.
l Default VLAN ID is
actual situations.
Parameters for Static MAC Addresses


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


the static MAC
address.
l A static MAC address
is an address that is
set manually. It is not
aged automatically
and needs to be
deleted manually.
l Generally, a static
MAC address is used
for the port that
receives but does not
forward Ethernet
service packets or the
port whose MAC
address does not need
to be aged
automatically.

to the MAC address.
according to the

Parameters for Self-Learning MAC Address


invalid if MAC
Address Learning
Mode is SVL. That
is, the preset self-
learning 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

the self-learning
MAC address. A self-
learning MAC
address is also called
a dynamic MAC
address.
l A self-learning MAC
address is an entry
obtained by a bridge
in SVL or IVL
learning mode. A self-
learning MAC
address can be aged.

to the MAC address.
according to the

Parameters Associated with MAC Address Learning

Aging Ability Enabled Enabled OptiX RTN 900 supports

Disabled enabling/disabling of the
aging function and aging
Aging Time(min) 1 to 640 5 time for the MAC
address table.
If one routing entry is not
updated in a certain
period, that is, if no new
packet from this MAC
address is received to
enable the re-learning of
this MAC address, this
routing entry is
This mechanism is called
aging, and this period is
called aging time. The
aging time of a MAC
address table is 5 minutes
by default.
Specified Address Table 0 to 65534 512 l This parameter is

Capacity supported only by the
OptiX RTN
950A/905/RTN910A
and the OptiX RTN
950 that houses
CSHU/CSHUA
boards.
l This parameter
specifies the MAC
address forwarding
LAN services.
Address Detection 80 to 100 95 l This parameter is

Upper Threshold (%) supported only by the
OptiX RTN 950A and
the OptiX RTN 950
that houses CSHU/
CSHUA boards.
l When the MAC
address forwarding
LAN services is
greater than Address
Detection Upper
Threshold (%), an

Address Detection 60 to 100 90 FDBSIZEALM_ELA

Lower Threshold (%) N alarm is reported.
When the MAC
address forwarding
LAN services is less
than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELA
N alarm automatically
clears.
Parameters for Disabled MAC Addresses


ID of the service. A
disabled MAC address is
valid for the VLAN
whose VLAN ID is equal
to the preset VLAN ID.

specifies or indicates
the disabled MAC
address. A disabled
MAC address is also
called a blacklisted
MAC address.
l This parameter is
used for discarding an
entry, also called a
black hole entry,
whose data frame that
contains a specific
destination MAC
address. A disabled
MAC address needs
to be set manually and
cannot be aged.



l The default split
and cannot be set
manually.

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

Frame Type Unicast - This parameter indicates

Multicast the type of the received
unknown frame.

Handing Mode Discard Broadcast Selects the method of

Broadcast processing the unknown
frame. If this parameter is
set to Discard, the
unknown frame is
directly discarded. If this
parameter is set to
Broadcast, the unknown
frame is broadcast at the
forwarding port.
B.6.1.9 Parameter Description: QinQ Link_Creation

This topic describes the parameters that are used for creating a QinQ link.
Navigation Path
Ethernet Service Management > QinQ Link from the Function Tree.
2. Click New.
Parameters for the General Attributes

QinQ Link ID 1 to 4294967295 - This parameter specifies

the ID of the QinQ link.
NOTE
The OptiX RTN 900
supports 1024 QinQ links,
whose IDs must be
different from each other.
Board - - This parameter specifies

the board where the
QinQ link is located.
Port - - This parameter specifies

the port where the QinQ
link is located.
S-Vlan ID 1 to 4094 - l This parameter

specifies the VLAN
ID (at the network
operator side) for the
QinQ link.
according to the

B.6.1.10 Parameter Description: E-AGGR Services_Creation

This topic describes the parameters for creating E-AGGR services.
Navigation Path
Configuration > Ethernet Service Management > E-AGGR Service from the
Function Tree.
2. Click New.


the ID of an E-AGGR
service.

the name of an E-AGGR
service.
MTU (bytes) - - Setting this parameter is

not available.
Service Tag Role - - Setting this parameter is

not available.
UNI Parameters
Location Sink - This parameter specifies

Source whether a port functions
as a service source or
sink.
You can configure one or
more source ports but
only one sink port for an
E-AGGR service.
Otherwise, configuration
of the E-AGGR service
will fail.

UNI ports.

VLANs 1 to 4094 - l This parameter

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 - - Setting this parameter is

not available.
NNI (PW) Parameters
Table B-11 Basic attributes

Location Sink - This parameter specifies

Source whether a port functions
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.
PW ID 1 to 4294967295 - This parameter specifies

the ID of a PW.
PW Status - - Displays whether a PW is

enabled.

PW Signaling Type Static Static This parameter displays

the signaling type of a
PW.
You need to allocate the
same PW label for both
ends of a static PW.
PW Type Ethernet Ethernet l This parameter

Ethernet Tagged Mode specifies whether P-
TAGs will be added
to Ethernet frames
when the Ethernet
frames are
encapsulated on a
PW.
l If Request VLAN
does not need to be
added to Ethernet
frames that are
encapsulated on a
PW, 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 E-
AGGR services on OptiX
RTN 900 do not support
PWs in Ethernet tagged
mode.

PW Encapsulation Type MPLS MPLS This parameter displays

the encapsulation type of
a PW.
PW Incoming Label 16 to 1048575 - This parameter specifies

the ingress label for a
PW.
PW Outgoing Label 16 to 1048575 - This parameter specifies

the egress label for a PW.

Tunnel Selection Mode - - This parameter displays

whether an existing
MPLS tunnel or a new
MPLS tunnel is used.
Tunnel Type - - This parameter displays

the type of a tunnel.
Peer LSR ID - - This parameter specifies

the LSR ID for the NE at
the opposite end of a PW.
If an existing MPLS
tunnel is used, the peer
LSR ID is automatically
generated based on the
local LSR ID.
Ingress Tunnel - - This parameter displays

the tunnel.
Egress Tunnel - - This parameter displays

the egress tunnel.

local end.



selection policy.

Table B-12 Advanced attributes


words when
encapsulating ETH
PWE3 packets (PWE3
stands for pseudo wire
emulation edge-to-edge).
NOTE
control words when
Description.
Control Channel Type Alert Label Alert Label This parameter specifies
None the control channel type,
which determines the PW
CW continuity check (CC)
mode.
l None: indicates that
virtual circuit
connectivity
verification (VCCV)
packets are not used.
l Alert Label: indicates
that VCCV packets in
Alert Label
encapsulation mode
are used.
VCCV packets
used.
VCCV Verification Ping Ping l This parameter

Mode None specifies the VCCV
verification mode,
which is used for a
PW CC test.
l If the LSP ping
function is used to
implement VCCV,
VCCV Verification
Mode cannot be set to
None.

Request VLAN - - Setting this parameter is

not available.
TPID - - Setting this parameter is

not available.
Parameters for a VLAN Forwarding Table


the network attribute for
a source port.

a source port.

the source VLAN ID.

the sink port.

the sink port.

the sink VLAN ID.
NOTE
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN forwarding table
needs to be configured, specifying the source and sink VLAN IDs of each VLAN-based service.
l A VLAN forwarding table enables VLAN ID swapping for an E-AGGR service. After a VLAN
forwarding table is created, a service from Source Interface will carry the VLAN ID specified in Sink
VLAN ID when leaving Sink Interface.
l For an E-AGGR service, the VLAN forwarding table specifies bidirectional VLAN ID swapping
relationships. This means that swapping from Sink VLAN ID to Source VLAN ID and swapping from
Source VLAN ID to Sink VLAN ID will be implemented once a VLAN forwarding entry for changing
Source VLAN ID to Sink VLAN ID is configured.
l For service aggregation from UNI ports to an NNI port, Source VLAN ID must take any of the VLAN
IDs that have been configured for UNI ports.
l For service aggregation from NNI ports to a UNI port, Sink VLAN ID must take any of the VLAN IDs
that have been configured for UNI ports.

QoS (PW)

the ID of a PW.

of a PW.
PW.
PW.

the type of a PW.

prevent network
congestion.
l For transmission
channels, the
bandwidth limit
function controls the
bandwidth of one or
more PWs as
required.
l For services, the
bandwidth limit
bandwidth of each
ETH PWE3 service in
an MPLS tunnel,
because an ETH
PWE3 service
corresponds to a PW.
Policy - - Setting this parameter is

not available.

or specifies the
The CIR is recommended
to be the same as the PIR.

CBS (Kbit/s) - - This parameter displays

or specifies the
(CBS) for a PW.
PIR (Kbit/s) - - This parameter displays

a PW.
The PIR is recommended
to be the same as the
CIR.
PBS (Kbit/s) - - This parameter displays

PW.
EXP - - Setting this parameter is

not available.
LSP Mode Pipe Pipe Pipe: When an egress

node strips off the MPLS
tunnel labels in the
received service packets,
it does not renew the
packet scheduling
priorities.
B.6.1.11 Parameter Description: E-AGGR Services

This topic describes E-AGGR service parameters.
Navigation Path
Configuration > Ethernet Service Management > E-AGGR Service from the
Function Tree.


the ID of an E-AGGR
service.

the name of an E-AGGR
service.

MTU(byte) - - Setting this parameter is

not available.
Service Tag Role - - Setting this parameter is

not available.

whether an E-AGGR
service has been
deployed.
UNI Parameters
ID - - This parameter displays

the ID of a UNI port.
Location - - This parameter displays

whether a port functions
sink.

UNI ports.
VLANs - - This parameter displays

the VLAN ID of a UNI
port.
Priority - - Setting this parameter is

not available.
NNI (PW) Parameters
Table B-13 Basic attributes
ID - - This parameter displays

the ID of an NNI port.
Location - - This parameter displays

whether a port functions
sink.

the ID of a PW.



the signaling type of a
PW.

the type of a PW.


the encapsulation type of
a PW.

the ingress label of a PW.

the egress label of a PW.

the LSR ID for the NE at
the opposite end of a PW.
Tunnel Type - - This parameter displays

the type of a tunnel.
Ingress Tunnel 16 to 1048575 - This parameter specifies

the ingress label for a
PW.
Egress Tunnel 16 to 1048575 - This parameter specifies

the egress label for a PW.
Control Word - - This parameter displays

whether the control word
is used.


Mode the VCCV verification
mode.
Local Operation Status - - This parameter displays

the PW running status at
the local end.
Local Operation Status - - This parameter displays

the PW running status at
the opposite end.

Overall Operation - - This parameter displays

Status the overall PW running
status.

the request VLAN ID.

selection policy.

not allow TPIDs in
request VLANs to be
specified for a PW.
Parameters for a VLAN Forwarding Table


a source port.

a source port.

the source VLAN ID.

the sink port.

the sink port.

the sink VLAN ID.

NOTE
l Regardless of whether VLAN ID swapping is required by an E-AGGR service, a VLAN forwarding table
needs to be configured, specifying the source and sink VLAN IDs of each VLAN-based service.
l A VLAN forwarding table enables VLAN ID swapping for an E-AGGR service. After a VLAN
forwarding table is created, a service from Source Interface will carry the VLAN ID specified in Sink
VLAN ID when leaving Sink Interface.
l For an E-AGGR service, the VLAN forwarding table specifies bidirectional VLAN ID swapping
relationships. This means that swapping from Sink VLAN ID to Source VLAN ID and swapping from
Source VLAN ID to Sink VLAN ID will be implemented once a VLAN forwarding entry for changing
Source VLAN ID to Sink VLAN ID is configured.
l For service aggregation from UNI ports to an NNI port, Source VLAN ID must take any of the VLAN
IDs that have been configured for UNI ports.
l For service aggregation from NNI ports to a UNI port, Sink VLAN ID must take any of the VLAN IDs
that have been configured for UNI ports.
QoS (PW)

the ID of a PW.

of a PW.
PW.
PW.

the type of a PW.


prevent network
congestion.
l For transmission
channels, the
bandwidth limit
bandwidth of one or
more PWs as
required.
l For services, the
bandwidth limit
bandwidth of each
ETH PWE3 service in
an MPLS tunnel,
because an ETH
PWE3 service
corresponds to a PW.
Policy - - Setting this parameter is

not available.

or specifies the
The CIR is recommended
to be the same as the PIR.
CBS (Kbit/s) - - This parameter displays

or specifies the
(CBS) for a PW.
PIR (Kbit/s) - - This parameter displays

a PW.
The PIR is recommended
to be the same as the
CIR.
PBS (Kbit/s) - - This parameter displays

PW.

EXP - - Setting this parameter is

not available.
LSP Mode Pipe Pipe Pipe: When an egress

node strips off the MPLS
tunnel labels in the
received service packets,
it does not renew the
packet scheduling
priorities.
B.6.2 Parameters for Ethernet Protocols

This topic describes the parameters that are related to the Ethernet protocol.
B.6.2.1 Parameter Description: ERPS Management_Creation

This topic describes the parameters that are used for creating ERPS management tasks.
Navigation Path
Ethernet Protection > ERPS Management.
2. Click New.
Parameters
ERPS ID 1 to 8 - l This parameter specifies the

ID of the Ethernet ring
protection switching (ERPS)
instance.
l The IDs of ERPS instances
on an NE must be different
from each other.

East Port - - This parameter specifies the east

port of the ERPS instance.
NOTE
plan the counterclockwise
direction as the main direction
of services transmission, and
plan the port that transmits
services in the main direction
as an east port, and the port that
receives services as a west port.
l Set East Port or West Port to
- for the sub-ring ERPS
instance on an interconnection
node.
West Port - - This parameter specifies the

west port of the ERPS instance.
NOTE
plan the counterclockwise
direction as the main direction
of services transmission, and
plan the port that transmits
services in the main direction
as an east port, and the port that
receives services as a west port.
l Set East Port or West Port to
- for the sub-ring ERPS
instance on an interconnection
node.
ERP Ring Node Flag None None l If the node is the RPL owner,
RPL Port set this parameter to RPL
Port.
Neighbor Port
l If the node is an RPL
Next Neighbor Port 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.

Flag Port - - l Set ERP Ring Node Flag

and Flag Port to matching
values according to the
network plan.
l One ERPS ring has only one
RPL Port and one
Neighbor Port.
set the east port of the RPL
owner to RPL Port and the
west port of the RPL
neighbor node to Neighbor
Port.
set the east port on RPL
owner node's upstream node
and the west port on the RPL
neighbor node's downstream
node as Next Neighbor
Port.
Revertive Mode Revertive Revertive This parameter generally takes

Non-Revertive the default value Revertive.
You can set this parameter to
Non-Revertive according to the
network plan.

Control VLAN 1 to 4094 - l This parameter specifies the

VLAN ID of Control
VLAN.
l Each node on the Ethernet
ring transmits the R-APS
packets on the dedicated ring
APS (R-APS) channel to
ensure consistency between
the nodes when the ERPS
switching is performed.
Control VLAN is used for
isolating the dedicated R-
APS channel. Therefore, the
VLAN ID in Control VLAN
cannot be duplicate with the
VLAN IDs that are
contained in the service
packets.
l The ID of a Control VLAN
must not be the same as any
VLAN ID used by Ethernet
services. All ring nodes
should use the same Control
VLAN ID.
Destination Node 01-19-A7-00-00-01 01-19- This parameter indicates the

A7-00-00-01 MAC address of the destination
node. The default destination
MAC address in the R-APS
packets is always 01-19-
A7-00-00-01.
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

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

Control VLAN 1 to 4094 - l This parameter

indicates or
specifies the
VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring
transmits the R-
APS packets on
the dedicated ring
APS (R-APS)
channel to ensure
consistency
between the
nodes when the
ERPS switching
is performed.
Control VLAN is
used for isolating
the dedicated R-
APS channel.
Therefore, the
VLAN ID in
Control VLAN
cannot be
duplicate with the
VLAN IDs that
are contained in
the service
packets or inband
DCN packets.
l The Control
VLAN must be
set to the same
value for all the
NEs on an ERPS
ring.
Destination Node 01-19-A7-00-00-01 - This parameter

indicates the MAC
address of the
destination node. The
default destination
MAC address in the
R-APS packets is
always 01-19-
A7-00-00-01.

Current Node - - This parameter

indicates the node
that initiates a
switching request.
Revertive Mode Revertive - This parameter

Non-Revertive indicates the
revertive mode and
can be reset.
Compatible_Version ver2 ver2 l This parameter

ver1 indicates the
configured
compatible ERPS
protocol version
and can be reset.
l For multi-ring
networks,
Compatible_Ver
sion for all ring
nodes must be
ver2.
l For single ring
networks,
Compatible_Ver
sion for ring
nodes except the
RPL owner can
be either ver1 or
ver2.
Compatible_Ver
sion for the RPL
owner must be
ver2.
Virtual Channel Status Enable Enable l This parameter

Disable indicates the
configured status
and VLAN ID of
an R-APS virtual
channel, and can
be reset.
l For details about
the value of this
parameter, refer
to Planning
Guidelines for R-
APS Virtual
Channels in the

Virtual Channel VLANs 1 to 4094 - Feature

Description.
Major ERPS Ring ID - - Set this parameter

only for the sub-ring
ERPS instance on an
interconnection node
to associate the sub-
ring ERPS instance
with the major ring
ERPS instance.
ETH Type Domain Transfer mode Transfer mode l If an ERP ring

Standard mode consists of OptiX
RTN and third-
party equipment
and the type
domain in R-APS
packets used by
the third-party
equipment is
0x8902, set ETH
Type Domain to
Standard mode
(Ox8902) for the
OptiX RTN
equipment.
l In other cases,
retain the default
value Transfer
mode (Ox8809)
for this parameter.

Hold-Off Time(ms) - 0 l This parameter

indicates or
specifies the hold-
off time of the
ERPS hold-off
timer.
l The hold-off
timer is used for
negotiating the
protection
switching
sequence when
the ERPS coexists
with other
protection
schemes so that
the fault can be
rectified in the
case of other
protection
switching (such
as LAG
protection) before
the ERPS occurs.
When a node on
the ring detects
one or more new
faults, it starts up
the hold-off timer
if the preset hold-
off time is set to a
value that is not
0. During the
hold-off time, the
fault is not
reported to trigger
an ERPS. When
the hold-off timer
times out, the
node checks the
link status
regardless
whether the fault
that triggers the
startup of the
timer exists. If the
fault exists, the
node reports it to
trigger an ERPS.
This fault can be

the same as or
different from the
fault that triggers
the initial startup
of the hold-off
timer.

Guard Time(ms) - 500 l This parameter

indicates or
specifies the
guard time of the
ERPS guard
timer.
l The nodes on the
ring continuously
forward the R-
APS packets to
the Ethernet ring.
As a result, the
outdated R-APS
packets may exist
on the ring
network. After a
node on the ring
receives the
outdated R-APS
packets, an
incorrect ERPS
may occur. The
ERPS guard timer
is an R-APS timer
used for
preventing a node
on the ring from
receiving
outdated R-APS
packets. When a
faulty node on the
ring detects that
the switching
condition is
cleared, the node
starts up the
guard timer and
starts to forward
the R-APS (NR)
packets. During
this period, the R-
APS packets
received by the
node are
discarded. The
received R-APS
packets are
forwarded only
after the time of

the guard timer

expires.

WTR Time(mm:ss) 1 to 12, in step of 1 5 l This parameter

indicates or
specifies the
WTR time of the
WRT timer in the
case of ERPS
protection.
l The WTR time
refers to the
duration from the
time when the
working channel
is restored to the
time when the
switching is
released. When
the working
channel is
restored, the
WTR timer of the
RPL owner starts
up. In addition, a
signal that
indicates the
operation of the
WTR timer is
continuously
output in the
timing process.
When the WTR
timer times out
and no switching
request of a
higher priority is
received, the
signal indicating
the operation of
the WTR timer is
not transmitted.
In addition, the
WTR release
signal is
continuously
output.
l The WTR timer is
used to prevent
frequent
switching caused
by the unstable
working channel.

Packet Transmit Interval(s) 1 to 10 5 This parameter

displays or specifies
the interval for
sending R-APS
packets periodically.
Entity Level 0 to 7 4 This parameter

the level of the
maintenance entity.
Last Switching Request - - This parameter

indicates the last
switching request.
RB Status - - This parameter

indicates the RB
(RPL Blocked) status
of the packets
received by the
working node.
l noRB: The RPL
is not blocked.
l RB: The RPL is
blocked.

DNF Status - - This parameter

indicates the DNF
status of the packets
received by the
working node.
l noDNF: The R-
APS packets do
not contain the
DNF flag. In this
case, the packets
are forwarded by
the node that
detects the fault
on a non-RPL
link, and the node
that receives the
packets is
requested to clear
the forwarding
address table.
l DNF: The R-APS
packets contain
the DNF flags. In
this case, the
packets are
forwarded by the
node that detects
the fault on an
RPL link, and the
node that receives
the packets is
informed not to
clear the
forwarding
address table.

State Machine Status - - This parameter

indicates the status of
the state machine at
the working node.
l Idle: The Ethernet
ring is in normal
state. For
example, no node
on the Ethernet
ring detects any
faults or receives
the R_APS (NR,
RB) packets.
l Protection: The
Ethernet ring is in
protected state.
For example, a
fault on the node
triggers the
ERPS, or a node
on the ring is in
the WTR period
after the fault is
rectified.
Node Carried with Current Packet - - This parameter

indicates the MAC
address carried in the
R-APS packets
received by the
current node. The
MAC address refers
to the MAC address
of the source node
that initiates the
switching request.
East Port Status - - 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 sub-
ring.

Bound MEP - - This parameter

specifies the MEP
with which a sub-
ring port is bound. It
applies to only an
ERPS sub-ring.
Interconnected Node None None l This parameter

Primary specifies the
interconnection
Secondary node attribute. It
Multi-point Failure Disable Disable applies to only an
ERPS sub-ring.
Primary
l After multiple
Secondary
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 Multi-
point 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
Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
2. Click the Port Group Parameters tab.
3. Click Create.


Protocol Type MSTP MSTP This parameter specifies

STP the protocol type.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports the CIST
MSTP only.
l STP: stands for
Spanning Tree
Protocol.
Enable Protocol Enabled Disabled This parameter specifies

Disabled whether to enable the
protocol of the port group
or a member port in the
port group.
Parameters for Application Ports


the board where the
member of port group is
located.
Available Port - - This parameter indicates

the available port list in
which a port can be
added to the port group.
Selected Port - - This parameter indicates

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

2. Click the Port Group Parameters tab.

3. On the main interface, select the port group to be configured.
4. Click Config. The Config Port Group dialog box is displayed.
Parameters for the Added Port


the board where the
member of port group is
located.
Available Port List - - This parameter indicates

the available port list in
which a port needs to be
added to the port group.
Selected Port List - - This parameter indicates

the selected ports that
need to be added to the
port group.
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters

This topic describes the parameters that are related to MSTP bridges.
Navigation Path

Port Group ID - - l This parameter

port group.
set to only the port
group ID that is
automatically
allocated.
MST Domain Name - - The OptiX RTN 900 does

not support this
parameter.

Redaction Level - - The OptiX RTN 900 does

not support this
parameter.
Mapping List - - The OptiX RTN 900 does

not support this
parameter.
Bridge Parameters
Port Group ID - - l This parameter

port group.
set to only the port
Group ID that is
automatically
allocated.
MST Domain Max Hop - 20 Specifies the maximum

Count hop count of the MSTP.
Network Diameter 2 to 7 7 l This parameter

specifies the MSTP
network diameter.
l If the value of
Network Diameter is
greater, the network is
in a larger scale.
Hello Time(s) 1 to 10 2 l This parameter

specifies the interval
for transmitting the
CBPDU packets
through the bridge.
l The greater the value
of this parameter, the
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.

Max Age(s) 6 to 40 20 l This parameter

specifies the
maximum age of the
CBPDU packet that is
recorded by the port.
l The greater the value,
the longer the
transmission distance
of the CBPDU, which
indicates that the
network diameter is
greater. When the
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

the port in the port group.

Enable Edge Attribute Disabled Disabled l This parameter

Enabled specifies the
management edge
attributes of the port.
set to Enabled only
when the port is
directly connected to
the data
communications
terminal equipment,
such as a computer. In
other cases, it is
recommended that
you use the default
value.
Actual Edge Attribute - - This parameter indicates

the actual management
edge attributes of the
port.

Point-to-Point Attribute false auto l This parameter

true specifies the point-to-
point attribute of the
auto port.
l false: forced non-
point-to-point link
attribute
l true: forced point-to-
point link attribute
l auto: automatically
detected point-to-
to auto, the bridge
determines Actual
Point-to-Point
Attribute of the port
according to the
actual working mode.
If the actual working
mode is full-duplex,
the actual point-to-
point 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 - - This parameter indicates

Attribute the actual point-to-point
attribute of the port.

Max Transmit Packet 1 to 255 3 l This parameter

Count specifies the
maximum number of
packets to be
transmitted.
l The maximum
number of packets to
be transmitted by the
port refers to the
maximum number of
MSTP packets that
the port can transmit
within 1s.
l This parameter needs
to be set according to
the planning
information.
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters

This topic describes the parameters that are related to the MSTP CIST.
Navigation Path
2. Click the CIST&MSTI Parameters tab.

Port Group - - This parameter specifies

the port group.
MSTI ID 0 0 This parameter indicates

the MSTI ID. The value
0 indicates common and
internal spanning tree
(CIST). The OptiX RTN
900 supports only the
MSTP that uses CIST.

Bridge Priority 0 to 61440, in step of 32768 l The most significant

4096 16 bits of the bridge
ID indicate the
priority of the bridge.
l When the value is
smaller, the priority is
higher. As a result, the
bridge is more
possible to be selected
as the root bridge.
l If the priorities of all
the bridges in the
STP/MSTP network
use the same value,
the bridge whose
MAC address is the
smallest is selected as
the root bridge.
Port Parameters

Priority 0 to 240, in step of 16 128 l The most significant

eight bits of the port
ID indicate the port
priority.
l When the value is
higher.
Path Cost 1 to 200000000 FE Port: 200000 l This parameter

GE Port: 20000 indicates the status of
the network that the
port is connected to.
l In the case of the
bridges on both ends
of the path, set this
parameter to the same
value.

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
2. Click the CIST Running Information tab.

Port Group ID - - This parameter indicates

the ID of the port group.
Protocol Running Mode MSTP - l This parameter

STP indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.

Bridge Priority 0 to 61440, in step of 32768 l This parameter

4096 indicates the priority
of the bridge.
l The most significant
16 bits 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 - - This parameter indicates

the MAC address of the
bridge.
Root Bridge Priority 0 to 61440, in step of 32768 This parameter indicates

4096 the priority of the root
bridge.
Root Bridge MAC - - This parameter indicates

Address the MAC address of the
root bridge.
External Path Cost - - The OptiX RTN 900 does

ERPC not support this
parameter.
Domain Root Bridge - - The OptiX RTN 900 does

Priority not support this
parameter.
Domain Root Bridge - - The OptiX RTN 900 does

MAC Address not support this
parameter.
Internal Path Cost - - The OptiX RTN 900 does

IRPC not support this
parameter.

Root Port Priority 0 to 240, in step of 16 128 l This parameter

indicates the priority
of the root port.
l The most significant
eight bits of the ID of
the root port indicate
the priority of the root
port.
l When the value is
higher.
Root Port - - This parameter indicates

the root port.
Hello Time(s) - 2 l This parameter

indicates the interval
for transmitting
CBPDU packets
through the bridge.
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.

specifies the
maximum age of the
the longer the
of the CBPDU, which
indicates that the
network diameter is
greater. When the
value of this
manner and thus the
network adaptation
ability is reduced.


specifies the holdoff
the learning state.
the network state
change. Hence, the
slower and the
MST Domain Max Hop - - This parameter indicates

Count the maximum hop count
of the MSTP.
Topology Change - - This parameter indicates

Identifier the identifier of the
topology change.
Last Topology Change - - This parameter indicates

Time(s) the duration of the last
topology change.
Topology Change Count - - This parameter indicates

the count of the topology
changes.
Port Parameters

Enable Protocol Enabled Disabled This parameter indicates

Disabled whether the protocol of
the port group or a
member of the port group
is enabled.
Port Role - Disabled This parameter indicates

the role of a port.

Port Status Discarding Discarding This parameter indicates

Learning the state of a port.
Forwarding l Discarding: receives
only BPDU packets
l Learning: only
receives or transmits
BPDU packets
l Forwarding: forwards
user traffic, and
transmits/receives
BPDU packets
Priority 0 to 240, in step of 16 128 l The most significant

eight bits of the port
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 0 to 61440, in step of 32768 l The most significant

4096 16 bits 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 - - This parameter indicates

bridge.
Designated Port 0 to 240, in step of 16 0 l The most significant

Priority eight bits of the port
priority.
l When the value is
higher.
Design Port - 0 This parameter indicates

the designated port.
Edge Port Attribute Disabled Disabled l This parameter

Enabled specifies the
management edge
attributes of the port.
l This parameter
specifies whether to
set the port as an edge
port. The edge port
refers to the bridge
port that is connected
to the LAN. In normal
cases, this port does
not receive or
transmit BPDU
messages.
set to Enabled only
when the port is
directly connected to
the data
communications
terminal equipment,
such as a computer. In
other cases, it is
recommended that
you use the default
value.
Actual Edge Port - Disabled This parameter indicates

Attribute the actual management
edge attributes of the
port.

Point to Point false auto l This parameter

true specifies the point-to-
point attribute of the
auto port.
l false: forced non-
point-to-point link
attribute
l true: forced point-to-
l auto: automatically
detected point-to-
to auto, the bridge
determines Actual
Point to Point
Attribute of the port
according to the
actual working mode.
mode is full-duplex,
the actual point-to-
point 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 - - This parameter indicates

the actual point-to-point
attribute of the port.

Max Count of 1 to 255 3 l This parameter

Transmitting Message indicates the
maximum number of
packets to be
transmitted.
l The maximum
number of packets to
be transmitted by the
port refers to the
maximum number of
MSTP packets that
the port can transmit
within 1s.
Protocol Running Mode STP - l This parameter

MSTP indicates the running
mode of the protocol.
l MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
l STP: stands for
Spanning Tree
Protocol.
Hello Time(s) 1 to 10 2 l This parameter

indicates the interval
for transmitting the
CBPDU packets
through the bridge.
less the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.


specifies the
maximum age of the
the longer the
of the CBPDU, which
indicates that the
network diameter is
greater. When the
value of this
manner and thus the
network adaptation
ability is reduced.

specifies the holding
the learning state.
the network state
change. Hence, the
slower and the
Remain Hop - - The OptiX RTN 900 does

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

Navigation Path
Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function
Tree.
2. Click the Protocol Configuration tab.

Service ID - - This parameter indicates

the service ID.
Enabled Protocol Enabled Disabled l This parameter

Disabled specifies whether to
enable the IGMP
Snooping protocol.
l If the bridge accesses
a LAN where the
IGMP multicast
server exists, you can
enable the IGMP
Snooping protocol
according to the
requirement.

Router Port Aging 1 to 120 8 l If an entry is not

Time(min) updated in a certain
period (that is, no
IGMP query packet is
received), this entry is
This mechanism is
called aging, and this
period is called aging
time.
to a very large value,
the bridge stores
excessive multicast
entries that are
outdated.
Consequently, the
resources of the
multicast table are
exhausted.
to a very small value,
the bridge may delete
the multicast entry
that is required.
Consequently, the
forwarding efficiency
decreases.

Max Nonresponse 1 to 4 3 l This parameter

Times from Multicast specifies the
Members maximum number of
multicast group
members who do not
respond.
l If the IEEE 802.1q
bridge transmits an
IGMP group query
packet to the
multicast member
ports, the IEEE
802.1q bridge starts
the timer for the query
of the maximum
number of responses.
If no IGMP report
packets are received
within the query time,
the IEEE 802.1q
bridge adds one to the
number of no
responses at the port.
When the number of
no responses exceeds
the preset value of
Maximum Times of
No Response from
Multicast Members,
the IEEE 802.1q
bridge deletes the
additional multicast
members from the
multicast group.
Maximum Multicast 1 512 l This parameter

Groups 128 specifies the
maximum number of
256 allowable multicast
512 groups.
Unlimited l The multicast group
records the mapping
relationships between
the ports on the
router, MAC
multicast addresses,
and member ports in
the multicast group.

Maximum Number of 1 1024 l This parameter

Multicast Group 128 specifies the
Members maximum number of
256 allowable multicast
512 group members.
1024 l A multicast group
Unlimited member refers to the
host that is added to a
multicast group.
Actual Multicast Count - - This parameter indicates

the number of actually
used multicast groups.
Actual Multicast - - This parameter indicates

Members Count the number of actually
used multicast group
members.
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
Tree.
2. Click the Protocol Config tab.
3. Click Add.
Parameters for Fast Leave Ports


the service ID.

VLAN ID 1 to 4094 1 l This parameter

specifies the VLAN
where the port to be
quickly deleted is
located.
the planning
information.
Port Type V-UNI V-UNI l This parameter

V-NNI specifies the type of
the port to be quickly
deleted.
the planning
information.

the port to be quickly
deleted.
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
Tree.
2. Click the Router Port Management tab.
Parameters for Router Port Management

Service ID - - This parameter specifies

the ID of the created E-
LAN service.


the VLAN ID of the
router port.
Port Type - - This parameter indicates

the type of the router
port.

the router port.
Port Status - - This parameter indicates

the status of the router
port.
Port Created AT - - This parameter indicates

the time when the router
port is created.
Port Remainder Aging - - This parameter indicates

Time(min) the remaining aging time
of the router port.
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
Tree.
2. Click the Route Management tab.
3. Click New.
Parameters for Router Port Creation


LAN service.

VLAN ID 1 to 4094 1 This parameter indicates

the VLAN ID of the
router port.

the available ports.

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
Tree.
2. Click the Route Member Port Management tab.
Parameters for Multicast Groups Information


LAN service.

the VLAN ID of the
multicast group.
Multicast MAC Address - - This parameter indicates

the multicast MAC
address.
Multicast Groups Type - - This parameter indicates

the type of the multicast
group.
Multicast Group - - This parameter indicates

Creating Time the time when the
multicast group is set up.

Parameters for Multicast Group Members Information


LAN service.

the VLAN ID of the
multicast group member.

the type of the multicast
group member.

the multicast group
member port.
Port Remainder Aging - - This parameter indicates

Times the remaining non-
response times of the
multicast group member
port.
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
Tree.
2. Click the Route Member Port Management tab.
3. Click New.

Parameters for Router Port Creation


LAN service.
VLAN ID 1 to 4094 1 This parameter specifies

the VLAN ID of the
multicast group.
Multicast MAC Address - - This parameter specifies

the multicast MAC
address.

the available interfaces.

the preset port of the
multicast group
members.
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
Tree.
2. Click the Data Count tab.
Parameters for Routing Member Interface Management


the service ID.

the VLAN ID of the
service.

the port type.


the port.
Packet Statistic Status Clear Clear This parameter indicates

Start or specifies the status of
collecting the packet
Stop statistics.
IGMPv1 Query Packet - - This parameter indicates

Count the number of received
IGMPv1 query packets.


IGMP Leaving Packet - - This parameter displays

Count the number of leaving
packets that are received.
IGMPv1 Member - - This parameter indicates

Report Packet Count the number of received
packets that are reported
by the IGMPv1
members.

by the IGMPv2
members.

by the IGMPv3
members.
Unrecognized or - - This parameter indicates

Unprocessed Packet the number of packets
Count that cannot be recognized
or processed.
Discarded Incorrect - - This parameter indicates

Packet Count the number of discarded
error packets.

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
Interface Management > Link Aggregation Group Management from the Function
Tree.
2. Click the Link Aggregation Group Management tab.
3. Click New.

LAG No. - 1 l This parameter

specifies the LAG
number to be set
manually.
l This parameter is
valid only when
Automatically
Assign is not selected.
Automatically Assign Selected Selected l This parameter

LAG No. is allocated
automatically.
l When Automatically
Assign is selected,
LAG No. cannot be
set.
LAG Name - - This parameter specifies

the LAG name.

LAG Type Static Static l Static: You can create

Manual a LAG. When you
add or delete a
member port to or
from the LAG, the
Link Aggregation
Control Protocol
(LACP) protocol is
required. In a LAG, a
port can be in
selected, standby, or
unselected state. The
aggregation
information is
exchanged among
different equipment
through the LACP
protocol to ensure that
the aggregation
information is the
same among all the
nodes.
l Manual: You can
create a LAG. When
you add or delete a
member port, the
LACP protocol is not
required. The port can
be in the up or down
state. The system
determines whether to
aggregate a port
according to its
physical state (UP or
DOWN), working
mode, and rate.
Switch Protocol - - OptiX RTN 900 does not

Switch Mode - - OptiX RTN 900 does not

Link Detection Protocol Null Null This parameter is set

802.3ah according to the planning
information.

Revertive Mode Revertive Mode Non-Revertive Mode l Revertive Mode can

Non-Revertive Mode be set only when
Load Sharing is set
to Non-Sharing.
l When Revertive
Mode is set to
Revertive Mode, the
services are switched
back to the former
working channel after
this channel is
restored to normal.
l When Revertive
Mode is set to Non-
Revertive Mode, the
status of the LAG
does not change after
the former working
channel is restored to
normal. That is, the
services are still
transmitted on the
protection channel.

Load Sharing Sharing Non-Sharing l Set Load Sharing to

Non-Sharing the same value as the
peer equipment. It is
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 Sharing: Each
member link of a
LAG processes traffic
at the same time and
shares the traffic load.
The sharing mode can
increase a bandwidth
utilization for the link.
When the LAG
members change, or
certain links fail, the
system automatically
re-allocates the traffic.
l Non-Sharing: Only
one member link of a
LAG carries traffic,
and the other link is in
the standby state. In
this case, a hot backup
mechanism is
provided. When the
active link of a LAG
is faulty, the system
activates the standby
link, preventing link
failure.
Load Sharing Hash - - Set this parameter in the

Algorithm Link Aggregation
Parameters tab page.

System Priority 0 to 65535 32768 l System Priority

of a LAG. The
smaller the value of
System Priority, the
higher the priority.
l When a local LAG
negotiates with an
opposite LAG
through LACP
packets, both LAGs
can obtain the system
priorities of each
other. Then, the LAG
of the higher system
priority is considered
as the comparison
result of both LAGs
so that the
aggregation
information is
consistent at both
LAGs. If the priorities
of both LAGs are the
same, the system
MAC addresses are
compared. Then, the
comparison result
based on the LAG
with smaller system
MAC address is
considered as the
result of both LAGs
and is used to ensure
that the aggregation
information is
consistent at both
LAGs.
WTR Time(min) 0 to 30 10 l Specifies the WTR

time for the LAG.
l WTR Time(min)
takes effect only when
Revertive Mode is
Revertive Mode.

Switch LAG upon Air Disabled Disabled l This parameter

Interface SD Enabled specifies whether to
enable the switching
triggered by bit errors.
l If Switch LAG upon
Air Interface SD is
set to Enabled, the
MW_BER_SD 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 air-
interface LAG.
Packet Receive Timeout Short period Short period l A LAG switching is

Period Long period triggered if no LACP
packet is received
after Packet Receive
Timeout Period
times out.
l When LACP protocol
packets pass through
an intermediate
network, it is
recommended to set
Packet Receive
Timeout Period to
Short period. In
other scenarios, set it
to Long period to
avoid mistaken
switching.
l This parameter is
supported only when
LAG Type is set to
Static.

LAG Min Active Link - 1 To trigger ERPS

Threshold switching upon failure of
a member link in a LAG
when LAG and ERPS
coexist, LAG Min
Active Link Threshold
must be set to the total
number of links in the
LAG.
Port Settings Parameters

Main Board - - l This parameter

specifies the main
board in a LAG.
according to the
Main Port - - l This parameter

specifies the main
port in a LAG.
l After a LAG is
created, you can add
Ethernet services to
the main port only.
Services cannot be
added to a slave port.
When Load Sharing
is set to Non-
Sharing, the link
connected to the main
port is used to
transmit the services,
and the link
connected to the slave
port is used for
protection.
Board (Available Slave - - l This parameter

Ports) specifies the slave
board in a LAG.
according to the

Port (Available Slave - - l This parameter

Ports) specifies the slave
port in a LAG.
l The slave ports in a
LAG are fixed.
Unless they are
manually modified,
the system does not
automatically add
them to or delete them
from the LAG.
Selected Standby Ports - - This parameter indicates

the selected slave ports.
B.6.2.16 Parameter Description: Ethernet Link Aggregation_Link Aggregation

This section describes the parameters for configuring the port priority and system load-
sharing hash algorithm.
Navigation Path
Interface Management > Link Aggregation Group Management from the Function
Tree.
2. Click the Link Aggregation Parameters tab.


the port whose priority
can be set.
Port Priority 0 to 65535 32768 l This parameter

indicates the priorities
of the ports in a LAG
as defined in the
LACP protocol. The
smaller the value, the
l When ports are added
into a LAG, the port
of the highest priority
is preferred for
service transmission.

Load Sharing Hash Automatic Automatic l System Load

Algorithm Source MAC Sharing Hash
Algorithm is valid
Destination MAC only when Load
Source and Destination Sharing of a LAG is
MACs set to Sharing.
Source IP Address l The load sharing
Destination IP Address computation methods
include algorithm
Source and Destination IP
auto-sensing,
Address
computation based on
MPLS Label MAC addresses
(based on the source
MAC address, based
on the destination
MAC address, and
based on the source
MAC address + sink
MAC address),
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 UNI-
NNI 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.

Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT
Management > Simple LPT from the Function Tree.
2. Click New.
Parameters for Convergence Points

Board - - This parameter specifies the board at the

convergence point.
Port - - This parameter specifies the port on the

board of the convergence point.
NOTE
One port can be in an LPT only.
Parameters for Access Points

Board - - This parameter specifies the board at the

access point.
Port - - This parameter specifies the port on the

board of the access point.
NOTE
The access point supports selection of multiple
ports on different boards.
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
2. Click the Point-to-Point LPT tab.
Parameters on the main interface

Binding Status - - This parameter displays

the binding status of
point-to-point services.

Primary Function Point - - This parameter displays

the port where the
primary point of point-to-
point LPT resides.
Secondary Function - - This parameter displays

Point Type the type of secondary
point for point-to-point
LPT.

Point the port where the
secondary point of point-
to-point LPT resides.
LPT Instance Status - - This parameter displays

the status of point-to-
point LPT.
LPT Enabled Enabled Disabled This parameter displays

Disabled or specifies the enabling
status of point-to-point
LPT.
The LPT function can
take effect only when
LPT Enabled is set to
Enabled.
Recovery Times(s) 1-600 1 This parameter displays

or specifies the recovery
time of point-to-point
LPT.
Hold-Off Times(ms) 0-10000 1000 This parameter displays

or specifies the hold-off
time of point-to-point
LPT.
Switching Mode - - This parameter displays

the switching mode of
point-to-point LPT.
Point-to-point LPT is
available only in strict
mode.

Fault Detection Mode PW OAM LPT OAM This parameter displays

LPT OAM the fault detection mode
of point-to-multipoint
LPT.
l LPT-enabled NEs
periodically transmit
LPT OAM packets in
specific formats to
check the status of an
L2 service network or
QinQ service network.
If the LPT OAM
packets are absent for
3.5 fault detection
periods or the number
and contents of
received LPT OAM
packets are incorrect,
the NEs consider that
a network-side fault
occurred and the LPT
l To detect a network-
side fault on a PSN,
LPT OAM or PW
OAM packets can be
used. Note that the
PW OAM function
must be enabled on
NEs before usage of
PW OAM packets.
Fault Detection 10-100 10 This parameter displays

Period(100ms) or specifies the fault
detection period of point-
to-point LPT.
User-Side Port Status - - This parameter displays

the status of a user-side
port.
L2 net ID-L2 Peer net - - This parameter displays

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.

Navigation Path
2. Click the Point-to-Point LPT tab.
3. Click Bind in the lower right corner of the pane based on the type of service network.
4. Choose PW+QinQ or L2 net from the shortcut menu based on the type of service
network.

L2 net ID 1-4294967295 - This parameter specifies

the NET ID of LPT
packet out port at the
local end.
L2 Peer net ID 1-4294967295 - This parameter specifies

the NET ID of LPT
packet out port at the
opposite end.
Primary Function Point - - This parameter specifies

the port where the
point LPT resides.
VLAN ID 1-4094 - This parameter specifies

the VLAN ID that is
carried by a point-to-
point LPT packet to
traverse an L2 network.
LPT package out port - - This parameter specifies

the out port of a point-to-
point LPT packet.
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
2. Click the Point-to-Multipoint LPT tab.

Parameters of Primary Point


Type the type of primary point
for point-to-multipoint
LPT.

the port where the
multipoint LPT resides.
LPT Instance Status - - This parameter displays

the status of point-to-
multipoint LPT.
LPT Enabled Enabled Disabled This parameter displays

point-to-multipoint LPT.
Recovery Times(s) 1-600 1 This parameter displays

or specifies the recovery
time of point-to-
multipoint LPT.
Hold-Off Times(ms) 0-10000 1000 This parameter displays

or specifies the hold-off
time of point-to-
multipoint LPT.
Switching Mode Strict mode Strict mode This parameter displays

Non-strict mode the switching mode of
point-to-multipoint LPT.
Point-to-point LPT is
available only in strict
mode.
l Strict mode
A primary point
triggers LPT
switching when all its
secondary points
detect faults.
l Non-strict mode
A primary point
triggers LPT
switching when
anyone of its
secondary points
detects a fault.

Fault Detection Mode PW OAM LPT OAM This parameter displays

LPT OAM the fault detection mode
of point-to-multipoint
LPT.
l LPT-enabled NEs
periodically transmit
LPT OAM packets in
specific formats to
check the status of an
L2 service network or
QinQ service network.
If the LPT OAM
packets are absent for
3.5 fault detection
periods or the number
and contents of
received LPT OAM
packets are incorrect,
the NEs consider that
a network-side fault
occurred and the LPT
l To detect a network-
side fault on a PSN,
LPT OAM or PW
OAM packets can be
used. Note that the
PW OAM function
must be enabled on
NEs before usage of
PW OAM packets.
Fault Detection 10-100 10 This parameter displays

Period(100ms) or specifies the fault
detection period of point-
to-multipoint LPT.

port.

ends, when the service
network is an L2
network.

Parameters of Secondary Point


Point Type the type of second point
LPT.
Sencondary Function - - This parameter displays

Point the port or PW ID for the
to-multipoint LPT.

port.

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
2. Click the Point-to-Multipoint LPT tab.
3. Click New in the lower right corner of the pane based on the type of service network.
4. Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service
network.

Parameters of primary point

Point Type UNI - This parameter specifies

PW the type of primary point
QinQ LPT. The value range of
L2 net this parameter pertains to
the type of service
network.
If the primary point is on
the access side, select
UNI; if the primary point
is on the network side, set
the parameter as follows.
l If the service network
is a PSN, select PW.
is a QinQ network,
select QinQ.
is an L2 network,
select L2 net.

the board where the
This parameter is valid
only when Point Type is
set to UNI.

the port where the
set to UNI.
Point ID - - This parameter specifies

the service ID for the
multipoint LPT.
set to PW or QinQ.


the NET ID of a local
NE.
only when Point Type of
the primary point is set to
UNI, and when Point
Type of the secondary
point is set to L2 net.

the NET ID of an
opposite NE.
set to L2 net.

the VLAN ID that is
carried by an LPT packet
to traverse an L2
network.
set to L2 net.
LPT package out port - - This parameter specifies

the out port of an LPT
packet.
set to L2 net.
Parameters of secondary point

Point Type UNI - This parameter displays

PW or specifies the type of
secondary point for point-
QinQ to-multipoint LPT.
L2 net


the board where the
to-multipoint LPT
resides.
set to PW, QinQ, or L2
net.
Available Points - - This parameter displays

the available ports where
the secondary point of
point-to-multipoint LPT
can reside.
net.
Selected Points - - This parameter displays

the selected port where
the secondary point of
point-to-multipoint LPT
resides.
net.

the NET ID of a local
NE.
set to UNI.

the NET ID of an
opposite NE.
UNI, and when Point


the VLAN ID that is
carried by an LPT packet
to traverse an L2
network.
UNI, and when Point
LPT Package out port - - This parameter specifies

the out port of an LPT
packet.
UNI, and when Point
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
Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Click the Maintenance Association tab.
3. Choose New > New Maintenance Domain.


Maintenance - default l This parameter specifies the name of

Domain Name 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 0 4 l Maintenance Domain Level specifies

Domain Level 1 the level of the maintenance domain.
2 l The values 0 to 7 indicates maintenance
domain levels in an ascending order.
3
l MEPs transparently transmit OAM
4 protocol packets if the packets have a
5 higher level than the parameter value.
6 l MEPs discard OAM protocol packets if
7 the packets have a lower level than the
parameter value.
l MEPs respond to or terminate OAM
protocol packets based on the packet
type if the packets have the same level
as the parameter value.
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
Function Tree.
3. Select the maintenance domain in which a maintenance association needs to be created.
Choose New > New Maintenance Association.

Maintenance - - This parameter indicates the maintenance

Domain Name domain of the created maintenance
association.

Maintenance - - l This parameter specifies the name of

Association Name 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 3.33ms 1s l This parameter specifies the interval for

Period 10ms transmitting packets in the CC.
100ms l The CC is performed to check the
availability of the service.
1s
10s
1m
10m
Protocol/Standard 802.1ag 802.1ag When the Ethernet service OAM based on

Y.1731 IEEE 802.1ag is adopted, set Protocol/
Standard to 802.1ag. When the Ethernet
service OAM based on ITU-T Y.1731 is
adopted, set Protocol/Standard to Y.1731
and set MEGs and MPs according to the
plan.
MEG ID - - When the protocol is Y.1731, set this

parameter according to the plan.
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
Function Tree.
3. Select the maintenance association in which an MEP needs to be created. Choose New >
New MEP Point.



Domain Name domain of the created MEP.

Association Name association of the created MEP.
Board - - This parameter specifies the board where

the MEP is located.
Port - - This parameter specifies the port where the

MEP is located.
VLAN - - This parameter indicates the VLAN ID of

the current service.
MP ID 1 to 2048 1 l This parameter specifies the MEP ID.

l Each MEP needs to be configured with
an MP ID, which is unique in the
maintenance association. The MP ID is
required in the OAM operation.
Direction Ingress Ingress l Direction specifies the direction of the

Egress MEP.
l Ingress indicates the direction in which
the packets are transmitted to the port,
and Egress indicates the direction in
which the packets are transmitted from
the port.
CC Status Active Active l This parameter specifies whether to

Inactive enable the CC function of the MEP.
l In the case of the tests based on the MP
IDs, CC Status must be set to Active.
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
Function Tree.
3. Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point dialog
box is displayed.

4. Click New.


Domain Name domain of the MEP.

Association Name association of the created MEP.
Remote 1 to 2048 - l This parameter specifies the ID of the

Maintenance Point remote MEP.
ID(e.g:1,3-6) l If other MEPs will initiate OAM
operations to an MEP in the same MA,
set these MEPs as remote MEPs.
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
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.


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.

MIP ID 1 to 2048 1 l This parameter specifies the MIP ID.

l Each MIP needs to be configured with
an MP ID, which is unique in the
maintenance domain. The MP ID is
required in the OAM operation.
NOTE
To create MEPs and MIPs in a service at a
port, ensure that only one MIP can be
created and the level of the MIP must be
higher than the level of the MEP.
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
Function Tree.
3. Select the maintenance domain and maintenance association for the LB test.
4. Choose OAM > Start LB.

Destination Selected Deselected This parameter needs to be selected if the

Maintenance Point Deselected LB test is performed on the basis of
ID Destination Maintenance Point IDs.
Destination Selected Selected This parameter needs to be selected if the

Maintenance Point Deselected LB test is performed on the basis of MAC
MAC Address addresses.
Maintenance - - This parameter indicates the name of the

Domain Name maintenance domain for the LB test.

Association Name maintenance association for the LB test.
Source - - l This parameter specifies the source

Maintenance Point maintenance point in the LB test.
ID l Only the MEP can be set to the source
maintenance point.

Destination - - l This parameter specifies the destination

Maintenance Point maintenance point in the LB test.
ID l Only the MEP ID can be set to the
Destination Maintenance Point ID.
l Destination Maintenance Point ID
can be set only when MP ID is
selected.
Destination - 00-00-00-00-00-00 l This parameter specifies the MAC

Maintenance Point address of the port where the
MAC Address 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 1 to 255 3 l This parameter specifies the number of

Packet Count packets transmitted each time in the LB
test.
l When the value is greater, the required
duration is longer.
Transmitted 64 to 1400 64 l This parameter specifies the length of a

Packet Length transmitted LBM packet.
l If the packet length is different, the test
result may be different. In normal
cases, it is recommended that you use
the default value.
Transmitted 0 to 7 7 l This parameter specifies the priority of

Packet Priority transmitting packets.
l 0 indicates the lowest priority, and 7
indicates the highest priority. In normal
cases, this parameter is set to the
highest priority.
Detection Result - - This parameter indicates the relevant

information and result of the LB test.
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

This topic describes the parameters that are used for enabling the LT.

Navigation Path
Function Tree.
3. Select the maintenance domain and maintenance association for the LT test.
4. Choose OAM > Start LT.
Test Node Parameters

Destination Selected Deselected This parameter needs to be selected if the

Maintenance Point Deselected LT test is performed on the basis of MP
ID IDs.
Destination Selected Selected This parameter needs to be selected if the

Maintenance Point Deselected LT test is performed on the basis of MAC
MAC Address addresses.

Domain Name maintenance domain for the LT test.

Association Name maintenance association for the LT test.
Source - - l This parameter specifies the source

Maintenance Point maintenance point in the LT test.
ID l Only the MEP can be set to the source
maintenance point.
Destination - - l This parameter specifies the destination

ID l Only the MEP ID can be set to the
Destination Maintenance Point ID.
l Destination Maintenance Point ID
can be set only when MP ID is
selected.
Destination - 00-00-00-00-00-00 l This parameter specifies the MAC

Maintenance Point address of the port where the
MAC Address destination maintenance point is
located in the LT test.
l Only the MAC address of the MEP can
be set to the MAC address of the
Destination Maintenance Point MAC
Address.
l Destination Maintenance Point MAC
Address can be set only when Sink

Parameters for the Detection Result

Source - - This parameter indicates the source

ID
Destination - - This parameter indicates the MAC address

Maintenance Point of the port where the destination
ID/MAC maintenance point is located in the LT test.
Response - - This parameter indicates the MAC address

Maintenance Point of the port where the responding
ID/MAC maintenance point is located in the LT test.
Hop Count 1 to 64 - l This parameter indicates the number of

hops from the source maintenance
point to the responding maintenance
point or to the destination maintenance
point in the LT test.
l The number of hops indicates the
adjacent relation between the
responding maintenance point to the
source maintenance point. The number
of hops increases by one when a
responding point occurs on the link
from the source maintenance point to
the destination maintenance point.
Test Result - - This parameter indicates the result of the

LT test.
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.

Parameters for Enabling Service Loopback Detection

Vlans/CVLAN 1 to 4094 1 to 4094 Vlans/CVLAN displays

the VLAN ID of a
loopback service.
Loopback detection can
be performed for only
one service one time.
Packet Timeout 3 to 10 3 Loopback detection stops

Period(s) if no loopback detection
packets are received until
Packet Timeout
Period(s) expires.
Packet Length - - This parameter displays

the loopback detection
packet length.
VLAN Packet Sending - - This parameter displays

Interval(s) the intervals for
transmitting different
VLAN packets.
Disable Service When No No Disable Service When

Loopback is Detected Yes Loopback is Detected
displays whether a
loopback service will be
deactivated.
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
Ethernet OAM Management > Ethernet Port OAM Management from the Function
Tree.
2. Click the OAM Parameter tab.

Range Value
Port - - This parameter indicates the

corresponding port.


Range Value
Enable OAM Protocol Enabled Disabled l This parameter indicates

Disabled or specifies whether to
enable the OAM
protocol.
l After the OAM protocol
is enabled, the current
Ethernet port starts to use
the preset mode to create
the OAM connection
with the opposite end.
OAM Working Mode Active Active l This parameter indicates

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.


Range Value
Link Event Notification Enabled Enabled l This parameter indicates

Disabled or specifies whether the
local link events can be
notified to the opposite
end.
l If the alarms caused by
link events can be
reported, that is, if the
number of performance
events (for example,
error frame period, error
frame, error frame
second, and error frame
signal cycle) at the local
end exceeds the preset
threshold, these
performance events are
notified to the port at the
opposite end through the
link event notification
function.
information.
Remote Side Loopback Response Disabled Disabled l This parameter indicates

Enabled or specifies whether the
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.


Range Value
Loopback Status Non- - This parameter indicates the

Loopback loopback status at the local
Initiate end.
Loopback at NOTE
Local Loopback Status is valid only
after you choose OAM >
Respond Enable Remote Loopback.
Loopback of
Remote
OAM Discovery Status - - This parameter indicates the

OAM discovery status at the
local end.
Port Transmit Status - - This parameter indicates the

status of transmitting packets
at the local end.
Port Receive Status - - This parameter indicates the

status of receiving packets at
the local end.
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
Ethernet OAM Management > Ethernet Port OAM Management from the Function
Tree.
2. Click the OAM Error Frame Monitor tab.


port.
Error Frame 1000 to 60000, in 1000 This parameter specifies the duration of
Monitor step of 100 monitoring error frames.
Window(ms)

Error Frame 1 to 4294967295, in 1 l This parameter specifies the threshold

Monitor step of 1 of monitoring error frames.
Threshold(frames) l Within the specified value of Error
Frame Monitor Window(ms), if the
number of error frames on the link
exceeds the preset value of Error
Frame Monitor Threshold(frame), an
alarm is reported.
Error Frame 1488 to 892800000, 892800000 This parameter specifies the window of
Period in step of 1 monitoring the error frame period.
Window(frame)
Error Frame 1 to 892800000, in 1 l This parameter specifies the threshold

Period step of 1 of monitoring the error frame period.
Threshold(frames) 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.
Error Frame 10 to 900, in step of 60 This parameter specifies the time window
Second Window(s) 1 of monitoring the error frame second.
Error Frame 10 to 900, in step of 1 l This parameter specifies the threshold

Second 1 of monitoring error frame seconds.
Threshold(s) l If any error frame occurs in one
second, this second is called an errored
frame second. Within the specified
value of Error Frame Second
Window(s), if the number of error
frames on the link exceeds the preset
value of Error Frame Second
Threshold(s), an alarm is reported.
B.6.3.11 Parameter Description: Ethernet OAM Management_Configuring

Bandwidth Notification
This section describes parameters for configuring bandwidth notification.
Navigation Path
> Ethernet OAM Management > Ethernet Service OAM Management from the
Function Tree.
2. Specify Maintenance Domain Name, Maintenance Association Name, and MEP
Point according to the data plan.

3. Click OAM and select Configure Bandwidth Advertisement.
Parameters for configuring bandwidth notification

Maintenance Domain - - Displays the MD for

Name bandwidth notification.
Maintenance - - Displays the MA for

Association Name bandwidth notification.
MEP ID - - Displays the ID of the

MEP for bandwidth
notification.
Advertisement l Disable Disable Enables or disables

l Enable bandwidth notification.
Client Layer Level 0-7 7 Specifies the client layer

level.
NOTE
l The client layer level
must be the same as
that on the
interconnected
equipment.
l The client layer level is
higher than or equal to
that of the local MEP.
Periodic l Period Period Specifies whether to

l Non-period periodically send
bandwidth notification
packets.
Periodic(s) l 1 1 Specifies the interval for

l 10 sending bandwidth
notification packets.
l 60
Hold Time(s) 0-10 0 Specifies the hold time

for sending bandwidth
notification packets when
the bandwidth changes.
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.

Mapping Relation ID 1 to 8 1 This parameter indicates

the ID of the mapping
relationship between DS
domains.
Mapping Relation - Default Map This parameter indicates

Name the name of the mapping
relationship between DS
domains.
NOTE
If one default DS domain exists on the OptiX RTN 900 equipment, Mapping Relation ID is set to 1, and
Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this
domain.
Parameters for Ingress Mapping Relation

CVLAN 0 to 7 - l This parameter

of the C-VLAN of the
ingress packets.
l C-VLAN indicates
the client-side VLAN,
and the value 7
indicates the highest
priority.

of the S-VLAN of the
ingress packets.
l S-VLAN indicates the
server-side VLAN,
and the value 7
priority.

IP DSCP 0 to 63 - l This parameter

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
l The differentiated
services code point
(DSCP) refers to bits
0-5 of the
differentiated services
(DS) field in the
packet and indicates
the service class and
discarding priority of
the packet.
MPLS EXP 0 to 7 - l Displays the MPLS

EXP value of ingress
packets.
l When a packet in an
egress queue leaves
an NNI port, the NNI
port obtains the
packet priority value
according to the
mappings between
PHB service classes
of egress queues and
egress packet
priorities (MPLS EXP
values), and writes the
obtained priority
value into the EXP
field of the egress
MPLS packet.
NOTE
For OptiX RTN 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).

PHB BE - l This parameter

AF11 indicates the per-hop
behavior (PHB)
AF12 service class of the
AF13 DS domain.
AF21 l The PHB service
AF22 class refers to the
forwarding behavior
AF23
of the DS node on the
AF31 behavior aggregate
AF32 (BA) operation. The
forwarding behavior
AF33
can meet the specific
AF41 requirements.
AF43 classes are BE, AF1,
AF2, AF3, AF4, EF,
EF
CS6, and CS7. The
CS6 priorities (C_VLAN
CS7 priority, S_VLAN
priority, DSCP value
and MPLS EXP
value) contained in
the packets of the DS
domain and the eight
PHB service classes
meet the requirements
of the specified or
default mapping
relationship.

Parameters for Egress Mapping Relation


AF11 indicates the PHB
service class of the
AF12 DS domain.
AF22 forwarding behavior
AF23
behavior aggregate
AF33
requirements.
AF41
l The PHB service
AF43 AF2, AF3, AF4, EF,
CS6, and CS7. The
EF
priorities (C_VLAN
CS7 priority, DSCP value
and MPLS EXP
value) contained in
PHB service classes
of the specified or
default mapping
relationship.
CVLAN 0 to 7 - l This parameter

of the C-VLAN of the
egress packets.
l C-VLAN indicates
and the value 7
priority.


of the S-VLAN of the
egress packets.
server-side VLAN,
and the value 7
priority.

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
l The DSCP refers to
bits 0-5 of the DS
field in the packet and
indicates the service
class and discarding
priority of the packet.
MPLS EXP 0 to 7 - l Displays the MPLS

EXP value of egress
packets.
l When a packet arrives
at an NNI port, the
NNI port obtains the
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.


the port that uses the DS
domain.

Packet Type CVLAN CVLAN The packets trusted by

SVLAN the OptiX RTN 900 are
the C_VLAN, S_VLAN
IP-DSCP and IP DSCP packets that
MPLS-EXP contain the C_VLAN
priority, S_VLAN
priority, DSCP value or
MPLS value. By default,
the untrusted packets are
mapped to the BE service
class for best-effort
forwarding.
NOTE
l For the E-Line services
that are transparently
transmitted end to end
(UNI-UNI), a UNI port
only trusts DSCP
value.
l An NNI port carrying
MPLS/PWE3 services
trusts only packets with
MPLS EXP values.
l A QinQ-based NNI
port 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. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS
Management > Diffserv Domain Management > Diffserv Domain Management
2. Click New.

Mapping Relation ID 2 to 8 - This parameter specifies

the ID of the mapping
relationship of a DS
domain.

Mapping Relation - - This parameter specifies

relationship of a DS
domain.
Parameters for Ingress Mapping Relation

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.

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.

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.

AF12 DS domain.
AF23
behavior aggregate
AF33
requirements.
AF41
l The PHB service
CS6, and CS7. The
EF
priorities (C_VLAN
and MPLS EXP
value) contained in
PHB service classes
of the specified or
default mapping
relationship.

Parameters for Outbound Mapping Relationship


AF12 DS domain.
AF23
behavior aggregate
AF33
requirements.
AF41
l The PHB service
CS6, and CS7. The
EF
priorities (C_VLAN
and MPLS EXP
value) contained in
PHB service classes
of the specified or
default mapping
relationship.
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.

S-VLAN 0 to 7 - l This parameter

priority of the egress
packets.
server-side VLAN,
and the value 7
priority.

specifies the DSCP
priority of the IP
addresses of the
egress packets.
services code point
0-5 of the
(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.



the board that uses the
mapping relationships
between DS domains.
Available Port - - This parameter displays

the available port list
from which you can
select the port that uses
the mapping relationships
between DS domains.

the selected port list. The
ports in the list use the
mapping relationships
between DS domains.
Packet Type cvlan cvlan l This parameter

svlan specifies the type of
the packet.
ip-dscp
l The packets trusted by
mpls-exp the OptiX RTN 900
are the C_VLAN,
S_VLAN, IP DSCP
and MPLS packets
that contain the
C_VLAN priority,
S_VLAN priority,
DSCP value or MPLS
EXP value. By
default, the untrusted
packets are mapped to
the BE service class
for best-effort
forwarding.
NOTE
only trusts DSCP value.
MPLS/PWE3 services
MPLS EXP values.
l A QinQ-based NNI port
DSCP values or S-
VLAN priorities.

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

Mapping Relation - - This parameter indicates

relation of a DS domain.
Packet Type CVLAN CVLAN The packets trusted by

SVLAN the OptiX RTN 900 are
the C-VLAN, S-VLAN,
IP-DSCP IP DSCP packets, and
MPLS-EXP MPLS packets that
respectively contain the
C-VLAN priority, S-
VLAN priority, IP DSCP
value and MPLS EXP
value. By default, the
untrusted packets are
mapped to the BE service
class for best-effort
forwarding.
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.


the board where the port
is located.

the available port.

the selected port.
The selected port is
applied to the DS
domain.
NOTE
If one default DS domain exists on the OptiX RTN 900, Mapping Relation ID is set to 1, and Mapping
Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
B.6.4.4 Parameter Description: Policy Management

This topic describes the parameters that are related to port policies.
Navigation Path
2. Click the CoS Configuration tab.
Parameters
Policy ID - - This parameter indicates

the policy ID of the port.
Policy Name - - This parameter indicates

or specifies the policy
name of the port.
WRR Scheduling Policy - - This parameter indicates

the current WRR
scheduling policy.

CoS CS7 - l The BE, AF1, AF2,

CS6 AF3, AF4, EF, CS6,
and CS7 service
EF classes respectively
AF4 map eight queuing
AF3 entities. The OptiX
RTN 900 provides
AF2
different QoS policies
AF1 for the queues at
BE different service
classes.
l CS6-CS7: indicates
the highest service
grade, which is
mainly involved in
signaling
transmission.
l EF: indicates fast
forwarding. This
service class is
applicable to the
traffic whose delay is
small and packet loss
ratio is low, for
example, voice and
video services.
l AF1-AF4: indicates
assured forwarding.
This service class is
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.

Grooming Police After SP CS7, CS6, EF, BE: SP l The strict priority
Reloading WRR AF4, AF3, AF2, AF1: (SP) scheduling
WRR algorithm is designed
for the key services.
One important
characteristic of the
key services is that
higher priorities are
required to minimize
the response delay in
the case of congestion
events.
l The weighted round
robin (WRR)
scheduling algorithm
divides each port into
multiple output sub-
queues. The polling
scheduling is
performed among the
output sub-queues to
ensure that each sub-
queue has a certain
period of service time.
l The OptiX RTN 900
supports the setting of
the SP+WRR
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

a descending order
(CS7-BE).
according to the
Enable Bandwidth Disabled Disabled l This parameter

Restriction Enabled indicates or specifies
whether traffic
shaping is enabled for
an egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
(kbit/s), CBS (byte),
and PBS (byte) can
be set only when
Bandwidth Limit is
set to Enabled.
according to the
CIR(kbit/s) - - This parameter is set

information.
PIR(kbit/s) - - If the rate of a packet is

higher than the PIR, it
enters the buffer queue
and then is forwarded at a
rate equal to the PIR.
CBS(byte) - - This parameter is set

information.

PBS(byte) - - l When the buffer

queue is empty,
certain burst packets
can be forwarded if
the rate of the packets
is equal to or lower
than the PIR in a
certain period. The
maximum traffic of
the burst packets is
determined by the
PBS.
according to the
Tail Drop Threshold — — l Two port congestion

(256 bytes) avoidance algorithms
are available: tail drop
Port WRED Policy — — and weighted random
early detection
(WRED).
l If tail drop is used, set
Tail Drop Threshold
(256 bytes) only.
l If WRED is used, set
Port WRED Policy
only.
B.6.4.5 Parameter Description: Port Policy

This topic describes the parameters that are used for creating port policies.
Navigation Path
2. Click New. The Create Port Policy dialog box is displayed.
Parameters
Policy ID - - This parameter

specifies the policy ID
of the port.

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.
Policy Name - - This parameter

specifies the policy
name of the port.

WRR Scheduling Policy - - l This parameter

specifies the desired
WRR scheduling
policy.
l The WRR weight
set in the WRR
scheduling policy
only applies to
WRR queues.
l When the total
WRR weight value
of all WRR queues
equals to 100%, the
WRR weight set for
each queue in the
WRR scheduling
policy is the actual
WRR weight. For
example, when
AF4, AF3, AF2,
and AF1 are all
WRR queues and
their weight values
are 25%, 25%,
25%, and 25%
respectively, each
queue is actually
allocated with 25%
total bandwidth.
l When the total
WRR weight value
of all WRR queues
is less than 100%,
the actual WRR
weight is
recalculated based
on the proportion
between the WRR
weights of different
queues set in the
WRR scheduling
policy. For
example, when
AF4, AF3, AF2,
and AF1 are all
WRR queues and
their weight values
are 20%, 20%,
20%, and 20%

respectively, the
actual bandwidth
allocation weight of
each queue will be
recalculated based
on the proportion
between the set
WRR weight
(1:1:1:1). That is,
each queue is
allocated with 25%
total bandwidth.


and CS7 service
RTN 900 provides
AF2
different QoS
AF1 policies for the
BE queues at different
service class.
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 best-
effort manner
without special
processing.

WRR 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
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
that each sub-queue
has a certain period
of service time.
l The OptiX RTN
900 supports the
setting of the SP
+WRR scheduling
algorithm of the
CoS queue
according to the
requirement, and
provides one or
more queues that
comply with the SP
algorithm. Except
for the default
value, however, the
value of the WRR
scheduling
algorithm and the
value of the SP
scheduling
algorithm cannot be

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 l Bandwidth Limit

Enabled indicates or
specifies whether
traffic shaping is
enabled for an
egress queue
corresponding to a
PHB service class.
l CIR (kbit/s), PIR
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit
is set to Enabled.
l This parameter is
planning
information.

according to the

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.

according to the


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 - - l Two port

bytes) congestion
avoidance
Port WRED Policy - - 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
2. Click the Traffic Classification Configuration tab.
3. Click New.


Traffic Classification ID 1 to 512 - This parameter specifies

the ID of the traffic
classification.
ACL Action Permit Permit l The access control list

Deny (ACL) determines
whether to forward or
discard the packets
that enter the port
according to the
specified matching
rules.
l When ACL Action is
set to Permit, the
ingress port accepts
and then performs
QoS processing for
only the packets that
meet the specified
mapping rules.
l When ACL Action is
set to Deny, the
ingress port discards
the packets that meet
the specified mapping
rules.
Ingress Parameters
Logical Relation And And l This parameter

Between Matched Rules specifies the logical
relationship between
the traffic
classification
matching rules.
l The OptiX RTN 900
supports the setting of
the logical AND
between multiple
matching rules.

Match Type DSCP Value - l After you click Add

CVlan ID or Delete, complex
traffic classification
CVlan priority can be performed on
SVlan ID the traffic that enters
SVlan priority the ingress port
according to the
Source MAC Address
preset matching rules.
Destination MAC
l Traffic type is based
Address
on the associated
Destination IP Address Ethernet packets.
Source IP Address Therefore, this
parameter is set
Protocol Type
according to the
Source Port packet type and the
Destination Port planning information.
ICMP Packect Type Code l Only OptiX RTN 950
housing CSHU/
CSHUA, OptiX RTN
950A, OptiX RTN
910A and OptiX RTN
905 support traffic
classification by IP
address, protocol
type, port number,
and ICMP type.
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
traffic classification.
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

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 l This parameter

CS7 specifies the PHB
service class queue
CS6 mapped by the traffic
EF classification packets.
AF4 l If this parameter is set
AF3 to empty (-), the
AF2
packets map the PHB
AF1 service class queue
BE according the
mapping specified in
the topic about
Diffserv domain
management.
according to the
Enable Bandwidth Disabled Enabled l This parameter

Restriction Enabled indicates or specifies
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

CIR(kbit/s) - - l When the rate of the

packets is not more
than the CIR, the
packets are marked
green and pass the
CAR policing. These
packets are first
forwarded in the case
of network
congestion.
l When the rate of the
packets is more than
the CIR but not more
than the PIR, the
packets whose rate is
more than the CIR
can pass the
restriction of the CAR
and are marked
yellow. The
processing method of
the packets marked
yellow can be set to
"Pass" or "Remark".
"Remark" indicates
mapped into another
specified queue of a
higher priority (this is
equal to changing the
priority of the
packets) and then
forwarded to the next
port. If a network
congestion event
occurs again, the
packets marked
yellow can be
processed according
to the new priority.
according to the

PIR(kbit/s) - - l When the rate of the

the PIR, the packets
that exceed the rate
restriction are marked
red and directly
discarded.
l When the rate of the
the CIR but not more
than the PIR, the
packets whose rate is
more than the CIR
can pass the
restriction of the CAR
and are marked
yellow. The
processing method of
the packets marked
yellow can be set to
"Pass" or "Remark".
"Remark" indicates
mapped into another
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

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 - - This parameter specifies

the CAR operation
performed by the
equipment on the
packets. The packets are
dyed according to the
result of the CAR
operation. The dying rule
is determined by the
comparison between the
rate of the packets and
the preset CAR value.

Packet Color Red - Packets can be dyed in

Yellow three colors: red, yellow,
and green. The packets in
Green red are first discarded.
Processing Mode Discard - l This parameter

Pass specifies the method
of handling the
Remark packets.
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 - If the handling method is

CS6 set to "Remark", you can
reset the CoS of the
EF packets.
AF4
AF3
AF2
AF1
BE

Egress Parameters
Bandwidth Limit Disabled Enable l This parameter

Enable indicates or specifies
whether the traffic
shaping is performed
in the egress function.
l CIR (kbit/s), PIR
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

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

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
Management > Port Shaping Management from the Function Tree.
2. Click New.
Parameters for Port Shaping Management

Slot No. - - This parameter specifies

the slot ID.

the port.
PIR (kbit/s) - - If the traffic shaping

function is enabled,
OptiX RTN 900
processes the packets in
the buffer queue through
the following methods
when no packets are
available in the queue.
l When the buffer
queue is empty, the
packets are processed
as follows: If the rate

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
Management > Policy Management > Port WRED Policy from the Function Tree.
2. Click New.

Parameters
Policy ID - - This parameter specifies

WRED policy.
Assign automatically Selected Deselected This parameter specifies

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.
Policy Name - - This parameter specifies

the policy name of the
WRED policy.
Packet Color Green - Packets with different

Yellow colors have different
discard thresholds and
Red discard ratios. In the case
Lower Discard 0 to 480 32 of congestion, lower
Threshold (256 bytes) priority packets are
discarded first so that
Upper Discard 0 to 480 80 higher priority packets
Threshold (256 bytes) can pass.
Discard Rate (%) 0 to 100 40
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).
Navigation Path
Management > Policy Management > Service WRED Policy from the Function Tree.
2. Click New.
Parameters
Policy ID - - This parameter specifies

WRED policy.

Assign automatically Selected Deselected This parameter specifies

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.
Policy Name - - This parameter specifies

the policy name of the
WRED policy.
Packet Color Green - Packets with different

Yellow colors have different
discard thresholds and
Red discard ratios. In the case
Lower Discard 0 to 480 32 of congestion, lower
Threshold (256 bytes) priority packets are
discarded first so that
Upper Discard 0 to 480 80 higher priority packets
Threshold (256 bytes) can pass.
Discard Rate (%) 0 to 100 40
B.6.4.10 Parameter Description: WRR Scheduling Policy_Create

This section describes parameters for creating a WRR scheduling policy.
Navigation Path
Management > Policy Management > WRR Scheduling Policy from the Function
Tree.
2. Click New.
Parameters
ault
Val
ue
Policy ID - - This parameter specifies the

policy ID of the WRR scheduling
policy.


ault
Val
ue
Policy Name - - This parameter specifies the

policy name of the WRR
scheduling policy.
Assign automatically Selected Dese This parameter specifies whether

Deselected lecte to automatically assign a policy
d ID to the WRED policy. If this
parameter is selected, the policy
ID for the WRED policy is
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
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

of the port.

the system
set manually.

name of the port.


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%

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.


and CS7 service
RTN 900 provides
AF2
different QoS
service class.
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
forwarded in best-
effort manner
without special
processing.

WRR 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
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
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

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.

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.

according to the


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.

according to the


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) congestion
avoidance
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
Management > Policy Management > PW Policy from the Function Tree.
2. Click New. The Create PW Policy dialog box is displayed.

Parameters

of the port.

the system
set manually.

name of the port.


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%

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.


and CS7 service
RTN 900 provides
AF2
different QoS
service class.
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
forwarded in best-
effort manner
without special
processing.

WRR 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
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
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

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.

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.

according to the


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.

according to the


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) congestion
avoidance
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
Management > Policy Management > QinQ Policy from the Function Tree.
2. Click New. The Create QinQ Policy dialog box is displayed.

Parameters

of the port.

the system
set manually.

name of the port.


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%

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.


and CS7 service
RTN 900 provides
AF2
different QoS
service class.
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
forwarded in best-
effort manner
without special
processing.

WRR 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
queues. The polling
scheduling is
performed among
the output sub-
queues to ensure
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

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.

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.

according to the


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.

according to the


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) congestion
avoidance
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.

Table B-14 Parameters on the Main Interface

Set IP mark bits l IP FLAG BIT0 IP FLAG BIT0 Set the flag bit of the
l IP TOS BIT3 marked packets, which is
used to count the packets.
l IP TOS BIT4
l IP TOS BIT5
l IP TOS BIT6
l IP TOS BIT7
ID 1 to 5 1 Display or set the ID.
Automatically Assign l Checked Unchecked Set the automatically

l Unchecked assign.
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

l Intermediate of the test packets.
l Downstream
Action l Collect only Collect only Set the function of the

l Mark and collect testing.
l Restore and collect
Auto Stop After 1 to 10080 5 Display and set the time

(minutes) for automatically
stopping.

Logical Relation Between l And And Specifies the logical

Matched Rules l Or relationships between
matched rules.
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.

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 - - Specifies the Match

Value of each match
type.

Wildcard - - Specifies the Wildcard

of the match value.
Adopt 0 for strictly
matched bits, and 1 for
unconcerned bits.
Rules Example: {Outer VLAN: - Display and set the rules

1:0}&{Inner VLAN:2:0} for marking. The
conformed packets will
be marked.
Status l Stop Stop Display and set the

l Start testing status.
Number of Marked - - Display the number of

Packets the marked packets after
testing.
Number of Marked Bytes - - Display the number of

the marked bytes after
testing.
Number of Unmarked - - Display the number of

Packets the unmarked packets
after testing.
Number of Unmarked - - Display the number of

Bytes the unmarked packets
after testing.
Table B-15 VUNI parameters

Direction l Transmit - Display the direction

l Receive for the test packets.
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.

Table B-16 QinQ parameters

Service - - Display and set the

service ID.
QinQ - - Display and set the

QinQ ID.
Table B-17 Tunnel parameters

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

l Service tag role of E-LAN
service.
PW Type l Ethernet Ethernet Set the PW type.

l Ethernet Tag PWs of different
Mode types process the
borne services
differently. For
example, the PW in
the Ethernet tagged
mode attaches the
tag on the services
on this PW.
Request VLAN - - Specifies the type

TPID 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

l Used first word of the PW.
l Use required

UNI Port l NULL NULL Indicates the way in

Encapsulation Type l C-Tag which the port
processes accessed
l S-Tag packets.
UNI Port TPID - - Specifies the type

field of the UNI port
TPID.
Service Type l E-Line service E-LAN service Specifies the type

l E-LAN service field of the Service
Type.
l E-AGGR service
S-TAG TPID - - Indicates the TPID

of S-VLAN tags in
the PW user packets
of a VPLS service.
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/905e/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.

Board - - Displays the board name.
Service Type EPL EPL Specify the Ethernet service type to EPL.
Service Direction Bidirectional Bidirectional l If this parameter is set to

Unidirectional Unidirectional, you only need to create
a service from the service source to the
service sink. That is, there is traffic
only in the direction from the service
source to the sink port.
l If this parameter is set to Bidirectional,
you need to create a service from the
service source to the service sink and a
service from the service sink to the
service source. That is, there is traffic
in the direction from the service source
to the sink port and in the direction
from the service sink to the source port
at the same time.
Source Port - - l Specifies the port of the service source.

l When you create bidirectional Ethernet
services from a PORT to a VCTRUNK,
it is recommended that you set the
PORT to the source port.
Source VLAN(e.g. 1-4095 - l This parameter can be set to null, a

1,3-6) number, or several numbers. When
setting this parameter to several
numbers, use the comma (,) to separate
the discrete numbers, or use the hyphen
(-) to represent consecutive numbers.
For 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.

Sink Port - - l Specifies the port of the service sink.

l This parameter cannot take the same
value as Source Port.
l When you create bidirectional Ethernet
services from a PORT to a VCTRUNK,
it is recommended that you set the
VCTRUNK to the sink port.
Sink VLAN(e.g. 1-4095 - l This parameter can be set to null, a

1,3-6) number, or several numbers. When
setting this parameter to several
numbers, use the comma (,) to separate
the discrete numbers, or use the hyphen
(-) to represent consecutive numbers.
For 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

Port - - Displays the ports involved in the Ethernet

service.
Port Type - - Displays the network attribute of the

Ethernet port.
Port Enabled Enabled - l When the source port or the sink port is
Disabled set to a PORT, set Port Enabled to
Enabled.
l This parameter need not be set when
the source port or sink port is a
VCTRUNK.

TAG Tag Aware - l If all the accessed services are frames

Access with VLAN tags (tagged frames), set
this parameter to Tag Aware.
Hybrid
l If all the accessed services are frames
without VLAN tags (untagged frames),
set this parameter to Access.
l If the accessed services contain tagged
frames and untagged frames, set this
parameter to Hybrid.
Table B-20 Parameters for bound paths

VCTRUNK Port EFP8: VCTRUNK1 Specifies the VCTRUNK to bind paths.

VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8
Level - - Displays the level of the bound VC path.

In the case of the EFP8 board, this
parameter always takes the value of VC12-
Xv.
Service Direction Bidirectional Bidirectional l Specifies the direction of the bound

Uplink path.
Downlink l Set this parameter to Bidirectional
unless otherwise specified.
Bound Path - - You need to plan and set this parameter

according to the following principles:
l The capacity of the VCTRUNK is
determined by the actual bandwidth
required by the services.
l The EFP8 board supports 16
VCTRUNKs. Each VCTRUNK can
bind a maximum of 16 VC-12 paths
and the total number of bound VC-12
paths cannot exceed 63.
l For EMS6 boards, their VCTRUNKs
1-7 each support a maximum
bandwidth of 100 Mbit/s. If a
bandwidth higher than 100 Mbit/s is
required, VCTRUNK8 is
recommended.

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 Defau Description
Range lt
Value
Board - - Displays the

board name.
Service Type EPL EPL Specifies the

EVPL( service type to
QinQ) EVPL(QinQ).


Range lt
Value
Service Direction Bidire Bidirec l When this

ctional tional parameter is
Unidir set to
ectiona Unidirection
l 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.
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


Range lt
Value
Bidirectional
.


Range lt
Value
Operation Type l Ad Strip l When used

d S- for private
S- VLAN line services,
VL QinQ can
AN process
l Tra VLAN tags
nsp in different
are manners as
ntly required.
tran l When
smi Service
t C- Direction is
VL set to
AN Unidirection
l Tra al, you can
nsp set
are Operation
ntly Type to Strip
tran S-VLAN.
smi l Set this
t S- parameter
VL according to
AN actual
l Tra situations.
nsp
are
ntly
tran
smi
t S-
VL
AN
and
C-
VL
AN
l Tra
nsl
ate
S-
VL
AN
l Tra
nsl
ate
S-


Range lt
Value
VL
AN
and
tran
spa
rent
ly
tran
smi
t C-
VL
AN
l Stri
p
S-
VL
AN
Source Port - - l Specifies the

port where
the service
source
resides.
l When
creating a
bidirectional
Ethernet
service from
a PORT to a
VCTRUNK,
it is
recommende
d that you use
the PORT as
the source
port.


Range lt
Value
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 C-
VLAN(e.g.
1, 3-6).
l When you set
this
parameter to
null, all the
services of
the source
port work as
the service
source.
l When you set
this
parameter to


Range lt
Value
a non-null
value, only
the services
of the source
port whose
VLAN IDs
are included
in the value
range of this
parameter
work as the
service
source.
Source S-VLAN 1-4095 - l This

parameter
must be set to
a numerical
value.
l Only the
service of the
source port
whose S-
VLAN ID is
equal to the
value of this
parameter
work as the
service
source.


Range lt
Value
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.


Range lt
Value
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 C-
VLAN(e.g.
1, 3-6).
l When you set
this
parameter to
null, all the
services of
the sink port
work as the
service sink.
l When you set
this
parameter to
a non-null


Range lt
Value
value, only
the services
of the sink
port whose
VLAN IDs
are included
in the value
range of this
parameter
work as the
service sink.
Sink S-VLAN 1-4095 - l This

parameter
must be set to
a numerical
value.
l Only the
services of
the sink port
whose S-
VLAN IDs
are equal to
the value of
this
parameter
work as the
service sink.
C-VLAN Priority AUTO AUTO Displays the C-

VLAN priority.
S-VLAN Priority AUTO AUTO Specifies the S-

Priorit VLAN priority.
y 0 to The bigger the
Priorit value, the higher
y7 the priority.
Table B-22 Parameters of port attributes

Range Value
Port - - Displays the ports that

are configured to
transmit the service.


Range Value
Port Type - - Displays the network

attribute of the Ethernet
port.
Port Enabled Enabled - l When the source

Disabled port or the sink port
is set to a PORT, set
Port Enabled to
Enabled.
l This parameter need
not be set when the
source port or sink
port is a
VCTRUNK.
TAG - - This parameter is

invalid for QinQ line
services.

Range Value
VCTRUNK Port EFP8: VCTRUN Specifies the

VCTRUN K1 VCTRUNK to bind
K1- paths.
VCTRUN
K16
EMS6:
VCTRUN
K1-
VCTRUN
K8
Level - - Displays the level of

the bound VC path.
In the case of the EFP8
board, this parameter
always takes the value
of VC12-Xv.


Range Value
Service Direction Bidirection Bidirectio l Specifies the

al nal direction of the
Uplink bound path.
Downlink l Set this parameter
to Bidirectional
unless otherwise
specified.
Bound Path - - You need to plan and

set this parameter
according to the
following principles:
l The capacity of the
VCTRUNK is
determined by the
actual bandwidth
required by the
services.
l The EFP8 board
supports 16
VCTRUNKs. Each
VCTRUNK can
bind a maximum of
16 VC-12 paths and
the total number of
bound VC-12 paths
cannot exceed 63.
l For EMS6 boards,
their VCTRUNKs
1-7 each support a
maximum
bandwidth of 100
Mbit/s. If a
bandwidth higher
than 100 Mbit/s is
required,
VCTRUNK8 is
recommended.
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.

Navigation Path
In the NE Explorer, select the EFP8/EMS6 board from the Object Tree and choose
Table B-24 Parameters on the main interface (Display QinQ Shared Service is not selected)
Service Type - - Displays the service type.
Service Direction - - Displays the service direction.
Source Port - - Displays the port of the service source.
Source VLAN - - Displays the VLAN ID of the service

source.
Sink Port - - Displays the port of the service sink.
Sink VLAN - - Displays the VLAN ID of the service sink.
Activation Status - - Displays whether to activate the service.
Table B-25 Parameters on the main interface (Display QinQ Shared Service is selected)
Service Type - - Displays the service type.
Source Port - - Displays the port of the service source.
Source C-VLAN - - Displays the VLAN ID of the service

source.
Source S-VLAN - - l Displays the S-VLAN ID of the service

source.
l This parameter can be set only for the
QinQ-based EVPL service.
Sink Port - - Displays the port of the service sink.
Sink C-VLAN - - Displays the VLAN ID of the service sink.

Sink S-VLAN - - l Displays the S-VLAN ID of the service

sink.
C-VLAN Priority - - l Displays the priority of the C-VLAN.

S-VLAN Priority - - l Displays the priority of the S-VLAN.

Activation Status - - Displays whether to activate the service.
Table B-26 Parameters for port attributes


Ethernet port.
Port Enabled - - When the source port or sink port is a

PORT, this parameter indicates whether the
port is enabled.
TAG - - Displays the tag attribute of the Ethernet

port.

VCTRUNK Port - - Displays the VCTRUNK that binds VC

paths.
Level - - Displays the level of the bound VC paths.
Service Direction - - Displays the direction of the bound VC

paths.
Bound Path - - Displays the serial numbers of the bound

VC paths.
Number of Bound - - Displays the number of the bound VC

Paths paths.

Activation Status - - Displays whether the bound VC paths are

activated.
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
2. Click New.

Board - - Displays the board that is configured with

a bridge.
VB name - - Describes the bridge. It is recommended

that you set this parameter to a character
string that indicates the function of the
bridge.
Bridge Type 802.1q 802.1q l If this parameter is set to 802.1q, an

802.1d IEEE 802.1q bridge is created.
802.1ad l If this parameter is set to 802.1d, an
IEEE 802.1d bridge is created.

Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode,
Mode Filter Enable Filter Enable all the VLANs share one MAC address
(supported by (IEEE 802.1q table. When the bridge uses the IVL
the IEEE 802.1q bridge and the mode, each VLAN has an MAC
bridge and IEEE IEEE 802.1ad address table.
802.1ad bridge, bridge) l When the filtering function is enabled
unsupported by l SVL/Ingress at the ingress port, the ingress port
the IEEE 802.1d Filter Disable checks the VLAN tags of all incoming
bridge) (IEEE 802.1d packets. If the VLAN ID contained in
l SVL/Ingress bridge) the VLAN tag of a packet is not
Filter Disable included in the VLAN filtering table,
(supported by the packet is discarded. When the
the IEEE 802.1d filtering function is disabled at the
bridge and IEEE ingress port, the ingress port does not
802.1ad bridge, check any VLAN tag of the incoming
unsupported by packets.
the IEEE 802.1q
bridge)
Bridge Learning - - Displays the learning mode of the bridge.

Mode
Ingress Filter - - Displays whether the filtering function is

enabled at the ingress port.
MAC Address - - Displays whether the MAC address self-

Self-learning learning of the bridge is enabled.
Active - - Displays whether to activate the service.
Table B-29 Parameters for mounting services

VB Port - - Displays the ID of the logical port on the

bridge.
Mount Port - - Displays or specifies which physical port

or VCTRUNK on the Ethernet switch
board is 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

Enabled mounted to the bridge is enabled.
TAG Access - Displays or specifies the tag attribute of

Tag Aware the port mounted to the bridge.
Hybrid

Default VLAN ID - - Displays or specifies the default VLAN ID

of the port mounted to the bridge.
This parameter is valid only when you set
the tag attribute of the port to Access or
Hybrid.
Working Mode Auto-Negotiation - Displays or specifies the working mode of

10M Half-Duplex the port mounted to the bridge.
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Service Direction - - Displays the direction of the service.
C-VLAN - - The IEEE 802.1d/802.1q bridge does not

S-VLAN - - The IEEE 802.1d/802.1q bridge does not

S-VLAN Priority - - The IEEE 802.1d/802.1q bridge does not

C-VLAN Priority - - The IEEE 802.1d/802.1q bridge does not

Table B-30 Parameters for mounting configuration

Available Mounted - - Displays which physical port or

Ports VCTRUNK on the Ethernet switch board
can be mounted to the bridge.
Selected Mounted - - Displays which physical port or

Ports VCTRUNK on the Ethernet switch board
is mounted to the bridge.



VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8

parameter always takes the value of
VC12-Xv.

Uplink path.

recommended.

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.

Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and then choose Configuration >
Ethernet Service > Ethernet LAN Service from the Function Tree.
2. Click New.

Board - - Displays the board where the bridge is

configured.
VB Name - - This parameter is a string that describes

the bridge. It is recommended that you set
this parameter to a character string that
contains the information about the detailed
application of the bridge.
Bridge Type 802.1q 802.1q When this parameter is set to 802.1ad,

802.1d create the IEEE 802.1ad bridge.
802.1ad
Bridge Switch l IVL/Ingress l IVL/Ingress l When the bridge uses the SVL mode,
Mode Filter Enable Filter Enable all the VLANs share one MAC address
(supported by (the 802.1q table. When the bridge uses the IVL
the 802.1q bridge and the mode, all the VLANs correspond to
bridge and 802.1ad bridge) their respective MAC address tables.
802.1ad bridge, l SVL/Ingress l If the ingress filter is enabled, the
unsupported by Filter Disable VLAN tag is checked at the ingress
the 802.1d (the 802.1d port. If the VLAN ID does not equal
bridge) bridge) the VLAN ID of the port defined in the
l SVL/Ingress VLAN filtering table, the packet is
Filter Disable discarded. If the ingress filter is
(supported by disabled, the preceding described check
the 802.1d is not conducted.
bridge and
802.1ad bridge,
unsupported by
the 802.1q
bridge)
Bridge Learning - - Displays the bridge learning mode.

Mode
Ingress Filter - - Displays whether the ingress filter function

is enabled.
MAC Address - - Displays whether the MAC address self-

Self-learning learning function of the bridge is enabled.

Table B-33 Parameters of service mounting

VB Port - - Displays the ID of the logical port of the

bridge.
Mount Port - - Displays or specifies the external port or

VCTRUNK on the Ethernet switching
board that is connected to the bridge.

external port/VCTRUNK connected to the
bridge.
Port Enabled Disabled - Displays or specifies whether the external

Enabled port connected to the bridge is enabled.
TAG - - This parameter is invalid in the case of

Ethernet LAN services based on 802.1ad
bridge.
Default VLAN ID - - Displays or specifies the default VLAN

ID.
This parameter is valid only when TAG is
set to Access or Hybrid.
Working Mode Auto-Negotiation Auto-Negotiation Displays or specifies the working mode of

10M Half-Duplex the external port.
10M Full-Duplex
100M Half-Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex
Activate - - Displays whether the service is activated.
C-VLAN - - Displays or specifies the C-VLAN ID that

the data frames carry.
Is valid only when the bridge is an IEEE
802.1ad bridge and Operation Type is set
to Add S-VLAN Base for Port and C-
VLAN.
Specifies the mapping relationship
between the C-VLAN ID carried by the
data frames and the S-VLAN ID to be
added.

S-VLAN - - Displays or specifies the S-VLAN ID that

the data frames carry.
l When Operation Type is set to Add S-
VLAN Base for Port, this parameter
specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN ID.
VLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify
the mapping relationship between the
S-VLAN ID to be added and the C-
VLAN ID carried by the data frames
that enter the IEEE 802.1ad bridge.
l When Operation Type is set to Mount
Port, this parameter is invalid.
Port and Base for Port and S-VLAN,
this parameter specifies the S-VLAN
ID to be carried by the data frames that
enter 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

Operation Type Add S-VLAN base Add S-VLAN base For the meaning of each operation type,
for port for port see Application of QinQ in 802.1ad Bridge
Add S-VLAN base Services.
for Port and C-
VLAN
Mount Port
Mount Port and
base for Port and S-
VLAN
VB Port - - Specifies the ID of the logical port of the

bridge.
Mount Port - - Selects the external port or VCTRUNK on

the Ethernet switching board that is
connected to the bridge.
Port Type - - Displays the port type.

C-VLAN 1-4095 - Is valid only when Operation Type is set

to Add S-VLAN Base for Port and C-
VLAN.
Specifies the mapping relationship
between the C-VLAN ID carried by the
data frames and the S-VLAN ID to be
added.
S-VLAN 1-4095 - l When Operation Type is set to Add S-

VLAN Base for Port, this parameter
specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN ID.
VLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify
the mapping relationship between the
S-VLAN ID to be added and the C-
VLAN ID carried by the data frames
that enter the IEEE 802.1ad bridge.
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.


VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8


parameter always takes the value of VC12-
Xv.

Uplink path.

recommended.

path.
B.7.1.6 Parameter Description: Ethernet LAN Service

This section describes the parameters for creating an Ethernet LAN service.
Navigation Path
Board - - Displays the board that is configured with

a bridge.

VB ID - - Displays the ID of the bridge.
VB Name - - This parameter is a character string that

describes the bridge. It is recommended
that you set this character string to a value
that indicates the specific purpose of the
bridge.
Bridge Type - - Displays the type of the bridge.
Bridge Switch - - Displays the switching mode of the bridge.

Mode
Bridge Learning - - Displays the learning mode of the bridge.

Mode
Ingress Filter - - Displays whether the filtering function is

enabled at the ingress port.
MAC Address self- - - Displays whether the MAC address self-

Learning learning of the bridge is enabled.
Table B-37 Parameters for mounting services

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

the port mounted to the bridge.
Port Enabled - - Displays or specifies whether the

port mounted to the bridge is
enabled.

Hub/Spoke Hub Hub Displays or specifies the Hub/

Spoke Spoke attribute of the port
mounted to the bridge.
l Hub ports can mutually access
each other.
l Hub ports and Spoke ports can
mutually access each other.
l Spoke ports cannot mutually
access each other.
TAG - - Displays or specifies the TAG

attribute of the mounted port in the
case of Ethernet LAN services
based on 802.1d bridge or 802.1q
bridge.
This parameter is invalid in the
case of Ethernet LAN services
based on 802.1ad bridge.
Default VLAN ID - - Displays or specifies the default

VLAN ID of the port mounted to
the bridge.
This parameter is valid only when
you set the tag attribute of the port
to Access or Hybrid.
Working Mode - - Displays or specifies the working

mode of the port mounted to the
bridge.
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.
This parameter is valid only when
the bridge is an IEEE 802.1ad
bridge and Operation Type is
Add S-VLAN Base for Port and
C-VLAN.
This parameter specifies the
mapping relation between the C-
VLAN tag carried by the data
frame and the S-VLAN tag to be
added.

S-VLAN - - Displays or specifies the S-VLAN

ID carried by the data frame.
l When Operation Type is set to
Add S-VLAN Base for Port,
this parameter specifies the S-
VLAN 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 S-

VLAN.
C-VLAN Priority - - Displays the priority of the C-

VLAN.
Table B-38 Parameters for VLAN filtering table

VLAN ID - - Displays the VLAN ID that needs to be

filtered in forwarding.

bridge.

Forwarding - - Displays the actually specified forwarding

Physical Port port.
l Selected forwarding ports can send
packets only among themselves.
l Selected forwarding ports can only
forward the packet that carries the
VLAN ID tag. These ports discard the
packet that carries other VLAN tags.
l The broadcast packets transmitted by
any of Selected forwarding ports can
be forwarded only among Selected
forwarding ports.
Activation Status - - Displays whether the VLAN ID entry is

valid.
Table B-39 Parameters for VLAN unicast

VLAN ID - - l This parameter is invalid for the 802.1d

bridge and the 802.1ad bridge that
adopt the SVL learning mode. The
entry applies to all VLANs.
l In the case of the 802.1d bridge and the
802.1ad bridge that adopt the SVL
learning mode, the entry applies to only
the VLAN with the ID specified by this
parameter.
MAC Address - - l Displays or specifies the static MAC

address.
l A static MAC address is an address that
is set manually. It does not age
automatically and needs to be deleted
manually.
l Generally, a static MAC address is used
for the port that receives but does not
forward Ethernet service packets or the
port whose MAC address need not age
automatically.

bridge.

Physical Port - - l Specifies the Ethernet port that

corresponds to the MAC address.
Aging Status - - Displays the aging status of the entries.
Table B-40 Parameters for disabling MAC addresses

VLAN ID(e.g. - - Displays or specifies the VLAN ID of the

1,3-6) service. A disabled MAC address is valid
for the VLAN with the ID as specified by
this parameter.
MAC Address - - l Displays or specifies the disabled MAC

address. A disabled MAC address is
also called a blacklisted MAC address.
l The data frame that contains a disabled
destination MAC address is discarded.
A disabled MAC address needs to be
set manually and does not age.

VCTRUNK Port - - Displays the VCTRUNK to bind VC paths.
Level - - Displays the level of the bound VC paths.
Service Direction - - Displays the direction of the bound VC

paths.
Bound Path - - Displays the bound paths.
Number of Bound - - Displays the number of bound paths.

Paths

Table B-42 Parameters for self-learned MAC addresses

MAC Address - - l Displays or specifies the self-learned

MAC address. A self-learned MAC
address is also called a dynamic MAC
address.
l The entries of self-learned MAC
addresses are obtained when the bridge
uses the SVL or IVL learning mode. A
self-learned MAC address ages.
Port - - Displays the ID of the logical port of the

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

VLAN - - Displays the VLAN ID specified for

querying the self-learned MAC addresses.
Actual MAC - - Displays how many MAC addresses are

Address Table actually self-learned in the query condition
Capacity of a specific VLAN ID.
Table B-44 Parameters for VB port MAC address table capacity

Port - - Displays the ID of the logical port of the

bridge. The ID is specified for querying
the self-learned MAC addresses.
Actual MAC - - Displays how many MAC addresses are

Address Table actually self-learned in the query condition
Capacity of a specific VB port.

B.7.1.7 Parameter Description: VLAN Filtering Table_Creation

This section describes the parameters for creating VLAN filtering tables.
Navigation Path
2. Select an IEEE 802.1q or 802.1ad bridge and click the VLAN Filtering tab.
NOTE
In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning mode of the VB
must be IVL.
3. Click New.
VB - - Displays the bridge whose VLAN filtering

table is to be created.
VLAN ID(e.g. 1-4095 1 Specifies the VLAN IDs in the VLAN

1,3-6) filtering table.
l You can set this parameter to a number
or several numbers. When you set this
parameter to several numbers, use "," to
separate these discrete values and use
"-" to indicate continuous numbers. For
example, "1, 3-6" indicates numbers 1,
3, 4, 5, and 6.
Available - - Displays the ports mounted to the bridge.

forwarding ports
Selected - - Displays the selected forwarding ports.

forwarding ports l The selected forwarding ports can send
packets only among themselves.
l The selected forwarding ports can only
forward the packet that carries the
VLAN ID (e.g:1,3-6) tag. These ports
discard the packet that carries other
VLAN tags.
l The broadcast packet that carries the
VLAN ID(e.g.1,3-6) tag can be
forwarded only among the selected
forwarding ports.

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.

Board - - Displays the Ethernet board.
MAC Address l 1 to 120 Min 5 Min l If one entry is not updated in a certain
Aging Time l 1 to 120 Hour period, that is, if no new packet from
this MAC address is received to enable
l 1 to 12 Day 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 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.

Navigation Path
1. In the NE Explorer, select the EMS6 board. Choose Configuration > Ethernet
2. Click New.
Parameters
ERPS ID 1 to 7 - l This parameter

Ethernet ring
protection switching
(ERPS) instance.
l The IDs of ERPS
instances on an NE
must be different from
each other.
East Port - - This parameter specifies

the east port of the ERPS
instance.
West Port - - This parameter specifies

the west port of the ERPS
instance.
RPL Owner Ring Node Yes No l This parameter

Flag No specifies whether the
node on the ring is the
ring protection link
(RPL) owner.
l Only one node on the
ring can be set as the
RPL owner for each
Ethernet ring.
l An RPL owner needs
to balance the traffic
on each link of an
Ethernet ring.
Therefore, it is not
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.

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.

specifies the VLAN
ID of Control
VLAN.
l Each node on the
Ethernet ring
transmits the R-APS
packets on the
dedicated ring APS
(R-APS) channel to
ensure consistency
between the nodes
when the ERPS
switching is
performed. Control
VLAN is used for
isolating the dedicated
R-APS channel.
Therefore, the VLAN
ID in Control VLAN
cannot be duplicate
with the VLAN IDs
that are contained in
the service packets.
l The ID of a Control
VLAN must not be
the same as any
VLAN ID used by
Ethernet services. All
ring nodes should use
the same Control
VLAN ID.

Destination Node 01-19-A7-00-00-01 01-19-A7-00-00-01 This parameter indicates

default destination MAC
address in the R-APS
packets is always 01-19-
A7-00-00-01.
Loop Detect Enabled Enabled This parameter specifies

Disabled the Loop Detect.
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
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

No indicates whether a
node on the ring is
the ring protection
link (RPL) owner.
RPL Port - - This parameter

indicates the RPL
port.


indicates or
specifies the
VLAN ID of
Control VLAN.
l Each node on the
Ethernet ring
transmits the R-
APS packets on
the dedicated ring
APS (R-APS)
channel to ensure
consistency
between the
nodes when the
ERPS switching
is performed.
Control VLAN
is used for
isolating the
dedicated R-APS
channel.
Therefore, the
VLAN ID in
Control VLAN
cannot be
duplicate with the
VLAN IDs that
are contained in
the service
packets or inband
DCN packets.
l The Control
VLAN must be
set to the same
value for all the
NEs on an ERPS
ring.
Destination Node 01-19-A7-00-00-01 - This parameter

indicates the MAC
address of the
default destination
MAC address in the
R-APS packets is
always 01-19-
A7-00-00-01.

Hold-Off Time(ms) - 0 l This parameter

indicates or
specifies the
hold-off time of
the ERPS hold-
off timer.
l The hold-off
timer is used for
negotiating the
protection
switching
sequence when
the ERPS
coexists with
other protection
schemes so that
the fault can be
rectified in the
case of other
protection
switching (such
as LAG
protection) before
the ERPS occurs.
When a node on
the ring detects
one or more new
faults, it starts up
the hold-off timer
if the preset hold-
off time is set to a
value that is not
0. During the
hold-off time, the
fault is not
reported to trigger
an ERPS. When
the hold-off timer
times out, the
node checks the
link status
regardless
whether the fault
that triggers the
startup of the
timer exists. If the
fault exists, the
node reports it to
trigger an ERPS.
This fault can be

the same as or
different from the
fault that triggers
the initial startup
of the hold-off
timer.

Guard Time(ms) - 500 l This parameter

indicates or
specifies the
guard time of the
ERPS guard
timer.
l The nodes on the
ring continuously
forward the R-
APS packets to
the Ethernet ring.
As a result, the
outdated R-APS
packets may exist
on the ring
network. After a
node on the ring
receives the
outdated R-APS
packets, an
incorrect ERPS
may occur. The
ERPS guard timer
is an R-APS
timer used for
preventing a node
on the ring from
receiving
outdated R-APS
packets. When a
faulty node on the
ring detects that
the switching
condition is
cleared, the node
starts up the
guard timer and
starts to forward
the R-APS (NR)
packets. During
this period, the R-
APS packets
received by the
node are
discarded. The
received R-APS
packets are
forwarded only
after the time of

the guard timer

expires.

WTR Time(mm:ss) 5 to 12, in step of 1 5 l This parameter

indicates or
specifies the
WTR time of the
WRT timer in the
case of ERPS
protection.
l The WTR time
refers to the
duration from the
time when the
working channel
is restored to the
time when the
switching is
released. When
the working
channel is
restored, the
WTR timer of the
RPL owner starts
up. In addition, a
signal that
indicates the
operation of the
WTR timer is
continuously
output in the
timing process.
When the WTR
timer times out
and no switching
request of a
higher priority is
received, the
signal indicating
the operation of
the WTR timer is
not transmitted.
In addition, the
WTR release
signal is
continuously
output.
l The WTR timer
is used to prevent
frequent
switching caused
by the unstable
working channel.

Packet Transmit Interval(s) 1 to 10 5 This parameter

displays or specifies
the interval for
sending R-APS
packets periodically.
Entity Level 0 to 7 4 This parameter

the level of the
maintenance entity.
Last Switching Request - - This parameter

indicates the last
switching request.
RB Status - - This parameter

indicates the RB
(RPL Blocked) status
of the packets
received by the
working node.
l noRB: The RPL
is not blocked.
l RB: The RPL is
blocked.

DNF Status - - This parameter

indicates the DNF
status of the packets
received by the
working node.
l noDNF: The R-
APS packets do
not contain the
DNF flag. In this
case, the packets
are forwarded by
the node that
detects the fault
on a non-RPL
link, and the node
that receives the
packets is
requested to clear
the forwarding
address table.
l DNF: The R-APS
packets contain
the DNF flags. In
this case, the
packets are
forwarded by the
node that detects
the fault on an
RPL link, and the
node that receives
the packets is
informed not to
clear the
forwarding
address table.

State Machine Status - - This parameter

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.


VB - - Displays the created bridge.
Protocol Enabled Enabled Disabled l Indicates whether to enable the

Disabled spanning tree protocol.
l Try to avoid Layer 2 service loopbacks
in the service networking. If no loop
occurs, you need not start the STP/
RSTP.
l If the loop is already formed in the
service networking, you must start the
STP or RSTP.
Protocol Type STP RSTP l This parameter is valid only when

RSTP Protocol Enabled is Enabled.
l The protocol type should be set
according to the requirement of the
interconnected Ethernet equipment.
The default value is recommended
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters

This section describes the parameters for the spanning tree protocol.
Navigation Path
Tree.


Priority 0-61440 32768 l The most significant 16 bits of the

bridge ID indicate the priority of the
bridge.
l When the value is smaller, the priority
is higher. As a result, the bridge is more
likely to be selected as the root bridge.
l If the priorities of all the bridges on the
STP network take the same value, the
bridge whose MAC address is the
smallest is selected as the root bridge.
MAC Address - - Displays the MAC address of a bridge.
Max Age(s) 6-40 20 l Indicates the maximum age of the

CBPDU packet that is recorded by the
port.
l The greater the value, the longer the
transmission distance of the CBPDU
packet, and the greater the network
diameter. When the value of this
parameter is greater, however, the link
fault detection of the bridge is slower
and thus the network adaptability is
reduced.
Hello Time(s) 1-10 2 l Indicates the interval for transmitting

CBPDU packets through the bridge.
l The greater the value of this parameter,
the less the network resources that are
occupied by the spanning tree. As the
value of this parameter increases,
however, the topology stability
decreases.
Forward Delay(s) 4-30 15 l Indicates the holding time of a port in

the listening state and in the learning
state.
l The greater the value, the longer the
delay of the network state change.
Therefore, the topology changes are
slower and recovery in the case of
faults is slower.
TxHoldCout(per 1-10 6 Indicates how many times the port

second) 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.

Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board, and choose Configuration > Layer-2
2. Click the Port Parameters tab.

Port - - Displays the created bridge.
Priority 0-240 128 l The most significant eight bits of the

port ID indicate the port priority.
l The smaller the value of this parameter,
the higher the priority.
Port Path Cost 1-200000000 - l Indicates the status of the network to

which the port is connected.
l In the case of the bridges on both ends
of the path, set this parameter to the
same value.
Status - - Displays the state of a port.
Admin Edge Enabled Disabled l Is valid only when the RSTP is used.
Attribute Disabled l Specifies whether to set the port to an
edge port. The edge port refers to the
bridge port that is connected only to the
LAN. The edge port receives the
BPDU and does not transmit the
BPDU.
l Set this parameter to Enabled only
when the Ethernet port on the Ethernet
board is directly connected to the data
communication terminal equipment,
such as a computer. In other cases, it is
recommended that this parameter takes
the default value.
Protocol Enabled Enabled Enabled l Specifies whether the STP or RSTP is

Disabled enabled for the port.
l When this parameter is set to Disabled,
the port does not process or transmit
the BPDU.

Auto Edge Enabled Disabled l Is valid only when Admin Edge

Detection Disabled Attribute is set to Enabled.
if the bridge detects that this port is
connected to the port of another bridge,
the RSTP considers this port as a non-
edge port.
l When Admin Edge Attribute is set to
Enabled, set this parameter to
Enabled. In other cases, it is
recommended that this parameter takes
the default value.
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
2. Click the Bridge Running Information tab.
Priority - - Displays the priority of the bridge. The

most significant 16 bits of the bridge ID
indicate the priority of the bridge.
MAC Address - - Displays the MAC address of the bridge.
Designed Root - - Displays the priority of the specified

Bridge Priority bridge.
Designed Root - - Displays the MAC address of the specified

Bridge MAC bridge.
Address
Root Path Cost - - Displays the root path cost. The root path
cost is the path cost of the root port and is
used for calculating the network topology.

Root Port - - Displays the root port of the spanning tree

protocol.
Max Age(s) - - Displays the maximum age of the CBPDU

packet that is recorded by the port.
Hello Time(s) - - Displays the interval for transmitting the

CBPDU packets through the bridge.
Forward Delay(s) - - Displays the holding time of a port in

listening state and in learning state.
HoldCout - - Displays the number of times that each

port transmits CBPDU packets per second.
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
2. Click the Port Running Information tab.

Port - - Displays the logical port of the bridge.
Port ID - - Displays the port ID.
Port Status - - Displays the port status.
Port Path Cost - - Displays the port path cost.
Designated Port - - Displays the ID of the specified port.

ID
Designated Root - - Displays the priority of the specified root

Bridge Priority bridge.
Designated Root - - Displays the MAC address of the specified

Bridge MAC root bridge.
Address

Designated Path - - Displays the specified path cost.

Cost
Designated Bridge - - Displays the priority of the specified

Priority bridge.
Designated Bridge - - Displays the MAC address of the specified

MAC Address bridge.
Topology - - Displays the enabled status of topology

Detection detection.
Edge Port Status - - Displays the enabled status of the edge

port.
Running Time(s) - - Displays the duration when the topology

remains unchanged.
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
2. Click the Point to Point Attribute tab.

Port - - Displays the internal and external ports on

the Ethernet board.

Point-to-point Adaptive Adaptive l This parameter is valid only when the

Attribute connection connection RSTP is used.
Link connection l If this parameter is set to Adaptive
Shared media connection, the bridge determines the
actual point-to-point attribute of the
port according to the actual working
mode of the port. If the port works in
full-duplex mode, the actual point-to-
point attribute of the port is True. If the
port works in half-duplex mode, the
actual point-to-point attribute of the
port is False.
l If you set this parameter to Link
connection, the actual point-to-point
attribute of the port is True.
l If you set this parameter to Shared
media, the actual point-to-point
attribute of the port is False.
l Only the port whose actual point to
point attribute is True can transmit the
fast transition request and response
messages.
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling

This section describes the parameters for enabling the IGMP snooping protocol.
Navigation Path
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from
the Function Tree.
2. Click the Enable IGMP Snooping Protocol tab.

VB - - Displays the ID of the bridge.

Protocol Enable Enabled Disabled l Specifies whether to enable the IGMP

Disabled snooping protocol.
l If the IGMP multicast router exists on
the interconnected Ethernet network,
enable the IGMP snooping protocol
according to the requirements of the
router.
The Discarded Tag Disabled Disabled l This parameter specifies the method of
of the Packet the port to process unknown multicast
Excluded in the packets. When the IEEE 802.1q or
Multicast Group 802.1ad bridge receives the multicast
packets whose multicast addresses are
not included in the multicast table,
these packets are considered as
unknown packets.
Protocol Enable is Enabled.
l If this parameter is set to Disabled,
unknown multicast packets are
broadcast in the VLAN.
l Set this parameter as required by the
IGMP multicast server.
Max.Non- 1 to 4 3 If the bridge transmits an IGMP group

Response Times 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
the Function Tree.
2. Click the Static Multicast Table tab.

3. Click New.

VB ID - - Displays the ID of the created bridge.
VLAN ID - - Specifies the VLAN ID of the static

multicast table entry.
MAC Address - - l Specifies the MAC address in the static

multicast table.
Multicast Port - - l Specifies the port as an entry in the

static multicast table.
l An entry in the static multicast table
does not age.
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
the Function Tree.
2. Click the Multicast Aging Time tab.


Multicast Aging 1-120 8 l Specifies the aging time for multicast

Time(Min) table entries. When a dynamic
multicast table entry is not updated in a
certain period (that is, no IGMP request
from this multicast address is received),
this entry is automatically deleted. This
mechanism is called aging, and this
period is called aging time.
l If this parameter is set to a very great
value, the bridge stores excessive
multicast table entries that are no
longer needed, which exhausts the
resources of the multicast table.
l If this parameter is set to a very small
value, the bridge may delete the
multicast table entry that is needed,
which reduces the forwarding
efficiency.
l The default value is recommended.
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
2. Click the Link Aggregation Group Management tab.
3. Click New.
Attribute Parameters
LAG No. EFP8: 1-12 1 Specifies the LAG number.

EMS6: 1-8
LAG Name - - Specifies the LAG name.

LAG Type Static Static l Static: A static LAG is created by the

Manual user. To add or delete a member port,
you need to run the Link Aggregation
Control Protocol (LACP) protocol. In a
static LAG, a port can be in selected,
standby, or unselected state. By running
the LACP protocol, devices exchange
aggregation information so that they
share the same aggregation
information.
l Manual: A manual LAG is created by
the user. When you add or delete a
member port, you need not run the
LACP protocol. In a manual LAG, a
port can be in the UP or DOWN state.
The system determines whether to
aggregate a port according to its
physical state (UP or DOWN), working
mode, and rate.
Load Sharing Sharing Sharing l Sharing: In a sharing LAG, all member

Non-Sharing ports always share the traffic load. The
sharing mode can improve bandwidth
utilization on a link. When the member
ports are changed or some member
ports fail, the traffic load of each
member port is automatically re-
allocated.
l Non-Sharing: In a non-sharing LAG,
only one member port carries the traffic
load and the other member ports are in
Standby state. Actually, a non-sharing
LAG works in hot-standby mode.
When the active port fails, the system
selects a standby port to substitute for
the failed port, thus preventing a link
failure.
Sharing Mode IP Sharing Mode IP Sharing Mode You can set this parameter only when
MAC Sharing Load Sharing is Sharing.
Mode

Revertive Mode Revertive Revertive l You can set this parameter only when
Non-Revertive Load Sharing is Non-Sharing.
l If this parameter is set to Revertive,
services are automatically switched
back to the working path after the
working path recovers.
l If this parameter is set to Non-
Revertive, services are still transmitted
in the protection path after the working
path recovers and the LAG remains the
same.
Port Setting Parameters

Main Port - - l Specifies the main port in a LAG.

l After a LAG is created, you can add
Ethernet services to the main port only.
That is, services cannot be added to a
slave port.
l When Load Sharing is set to Non-
Sharing, the link connected to the
main port is the working path and the
links connected to the slave ports are
protection paths.
Available Standby - - l Specifies the slave port in a LAG.

Ports l After a LAG is created, you need to
perform manual operations to add or
delete a slave port.
Selected Standby - - Displays the selected slave ports.

Ports
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation

This section describes the parameters for port priorities and system priorities.
Navigation Path
2. Click the Link Aggregation Parameters tab.


Port Priority 0-65535 32768 l This parameter is valid only when

LAG Type of a LAG is set to Static.
l This parameter indicates the priorities
of the ports in a LAG as defined in the
LACP protocol. The smaller the value,
the higher the priority.
Parameters for the system settings

System Priority 0-65535 32768 l This parameter is valid only when

LAG Type of a LAG is set to Static.
l This parameter indicates the priority of
a LAG. The smaller the value, the
l When the local LAG and the opposite
LAG negotiate through LACP packets,
one can obtain the system priority of
the other. The LAG with the higher
system priority is considered as the
comparison result. Then, the
aggregation information is consistent at
both ends. If the local LAG and the
opposite LAG have the same system
priority, the MAC addresses are
compared. The LAG with a lower
MAC address is considered as the
comparison result. Then, the
aggregation information is consistent at
both ends.
System MAC - - Displays the MAC address of the system.

Address
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point

Service LPT
This section describes the parameters for creating point-to-point service LPT.

Navigation Path
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click Query.

VCTRUNK Port - - Displays the VCTRUNK used by the

Ethernet service.
Direction - - l Displays the direction of the Ethernet

service at the port.
l The service direction is set to positive
when the source port is a PORT and the
sink port is a VCTRUNK; the service
direction is set to reverse when the
source port is a VCTRUNK and the
sink port is a PORT.
LPT Yes No Specifies whether to enable the LPT.

No
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l Specifies the bearer mode of the LPT
Ethernet packets.
GFP-CSF l The default value is recommended.
PORT-Type Port 0-10000 100 l When the link on which Ethernet

Hold-Off services are transmitted is configured
Time(ms) with other protection schemes, you
need to set the hold-off time of LPT.
This enables the NE to notify the
equipment at both ends of a
transmission network of the fault on the
transmission link only when the other
protection schemes fail.
l This parameter is valid only in the
positive direction of LPT.

VCTRUNK Port 0-10000 100 l When the link on which Ethernet

Hold-Off services are transmitted is configured
Time(ms) 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-to-

Multipoint Service LPT
This section describes the parameters for creating point-to-multipoint service LPT.
Navigation Path
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
2. Click PtoMP LPT. Then, the LPT Management dialog box appears.
3. Click New.
Parameters for Convergence Points

Port - - Specifies the port of the convergence

point.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when
Ethernet the selected port is a VCTRUNK.
Port Hold-Off 0-10000 0 When the link on which Ethernet services

Time(ms) are transmitted is configured with other
protection schemes, you need to set the
hold-off time of LPT. This enables the NE
to notify the equipment at both ends of a

Parameters for Access Points

Port - - Specifies the port at the access node.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) l This parameter can be set only when
Ethernet the selected port is a VCTRUNK.
B.7.2.16 Parameter Description: Port Mirroring_Creation

This section describes the parameters for creating port mirroring tasks.
Navigation Path
Configuration > Ethernet Interface Management > Port Mirroring from the
Function Tree.
2. Click New.

Mirrored Port - - l After the mirroring function of the port

is configured, you can monitor all the
mirrored ports by analyzing the packets
at the mirroring port only. As a result,
you can easily manage the ports.
l Mirrored Port indicates the port that
sends the packets copied from
Mirrored Upstream Port and
Mirrored Downstream Port.
l Mirrored Port cannot be set to a port
that carries any service.
Mirrored - - l Mirrored Upstream Port and

Upstream Port Mirrored Downstream Port indicate
the ports that copy packets for
Mirrored Port.
l Mirrored Upstream Port can be a
PORT or a VCTRUNK. As a PORT,
the 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.

Mirrored - - l Mirrored Downstream Port can be a

Downstream Port 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
Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MD from the drop-down list.

Maintenance Domain For example: MD1 - Specifies the name of the

Name MD.

Maintenance Domain Consumer High(7) Operator Low(0) Specifies the level of the
Level Consumer Middle(6) MD. The greater the
value, the higher the
Consumer Low(5) level.
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
Tree.
2. In the right pane, click OAM Configuration.
3. Click New and choose Create MA from the drop-down list.

Maintenance Domain For example: MD1 - Displays the MD in

Name which an MA is to be
created.
Maintenance For example: MA1 - This parameter specifies

Association Name the name of the MA,
which is a service-related
domain. By creating
MAs, the connectivity
check (CC) can be
performed on the network
that transmits a particular
service instance.
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs

This section describes the parameters for creating a maintenance point (MP).

Navigation Path
Tree.
2. Click New.

Maintenance - NULL Specifies the maintenance domain (MD) of

Domain Name the MP.
NOTE
An MD is not required for a common MP. For
the creation of a common MP, select NULL.
Maintenance - NULL Specifies the maintenance association

Association Name (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 Uniquely identifies an MP. From the

00-00-0000 to FF- highest to the lowest, the first byte
FF-1FFF indicates the network number, the second
Common MP: byte indicates the number of the node in
00-00-0000 to FF- the local network, and the third and forth
FF-FF00 bytes indicate the ID of the MP on the
network node. The MP ID must be unique
in the entire network.
Type MEP MEP Specifies the MP type defined in IEEE

MIP 802.1ag. An MP can be a maintenance
association end point (MEP) or a
maintenance association intermediate point
(MIP).

Service Direction SDH SDH l Specifies the MEP direction.

IP l Set this parameter to SDH if the OAM
data initiated by the MEP travels
through the Ethernet switching unit on
the local NE. Otherwise, set this
parameter to IP.
Table B-56 Parameters for advanced attributes

Level Consumer High(7) Provider High(4) Specifies the level of a common MP. The
Consumer greater the value, the higher the level.
Middle(6) NOTE
This parameter is valid only for a common MP
Consumer Low(5) (NULL).
Provider High(4)
Provider Low(3)
Operator High(2)
Operator Middle(1)
Operator Low(0)
CC Status Active Inactive Specifies whether to enable the

Inactive connectivity check (CC) function at an
MP.
LB Timeout(ms) 3000 to 60000, in 5000 l Specifies the timeout duration of an LB

step of 100 test.
l This parameter can be set only for an
MEP.
LT Timeout(ms) 3000 to 60000, in 5000 l Specifies the timeout duration of an LT

step of 100 test.
MEP.

CCM Sending Standard MP: Standard MP Specifies the interval for sending the CCM
Period(ms) 1000 1000 packet at the MP where the CC test is
performed.
10000 Common MP:
l If this parameter takes a very small
6000 5000 value, service bandwidth decreases
600000 significantly.
Common MP: l If this parameter takes a very large
1000 to 60000, in value, the CC test will become less
step of 100 capable in detecting service
interruptions. The default value is
recommended.
MEP.
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB

This section describes the parameters for enabling the LB.
Navigation Path
Tree.
2. Select the node that requires an LB test, click OAM Operation, and select Start LB.

LB Source MEP ID - - Specifies the ID of the

source maintenance point
in the LB test.
LB Sink MEP ID - - Specifies the ID of the

sink maintenance point in
the LB test.
Test Result - - Indicates the result of one

LB test.
Test based on the MAC Selected Not selected Select this parameter for
Address Not selected an LB test based on MAC
addresses.
NOTE
only for a standard MP.

LB Sink MP MAC - - Specifies the MAC

Address address of the sink
maintenance point in the
LB test. This parameter is
valid only in the case of
Test based on the MAC
Address.
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT

This topic describes the parameters for enabling the LT.
Navigation Path
Tree.
2. Select the node that requires an LT test, click OAM Operation, and select Start LT.

LT Source MP ID - - Specifies the source MP

in the LT test.
LT Sink MP ID - - Specifies the sink MP in

the LT test.
Responding MP ID - - Displays the MP that

responds to the test.
Responding MP Type - - Displays the type of the

MP that responds to the
test.
Hop Count - - Displays the count of

hops between the source
MP and the responding
MP. That is, the number
of responding MPs from
the source MP to a
certain responding MP in
an LT test.
Test Result - - Indicates the result of one

LT test.

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
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function
Tree.
PORT - - Displays the name of the

external Ethernet port.
Enable OAM Protocol Enabled Disabled Specifies whether the

Disabled point-to-point OAM
protocol is enabled.
After the OAM protocol
is enabled, the current
Ethernet port starts to use
the preset mode to set up
an OAM connection with
the opposite end.
OAM Working Mode Active Active The negotiation mode of

Passive Ethernet port OAM
includes active and
passive modes.
If this parameter is set to
Active, the port can
initiate an OAM
connection. If this
parameter is set to
Passive, the port can only
respond to the OAM
connection requests from
the opposite end.
Link Event Notification Enabled Enabled Specifies whether the

Disabled detected link event is
notified to the opposite
end (for example, error
frame periods, error
frames, and error frame
seconds).

Max OAM Packet - - Displays the maximum

Length(byte) length of the OAM
packets.
This parameter takes the
same value as the
Maximum Frame
Length (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
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function
Tree.
2. Click the OAM Error Frame Monitor tab.

PORT For example: - Displays the name of the external Ethernet

PORT1 port.
Error Frame 1000 to 60000, in 1000 In the specified Error Frame Monitor
Monitor step of 100 Window (ms), if the number of error
Window(ms) frames exceeds the specified Error Frame
Monitor Threshold (frames) due to the
link degradation, the link event alarm is
reported.
Error Frame 1 to 4294967295, in 2 Specifies the threshold of monitoring error

Monitor step of 1 frames.
Threshold(frames)

Error Frame 1488 to 89280000, GE port: 1488000 Within the specified value of Error
Period in step of 1 FE port: 148800 Frame Period Window (frames), if the
Window(frames) number of error frames on the link exceeds
the preset value of Error Frame Period
Threshold (frames), an alarm is reported.
Error Frame 1 to 89280000, in 2 Specifies the threshold of monitoring the

Period step of 1 error frame period.
Threshold(frames)
Error Frame 10 to 900, in step of 60 If any error frame occurs in one second,
Second Window(s) 1 this second is called an error frame second.
Within the specified value of Error
Frame Second Window(s), if the number
of error frames on the link exceeds the
preset value of Error Frame Second
Threshold (s), an alarm is reported.
Error Frame 1 to 900, in step of 2 Specifies the threshold of monitoring error

Second 1 frame seconds.
Threshold(s)
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 - - Displays the name of the

remote Ethernet port.
Remote OAM Working - - Displays the working

Mode mode of the remote
Ethernet port.

Field Value Range Default Value Description
Link Event Notification - - Displays whether the

remote Ethernet port can
notify link events to the
local port.
Remote Side Loopback - - Displays how the remote

Response Ethernet port responds to
a loopback.
Unidirectional - - Displays whether the

Operation remote Ethernet port
supports unidirectional
operations.
Max.OAM Packet - - Displays the maximum

Length (byte) OAM packet size
supported by the remote
Ethernet port.
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
2. Click the Flow Configuration tab.
3. Click New.


Flow Type Port Flow Port Flow l Port flow: The packets from a certain
Port+VLAN Flow port are classified as a type of flow.
The Ethernet service associated with
Port+SVLAN Flow this flow type is the line service or
Port+CVLAN Layer 2 switching service that uses this
+SVLAN Flow port as the service source.
Port+VLAN l Port+VLAN flow: The packets that are
+Priority Flow from a certain port and have a specified
VLAN ID are classified as a type of
flow. The associated Ethernet service of
this flow type is the EVPL service
(based on VLAN) or EVPLAN service
(based on the 802.1q bridge) that uses
this PORT+VLAN as the service
source.
l Port+SVLAN flow: The packets that
are from a certain port and have a
specified SVLAN ID are classified as a
type of flow. The associated Ethernet
service of this flow type is the EVPL
service (based on QinQ) or EVPLAN
service (based on the 802.1ad bridge)
that uses this PORT+SVLAN as the
service source.
l Port+CVLAN+SVLAN flow: The
packets that are received from or
transmitted to a certain port and have a
specified CVLAN+SVLAN are
classified as a type of flow. The
associated Ethernet service of this flow
type is the EVPL service (based on
QinQ) or EVPLAN service (based on
the 802.1ad bridge) that uses this PORT
+CVLAN+SVLAN as the service
source.
l Port+VLAN+Priority flow: The
packets that are from a certain port and
have a specified VLAN ID and a
specified VLAN priority are classified
as a type of flow. The associated
Ethernet service of this flow type is the
line service that uses this Port+VLAN
+Priority as the service source.


NOTE
An EMS6 board does not support Port+VLAN
+Priority Flow.
Port EFP8: PORT1 to PORT1 l When the associated service is the line
PORT9, service, set this parameter to the source
VCTRUNK1 to port or sink port of the associated
VCTRUNK16 Ethernet service.
EMS6: PORT1 to l When the associated service is the
PORT7, Layer 2 switching service, set this
VCTRUNK1 to parameter to a mounted port of the
VCTRUNK8 bridge.
VLAN ID 1 to 4095 1 l This parameter is valid only when

Flow Type is set to Port+VLAN Flow
or Port+VLAN+Priority Flow.
l Set this parameter to the source VLAN
of the associated Ethernet service.
C-VLAN 1 to 4095 1 l This parameter is valid only when

Flow Type is set to Port+CVLAN
+SVLAN Flow.
l Set this parameter to the source C-
VLAN of the associated Ethernet
service.
S-VLAN 1 to 4095 1 l This parameter is valid only when

Flow Type is set to Port+SVLAN
Flow or Port+SVLAN+CVLAN
Flow.
l Set this parameter to the source S-
VLAN of the associated Ethernet
service.
Priority - - l This parameter is valid only when

Flow Type is PORT+VLAN+Priority
Flow.
l This parameter indicates the VLAN
priority of the flow-associated Ethernet
services.
NOTE
An EMS6 board does not support Priority.
B.7.4.2 Parameter Description: QoS Management_Creation of CAR

This section describes the parameters for creating CAR.

Navigation Path
QoS Management > Flow Management from the Function Tree.
2. Click the CAR Configuration.
3. Click New.

CAR ID EFP8: 1 to 512 1 This parameter identifies a CAR

EMS6: 1 to 1024 operation, and is used to bind a flow to an
associated CAR operation.
Enabled/Disabled Enabled Disabled Indicates whether to enable the CAR

Disabled operation performed on the flow bound to
the CAR.
Committed EFP8: 0 to 100032, 0 l Indicates the CIR. When the rate of a

information Rate in steps of 64 packet is not more than the CIR, this
(kbit/s) EMS6 (FE ports): 0 packet passes the restriction of the
to 102400, in steps CAR and is forwarded first even in the
of 64 case of network congestion.
EMS6 (GE ports): l The value of this parameter should not
0 to 1024000, in be more than the PIR.
steps of 64
Committed Burst EFP8: 0 to 1024 0 Indicates the CBS. When the rate of a
Size (kbyte) EMS6: 0 to 16384 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.

Peak information EFP8: 0 to 100032, 0 l Indicates the PIR. When the rate of a
Rate (kbit/s) in steps of 64 packet is more than the PIR, the packet
EMS6 (FE ports): 0 that exceeds the rate restriction is
to 102400, in steps directly discarded. When the rate of
of 64 packets is more than the CIR but is
lower than or equal to the PIR, these
EMS6 (GE ports): packets whose rate exceeds the CIR
0 to 1024000, in can pass the restriction of the CAR and
steps of 64 are marked yellow.
l The value of this parameter should not
be more than the port bandwidth.
Maximum Burst EFP8: 0 to 1024 0 Indicates the MBS. When the rate of the
Size (kbyte) EMS6: 0 to 16384 packet that passes the restriction of the
CAR is more than the CIR but is not more
than the PIR, some packets can burst and
are marked yellow. The maximum traffic
of the burst packets is determined by the
MBS. Note that the MBS has an inherent
size, and this parameter indicates the
increment value only. The inherent size of
the MBS is determined by the PIR. The
greater the PIR, the greater the MBS.
B.7.4.3 Parameter Description: QoS Management_Creation of CoS

This section describes the parameters for creating CoS.
Navigation Path
3. Click New.

CoS ID EFP8: 1-64 1 This parameter identifies a CoS operation,

EMS6: 1-1054 and is used to bind a flow to an associated
CoS operation.

CoS Type simple simple l If the CoS type of a flow is set to

VLAN Priority simple, all the packets in this flow are
directly scheduled to a specified egress
IPTOS queue.
DSCP l If the CoS type of a flow is set to
VLAN priority, the packets in this flow
are scheduled to specified egress
queues according to the user priorities
specified in the VLAN tags of these
packets.
l If the CoS type of a flow is set to
DSCP, the packets in this flow are
scheduled to specified egress queues
according to differentiated services
code point (DSCP) in the IPv6 tags of
these packets.
l If the CoS type of a flow is set to IP
TOS, the packets in this flow are
scheduled to specified egress queues
according to the TOS values carried in
the IPv4 packets. This CoS type is
applicable to IPv4 packets.
CoS parameter - - Displays the CoS parameters

corresponding to different CoS types.

CoS Priority 0-7 - This parameter determines to which egress

queue a packet is schedule.
l Each Ethernet port on the EFP8/EMS6
board supports eight egress port
queues. Queues 1-8 respectively
correspond to the CoS priorities from 0
to 7.
l Queue 8, with the CoS priority of 7, is
as SP queue. Queues 1-7, with the CoS
priorities from 0 to 6, are WRR queues.
The weighted proportion of these WRR
queues is 1:2:4:8:16:32:64 (from
priority 0 to priority 6). On the EFP8
board, the weighted proportion of these
WRR queues cannot be changed. On
the EMS6 board, the weighted
proportion of these WRR queues can
be changed.
l If the traffic shaping feature of some
queues is enabled, bandwidth is
allocated first to the queues whose
traffic shaping feature is enabled based
on the CIR. The remaining bandwidth
is allocated to the eight queues by using
the SP+WRR algorithm.
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS

This section describes the parameters for creating CAR/CoS.
Navigation Path
QoS Management > Flow Management from the Function Tree.
2. Click the Flow Configuration tab.

Flow Type - - Displays the type of a flow.
VB ID - - Displays the ID of the bridge.
Port - - Displays the port where a flow is to be

created.

C-VLAN - - l Displays the C-VLAN.

l This parameter is valid is Flow Type is
Port+VLAN Flow, Port+CVLAN
+SVLAN Flow, or Port+VLAN
+Priority Flow.
S-VLAN - - l Displays the S-VLAN.

l This parameter is valid when Flow
Type is Port+SVLAN Flow or Port
+CVLAN+SVLAN Flow.
Priority - - l Displays the priority of the flow.

l This parameter is valid when Flow
Type is Port+VLAN+Priority Flow.
Bound CAR - None This parameter indicates the CAR ID

corresponding to a CAR operation.
Different CAR IDs should be bound to
different flows, even though the
parameters of the CAR operations are the
same.
Bound CoS - None Indicates the CoS ID that corresponds to a

CoS operation.
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.
Port Queue - - Displays the queue name.

Status Enabled Disabled Indicates whether to enable the traffic

Disabled shaping feature of an egress queue.
CIR (kbit/s) EFP8: 0 to 100032, 0 l When the rate of a packet is not more
in steps of 64 than the CIR, this packet directly enters
EMS6 (FE ports): 0 the egress queue.
to 102400, in steps l The value of this parameter should not
of 64 be more than the PIR.
EMS6 (GE ports): 0
to 1024000, in steps
of 64
DCBS (kbyte) - 0 Displays the excess burst size.
PIR (kbit/s) EFP8: 0 to 100032, 0 l When the rate of a packet is more than
in steps of 64 the PIR, the packet that exceeds the
EMS6 (FE ports): 0 rate restriction is directly discarded.
to 102400, in steps When the rate of packets is more than
of 64 the CIR but not more than the PIR, the
packets that exceed the restriction of
EMS6 (GE ports): 0 the CIR enter the buffer of the CIR.
to 1024000, in steps When the buffer overflows, the packets
of 64 are marked yellow and enter the egress
queue, which enables the packets to be
discarded first in the case of queue
congestion.
l The value of this parameter should not
be more than the port bandwidth.
DMBS (kbyte) - 0 Displays the maximum excess burst size.

Scheduling Mode SP Queue 1: WRR By default, queue 8 (with the CoS priority
WRR Queue 2: WRR of 7) of the EMS6 board is the SP queue,
and queues 1-7 (with the respective CoS
Queue 3: WRR priority of 0-6) are the WRR queues and
Queue 4: WRR their weights are in the proportion of
Queue 5: WRR 1:2:8:16:32:64.
Queue 6: WRR The scheduling principles of the SP+WRR
are as follows:
Queue 7: WRR
l A port immediately transmits the
Queue 8: SP
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 Queue 1: 1 By default, queue 8 (with the CoS priority
from 1 to 64 Queue 2: 2 of 7) of the EMS6 board is the SP queue,
and queues 1-7 (with the respective CoS
Queue 3: 4 priority of 0-6) are the WRR queues and
Queue 4: 8 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.

Click the Port Shaping tab.
Status Enabled Disabled This parameter specifies whether to enable

Disabled the traffic shaping at a port.
PIR (kbit/s) EMS6 (FE ports): 0 0 In the case of an EMS6 board, the PIR of a
to 102400, in steps port meets the following constraints:
of 64 l The PIR of the port is equal to or more
EMS6 (GE ports): 0 than the PIR of any queue at this port.
to 1024000, in steps l The PIR of the port is equal to or more
of 64 than the sum of the CIRs of all the
queues at this port.
B.7.5 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the EoS/EoPDH plane.
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
Port - - Displays the name of the external port.
Name - - Displays or specifies the name of the

external port.

Enabled/Disabled Enabled Disabled l If the port gains access to services, set

Disabled this parameter to Enabled. Otherwise,
set this parameter to Disabled.
l If this parameter is set to Enabled for
the port that does not access services,
an ETH_LOS alarm may be generated.
This parameter is invalid for PORT9 on an
EFP8 board.
EMS6 board.
Working Mode EFP8: Auto-Negotiation l Different types of Ethernet ports

l Auto- support different working modes.
Negotiation l If the opposite port works in auto-
l 10M Half- negotiation mode, set this parameter to
Duplex Auto-Negotiation.
l 10M Full- l If the opposite port works in full-
Duplex duplex mode, set this parameter to 10M
Full-Duplex or 100M Full-Duplex,
l 100M Half- depending on the rate of the opposite
Duplex port.
l 100M Full- l If the opposite port works in half-
Duplex duplex mode, set this parameter to 10M
EMS6: Half-Duplex or 100M Half-Duplex,
l Auto- depending on the rate of the opposite
Negotiation port, or set this parameter to Auto-
Negotiation.
l 10M Half-
Duplex l GE optical ports on an EMS6 board
support only Auto-Negotiation and
l 10M Full- 1000M Full-Duplex modes.
Duplex
NOTE
l 100M Half- This parameter is invalid for PORT9 on an
Duplex EFP8 board.
l 100M Full- This parameter is invalid for PORT7 on an
Duplex EMS6 board.
l 1000M Full-
Duplex

Maximum Frame EFP8: 1518 to 2000 1522 l Set this parameter to a value greater
Length (bytes) EMS6: 1518 to than the maximum length of all the data
9600 frames to be transmitted.
l The default value is recommended if
the jumbo frame is not considered and
the data frames contain only one layer
of VLAN tags or even no tags. The
value of 1526 or greater is
recommended if the data frames
contain two layers of tags, such as
QinQ.
Port Physical - - Displays the actual working status of a

Parameters PORT.
EFP8 board.
EMS6 board.
MAC Loopback Non-Loopback Non-Loopback l A MAC loopback is to loop back the

Loopback Ethernet frames transmitted to the
opposite port.
l Use the default value unless otherwise
specified.
PHY Loopback Non-Loopback Non-Loopback l A PHY loopback is to loop back the

Loopback Ethernet physical signals transmitted to
the opposite port.
l Use the default value unless otherwise
specified.
EFP8 board.
EMS6 board.
Table B-69 Parameters for flow control


Non- Disabled Disabled l This parameter is valid only when

Autonegotiation Enable Symmetric Working Mode is not set to Auto-
Flow Control Flow Control Mode Negotiation.
Mode l If this parameter is set to Enable
Send Only
Symmetric Flow Control Mode, the
Receive Only port can send PAUSE frames and
process the received PAUSE frames.
l If this parameter is set to Send Only,
the port can send PAUSE frames in the
case of congestion but cannot process
the 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 Disabled Disabled l This parameter is valid only when

Flow Control Enable Working Mode is Auto-Negotiation.
Mode Dissymmetric Flow l If this parameter is set to Enable
Control Symmetric Control, the port can send
Enable Symmetric PAUSE frames and process the
Control received PAUSE frames.
Enable Symmetric/ l If this parameter is set to Enable
Dissymmetric Flow Dissymmetric Flow Control, the port
Control can send PAUSE frames in the case of
congestion but cannot process the
received PAUSE frames.
l If this parameter is set to Enable
Symmetric/Dissymmetric Flow
Control, the port can function as
follows:
– Sends and processes PAUSE
frames.
– Sends but does not process PAUSE
frames.
– Processes but does not send PAUSE
frames.
autonegotiation flow control mode of
the opposite port.
EFP8 board.
EMS6 board.

Table B-70 Parameters for the tag attributes

TAG Tag Aware Tag Aware l With different tag attributes, the port
Access processes frames in different modes.
For details, see Table B-73.
Hybrid
l Set this parameter to Tag Aware if the
port processes the frames with VLAN
tags (or tagged frames).
l Set this parameter to Access if the port
processes the frames without VLAN
tags (or untagged frames).
l Set this parameter to Hybrid if the port
processes the tagged frames and
untagged frames.
Default VLAN ID 1-4095 1 l This parameter is valid only when TAG

is set to Access or Hybrid.
l For the usage of this parameter, see
Table B-73.
VLAN Priority 0-7 0 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 l Indicates whether to check the

Disabled incoming packets according to the tag
attribute.
Table B-71 Parameters for the network attributes


Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Awareor S-
Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter
Table B-72 Parameters for the advanced attributes

Broadcast Packet Disabled Disabled This parameter specifies whether to restrict

Suppression Enabled the traffic of broadcast packets according
to the proportion of the broadcast packets
to the total packets. Set this parameter to
Enabled when a broadcast storm may
occur at the opposite port.
Broadcast Packet 10%-100% 30% When the proportion of the received

Suppression broadcast packets to the total packets
Threshold crosses the threshold, the port discards the
received broadcast packets. Set this
parameter to a value greater than the
proportion when no broadcast storm
occurs. The value of 30% or greater is
recommended.

Traffic Threshold EFP8: - Specifies the traffic threshold of the port.

(Mbit/s) l 0 to 100 You can specify the traffic monitoring
(PORT1 to period by setting Port Traffic Threshold
PORT8) Time Window(Min).
l 0 to 1000
(PORT9)
EMS6:
l 0 to 1000
(PORT1 and
PORT2)
l 0 to 100
(PORT3 to
PORT6)
l 0 to 1000
(PORT7)
Port Traffic 0-30 0 Specifies the traffic monitoring period.

Threshold Time l If Port Traffic Threshold Time
Window(Min) Window(Min) is set to 0, an associated
alarm is reported at the moment when
the traffic received at the port crosses
the value of Traffic
Threshold(Mbit/s).
l If the Port Traffic Threshold Time
Window(Min) is set to a value other
than 0, an associated alarm is reported
only when the traffic received at the
port always crosses the value of Traffic
Threshold(Mbit/s) in the monitoring
period.
Loop Detection Enabled Disabled This parameter specifies whether to enable

Disabled loop detection, which is used to check
whether a loop exists on the port.
Table B-73 Methods used by ports to process data frames

Direction Type of Data Processing Method
Frame
Tag aware Access Hybrid
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.


Frame
Untagged frame Discards the frame. The port receives The port receives
the frame after the frame after
adding to the frame adding to the frame
the VLAN tag that the VLAN tag that
contains Default contains Default
VLAN ID and VLAN ID and
VLAN Priority. VLAN Priority.
Egress port Tagged frame Transmits the The port strips the l If the VLAN ID
frame. VLAN tag from the in the frame is
frame and then Default VLAN
transmits the frame. ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
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
Port - - Displays the name of the internal

port.
Name - -

TAG Tag Aware Tag Aware l With different tag attributes,

Access the port processes frames in
different modes. For details,
Hybrid see Table B-79.
l Set this parameter to Tag
Aware if the port processes the
frames with VLAN tags (or
tagged frames).
l Set this parameter to Access if
the port processes the frames
without VLAN tags (or
untagged frames).
l Set this parameter to Hybrid if
the port processes the tagged
frames and untagged frames.
Default VLAN ID 1-4095 1 l This parameter is valid only

when TAG is set to Access or
Hybrid.
l For the usage of this parameter,
see Table B-79.
VLAN Priority 0-7 0 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 l Indicates whether to check the

Disabled incoming packets according to
the tag attribute.
Table B-75 Parameters for encapsulation or mapping

Port - - Displays the name of the internal port.

Mapping Protocol GFP GFP The default value is recommended.

HDLC The EFP8 board supports GFP only.
LAPS
Scramble Scrambling Mode Scrambling l Indicates the scrambling polynomial

[X43+1] Mode[X43+1] used by the mapping protocol.
Scrambling Mode l The default value is recommended.
[X48+1]
Unscrambled
Set Inverse Value - - l This parameter indicates whether the

for CRC value of the CRC field defined in the
LAPS or HDLC encapsulation frame
format will be reversed. This means
that this parameter takes effect only if
Mapping Protocol is set to LAPS or
HDLC.
l Set Set Inverse Value for CRC to the
same value for the VCTRUNKs at both
ends.
Check Field FCS32 FCS32 l When the Ethernet board uses the GFP
Length No mapping protocol, set this parameter to
FCS32 or No.
l When you set this parameter to FCS32,
a 32-bit FCS is used.
FCS Calculated Big endian Big endian l When you set this parameter to Big
Bit Sequence Little endian endian, the least significant byte of the
FCS is placed first and the most
significant byte is placed last.
l When you set this parameter to Little
endian, the most significant byte of the
FCS is placed first and the least
significant byte is placed last.
Table B-76 Parameters for the network attributes


Port Attributes UNI UNI l If this parameter is set to UNI, the port
C-Aware processes data frames according to the
tag attribute.
S-Aware
l If this parameter is set to C-Aware or
S-Aware, the port processes the data
frames by using the processing method
of QinQ services.
l Set this parameter to C-Aware or S-
Aware when the port processes QinQ
services. Otherwise, this parameter
Table B-77 Parameters for the LCAS

Enabling LCAS Disabled Disabled l Indicates whether to enable the LCAS

Enabled function.
l The LCAS can dynamically adjust the
number of virtual containers for
mapping required services to meet the
bandwidth needs of the applications.
As a result, the bandwidth utilization is
improved.
LCAS Mode Huawei Mode Huawei Mode l Indicates the sequence in which the
Standard Mode LCAS sink sends the MST control
packet and Rs-Ack control packet.
l When you set this parameter to
Huawei Mode, the LCAS sink first
sends the Rs-Ack and then sends the
MST.
l When you set this parameter to
Standard Mode, the LCAS sink first
sends the MST and then sends the Rs-
Ack.
l If the equipment at the opposite end is
the third-party equipment and does not
support the Huawei mode, set this
parameter to Standard Mode.
Otherwise, set this parameter to
Huawei Mode.

Hold Off Time(ms) An integer ranging 2000 l When a member link is faulty, the
from 0, 2000 to LCAS performs switching after a delay
10000, in the of time to prevent the situation where
increments of 100 an NE simultaneously performs a
protection switching such as SNCP and
performs an LCAS switching. This
parameter specifies the duration of the
delay.
WTR Time(s) 0-720 300 l When the time after a member link is
restored to normal reaches the specified
value of this parameter, the VCG uses
the restored member link.
TSD Disabled Disabled l Indicates whether the TSD is used as a

Enabled condition for determining whether a
member link is faulty. In the case of the
VC-12, the TSD refers to the BIP_SD.
In the case of the VC-3, the TSD refers
to the B3_SD_VC3.
Table B-78 Parameters for bound path

Range Value
VCTRUNK Port EFP8: VCTRUNK Specifies the VCTRUNK to

VCTRUNK 1 bind paths.
1-
VCTRUNK
16
EMS6:
VCTRUNK
1-
VCTRUNK
8
Level - - Displays the level of the

bound VC path.
In the case of the EFP8
board, this parameter
always takes the value of
VC12-Xv.


Range Value
Service Direction Bidirectional Bidirectional l Specifies the direction of

Uplink the bound path.
Downlink l Set this parameter to
Bidirectional unless
otherwise specified.
Bound Path - - You need to plan and set

this parameter according to
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

Frame
Ingress port Tagged frame Receives the frame. Discards the frame. Receives the frame.


Frame
Untagged frame Discards the frame. The port receives The port receives
the frame after the frame after
adding to the frame adding to the frame
the VLAN tag that the VLAN tag that
contains Default contains Default
VLAN ID and VLAN ID and
VLAN Priority. VLAN Priority.
Egress port Tagged frame Transmits the The port strips the l If the VLAN ID
frame. VLAN tag from the in the frame is
frame and then Default VLAN
transmits the frame. ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
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.


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 81 00 8100 Specifies the type field of QinQ frames.

Area(Hexadecimal 88 A8 Set this parameter according to the type
) field of the accessed QinQ frames.
91 00
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
In the NE Explorer, select the required NE from the Object Tree and choose Configuration >


LSR ID - 0.0.0.0 l Specifies or

displays the LSR
ID of an NE. On a
PSN, each NE is
assigned a unique
LSR ID.
l This parameter
must be set in IPv4
address format.
Start of Global Label Space 0-1015808 0 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 MPLS-
enabled network,
global label spaces
of NEs are
recommended to
overlap each other
if possible.
Global Label Space Size - - Displays the size of a

global label space.
Start of Multicast Label Space - - The OptiX RTN 900

does not support this
parameter.
TTL Processing Mode pipe pipe Specifies the TTL

uniform Processing Mode.

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

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 Set Port AIS Status

Enabled to Enabled if you
want to suppress
alarms triggered by an
MPLS tunnel fault
that results from a
port fault.

Channel Type 0 to FFFF 7FFA l Specifies the

channel type in an
MPLS-TP OAM
packet.
l Set Channel Type
to the same value
for all NEs on a
network.
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 When AC link

Disabled failures must be
notified to its peer end
in real time, set CSF
Status to Enabled.
Ping/Tracert Socket Port Status 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
Configuration > MPLS Management > Unicast Tunnel Management from the
Function Tree.
3. Click Query.

Tunnel Key - - Displays the tunnel Key.


customized tunnel name.
Enable State Enabled Enabled Specifies or displays

Disabled whether a tunnel is
enabled.
NOTE
The OptiX RTN 900
supports only the value
Enabled.
Node Type - - l Displays the node

type.
l For bidirectional
tunnels, this parameter
displays the node
types of forward
tunnels.

a tunnel.
CIR(kbit/s) No Limit - l Specifies or displays

1024-1024000 the committed
information rate (CIR)
of a tunnel.
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) - - The OptiX RTN 900 does

not support this
parameter.
CBS(byte) - - The OptiX RTN 900 does

not support this
parameter.
PBS(byte) - - The OptiX RTN 900 does

not support this
parameter.

Bandwidth - - The OptiX RTN 900 does

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 - - Displays the MPLS label

Label that a forward tunnel
carries when entering a
node.
Reverse Outgoing Label - - Specifies the MPLS label

that a reverse tunnel
carries when entering a
tunnel.
Out Port - - Displays the egress port

of a forward tunnel,
which is also the ingress
port of the mapping
reverse tunnel.
Forward Outgoing - - Displays the MPLS label

Label that a forward tunnel
carries when leaving a
node.
Reverse Incoming Label - - Displays the MPLS label

that a reverse tunnel
carries when leaving a
node.
Forward Next Hop - - Displays the IP address of

Address the next-hop port of a
forward tunnel.
Reverse Next Hop - - Displays the IP address of

Address the next-hop port of a
reverse tunnel.
Source Node - - Displays the LSR ID of

the ingress node.
Sink Node - - Displays the LSR ID of

the egress node.
Tunnel Type - - Displays the tunnel type.

EXP 0-7 - l Specifies or displays

None the value of the EXP
field in the packets
transmitted through
MPLS tunnels.
l For unidirectional
is available only if
Node Type is Ingress.
l For bidirectional
cannot be set if Node
Type is Transit.
to a value from 0 to 7,
the EXP field takes its
fixed value.
l If this parameter takes
its default value None,
the EXP field varies
based on the DiffServ
mappings.
LSP Mode Pipe - l Displays or specifies

the LSP mode.
l Pipe: When stripping
MPLS tunnel labels
from packets, an
egress node does not
update the scheduling
priority for the
packets.
l For bidirectional
is available only if
Node Type is Egress.
l For bidirectional
cannot be set if Node
Type is Transit.
NOTE
On the OptiX RTN 900,
this parameter can be set to
Pipe only.
MTU(byte) - - The OptiX RTN 900 does

not support this
parameter.

Protection Group - - Displays the MPLS APS

protection group to which
a tunnel belongs.
VLAN ID - - l Specifies or displays

the VLAN ID that
Ethernet packets carry
when transmitted over
MPLS tunnels.
l If packets need to
traverse a Layer 2
network, set the
VLAN ID for the
tunnel carried by the
NNI port according to
the VLAN planning
requirements on the
Layer 2 network.
the same value for
both ends of a tunnel.

CoS CS7 - l This parameter

CS6 specifies the PHB
service class of an L-
EF LSP, if the type of an
AF4 MPLS tunnel is L-
AF3 LSP.
AF2 l CS6-CS7: indicates
the highest service
AF1
grade, which is mainly
BE 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.
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 - - Displays the 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
Function Tree.


3. Click New and choose Unidirectional Tunnel from the drop-down list.
The New Unicast Unidirectional Tunnel dialog box is displayed.
4. Select New Reverse Tunnel.

Range Value
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

Egress forward tunnel.
Transit
Direction - - Indicates the direction of a tunnel.
CIR(kbit/s) No Limit No Limit l Specifies the committed

1024-102400 information rate (CIR) of a
0 tunnel.
l Generally, it is recommended
that you set this parameter to
No Limit. If you need to limit
the tunnel bandwidth, set this
parameter to be the same as the
planned tunnel bandwidth.
CBS(kbit/s) - - The OptiX RTN 900 does not

PIR(Byte) - - The OptiX RTN 900 does not

PBS(Byte) - - The OptiX RTN 900 does not

In Board/Logic Interface Type - - Specifies the MPLS port at the

ingress direction of a forward
tunnel on a transit or egress node.


Range Value
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 - - Specifies the MPLS port at the

egress direction of a forward
Out Port - - 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 16-1048575 - Specifies the MPLS label at the

egress direction of a forward
tunnel on an ingress or transit
node.


Range Value
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 Specifies the tunnel type.

L-LSP l The value E-LSP indicates
that the EXP field is used to
identify packet scheduling
priorities of PWs. An E-LSP
tunnel can contain PWs of
eight packet scheduling
priorities.
l The value L-LSP indicates
that the MPLS label value is
used to identify packet
scheduling priorities of PWs.
An L-LSP tunnel can contain
PWs of the same packet
scheduling priority.


Range Value
EXP 0-7 None l Specifies the value of the EXP

None field in the packets transmitted
through MPLS tunnels.
l This parameter is available
only if Node Type is Ingress.
l If this parameter is set to a
value from 0 to 7, the EXP
field takes its fixed value.
l If this parameter takes its
default value None, the EXP
field is set based on the
DiffServ mappings.
LSP Mode Pipe Pipe l Pipe: When stripping MPLS

tunnel labels from packets, an
egress node does not update
the scheduling priority for the
packets.
l This parameter is available
only if Node Type is Egress.
NOTE
The OptiX RTN 900 supports only
the value Pipe.
MTU - - The OptiX RTN 900 does not



Range Value
CoS CS7 BE l This parameter specifies the

CS6 PHB service class of an L-LSP,
if the type of an MPLS tunnel
EF is L-LSP.
AF4 l CS6-CS7: indicates the highest
AF3 service grade, which is mainly
AF2 involved in signaling
transmission.
AF1
l EF: indicates fast forwarding.
BE
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
Function Tree.
3. Click New and choose Bidirectional Tunnel from the drop-down list.


Tunnel ID 1 to 65535 - l Specifies the tunnel ID.

l The total number of tunnels and
PWs must be equal to or less than
1024. The number of tunnels that
carry PWs is not included in the
total.
Tunnel Name - - Specifies the tunnel name.
Node Type Ingress Ingress Specifies the node type of a forward

Egress tunnel.
Transit
Direction - - Indicates the direction of a tunnel.
CIR(kbit/s) No Limit No Limit l Specifies the committed

1024-1024000 information rate (CIR) of a tunnel.
l Generally, it is recommended that
you set this parameter to No Limit.
If you need to limit the PW
bandwidth, set this parameter to be
the same as the planned tunnel
bandwidth.
CBS(kbit/s) - - The OptiX RTN 900 does not support

this parameter.
PIR(Byte) - - The OptiX RTN 900 does not support

this parameter.
PBS(Byte) - - The OptiX RTN 900 does not support

this parameter.
In Board/Logic - - Specifies the MPLS port at the ingress

Interface Type direction of a forward tunnel on a
transit or egress node.

In Port - - NOTE
l If the MPLS port is an FE/GE port,
ensure that:
l The Port Mode parameter of the
MPLS port is set to Layer 3
according to 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 - - Specifies the MPLS port at the egress

Interface Type direction of a forward tunnel on an
Out Port - -
NOTE
The method and prerequisites for setting
parameters of the MPLS port at the egress
direction of a forward tunnel are the same
as those on the ingress direction.
Forward Out Label 16 to 1048575 - Specifies the MPLS label at the egress
direction of a forward tunnel on an

Reverse In Label 16 to 1048575 - l Specifies the MPLS label at the

ingress direction of a reverse tunnel
on an ingress or transit node.
l The Reverse In Label and
Forward Out Label parameters
can be set to either the same value
or different values.
Forward Next Hop - - l The Forward Next Hop Address

Address parameter needs to be set only for
the egress port on an ingress or
transit node.
ingress port on the next hop LSR
node to Forward Next Hop
Address according to the network
plan.
Reverse Next Hop - - l The Reverse Next Hop Address

Address parameter needs to be set only for
the ingress port on a transit or
egress node.
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

Tunnel Type E-LSP E-LSP l Specifies the tunnel type.

L-LSP l The value E-LSP indicates that the
EXP field is used to identify packet
scheduling priorities of PWs. An E-
LSP tunnel can contain PWs of
eight packet scheduling priorities.
l The value L-LSP indicates that the
MPLS label value is used to
identify packet scheduling
priorities of PWs. An L-LSP tunnel
can contain PWs of the same
packet scheduling priority.
EXP 0 to 7 None l Specifies the value of the EXP field

None in the packets transmitted through
MPLS tunnels.
l This parameter cannot be set if
Node Type is Transit.
l If this parameter is set to a value
from 0 to 7, the EXP field takes its
fixed value.
l If this parameter takes its default
value None, the EXP field is set
based on the DiffServ mappings.
LSP Mode Pipe Pipe l Pipe: When stripping MPLS tunnel

labels from packets, an egress node
does not update the scheduling
priority for the packets.
l This parameter cannot be set if
Node Type is Transit.
NOTE
The OptiX RTN 900 supports only the
value Pipe.
MTU - - The OptiX RTN 900 does not support

this parameter.

CoS CS7 BE l This parameter specifies the PHB

CS6 service class of an L-LSP, if the
type of an MPLS tunnel is L-LSP.
EF
l CS6-CS7: indicates the highest
AF4 service grade, which is mainly
AF3 involved in signaling transmission.
AF2 l EF: indicates fast forwarding. This
AF1 service class is applicable to the
traffic whose delay is small and
BE
packet loss ratio is low, for
example, voice and video services.
l AF1-AF4: indicates assured
forwarding. This service class is
applicable to the traffic that
requires rate guarantee but does not
require delay or jitter limit.
l BE: indicates that the traffic is
forwarded in best-effort manner
without special processing.
B.8.1.6 Parameter Description: Unicast Tunnel Management_OAM Parameters

This topic describes parameters that are related to MPLS OAM.
Navigation Path
Function Tree.

Tunnel ID - - Displays the tunnel ID.
Tunnel Name - - Displays the tunnel name.
Node Type - - l Displays the node

type.
l For bidirectional
displays the node
types of forward
tunnels.

Tunnel Direction - - Displays the direction of

a tunnel.
OAM Status Enabled Disabled l Specifies or displays

Disabled whether the local node
can perform and
respond to OAM
operations.
l If OAM Status is
Enabled, the local NE
can perform and
respond to OAM
operations.
l If OAM Status is
Disabled, the local
NE cannot perform
and respond to OAM
operations.
l If MPLS APS
protection needs to be
configured or a CC
test needs to be
performed for the
tunnel, OAM Status
needs to be set to
Enabled.

Detection Mode Adaptive Adaptive l Specifies or displays

Manual the MPLS OAM
detection mode.
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.


fixed interval.
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.

Packet Detection 3.3 50 l Displays or specifies

Interval(ms) 10 the OAM detection
period.
20
l This parameter is
50 available only when
100 Detection Packet
200 Type is FFD. It takes
its fixed value of 1000
500
ms when Detection
Packet Type is CV.
3.3 for MPLS APS
usually. If the packet
transmission delay
time of an MPLS
tunnel exceeds 3.3 ms,
the transmission
interval of FFD
packets needs to be a
value greater than the
delay time.
Reverse Tunnel ID - - l Specifies the mapping

reverse tunnel of a
forward tunnel.
cannot be set.
CV/FFD Status - - Displays whether

CV/FFD is enabled.
Local LSP Status - - Displays whether an LSP

is available.
Local LSP Defect Type - - Displays the LSP defect

type.
Local Disable LSP - - Displays the duration

Duration(ms) when an LSP is
unavailable.
Local LSP Defect - - Displays the LSR ID of a

Location node where LSP defects
are detected.
Remote LSP Defect - - Displays whether an LSP

Type is available.
Remote LSP Defect - - Displays the LSP defect

Type type.

Remote Disable LSP - - Displays the duration

Duration(ms) when an LSP is
unavailable.
Remote LSP Defect - - Displays the LSR ID of a

Location node where LSP defects
are detected.
SD Threshold(%) 0-100 0 l Specifies or displays

the SD threshold.
When the OAM
packet loss ratio is
higher than the
parameter value, the
corresponding alarm
is reported.
can be set for its
egress node only.
is set to 0, SD
threshold detection is
not supported.
SF Threshold(%) 0-100 0 l Specifies or displays

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.

B.8.1.7 Parameter Description: Unicast Tunnel Management_FDI

This topic describes FDI parameters.
Navigation Path
Function Tree.
2. Click the FDI tab.

Enable FDI Selected Selected l Specifies or displays

Not selected whether Enable FDI
is selected.
l If the FDI function is
enabled for a transit
node, the transit node
inserts an FDI packet
to all LSPs that travel
through the transit
node when a fault
occurs on the link
between the ingress
and transit nodes. On
reception of the FDI
packet, the egress
node reports an alarm.
In this case, if MPLS
APS is configured
correctly, protection
switching is triggered
before the egress node
detects an LSP defect
within a detection
period.
l Generally, the default
parameter value is
recommended.
B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Ping

This topic describes the parameters that are related to the LSP Ping test.

Navigation Path
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.

Packet Count 1 to 4294967295 3 Specifies the number of

test request packets.
EXP Value 0 to 7 7 l Specifies the EXP

value of the MPLS
label in test request
packets. The value 7
priority.
recommended.
TTL 1 to 255 255 l Specifies the time-to-

live (TTL) value of
the MPLS label in test
request packets.
recommended.
Transmit 1 to 1000 100 l Specifies the interval

Interval(10ms) for transmitting test
request packets.
recommended.
Packet Length 64 to 1400 64 l Specifies the length of

recommended.
Response Timeout 1 to 6000 300 l Specifies the wait-to-

Period(10ms) response timeout
value.
recommended.

Response Mode IPv4 UDP Response IPv4 UDP Response l Specifies the response
No Response mode of test request
packets.
Application Control
Channel Response l The value No
Response indicates
that the test
performance event is
reported without
sending response
packets.
l The value
Application Control
Channel Response
indicates that response
is performed through
the reverse channel.
l The value IPv4 UDP
Response indicates
that the IPv4 UDP
packets encapsulating
MPLS echo reply
messages are sent as
response packets.
Response is reserved
for scenarios where all
nodes on an LSP
communicate with
each other over a
DCN running IP
protocols.
based on the situation
of the egress node. If
the egress node
supports reverse
channel response, set
this parameter to
Application Control
Channel Response. If
the egress node does
not support reverse
channel response but
supports DCN
channel response by
means of IP protocols,
IPv4 UDP Response.


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
Function Tree.
2. Click the OAM Parameters tab.
3. Select the required tunnel, click OAM Operation in the lower right corner, and choose


value of the MPLS
label in test request
packets. The value 7
priority.
recommended.

live (TTL) value of
the MPLS label in test
request packets.
recommended.

recommended.


value.
recommended.

packets.
Application Control
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.


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
3. Click the MEP tab.
Parameters in the window for setting MEP parameters

Tunnel ID - - Displays the ID of a

tunnel.
Tunnel Name - - Displays the name of a

tunnel.
Node Type - - Displays the type of a

node.
Tunnel Direction - - Displays whether a tunnel

is bidirectional or
unidirectional.
Reverse Tunnel ID - - This parameter needs to

be set for a unidirectional
tunnel.
OAM Status Disabled Disabled Set this parameter to

Enabled Enabled when the
MPLS-TP tunnel OAM
function needs to be used.

MEG ID Type IP Based IP Based l When all NEs

ICC Based connected to an MPLS
tunnel are Huawei
Customer Based devices that supports
I-based MPLS-TP
OAM components, it
is 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.
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 7 It is recommended that

you set MEG Level to 7.
MEP ID 1 to 8191 - Set MEP ID at the source

end to the same value as
RMEP ID 1 to 8191 - RMEP ID at the sink
end.

Detection Mode Adaptive Adaptive l Manual: tests whether

Manual a tunnel is available
based on the user-
defined CCM
transmission interval.
l Adaptive: tests
whether a tunnel is
available based on the
interval at which
CCMs have been
received.
to Adaptive.
l Detection Mode
cannot be specified for
the ingress node of a
unidirectional tunnel.
CC Status - - Displays the CC status.
CC Packet Priority 0 to 7 7 l It is recommended that

you set CC Packet
Priority to 7 to ensure
that CC packets are
forwarded with
priority.
l CC Packet Priority
cannot be specified for
the egress node of a

CC Packet Interval (ms) 3.3 1000 l If the MPLS-TP OAM

10 CC function is used
for only continuity
100 check, it is
1000 recommended that you
set CC Packet
Interval (ms) to the
default value 1000.
l If the MPLS-TP OAM
CC function is used to
trigger MPLS APS, it
is 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 l If an NE is the S-PE

Enabled 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 Set Lock Status to Lock

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 - - Displays whether the LSP

is available at the local
end.

Local LSP Defect Type - - Indicates the type of the

tunnel defect at the local
end.
Local LSP Disabled - - Displays the duration

Duration (ms) when the LSP at the local
end is unavailable.
Local LSP Defect - - Displays the LSR ID of

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 - - Specifies the type of the

Type LSP defect at the opposite
end.
Remote LSP Disabled - - Displays the duration

Duration (ms) when the LSP at the
opposite end is
unavailable.
Remote LSP Defect - - Displays the LSR ID of

Location the node that has detected
the LSP defect.
SD Threshold (%) 0 to 100 0 l Displays or specifies

the SD threshold. An
alarm is reported if the
OAM packet loss ratio
is larger than the SD
threshold.
can be specified only
for the egress node.
l When the value is set
to 0, SD threshold
detection is not
supported.

SF Threshold (%) 0 to 100 0 l Displays or specifies

the SF threshold. An
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 - - Displays the source node

of a tunnel.
Sink Node - - Displays the sink node of

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
3. Click the MIP tab.
4. Click New.
Parameters in the Window for Creating an MIP

Tunnel – - Specifies the tunnel on

which an MIP needs to be
created.

MEG ID Type ICC Based ICC Based l It is recommended

Customer Based that you set MEG ID
Type to ICC Based.
with non-Huawei
this parameter to
Customer Based.
MEG ID - - l Set MEG ID to the

MPLS tunnel.
l Set MEG ID to
nodes connected to
different MPLS
tunnels.
MP ID 1 to 8191 - Each MP on an MPLS

tunnel must have a unique
MP ID.
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
4. Select one or more tunnels and choose OAM Operation > Start LB.
Parameters in the window for setting LB parameters

MEG ID - - Displays the MEG ID and

MEP ID. If the MEG ID
Local MEP ID - - type is in an IP address
format, the MEG ID or
MEP ID is not displayed.

Node Type MEP MEP Specifies whether the

MIP sink end of the tested
tunnel is an MEP or MIP.
Remote MEP/MIP ID - - l Set Remote

or IP Address MEP/MIP ID or IP
Address according to
the termination node
of an LB test.
l If MEG ID Type is
set to IP Based for the
termination node, set
Remote MEP/MIP
ID or IP Address to
the LSR ID of the
termination node.
l If MEG ID Type is
not set to IP Based
for the termination
node, set Remote
MEP/MIP ID or IP
Address to the MP ID
of the termination
node.
Packet Count 1 to 65535 3 l Specifies the number

of packets that can be
transmitted each time.
l It is recommended
that this parameter
Packet Priority 0 to 7 7 l Specifies the packet

priority.
l It is recommended
that this parameter

TTL 1 to 255 355 l If Node Type is MIP,

set TTL to the
number of hops
between the source
MEP and the current
MIP.
l If Node Type is
MEP, set TTL to a
value that is greater
than or equal to the
number of hops
between the current
MEP and the remote
MEP. It is
recommended that
this parameter take its
default value.
Transmit Interval 100ms 100ms l Specifies the packet

1s transmission interval.
10s l It is recommended
that this parameter
Packet length 128 to 1410 128 l Specifies the packet

length.
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
Configuration > MPLS Management > PW Management from the Function Tree.
2. Click the PW Management tab.

PW ID - - Displays the ID of the PW that carries a

service.
PW Status - - Displays whether a PW is enabled.

PW Signaling - - Displays the PW signaling type.

Type NOTE
The RTN 900 uses only static PWs.
PW Type - - l Displays the PW type. Different PW

types perform different service
processing modes.
l When a PW transmits E-Line services,
set PW Type to Ethernet or Ethernet
Tagged Mode.
l If a PW transmits circuit emulation
services (CESs), set PW Type to
CESoPSN or SATop.
l If a PW transmits ATM services, set PW
Type to ATM n-to-one VCC Cell
transport, ATM one-to-one VCC Cell
Mode, ATM n-to-one VPC Cell
transport, or ATM one-to-one VPC
Cell Mode.
NOTE
OptiX RTN 905 does not support ATM services.
PW Direction - - Displays the direction of a PW.
PW Incoming - - Displays the ingress label at the source port

Label of a PW.
PW - - Displays the encapsulation type of the

Encapsulation packets on a PW.
Type NOTE
The RTN 900 supports only MPLS encapsulation.
PW Outgoing - - Displays the egress label at the sink port of a

Label PW.
Peer LSR ID - - Displays the LSR ID of the node at the other

end of a PW.
Local - - Displays the working status of the PW at the

Operating local end.
Status
Remote - - Displays the working status of the PW at the

Operating remote end.
Status
Overall - - Displays the working status of the entire

Operating PW.
Status

Tunnel Type - - Displays the type of the tunnel that carries a

PW.
NOTE
The RTN 900 supports only MPLS tunnels.
Ingress - - Displays the ID of the tunnel that carries a

Tunnel PW.
Egress Tunnel - -
Deployment - - Displays the deployment status of a PW.

Status
Tunnel - - The RTN 900 does not support this

Automatic parameter.
Selection
Policy
QoS Parameters
Table B-81 CES services

PW ID - - Displays the ID of the

PW that carries a service.

the PW that carries a
service.
CIR(kbit/s) - - The RTN 900 does not

EXP - - The RTN 900 does not

Table B-82 E-Line services



service.

Bandwidth Limit - - Displays whether the

bandwidth is limited.
CIR(kbit/s) - - Displays the committed

a PW.
CBS(byte) - - Displays the committed

PIR(kbit/s) - - Displays the peak

a PW
PBS(byte) - - Displays the peak burst

size (PBS) of a PW.

LSP Mode - - Displays the LSP mode.

NOTE
The RTN 900 supports only
Pipe.
Policy - - The RTN 900 does not

Table B-83 ATM services



service.
Bandwidth Limit - - Displays whether the

bandwidth is limited.
CIR(kbit/s) - - Displays the committed

a PW.
CBS(byte) - - Displays the committed

PIR(kbit/s) - - Displays the peak

a PW

PBS(byte) - - Displays the peak burst

size (PBS) of a PW.

Policy - - The RTN 900 does not


PW ID - - Displays the PW ID.
RTP Head - - Displays whether the

CES service packets
carry an RTP header.
Packet Loading - - Displays the packet

Time(us) loading time.
Jitter Compensation - - Displays the jitter buffer

Buffering Time(us) time for the received CES
packets.
Ingress Clock Mode - - The RTN 900 does not

Egress Clock Mode - - The RTN 900 does not

Control Channel Type - - Displays the control

channel type.
VCCV Verification - - Displays the VCCV

Mode mode.
Enable CES Service - - Displays whether CES

Alarm Transparent service alarms are
Transmission transparently transmitted.
Threshold of Entering - - Displays the threshold of

R bit Inserting Status the packet loss ratio of
CES services. The
corresponding alarm will
be reported if the actual
packet loss ratio crosses
this threshold.

Threshold of Exiting R - - Displays the threshold of

bit Inserting Status received CES service
packets. The
be cleared after the actual
number of received CES
service packets crosses
this threshold.
Sequence Number - - Displays the sequence

Mode number mode.


control word is used to
transfer packet
information. For ETH
PWE3 services, this
parameter is always not
used.

channel type.

Mode mode.
Request VLAN - - When PW Type is

Ethernet Tag, this
parameter displays the
VLAN ID to be added to
packets that are sent from
the opposite end and do
not carry any VLAN IDs.
TPID - - When PW Type is

Ethernet Tag, this
TPID.


transfer packet
information.

channel type.

Mode mode.
Max Concatenated Cell - - Displays the maximum

Count number of concatenated
cells.

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
2. Click the MS PW tab.
3. Click New.

ID - - Specifies the ID of MS-PW.
Name - - Specifies the name of MS-PW.
MTU(bytes) - - The OptiX RTN 900 does not support this

parameter.
Service Type Ethernet Service Ethernet Service l Specifies the type of services carried by
CES Service the MS-PW.
ATM Service l Set this parameter according to the
NOTE

Connection Port Transparent Port Transparent l This parameter is available only when
Type PVP Service Type is ATM Service.
PVC l PVP: Only the VPIs of the source and
sink are exchanged.
l PVP: The VPIs and VCIs of the source
and sink are exchanged.
l Port Transparent: ATM transparent
transmission refers to the transparent
transmission of ATM cells that are
encapsulated into PWs as payloads.
NOTE
The OptiX RTN 905 does not support this
parameter.
Parameters for the Basic Attributes of PWs


PW Signaling Type Static Static Specifies the signaling

type of the PW. Labels
for static PWs need to be
manually assigned.

PW Type - - l Specifies the type of

the PW.
Ethernet if Service
Type is ETH Service
and no VLAN IDs
need to be added. If it
is required to add
VLAN IDs, set this
parameter to Ethernet
Tag Mode and then
set Request VLAN in
the Advanced
Attribute tab.
l If Service Type is
CES Service, the
value CESoPSN
indicates structure-
aware emulation,
which allows timeslot
compression; the
value SAToP
indicates structure-
agnostic emulation,
which does not allow
timeslot compression.
l If Service Type is
ATM Service, set this
parameter according
to the value of
Connection Type.
NOTE
OptiX RTN 905 does not
support ATM services.
PW Direction - - Displays the direction of

the PW.
PW Encapsulation Type - - Displays the

PW.

label.
PW Outging Label 16 to 1048575 - Specifies the PW Egress

label.

Tunnel Selection Mode Manually Manually Specifies the method to

select tunnels.
NOTE
The OptiX RTN 950
Manually.
Tunnel Type MPLS MPLS Specifies the type of the

PW.
Ingress Tunnel - - A created tunnel needs to

be selected. If no tunnel
is available, no PW can
be created.

be automatically
assigned.
Egress Tunnel - - For a bidirectional tunnel,

the system will configure
the reverse tunnel
automatically.
QoS Parameters
NOTE
CES Services


Ethernet services

is enabled.
or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.


a PW.


a PW.

size (PBS) of a PW.


does not update the
the packets.

ATM services


bandwidth limit is
enabled.
l This function can be
used to limit the
bandwidth of one or
more PWs, or the
bandwidth of one or
more ATM PWE3
services, in an MPLS
tunnel. (One ATM
PWE3 service
corresponds to one
PW.)
l An ATM PWE3
the bandwidth of
ATM PWE3 services
in an MPLS tunnel.

not support this
parameter.
CIR (Kbit/s) - - Specifies the committed

the PW.
CBS (kbyte) - - Specifies the excess burst

size of the PW.

the PW.
PBS (kbyte) - - Specifies the maximum

excess burst size of the
PW.


not support this
parameter.
Parameters for the Advanced Attributes of PWs

NOTE
CES Services
RTP Header Disable Disable l Specifies the RTP

Enable header.
l The RTP header
carries time stamps.
recommended.
Jitter Compensation 375 to 16000 8000 l Specifies the jitter

Buffering Time(us) buffer time for the
received CES packets.
l A greater value of this
parameter means
fewer impacts of
transmission jitters on
CES services, greater
delays of CES
services, and more
resources occupied by
CES services.
recommended.
NOTE
Set Jitter Compensation
Buffering Time(us) to a
value greater than the value
of Packet Loading
Time(us) at the opposite
end and the local end.

Packet Loading 125 to 5000 1000 l Specifies the length of

Time(us) fragments in the TDM
data stream. Each
fragment is
encapsulated into one
PW packet.
l A greater value of this
parameter means
higher encapsulation
efficiency but greater
delays of CES
services.
recommended.
Ingress Clock mode - - The OptiX RTN 900 does

not support this
parameter.
Egress Clock mode - - The OptiX RTN 900 does

not support this
parameter.
Control Channel Type None CW l Specifies the mode of

CW PW connectivity
check.
Alert Label
l The value None
indicates that the
control word is not
supported. That is, the
PW connectivity
check is not
supported.
VCCV packets in
Alert Label
encapsulation mode.
l The value CW
indicates that the
control word is
supported.

VCCV Verification None Ping l Specifies the VCCV

Mode Ping verification mode.
The VCCV
PW connectivity
check.
this parameter to
None.
64K Timeslot Number 1 to 31 1 l Specifies the number

of 64 kbit/s timeslots
that transmit service
traffic. If Frame
Mode of the opposite
end is 30, the source
64 kbit/s timeslots at
the local end must
include the 16th
timeslot.
l On the two ends of a
radio link, the timeslot
lists can be different
but the numbers of
timeslots must be the
same.
l This parameter is
unavailable if PW
Type is SAToP.
Sequence Number Huawei Mode Huawei Mode Specifies the sequence

Mode Standard Mode number mode.

Ethernet services

words when
encapsulating ETH
PWE3 packets.
NOTE
control words when
Description.

VCCV is not used.
VCCV packets in
Alert Label
encapsulation mode.
VCCV packets
used.

The VCCV
this parameter to
None.

when PW Type is
Ethernet Tagged
Mode.
do not carry any
VLAN IDs, the PW
the packets as
of this parameter.

TPID - - OptiX RTN 900 does not

support request VLAN
TPID of the PW level.
ATM services
Control Word Must Use Must Use l Specifies whether to

No Use use the control word.
In the MPLS packet
switching network,
the control word is
used to transmit
packet information.
l Set Control Word to
Must Use if PW Type
is ATM 1:1.
Control Channel Type CW CW l Specifies the mode of

None PW connectivity
check.
Alert Label
l The value None
indicates that the
control word is not
PW connectivity
check is not
supported.
l The value CW
indicates that the
control word is
supported.
l The value Alert
Label indicates
VCCV packets in
Alert Label
encapsulation mode.


The VCCV
PW connectivity
check.
this parameter to
None.
Max. Concatenated Cell 1 to 31 10 l Specifies the

Count maximum number of
concatenated cells.
l If the value 1 is
assumed, only one
ATM cell is
encapsulated in one
packet. If the value
from 2 to 31 is
assumed, a maximum
of 2 to 31 ATM cells
are encapsulated into
one packet.
Packet Loading Time 100 to 50000 1000 l Specifies the packet

(us) loading time. Once
the packet loading
time expires, the
packet is sent out even
if the concatenated
cells are less than the
maximum.
l If Max.
Concatenated Cell
Count assumes the
value 1, this
parameter is
ineffective. That is,
the packet will be sent
out once the cell is
loaded.
B.8.1.15 Parameter Description: PW Management_PW OAM

This topic describes parameters that are related to PW OAM.

Navigation Path
2. Click the PW OAM Parameter tab.


PW that carries the
service.
PW Type - - Displays the type of the

PW that carries the
service.
OAM Status Enabled Disabled l Specifies or displays

Disabled whether the local node
can perform and
respond to OAM
operations.
l If OAM Status is
Enabled, the local NE
can perform and
respond to OAM
operations.
l If OAM Status is
Disabled, the local
NE cannot perform
and respond to OAM
operations.
l If PW APS protection
needs to be configured
or a CC test needs to
be performed for the
tunnel, OAM Status
needs to be set to
Enabled.
Associate with AC - - The OptiX RTN 900 does

Status not support this
parameter.

Detection Mode Adaptive Auto-Sensing l Specifies or displays

Manual the detection mode for
PW OAM packets.
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.


fixed interval.
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 3.3 50 l Displays or specifies

Interval(ms) 10 the OAM detection
period.
20
l If Detection Packet
50 Type is FFD, this
100 parameter can be set;
200 if Detection Packet
Type is CV, the value
500
is always 1000.
3.3 for PW APS
usually. If the packet
transmission delay
time of a PW exceeds
3.3 ms, the
transmission interval
of FFD packets needs
to be a value greater
than the delay time.

SD Threshold (%) 0-100 0 l Specifies or displays

the SD threshold.
When the OAM
higher than the
corresponding alarm
is reported.
is set to 0, SD
not supported.
SF Threshold (%) 0-100 0 l Specifies or displays

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 - - l Specifies or displays

the LSR ID to be
received.
l This parameter is
available only if
OAM Status is
Disabled.
PW ID to be Received - - l Specifies or displays

the PW ID to be
received.
l This parameter is
available only if
OAM Status is
Disabled.
Local PW Status - - Displays whether PWs at

the local end are
available.

Local PW-Defect Type - - Displays the local PW

defect type.
Local PW-Disabled - - Displays the duration

Duration(ms) when the local PW is
unavailable.
Local PW-Defect - - Displays the local PW

Location defect location.
Remote PW Status - - Displays whether PWs at

the remote end are
available.
Remote PW-Defect - - Displays the remote PW

Type defect type.
Remote PW-Disabled - - Displays the duration

Duration(ms) when the remote PW is
unavailable.
Remote PW-Defect - - Displays the remote PW

Location defect location.
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
3. Select the required PW and click OAM Operation > Ping Test.

Packet Count 1 to 4294967295 3 Specifies the number of


value of the PW label
in test request packets.
The value 7 indicates
the highest priority.
recommended.


live (TTL) value of
the PW label in test
request packets.
recommended.
Transmit 1 to 1000 100 l Specifies the interval

Interval(10ms) for transmitting test
request packets.
recommended.

recommended.

value.
recommended.

packets.
Application Control
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.

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
3. Select the required PW, click OAM Operation in the lower right corner, and choose


value of the PW label
in test request packets.
The value 7 indicates
the highest priority.
recommended.

live (TTL) value of
the PW label in test
request packets.
recommended.

recommended.

value.
recommended.

packets.
Application Control
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.

B.8.1.18 Parameter Description: PW Management_MEP Management

This section describes the MEP parameters of MPLS-TP PW OAM.
Navigation Path
Parameters in the Window for Configuring MEP Parameters

PW ID - - Displays the ID of a PW.
PW Type - - Displays the PW service

type.
OAM Status Disabled Disabled Set this parameter to

Enabled Enabled when the
MPLS-TP PW OAM
function needs to be used.
MEG ID Type IP Based IP Based l When all NEs

ICC Based connected to a PW are
Huawei devices that
Customer Based support I-based
MPLS-TP OAM
components, it is
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.
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.

MEG ID - - l You need to set MEG

ID when MEG ID
Type is not IP Based.
l Set MEG ID to the
PW.
l Set MEG ID to
nodes connected to
different PWs.
MEG Level 0 to 7 7 It is recommended that

you set MEG Level to 7.
MEP ID 1 to 8191 - Set MEP ID at the source

end to the same value as
RMEP ID 1 to 8191 - RMEP ID at the sink
end.
Detection Mode Adaptive Adaptive l Manual: tests

Manual whether a PW is
user-defined CCM
transmission interval.
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 7 It is recommended that

you set CC Packet
Priority to 7 to ensure
that CC packets are
forwarded with priority.

CC Packet Interval (ms) 3.3 1000 l If the MPLS-TP OAM

10 CC function is used
for only continuity
100 check, it is
1000 recommended that
you set CC Packet
Interval (ms) to the
default value 1000.
l If the MPLS-TP OAM
CC function is used to
trigger PW APS, it is
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 Set Lock Status to Lock

Lock if a PW needs to be
locked.
NOTE
this operation.
Local Status - - Displays whether a local

PW is available.
Local Defect Type - - Displays the type of a

PW fault at the local end.
Local Disabled - - Displays the duration

Duration (ms) when the local PW is
unavailable.
Local Defect Location - - Displays the position of a

PW fault.
Remote Status - - Displays whether the PW

is available at the
opposite end.
Remote Defect Type - - Displays the type of a

PW fault at the remote
end.

Remote Disabled - - Displays the duration

Duration (ms) when the remote PW is
unavailable.
Remote Defect Location - - Displays the position of a

PW fault.
SD Threshold (%) 0 to 100 0 l Displays or specifies

the SD threshold. An
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 0 l Displays or specifies

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.
LSR ID to be Received - - l For an MS-PW, you

need to manually
PW ID to be Received - - specify the LSR ID
and PW ID for the
sink node of the MS-
PW.
l LSR ID to be
Received and PW ID
to be Received are
available only when
OAM is disabled.

GAL Enable Status Disabled Disabled l Specifies whether

Enabled OAM packets carry
generic associated
channel header labels
(GALs).
l If PWE3 services use
control worlds,
MPLS-TP PW OAM
packets do not
necessarily carry
GALs. Otherwise,
MPLS-TP PW OAM
packets must carry
GALs.
LM Packet Mode Standard Mode Standard Mode It is recommended that

Huawei Mode you set LM Packet
Mode to Standard.
NOTE
this operation.
GAL Mode RFC5586 RFC5586 When this parameter is

Y.1711 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
3. Click the MIP tab.
4. Click New.

Parameters in the Window for Creating an MIP

MS PW – - Specifies the MS-PW on

which an MIP needs to be
created.
MEG ID Type ICC Based ICC Based l It is recommended

Customer Based that you set MEG ID
Type to ICC Based.
with non-Huawei
this parameter to
Customer Based.
MEG ID - - l Set MEG ID to the

PW.
l Set MEG ID to
nodes connected to
different PWs.
MP ID 1 to 8191 - Each MP on a PW must

have a unique MP ID.
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
4. Select one or more PWs and choose OAM Operation > Start LB.
Parameters in the window for setting LB parameters

MEG ID - - Displays the MEG ID and

MEP ID. If the MEG ID
type is in an IP address

Local MEP ID - - format, the MEG ID or

MEP ID is not displayed.
Node Type MEP MEP Specifies whether the

MIP sink end of the tested
tunnel is an MEP or MIP.
Remote MEP/MIP ID - - l Set Remote

or IP Address MEP/MIP ID or IP
Address according to
the termination node
of an LB test.
l If MEG ID Type is
set to IP Based for the
termination node, set
Remote MEP/MIP
ID or IP Address to
the LSR ID of the
termination node.
l If MEG ID Type is
not set to IP Based
for the termination
node, set Remote
MEP/MIP ID or IP
Address to the MP ID
of the termination
node.
Packet Count 1 to 65535 3 l Specifies the number

of packets that can be
transmitted each time.
l It is recommended
that this parameter
Packet Priority 0 to 7 7 l Specifies the packet

priority.
l It is recommended
that this parameter

TTL 1 to 255 355 l If Node Type is MIP,

set TTL to the
number of hops
between the source
MEP and the current
MIP.
l If Node Type is
MEP, set TTL to a
value that is greater
than or equal to the
number of hops
between the current
MEP and the remote
MEP. It is
recommended that
this parameter take its
default value.
Transmit Interval 100ms 100ms l Specifies the packet

1s transmission interval.
10s l It is recommended
that this parameter
Packet length 128 to 1410 128 l Specifies the packet

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
Configuration > APS Protection Management from the Function Tree.
2. Click the Tunnel APS Management tab.


Protection Group ID - - l Displays the

protection group ID.
l The system
automatically assigns
IDs to the protection
groups according to
their creation
sequence.

group type.
Switching Mode Dual-Ended - l Displays or specifies

Single-Ended the switching mode of
a protection group.
l The value Single-
Ended indicates that
only in the direction
where faults occur.
l The value Dual-
services in both
positive and reverse
directions are
switched to their
protection channels
when faults occur.
l It is recommended
that you set this
parameter to Dual-
Ended.

BDI Status Disabled - l Specifies or displays

Enabled whether the protection
switching is triggered
upon receiving BDI
packets.
l This parameter is
available only when
Switching Mode is
set to Single-Ended.
l If BDI Status is set to
Enabled, the egress
node notifies the
ingress node of any
detected faults by
sending BDI packets;
upon receiving BDI
packets, the ingress
node triggers
Transmit and receive - - Displays the protocol

Status of Protocol packet status.
Packet
Revertive Mode Non-Revertive - l Specifies or displays

Revertive whether to switch
services to the original
working tunnel after
the fault is rectified.
indicates to perform
the switching; the
value Non-Revertive
indicates not to
perform the switching.
l It is recommended
that you set this
parameter to
Revertive.

WTR Time(min) 1-12 - l Specifies and displays

the WTR time of the
protection group.
original working
tunnel recovers,
to the original
working tunnel.
l This parameter is
available only when
Revertive Mode is
Revertive.
l It is recommended
that you set this
parameter to 5.
Hold-off Time(100ms) 0-100 - l Specifies the hold-off

time of the protection
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 - - Displays the switching

group.

group.

Unit - - Displays whether a tunnel

is a working or protection
tunnel.
Active Tunnel - - Displays the currently

used tunnel.
Tunnel Status - - Displays the tunnel

status.
Tunnel Type - - Displays the tunnel type.
Tunnel Direction - - Displays the direction of

a tunnel.
Ingress Tunnel - - Displays the ingress

tunnel.
Egress Tunnel - - Displays the egress

tunnel.
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
2. Click the Tunnel APS Management tab.
3. Click New.

Protection Type 1:1 1:1 Specifies the protection

type of the tunnel
protection group.
NOTE
The OptiX RTN 900
supports only the value 1:1.

Switching Mode Single-Ended Dual-Ended l Specifies the

Dual-Ended switching mode to be
adopted when a tunnel
fails.
l The value Single-
only in the direction
where faults occur.
l The value Dual-
to the protection
channel in both
directions when faults
occur.
l The value Dual-
Ended is
recommended.
BDI Status Enabled Disabled l Specifies whether the

Disabled protection switching
is triggered upon
receiving BDI
packets.
l This parameter is
available only when
Switching Mode is
set to Single-Ended.
l If BDI Status is set to
Enabled, the egress
node notifies the
ingress node of any
detected faults by
sending BDI packets;
upon receiving BDI
packets, the ingress
node triggers the
Working Tunnel Type MPLS Tunnel MPLS Tunnel Specifies the type of the
working tunnel.
NOTE
The OptiX RTN 900
MPLS Tunnel.

Working Ingress Tunnel - - l Specifies the working

ID tunnel of the
protection group in
the ingress direction.
for a bidirectional
tunnel, a value is
automatically
assigned to the
parameter Working
Egress Tunnel ID.
Working Ingress Tunnel - - Displays the name of the

Name working tunnel in the
ingress direction.
Working Egress Tunnel - - l Specifies the working

ID tunnel of the
protection group in
the egress direction.
tunnel, if the
parameter Working
Ingress Tunnel ID is
set, a value is
automatically
assigned to the
parameter Working
Egress Tunnel ID.
Working Egress Tunnel - - Displays the name of the

Name working tunnel in the
egress direction.
Protection Tunnel Type - - Displays the type of

protection tunnel, which
is the same as the type of
working tunnel.
Protection Ingress - - l Specifies the working

Tunnel ID tunnel of the
protection group in
the ingress direction.
for a bidirectional
tunnel, a value is
automatically
assigned to the
parameter Protection
Egress Tunnel ID.

Protection Ingress - - Displays the name of the

Tunnel Name protection tunnel in the
ingress direction.
Protection Egress - - l Specifies the

Tunnel ID protection tunnel of
the protection group
in the egress direction.
tunnel, if the
Ingress Tunnel ID is
set, a value is
automatically
assigned to the
Egress Tunnel ID.
Protection Egress - - Displays the name of the

Tunnel Name protection tunnel in the
egress direction.
Revertive Mode Non-Revertive Non-Revertive l This parameter

to the original
working tunnel after it
recovers.
indicates to switch
services back to the
original working
tunnel after it
recovers; the value
Non-Revertive
indicates not to switch
services back to the
original working
tunnel after it
recovers.
is recommended.

WTR Time(min) 1 to 12 5 l Specifies the WTR

group.
original working
tunnel recovers,
to the original
working tunnel.
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.
Hold-off Time(100ms) 0 to 100 0 l Specifies the hold-off

group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.
Protocol Status Disabled Disabled l Specifies the protocol

Enabled status.
Protocol Status to
Disabled. After the
ends, set Protocol
Status to Enabled.

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:
CES Service Management from the Function Tree.
3. Click the PW APS tab.
4. Click New.
The navigation path for E-Line services is as follows:
4. Click New.
The navigation path for ATM services is as follows:
ATM Service Management from the Function Tree.
4. Click New.



manually assigned.

a PW.


PW.

label.

label.

select tunnels.

PW.
Ingress Tunnel - - A tunnel needs to be

PW will fail.

be automatically
assigned.

the reverse tunnel
automatically.
QoS Parameters


not support this
parameter.


Bandwidth Limit Disabled - Specifies whether the

Enabled bandwidth limit function
is enabled.
or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.

not support this
parameter.
CIR(kbit/s) - - Specifies the committed

a PW.
CBS(byte) - - Specifies the committed

PIR(kbit/s) - - Specifies the peak

a PW.
PBS(byte) - - Specifies the peak burst

size (PBS) of a PW.

not support this
parameter.

NOTE
The OptiX RTN 900
supports only Pipe.



is enabled.
or more PWs in an
MPLS tunnel.
l An ATM PWE3
the bandwidth of
ATM PWE3 services
in an MPLS tunnel.

a PW.


a PW.

size (PBS) of a PW.

not support this
parameter.

not support this
parameter.



CES service packets


packets.
Ingress Clock Mode - - The OptiX RTN 900 does

not support this
parameter.
Egress Clock Mode - - The OptiX RTN 900 does

not support this
parameter.
Control Channel Type - - Displays the mode of PW

continuity check.

Mode verification mode. The
VCCV verification is
used for PW continuity
check.


CES services. The
this threshold.

packets. The
this threshold.


Mode number mode.


transfer packet
PWE3 services, this
used.

channel type.

Mode mode.

Ethernet Tag, this

not support VLAN TPID
of the PW level.


transfer packet
information.

channel type.

Mode mode.


cells.



type.

group ID.

protection group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

mode.
NOTE
protection mode.

working PW.

protection PW.

PW fails.
NOTE


to the original
working PW after it
recovers.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.


group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.

mode of the PW APS
protection group.
OAM Parameters

status of PW OAM.


Manual mode of OAM
packets.
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
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.

configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

be received.

received.

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
3. Click the PW FPS tab.
4. Click New.



manually assigned.

a PW.

PW.

label.

label.
Tunnel Selection Mode - - Displays the method to

select tunnels.

PW.

PW will fail.


be automatically
assigned.

the reverse tunnel
automatically.
QoS Parameters

is enabled.
or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.

not support this
parameter.

a PW.



a PW.

size (PBS) of a PW.

not support this
parameter.

NOTE
The OptiX RTN 900
supports only Pipe.


transfer packet
PWE3 services, this
used.

channel type.

Mode mode.

Ethernet Tag, this

of the PW level.



type.

group ID.
Enabling Status Disabled Disabled Specifies the enabling

protection group.

mode.

working PW.

protection PW.

PW fails.

to the original
working PW after it
recovers.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.


group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.

group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.

mode of the PW APS
protection group.
MPLS-TP OAM Parameters


status of PW OAM.

Detection Mode Adaptive Adaptive l Specifies the detection

Manual mode of OAM
packets.
l Manual: The CC
the user.
l Adaptive: The CC
interval of receiving
PW OAM packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Adaptive is
recommended.
CC Packet Detection 3.33ms 1s l Specifies the period of

Interval(ms) 10ms detection packets.
100ms l This parameter is
configurable when
1s Detection Packet
10s Type is FFD and
1min assumes the fixed
value of 1000 when
10min
Detection Packet
Type is CV.
3.3 for PW APS.

be received.

received.
GAL Enable Status Enabled Enabled Set the GAL enable

Disabled status.

status of PW OAM.


Manual mode of OAM
packets.
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
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.

configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

be received.

received.

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:
3. Click the Slave Protection Pair tab.
4. Click New.
The navigation path for E-Line services is as follows:
4. Click New.
The navigation path for ATM services is as follows:
4. Click New.



manually assigned.


a PW.

PW.

label.

label.

select tunnels.

PW.

PW will fail.

be automatically
assigned.

the reverse tunnel
automatically.
QoS Parameters


not support this
parameter.



is enabled.
or more PWs in an
MPLS tunnel.
l An ETH PWE3
PWE3 services in an
MPLS tunnel.

not support this
parameter.

a PW.


a PW.

size (PBS) of a PW.

not support this
parameter.

NOTE
The OptiX RTN 900
supports only Pipe.



is enabled.
or more PWs in an
MPLS tunnel.
l An ATM PWE3
the bandwidth of
ATM PWE3 services
in an MPLS tunnel.

a PW.


a PW.

size (PBS) of a PW.

not support this
parameter.

not support this
parameter.



CES service packets


packets.

not support this
parameter.

not support this
parameter.

continuity check.

used for PW continuity
check.


CES services. The
this threshold.

packets. The
this threshold.


Mode number mode.


transfer packet
PWE3 services, this
used.

channel type.

Mode mode.

Ethernet Tag, this

of the PW level.


transfer packet
information.

channel type.

Mode mode.


cells.



mode.

PW APS protection
group triggers the
PW APS protection

protection pair.

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.

NE Name - - This parameter displays

the NE name.

T-PID (PW S-TAG) 8100 88A8 This parameter specifies

88A8 the value of TPIDs in S-
TAGs carried in QinQ-
9100 based VPLS service
packets.
VUNI Number 1 to 1024 32 This parameter specifies

the maximum number of
VUNIs that one virtual
switch instance (VSI)
supports.
OptiX RTN 950 using
CSHU/CSHUA and
OptiX RTN 950A/905 do
not support this
parameter.
VLAN Number - - This parameter displays

the relationship between
the number of VUNIs and
the number of VLAN IDs
that one VUNI supports.
For details, see VPLS.
OptiX RTN 950 using
CSHU/CSHUA and
OptiX RTN 950A/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


Service ID - - Displays the ID of the

CES service to be
created.
Service name - - Displays or specifies the

service name.
Level - - Displays the level of the

received TDM frames.
Service Type Common Common l When this parameter

SOH only is set to common,
CES services are used
to transmit common
CES packets.
is set to SOH only,
CES services are used
to transparently
transmit only segment
overhead bytes.
SOH Byte D1-D12, E1-E2, F1, K1- - l Specifies the segment

K2 and X1-X4 overhead bytes
transparently
transmitted by CES
services. This
parameter can be set
manually.
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 - - Displays the source lower

order path.

Source 64K Timeslot - - Displays the source 64

kbit/s timeslot.
Priority List CS7 - l Specifies the priority

CS6 of a CES service. This
parameter is available
EF only when Mode is
AF4 set to UNI-NNI.
AF3 l This parameter needs
AF2 to be configured if
QoS processing needs
AF1
to be performed for
BE 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 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 that carries the CES
service. This parameter is
meaningful when the
CES service type is UNI-
NNI.

Tunnel - - Displays the tunnel that

carries the PW. The
tunnel must have been
configured in advance.
This parameter is
meaningful when the
CES service type is UNI-
NNI.
Sink Board - - Displays the sink board

of the CES service. This
parameter is meaningful
when the CES service
type is UNI-UNI.
Sink High Channel - - l Specifies the sink

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

status of the CES service.


PW that carries the CES
service.

Working Status - - Displays working status

of the PW.
PW Status - - Displays the enabling

status of the PW.
PW Signaling Type - - Displays the PW

signaling type.
NOTE
The OptiX RTN 900
supports static PWs only.
PW Type - - Displays the PW type for

CES service
encapsulation.
CESoPSN: Indicates
structure-aware TDM
circuit emulation service
over packet switched
network. Timeslot
compression can be set.
SAToP: Indicates
structure-agnostic TDM
over packet. Timeslot
compression cannot be
set.
PW Encapsulation Type - - Displays the tunnel type

for PW encapsulation.
NOTE
The OptiX RTN 900
supports MPLS only.
PW Incoming Label - - Displays the Ingress label

of the PW that carries the
CES service.
PW Outgoing Label - - Displays the Egress label

of the PW that carries the
CES service.
Peer LSR ID - - Displays the LSR ID of

Local Working Status - - Displays the working

local end.
Remote Working Status - - Displays the working

remote end.

Compositive Working - - Displays the compositive

Status working status of the PW.
The compositive working
status is up when both
ends are up, and is down
when one end is down.
Tunnel type - - Displays the type of the

PW.
NOTE
The OptiX RTN 900
supports MPLS tunnels
only.
Tunnel - - Displays the ID of the

CES service.

status of the tunnel.
Tunnel Automatic - - The OptiX RTN 900 does

Selection Policy not support this
parameter.
QoS Parameters

a PW.
CIR(kbit/s) - - The OptiX RTN 900 does

not support this
parameter.

not support this
parameter.


RTP Header - - Displays the RTP header.

The RTP header carries
time stamps.
Jitter Compensation - - Displays or specifies the

Buffering Time(us) jitter buffer time.


not support this
parameter.

not support this
parameter.

continuity check (CC).

used for PW CC.
Enable CES Service Enabled - Displays or specifies the

Alarm Transparent Disabled enabling status of the
Transmission transparent transmission
of CES service alarms. If
this function is enabled,
the fault on the AC side
of the CES service is
notified to the remote
end. Upon receiving the
fault notification from the
network side or the
remote end, the local NE
inserts the corresponding
alarm to the AC side.
Threshold of Entering 1-65535 - Displays or specifies the

R Bit Inserting Status 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.

Threshold of Exiting R 1-65535 - Displays or specifies the

Bit Inserting Status 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 Huawei Mode - Specifies the sequence

Mode Standard Mode number mode. The
Sequence Number
Mode must be set to the
same value at both ends
of a radio link.

NOTE

created.

working PW.

protection PW.

mode.


the PW protection
group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.

original working PW
after the fault is
rectified.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.


protection group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.

0, the protection
switching once it
detects faults, but
otherwise, no

group.

group.





NOTE

PW APS protection
group triggers the
PW APS protection

protection pair.


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
2. Click New.

Service ID (e.g.1,3-6) 1 to 4294967295 - Specifies the

service ID.
Service name - - Specifies the

service name.

Level E1 E1 The value E1

indicates that the
CES service is
used to transmit
the TDM services
from E1 ports.
Service Type Common Common l When this

SOH only parameter is
set to
common, CES
services are
used to
transmit
common CES
packets.
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 l Specifies the

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

SOH Byte D1-D12, E1-E2, - l Specifies the

F1, K1-K2 and segment
X1-X4 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) - - If Level is set to

E1, this
parameter
indicates the E1
port where the
service source is
located. If Mode
is set to UNI-
NNI, this
parameter can
assume only one
value.

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 UNI-
NNI and PW
Type is
SAToP.

Priority List CS7 EF l Specifies the

CS6 priority of a
CES service.
EF This
AF4 parameter is
AF3 available only
when Mode is
AF2
set to UNI-
AF1 NNI.
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

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 l Specifies the

SAToP type of the
PW. This
parameter is
available only
when Mode is
UNI-NNI.
l CESoPSN:
Indicates
structure-
aware TDM
circuit
emulation
service over
packet
switched
network.
Timeslot
compression
can be set.
SAToP:
Indicates
structure-
agnostic TDM
over packet.
Timeslot
compression
cannot be set.

Protection Type No Protection No Protection l Specifies the

PW APS protection
mode of the
Slave Protection PW. This
Pair parameter is
available only
when Mode is
UNI-NNI.
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.

Sink Board - - l Specifies the

board where
the sink of the
CES service is
located.
l This
parameter is
available only
when Mode is
set to UNI-
UNI.
Sink High Channel - - l Specifies the

source 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 UNI-
UNI.

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

NOTE
If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters of
working and protection PWs need to be configured. This section considers the parameters of the working PW
as an example.


manually assigned.

the PW.

PW.

label.


label.

select tunnels.

PW.

PW will fail.

be automatically
assigned.

the reverse tunnel
automatically.
QoS Parameters

Parameters for the Advanced Attributes of PWs

RTP Header Disable Disable l Specifies the RTP

Enable Huawei RTP header.
l The RTP header
carries time stamps.
recommended.

Jitter Compensation 375 to 16000 8000 l Specifies the jitter

Buffering Time (us) NOTE buffer time for the
l The minimum value for
received CES packets.
CES services on Smart The step is 125.
E1 boards is 375. l The larger the jitter
l The minimum value for compensation
CES services on buffering time, the
channelized STM-1 larger jitter CES
boards is 875.
services can bear, and
the larger the network
latency.
l The jitter
compensation
buffering time should
be larger or equal to
(3 * packet loading
time + 2 * end-to-end
network jitter time).
recommended.
Packet Loading Time 125 to 5000 1000 l Specifies the length of

(us) fragments in the TDM
data stream. The step
is 125.
l A larger value of this
parameter means
higher encapsulation
efficiency but larger
delays of CES
services.
recommended.
Ingress Clock Mode Null Null The RTN 900 does not
Adaptive Clock Mode support this parameter.
Egress Clock Mode - - The RTN 900 does not


Control Channel Type None CW l Specifies the mode of

CW PW continuity check
(CC).
Alert Label
l The value None
indicates that the
control word is not
PW CC is not
supported.
VCCV packets in
Alert Label
encapsulation mode.
l The value CW
indicates that the
control word is
supported.
VCCV Verification None Ping l Specifies the VCCV

Mode Ping verification mode.
The VCCV
PW CC.
this parameter to
None.
Enable CES Service Disabled Disabled If this function is

Alarm Transparent Enabled enabled, the fault on the
Transmission AC side of the CES
service is notified to the
remote end. Upon
receiving the fault
notification from the
network side or the
remote end, the local NE
inserts the corresponding
alarm to the AC side.

Threshold of Entering 1-65535 100 l The corresponding

R Bit Inserting Status alarm will be reported
if the number of
consecutive lost
packets crosses the
threshold specified by
this parameter.
l This function is
available only when
the transparent
transmission of CES
service alarms is
enabled.
Threshold of Exiting R 1-65535 5 l The corresponding

Bit Inserting Status alarm will be cleared
if the number of
consecutive received
packets crosses the
threshold specified by
this parameter.
l This function is
available only when
the transparent
transmission of CES
service alarms is
enabled.
Sequence Number Huawei Mode Standard Mode Specifies the sequence

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.

type.

group ID.


protection group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

mode.
NOTE
protection mode.

working PW.

protection PW.

PW fails.
NOTE

to the original
working PW after it
recovers.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.


group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.

group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.

mode of the PW APS
protection group.
OAM Parameters
NOTE


status of PW OAM.

Manual mode of OAM
packets.
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
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.

configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

be received.

received.


NOTE

mode.

PW APS protection
group triggers the
PW APS protection

protection pair.

B.8.4 ATM Parameters

This topic describes the parameters that are related to ATM services.
NOTE
OptiX RTN 905/905e does not support the 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
2. Click the IMA Group Management tab.

VCTRUNK - - Displays the ATM

TRUNK.

IMA Protocol Status Enabled Disabled l Specifies the IMA

Disabled protocol enable status.
l Set IMA Protocol
Enable Status to
Enabled if the links
bound in the ATM
TRUNK require the
IMA protocol;
otherwise, set this
parameter to
Disabled.
l After IMA Protocol
Enable Status is set
to Enabled, the E1
links or Fractional E1
timeslots bound in the
ATM TRUNK start
running the IMA
protocol.
Minimum Number of 1 to 16 1 l The links of the IMA

Active Transmitting group can carry
Links services only when
the number of
activated links in the
transmit/receive
direction is not
smaller than the value
of Minimum
Number of Active
Transmitting Links/
Minimum Number
of Active Receiving
Links.
l The values of
Minimum Number
of Active
Transmitting Links
and Minimum
Number of Active
Receiving Links must
be the same because
the OptiX RTN 950
supports Symmetrical
Mode and
Symmetrical
Operation only. The
parameters Minimum
Number of Active

Minimum Number of 1 to 16 1 Transmitting Links

Active Receiving Links and Minimum
Number of Active
Receiving Links must
assume the same
value on the two ends
of an IMA link.
recommended.
IMA Protocol Version 1.0 1.1 l Specifies the IMA

1.1 protocol version.
l The parameter IMA
Protocol Version
must assume the same
of an IMA link.
recommended.
IMA Transmit Frame 32 128 l Specifies the IMA

Length 64 transmit frame length.
128 l Based on the IMA
frame format, the
256 receive end rebuilds
the ATM cell stream
with the cells arriving
from diversely-
delayed links. Longer
IMA frames result in
higher transmission
efficiency and occupy
more resources. Once
a member link fails,
the impact on the
entire IMA group
increases as the length
of IMA frames
increases.
l The IMA Transmit
Frame Length must
assume the same
of an IMA link.
recommended.

IMA Symmetry Mode Symmetrical Mode and Symmetrical Mode and l Specifies the
Symmetrical Operation Symmetrical Operation symmetrical mode of
the IMA group.
l If the symmetrical
mode and
symmetrical operation
is adopted, the
bandwidth of the IMA
group is always
consistent in the
transmit direction and
in the receive
direction, even when
some member links
fail. In symmetrical
mode:
– Bandwidth of the
IMA group = min
{bandwidth in the
transmit direction,
bandwidth in the
receive direction}
– The unidirectional
failure in one
member link is
equivalent to the
bidirectional
failure in one
member link.

Maximum Delay 1 to 120 25 l Specifies the

Between Links (ms) maximum differential
delay that is allowed
between the member
links.
l If the differential
delay between a
member link and the
other member links
exceeds the value, this
link will be
deactivated and
deleted from the IMA
group.
to a value higher than
the normal value
range, the delay of
IMA services will be
prolonged and even
packet loss will occur;
if this parameter is set
to a value lower than
the normal value
range, a working link
will be deleted by
mistake.
l The Maximum Delay
Between Links (ms)
must assume the same
of an IMA link.
recommended.
Clock Mode CTC Mode CTC Mode l Specifies the clock

ITC Mode mode of the IMA
group.
l Clock Mode is set to
the same value for the
interconnected ends of
IMA links.
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.

Navigation Path
2. Click the Binding tab.

Available Boards - - Selects the available

boards.
Configurable Ports - - Selects the

configurable ATM
trunks.
Level E1 E1 Specifies the level of

Fractional E1 bound paths.
l If ATM/IMA
services need to
be mapped into
the ATM
TRUNK that
binds one or
more E1 ports,
select E1 in
Level.
l If ATM/IMA
services need to
be mapped into
the ATM
TRUNK that
binds one or
more serial ports,
select Fractional
E1 in Level.
Direction Bidirectional Bidirectional Displays the

Uplink direction of bound
paths. The fixed
Downlink value is
bidirectional.
Optical Interface - - The OptiX RTN 950

parameter.

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 950

parameter.
Selected Bound Paths - - Displays the bound

paths.
VCTRUNK - - Displays the name of

the ATM TRUNK.

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

Not selected display bound paths
in combination.
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
2. Click the IMA Group States tab.


VCTRUNK - - Displays the VCTRUNK.
Near-End Group Status - - Displays the status of the

near-end group.
Far-End Group Status - - Displays the status of the

far-end group.
Transmit Rate (cell/s) - - Displays the cell

transmission rate.
Receive Rate (cell/s) - - Displays the cell

receiving rate.
Number of Transmit - - Displays the number of

Links transmit links.
Number of Receive - - Displays the number of

Links receive links.
Number of Activated - - Displays the number of

Transmit Links activated transmit links.
Number of Activated - - Displays the number of

Receive Links activated receive links.
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
2. Click the IMA Link States tab.

E1 Link - - Displays E1 links.
Differential Delay - - Displays the status of the

Check Status deferential delay check.
Near-End Receiving - - Displays the near-end

Status receiving status.

Near-End Transmission - - Displays the near-end

Status transmitting status.
Far-End Receiving - - Displays the far-end

Status receiving status.
Far-End Transmitting - - Displays the far-end

Status transmitting status.
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
2. Click the ATM Interface Management tab.

Port - - Displays the port.
Name - - Displays or specifies the

name of port.

Port Type UNI UNI Specifies the type of

NNI ATM port.
l UNI: the port
connecting user-side
devices. For example,
the UNI port applies
to the user-side
interface on the
common ATM
network or to the user-
side interface of the
PE on the PSN
network that transmits
ATM PWE3 services.
l NNI: the port
connecting network-
side devices. For
example, the NNI port
applies to the
network-side interface
on the common ATM
network.
ATM Cell Payload Disabled Enabled Specifies whether to

Scrambling Enabled enable payload
scrambling of ATM cells.
l The ITU-T G.804
stipulates that the
payload (48 bytes) of
ATM cells must be
scrambled before it is
mapped into E1
signals. Therefore, it
is 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 - - The OptiX RTN 900 does

not support this
parameter.

Max. VPI - - The OptiX RTN 900 does

not support this
parameter.
Min. VCI - - The OptiX RTN 900 does

not support this
parameter.
Max. VCI - - The OptiX RTN 900 does

not support this
parameter.
VCC-Supported VPI - - The OptiX RTN 900 does

Count not support this
parameter.
Loopback No Loopback No Loopback Specifies the loopback

Outloop status of the port.
Inloop
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.

Mapping Relation ID - - Specifies the ID of the

mapping table.
Mapping Relation - - Specifies the name of the

Name mapping relationship.
UBR BE UBR: BE Displays or specifies the

AF11 CBR: EF PHB service classes that
CBR correspond to different
AF12 RT-VBR: AF31 ATM service types.
RT-VBR
AF13 NRT-VBR: AF21 l Eight PHB service
NRT-VBR AF21 UBR+: AF11 classes are available:
BE, AF1, AF2, AF3,
UBR+ AF22 PORT-TRANS: BE

PORT-TRANS AF23 AF4, EF, CS6, and

AF31 CS7. The OptiX RTN
AF32 900 provides different
QoS policies for the
AF33 queues of different
AF41 service classes.
AF42 l CS6 to CS7: highest
AF43 service classes,
EF mainly applicable to
signaling
CS6
transmission.
CS7
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
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.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.

Navigation Path
QoS Management > Diffserv domain Management > ATM COS Mapping
2. Click New.

Mapping Relation ID 2 to 8 - Specifies the ID of the

mapping table.
Mapping Relation - - Specifies the name of the

Name mapping relationship.
UBR BE UBR: BE Specifies the PHB service

AF11 CBR: EF classes that correspond to
CBR different ATM service
AF12 RT-VBR: AF31
RT-VBR types.
AF13 NRT-VBR: AF21 l Eight PHB service
NRT-VBR AF21 classes are available:
UBR+: AF11
AF22 BE, AF1, AF2, AF3,
UBR+ PORT-TRANS: BE
AF23 AF4, EF, CS6, and
CS7. The OptiX RTN
AF31
900 provides different
AF32 QoS policies for the
AF33 queues of different
AF41 service classes.
AF42 l CS6 to CS7: highest
AF43 service classes,
mainly applicable to
EF signaling
CS6 transmission.
CS7 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

PORT-TRANS 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
QoS Management > Policy Management > ATM Policy from the Function Tree.
2. Click the ATM Policy tab.

Policy ID - 1 Displays the policy ID of

the ATM service.
Policy Name - - Displays or specifies the

policy name of the ATM
service. The maximum
length of the value is 64
bytes.

Parameters for Configuring ATM Traffic

Service Type UBR UBR Displays or specifies the

CBR type of the ATM service.
RT-VBR l The UBR service is
characterized by non-
NRT-VBR real-time applications
UBR+ 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 rt-
VBR service allows
sources to transmit
data at a rate that
varies with time.

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 rt-
VBR service, the nrt-
VBR service does not
require tightly
constrained delay or
delay variation, and is
intended for non-real-
time 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 - - The Table B-100 lists the

ATM service type, traffic
Clp01Pcr(cell/s) 90 to 74539 - type descriptor, and the
Clp01Scr(cell/s) 90 to 74539 - related traffic parameters.
ATM policies are
Clp0Pcr(cell/s) 90 to 74539 - configured based on these
mapping relationships.
Clp0Scr(cell/s) 90 to 74539 -
Max. Cell Burst Size 2 to 200000 -

(cell)
Cell Delay Variation 7 to 13300000 -

Tolerance (0.1us)

Discard Traffic Frame Enabled Disabled Displays or specifies the

Disabled frame discarding mark in
ATM policies. This
parameter is effective to
AAL5 traffic.
UPC/NPC Enabled Disabled Displays or specifies

Disabled UPC/NPC.
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 ATM Traffic Type Traffic Traffic Traffic Traffic
Service Descriptor Parameter 1 Parameter 2 Parameter 3 Parameter 4
Type
UBR NoTrafficDescriptor - - - -
NoClpTaggingNoScr Clp01Pcr CDVT - -
NoClpNoScr Clp01Pcr - - -
NoClpNoScrCdvt Clp01Pcr CDVT - -
CBR ClpTransparentNoScr Clp01Pcr CDVT - -
ClpNoTaggingNoScr Clp01Pcr Clp0Pcr - -
ClpTaggingNoScr Clp01Pcr Clp0Pcr - -
nrtVBR NoClpScr Clp01Pcr Clp01Scr MBS -
ClpNoTaggingScr Clp01Pcr Clp0Scr MBS -
ClpTaggingScr Clp01Pcr Clp0Scr MBS -
rtVBR ClpTransparentScr Clp01Pcr Clp01Scr MBS CDVT
NoClpScrCdvt Clp01Pcr Clp01Scr MBS CDVT


Type
ClpNoTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
ClpTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
UBR+ atmnotrafficdescriptormcr Clp01Mcr - - -
atmnoclpmcr Clp01Pcr Clp01Mcr - -
atmnoclpmcrcdvt Clp01Pcr Clp01Mcr CDVT -
Parameters for the application object

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.

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
QoS Management > Policy Management > ATM Policy from the Function Tree.
2. Click New.

Policy ID - 1 Specifies the policy ID of

the ATM service. The
policy ID can also be
automatically allocated.

Policy Name Synchronous signal Synchronous signal Specifies the policy name
Signaling of the ATM service. The
maximum length of the
Voice value is 64 bytes.
Data NOTE
Video You can select one of the
five ATM service policy
names from the drop-down
list or enter the policy
name.

Service Type UBR UBR Specifies the type of the

CBR ATM service.
RT-VBR l The UBR service is
characterized by non-
NRT-VBR real-time applications
UBR+ 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 rt-
VBR service allows
sources to transmit
data at a rate that
varies with time.
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 rt-
VBR service, the nrt-
VBR service does not
require tightly
constrained delay or
delay variation, and is
intended for non-real-
time 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 - - For the mapping

relationships between
Clp01Pcr(cell/s) 90 to 74539 - ATM service types, ATM
Clp01Scr(cell/s) 90 to 74539 - traffic type descriptors,
and traffic parameters,
Clp0Pcr(cell/s) 90 to 74539 - see Table B-101. ATM
policies are configured
Clp0Scr(cell/s) 90 to 74539 - based on these mapping
relationships.
Max. Cell Burst Size 2 to 200000 -
(cell)
Cell Delay Variation 7 to 13300000 -

Tolerance (0.1us)

Discard Traffic Frame Enabled Disabled Specifies the frame

Disabled discarding mark in ATM
policies. This parameter
is effective to AAL5
traffic.
UPC/NPC Enabled Disabled l UPC is user-side

Disabled 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-101 Mapping relationship between ATM service types, ATM traffic types, and traffic parameters
Type
UBR NoTrafficDescriptor - - - -
NoClpTaggingNoScr Clp01Pcr CDVT - -
CBR ClpTransparentNoScr Clp01Pcr CDVT - -
ClpNoTaggingNoScr Clp01Pcr Clp0Pcr - -
ClpTaggingNoScr Clp01Pcr Clp0Pcr - -
nrtVBR NoClpScr Clp01Pcr Clp01Scr MBS -
ClpNoTaggingScr Clp01Pcr Clp0Scr MBS -
ClpTaggingScr Clp01Pcr Clp0Scr MBS -
rtVBR ClpTransparentScr Clp01Pcr Clp01Scr MBS CDVT
NoClpScrCdvt Clp01Pcr Clp01Scr MBS CDVT
ClpNoTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT


Type
ClpTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
UBR+ 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

Service ID - - Displays the service ID.
Service Name - - Displays or specifies the

service name.
Service Type - - Displays the ATM service

type.

status of the ATM
service.
Connection Parameters
Connection ID - - Displays the connection

ID of the ATM service.
Connection Name - - Displays or specifies the

connection name of the
ATM service.
Source Port - - Displays the source port

of the ATM service.


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

source port of the ATM
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

Port - - Displays the port of the

ATM IMA service.
Port Type - - Displays the port type of

the ATM IMA service.
Max. VPI - - Displays the maximum

VPI.
Max. VCI - - Displays the maximum

VCI.
VCC-Supported VPI - - Displays the count of

Count VPIs that are used for VC
exchange.

Parameters for Bound Paths


bound paths.

bound paths. The fixed
value is bidirectional.
Bound Paths - - Displays the bound paths.
Number of Bound Paths - - Displays the number of

bound paths.
IMA Group Status - - Displays the status of the

IMA group.
Parameters of PWs
Tab Parameter Value Range Default Value Description
General PW ID - - Displays the PW ID.

Attributes
Working Status - - Displays the working
status of a PW.
- - Displays whether a PW
is enabled.
PW Signaling Type - - Displays the 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 - - Displays the direction

of the PW.

PW Encapsulation - - Displays the

Type encapsulation type of
NOTE
The OptiX RTN 900
uses MPLS only.
PW Incoming - - Displays the

Label configured PW Ingress
label.
PW Outgoing - - Displays the

Label configured PW Egress
label.
Peer LSR ID - - Displays the LSR ID of

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 - - Displays the local

Status running status of PW.
Remote Operating - - Displays the remote

Status running status of PW.
Overall Operating - - Displays the

Status comprehensive
working status of the
PW.
Tunnel for Auto - - Displays the tunnel

Selection that is automatically
selected.
QoS PW ID - - Displays the PW ID.
Direction - - Displays the direction

of the PW.

Bandwidth Limit - - Displays or specifies

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) - - Displays or specifies

the committed
information rate.
to the same value as
PIR.
CBS (kbyte) - - Displays or specifies

the excess burst size of
the PW.
PIR (kbit/s) - - Displays or specifies

the peak information
rate.
to the same value as
CIR.
PBS (kbyte) - - Displays or specifies

the maximum excess
burst size of the PW.
EXP - - The OptiX RTN 900

parameter.

Policy - - The OptiX RTN 900

parameter.
Advanced Control Word Must Use - Displays or specifies

Attributes No Use whether to use the
control word. In the
MPLS packet
switching network, the
transmit packet
information.
Control Channel CW - l Displays or

Type None specifies the mode
of PW connectivity
Alert Label check.
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 Ping - l Displays or

Mode None 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.

Max. Concatenated 1 to 31 - l Displays or

Cell Count 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 100 to 50000 - l Displays or

Time (us) 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


PW that carries the
service.

CoS Mapping - - Specifies the policy for

mapping different ATM
service levels to CoS
priorities. By setting this
parameter, different
quality measures are
provided for different
ATM services.

NOTE

created.

working PW.

protection PW.

mode.

the PW protection
group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.


original working PW
after the fault is
rectified.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.

protection group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.

0, the protection
switching once it
detects faults, but
otherwise, no


group.

group.




NOTE

PW APS protection
group triggers the
PW APS protection

protection pair.


status of the slave
protection pair.

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
2. Click New.

Service ID 1 to 4294967295 - Specifies the service ID.
Service Name - - Specifies the service

name.
Service Type UNIs-NNI UNIs-NNI l Specifies the type of

UNI-UNI the ATM service.
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.

Connection Type PVC PVC Specifies the connection

PVP type of the ATM service.
Transparent For common ATM
services (UNI-UNI):
l PVP: Only the VPIs
of the source and sink
are exchanged.
l PVC: The VPIs and
VCIs of the source
and sink are
exchanged.
For ATM PWE3 services
(UNIs-NNI):
l PVP: This value
applies to the N-
to-1/1-to-1 VPC
encapsulation mode.
l PVC: This value
applies to the N-
to-1/1-to-1 VCC
encapsulation mode.
For transparently
transmitted ATM
services, set Connection
Type to Transparent.
Protection Type No Protection No Protection l Specifies the

PW APS protection mode of the
PW. This parameter is
Slave Protection Pair available only when
Service Type is
UNIs-NNI.
according to the
network plan.
Connection Parameters
Connection Name - - Specifies the name of the

ATM connection.
Source Board - - Specifies the source

board of the ATM
service.

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

NNI: 0 to 4095 source port of the ATM
service.
Source VCI(eg. 32 to 65535 - Specifies the VCI of the

35,36-39) source port of the ATM
service.
PW ID 1 to 4294967295 - Specifies the ID of the

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

NNI: 0 to 4095 sink port of the ATM
service.
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.


Working Status - - Displays the working

status of the PW.
NOTE
This parameter is available
only after the PW
parameters are configured.
PW Status - - Displays the enabling

status of the PW.
NOTE
This parameter is available
only after the PW
parameters are configured.

need to be manually
assigned.
PW Type The ATM connection The ATM connection l Specifies the type of
type is PVC: type is PVC: the PW.
l ATM n-to-one VCC ATM n-to-one VCC cell l In the case of ATM
cell transport transport 1_to_1 encapsulation,
l ATM one-to-one VCC The ATM connection one PW carries one
Cell Mode type is PVP: VPC or VCC.
The ATM connection ATM n-to-one VPC cell l In the case of ATM
type is PVP: transport n_to_1 encapsulation,
one PW carries one or
l ATM n-to-one VPC more VPCs or VCCs.
cell transport
l ATM one-to-one VPC
Cell Mode
PW Direction Bidirectional Bidirectional Displays the direction of

the PW.

packets on the PW.

label.

label.
Tunnel Selection Mode Manually Manually Displays the method to

select tunnels.


PW.

PW will fail.

be automatically
assigned.
QoS Parameters


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.

not support this
parameter.

CIR (Kbit/s) - - Specifies the committed

the PW.
CBS (kbyte) - - Specifies the excess burst

size of the PW.

the PW.
PBS (kbyte) - - Specifies the maximum

excess burst size of the
PW.

not support this
parameter.
Parameters of Advanced Attributes

Control Word Must Use Must Use l Specifies whether to

No Use use the control word.
In the MPLS packet
switching network,
the control word is
used to transmit
packet information.
l Set Control Word to
Must Use if PW Type
is ATM 1:1.

Control Channel Type CW CW l Specifies the mode of

None PW connectivity
check.
Alert Label
l The value None
indicates that the
control word is not
PW connectivity
check is not
supported.
l The value CW
indicates that the
control word is
supported.
l The value Alert
Label indicates
VCCV packets in
Alert Label
encapsulation mode.

The VCCV
PW connectivity
check.
this parameter to
None.
Max. Concatenated Cell 1 to 31 10 l Specifies the

Count maximum number of
concatenated cells.
l If the value 1 is
assumed, only one
ATM cell is
encapsulated in one
from 2 to 31 is
assumed, a maximum
of 2 to 31 ATM cells
are encapsulated into
one packet.

Packet Loading Time 100 to 50000 1000 l Specifies the packet

(us) loading time. Once
the packet loading
time expires, the
packet is sent out even
if the concatenated
cells are less than the
maximum.
l If Max.
Concatenated Cell
Count assumes the
value 1, this
parameter is
the packet will be sent
out once the cell is
loaded.

NOTE
to PW APS.

type.

group ID.

protection group.
Enabling Status to
Disabled. After the
ends, set Enabling
Status to Enabled.

mode.
NOTE
protection mode.


working PW.

protection PW.

PW fails.
NOTE

to the original
working PW after it
recovers.
are switched to the
original working PW
and the value Non-
revertive indicates
switched to the
is recommended.

group.
original working PW
switched to the
l This parameter is
available only when
Revertive Mode is
Revertive.
recommended.


group.
0, the protection
switching once it
detects faults, but
otherwise, no
recommended.

mode of the PW APS
protection group.
OAM Parameters
NOTE

status of PW OAM.


Manual mode of OAM
packets.
l Manual: The CC
the user.
l Auto-Sensing: The
the interval of
receiving PW OAM
packets.
set to Manual, you
need to set the PW
OAM detection
and transmitted.
l The value Auto-
Sensing is
recommended.


fixed interval.
the user.
this parameter
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.

configurable when
50 Detection Packet
100 Type is FFD and
value of 1000 when
500
Detection Packet
Type is CV.
3.3 for PW APS.

be received.

received.


NOTE

mode.

slave protec

RTN 900 V100R009C10 Feature Configuration Guide 02

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RTN 900 V100R009C10 Feature Configuration Guide 02

Uploaded by

Copyright:

Available Formats

OptiX RTN 900 Radio Transmission System

Feature Configuration Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2017-12-25) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 900 V100R009C10

iManager U2000 V200R016C60

The intended audiences of this document are:

Indicates an imminently hazardous situation

Issue 02 (2017-12-25) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Calls attention to important information,

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Updates in Issue 02 (2017-12-25) Based on Product Version

Issue 02 (2017-12-25) Huawei Proprietary and Confidential iii

- Fixed the known bugs.

Updates in Issue 01 (2017-05-20) Based on Product Version

Issue 02 (2017-12-25) Huawei Proprietary and Confidential iv

About This Document.....................................................................................................................ii

Issue 02 (2017-12-25) Huawei Proprietary and Confidential v

1.17.1 Networking Diagram............................................................................................................................................... 68

2 Configuring Microwave Features.............................................................................................87

Issue 02 (2017-12-25) Huawei Proprietary and Confidential vi

2.14 Configuration Example (PLA on an NE)................................................................................................................. 127

3 Configuring SDH Protection Features.................................................................................. 138

4 Configuring Native Ethernet Features.................................................................................. 149

Issue 02 (2017-12-25) Huawei Proprietary and Confidential vii

4.14.2 Configuration Procedure........................................................................................................................................183

5 Ethernet Features on the EoS/EoPDH Boards...................................................................... 224

Issue 02 (2017-12-25) Huawei Proprietary and Confidential viii

5.11.2 Configuration Process............................................................................................................................................247

6 Configuring MPLS/PWE3 Features........................................................................................281

Issue 02 (2017-12-25) Huawei Proprietary and Confidential ix

6.11 Configuration Procedure (ML-PPP)......................................................................................................................... 305

7 Configuring Clock Features.................................................................................................... 345

Issue 02 (2017-12-25) Huawei Proprietary and Confidential x

7.5 Configuration Example (Network-wide Time Synchronization ).............................................................................. 356

8 Configuring Maintenance Features....................................................................................... 383

A Task Collection......................................................................................................................... 393

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xi

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xii

A.3.7.13 Configuring the Network Information of an ABR............................................................................................ 449

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xiii

A.5 Managing Radio Links.............................................................................................................................................. 483

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xiv

A.8.2 Setting Working Modes of E1 Ports....................................................................................................................... 530

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xv

A.9.1.1 Creating Ethernet Ring Protection Instances....................................................................................................... 563

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xvi

A.9.6 Managing the MSTP............................................................................................................................................... 611

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xvii

A.9.9.4 Creating Remote MEPs in an MA....................................................................................................................... 649

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xviii

A.10.4.1 Creating a Static MAC Address Entry...............................................................................................................693

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xix

A.10.11 Configuring LPT.................................................................................................................................................726

Issue 02 (2017-12-25) Huawei Proprietary and Confidential xx

A.11.4.3 Setting PW OAM (Y.1711) Parameters............................................................................................................. 760