RTN 900 V100R020C00 Feature Configuration Guide 02

OptiX RTN 900 Radio Transmission System
V100R020C00
Feature Configuration Guide
Issue 02
Date 2020-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. 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: https://www.huawei.com
Email: support@huawei.com
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. i

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 V100R020C00
NCE V100R019C00
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:
● Installation and commissioning engineer

● Data configuration engineer
● System maintenance engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. ii

Symbol Description
Indicates a hazard with a medium level of risk which, if

not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not

avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation 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.
Supplements the important information in the main text.

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 (2020-09-30) Based on Product Version V100R020C00

This issue is the second official issue for the V100R020C00 product version.
The document updates are as follows:
Change Description
- Fixed the known bugs.
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. iii

Change Description
Security Management Deleted the description of the USB

flash drive.
Updates in Issue 01 (2020-06-30) Based on Product Version V100R020C00

This issue is the first official issue for the V100R020C00 product version.
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. 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)...................................................... 11
1.4 Configuration Procedure (DCC Transmission Through the External Clock Port Solution).......................... 12
1.5 Configuration Process (L2 DCN Solution).................................................................................................................... 13
1.6 Configuration Process (SNMP).........................................................................................................................................19
1.7 Configuration Procedure (LLDP)..................................................................................................................................... 20
1.8 Configuration Procedure (RADIUS)................................................................................................................................ 21
1.9 Configuration Process (NE Anti-Theft Solution)........................................................................................................ 22
1.10 Configuration Example (HWECC Solution)............................................................................................................... 23
1.10.1 Networking Diagram..................................................................................................................................................... 23
1.10.2 Configuration Procedure...............................................................................................................................................24
1.11 Configuration Example (IP DCN Solution in Single OSPF Area)........................................................................30
1.12 Configuration Example (IP DCN Solution in Multiple OSPF Areas)................................................................. 37
1.13 Configuration Example (IP DCN Solution Using OSPF Multi-process)............................................................ 47
1.14 Configuration Example (DCC Bytes Transparent Transmission Solution)....................................................... 53
1.15 Configuration Example (DCC Transmission Through the External Clock Port Solution)...........................58
1.16 Configuration Example (L2 DCN Solution, with Third-Party DCN Packets Not Identified by VLAN IDs)
............................................................................................................................................................................................................ 61
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. v

1.17 Configuration Example (L2 DCN Solution, with Third-Party DCN Packets Identified by VLAN IDs).... 67
1.18 Configuration Example (SNMP).................................................................................................................................... 74
1.19 Configuration Example (LLDP)...................................................................................................................................... 75
1.20 Configuration Example (RADIUS).................................................................................................................................77
1.21 Configuration Example (NE Anti-Theft Solution)....................................................................................................81
2 Configuring Microwave Features.......................................................................................84

2.1 Configuration Process (1+1 HSB/FD/SD)......................................................................................................................85
2.2 Configuration Procedure (N+1 Protection).................................................................................................................. 88
2.3 Configuration Process (XPIC)............................................................................................................................................ 89
2.4 Configuration Process (AM).............................................................................................................................................. 90
2.5 Configuration Procedure (ATPC)..................................................................................................................................... 91
2.6 Configuration Process (PLA/EPLA/EPLA+/Super EPLA)........................................................................................... 92
2.7 Configuration Example (1+1 HSB/FD/SD on an NE)................................................................................................93
2.7.1 Networking Diagram........................................................................................................................................................93
2.7.2 Configuration Procedure1...............................................................................................................................................93
2.8 Configuration Example (1+1 HSB/FD/SD on Cascaded NEs)................................................................................ 98
2.8.1 Networking Diagram........................................................................................................................................................98
2.8.2 Configuration Procedure................................................................................................................................................. 98
2.9 Configuration Example (XPIC on an NE)................................................................................................................... 102
2.10 Configuration Example (XPIC on Cascaded NEs)..................................................................................................107
2.10.1 Networking Diagram................................................................................................................................................... 107
2.10.2 Configuration Procedure............................................................................................................................................ 108
2.11 Configuration Example (N+1 Protection)................................................................................................................ 110
2.12 Configuration Example (ATPC)................................................................................................................................... 116
2.13 Configuration Example (AM)....................................................................................................................................... 120
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. vi


2.14 Configuration Example (PLA on an NE).................................................................................................................. 125
2.15 Configuration Example (PLA on Cascaded NEs)................................................................................................... 128
2.16 Configuration Example (EPLA)....................................................................................................................................131
3 Configuring SDH Protection Features............................................................................ 135

3.1 Configuration Procedure (LMSP).................................................................................................................................. 135
3.2 Configuration Procedure (SNCP).................................................................................................................................. 136
3.3 Configuration Procedure (Ring MSP).......................................................................................................................... 137
3.4 Configuration Example (SNCP)..................................................................................................................................... 138
3.5 Configuration Example (LMSP)..................................................................................................................................... 138
3.6 Configuration Example (Ring MSP)............................................................................................................................. 142
4 Configuring Native Ethernet Features........................................................................... 146

4.1 Configuration Process (ERPS on a Single-ring Network)..................................................................................... 148
4.2 Configuration Process (ERPS on a Multi-ring Network).......................................................................................149
4.3 Configuration Process (ERPS Multi-Instance)...........................................................................................................151
4.4 Configuration Procedure (SEP)...................................................................................................................................... 153
4.5 Configuration Procedure (MSTP).................................................................................................................................. 154
4.6 Configuration Procedure (LAG)..................................................................................................................................... 155
4.7 Configuration Procedure (LPT)...................................................................................................................................... 157
4.8 Configuration Process (QoS/HQoS)............................................................................................................................. 159
4.9 Configuration Process (Ethernet Service OAM)....................................................................................................... 165
4.10 Configuration Procedure (Ethernet Port OAM)..................................................................................................... 169
4.11 Configuration Process (Bandwidth Notification).................................................................................................. 169
4.12 Configuration Procedure (IGMP Snooping V2)..................................................................................................... 170
4.13 Configuration Procedure (IGMP Snooping V3)..................................................................................................... 171
4.14 Configuration Example (ERPS on a Single-ring Network)................................................................................ 172
4.15 Configuration Example (ERPS on a Multi-ring Network).................................................................................. 178
4.16 Configuration Example (ERPS Multi-Instance)...................................................................................................... 185
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. vii


4.17 Configuration Example (SEP)...................................................................................................................................... 193
4.18 Configuration Example (MSTP).................................................................................................................................. 197
4.19 Configuration Example (LAG)..................................................................................................................................... 200
4.20 Configuration Example (LPT for Services Traversing an L2 Network).......................................................... 203
4.20.1 Network Diagram......................................................................................................................................................... 203
4.21 Configuration Example (LPT for Services Traversing a PSN)............................................................................ 206
4.21.1 Network Diagram......................................................................................................................................................... 206
4.22 Configuration Example (QoS)..................................................................................................................................... 209
4.23 Configuration Example (HQoS).................................................................................................................................. 214
4.24 Configuration Example (Ethernet Service OAM).................................................................................................. 221
4.25 Configuration Example (Ethernet Port OAM)........................................................................................................225
4.26 Configuration Example (Bandwidth Notification)................................................................................................ 228
4.27 Configuration Example (IGMP Snooping V2)........................................................................................................ 233
4.28 Configuration Example (IGMP Snooping V3)........................................................................................................ 235
5 Configuring MPLS/PWE3 Features.................................................................................. 239

5.1 Configuration Procedure (MPLS OAM_Y.1711)........................................................................................................ 240
5.2 Configuration Procedure (LSP Ping/Traceroute)...................................................................................................... 241
5.3 Configuration Procedure (MPLS APS)......................................................................................................................... 243
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. viii

5.4 Configuration Procedure (PW OAM_Y.1711)............................................................................................................ 247

5.5 Configuration Procedure (PW Ping/Traceroute)...................................................................................................... 247
5.6 Configuration Procedure (PW APS)............................................................................................................................. 248
5.7 Configuration Process (MPLS-TP OAM)..................................................................................................................... 251
5.8 Configuration Procedure (IMA)..................................................................................................................................... 260
5.9 Configuration Procedure (ATM OAM)........................................................................................................................ 261
5.10 Configuration Procedure (ATM Traffic Management)........................................................................................264
5.11 Configuration Procedure (ML-PPP)............................................................................................................................265
5.12 Configuration Example (MPLS OAM_Y.1711)........................................................................................................ 267
5.12.1 Network Diagram......................................................................................................................................................... 267
5.13 Configuration Example (LSP Ping/Traceroute)...................................................................................................... 268
5.14 Configuration Example (MPLS APS)..........................................................................................................................270
5.14.1 Network Diagram......................................................................................................................................................... 270
5.15 Configuration Example (PW OAM_Y.1711).............................................................................................................273
5.15.1 Network Diagram......................................................................................................................................................... 273
5.16 Configuration Example (PW Ping/Traceroute).......................................................................................................274
5.16.1 Network Diagram......................................................................................................................................................... 274
5.17 Configuration Example (PW APS).............................................................................................................................. 276
5.17.1 Network Diagram......................................................................................................................................................... 276
5.18 Configuration Example (PW FPS).............................................................................................................................. 281
5.19 Configuration Example (MPLS-TP OAM for Tunnels)......................................................................................... 284
5.20 Configuration Example (MPLS-TP OAM for PWs)................................................................................................ 289
5.21 Configuration Example (IMA)..................................................................................................................................... 293
5.21.1 Network Diagram......................................................................................................................................................... 293
5.22 Configuration Example (ATM OAM).........................................................................................................................296
5.22.1 Network Diagram......................................................................................................................................................... 296
5.23 Configuration Example (ATM Traffic Management).......................................................................................... 298
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. ix

5.23.1 Network Diagram......................................................................................................................................................... 298

6 Configuring Clock Features.............................................................................................. 302

6.1 Configuration Procedure (IEEE 1588v2)..................................................................................................................... 303
6.2 Configuration Process (ITU-T G.8275.1)..................................................................................................................... 309
6.3 Configuration Procedure (CES ACR)............................................................................................................................ 314
6.4 Configuration Procedure (IEEE 1588 ACR)................................................................................................................ 315
6.5 Configuration Process (ITU-T G.8265.1)..................................................................................................................... 317
6.6 Configuration Example (Network-wide Time Synchronization )....................................................................... 319
6.6.1 Network Diagram........................................................................................................................................................... 320
6.7 Configuration Example (Transparent Transmission of Time Signals).............................................................. 326
6.8 Configuration Example (ITU-T G.8275.1)................................................................................................................... 330
6.9 Configuration Example (CES ACR)............................................................................................................................... 336
6.9.1 Network Diagram........................................................................................................................................................... 336
6.10 Configuration Example (IEEE 1588 ACR).................................................................................................................338
6.10.1 Network Diagram......................................................................................................................................................... 338
6.11 Configuration Example (G.8265.1)............................................................................................................................ 343
6.11.1 Network Diagram......................................................................................................................................................... 343
7 Configuring Maintenance Features................................................................................ 348

7.1 Configuration Procedure (RMON)................................................................................................................................ 348
7.2 Configuration Process (IP Packet Coloring and Statistics Collection).............................................................. 349
7.3 Configuration Process (TWAMP Light)....................................................................................................................... 350
7.4 Configuration Example (RMON)...................................................................................................................................350
7.4.2 Troubleshooting Analysis.............................................................................................................................................. 351
7.4.3 Troubleshooting Flow.................................................................................................................................................... 351
7.5 Configuration Example (IP Packet Coloring and Statistics Collection)............................................................352
7.5.1 Network Diagram........................................................................................................................................................... 352
7.6 Configuration Example (TWAMP Light)..................................................................................................................... 357
7.6.1 Network Diagram........................................................................................................................................................... 357
A Task Collection.................................................................................................................... 361
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. x

A.1 NCE Quick Start.................................................................................................................................................................. 361

A.1.1 Logging In to the NCE Client...................................................................................................................................... 361
A.1.2 Logging Out of the NCE Client.................................................................................................................................. 363
A.1.3 Using Online Help.......................................................................................................................................................... 363
A.1.4 Navigating to Common Views................................................................................................................................... 363
A.1.4.1 Navigating to the Main Topology......................................................................................................................... 364
A.1.4.2 Navigating to the NE Explorer................................................................................................................................364
A.1.4.3 Navigating to the NE Panel..................................................................................................................................... 365
A.2 Web LCT Quick Start......................................................................................................................................................... 366
A.2.1 Using Online Help.......................................................................................................................................................... 366
A.2.2 Navigating to the NE Explorer................................................................................................................................... 366
A.3 Network Management..................................................................................................................................................... 367
A.3.1 Managing NEs................................................................................................................................................................. 367
A.3.1.1 Creating NEs by Using the Search Method (NCE)...........................................................................................367
A.3.1.2 Creating NEs by Using the Search Method (Web LCT)..................................................................................370
A.3.1.3 Creating NEs by Using the Manual Method (NCE).........................................................................................373
A.3.1.4 Creating NEs by Using the Manual Method (Web LCT)................................................................................374
A.3.1.5 Logging In to an NE (Web LCT)............................................................................................................................. 375
A.3.1.6 Configuring the Logical Board................................................................................................................................ 376
A.3.1.7 Configuring an SFP Port............................................................................................................................................378
A.3.1.8 Configuring the Backplane Bus Rate.................................................................................................................... 384
A.3.1.9 Changing the NE ID....................................................................................................................................................384
A.3.1.10 Changing the NE Name..........................................................................................................................................385
A.3.1.11 Enabling NE Automatic Reporting...................................................................................................................... 386
A.3.1.12 Synchronizing the NE Time (NCE)...................................................................................................................... 387
A.3.1.13 Synchronizing the NE Time (Web LCT)............................................................................................................. 390
A.3.1.14 Localizing the NE Time........................................................................................................................................... 391
A.3.1.15 Configuring Standard NTP Keys.......................................................................................................................... 392
A.3.1.16 Configuring NE Anti-Theft..................................................................................................................................... 393
A.3.1.17 Querying the Anti-Theft Status of Boards........................................................................................................396
A.3.2 Configuring the NE Data............................................................................................................................................. 396
A.3.2.1 Uploading the NE Data (NCE)................................................................................................................................397
A.3.2.2 Synchronizing NE Data (NCE)................................................................................................................................ 398
A.3.3 Configuring the Performance Monitoring Status of NEs.................................................................................. 399
A.3.4 Suppressing Alarms for Monitored Objects........................................................................................................... 400
A.3.5 Managing Fibers or Cables..........................................................................................................................................401
A.3.5.1 Creating Optical Fibers by Using the Search Method.................................................................................... 401
A.3.5.2 Creating Fibers Manually......................................................................................................................................... 402
A.3.5.3 Searching for Ethernet Links................................................................................................................................... 403
A.3.5.4 Creating an Extended ECC........................................................................................................................................405
A.3.5.5 Creating a Back-to-Back Radio Connection....................................................................................................... 406
A.3.5.6 Deleting Fibers............................................................................................................................................................. 406
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xi

A.3.6 Managing Subnets......................................................................................................................................................... 407

A.3.6.1 Creating a Subnet....................................................................................................................................................... 407
A.3.6.2 Copying Topology Objects........................................................................................................................................409
A.3.6.3 Moving Topology Objects......................................................................................................................................... 409
A.3.7 Managing Communication..........................................................................................................................................410
A.3.7.1 Setting NE IP Communication Parameters.........................................................................................................410
A.3.7.2 Configuring DCCs........................................................................................................................................................ 411
A.3.7.3 Configuring DCC Transparent Transmission....................................................................................................... 412
A.3.7.4 Configuring the VLAN ID and Bandwidth Used by an Inband DCN..........................................................413
A.3.7.5 Configuring the Priority of Inband DCN Packets............................................................................................. 414
A.3.7.6 Configuring Inband DCN Ports............................................................................................................................... 415
A.3.7.7 Configuring Access Control...................................................................................................................................... 416
A.3.7.8 Configuring Extended ECC Communication.......................................................................................................417
A.3.7.9 Creating a Static IP Route........................................................................................................................................ 419
A.3.7.10 Creating Static Route Entries in Kernel Route Tables.................................................................................. 420
A.3.7.11 Setting OSPF Protocol Parameters..................................................................................................................... 421
A.3.7.12 Creating an OSPF Area........................................................................................................................................... 422
A.3.7.13 Configuring the Network Information of an ABR......................................................................................... 423
A.3.7.14 Creating a Manual Route Aggregation Group................................................................................................424
A.3.7.15 Configuring the OSPF Authentication Type..................................................................................................... 425
A.3.7.16 Enabling the Proxy ARP.......................................................................................................................................... 426
A.3.7.17 Enabling/Disabling the RSTP Protocol When the L2 DCN Solution Is Used........................................ 427
A.3.7.18 Querying ECC Routes...............................................................................................................................................428
A.3.7.19 Querying IP Routes.................................................................................................................................................. 428
A.3.7.20 Querying Core Routing Table Entries.................................................................................................................429
A.3.7.21 Querying OSPF Neighbor Information.............................................................................................................. 430
A.3.7.22 Verifying Connectivity of an ECC Network...................................................................................................... 431
A.3.7.23 Verifying Connectivity of an IP DCN Network................................................................................................ 433
A.3.7.24 Setting SNMP Communications Parameters................................................................................................... 434
A.3.7.25 Configuring the Active and Standby Gateway NEs.......................................................................................436
A.3.8 Configuring the NMS Port........................................................................................................................................... 437
A.3.8.1 Configuring Basic Parameters for the NMS Port..............................................................................................437
A.3.8.2 Setting the VLAN ID for Huawei NMS................................................................................................................. 438
A.3.8.3 Changing the Encapsulation Type and QinQ Type Domain for the Ethernet NMS Port....................439
A.3.8.4 Configuring the Network Management Serial Port on an NE.................................................................... 440
A.3.8.5 Configuring the Mini USB Port............................................................................................................................... 441
A.4 Security Management...................................................................................................................................................... 441
A.4.1 Configuring an NE User................................................................................................................................................442
A.4.1.1 Creating an NE User...................................................................................................................................................442
A.4.1.2 Changing the Password of an NE User................................................................................................................443
A.4.1.3 Configuring Additional User Information........................................................................................................... 445
A.4.1.4 Setting Warning Screen Parameters..................................................................................................................... 445
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xii

A.4.1.5 Querying NE User Groups........................................................................................................................................ 446

A.4.1.6 Managing Online NE Users..................................................................................................................................... 447
A.4.1.7 Switching NE Users..................................................................................................................................................... 447
A.4.2 Configuring LCT Access to NEs.................................................................................................................................. 448
A.4.3 Configuring SSL Protocol Communication.............................................................................................................449
A.4.3.1 Configuring the Connection Mode Between an NCE and Its Gateway NE............................................. 449
A.4.4 Configuring RADIUS Authentication........................................................................................................................ 451
A.4.4.1 Enabling/Disabling the RADIUS Function........................................................................................................... 451
A.4.4.2 Creating a RADIUS Server or a RADIUS Proxy Server.....................................................................................452
A.4.4.3 Configuring RADIUS Server Parameters.............................................................................................................. 454
A.4.4.4 Configuring a KMC Key............................................................................................................................................. 455
A.4.5 Configuring LLDP............................................................................................................................................................ 456
A.4.5.1 Configuring the Transmit Parameters for LLDP Packets................................................................................456
A.4.5.2 Configuring LLDP for an Ethernet Port............................................................................................................... 457
A.4.5.3 Querying LLDP Neighbor Relationship................................................................................................................ 457
A.5 Managing Radio Links...................................................................................................................................................... 458
A.5.1 Configuring a Single-Hop Radio Link...................................................................................................................... 458
A.5.2 Creating an IF 1+1 Protection Group....................................................................................................................... 462
A.5.3 Modifying the Parameters of IF 1+1 Protection.................................................................................................. 464
A.5.4 Creating an N+1 Protection Group........................................................................................................................... 466
A.5.5 Querying the IF 1+1 Protection Status.................................................................................................................... 468
A.5.6 Querying the IF N+1 Protection Status................................................................................................................... 469
A.5.7 IF 1+1 Protection Switching........................................................................................................................................ 469
A.5.8 IF N+1 Protection Switching....................................................................................................................................... 470
A.5.9 Starting/Stopping the N+1 Protection Protocol................................................................................................... 471
A.5.10 Creating a PLA/EPLA/EPLA+/Super EPLA Group............................................................................................... 472
A.5.11 Querying the Status of a PLA/EPLA/EPLA+/Super EPLA Group................................................................... 479
A.5.12 Configuring Ethernet Frame Header Compression over Air Interfaces..................................................... 480
A.5.13 Configuring Enhanced Ethernet Frame Compression...................................................................................... 481
A.5.14 Setting AES-based Encryption at Air Interfaces.................................................................................................481
A.6 Managing the MSP............................................................................................................................................................ 483
A.6.1 Configuring Linear MSP............................................................................................................................................... 483
A.6.2 Querying the Status of the Linear MSP.................................................................................................................. 484
A.6.3 Performing Linear MSP Switching............................................................................................................................ 485
A.6.4 Starting/Stopping the Linear MSP Protocol.......................................................................................................... 486
A.6.5 Configuring Ring MSP................................................................................................................................................... 487
A.6.6 Querying Ring MSP Status.......................................................................................................................................... 488
A.6.7 TriggeMSP ring Ring Switching.................................................................................................................................. 489
A.6.8 Starting/Stopping the MSP Ring Protocol.............................................................................................................. 490
A.6.9 Creating a Packet-based Linear MSP Group......................................................................................................... 490
A.6.10 Querying the Status of a Packet-based Linear MSP Group...........................................................................492
A.6.11 Performing Packet-based Linear MSP Switching.............................................................................................. 493
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xiii

A.6.12 Enabling/Disabling the Linear MSP Protocol......................................................................................................494

A.7 Managing TDM Services.................................................................................................................................................. 495
A.7.1 Creating the Cross-Connections of Point-to-Point Services............................................................................. 495
A.7.2 Creating Cross-Connections of SNCP Services......................................................................................................496
A.7.3 Modifying the Priorities of E1 Services................................................................................................................... 497
A.7.4 Inserting E1_AIS upon a TU_AIS Condition............................................................................................................499
A.7.5 Configuring the Automatic Switching of SNCP Services...................................................................................500
A.7.6 Deleting Cross-Connections........................................................................................................................................ 501
A.7.7 Converting a Normal Service into an SNCP Service........................................................................................... 502
A.7.8 Converting an SNCP Service to a Normal Service...............................................................................................504
A.7.9 Querying TDM Services................................................................................................................................................ 505
A.7.10 Switching SNCP Services............................................................................................................................................ 505
A.7.11 Querying the Protection Status of SNCP Services............................................................................................ 506
A.8 Managing Ports.................................................................................................................................................................. 507
A.8.1 Setting the Parameters of SDH Ports...................................................................................................................... 507
A.8.2 Setting Working Modes of E1 Ports......................................................................................................................... 508
A.8.3 Setting the Parameters of PDH Ports...................................................................................................................... 509
A.8.4 Configuring Overhead Bytes....................................................................................................................................... 509
A.8.4.1 Configuring RSOHs..................................................................................................................................................... 510
A.8.4.2 Configuring VC-4 POHs.............................................................................................................................................511
A.8.4.3 Configuring VC-12 POHs.......................................................................................................................................... 512
A.8.5 Changing the E1 Frame Format and Frame Mode for a Channelized STM-1...........................................514
A.8.6 Setting Smart E1 Port Parameters............................................................................................................................ 514
A.8.6.1 Setting Basic Attributes of Smart E1 Ports......................................................................................................... 514
A.8.6.2 Setting Advanced Attributes of Smart E1 Ports................................................................................................515
A.8.7 Setting Serial Port Parameters................................................................................................................................... 516
A.8.7.1 Creating Serial Ports...................................................................................................................................................516
A.8.7.2 Setting Basic Attributes of Serial Ports................................................................................................................ 517
A.8.8 Setting Ethernet Port Parameters............................................................................................................................. 518
A.8.8.1 Setting the Basic Attributes of Ethernet Ports.................................................................................................. 518
A.8.8.2 Configuring the Traffic Control of Ethernet Ports........................................................................................... 519
A.8.8.3 Setting the Layer 2 Attributes of Ethernet Ports.............................................................................................. 520
A.8.8.4 Setting Layer 3 Attributes of Ethernet Ports......................................................................................................521
A.8.8.5 Setting the Advanced Attributes of Ethernet Ports......................................................................................... 522
A.8.9 Setting Microwave Port Parameters.........................................................................................................................523
A.8.9.1 Setting the Basic Attributes of IF_ETH Ports..................................................................................................... 523
A.8.9.2 Setting the Layer 2 Attributes of IF_ETH Ports................................................................................................. 524
A.8.9.3 Setting Layer 3 Attributes of IF_ETH Ports.........................................................................................................524
A.8.9.4 Setting the Advanced Attributes of IF_ETH Ports............................................................................................ 525
A.8.10 Setting IF Port Parameters........................................................................................................................................ 526
A.8.10.1 Setting IF Attributes................................................................................................................................................. 526
A.8.10.2 Configuring ATPC Attributes................................................................................................................................. 528
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xiv

A.8.10.3 Setting Advanced AM Attributes......................................................................................................................... 529

A.8.10.4 Querying the AM Status......................................................................................................................................... 530
A.8.10.5 Querying ATPC Adjustment Records.................................................................................................................. 531
A.8.10.6 Changing the IF Service Type............................................................................................................................... 531
A.8.10.7 Changing the Running Mode of an IF Port..................................................................................................... 532
A.8.10.8 Enabling or Disabling the AM Booster Function........................................................................................... 533
A.8.10.9 Modifying the Hybrid/AM Attributes................................................................................................................. 534
A.8.11 Setting ODU Port Parameters.................................................................................................................................. 536
A.8.11.1 Setting ODU Transmit Frequency Attributes................................................................................................... 537
A.8.11.2 Querying ODU Information.................................................................................................................................. 538
A.8.11.3 Setting ODU Power Attributes............................................................................................................................. 538
A.8.11.4 Setting ODU Advanced Attributes...................................................................................................................... 539
A.8.12 Creating VLAN Sub-Interfaces................................................................................................................................. 540
A.9 Configuring Native Ethernet Services and Features.............................................................................................. 541
A.9.1 Managing ERPS............................................................................................................................................................... 541
A.9.1.1 Creating Ethernet Ring Protection Instances..................................................................................................... 541
A.9.1.2 Setting Global ERPS Protocol Parameters.......................................................................................................... 543
A.9.1.3 Setting Protocol Parameters for an ERPS Instance..........................................................................................544
A.9.1.4 Creating a Virtual Channel VLAN Forwarding Table...................................................................................... 545
A.9.1.5 Setting Parameters for Switching Upon Multiple Failures............................................................................ 546
A.9.1.6 Performing an External ERPS Switchover........................................................................................................... 547
A.9.1.7 Querying the Status of the Ethernet Ring Protocol........................................................................................ 548
A.9.2 Managing SEP.................................................................................................................................................................. 548
A.9.2.1 Creating SEP Protection Instances......................................................................................................................... 548
A.9.2.2 Configuring the Port Blocking Mode.................................................................................................................... 549
A.9.2.3 Configure the port priority....................................................................................................................................... 550
A.9.2.4 Configuring the Preemption Mode....................................................................................................................... 551
A.9.2.5 Querying the Status of the Ethernet Ring Protocol........................................................................................ 552
A.9.3 Managing the LAG......................................................................................................................................................... 553
A.9.3.1 Creating a LAG............................................................................................................................................................. 553
A.9.3.2 Setting LAG Parameters............................................................................................................................................ 555
A.9.3.3 Querying the Protocol Information of the LAG................................................................................................ 556
A.9.4 Configuring Ethernet Services.................................................................................................................................... 557
A.9.4.1 Configuring the QinQ Link.......................................................................................................................................557
A.9.4.2 Configuring the Forwarding Mode for Ethernet Services..............................................................................558
A.9.4.3 Configuring UNI-UNI E-Line Services (NCE)..................................................................................................... 559
A.9.4.4 Configuring UNI-UNI E-Line Services(Web LCT)..............................................................................................561
A.9.4.5 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(NCE)...................................................... 562
A.9.4.6 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)............................................. 563
A.9.4.7 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(NCE)...................................................... 565
A.9.4.8 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(Web LCT)............................................. 566
A.9.4.9 Configuring UNI-NNI E-Line Services (Carried by PWs)(NCE)....................................................................568
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xv

A.9.4.10 Configuring UNI-NNI E-Line Services (Carried by PWs)(Web LCT)........................................................ 570

A.9.4.11 Creating E-AGGR Services...................................................................................................................................... 572
A.9.4.12 Creating a VLAN Forwarding Table for an E-Line Service.......................................................................... 575
A.9.4.13 Configuring TPID for a Request VLAN...............................................................................................................575
A.9.4.14 Configuring IEEE 802.1d Bridge-Based E-LAN Services (NCE)..................................................................576
A.9.4.15 Configuring IEEE 802.1d Bridge-Based E-LAN Services(Web LCT).......................................................... 577
A.9.4.16 Configuring IEEE 802.1q Bridge-Based E-LAN Services (NCE)..................................................................579
A.9.4.17 Configuring IEEE 802.1q Bridge-Based E-LAN Services(Web LCT).......................................................... 580
A.9.4.18 Configuring IEEE 802.1ad Bridge-Based E-LAN Services (NCE)............................................................... 582
A.9.4.19 Configuring IEEE 802.1ad Bridge-Based E-LAN Services(Web LCT)........................................................584
A.9.4.20 Configuring PW-Carried E-LAN Services (NCE)............................................................................................. 585
A.9.4.21 Configuring Global Attributes of VPLS Services............................................................................................. 588
A.9.4.22 Changing Logical Ports Connected to a VB..................................................................................................... 589
A.9.4.23 Deleting an E-Line Service..................................................................................................................................... 590
A.9.4.24 Deleting E-LAN Services......................................................................................................................................... 591
A.9.5 Managing the MAC Address Table........................................................................................................................... 591
A.9.5.1 Creating a Static MAC Address Entry................................................................................................................... 592
A.9.5.2 Creating a Blacklist Entry of MAC Addresses.................................................................................................... 592
A.9.5.3 Configuring the MAC Address Learning Parameters...................................................................................... 593
A.9.5.4 Querying or Deleting a Dynamic MAC Address............................................................................................... 594
A.9.6 Setting the Mode for Processing an Unknown Frame of the E-LAN Service.............................................594
A.9.7 Managing the MSTP...................................................................................................................................................... 595
A.9.7.1 Creating the MSTP Port Group............................................................................................................................... 595
A.9.7.2 Setting the Bridge Parameters of the MSTP...................................................................................................... 597
A.9.7.3 Setting the Parameters of the CIST...................................................................................................................... 597
A.9.7.4 Querying the CIST Running Information............................................................................................................ 598
A.9.7.5 Changing the Spanning Tree Protocol Used by the Port Group................................................................. 599
A.9.7.6 Enabling/Disabling the MSTP Protocol................................................................................................................ 600
A.9.7.7 Modifying the Configuration Data of the MSTP Port Group....................................................................... 601
A.9.8 Managing the IGMP Snooping...................................................................................................................................602
A.9.8.1 Configuring the IGMP Snooping Protocol.......................................................................................................... 602
A.9.8.2 Querying the Port Information of the Routers................................................................................................. 603
A.9.8.3 Querying the Information About the Multicast Groups................................................................................ 603
A.9.8.4 Creating Static Router Ports.................................................................................................................................... 604
A.9.8.5 Creating a Member of a Static Multicast Group for V2................................................................................ 605
A.9.8.6 Creating a Member of a Static Multicast Group for V3................................................................................ 606
A.9.8.7 Adding a Quickly Deleted Port............................................................................................................................... 607
A.9.8.8 Calculating IGMP Packets........................................................................................................................................ 608
A.9.8.9 Adding SSM Mapping................................................................................................................................................ 608
A.9.9 Managing the QoS......................................................................................................................................................... 609
A.9.9.1 Creating a DS Domain............................................................................................................................................... 609
A.9.9.2 Modifying the Mapping Relationships for the DS Domain.......................................................................... 611
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xvi

A.9.9.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types..................................... 612
A.9.9.4 Enabling/Disabling DSCP Demapping at the Egress Port of a DiffServ Domain.................................. 614
A.9.9.5 Enabling/Disabling Outbound Demapping at the Egress Port of a DiffServ Domain.........................615
A.9.9.6 Creating a Port Policy................................................................................................................................................ 616
A.9.9.7 Modifying the Port Policy......................................................................................................................................... 617
A.9.9.8 Creating Traffic............................................................................................................................................................ 618
A.9.9.9 Creating a Port WRED Policy.................................................................................................................................. 620
A.9.9.10 Creating a Service WRED Policy.......................................................................................................................... 621
A.9.9.11 Creating a WRR Policy............................................................................................................................................ 622
A.9.9.12 Setting the Port That Uses the Port Policy...................................................................................................... 623
A.9.9.13 Creating a V-UNI Egress Policy............................................................................................................................ 625
A.9.9.14 Creating a V-UNI Group......................................................................................................................................... 626
A.9.9.15 Creating a PW Policy............................................................................................................................................... 628
A.9.9.16 Creating a QinQ Policy........................................................................................................................................... 629
A.9.9.17 Applying policies for Ethernet services.............................................................................................................. 630
A.9.9.18 Configuring Port Shaping.......................................................................................................................................631
A.9.9.19 Configuring Bandwidth Limitation for MPLS Tunnels..................................................................................632
A.9.9.20 Configuring Bandwidth Limitation for PWs.....................................................................................................633
A.9.9.21 Configuring Bandwidth Limitation for QinQ Links....................................................................................... 633
A.9.10 Using the ethernet service OAM.............................................................................................................................634
A.9.10.1 Creating an MD......................................................................................................................................................... 634
A.9.10.2 Creating an MA......................................................................................................................................................... 635
A.9.10.3 Creating MEPs............................................................................................................................................................ 636
A.9.10.4 Creating Remote MEPs in an MA........................................................................................................................637
A.9.10.5 Creating MIPs............................................................................................................................................................. 638
A.9.10.6 Performing a CC Test............................................................................................................................................... 639
A.9.10.7 Performing an LB Test............................................................................................................................................. 640
A.9.10.8 Performing an LT Test............................................................................................................................................. 642
A.9.10.9 Activating the AIS..................................................................................................................................................... 643
A.9.10.10 Monitoring Packet Loss Ratio, Delay, or Delay Variation of Ethernet Services................................ 644
A.9.10.11 E-LAN Service Loopback Detection.................................................................................................................. 645
A.9.10.12 Reactivating E-LAN Services............................................................................................................................... 646
A.9.10.13 Setting the Enabling Status of Automatic Service Loop Detection for NEs.......................................647
A.9.10.14 Configuring Bandwidth Notification................................................................................................................ 650
A.9.11 Using the ethernet port OAM.................................................................................................................................. 652
A.9.11.1 Enabling the OAM Auto-Discovery Function.................................................................................................. 652
A.9.11.2 Enabling the Link Event Notification ................................................................................................................ 653
A.9.11.3 Modifying the OAM Error Frame Monitoring Threshold............................................................................ 654
A.9.11.4 Performing Remote Loopbacks............................................................................................................................ 655
A.9.11.5 Enabling Self-Loop Detection............................................................................................................................... 656
A.9.12 LPT Configuration........................................................................................................................................................ 657
A.9.12.1 Configuring Point-to-Point LPT Traversing an L2 Network........................................................................657
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xvii

A.9.12.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network..................................................... 658

A.9.12.3 Configuring Point-to-Multipoint LPT................................................................................................................. 659
A.9.12.4 Configuring Simple LPT.......................................................................................................................................... 660
A.9.13 Configuring IP Packet Coloring and Statistics Collection............................................................................... 661
A.10 Configuring Ethernet Services and Features on the EoS/EoPDH Boards..................................................... 664
A.10.1 Managing ERPS............................................................................................................................................................. 664
A.10.1.1 Creating ERPS Instances......................................................................................................................................... 664
A.10.1.2 Setting the Parameters of the ERPS Protocol................................................................................................. 665
A.10.1.3 Querying the Status of the ERPS Protocol....................................................................................................... 666
A.10.2 Managing LAGs ........................................................................................................................................................... 666
A.10.2.1 Creating a LAG...........................................................................................................................................................666
A.10.2.2 Setting Parameters for LAGs................................................................................................................................. 668
A.10.2.3 Querying the Protocol Information of LAGs................................................................................................... 669
A.10.3 Configuring Ethernet Services..................................................................................................................................669
A.10.3.1 Creating Ethernet Private Line Services............................................................................................................ 670
A.10.3.2 Creating Ethernet LAN Services........................................................................................................................... 672
A.10.3.3 Changing the Ports Connected to a VB............................................................................................................ 676
A.10.3.4 Creating the VLAN Filtering Table...................................................................................................................... 677
A.10.3.5 Creating QinQ-Based EVPL Services.................................................................................................................. 678
A.10.3.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services................................................................................680
A.10.3.7 Deleting an Ethernet Private Line Service........................................................................................................ 683
A.10.3.8 Deleting an Ethernet LAN Service...................................................................................................................... 684
A.10.4 Managing the MAC Address Table.........................................................................................................................685
A.10.4.1 Creating a Static MAC Address Entry.................................................................................................................685
A.10.4.2 Creating a Blacklist Entry of a MAC Address.................................................................................................. 686
A.10.4.3 Setting the Aging Time of a MAC Address Table Entry...............................................................................686
A.10.4.4 Querying or Deleting a Dynamic MAC Address.............................................................................................687
A.10.4.5 Querying the Actual Capacity of a MAC Address Table.............................................................................. 688
A.10.5 Configuring Ethernet Ports....................................................................................................................................... 688
A.10.5.1 Configuring External Ethernet Ports.................................................................................................................. 688
A.10.5.2 Configuring VCTRUNKs on an Ethernet Board............................................................................................... 690
A.10.5.3 Modifying the Type Field of QinQ Frames.......................................................................................................692
A.10.5.4 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth................................................................ 693
A.10.6 Managing the Spanning Tree Protocol................................................................................................................. 694
A.10.6.1 Configuring the Type and Enabled Status of the Spanning Tree Protocol........................................... 694
A.10.6.2 Setting the Parameters of Spanning Tree Protocol....................................................................................... 695
A.10.6.3 Querying the Running Information About the Spanning Tree Protocol................................................ 696
A.10.7 Managing the IGMP Snooping Protocol.............................................................................................................. 697
A.10.7.1 Configuring the IGMP Snooping Protocol........................................................................................................ 697
A.10.7.2 Configuring Static Multicast Entries...................................................................................................................697
A.10.7.3 Modifying the Aging Time of a Multicast Table Entry................................................................................ 699
A.10.7.4 Querying the Running Information of the IGMP Snooping Protocol..................................................... 699
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xviii

A.10.8 Managing the QoS.......................................................................................................................................................700

A.10.8.1 Creating a Flow......................................................................................................................................................... 700
A.10.8.2 Creating the CAR.......................................................................................................................................................701
A.10.8.3 Creating the CoS....................................................................................................................................................... 702
A.10.8.4 Binding the CAR/CoS............................................................................................................................................... 706
A.10.8.5 Configuring Traffic Shaping for Egress Queues............................................................................................. 707
A.10.8.6 Configuring Port Shaping.......................................................................................................................................707
A.10.8.7 Setting Egress Queue Scheduling Policies........................................................................................................ 708
A.10.9 Using the Ethernet service OAM.............................................................................................................................708
A.10.9.1 Creating MDs............................................................................................................................................................. 709
A.10.9.2 Creating MAs.............................................................................................................................................................. 710
A.10.9.3 Creating MPs.............................................................................................................................................................. 711
A.10.9.4 Performing a CC Test............................................................................................................................................... 712
A.10.9.5 Performing an LB Test............................................................................................................................................. 713
A.10.9.6 Performing an LT Test............................................................................................................................................. 714
A.10.9.7 Activating the AIS..................................................................................................................................................... 715
A.10.9.8 Performing a Ping Test............................................................................................................................................716
A.10.9.9 Performing Performance Check........................................................................................................................... 717
A.10.10 Using the Ethernet port OAM............................................................................................................................... 718
A.10.10.1 Enabling the OAM Auto-Discovery Function................................................................................................ 718
A.10.10.2 Enabling the Link Event Notification............................................................................................................... 719
A.10.10.3 Modifying the OAM Error Frame Monitoring Threshold.......................................................................... 720
A.10.10.4 Performing the Remote Loopback................................................................................................................... 721
A.10.11 Configuring LPT.......................................................................................................................................................... 722
A.10.11.1 Configuring LPT for Point-to-Point Services................................................................................................. 722
A.10.11.2 Configuring LPT for Point-to-Multipoint Services....................................................................................... 723
A.11 Managing MPLS/PWE3 Services and Features...................................................................................................... 724
A.11.1 Managing Address Resolution................................................................................................................................. 724
A.11.1.1 Creating ARP Static Entries................................................................................................................................... 724
A.11.1.2 Querying ARP Entries.............................................................................................................................................. 725
A.11.1.3 Converting Dynamic ARP Entries to Static ARP Entries.............................................................................. 726
A.11.1.4 Deleting Static ARP Entries................................................................................................................................... 726
A.11.1.5 Setting ARP Aging Time......................................................................................................................................... 727
A.11.2 Managing MPLS Tunnels........................................................................................................................................... 728
A.11.2.1 Setting Basic MPLS Attributes.............................................................................................................................. 728
A.11.2.2 Configuring Global OAM Parameters................................................................................................................ 729
A.11.2.3 Changing the MPLS Tunnel/PW OAM Standard............................................................................................ 729
A.11.2.4 Creating a Unidirectional MPLS Tunnel............................................................................................................ 730
A.11.2.5 Creating a Bidirectional MPLS Tunnel............................................................................................................... 732
A.11.2.6 Querying MPLS Tunnel Information.................................................................................................................. 734
A.11.2.7 Changing MPLS Tunnel Information.................................................................................................................. 734
A.11.2.8 Deleting MPLS Tunnels........................................................................................................................................... 735
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xix

A.11.2.9 Setting MPLS OAM (Y.1711) Parameters......................................................................................................... 736

A.11.2.10 Enabling/Disabling FDI......................................................................................................................................... 737
A.11.2.11 Starting/Stopping CV/FFD Detection for MPLS Tunnels........................................................................... 737
A.11.2.12 Querying LSP Running Status............................................................................................................................ 739
A.11.2.13 Clearing OAM Configuration Data for MPLS Tunnel OAM (Y.1711)....................................................739
A.11.2.14 Performing an LSP Ping Test.............................................................................................................................. 740
A.11.2.15 Performing an LSP Traceroute Test.................................................................................................................. 741
A.11.2.16 Configuring MEP Parameters for MPLS-TP Tunnel OAM......................................................................... 742
A.11.2.17 Creating MIPs of MPLS-TP Tunnel OAM........................................................................................................ 743
A.11.2.18 Starting a CC Test of MPLS-TP Tunnel OAM.................................................................................................744
A.11.2.19 Starting an LB Test of MPLS-TP Tunnel OAM...............................................................................................745
A.11.2.20 Starting an LT Test Provided by MPLS-TP Tunnel OAM............................................................................ 746
A.11.2.21 Testing the Delay and Delay Variation of an MPLS Tunnel.................................................................... 747
A.11.2.22 Setting the LCK Status of MPLS-TP Tunnel OAM........................................................................................ 748
A.11.2.23 Starting a TST Test Provided by MPLS-TP Tunnel OAM............................................................................749
A.11.3 Managing MPLS APS Protection Groups..............................................................................................................750
A.11.3.1 Creating an MPLS APS Protection Group......................................................................................................... 750
A.11.3.2 Querying MPLS APS Status................................................................................................................................... 752
A.11.3.3 Triggering MPLS APS Switching........................................................................................................................... 753
A.11.3.4 Enabling/Disabling MPLS APS Protection........................................................................................................ 754
A.11.4 Managing PWs.............................................................................................................................................................. 755
A.11.4.1 Querying Information and Running Status of PWs...................................................................................... 755
A.11.4.2 Creating an MS-PW................................................................................................................................................. 756
A.11.4.3 Setting PW OAM (Y.1711) Parameters..............................................................................................................758
A.11.4.4 Performing a PW Ping Test....................................................................................................................................758
A.11.4.5 Performing a PW Traceroute Test....................................................................................................................... 759
A.11.4.6 Configuring MEP Parameters for MPLS-TP PW OAM.................................................................................. 760
A.11.4.7 Creating MIPs of MPLS-TP PW OAM................................................................................................................. 761
A.11.4.8 Starting a CC Test of MPLS-TP PW OAM..........................................................................................................762
A.11.4.9 Starting an LB Test of MPLS-TP PW OAM........................................................................................................763
A.11.4.10 Starting an LT Test Provided by MPLS-TP PW OAM...................................................................................764
A.11.4.11 Testing the Packet Loss Ratio, Delay, and Delay Variation of a PW.....................................................765
A.11.4.12 Setting the LCK Status of MPLS-TP PW OAM.............................................................................................. 766
A.11.4.13 Starting a TST Test of MPLS-TP PW OAM..................................................................................................... 767
A.11.5 Managing a PW APS/PW FPS Protection Group............................................................................................... 768
A.11.5.1 Creating a PW APS Protection Group................................................................................................................ 768
A.11.5.2 Creating a PW FPS Protection Group.................................................................................................................771
A.11.5.3 Configuring Slave Protection Pairs of PW APS............................................................................................... 773
A.11.5.4 Querying PW APS Status........................................................................................................................................775
A.11.5.5 Triggering PW APS Switching............................................................................................................................... 776
A.11.5.6 Enabling/Disabling PW APS Protection............................................................................................................. 777
A.11.6 Managing CES Services.............................................................................................................................................. 778
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xx

A.11.6.1 Creating CES Services.............................................................................................................................................. 778

A.11.6.2 Modifying CES Service Parameters..................................................................................................................... 782
A.11.6.3 Querying CES Service Information......................................................................................................................783
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............................................................................................................................... 788
A.11.7.4 Querying Running Status of an IMA Group.................................................................................................... 789
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................................................................................................................... 795
A.11.8.3 Querying ATM Services...........................................................................................................................................795
A.11.8.4 Deleting an ATM Service........................................................................................................................................ 796
A.11.9 ATM Traffic Management......................................................................................................................................... 797
A.11.9.1 Creating an ATM-DiffServ Domain.....................................................................................................................797
A.11.9.2 Modifying an ATM-Diffserv Domain..................................................................................................................798
A.11.9.3 Creating an ATM Policy.......................................................................................................................................... 800
A.11.9.4 Modifying an ATM Policy....................................................................................................................................... 801
A.11.10 Using ATM OAM........................................................................................................................................................ 802
A.11.10.1 Enabling/Disabling the AIS/RDI Insertion Status........................................................................................ 802
A.11.10.2 Setting Segment and End Attributes of AIS/RDI......................................................................................... 803
A.11.10.3 Performing a Continuity Check Test................................................................................................................ 803
A.11.10.4 Querying or Setting LLIDs................................................................................................................................... 804
A.11.10.5 Performing an LB Test.......................................................................................................................................... 805
A.11.11 Managing MP Groups.............................................................................................................................................. 806
A.11.11.1 Creating MP Groups.............................................................................................................................................. 806
A.11.11.2 Querying the MP Group Protocol Information............................................................................................ 807
A.12 Managing the Clock........................................................................................................................................................808
A.12.1 Managing Clocks at the Physical Layer................................................................................................................ 808
A.12.1.1 Setting the SDH Retiming Function................................................................................................................... 808
A.12.1.2 Setting the E1 Clock Source for a Channelized STM-1 Interface Board................................................ 809
A.12.1.3 Configuring the Clock Sources............................................................................................................................. 810
A.12.1.4 Configuring Clock Subnets.................................................................................................................................... 811
A.12.1.5 User-Defined Clock Quality...................................................................................................................................811
A.12.1.6 Configuring a Clock Source Group......................................................................................................................813
A.12.1.7 Configuring the SSM Output Status.................................................................................................................. 814
A.12.1.8 Configuring the Clock ID Output Status........................................................................................................... 815
A.12.1.9 Modifying the Parameters of the Clock Output............................................................................................ 816
A.12.1.10 Configuring Clock Sources for External Clock Output............................................................................... 816
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxi

A.12.1.11 Changing the Conditions for Clock Source Switching............................................................................... 817

A.12.1.12 Modifying the Recovery Parameter of the Clock Source.......................................................................... 818
A.12.1.13 Querying the Clock Synchronization Status.................................................................................................. 819
A.12.2 Managing CES ACR Clocks........................................................................................................................................ 819
A.12.2.1 Configuring a CES Transmit Clock.......................................................................................................................819
A.12.2.2 Configuring the Primary Clock for an ACR Clock Domain......................................................................... 822
A.12.2.3 Configuring Ports Using the Clock Domain..................................................................................................... 823
A.12.2.4 Querying the CES ACR Clock Status................................................................................................................... 824
A.12.3 Managing the PTP Clock........................................................................................................................................... 825
A.12.3.1 Configuring the PTP Profile................................................................................................................................... 825
A.12.3.2 Changing the Mode for Selecting the Frequency Source........................................................................... 826
A.12.3.3 Querying or Modifying the PTP System Time................................................................................................ 826
A.12.3.4 Setting the PTP NE Attributes.............................................................................................................................. 827
A.12.3.5 Creating PTP Clock Ports........................................................................................................................................ 828
A.12.3.6 Setting PTP Clock Port Attributes........................................................................................................................829
A.12.3.7 Setting Parameters for PTP Clock Packets....................................................................................................... 830
A.12.3.8 Configuring the Cable Transmission Offset Between NEs.......................................................................... 831
A.12.3.9 Configuring a PTP Clock Subnet.......................................................................................................................... 831
A.12.3.10 Modifying the BMC Algorithm Parameters for NE Clocks....................................................................... 832
A.12.3.11 Setting Basic Attributes of External Time Ports........................................................................................... 833
A.12.3.12 Setting BMC Algorithm Parameters for External Time Ports.................................................................. 833
A.12.3.13 Setting the Cable Transmission Offset for External Time Ports............................................................. 834
A.13 Ethernet Performance Query....................................................................................................................................... 835
A.13.1 Browsing Current Ethernet Performance............................................................................................................. 835
A.13.2 Configuring Ethernet Performance Threshold-Crossing Parameters..........................................................840
A.13.3 Setting Parameters for Monitoring Historical Ethernet Performance........................................................845
A.13.4 Browsing Historical Ethernet Performance Data.............................................................................................. 845
A.14 Configuring Auxiliary Ports and Functions............................................................................................................. 850
A.14.1 Configuring Orderwire................................................................................................................................................ 850
A.14.2 Configuring the Synchronous Data Service.........................................................................................................851
A.14.3 Configuring the Asynchronous Data Service...................................................................................................... 852
A.14.4 Configuring the Wayside E1 Service...................................................................................................................... 853
A.14.5 Configure External Alarms........................................................................................................................................ 854
A.14.6 Monitoring the Outdoor Cabinet............................................................................................................................855
A.14.6.1 Configuring the Function for an Auxiliary Port.............................................................................................. 855
A.14.6.2 Setting the Type of the Outdoor Cabinet......................................................................................................... 856
A.14.6.3 Querying and Setting the Temperature and Fan Information of the Outdoor Cabinet...................857
A.14.6.4 Querying and Setting the Information About the Power System of the Outdoor Cabinet............ 858
A.14.6.5 Querying the Ambient Temperature and Humidity of the Outdoor Cabinet...................................... 859
A.14.6.6 Setting Environment Alarm Parameters for Outdoor Cabinets................................................................ 860
B Parameters Description..................................................................................................... 861

B.1 Parameters for Network Management.......................................................................................................................861
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxii

B.1.1 Parameters for NE Management.............................................................................................................................. 861

B.1.1.1 Parameter Description: NE Searching (NCE)..................................................................................................... 861
B.1.1.2 Parameter Description: NE Searching (Web LCT)............................................................................................ 866
B.1.1.3 Parameter Description: NE Creation (NCE)........................................................................................................ 867
B.1.1.4 Parameter Description: NE Creation (Web LCT)...............................................................................................872
B.1.1.5 Parameter Description: Login to an NE (Web LCT).........................................................................................873
B.1.1.6 Parameter Description:Changing NE IDs.............................................................................................................874
B.1.1.7 Parameter Description: NE Time Synchronization (NCE).............................................................................. 875
B.1.1.8 Parameter Description: NE Time Synchronization (Web LCT)..................................................................... 879
B.1.1.9 Parameter Description: Localization Management of the NE Time.......................................................... 884
B.1.1.10 Parameter Description: Standard NTP Key Management...........................................................................886
B.1.1.11 Parameter Description: License Management................................................................................................ 887
B.1.2 Parameters for Communications Management................................................................................................... 888
B.1.2.1 Parameter Description: NE Communication Parameter Setting................................................................. 888
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration....................................................... 889
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management............... 892
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC.................................................893
B.1.2.5 Parameter Description: NE ECC Link Management......................................................................................... 895
B.1.2.6 Parameter Description: ECC Link Management_Availability Test............................................................... 896
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management................................. 897
B.1.2.8 Parameter Description: IP Protocol Stack Management_IP Route Management Creation............... 899
B.1.2.9 Parameter Description: IP Protocol Stack Management_Availability Test...............................................900
B.1.2.10 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings.......................... 901
B.1.2.11 Parameter Description: IP Protocol Stack_Proxy ARP................................................................................... 907
B.1.2.12 Parameter Description: Management of Multiple OSPF Areas.................................................................908
B.1.2.13 Parameter Description: Management of Multiple OSPF Areas_Adding OSPF Areas.........................909
B.1.2.14 Parameter Description: Management of Multiple OSPF Areas_Adding Routes to Be Manually
Aggregated.................................................................................................................................................................................. 911
B.1.2.15 Parameter Description: Port OSPF Setting....................................................................................................... 911
B.1.2.16 Parameter Description: Static Route Entries in a Kernel Route Table_Creation..................................912
B.1.2.17 Parameter Description: DCN Management_Bandwidth Management.................................................. 913
B.1.2.18 Parameter Description: DCN Management_Port Setting............................................................................ 914
B.1.2.19 Parameter Description: DCN Management_Access Control.......................................................................916
B.1.2.20 Parameter Description: DCN Management_Packet Control.......................................................................917
B.1.2.21 Parameter Description: L2 DCN Management............................................................................................... 918
B.1.2.22 Parameter Description: Access Control..............................................................................................................919
B.1.2.23 Parameter Description: SNMP Communication..............................................................................................921
B.1.2.24 Parameter Description: LLDP................................................................................................................................ 923
B.1.3 Parameters for Network Security Management.................................................................................................. 925
B.1.3.1 Parameter Description: RADIUS Configuration_Creation.............................................................................. 925
B.1.3.2 Parameter Description: RADIUS Configuration_RADIUS Server.................................................................. 926
B.1.3.3 Parameter Description: Enabling/Disabling the RADIUS Function.............................................................927
B.2 Radio Link Parameters...................................................................................................................................................... 928
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxiii

B.2.1 Parameter Description: N+1 Protection_Create....................................................................................................928

B.2.2 Parameter Description: N+1 Protection.................................................................................................................. 930
B.2.3 Parameter Description: IF 1+1 Protection_Create................................................................................................932
B.2.4 Parameter Description: IF 1+1 Protection.............................................................................................................. 937
B.2.5 Parameter Description: Link Configuration_Creating a PLA/EPLA/EPLA+/Super EPLA Group............. 940
B.2.6 Parameter Description: Link Configuration_PLA/EPLA/EPLA+/Super EPLA................................................ 945
B.2.7 Parameter Description: Microwave Link Management......................................................................................952
B.2.8 Parameter Description: Single Site MIMO_New Deployment......................................................................... 958
B.2.9 Parameter Description: CA_New Deployment...................................................................................................... 962
B.3 Multiplex Section Protection Parameters...................................................................................................................966
B.3.1 Parameter Description: Linear MSP_Creation....................................................................................................... 967
B.3.2 Parameter Description: Linear MSP.......................................................................................................................... 970
B.3.3 Parameter Description: Packet-based Linear MSP_Creation............................................................................ 973
B.3.4 Parameter Description: Packet-based Linear MSP.............................................................................................. 976
B.3.5 Parameter Description: Ring MSP_Creation...........................................................................................................979
B.3.6 Parameter Description: Ring MSP............................................................................................................................. 982
B.4 TDM Service Parameters..................................................................................................................................................983
B.4.1 Parameter Description: SDH/PDH Service Configuration_Creation...............................................................983
B.4.2 Parameter Description: SDH/PDH Service Configuration_SNCP Service Creation................................... 986
B.4.3 Parameter Description: SDH/PDH Service Configuration_Converting Normal Services Into SNCP
Services.......................................................................................................................................................................................... 991
B.4.4 Parameter Description: SDH/PDH Service Configuration................................................................................. 995
B.4.5 Parameter Description: SNCP Service Control...................................................................................................... 996
B.4.6 Parameter Description: TU_AIS Insertion............................................................................................................. 1000
B.5 Parameters for Board Interfaces................................................................................................................................. 1002
B.5.1 Parameter Description: Working Modes of Ports.............................................................................................. 1002
B.5.2 PDH Port Parameters.................................................................................................................................................. 1002
B.5.2.1 Parameter Description: PDH Ports_Basic Attributes..................................................................................... 1003
B.5.2.2 Parameter Description: PDH Ports_Advanced Attributes............................................................................ 1004
B.5.3 Parameters for the Ports on Ethernet Boards.....................................................................................................1009
B.5.3.1 Parameter Description: Ethernet Interface_Basic Attributes...................................................................... 1009
B.5.3.2 Parameter Description: Ethernet Interface_Flow Control........................................................................... 1013
B.5.3.3 Parameter Description: Ethernet Interface_Layer 2 Attributes..................................................................1015
B.5.3.4 Parameter Description: Ethernet Port_Layer 3 Attributes........................................................................... 1017
B.5.3.5 Parameter Description: Ethernet Interface_Advanced Attributes............................................................. 1018
B.5.4 Serial Port Parameters................................................................................................................................................ 1025
B.5.4.1 Parameter Description: Serial Port_Basic Attributes..................................................................................... 1025
B.5.4.2 Parameter Description: Serial Port_Creation of Serial Ports...................................................................... 1027
B.5.5 Channelized STM-1 Port Parameters.....................................................................................................................1028
B.5.5.1 Parameter Description: Clock Transparent Transmission.............................................................................1029
B.5.5.2 Parameter Description: Path Configuration..................................................................................................... 1030
B.5.6 Microwave Interface Parameters............................................................................................................................ 1033
B.5.6.1 Parameter Description: Microwave Interface_Basic Attributes..................................................................1033
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxiv

B.5.6.2 Parameter Description: Microwave Interface_Layer 2 Attributes............................................................. 1035

B.5.6.3 Parameter Description: Microwave Interface_Layer 3 Attributes............................................................. 1037
B.5.6.4 Parameter Description: Microwave Interface_Advanced Attributes........................................................ 1039
B.5.7 IF Board Parameters.................................................................................................................................................... 1041
B.5.7.1 Parameter Description: IF Port_IF Attributes................................................................................................... 1041
B.5.7.2 Parameter Description: IF Interface_ATPC Attribute.....................................................................................1049
B.5.7.3 Parameter Description: IF Port_Advanced Attributes................................................................................... 1051
B.5.7.4 Parameter Description: ATPC Adjustment Records....................................................................................... 1052
B.5.7.5 Parameter Description: IF Multiplexing Port Management....................................................................... 1053
B.5.8 RFU/ODU Parameters................................................................................................................................................. 1054
B.5.8.1 Parameter Description: RFU/RFU-SD/ODU Interface_Radio Frequency Attribute..............................1054
B.5.8.2 Parameter Description: RFU/RFU-SD/ODU Interface_Power Attributes................................................ 1056
B.5.8.3 Parameter Description: RFU/RFU-SD/ODU Interface_Equipment Information................................... 1061
B.5.8.4 Parameter Description: ODU Interface_Advanced Attributes.................................................................... 1062
B.5.9 Parameters for SDH Interface Boards................................................................................................................... 1064
B.5.9.1 Parameter Description: SDH Interfaces............................................................................................................. 1064
B.5.9.2 Parameter Description: Automatic Laser Shutdown..................................................................................... 1066
B.5.10 Parameters for PDH Interface Boards................................................................................................................. 1067
B.5.10.1 Parameter Description: PDH Ports....................................................................................................................1067
B.5.11 Parameters for Overhead........................................................................................................................................ 1070
B.5.11.1 Parameter Description: Regenerator Section Overhead........................................................................... 1070
B.5.11.2 Parameter Description: VC-4 POHs.................................................................................................................. 1071
B.5.11.3 Parameter Description: VC-12 POHs................................................................................................................1073
B.5.12 Parameter Description: Ethernet Virtual Interfaces....................................................................................... 1075
B.5.13 Parameter Description: COMBO Port..................................................................................................................1079
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane..........................................1079
B.6.1 Parameters for Ethernet Services............................................................................................................................ 1080
B.6.1.1 Parameter Description: E-Line Service_Creation (NCE)............................................................................... 1080
B.6.1.2 Parameter Description: E-Line Service_Creation(Web LCT)....................................................................... 1105
B.6.1.3 Parameter Description: E-Line Service............................................................................................................... 1131
B.6.1.4 Parameter Description: VLAN Forwarding Table Items for E-Line Services_Creation....................... 1144
B.6.1.5 Parameter Description: E-LAN Service_Creation (NCE)............................................................................... 1145
B.6.1.6 Parameter Description: E-LAN Service_Creation(Web LCT)....................................................................... 1155
B.6.1.7 Parameter Description: E-LAN Service(NCE)................................................................................................... 1167
B.6.1.8 Parameter Description: E-LAN Service(Web LCT)..........................................................................................1183
B.6.1.9 Parameter Description: QinQ Link_Creation....................................................................................................1198
B.6.1.10 Parameter Description: E-AGGR Services_Creation.....................................................................................1199
B.6.1.11 Parameter Description: E-AGGR Services....................................................................................................... 1208
B.6.2 Parameters for Ethernet Protocols......................................................................................................................... 1214
B.6.2.1 Parameter Description: ERPS Management_Creation.................................................................................. 1214
B.6.2.2 Parameter Description: ERPS Management.....................................................................................................1217
B.6.2.3 Parameter Description: SEP Management_Creation.....................................................................................1231
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxv

B.6.2.4 Parameter Description: SEP Management....................................................................................................... 1234

B.6.2.5 Parameter Description: MSTP Configuration_Port Group Creation......................................................... 1239
B.6.2.6 Parameter Description: MSTP Configuration_Port Group Configuration.............................................. 1241
B.6.2.7 Parameter Description: MSTP Configuration_ Bridge Parameters........................................................... 1241
B.6.2.8 Parameter Description: MSTP Configuration_CIST Parameters................................................................ 1246
B.6.2.9 Parameter Description: MSTP Configuration_Running Information About the CIST........................ 1248
B.6.2.10 Parameter Description: IGMP Snooping Configuration_Protocol Configuration.............................. 1258
B.6.2.11 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted....... 1261
B.6.2.12 Parameter Description: IGMP Snooping Configuration_Route Management................................... 1262
B.6.2.13 Parameter Description: IGMP Snooping Configuration_Static Router Port Creation......................1263
B.6.2.14 Parameter Description: IGMP Snooping Configuration_Route Member Port Management........1264
B.6.2.15 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation
....................................................................................................................................................................................................... 1266
B.6.2.16 Parameter Description: IGMP Snooping Configuration_Data Count.................................................... 1267
B.6.2.17 Parameter Description: IGMP Snooping Configuration_SSM Mapping............................................... 1269
B.6.2.18 Parameter Description: Ethernet Link Aggregation Management_LAG Creation............................ 1270
B.6.2.19 Parameter Description: Ethernet Link Aggregation_Link Aggregation................................................ 1278
B.6.2.20 Parameter Description: LPT Management_Creating Simple LPT........................................................... 1281
B.6.2.21 Parameter Description: LPT Management_Point-to-Point LPT...............................................................1281
B.6.2.22 Parameter Description: LPT Management_Creating Point-to-Point LPT.............................................1284
B.6.2.23 Parameter Description: LPT Management_Point-to-Multipoint LPT.................................................... 1285
B.6.2.24 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT.................................. 1288
B.6.3 Parameters for the Ethernet OAM......................................................................................................................... 1292
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation.... 1293
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation
....................................................................................................................................................................................................... 1293
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation...................................... 1295
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation......................1296
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation....................................... 1296
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling..........................................1297
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling.......................................... 1299
B.6.3.8 Parameter Description: Ethernet Service OAM_Enabling Service Loopback Detection.................... 1301
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Parameter.......................................1302
B.6.3.10 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring..........1306
B.6.3.11 Parameter Description: Ethernet OAM Management_Configuring Bandwidth Notification....... 1307
B.6.4 QoS Parameters............................................................................................................................................................ 1308
B.6.4.1 Parameter Description: DiffServ Domain Management.............................................................................. 1308
B.6.4.2 Parameter Description: DiffServ Domain Management_Create............................................................... 1314
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification..................................................... 1321
B.6.4.4 Parameter Description: Policy Management................................................................................................... 1323
B.6.4.5 Parameter Description: Port Policy..................................................................................................................... 1327
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration............................................... 1335
B.6.4.7 Parameter Description: Port Shaping Management_Creation.................................................................. 1347
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxvi

B.6.4.8 Parameter Description: Port WRED Policy_Create......................................................................................... 1349

B.6.4.9 Parameter Description: Service WRED Policy_Create................................................................................... 1350
B.6.4.10 Parameter Description: WRR Scheduling Policy_Create............................................................................ 1351
B.6.4.11 Parameter Description: V-UNI Egress Policy................................................................................................. 1352
B.6.4.12 Parameter Description: PW Policy.................................................................................................................... 1360
B.6.4.13 Parameter Description: QinQ Policy.................................................................................................................1368
B.6.5 Parameter Description: IP Packet Marking and Statistics Collection..........................................................1376
B.7 Parameters for Ethernet Services and Ethernet Features on the EoS/EoPDH Plane................................ 1381
B.7.1 Parameters for Ethernet Services............................................................................................................................ 1381
B.7.1.1 Parameter Description: Ethernet Line Service_Creation.............................................................................. 1381
B.7.1.2 Parameter Description: Ethernet Line Service_Creating QinQ-Based Ethernet Line Services........ 1386
B.7.1.3 Parameter Description: Ethernet Line Service................................................................................................. 1399
B.7.1.4 Parameter Description: Ethernet LAN Service_Creation of Ethernet LAN Services Based on IEEE
802.1d/802.1q Bridge............................................................................................................................................................. 1402
B.7.1.5 Parameter Description: Ethernet LAN Service_Creating IEEE 802.1ad Bridge-Based Ethernet LAN
Service......................................................................................................................................................................................... 1406
B.7.1.6 Parameter Description: Ethernet LAN Service.................................................................................................1411
B.7.1.7 Parameter Description: VLAN Filtering Table_Creation............................................................................... 1418
B.7.1.8 Parameter Description: Aging Time of MAC Address Table Entries........................................................ 1419
B.7.2 Parameters for Ethernet Protocols......................................................................................................................... 1420
B.7.2.1 Parameter Description: ERPS Management_Creation.................................................................................. 1420
B.7.2.2 Parameter Description: ERPS Management.....................................................................................................1424
B.7.2.3 Parameter Description: Spanning Tree_Protocol Enabling..........................................................................1434
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters........................................................................ 1435
B.7.2.5 Parameter Description: Spanning Tree_Port Parameters.............................................................................1437
B.7.2.6 Parameter Description: Spanning Tree_Bridge Running Information..................................................... 1438
B.7.2.7 Parameter Description: Spanning Tree_Port Running Information..........................................................1440
B.7.2.8 Parameter Description: Spanning Tree_Point-to-Point Attribute..............................................................1441
B.7.2.9 Parameter Description: IGMP Snooping Protocol_Enabling....................................................................... 1442
B.7.2.10 Parameter Description: IGMP Snooping Protocol_Creation of Static Multicast Table Entries..... 1443
B.7.2.11 Parameter Description: IGMP Snooping Protocol_Aging Time of Multicast Table Entries........... 1444
B.7.2.12 Parameter Description: Ethernet Link Aggregation_Creation of LAGs.................................................1444
B.7.2.13 Parameter Description: Ethernet Link Aggregation_Link Aggregation................................................ 1447
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point Service LPT........................ 1448
B.7.2.15 Parameter Description: LPT Management_Creation of Point-to-Multipoint Service LPT..............1449
B.7.2.16 Parameter Description: Port Mirroring_Creation......................................................................................... 1450
B.7.3 Parameters for the Ethernet OAM......................................................................................................................... 1452
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs............................................................ 1452
B.7.3.2 Parameter Description: Ethernet Service OAM_Creation of MAs.............................................................1452
B.7.3.3 Parameter Description: Ethernet Service OAM_Creation of MPs............................................................. 1453
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB..................................................................... 1455
B.7.3.5 Parameter Description: Ethernet Service OAM_Enabling LT...................................................................... 1456
B.7.3.6 Parameter Description: Ethernet Port OAM_OAM Parameter.................................................................. 1457
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxvii

B.7.3.7 Parameter Description: Ethernet Port OAM_OAM Error Frame Monitoring........................................ 1459
B.7.3.8 Parameter Description: Ethernet Port OAM_Remote OAM Parameter..................................................1460
B.7.4 QoS Parameters............................................................................................................................................................ 1461
B.7.4.1 Parameter Description: QoS Management_Creation of Flows..................................................................1461
B.7.4.2 Parameter Description: QoS Management_Creation of CAR.....................................................................1464
B.7.4.3 Parameter Description: QoS Management_Creation of CoS..................................................................... 1465
B.7.4.4 Parameter Description: QoS Management_Creation of CAR/CoS............................................................1467
B.7.4.5 Parameter Description: QoS Management_Shaping Management of Egress Queues..................... 1468
B.7.4.6 Parameter Description: QoS Management_Port Shaping........................................................................... 1470
B.7.5 Parameters for the Ports on Ethernet Boards.....................................................................................................1471
B.7.5.1 Parameter Description: Ethernet Port_External Port.................................................................................... 1471
B.7.5.2 Parameter Description: Ethernet Port_Internal Port..................................................................................... 1479
B.7.5.3 Parameter Description: Type Field of QinQ Frames......................................................................................1486
B.8 Parameters for MPLS/PWE3 Services........................................................................................................................ 1487
B.8.1 MPLS Tunnel Parameters........................................................................................................................................... 1487
B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels................................................................ 1487
B.8.1.2 Parameter Description: MPLS Basic Configuration_Global OAM Parameters..................................... 1489
B.8.1.3 Parameter Description: Unicast Tunnel Management_Static Tunnel......................................................1490
B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels............1496
B.8.1.5 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels............... 1501
B.8.1.6 Parameter Description: Unicast Tunnel Management_OAM Parameters............................................. 1506
B.8.1.7 Parameter Description: Unicast Tunnel Management_FDI.........................................................................1512
B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Ping.............................................................. 1513
B.8.1.9 Parameter Description: Unicast Tunnel Management_LSP Traceroute.................................................. 1516
B.8.1.10 Parameter Description: Unicast Tunnel Management_MEP Management........................................ 1519
B.8.1.11 Parameter Description: Unicast Tunnel Management_Creating Tunnel MIPs...................................1524
B.8.1.12 Parameter Description: Unicast Tunnel Management_Enabling an LB Test...................................... 1525
B.8.1.13 Parameter Description: PW Management_PW Management................................................................. 1528
B.8.1.14 Parameter Description: PW Management_MS-PW Creation...................................................................1534
B.8.1.15 Parameter Description: PW Management_PW OAM................................................................................. 1546
B.8.1.16 Parameter Description: PW Management_PW Ping...................................................................................1552
B.8.1.17 Parameter Description: PW Management_PW Traceroute.......................................................................1555
B.8.1.18 Parameter Description: PW Management_MEP Management...............................................................1558
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...................................................................1576
B.8.1.24 Parameter Description: PW FPS Protection Group_Creation................................................................... 1588
B.8.1.25 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation............... 1597
B.8.2 Parameter Description: VPLS Management........................................................................................................ 1604
B.8.3 CES Parameters............................................................................................................................................................. 1605
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxviii

B.8.3.1 Parameter Description: CES Service Management........................................................................................ 1605

B.8.3.2 Parameter Description: CES Service Management_Creation..................................................................... 1616
B.8.4 ATM Parameters........................................................................................................................................................... 1636
B.8.4.1 Parameter Description: ATM IMA Management_IMA Group Management........................................ 1636
B.8.4.2 Parameter Description: ATM IMA Management_Bound Path Configuration...................................... 1642
B.8.4.3 Parameter Description: ATM IMA Management_IMA Group Status.......................................................1644
B.8.4.4 Parameter Description: ATM IMA Management_IMA Link Status...........................................................1644
B.8.4.5 Parameter Description: ATM IMA Management_ATM Interface Management..................................1645
B.8.4.6 Parameter Description: Configuration of ATM Service Class Mapping Table...................................... 1648
B.8.4.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation................... 1649
B.8.4.8 Parameter Description: ATM Policy Management........................................................................................ 1651
B.8.4.9 Parameter Description: ATM Policy Management_Creation......................................................................1655
B.8.4.10 Parameter Description: ATM Service Management....................................................................................1660
B.8.4.11 Parameter Description: ATM Service Management_Creation................................................................. 1672
B.8.4.12 Parameter Description: ATM OAM Management_Segment and End Attributes............................. 1686
B.8.4.13 Parameter Description: ATM OAM Management_CC Activation Status............................................. 1690
B.8.4.14 Parameter Description: ATM OAM Management_Remote End Loopback Status........................... 1694
B.8.4.15 Parameter Description: ATM OAM Management_LLID............................................................................ 1696
B.8.4.16 Parameter Description: ATM OAM_ATM Cell Insertion Status...............................................................1697
B.8.5 MP Group Parameters................................................................................................................................................ 1698
B.8.5.1 Parameter Description: MP Group Management_Creation........................................................................ 1698
B.8.5.2 Parameter Description: MP Group Management_Basic Attributes..........................................................1702
B.9 Clock Parameters............................................................................................................................................................. 1706
B.9.1 Parameter Description: Frequency Selection Mode.......................................................................................... 1706
B.9.2 Physical Clock Parameters......................................................................................................................................... 1707
B.9.2.1 Parameter Description: Clock Source Priority Table......................................................................................1707
B.9.2.2 Parameter Description: Priority Table for the PLL Clock Source of the External Clock Port...........1710
B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet......................................................................1712
B.9.2.4 Parameter Description: Clock Subnet Setting_Clock Quality..................................................................... 1715
B.9.2.5 Parameter Description: Clock Subset Setting_SSM Output Control........................................................ 1718
B.9.2.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status................................................1719
B.9.2.7 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters.................. 1721
B.9.2.8 Parameter Description: Clock Source Switching_Clock Source Switching............................................. 1723
B.9.2.9 Parameter Description: Clock Source Switching_Clock Source Switching Conditions....................... 1724
B.9.2.10 Parameter Description: Output Phase-Locked Source of the External Clock Source......................1726
B.9.2.11 Parameter Description: Clock Synchronization Status............................................................................... 1729
B.9.3 CES ACR Clock Parameters........................................................................................................................................1732
B.9.3.1 Parameter Description: ACR Clock Source........................................................................................................1732
B.9.3.2 Parameter Description: Clock Domain............................................................................................................... 1733
B.9.3.3 Parameter Description: Clock Domain_Creation............................................................................................ 1733
B.9.4 PTP Clock Parameters................................................................................................................................................. 1734
B.9.4.1 Parameter Description: Clock Synchronization Attribute............................................................................ 1734
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxix

B.9.4.2 Parameter Description: Clock Synchronization Attribute_Creation of PTP Clock Ports.................... 1748
B.9.4.3 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet....................................................1748
B.9.4.4 Parameter Description: Setting of a PTP Clock Subnet_BMC.................................................................... 1749
B.9.4.5 Parameter Description: External Time Port_Basic Attributes..................................................................... 1751
B.9.4.6 Parameter Description: External Time Port_BMC.......................................................................................... 1753
B.9.4.7 Parameter Description: External Time Port_Cable Transmission Distance............................................1754
B.9.5 Parameter Description: Auxiliary Ports................................................................................................................. 1756
B.10 Parameters for the Orderwire and Auxiliary Interfaces................................................................................... 1757
B.10.1 Parameter Description: Orderwire_General...................................................................................................... 1757
B.10.2 Parameter Description: Orderwire_Advanced.................................................................................................. 1760
B.10.3 Parameter Description: Orderwire_F1 Data Port............................................................................................ 1760
B.10.4 Parameter Description: Orderwire_Broadcast Data Port.............................................................................. 1761
B.10.5 Parameter Description: Environment Monitoring Interface........................................................................ 1762
C Glossary...............................................................................................................................1765
Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xxx

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

Features
This topic provides hyperlinks to configuration procedures 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
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 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. 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)
solution in multiple OSPF areas on a transmission network that consists of OptiX
1.13 Configuration Example (IP DCN Solution Using OSPF Multi-process)
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. In this 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

Configuration Flowchart
Figure 1-1 Flowchart for configuring the HWECC solution
Configuration Procedure
Table 1-1 Procedure for configuring the HWECC solution
Step Operation Description
1 Settin A.3.1.9 Required.

g Changing the
basic NE ID
NE
attrib
utes

A.3.7.1 Required.
Setting NE IP
Communicati
on
Parameters
2 A.3.7.2 Configuring Required.

DCCs NOTE
If a static route exists, the value of Protocol stack
type must match the protocol type of the static
route.
3 Confi A.3.7.4 Perform this operation if the VLAN ID and

gurin Configuring bandwidth of the inband DCN planned for
g the the VLAN ID OptiX equipment do not take their default
inban and values. (The default VLAN ID is 4094 and the
d Bandwidth default bandwidth is 512 kbit/s.)
DCN Used by an NOTE
Inband DCN 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 Ethernet service port.
Control
A.3.7.5 Required when priorities need to be specified

Configuring for DCN packets.
the Priority
of Inband
DCN Packets
4 A.3.7.8 Configuring Required for the NEs that are connected

Extended ECC through the Ethernet network management
Communication port or NE cascading port.
5 A.3.7.3 Configuring When the DCN route protection function is

DCC Transparent affected due to the division of a DCN subnet,
Transmission 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 This operation applies only to a gateway NE.

ECC Routes NOTE
You can check the route status by A.3.7.22 Verifying
Connectivity of an ECC Network, in addition to
querying ECC routes.

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

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

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

Creating NEs operation to create NEs on the centralized
by Using the NMS in other cases.
Search NOTE
Creating NEs
by Using the
Manual
Method
(Web LCT)
1.2 Configuration Procedure (IP DCN Solution)

Configuring the IP DCN solution includes configuring communication data at the

Figure 1-2 Flowchart for configuring the IP DCN solution

Table 1-2 Procedure for configuring the IP DCN solution

1 Settin A.3.1.9 Required.

g Changing the
basic NE ID
NE
attrib A.3.7.1 Required.
utes Setting NE IP
Communicati
on
Parameters

DCCs NOTE
If a static route exists, the value of Protocol stack
type must match the protocol type of the static
route.
3 Confi A.3.7.4 Perform this operation if the VLAN ID and

gurin Configuring bandwidth of the inband DCN planned for
g the the VLAN ID OptiX equipment do not take their default
inban and values. (The default VLAN ID is 4094 and the
d Bandwidth default bandwidth is 512 kbit/s.)
DCN Used by an NOTE
Inband DCN You can set the VLAN ID of the inband DCN based
on NEs or ports.
A.3.7.6 Required.
Configuring NOTE
Inband DCN The ATN-compatible mode can be enabled by port.
Ports 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 Required when a gateway NE needs to

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

Configuring specified for DCN packets.
the Priority
of Inband
DCN Packets
4 Confi A.3.7.11 Required.

gurin Setting OSPF
g IP Protocol
route Parameters
s

A.3.7.15 Optional.
Configuring
the OSPF
Authenticati
on Type
A.3.7.9 Optional.
Creating a
Static IP
Route
Enabling the If the third-party NMS and the third-party

proxy 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 Confi Changing the Required for an ABR.

gurin network
g segment of
multi the
-area backbone
OSPF area for an
ABR
A.3.7.12 When multi-area OSPF is deployed on a

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

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

Creating a configure manual route aggregation on the
Manual ABR to reduce the number of routes.
Route
Aggregation
Group

6 A.3.7.19 Querying IP ● The gateway NE has a route to the NMS.

Routes ● The gateway NE has routes to non-gateway
NEs and non-gateway NEs have routes to
the gateway NE.
● 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 Optional.

Basic Parameters for Required when the OptiX RTN 950 is
the NMS Port 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.

on Reporting
the
centr A.3.1.3 It is recommended that you perform this
alized Creating NEs operation to add one or more NEs to a large
NMS by Using the existing network on the centralized NMS.
Manual NOTE
Creating NEs
by Using the
Search
Method
(Web LCT)

Search NOTE
Creating NEs
by Using the
Manual
Method
(Web LCT)

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.
NOTE
The OptiX RTN 905 s does not support this configuration.
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

Routes normal cases:
● There is an ECC route between the GNE and
each of its managed non-GNEs.
6 Creati Enabling the Required when an NE needs to be

ng NE automatically created on the NCE after it
NEs automatic communicates with the NCE.
on reporting
the
centr
alized
NMS

A.3.1.3 It is recommended that you create NEs on the

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

Creating NEs NOTE
by Using the If NE Automatic Reporting is enabled, an NE is
Search automatically created on the NCE after it
Method communicates with the NCE.
(NCE) 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.
NOTE

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 Perform this operation to set up the point-
of Point-to-Point to-point cross-connection between the E1
Services port connected to 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:
● 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
● 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
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)

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

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

NE ID ● Set ID to be the NE ID according to the
DCN plan.
● 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 ● Set IP Address and Subnet Mask according
Parameters to the network plan.
● 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 A.3.7.2 Required.

the Configuring ● For DCC channels between L2 DCN subnets,
outba DCCs set Enabled/Disabled to Enabled and set
nd Protocol Type to TCP/IP.
DCN
● For DCC channels within an L2 DCN subnet,
set Enabled/Disabled to Enabled and set
Protocol Type to L2DCN.
Disabling Required if the IF board uses DCC channels as

inband DCN L2 DCN channels.
channels of a In the IF tab, set Enabled Status to Disabled
microwave for IF ports whose DCC channels are planned
port to be enabled.
4 Using A.3.7.4 Required.

the Configuring ● If the default VLAN ID of the inband DCN
inban the VLAN ID conflicts with the VLAN ID used by the
d and service, you can manually modify Ethernet
DCN Bandwidth Board VLAN ID of the inband DCN. The
Used by an same VLAN ID is used for inband DCN
Inband DCN communication over the entire network.
● 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.

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

DCC channels as L2 DCN channels.
channels For IF ports that are planned to use inband
DCN channels, set Enabled/Disabled to
Disabled.
5 Setting the VLAN ID If the DCN packets from Huawei NMS carry a
for Huawei NMS 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 Optional.

protocol If static IP routes are planned to be used
between L2 DCN subnets, it is recommended
that you disable the OSPF protocol.
7 A.3.7.9 Creating a Configure static IP routes if communication

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

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

Basic Parameters for external equipment through its network
the NMS Port management port or NE cascading port and
the working mode of the external equipment is
not auto-negotiation.

on Reporting
the
centr

alized A.3.1.3 It is recommended that you perform this

NMS Creating NEs operation to add one or more NEs to a large
by Using the existing network on the centralized NMS.
Manual NOTE
Creating NEs
by Using the
Search
Method
(Web LCT)

Search NOTE
Creating NEs
by Using the
Manual
Method
(Web LCT)
11 A.3.8.3 Changing the If the third-party DCN packets are

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

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

services for transparently transmitted as E-LAN services on
transparently the packet switching plane.
transmitting third-arty ● Configure E-LAN service ports based on the
DCN packets 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).
● The third-party DCN packets must carry
VLAN IDs and be received through NMS
ports (logical ports: NMS-1).
● In this scenario, NMS ports can only
function as UNIs of E-LAN services.
NOTE
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 ● 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.
● 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.
● Based on actual requirements, set Report
MW Performance Trap, Report IP
Performance Trap, and Report Alarm Trap
to Report.
● It is recommended that Port take the
default value.
● 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 Required.

function of Ethernet ports
A.4.5.1 Configuring the Optional.

Transmit Parameters for
LLDP Packets

NOTE
● When RTN equipment is interconnected with CX/ATN equipment and LLDP needs to be
used, set VLAN ID to 0.
● In addition to Ethernet ports, IF ports on the OptiX RTN 905/RTN 950 (housing CSHU/
CSHUA/CSHUF)/RTN 950A (housing SLF2 CSHO/CSHOF)/RTN 980 (housing CSHNU)
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
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)
1 A.4.4.1 Enabling/ Required.

Disabling the
RADIUS Function

2 A.4.4.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.

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

a 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.4.1 Enabling/ Required.

Disabling the NOTE
RADIUS Function Disable the proxy server function for NEs that use
the proxy NAS mode.
2 A.4.4.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 is
applicable when you need to enable Accounting
after Authentication is enabled.
A.4.4.3 Configuring Required.

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 OptiX RTN 950 (housing CST/CSH/CSHUF)/OptiX RTN 980/RTN 905 s (housing CSHN),
and OptiX RTN 905 1C/1A/2A (housing CSHN) do not support NE anti-theft.

Table 1-10 Configuring NE anti-theft

1 A.3.1.16 Configuring Required. Anti-theft policies consist of

NE Anti-Theft configuration control and service control
policies.
● Configuration control policies take effect
immediately when the device becomes
unreachable to the NMS. That is, all
configuration commands are restricted.
● 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.
● 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.
● The centralized NMS can manage all the OptiX equipment on the network.

Figure 1-7 Networking diagram of HWECC
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
● 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.
● Select the central node NE101 of the optical transmission service and the
central node NE202 of the radio transmission service as gateway NEs.
● 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.
● Allocate IDs and IP addresses for all the NEs based on network conditions.
● 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.
● 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
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
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 Enabled Enabled

Disabled
Channel - D1 (default value D1 (default value

of an IP port in of an IP port in
PDH radio mode PDH radio mode
whose capacity is whose capacity is
lower than 16 lower than 16
E1s) E1s)
D1-D3 (default D1-D3 (default
values of other values of other
line ports) line 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 Related Related

Port parameter values parameter values parameter values
of west ports on of west ports on of west ports on
the ring the ring the ring

Parameter Value
Transparent D1 D2 D3
Transmission of
Overhead Bytes
at Source Port
Sink Timeslot/ Related Related Related

Port parameter values parameter values parameter values
of east ports on of east ports on of east ports on
the ring the ring 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.
● The routes to all the OptiX optical transmission NEs can be queried on NE101
while the routes to NE201 and NE202 cannot be queried.
● 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 (NCE) 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)
solution in a single OSPF area on a transmission network that consists of OptiX

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 #EN-US_CONCEPT_0188442160/fig6912175184818, the OptiX radio
transmission equipment and the third-party radio transmission equipment
construct a radio transmission network. On the radio transmission network:
● The third-party radio equipment is located at the edge and the OptiX radio
equipment is located in the center.
● 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.
● 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.
● 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)

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
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:
● The IP address of NE1 (connected to the external DCN) meets the
requirements of the external DCN.
● The IP addresses of the NEs that are connected through Ethernet network
management ports are on the same network segment.
Route Information
● 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.
● 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 9 9 9 9
Extended ID


Parameter Value
NE1 NE3 NE4 NE6
IP Address 10.0.0.1 129.9.0.3 129.9.0.4 130.9.0.6
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 whose whose whose
capacity is capacity is capacity is capacity is
lower than 16 lower than 16 lower than 16 lower than 16
E1s) E1s) E1s) E1s)
D1-D3 D1-D3 D1-D3 D1-D3
(default (default (default (default
values of values of values of values of
other IF other IF other IF other line
ports) ports) ports) ports)
Protocol TCP/IP TCP/IP TCP/IP TCP/IP

Type

Step 4 Set OSPF parameters.
Parameter Value
NE1 NE3 NE4 NE6
OSPF Status Enabled Enabled Enabled Enabled
Static route Enabled Disabled Disabled Enabled
LAN Disabled Enabled Enabled Enabled

Interface
Step 5 Create static IP routes.
Parameter Value
NE1 NE6
Destination Address 11.0.0.100 130.9.0.7

Parameter Value
NE1 NE6
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:
● 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
● Route to the network segment 10.0.0.0, with the gateway whose IP address is
10.0.0.1
● Route to the NE IP address 11.0.0.100, with the gateway whose IP address is
10.0.0.200
For NE6:
● 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
● 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
130.9.0.7

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:
● 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.
● 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.
● 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)
solution in multiple OSPF areas on a transmission network that consists of OptiX

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:
● 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.
● The third-party radio NEs support the OSPF protocol and can communicate
the OSPF protocol with OptiX Radio NEs.
● 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.
● The IP addresses of the Huawei NMS and the third-party NMS are on the
10.2.0.0/16 network segment.
● 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)

This section describes the procedure for configuring OptiX radio transmission
equipment and third-party equipment in different OSPF areas.
Data Preparation
OSPF Area and NE ID/IP Address Information:

● 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.
● 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).
● 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.
● 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.
● Automatic route aggregation is enabled for Area 1 and Area 2.
Route Information:
● 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:
● 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.
● On the edge network, NEs use DCC channels for DCN communication.
● 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
Paramet Value
er
NE1 NE2 NE3 NE4 NE5 NE6
New ID 1 2 3 4 5 6
New 9 9 9 9 9 9
Extende
d ID

Paramet Value
er
IP 129.9.0.1 129.9.0.2 129.9.0.3 129.9.0.4 129.10.0. 129.10.0.

Address 5 6
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/ Enabled Enabled Enabled

Disabled
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(k 1000 1000 1000 1000

bit/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
Enable Enabled Enabled Enabled Disable Enabled Disable Disable

d d d d
Status
Protoco IP IP IP - IP - -
l 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 - - - - - - -
Addres
s
Subnet - - - - - - -
Mask
The values for the related OSPF parameters of each NE are provided as follows.
Paramet Value
er
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
Static Enabled Disabled Disabled Disabled Disabled Disabled

route

Paramet Value
er
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-

NMS Party 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:
● Routes to the NE IP addresses 129.9.0.2, 129.9.0.3, and 129.9.0.4
● Route to the network segment 129.10.0.0, with the gateway whose IP address
is 129.9.0.4
is 129.9.0.2
129.9.0.100
129.9.0.100
For NE4:
● Routes to the NE IP addresses 129.9.0.1, 129.9.0.2, and 129.9.0.3
is 129.9.0.5
is 129.9.0.3
129.9.0.1
129.9.0.1
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:
● 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.
● 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.
1.13 Configuration Example (IP DCN Solution Using

OSPF Multi-process)
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:
● The GE packet ring consisting of OptiX radio transmission equipment is
connected to the microwave network as an aggregation network.
● 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.
● 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)

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

OSPF areas and NE IDs/IP addresses:
● 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.
● 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:
● 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:
● GE packet equipment uses inband DCN. The management VLAN ID takes the
default value 4094, and the bandwidth is set to 1000 kbit/s.
● 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


This table provides the values of NE communication parameters.
Parameter Value
NE1
Gateway IP Address 0.0.0.0
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 (NCE).
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

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
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 (NCE).

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

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 See the following figure. -

mode
DCC Channel D1-D3 -

Figure 1-18 Service plan of the DCC transmission through the external clock port
solution
NOTE
● 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.
● If NE1 is an OptiX RTN 905 NE, fiber/cable connections to NE1 are not required.
● 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. 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.

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:
● The OptiX RTN 900 NEs are managed by the Huawei NMS. The third-party
radio equipment is managed by the third-party NMS.
● 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

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
NOTE
● Radio links comprised of the OptiX RTN 900 NEs use DCC channels to transmit DCN
information.
● 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 (NCE).
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
● To ensure the normal communication between Huawei NMS and Huawei NEs,
configure static routes for related routers.
● 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. In this 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:
● 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.
● Each vendor's subnet contains several hundreds of NEs.
● Microwave NEs from vendors A and B do not support any dynamic routing
protocol but support a Layer 2 data communication network (L2 DCN).
● 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

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
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.
Transmissio DCN packets from the OptiX RTN equipment are transmitted
n channel through the inband DCN channels on IF ports. The VLAN ID of an
of Huawei inband DCN channel is 4094, and the bandwidth is 2560 kbit/s
DCN because there are many NEs.
packets
Transparent The OptiX RTN equipment needs to be configured with E-LAN

transmissio services for transparently transmitting DCN packets from vendor
n method A and vendor B. Because all of the equipment works at Layer 2,
for third- the E-LAN service port type can be set to C-Aware.
party DCN
packets
DCN packet When OptiX RTN equipment and Vendor A's equipment or
communica Vendor B's equipment are co-sited, they are interconnected
tion through NMS ports to transparently transmit DCN packets.

Item Description
RSTP ● The OptiX RTN equipment forms a ring network, so RSTP must
be enabled on the control plane to prevent DCN loops.
● 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 NCE.

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

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 ● Read/Write The SNMP version, read/

information Permissions: Enabled write permissions, and
● Read/Write community name
Community Name: planned for an NE must
rtn900_read_01/ be the same as those of
rtn900_write_01 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)

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 5-EG4-3 -
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:
● The DCN on the equipment side uses the HWECC solution, and IP routes have
been configured between NE1 and the RADIUS server.
● 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.
● 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

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 ● 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.
● NE2 is configured as
the proxy RADIUS
server and its NE ID is
NE1.
RADIUS function The RADIUS client and -

enabling 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: NEs using the NAS mode

Abcd1234 need to be configured
Proxy server: - 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 NCE manages a hop of microwave link. You can use
the NCE 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
This topic provides hyperlinks to configuration processes and configuration

examples of 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
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+/Super EPLA)
The core of configuring PLA/EPLA/EPLA+ is to configure a PLA/EPLA/EPLA+/Super
EPLA protection group.
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 each end of the link.
2.10 Configuration Example (XPIC on Cascaded NEs)

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

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
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
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
NOTE
Table 2-1 Configuring microwave links with 1+1 HSB on an NE

1 A.8.10.7 Changing The IF ports on both ends of a microwave link

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

the 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
Protection be reported, it is advisable to set Alarm
Report Mode to Only protection group
alarms.
5 Confi A.9.3.1 Required when a hop of 1+1 Integrated IP

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

1 A.8.10.7 Changing The IF ports on both ends of a microwave

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

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

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

1+1 Protection on each of the main and standby NEs.
Group Set parameters as follows:
● Set Working Mode as planned.
● Set Working/Protection Unit Type to
Working Unit for the main NEs and to
Protection Unit for the standby NEs.
● It is recommended that you retain the
default value Revertive for Revertive
Mode.
● WTR Time(s) can be set only when
Revertive Mode is set to Revertive.
● It is recommended that you set Enable
Reverse Switching to Enable.
● 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:
● The modem chips on the main and standby
NEs work in different modes.
● No feature that conflicts with 1+1 protection,
such as physical link aggregation (PLA), has
been configured.
● The cascade cables between the main and
standby OptiX RTN 905 1E NEs are properly
connected.

Single-Hop Radio In a 1+1 HSB/SD protection group, the IF
Link 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 If only protection group alarms are expected
1+1 Protection to 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/RTN 905 s 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

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

Changing the the planned value for IF Service Type is not the default
IF Service value Hybrid (Native E1+ETH).
Type
3 A.5.1 Required. To configure Integrated IP microwave links

Configuring a with N+1 protection, you need to configure the IF and
Single-Hop RF information for each working link and the protection
Radio Link link.
NOTE
Configure the same IF information for each working link and
the protection link.
4 A.5.4 Required.
Creating 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:
● 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.
● 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
NOTE
Table 2-4 Configuring XPIC-enabled links on an NE

1 A.8.10.7 Changing the Optional.

Running Mode of an The IF ports on both ends of a microwave
IF Port link must work in the same mode.
2 A.8.10.6 Changing the Perform this step to change the IF service

IF Service Type type when the planned value for IF

Single-Hop Radio
Link
4 A.5.2 Creating an IF Required when two XPIC workgroups need

1+1 Protection Group to form two 1+1 protection groups.
5 A.5.4 Creating an N+1 Required if members in an XPIC

Protection Group workgroup need to be configured in an N
+1 protection group.

6 Configurin A.5.10 Required when XPIC-enabled Integrated IP

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

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

1 A.8.10.7 Changing the The IF ports on both ends of a microwave

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

IF Service Type type when the planned value for IF

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

PLA/EPLA/EPLA+/ microwave uses PLA/EPLA.
Super 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,

Configurin and other IF and RF information.
g a Single-
Hop Radio
Link
2 A.8.10.3 Optional.
Setting ● You can specify the maximum number of E1s that
Advanced can be transmitted in intermediate modulation
AM schemes, by setting the advanced attributes
Attributes correspondingly.
● Generally, it is recommended that you use the
default values.
● 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 Only ISX2 boards support the AM Booster function.
or
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:
● If a cross-connection is configured for a point-to-point service, the E1 priority is
configured when the cross-connection is created.
● If a cross-connection is configured for an SNCP service, the E1 priority is modified after
the cross-connection is created.
● 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 ● If the ATPC function is required, select ATPC.
Single-Hop
Radio Link ● Do not select ATPC during site commissioning.
● It is recommended that you set ATPC Upper
Threshold(dBm) to the central value plus 10 dB.
● It is recommended that you set ATPC Lower
Threshold(dBm) to the central value minus 10 dB.
● Set ATPC Automatic Threshold Enable Status to
Disabled by A.8.10.2 Configuring ATPC Attributes.
2 A.8.11.3 To set the maximum transmit power that is supported

Setting ODU by the ATPC adjustment function, you need to set
Power Maximum Transmit Power(dBm) according to the
Attributes 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+/Super

EPLA)
The core of configuring PLA/EPLA/EPLA+ is to configure a PLA/EPLA/EPLA+/Super
EPLA protection group.
NOTE
● The OptiX RTN 905 s does not support this configuration.

● The OptiX 910A, OptiX RTN 950A housing CSHO, and OptiX RTN 950 (housing CSHU/
CSHUA) support EPLA+ only when working with ISV3/ISM6.
● Only OptiX RTN 980 housing CSHN boards and OptiX RTN 950 housing CSH boards do
not support EPLA.
● When PLA/EPLA is implemented by stacking NEs, a PLA/EPLA group must be created on
both the master and slave NEs.
● For other PLA/EPLA configuration requirements, see Feature Dependencies and
Limitations.

Table 2-8 Flow for configuring PLA/EPLA/EPLA+/Super EPLA
1 A.5.10 Required.
Creating a
PLA/EPLA/
EPLA+/Super
EPLA Group
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.

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
2.7.2 Configuration Procedure1

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 ● Slot restrictions:

microwave links in a 1+1 details. Single-polarized – For OptiX RTN 905
HSB protection group antennas are used on 2E, it is
this network. recommended that
the IF unit in slot 3
be 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.
● 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.
● It is recommended
that you set Alarm
Report Mode to Only
protection group
alarms.
that you set Enable
Reverse Switching to
Enabled.

Item Value in this Example Planning Guideline
Hybrid/AM attribute Table 2-9 provides the ● Ensure that the air
information details. The Hybrid interface bandwidth
microwave capacity and for a microwave link
the AM function are in AM guaranteed
available only if the capacity mode is
corresponding license higher than the total
files are loaded. bandwidth of high-
priority services, and
link availability meets
availability
requirements of high-
priority services.
● Ensure that the air
interface bandwidth
for a microwave link
in AM full capacity
mode is more than
the total bandwidth
of all services, and
link availability meets
the availability
requirements of low-
priority services.
● When the E1 priority
function is enabled,
E1 service bandwidth
in AM full capacity
mode ≤ Service
bandwidth in AM full
capacity mode –
Service bandwidth in
AM guaranteed
capacity mode + E1
service bandwidth in
AM guaranteed
capacity mode.
Power information Table 2-10 provides the -

details.
NOTE
In the case of microwave 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 microwave links in a 1+1 HSB protection
group
Table 2-9 Hybrid/AM attribute information
Parameter NE1 NE2
3-ISV3 3-ISV3
AM Selected Selected
Capacity-assured QPSK QPSK

Modulation Scheme
Modulation Mode of the 128QAM 128QAM

Guarantee 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 microwave link for a 1+1 HSB protection group.
Step 2 Modify the IF 1+1 protection parameters.
----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

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


Data Preparation
Item Value in This Example Planning Guideline
1+1 HSB protection Figure 2-4 provides the ● If 1+1 HSB works in
information details. Single-polarized revertive mode, set
antennas are used on the wait to restore
this network. (WTR) time to a value
between 5 and 12
recommended.
that you set Alarm
Report Mode to Only
protection group
alarms.
that you set Enable
Reverse Switching to
Enabled.

Hybrid/AM attribute Table 2-11 provides the ● Ensure that the air
information details. The Hybrid radio interface bandwidth
capacity and the AM for a radio link in AM
function are available guaranteed capacity
only if the corresponding mode is higher than
license files are loaded. 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
higher than the total
bandwidth of all
services, and link
availability meets the
availability
requirement of low-
priority services.
● When the E1 priority
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

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(dB
m)

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 each end of the link.

This topic describes the networking information about the NEs.
The service requirements between two sets of OptiX RTN 980 are as follows:

● The radio link needs to transmit 32xE1 services and 400 Mbit/s Ethernet
services at the same time.
● 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.
● Two XPIC workgroups form two 1+1 HSB protection groups and load-sharing
LAGs are configured.
● As shown in Figure 2-6, NE1 and NE2 have the same board configurations.

Figure 2-6 Board configuration


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


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.

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

The service requirements on a hop of radio link are as follows:

● The radio link needs to transmit 32xE1 services and 400 Mbit/s Ethernet
services at the same time.
● 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.


Data Preparation
XPIC work group Figure 2-9 provides the ● XPIC must be enabled
configurations details. if CCDP is enabled.
● 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

Procedure
Step 1 Configure an XPIC work group that is implemented through cascading.
----End
2.11 Configuration Example (N+1 Protection)

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

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:
● The Integrated IP microwave link needs to transmit 32xE1 services and 300
Mbit/s Ethernet services at the same time.
● The link that is configured with the N+1 (N=2) protection.
● The AM function needs to be enabled.
● As shown in Figure 2-11, NE1 and NE2 have the same board configurations.
This example uses the ISU2 board.

Figure 2-11 Board configuration


Data Preparation
Basic information about Figure 2-12 provides the ● 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.
● 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 Table 2-17 provides the ● It is recommended

+1 (N=2) protection details. that the slot ID for
the IF board of the
protection channel be
greater than that of
the working channel.
that you set the wait
to restore time to 10
minutes.
that you set SD as a
switching condition.
Figure 2-12 Basic information about radio links in a N+1 protection group
Parameter Link 1 Link 2 Link 3

(working link 1) (protection link) (working link 2)
IF Service Type Hybrid (Naive Hybrid (Naive Hybrid (Naive

E1+ETH) E1+ETH) 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 QPSK QPSK QPSK

capacity mode


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

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-ISV3 3-ISV3

5-ISV3 5-ISV3
Work Unit 6-ISV3 6-ISV3
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.

----End
2.12 Configuration Example (ATPC)

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

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.



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

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

Figure 2-14 ATPC configuration
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.

----End
2.13 Configuration Example (AM)

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

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



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

information details. for 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.
● 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
higher than the
total bandwidth of
all services, and
link availability
meets the
availability
requirement of
low-priority
services.
● 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
Procedure
Step 1 Configure AM information for a link on Microwave Link Configuration.

----End
2.14 Configuration Example (PLA on an NE)

In this example, PLA protection is configured for a 2+0 microwave link, with one

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.


Data Preparation
PLA configurations Figure 2-18 provides the ● 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.
● Member links in a
PLA group must use
the same channel
spacing.
● The IF services
transmitted by the
members in a PLA
group must be of the
same type.
● The master and slave
ports in a PLA group
must use the same
Ethernet header
compression mode.
● 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
members in a PLA group
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.
Procedure
Step 1 Create a PLA group.

----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.


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

details. PLA group must use
the same channel
spacing.
● The master and slave
ports in a PLA group
must use the same
Ethernet header
compression mode.
● PLA parameter
and transmit ends.
Minimum Active Links 1 When PLA coexists with

members in a PLA group
are faulty. To trigger
Ethernet protection
switching by some failed
members, set Minimum
Active Links to 1 plus
the maximum number of
remaining activated
switching.

Context
In the networking shown in Figure 2-20, when the RTN 905 2F is used to
implement cascading PLA:
● If NE 1 is a gateway NE, configure PLA on NEs in the following sequence: NE
4, NE 3, NE 2, NE 1.
● If NE 2 is a gateway NE, configure PLA on NEs in the following sequence: NE
4, NE 3, NE 1, NE 2.
Procedure
Step 1 A.5.10 Creating a PLA/EPLA/EPLA+/Super EPLA Group.
----End

2.16 Configuration Example (EPLA)

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

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.


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

details. is supported at both
ends of a radio link.
● The IF services
transmitted by the
members in an EPLA
group must be of the
same type.
● EPLA parameter
and transmit ends.
Minimum Active Links 1 When EPLA coexists with

members in an EPLA
group are faulty. To
trigger Ethernet
protection switching by
some failed members,
set Minimum Active
Links to 1 plus the
maximum number of
remaining activated
switching.
EPLA CC Enabled Enable the EPLA CC

function as required to
check link reliability.

Context
In the networking shown in Figure 2-23, when the RTN 905 2F is used to
implement cascading EPLA:
● If NE 1 is a gateway NE, configure EPLA on NEs in the following sequence: NE
4, NE 3, NE 2, NE 1.
● If NE 2 is a gateway NE, configure EPLA on NEs in the following sequence: NE
4, NE 3, NE 1, NE 2.
Figure 2-23 Networking diagram of cascading EPLA
Procedure
Step 1 Create an EPLA group.

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.
Step 2 (Optional) Enabled EPLA CC.
----End

Feature Configuration Guide 3 Configuring SDH Protection Features
3 Configuring SDH Protection Features

examples of 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.
NOTE

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

Connections of Point-to-Point point-to-point service.
Services The parameters need to be set
according to the service planning.
NOTE
Under 1+1 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.
NOTE
Table 3-2 Procedure for configuring the SNCP service on an add/drop NE

1 A.7.2 Creating Cross- Required.

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

Automatic Switching of SNCP service.
SNCP Services
3 A.7.3 Modifying the Required when the working source,

Priorities of E1 Services protection 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- The parameters need to be set
Point Services according to the service planning.
2 A.7.4 Inserting E1_AIS Optional when the IFU2/IFX2/ISX2/ISU2/

upon a 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 the 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 the service
planning.
2 Configuring the cross- A.7.1 Creating the Required when the

connections of TDM Cross-Connections of service is a point-to-
servicesa Point-to-Point point service.
Services You need to set the
parameters according
to the service
planning.
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
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:
● 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.
● NE11 transmits the services in the first 16 E1s of the STM-1 to NE12.
● NE11 is an OptiX RTN 980.

Figure 3-1 Networking diagram of the linear MSP

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 non-
revertive mode or the
1:N dual-ended revertive
mode as required.
● 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.
● In 1:N dual-ended
revertive mode, extra
services can be
transmitted.

Switching Mode Single-Ended Switching 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
recommended.
SD Switching Enabled (default value) It is recommended that

you set SD as a
NOTE
Unless otherwise specified,
retain the default value for
SD Switching.
Protocol Type New Protocol (default The MSP protocols used

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

950/950A/980, it is
West Protection Unit 16-SL4D-2 recommended that 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.
Step 2 Create cross-connections for point-to-point services.
The following table provides parameter values for NE11.
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

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


Data Preparation
Planning Service On an optical ring —

Timeslots 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)
● 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.
● In the case of a new
ring network, it is
recommended that
you 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.
● 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

WTR time (s) 600 Set the wait to restore

(WTR) time to a value
between 5 minutes to 12
recommended.
Protocol type New protocol The MSP protocols used

on a ring network must
be consistent. It is
recommended that you
adopt the new MSP
protocol.
NOTE
Protocol Type.
West line 1 16-SL4D-1 The east and west ports

of a two-fiber
East line 1 16-SL4D-2 bidirectional MSP 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.
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

examples of 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)
ring network is creating Ethernet ring protection (ERP) instances. For a multi-ring
network, create ERPS V2-based instances.
4.3 Configuration Process (ERPS Multi-Instance)
The key to configuring ERPS is creating an ERPS protection instance. Multiple
services on the same ring network can be protected using ERPS multi-instance.
Both ERPS V1 and ERPS V2 support ERPS multi-instance. ERPS V1 is used as an
example.
4.4 Configuration Procedure (SEP)
The core of the SEP is to create a new SEP protection instance.
4.5 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.6 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.7 Configuration Procedure (LPT)
The configuration procedure for LPT contains only one configuration task.
4.8 Configuration Process (QoS/HQoS)
Configure QoS/HQoS policies, and then apply them to QoS objects.
4.9 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.10 Configuration Procedure (Ethernet Port OAM)

When you use the Ethernet port OAM function, you can perform appropriate OAM
4.11 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.12 Configuration Procedure (IGMP Snooping V2)
When the IGMP Snooping V2 protocol is applied, you can set the static router port
and the static routing member, except for the IGMP Snooping parameters.
The IGMP packet is available in three versions: V1, V2, and V3. V3 is compatible
with V2. Compared with V2, V3 supports to choose the source.
4.14 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.15 Configuration Example (ERPS on a Multi-ring Network)
protection switching (ERPS) for a multi-ring network based on network conditions.
4.16 Configuration Example (ERPS Multi-Instance)
This section provides an example of how to plan and configure ERPS multi-
instance based on network conditions.
4.17 Configuration Example (SEP)
This section uses an SEP semi-ring as an example to describe how to plan and
configure SEP protection based on network conditions.
4.18 Configuration Example (MSTP)
This topic uses an example to describe how to plan and configure the MSTP
4.19 Configuration Example (LAG)
By using an example, this topic describes how to plan and configure LAGs
4.20 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.21 Configuration Example (LPT for Services Traversing a PSN)
4.22 Configuration Example (QoS)
This topic uses an example to describe how to plan and configure the QoS
4.23 Configuration Example (HQoS)
This section provides an example of how to plan and configure hierarchical quality
of service (HQoS) based on network conditions.
4.24 Configuration Example (Ethernet Service OAM)

This section uses an example to describe how to plan and configure the Ethernet
service OAM feature.
4.25 Configuration Example (Ethernet Port OAM)
This topic describes how to plan and configure Ethernet port OAM by using an
example.
4.26 Configuration Example (Bandwidth Notification)
This section provides an example of how to plan and configure bandwidth
notification based on network conditions.
4.27 Configuration Example (IGMP Snooping V2)
This topic describes how to plan and configure the IGMP Snooping V2 by using an
example.
example.
4.1 Configuration Process (ERPS on a Single-ring

Network)
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.
NOTE

Table 4-1 Process of configuring ERPS

1 A.9.1.1 Creating Ethernet Ring Required. Set parameters as

Protection Instances follows:
● Set ERPS ID, East Port, West
Port, ERP Ring Node Flag,
Flag Port, and Control VLAN
according to the network plan.
● 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.
instance, you also need to
set the neighbor port and
the next neighbor port.
● Set Control VLAN to a value
different from the VLAN IDs of
Ethernet service packets.
2 A.9.1.3 Setting Protocol ERPS V1-based instance required.

Parameters for an ERPS Instance Set Compatible_Version to ver1.
3 A.9.1.2 Setting Global ERPS Required. It is recommended that

Protocol Parameters you set parameters to default or
planned values.
4.2 Configuration Process (ERPS on a Multi-ring

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


1 A.9.1.1 Required. Set parameters as follows:

Creating ● 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
● 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.
● 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 Required.
Setting ● If ring automatic protection switching (R-APS) virtual
Protocol channels are required by sub-ring instance, set
Parameters Virtual Channel Status to Enable (default) and set
for an ERPS Virtual Channel VLANs according to the network
Instance plan. If R-APS virtual channels are not required, set
Virtual Channel Status to Disable.
● 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.
● 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.

3 A.9.1.2 Required.
Setting It is recommended that you set parameters to default
Global ERPS or planned values.
Protocol
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 ● The control VLAN ID of an R-APS virtual channel must be
different from the VLAN IDs of the services carried by the
Forwarding same ERP ring.
Table
● 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 Optional. This operation is required when segmentation

Setting needs to be minimized after multiple failures occur on
Parameters an ERPS-protected network.
for Switching Set parameters according to the network topology and
Upon fault points.
Multiple
Failures ● Set Bound MEP when the network is in the normal
state.
● 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 Process (ERPS Multi-Instance)

The key to configuring ERPS is creating an ERPS protection instance. Multiple
services on the same ring network can be protected using ERPS multi-instance.
Both ERPS V1 and ERPS V2 support ERPS multi-instance. ERPS V1 is used as an
example.
NOTE


1 A.9.1.1 Creating Ethernet Ring Required. Set parameters as

● Set ERPS ID, East Port, West
Port, ERP Ring Node Flag,
Flag Port, Control VLAN,
and VLAN List according to
the network plan.
● When setting ERP Ring Node
Flag, note the following:
– An ERP ring has only one
ring protection link (RPL)
owner node.
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.
instance, you also need to
set the neighbor port and
the next neighbor port.
● Set Control VLAN to a value
different from the VLAN IDs
of Ethernet service packets.
● VLAN List must be set to a
subset of service VLANs on
the ring network. It must be
set when more than two
802.1Q services are
configured on a port.
2 A.9.1.3 Setting Protocol Required.

Parameters for an ERPS Instance Set Compatible_Version to
ver1.

3 A.9.10.3 Creating MEPs Optional.

To quickly detect a fault
between two ports to trigger
ERPS switching, it is
recommended that MEPs be
configured on ports. In addition,
the MEPs can be configured only
as egress ports.
NOTE
If other MEPs will initiate OAM
operations to an MEP in the same
MA, set these MEPs as remote
MEPs. For details, see Setting the
Remote Maintenance Point.
The remote MEP maintenance point
must be in the same MD and MA as
the MEP maintenance point, but
the MEP IDs are not the same.
4 A.9.1.2 Setting Global ERPS Required. It is recommended

Protocol Parameters that you set parameters to
default or planned values.
NOTE
If MEPs for Ethernet service OAM
have been created for east and west
ports, the MEPs must be bound to
the corresponding ports.
4.4 Configuration Procedure (SEP)

The core of the SEP is to create a new SEP protection instance.
NOTE
Only OptiX RTN 905 1E/2E/2F, OptiX RTN 950 housing SL93CSHUF and OptiX RTN 950A
housing CSHO/CSHOF boards and support SEP.

Table 4-4 Process of configuring SEP

1 A.9.2.1 Creating SEP Required. Set parameters as

● Set Instance ID, East Port,
East Port Configuration
Role, West Port, East Port
Configuration Role,
Control VLAN,
Preemption Delay(s), TC
Suppression Time
Interval(s), and
Authentication according
to the network plan.
● When setting Control
VLAN, note the following:
– In a SEP segment, the
control VLAN is used to
transmit only SEP
packets.
– Each SEP segment must
have a control VLAN.
– If different ports are
configured with
different SEP segments,
they can use the same
control VLAN.
– If different ports are
configured with
different SEP segments,
they can use the same
control VLAN.
2 A.9.2.2 Configuring the Port Optional.

Blocking Mode
3 A.9.2.3 Configure the port Optional.

priority
4 A.9.2.4 Configuring the Optional.

Preemption Mode
4.5 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.

NOTE
Only OptiX RTN 950A housing CSHO boards support MSTP.

Only OptiX RTN 950 housing CSH/CSHU/CSHUA boards support MSTP.
The OptiX RTN 905 2F does not support MSTP.
Table 4-5 Procedure for configuring the MSTP

1 A.9.7.1 Required when you need to configure the MSTP. Set the
Creating the parameters as follows:
MSTP Port ● Set Protocol Type, Board, and Selected Port
Group according to the network planning information.
● 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.7.2 Optional.
Setting the Use the default value unless otherwise specified.
Bridge
Parameters
of the MSTP
3 A.9.7.3 Optional.
Setting the Use the default value unless otherwise specified.
Parameters
of the CIST
4 A.9.7.6 Required when you need to configure the MSTP. Set

Enabling/ Enable Protocol to Enabled to enable the MSTP
Disabling the protocol.
MSTP
Protocol
4.6 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.

NOTE
● 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 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-6 Process of Configuring LAG
A.9.3.1 Set the parameters as follows:

Creating a ● Set LAG Type to the same value as that at the opposite end.
LAG Generally, set LAG Type to Static at both ends.
● 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.
● 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.
● 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.
● 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.3.2 Optional.
Setting LAG It is recommended that you set Load Sharing Hash Algorithm
Parameters to the default value Automatic.
Setting the Optional.

Minimum To trigger ERPS switching upon failure of some member links in
Number of a LAG when LAG and ERPS coexist, Minimum Active Links
Active Links must be set to 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.

4.7 Configuration Procedure (LPT)

The configuration procedure for LPT contains only one configuration task.
Configuration Flow Chart

Figure 4-1 provides procedures for configuring LPT.
Figure 4-1 Configuration flow chart
NOTE
The OptiX RTN 905 2F and OptiX RTN 950A (housing CSHOF) do not support LPT.

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

1 Configu A.9.12.1 Configuring Point- Required when LPT needs to

ring to-Point LPT Traversing an be configured for point-to-
point- L2 Network point services traversing an
to-point L2 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.12.2 Configuring Point- Required when LPT needs to

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

Table 4-8 Procedure for configuring LPT for point-to-multipoint services
1 A.9.12.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:
● L2 services
● QinQ services sharing UNIs
● E-Line services carried on PWs
sharing UNIs
Table 4-9 Procedure for configuring the Simple LPT
1 A.9.12.4 Configuring Simple LPT Required.

Set the
aggregation port
and the
corresponding
access port
according to the
planning
information.
4.8 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:
● OptiX RTN 950A
● OptiX RTN 950 (housing CSHU/CSHUA/CSHUF)
● OptiX RTN 905 1E/2E/2F
● OptiX RTN 910A
● OptiX RTN 980
Only the OptiX RTN 950A, OptiX RTN 950 (housing CSHU/CSHUA/CSHUF), OptiX RTN 905
1E/2E/2F, and OptiX RTN 910A /RTN 980 support the QinQ/V-UNI Egress policy.
Only the OptiX RTN 950A (housing CSHO), OptiX RTN 950 (housing CSHU/CSHUA), OptiX RTN
905 1E/2E, and OptiX RTN 910A/RTN 980 support the PW policy.

Flowchart
Figure 4-2 Flowchart for configuring QoS/HQoS

Configuring a DiffServ Domain
Table 4-10 Configuring a DiffServ Domain

1 A.9.9.2 Preferentially use the default DiffServ domain for OptiX

Modifying RTN equipment to reduce networkwide QoS
the Mapping configuration workload.
Relationships Set parameters according to the service plan.
for the DS
Domain 1. If the mapping that is planned between the packet
priority and PHB service classes for base stations or
A.9.9.3 interconnected equipment are different from the
Changing the mapping that is configured for the default DiffServ
Ports Applied domain of OptiX RTN equipment, change the
to a DS mapping of the OptiX RTN equipment to be the
Domain and same as the mapping planned for the base stations
Their Trusted or interconnected equipment.
Packet Types 2. If the packet priority type (that is, the trusted packet
type) supported by base stations or interconnected
equipment is different from the trusted packet type
(C-VLAN priority, by default) for the default 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.9.1 Required when the default DiffServ domain does not

Creating a DS meet the requirements.
Domain Set the parameters according to the service plan.
3 A.9.9.4 If you do not want the RTN transmission network to

Enabling/ change the DSCP values in packets from wireless base
Disabling stations, you can disable DSCP demapping on RTN
DSCP equipment.
Demapping
at the Egress
Port of a
DiffServ
Domain

4 A.9.9.5 If you do not want the RTN transmission network to

Enabling/ change service packet priorities, you can disable PHB
Disabling demapping on RTN equipment.
Outbound
Demapping
at the Egress
Port of a
DiffServ
Domain
Creating Policies
Table 4-11 Creating port policies

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

Creating a policies do not meet the requirements.
WRR Policy
2 A.9.9.9 Required when egress port queues use the weighted

Creating a random early detection (WRED) algorithm. Egress port
Port WRED queues use the tail drop algorithm by default.
Policy
3 A.9.9.6 Required when the queues at a port need to be

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

Creating list (ACL), class of service (CoS), committed access rate
Traffic (CAR), or 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-12 Creating PW/QinQ/V-UNI egress policies

1 A.9.9.11 Required when the default WRR policies do not meet

Creating a the requirements.
WRR Policy

2 A.9.9.10 Required when flow queues use the weighted random

Creating a early detection (WRED) algorithm. Flow queues use the
Service WRED tail drop algorithm by default.
Policy
3 A.9.9.15 Required when the flow queues on a PW need to be

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

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

Creating a V- configured with the scheduling algorithm, queue
UNI Egress shaping, and drop algorithm.
Policy
Applying Port Policies
Table 4-13 Applying port policies

1 A.9.9.12 Required when you need to apply created port policies

Setting the to ports.
Port That
Uses the Port
Policy
2 A.9.9.18 Required when you need to limit the egress port

Configuring bandwidth that an Ethernet service occupies.
Port Shaping
Applying V-UNI Egress Policies to Local Ethernet Services Carried by Ports
Table 4-14 Applying V-UNI egress policies to local Ethernet services carried by
ports
1 Applying V- Apply V-UNI egress policies when creating local

UNI egress Ethernet services carried by ports. Allocate bandwidths,
policies drop policies, and scheduling policies to services with
different priorities such as voice services and Internet
access services.

2 A.9.9.14 Limit the bandwidth of a V-UNI group whose member

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

1 A.9.9.19 When a tunnel carries multiple PWs, limit the

Configuring bandwidth of each PW and the bandwidth of the entire
Bandwidth tunnel.
Limitation for
MPLS Tunnels
2 A.9.9.20
Configuring
Bandwidth
Limitation for
PWs
3 Applying PW Apply PW policies in the UNI-to-NNI direction when

policies creating ETH PWE3 services. Allocate bandwidths, drop
policies, and scheduling policies to services with
access services.
4 Applying V- Apply V-UNI egress policies in the NNI-to-UNI direction

UNI egress when creating ETH PWE3 services. Allocate bandwidths,
access services.


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

1 A.9.9.21 When multiple QinQ services are converged at one

Configuring port, limit the bandwidth of each QinQ service.
Bandwidth
Limitation for
QinQ Links
2 Applying Apply QinQ policies in the UNI-to-NNI direction when

QinQ policies creating QinQ services. Allocate bandwidths, drop
policies, and scheduling policies to services with
access services.
3 Applying V- Apply V-UNI egress policies in the NNI-to-UNI direction

UNI egress when creating ETH PWE3 services. Allocate bandwidths,
access services.

4.9 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

Table 4-17 Procedure for configuring Ethernet service OAM

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

MD Ethernet ports involved in the service test
are located. Set the parameters as follows:
● Set Maintenance Domain Name and
Maintenance Domain Level to the
same values for the NEs for which OAM
operations are performed.
● 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.10.2 Creating an Required in the case of the NE where the

MA Ethernet ports involved in the service test
● Set Maintenance Domain Name to the
value of Maintenance Domain Name
that is set in the previous step.
● Set Maintenance Association Name to
the same value for the NEs for which
OAM operations are performed.
● Set Relevant Service to the same
service for the NEs for which OAM
operations are performed.
● 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.10.3 Creating MEPs Required in the case of the NE where the

Ethernet ports involved in the service test
the value of Maintenance Association
Name that is set in the previous step.
● Set Board and Port to the board and
port where the OAM operation is
started or terminated.
● Set VLAN to a VLAN. The settings of the
source and sink MEPs must be the
same.
● In the same MA, the value of MP ID
must be unique.
● 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.
● If the sink maintenance point is
identified based on the MP ID, CC
Status must be set to Active.
4 A.9.10.4 Creating Required in the case of the NE where the

Remote MEPs in an Ethernet ports involved in the OAM
MA operation are located. Set the parameters
as follows:
that is set in the first step.
the value of Maintenance Association
Name that is set in the second step.
● 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.10.5 Creating MIPs Required when you need to perform LT

tests and divide the faulty part into
sections.
that is set in the first step.
● Set Board and Port to the board and
port through which the Ethernet service
passes.
● In the same MA, the value of MIP ID
must be unique.
6 A.9.10.6 Performing a Required when you need to perform a CC

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

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

LT Test test.
A.9.10.9 Activating the Required When the AIS of the maintenance

AIS point 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.10.10 Monitoring Required when you need to perform an

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

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

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

4.10 Configuration Procedure (Ethernet Port OAM)

When you use the Ethernet port OAM function, you can perform appropriate OAM
NOTE
The OptiX RTN 950 housing CSHUF does not Ethernet port OAM.
Table 4-18 Procedure for configuring Ethernet port OAM

1 A.9.11.1 Enabling Required. Set the parameters as follows:

the OAM Auto- ● Set Enable OAM Protocol to Enabled.
Discovery Function
● Set OAM Working Mode to Active for the
NE that starts the discovery.
2 Link A.9.11.2 Optional.

perfor Enabling Set Link Event Notification to Enabled if the
mance the Link opposite NE needs to be informed of the faults
monito Event or performance events that are detected.
ring Notificatio
n
A.9.11.3 Optional.
Modifying You can perform this operation when you need
the OAM to adjust the thresholds of the performance
Error events.
Frame
Monitoring
Threshold
Remot A.9.11.4 Optional.

e Performing Set Remote Side Loopback Response to
loopba Remote Enabled when you need to perform a remote
ck Loopbacks loopback operation.
3 Self- A.9.11.5 Optional.

loop Enabling Set Loopback Check to Enabled when you
detecti Self-Loop need to perform local loopback detection for
on Detection the ports.
NOTE
Skip steps 1 and 2 in local loopback detection.
4.11 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.

NOTE
The OptiX RTN 980 housing CSHNU does not support Bandwidth Notification.
The OptiX RTN 950 housing CSHUF does not support Bandwidth Notification.
Table 4-19 Process of configuring bandwidth notification

1 A.9.10.1 Creating Required. Set parameters as follows:

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

an MA ● Set Maintenance Domain Name to the
Maintenance Domain Name configured in
step 1.
● Set Maintenance Association Name
consistently on the microwave equipment
and interconnected router.
● Set Protocol/Standard to Y.1731.

MEPs ● Set Maintenance Association Name to the
Maintenance Association Name configured
in step 2.
● Set Port to a microwave port or the master
port in an S-EPLA group.
● Set VLAN to the VLAN ID configured on the
interconnected router.
● Set MP ID to a unique value in a
maintenance association (MA).
● Set Direction to Egress.

Configuring ● Set Advertisement to Enable.
Bandwidth
Notification ● 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 V2 protocol is applied, you can set the static router port
and the static routing member, except for the IGMP Snooping parameters.

NOTE
OptiX RTN 905 s, OptiX RTN 905 1E/2E, OptiX RTN 910A, OptiX RTN 980 (housing CSHN/
CSHNA), OptiX RTN 950A (housing CSHOF) and OptiX RTN 950 (housing CSH) support
IGMP Snooping V2.
Table 4-20 Procedure for Configuring the IGMP Snooping V2
1 A.9.8.1 Configuring the IGMP Required.

Snooping Protocol After IGMP Snooping V2 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.8.4 Creating Static Router Optional.

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

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

Deleted 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.

The IGMP packet is available in three versions: V1, V2, and V3. V3 is compatible
with V2. Compared with V2, V3 supports to choose the source.
NOTE
OptiX RTN 905 2F, OptiX RTN 910A (housing CSHRF) and OptiX RTN 950A (housing
CSHOF) support IGMP Snooping V3.

Table 4-21 Procedure for Configuring the IGMP Snooping V3
1 A.9.8.1 Configuring the IGMP Required.

Snooping Protocol After IGMP Snooping V3 is
enabled, the parameters need
to be set according to the
service planning. It is
the default values.
2 A.9.8.4 Creating Static Router Optional.

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

Static Multicast Group for V3 If a multicast member need
not be aged, you can
configure the port as a static
multicast group member.
4 A.9.8.9 Adding SSM Mapping Optional.

If source-specific multicast
(SSM) in IGMP Snooping V3
is required for receiver hosts
that support only IGMP
Snooping V1 or V2, configure
SSM mapping on the last hop
router.
4.14 Configuration Example (ERPS on a Single-ring

Network)
protection 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.

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-22 ERPS plan

ERPS ID is 1. For details about -

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

Protocol version ver1 ● 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.
● 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

WTR time (mm:ss) 05:00 ● Set this parameter

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

Detection Enabling Status ● Configuration on a per-NE Set this parameter according

basis: Set this parameter to to the plan.
Enabled for one port and
Disabled for the other port.
For details, see Example of
configuration on a per-NE
basis .
● Configuration in an end-to-
end manner: In the case of
three NEs, set this
parameter to Enabled for
one port and Disabled for
the other port on two NEs.
On the other NE, set this
parameter to Disabled for
both ports. For details, see
Example of configuration
in an end-to-end manner .

Detection Period Short Period Set this parameter according

to the plan.
Figure 4-4 Parameters for configuring ERP instances
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.


Step 4 Configure ERPS heartbeat detection.

● Example of configuration on a per-NE basis
● Example of configuration in an end-to-end manner

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

Network)
protection 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:
● 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.
● 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:

● A ring automatic protection switching (R-APS) virtual channel is deployed on

the major ring.
● The ring network uses the revertive mode.
Figure 4-5 Networking diagram for ERPS

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

Data Preparation

● ERPS ID of the major ring: ● A major ring or sub-ring

1; ERPS ID of the sub-ring: 2 can have only one RPL
● Control VLAN: 4093 owner node. The ring node
adjacent to the RPL owner
● For details about the other node is an RPL neighbor
parameters, see Figure 4-6. node. It is 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.
● 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
the same control VLAN ID
for R-APS channels on all
ERP instance parameters ERP rings 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

Guard time (ms) 500 Set this parameter according


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

Virtual channel parameters ● Virtual-channel VLAN for all ● R-APS virtual channels must
NEs: 4092 be enabled on the two
● For NE2 and NE3: virtual interconnection nodes of
channel status: enabled; the sub-ring.
major ERPS ring ID: 1 ● The control VLAN ID of an
● Virtual channel VLAN R-APS virtual channel must
forwarding table configured differ from the VLAN IDs of
for NE2 and NE3: as the services carried on the
planned in Table 4-24 same ring.
● 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.
● 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.
Detection Enabling Status Configuration on a per-NE Set this parameter according

basis: Set this parameter to to the plan.
Disabled for the other port.
For details, see Example of
configuration on a per-NE
basis .
Configuration in an end-to-end
manner: In the case of three
NEs, set this parameter to
Disabled for the other port on
two NEs. On the other NE, set
this parameter to Disabled for
both ports. For details, see
Example of configuration in
an end-to-end manner .

Detection Period Short Period Set this parameter according

to the plan.
Figure 4-6 Parameters for configuring ERP instances
Table 4-24 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
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.

NE1 on the major ring is used as an example.

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.


----End
4.16 Configuration Example (ERPS Multi-Instance)

This section provides an example of how to plan and configure ERPS multi-
instance based on network conditions.


A network is primarily formed by NE1, NE2, and NE3 and transmits services with
VLAN 100. After NE4 is added for service expansion, the microwave ring network
needs to transmit services with VLAN 200. ERPS multi-instance is configured for
services with VLAN 200, without affecting original services with VLAN 100. Figure
4-7 shows the networking.
When ERPS Multi-Instance is deployed on the Hybrid microwave ring network, the
RPL owner node (NE3) blocks the east RPL port in normal cases and all services
with VLAN 200 are transmitted through the west port. In addition, services with
VLAN 100 carried over the east port are not affected by the blocking. When there
is a link fault or NE fault on the ring, NE3 unblocks the east RPL port so that the
interrupted services with VLAN 200 can be transmitted through the east port.


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
ERP instance parameters The ERPS ID is 1. For -

details, see Figure 4-8.
Protocol version ver1 ● 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.
● 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

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

WTR time (mm:ss) 05:00 ● Set this parameter

value is
recommended.
● Set this parameter
only for an RPL
owner.
Packet transmit interval 5 Set this parameter

(s) according to the plan.

VLAN List 200 ● Set this parameter

The parameter value
must be a subset of
service VLANs on the
ring network.
● This parameter must
be set when more
than two 802.1q
services are
configured on a port.
Detection Enabling Configuration on a per- Set this parameter

Status NE basis: Set this according to the plan.
parameter to Enabled
for one port and
Disabled for the other
port. For details, see
Example of
configuration on a per-
NE basis .
Configuration in an end-
to-end manner: In the
case of three NEs, set
this parameter to
Enabled for one port
and Disabled for the
other port on two NEs.
On the other NE, set this
parameter to Disabled
for both ports. For
details, see Example of
configuration in an
end-to-end manner .
Detection Period Short Period Set this parameter


Figure 4-8 Parameters for configuring
Procedure


Step 3 Configure MEPs for east and west ports.

1. Creating an MD.

2. Creating an MA.
3. Creating MEPs.




----End
4.17 Configuration Example (SEP)

This section uses an SEP semi-ring as an example to describe how to plan and
configure SEP protection based on network conditions.


As shown in Figure 4-9, NE1 to NE5 form a dual-homing link which is then
connected to an L2 network. Two edge NEs (NE1 and NE5) on the L2 network are
not directly connected. This networking mode is called access through an open
ring.

This section describes the procedure for configuring.
Data Preparation
Table 4-26 SEP plan

SEP instance Instance ID is 1. For details —

parameters about other parameters,
seeFigure 4-10.
Blocking Mode Optimal Set this parameter according

default value is
recommended.

User-defined 128 Set this parameter according

Priority to the plan. Generally, the
default value is
recommended.
NOTE
The higher the value, the higher
the priority.
Preemption Manual Preemption Set this parameter according

Mode to the plan. Generally, the
default value is
recommended.
Figure 4-10 Parameters for configuring SEP instances
Procedure
Step 1 Create SEP protection instances.

Step 2 Configure the port blocking mode.

Step 3 Configure the port priority.

Step 4 Configure the preemption mode.


----End
4.18 Configuration Example (MSTP)

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

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


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-27 MSTP plan

● Protocol type: MSTP It is recommended that you

● Enable protocol: enabled disable the protocol when
creating an MSTP port group
● Member ports: 3-EM6-1 and that you enable the
and 3-EM6-2 protocol after all the MSTP
parameters are set. In this
manner, the possible impact
on the MSTP protocol are
prevented in the case of
adjustments to the MSTP
Port group parameters parameters.
Bridge parameters All parameters take the default Set the bridge parameters
values. based on the requirements of
the user-side equipment.
Generally, default values are
recommended.
CIST parameters Change the path overhead to Set the CIST parameters based
200000. on the requirements of the
user-side equipment. Generally,
default values are
recommended.

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
4.19 Configuration Example (LAG)

By using an example, this topic describes how to plan and configure LAGs

As shown in Figure 4-12, 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.


This section describes the procedure for configuring link aggregation groups
(LAGs).
Data Preparation
Table 4-28 LAG plan
Static (default value) Configure the same

aggregation type at both ends.
Static aggregation is
LAG type 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.
System priority 32768 (default value) The default value is

recommended. The system
priority can be set only in
static aggregation.
Switching upon air interface Enable It is recommended that you

SD enable this function when a
LAG is configured at air
interfaces.
Minimum number of active 2 To trigger switching upon

links 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.

Master and slave ports ● Master port: 3-ISU2-1 It is recommended that you set
● Slave port: 4-ISU2-1 the main and slave ports
consistently for the equipment
at both ends.
Load sharing hash algorithm Automatic (default value) The automatic load sharing
hash algorithm is
recommended.
● 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.
● 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.
Procedure
Step 1 Create LAGs.

Step 2 Set LAG parameters.

----End
4.20 Configuration Example (LPT for Services

Traversing an L2 Network)
4.20.1 Network Diagram

On the network as shown in Figure 4-13, 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-13 Network diagram of LPT (traversing an L2 network)

This section describes the procedure for configuring link state pass through (LPT).
Data Preparation
Table 4-29 LPT plan
Point-to-multipoint LPT NE1 functions as the primary ● Plan point-to-point LPT for
configuration for NE1 point of the point-to- a point-to-point network
multipoint LPT, and the topology. Plan point-to-
primary point resides on the multipoint LPT for a point-
UNI port 4-EM6T-1. to-multipoint network
Secondary LPT point 1 (NE1 to topology.
NE2) ● Allocate a unique L2 net ID
to each LPT function point
● Packet out port: 1-ISU2
on the network side.
● L2 net ID: 11
● The LPT packets sent from
● VLAN ID: 100 L2 network-side ports can
Secondary LPT point 2 (NE1 to carry VLAN IDs.
NE3) – If the L2 network
● Packet out port: 2-ISU2 transmits packets based
on VLAN IDs, set the
● L2 net ID: 12 VLAN ID of the LPT
● VLAN ID: 100 packets the same as the

Point-to-point LPT ● L2 net ID: 21 service VLAN ID. This

configuration for NE2 ● VLAN ID carried by LPT ensures that LPT packets
packets: 100 are transmitted along
the service path.
Point-to-point LPT ● L2 net ID: 31 – If the L2 network does
configuration for NE3 ● VLAN ID carried by LPT not transmit packets
packets: 200 based on VLAN IDs,
setting VLAN IDs for LPT
packets is not required.
LPT parameters All parameters take default ● Set the LPT switching mode
values. 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, LPT
any of the secondary points
detects a fault.
● Set the WTR time and hold-
off time according to the
actual requirement.
recommended.
● 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.

Step 2 Configure point-to-point LPT that traverses the L2 network for NE2 and NE3.
----End
4.21 Configuration Example (LPT for Services

Traversing a PSN)


On the network as shown in Figure 4-14, 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-14 Network diagram of LPT (traversing a PSN)

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

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

Point-to-multipoint LPT ● The primary LPT point is a

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

----End
4.22 Configuration Example (QoS)

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

The packet microwave network shown in Figure 4-15 has the following quality of
service (QoS) requirements:
● 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.
● 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-15 Networking diagram for QoS

This section describes the procedure for configuring quality of service (QoS).
Data Preparation
Table 4-31 QoS plan
● In this example, the ● During the mapping from

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

Queue scheduling policy Figure 4-16 shows the queue —

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

mode 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-16.
Figure 4-16 QoS plan
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.23 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-17 has the following quality of
service (QoS) requirements:
● 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.
● Different services including VoIP, video, and data services of the same NodeB
are identified by VLAN priority values. Each service requires a committed
bandwidth.

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-18. required and
Set the UNI and NNI consequently
ports so the UNI ports networkwide QoS
trust C-VLAN priority configuration workload
values and the NNI ports is reduced.
trust MPLS EXP values.
Bandwidth limitation on See Figure 4-18. Different types of

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

(PW1): 80 Mbit/s NodeB is guaranteed
Services of NodeB2 using PW bandwidth
(PW2): 70 Mbit/s limitation.
Queue scheduling policy Figure 4-19 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-19

Figure 4-18 DiffServ mapping and PW bandwidth limitation

Figure 4-19 Queue scheduling policy and congestion avoidance
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
4.24 Configuration Example (Ethernet Service OAM)

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

Figure 4-20 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.
● 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.
● ON NE2, the Ethernet service from NE1 to NE3 is named NE1toNE3_Vline,
with an ID of 1.
● On NE3, the Ethernet service from NE2 to the RNC is named
NodeBtoRNC_Vline, with an ID of 1.

Figure 4-20 Networking diagram of the Ethernet service OAM

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

For details about values of the -

maintenance domain,
maintenance association, and
maintenance point (MP), see
OAM parameters Figure 4-21.
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-21 Parameters for configuring OAM

Procedure
Step 1 Create a maintenance domain containing NE1, NE2, and NE3.
Step 2 Create a maintenance association containing NE1 and NE3.

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
4.25 Configuration Example (Ethernet Port OAM)

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-22, 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-22 Networking diagram of the Ethernet port OAM

This section describes the procedure for configuring OAM.

Data Preparation
Table 4-33 OAM plan
Enable OAM auto-discovery ● Only the end in active

for NE1 and NE2 and set the mode can initiate an auto-
working mode to active. discovery or 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.
● You do no need to enable
OAM auto-discovery in a
local loopback detection
OAM auto-discovery test.
OAM operation In this example, the link The OAM error frame
performance monitoring monitoring threshold is a
function is used to monitor bit standard for OAM to check the
errors on the link. The window link performance. Generally,
values and threshold values for the default value is used. You
link performance events take can modify the value
default values. according to the actual link
status.
Procedure
Step 1 Enable OAM auto-discovery for 2-EG4-1 of NE1 and 2-EG4-1 of NE2.
Step 2 Enable link event notification for 2-EG4-1 of NE1 and 2-EG4-1 of NE2.

Step 3 Configure the OAM error frame monitoring threshold for 2-EG4-1 of NE1 and 2-
EG4-1 of NE2.
----End
4.26 Configuration Example (Bandwidth Notification)

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

● A microwave link is configured between NE1 and NE2. NE2 is connected to a

router.
● 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-23 Networking diagram for bandwidth notification

This section describes the procedure for configuring bandwidth notification.
Data Preparation
Table 4-34 Data plan
Item Parameter Value
MD configuration Maintenance Domain Name MD1
Maintenance Domain Level 4
MA configuration Maintenance Domain Name MD1
Maintenance Association MA1

Name
Relevant Service 1-NE1ToNE2
CC Test Transmit Period 1s
Protocol/Standard Y.1731
MEP configuration Maintenance Domain Name MD1

Name
Board 7-ISM6-1
Port 7-ISM6-1(RTNIF-1)
VLAN 3
MEP ID 1
Direction Egress
CC Status Active
Client Layer Level 4

Item Parameter Value
Bandwidth notification Maintenance Domain Name MD1

configuration
Name
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


example.

As shown in Figure 4-24, the E-LAN service (service ID: 1605; service name: elan1)
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:
● NE1 functions as the end node and accesses the network through the 5-ISV3
board.
● The 17-SLF2EM6-6 port is directly connected to a host.
Figure 4-24 Networking Diagram

This section describes the procedure for configuring IGMP Snooping V2.
Prerequisites
IGMP Snooping V2 is configured on this page.

Data Preparation
Table 4-35 IGMP Snooping V2 plan

Item Value in this Example Planning Principle
IGMP Snooping V2 parameters In this example, IGMP ● Set IGMP Snooping

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

Step 3 Set port 17-SLF2EM6-6 as a static member port.
Step 4 Set port 17-SLF2EM6-5 of NE1 to a fast leave port.
----End

example.


As shown in Figure 4-25, the E-LAN service (service ID: 1605; service name: elan1)
of NE1 carries the multicast service. To increase the multicast efficiency, you need
to enable the IGMP Snooping function. Compared with V2, V3 supports clock
source selection and allows you to select a specified route. The service
requirements are as follows:
● NE1 functions as the end node and accesses the network through the 5-ISV3
board.
● The 17-SLF2EM6-6 port is directly connected to a host.
Figure 4-25 Networking Diagram

This section describes the procedure for configuring IGMP Snooping.

Data Preparation
Table 4-36 IGMP Snooping V3 plan

Item Value in this Example Planning Principle
IGMP Snooping V3 parameters In this example, IGMP ● Set IGMP Snooping

Snooping parameters are set parameters according to the
as follows: service plan after enabling
● The aging time is set to the IGMP Snooping. Default
default value, 8 minutes. values are recommended.
● The maximum number of ● Setting a static router port
no response times is set to and a fast leave port is not
the default value, 3. necessarily required.
● The robustness variable is ● If a multicast member does
set to the default value, 2. not need to be aged, set the
port as a static multicast
● The query period is set to group member.
the default value, 125
seconds. ● If a router port does not
need to be aged, set the
● The response period is set port as a static router port.
to the default value, 10
seconds.
● The router port can only be
Integrated IP microwave
port. Therefore, you can set
the 5-ISV3-1 port to a static
router port to prevent it
from being aged.
Procedure
Step 1 Configure the IGMP Snooping V3 protocol for NE1.
Step 2 Set port 5-ISV3-1 of NE1 to a static router port.

Step 3 Set port 17-SLF2EM6-6 as a static member port.
Step 4 Set SSM mapping.
----End

Feature Configuration Guide 5 Configuring MPLS/PWE3 Features
5 Configuring MPLS/PWE3 Features

examples of various MPLS/PWE3.
5.1 Configuration Procedure (MPLS OAM_Y.1711)

The OAM configurations for MPLS APS are different from those for LSP long-term
monitoring.
5.2 Configuration Procedure (LSP Ping/Traceroute)
The configuration procedure of LSP ping/traceroute contains only one
configuration task.
5.3 Configuration Procedure (MPLS APS)
When MPLS APS is configured, OAM is configured simultaneously.
5.4 Configuration Procedure (PW OAM_Y.1711)
The OAM configurations of PW APS are different from those of the PW long-term
monitoring.
5.5 Configuration Procedure (PW Ping/Traceroute)
The configuration procedure of PW ping/traceroute contains only one
configuration task.
5.6 Configuration Procedure (PW APS)
When PW APS is configured, OAM is configured simultaneously.
5.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.
5.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.
5.9 Configuration Procedure (ATM OAM)
The ATM OAM configurations of an F4 flow are the same as those of an F5 flow.
5.10 Configuration Procedure (ATM Traffic Management)
ATM traffic management is configured based on ATM connections.
5.11 Configuration Procedure (ML-PPP)

Configure PPP links and then MP groups.

5.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.
5.13 Configuration Example (LSP Ping/Traceroute)
This section uses an example to describe how to plan and configure LSP ping/
traceroute according to network conditions.
5.14 Configuration Example (MPLS APS)
This section uses an example to describe how to plan and configure MPLS APS
5.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.
5.16 Configuration Example (PW Ping/Traceroute)
This section uses an example to describe how to plan and configure PW ping/
5.17 Configuration Example (PW APS)
This section uses an example to describe how to plan and configure PW APS
5.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.
5.19 Configuration Example (MPLS-TP OAM for Tunnels)
This section uses an example to describe how to plan and configure MPLS-TP
tunnel OAM according to network conditions.
5.20 Configuration Example (MPLS-TP OAM for PWs)
This section uses an example to describe how to plan and configure MPLS-TP PW
OAM according to network conditions.
5.21 Configuration Example (IMA)
This section uses an example to describe how to plan and configure IMA according
5.22 Configuration Example (ATM OAM)
This section uses an example to describe how to plan and configure ATM OAM
5.23 Configuration Example (ATM Traffic Management)
This section uses an example to describe how to plan and configure ATM traffic
management according to network conditions.
5.1 Configuration Procedure (MPLS OAM_Y.1711)

The OAM configurations for MPLS APS are different from those for LSP long-term
monitoring.

NOTE
The OptiX RTN 905 2F, the OptiX RTN 905 s, the OptiX RTN 950A (housing CSHOF), and
the OptiX RTN 950 (housing CSHUF) do not support this configuration.
The 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 5-1 Flow for configuring MPLS OAM (Y.1711)
1 Changing Required if the tunnel OAM does not comply with Y.

the OAM 1711.
Standard Change the tunnel OAM to be compliant with Y.
1711 (the default setting).
2 A.11.2.9 Required. Set the major parameters as follows:

Setting ● Set OAM Status on the ingress/egress node of
MPLS the required LSP to Enabled.
OAM (Y.
1711) ● Regarding a unidirectional tunnel, set Detection
Parameter Packet Type of the ingress node of the required
s LSP to CV; regarding a bidirectional tunnel, set
Detection Packet Type of the ingress/egress
node of the required LSP to CV.
● Set Detection Mode of the node of the required
LSP to Auto-Sensing.
● Regarding a unidirectional tunnel, set Reverse
Tunnel ID.
● 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
5.2 Configuration Procedure (LSP Ping/Traceroute)

The configuration procedure of LSP ping/traceroute contains only one
configuration task.
NOTE
The OptiX RTN 905 2F, OptiX RTN 905 s, OptiX RTN 950A (housing CSHOF), and OptiX RTN
950 (housing CSHUF) do not support this configuration.
The OptiX RTN 910A does not support this configuration.

Table 5-2 Flow for configuring LSP ping

1 A.11.2.14 Required. Regarding an MPLS tunnel,

Performing an LSP perform the operation on the required LSP
Ping Test on the ingress node. Set the major
parameters as follows:
● Set Packet Count to the default value.
● Set Packet Length and EXP Value as
required.
● 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.
egress 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 5-3 Flow for configuring LSP traceroute

1 A.11.2.15 Required. Regarding an MPLS tunnel,

Performing an LSP perform the operation on the required LSP
Traceroute Test on the ingress node. Set the major
● Set Packet Length and EXP Value as
required.
● Set Response Mode based on the tunnel
direction and the support capability of
egress node:
egress node supports the reverse
egress node does not support the
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.
No Response.
5.3 Configuration Procedure (MPLS APS)

When MPLS APS is configured, OAM is configured simultaneously.
NOTE
The /OptiX RTN 905 s/OptiX RTN 950 (housing CSHUF) does not support this configuration.
The OptiX RTN 910A only support the OAM with Y.1731.

Table 5-4 Flow for configuring MPLS APS

1 Changing Required.
the OAM ● 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).
● 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
MPLS OAM follows:
(Y.1711) ● Set OAM Status on the ingress/egress node of the
Parameters required tunnel to Enabled.
● 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.
● It is recommended that you set Detection Mode of
the ingress node to Auto-Sensing.
● Regarding a unidirectional tunnel, set Reverse Tunnel
ID.
● 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.

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 ● Set OAM Status to Enabled.
Parameters
● 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.
● 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.
● Set MEG Level to 7.
● 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.
● It is recommended that you set SD Threshold (%)
and SF Threshold (%) to the default value 0.
● 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.
● 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.
● 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.

● 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 ● To enable the function of triggering switching by bit
Advanced errors, set Enable Switching Triggered by Bit Error
Attributes to Enabled and set Switching Mode Triggered by
of Ethernet Bit Error (SF by default) according to the plan.
Ports
● 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 ● Set Protection Type to 1:1.
Group
● Set Switching Mode to Dual-Ended.
● 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.
● Set Protection Ingress Tunnel ID and Protection
Egress Tunnel ID for the protection tunnel according
to the network planning.
● It is recommended that you set Revertive Mode to
Revertive.
● It is recommended that you set WTR Time(min) to 5.
● It is recommended that you set Hold-off
Time(100ms) to 0.
● Set Protocol Status to Disabled.
5 A.11.3.4 After the ingress node and egress node are configured,
Enabling/ set Protocol Status of the APS protection groups on the
Disabling two nodes to Enabled.
MPLS APS
Protection

5.4 Configuration Procedure (PW OAM_Y.1711)

The OAM configurations of PW APS are different from those of the PW long-term
monitoring.
NOTE
The OptiX RTN 905 2F, OptiX RTN 905 s, OptiX RTN 950A (housing), and the OptiX RTN
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 5-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
Standard default setting).
2 A.11.4.3 Required. Set the major parameters as follows:

Setting ● Set OAM Status of the required PW to Enabled.
PW OAM
(Y.1711) ● Set Detection Packet Type of the required PW to
Parameter CV.
s ● Set Detection Mode of the required PW to Auto-
Sensing.
NOTE
If Packet Detection Interval(ms) needs to be set as
required, set Detection Packet Type to FFD.
5.5 Configuration Procedure (PW Ping/Traceroute)

The configuration procedure of PW ping/traceroute contains only one
configuration task.
NOTE
The OptiX RTN 905 2F, OptiX RTN 905 s, OptiX RTN 950A (housing CSHOF), and OptiX RTN
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 5-6 Flow for configuring PW ping

1 A.11.4.4 Performing Required. Set the major parameters as

a PW Ping Test follows:
● Set Packet Count and EXP Value to the
default values.
● Set Packet Length as required.
● Set Response Mode based on the
support capability of the remote PE:
– If the remote PE supports the reverse
– If the remote PE does not support the
UDP Response.
No Response.
Table 5-7 Flow for configuring PW traceroute

1 A.11.4.5 Performing Required. Set the major parameters as

a PW Traceroute follows:
Test ● Set Packet Length as required.
● Set EXP Value to the default value.
● Set Response Mode based on the
support capability of the remote PE:
– If the remote PE supports the reverse
– If the remote PE does not support the
UDP Response.
No Response.
5.6 Configuration Procedure (PW APS)

When PW APS is configured, OAM is configured simultaneously.

NOTE
The /OptiX RTN 905 s/OptiX RTN 950 (housing CSHUF) does not support this configuration.
The OptiX RTN 910A only support the OAM with Y.1731.
Table 5-8 Flow for configuring PW APS

1 Changing Required.
the OAM ● If PW OAM (Y.1711) is used to detect faults for
Standard PW APS, change PW OAM to be compliant with
Y.1711 (the default setting).
● 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
PW APS create a PW APS protection group.
Protection
Group ● Set the major parameters in the General
Attributes tab as follows.
– Set PW Incoming Label and PW Outgoing
Label according to the planning information.
● 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.
● 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

Configurin Required if MPLS-TP PW OAM is used to check the

g MPLS-TP availability of a PW. Set the parameters as follows:
PW OAM ● Set OAM Status to Enabled.
Parameter
s ● 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.
● 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. In this case, plan MEGs and MPs
according to the following principles:
– All MPs on a PW must belong to the same
MEG. Each PW must belong to a unique MEG.
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.
● Detection Mode can be set only for a T-PE.
Generally, it is recommended that you set this
parameter to the default value Adaptive.
● It is recommended that you set SD Threshold
(%) and SF Threshold (%) to the default value
0.
● 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.
● For an MS-PW, LSR ID to be Received and PW
ID to be Received need to be manually specified.
● 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
bidirectional tunnels and ingress nodes.

● 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.
● It is recommended that you set LM Packet Mode
to Standard.
Configurin Create slave protection pairs for the other PWE3
g Slave services that need to be bound to the PW APS
Protection protection group.
Pairs of
PW APS Set Protection Group ID of the slave protection
pairs to a protection group ID that is planned.
Enabling/ On the Protect Group tab page, set Enabling
Disabling Status to Enabled for the APS protection groups on
PW APS the two nodes.
Protection
5.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
Figure 5-1 provides the process of configuring MPLS-TP OAM.
Figure 5-1 MPLS-TP OAM configuration process

NOTE
/OptiX RTN 905 s/OptiX RTN 950 (housing CSHUF) does not support this configuration.
Some products of OptiX RTN 900 series do not support some OAM operations. For details,
see the specifications of the MPLS-TP OAM feature in the Feature Description.
Table 5-9 Configuring basic attributes for MPLS-TP OAM


Configurin ● Set Carrier ID according to the network plan if
g Global MPLS-TP OAM uses the ICC-based format.
OAM Carrier ID must be set to the same value for all
Parameter NEs on a network.
s
● Set Port AIS Status to Enabled if you want to
suppress alarms triggered by MPLS tunnel faults
that are caused by port faults.
● When AC link failures must be notified to its peer
end in real time, set CSF Status to Enabled.
● 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
the MPLS tunnel/PW that requires the MPLS-TP OAM
Tunnel/P functions. By default, OAM complies with Y.1711.
W OAM
Standard

Table 5-10 Configuring MPLS-TP tunnel OAM

1 A.11.2.16 Required for ingress/egress nodes. Set parameters as

Configurin follows:
g MEP ● Set OAM Status to Enabled.
Parameter
s for ● If the MPLS tunnels involve only Huawei
MPLS-TP equipment that supports IP-based MPLS-TP OAM,
Tunnel it is recommended that you set MEG ID Type to
OAM IP Based, to avoid planning MEG IDs, MP IDs,
RMEP IDs, and MIPs.
● 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.
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.
● 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.
● It is recommended that you set SD Threshold
(%) and SF Threshold (%) to the default value
0.
● 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.
● 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.
● 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.
● It is recommended that you set LM Packet Mode
to Standard.
2 A.11.2.16 If the value of MEG ID Type is not IP Based and LT

Configurin tests need to be performed, configure an MIP
g MEP creation task for every transmit node. Set
Parameter parameters as follows:
s for ● It is recommended that you set MEG ID Type to
MPLS-TP ICC Based.
Tunnel
OAM ● All MIPs and MEPs on an MPLS tunnel must
belong to the same MEG and have the same
MEG ID.
● 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

Starting a continuity of MPLS APS or the CC function is used to
CC Test of monitor the connectivity of a tunnel in real time,
MPLS-TP start a CC test on egress nodes on bidirectional
Tunnel tunnels or ingress nodes.
OAM
A.11.2.19 To perform LB tests, start an LB test on egress nodes

Starting on bidirectional tunnels or ingress nodes. Set
an LB Test parameters as follows:
of MPLS- ● If Node Type is set to MIP, set TTL correctly
TP Tunnel according to the number of hops between the
OAM MEP and 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.
● 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.
● 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

Starting test. Set parameters as follows:
an LT Test It is recommended that you retain the default values
Provided for Packet Sending Interval, Packet Sending
by MPLS- Priority, and Length of Sending Packet.
TP Tunnel
NOTE
OAM This task is supported only when the configuration is
performed in end-to-end mode on the NCE.
A.11.2.21 Perform this task when you need to query the delay
Testing and delay variation.
the Delay NOTE
and Delay This task is supported only when the configuration is
Variation performed in end-to-end mode on the NCE.
of an
MPLS
Tunnel
Setting Perform this task when you need to lock the MPLS
the 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
TST Test loss situation.
Provided NOTE
by MPLS- This task is supported only when the configuration is
TP Tunnel performed in end-to-end mode on the NCE.
OAM

Table 5-11 Configuring MPLS-TP PW OAM

1 A.11.4.6 Configuring MEP Required for the T-PE. Set

Parameters for MPLS-TP PW parameters as follows:
OAM ● Set OAM Status to
Enabled.
● 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.
● 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. In this case, plan
MEGs and MPs according
to the following principles:
– All MPs on a PW must
belong to the same
MEG. Each PW 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.
● Detection Mode can be
set only for a T-PE.
Generally, it is
this parameter to the
default value Adaptive.
● It is recommended that
you set SD Threshold (%)
and SF Threshold (%) to
the default value 0.

● 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
When GAL Mode is set to
RFC5586, the GAL is 13.
When GAL Mode is set to
Y.1711, the GAL is 14.
● For an MS-PW, LSR ID to
be Received and PW ID to
be Received need to be
manually specified.
● If the MPLS-TP PW OAM
CC function is used to
trigger PW APS, it is
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
CC Packet Interval (ms)
to the default value 1000.
This parameter is valid for
only egress nodes on
bidirectional tunnels and
ingress nodes.
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.

you set LM Packet Mode
to Standard.
2 A.11.4.7 Creating MIPs of MPLS- If the value of MEG ID Type

TP PW OAM is not IP Based and LT tests
need to be performed,
configure an MIP creation
task for every S-PE. Set
you set MEG ID Type to
ICC Based.
● All MIPs and MEPs on a
PW must belong to the
same MEG and they have
the same MEG ID.
● Each MP on a PW must
have a unique MP ID.
3 A.11.4.8 Starting a CC Test of If MPLS-TP PW OAM is used

MPLS-TP PW OAM to check the continuity of PW
APS or the CC function is
used to monitor the
connectivity of a PW in real
time, start a CC test on each
T-PE.

A.11.4.9 Starting an LB Test of To perform LB tests, start an

MPLS-TP PW OAM LB test on a T-PE. Set
● If Node Type is set to MIP,
set TTL correctly according
to the number of hops
between the MEP and 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
TTL to the default value.
● 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.
you set Packet Count,
Packet Priority, Transmit
Interval (ms), and Packet
Length to their default
values.
A.11.4.10 Starting an LT Test Perform this task when you

Provided by MPLS-TP PW OAM need to perform an LT test.
Set parameters as follows:
It is recommended that you
retain the default values for
Packet Sending Interval,
Packet Sending Priority, and
Length of Sending Packet.
NOTE
This task is supported only when
the configuration is performed
in end-to-end mode on the NCE.

A.11.4.11 Testing the Packet Perform this task when you

Loss Ratio, Delay, and Delay need to query the packet loss
Variation of a PW ratio, delay, and delay
variation.
NOTE
Setting the enabling status of Perform this task when you

LCK for MPLS-TP tunnel OAM need to lock the PW.
Set Lock Status to Lock.
Starting a TST Test of MPLS-TP Perform this task when you

PW OAM need to test the packet loss
situation.
NOTE
5.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
The OptiX RTN 905 2F, OptiX RTN 905 s, OptiX 950A (housing CSHOF), and the OptiX RTN
The OptiX RTN 905 1E/2E does not support this configuration.
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 5-12 Information about configuring an IMA group

A.11.7.1 Binding ATM TRUNKs Required.

● For ATM/IMA services, set Level to
E1. For Fractional E1 services, set
Level to Fractional E1.
● 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.

● For an ATM trunk requiring the IMA
function, set IMA Protocol Status
to Enabled.
● 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.
● 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 Optional.

Parameters ● 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.
● The other parameters take the
default values.
5.9 Configuration Procedure (ATM OAM)

The ATM OAM configurations of an F4 flow are the same as those of an F5 flow.
NOTE

Figure 5-2 Configuration flowchart
Setting Segment and End Attributes of AIS/RDI

A.11.10.2 Setting Segment and End Required. Set the parameters as

Attributes of AIS/RDI follows:
Set AIS/RDI Segment and End
Attribute of each connection direction
according to planning information.
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 Required.

Check Test A CC is used to continuously test link
connectivity, but not to locate a fault.
Set the parameters as follows:
● Set Segment and End Attribute of
the node. This parameter specifies
the termination point of CC cells,
determining the range of test link.
● 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:
● 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.
● Set Loopback Point NE of the LB
test to specify the NE whether the
LB cell is looped back.
● Test result
It should be Success.
● 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.
5.10 Configuration Procedure (ATM Traffic

Management)
ATM traffic management is configured based on ATM connections.
NOTE

Figure 5-3 Configuration flowchart
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
● Set Policy ID, or select
Automatically Assign.
● Select or assign a value for Policy
Name.
● Set Service Type according to the
● Set Traffic Type and corresponding
traffic parameters based on Service
Type.
● Set the enabled status of Discard
Traffic Frame and UPC/NPC
according to planning information.
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.
5.11 Configuration Procedure (ML-PPP)

Configure PPP links and then MP groups.

NOTE
When the OptiX RTN 905 1E/2E 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. For
details, see Setting Working Modes of E1 Ports.
When the 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 Setting Working Modes of E1 Ports.
Configuring ML-PPP (Smart E1s Are MP Group Members)
Table 5-13 Configuring ML-PPP (Smart E1s are MP group members)
Setting the A.8.6.1 Required. Set the parameters as follows:

attributes Setting ● Set Name according to service planning
of Smart Basic information.
E1 ports Attributes
of Smart ● Set Port Mode to Layer 3.
E1 Ports
A.8.6.2 Optional. Set the parameters as follows:

Setting Set Frame Format and Frame Mode according to
Advanced service planning information. Ensure that the same
Attributes frame mode is 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 5-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 Set Frame Format and Frame Mode according to
Frame Mode for a service planning information. Ensure that the same
Channelized STM-1 frame mode is used at both ends.
Normally, the port that services uses the CRC-4
multi-frame format and the PCM31 frame mode.
Creating A.8.7.1 Required.

and Creating
configuring Serial
serial ports Ports

A.8.7.2 Required.
Setting
Basic
Attributes
of Serial
Ports
A.11.11.1 Creating MP Required.

Groups
5.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.

On a PSN shown in Figure 5-4, CV packets are used to continuously test the
connectivity of the bidirectional MPLS tunnel (ID = 1501) between NE1 and NE3.
Figure 5-4 Network diagram of the MPLS OAM (Y.1711) function

This section describes the procedure for configuring MPLS OAM (Y.1711).

Data Preparation
OAM status Enabled -
Detection packet type CV LSP connectivity needs to

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
5.13 Configuration Example (LSP Ping/Traceroute)

This section uses an example to describe how to plan and configure LSP ping/
NOTE
This example describes only the application of LSP ping. The application of LSP traceroute is
similar, and therefore is not described.

On a PSN as shown in Figure 5-5, LSP ping is used to test the connectivity of a
bidirectional tunnel (ID = 1501) between NE1 and NE3.

Figure 5-5 Network diagram of the LSP ping function

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 NE3 can respond to LSP

channel 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
5.14 Configuration Example (MPLS APS)

This section uses an example to describe how to plan and configure MPLS APS

On a PSN shown in Figure 5-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 5-6 Network diagram of MPLS APS

This section describes the procedure for configuring MPLS APS.
Data Preparation
Item Value in This Planning
Example Principle
Basic information Detection packet CV -

Type
Detection mode Adaptive
Information about Protection type 1:1 Disable the

the protection PW protocol before
Mode Dual-ended configuring the
revertive protection PW.
Working ingress 1501
tunnel ID
Protection ingress 1502

tunnel ID
Protocol status Disabled
WTR time (min) 5
Hold-off time 0
(100 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

5.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.

On a PSN shown in Figure 5-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 5-7 Network diagram of the PW OAM (Y.1711) function

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
5.16 Configuration Example (PW Ping/Traceroute)

This section uses an example to describe how to plan and configure PW ping/
NOTE
This example describes the application of PW ping. The application of PW traceroute is

similar, and therefore is not described.

On a PSN as shown in Figure 5-8, PW ping is used to test the connectivity of a

PW between NE1 and NE3.
Figure 5-8 Network diagram of the PW ping function


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

1400 (long packet test) of 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 NE3 can respond to PW

channel 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

5.17 Configuration Example (PW APS)

This section uses an example to describe how to plan and configure PW APS

In Figure 5-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 5-9 Network diagram of 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:
● A working tunnel is configured with an ID of 1501, and a protection tunnel is

configured with an ID of 1502.
● Three unprotected PWE3 services are created on the working tunnel. Table
5-15 provides the service planning information.
● 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 5-15 Planning information about PW APS

Parameter Ethernet Service
Service ID 201 202 203
Protection type PW APS Slave protection Slave protection

protection pair 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

figure. protocol before
you configuring
the protection PW.
MPLS APS Protocol status Enabled -

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.

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.

Step 4 Enable PW APS protection.
----End
5.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.

On the network, the OptiX RTN 900 NEs are configured with PW FPS to
implement dual-homing protection of services.
In Figure 5-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 5-10 Networking diagram of PW FPS
NOTE
● A working tunnel is configured with an ID of 201, and a protection tunnel is configured

with an ID of 801.
● 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
Item Value in This Planning Principle
Example
Information PW ID 801 (Protection -

about the PW)
protection PW
PW Incoming 801 (Protection
Label PW)
PW Outgoing 801 (Protection

Label PW)
Information Packet Detection 3.33 -

about MPLS- Interval(ms)
TP OAM
GAL Enable Enabled
Status
ARP Dual Feed Enabled -
Procedure
Step 1 A.11.5.2 Creating a PW FPS Protection Group
Ingress Tunnel: A tunnel needs to be selected. If no tunnel is available, creation of
a PW will fail.
If Detection Mode is set to Manual, you need to set the PW OAM detection
packets to be received and
transmitted.The value Adaptive is recommended.

----End

5.19 Configuration Example (MPLS-TP OAM for

Tunnels)
This section uses an example to describe how to plan and configure MPLS-TP
tunnel OAM according to network conditions.

On a PSN shown in Figure 5-11, two LB tests must be performed to locate the
fault on the bidirectional MPLS tunnel (ID = 1501) between NE1 and NE3.
Figure 5-11 Networking diagram for MPLS-TP tunnel OAM

Data Preparation
OAM MPLS-TP OAM An NE must be allocated a

standard unique carrier ID.

OAM Figure 5-12 provides the ● If all NEs that MPLS

configurations 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.
● 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.
● 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 5-12 OAM configurations
Procedure
Step 1 Change the OAM standard to Y.1731 for NE1 and NE3.
Step 2 Set global OAM parameters.


Step 3 Configure MEP parameters for MPLS-TP Tunnel OAM.

Step 4 Start a CC test of MPLS-TP Tunnel OAM.


Step 5 Start an LB test of MPLS-TP Tunnel OAM.

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.
If an LB test is performed to check bidirectional 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

5.20 Configuration Example (MPLS-TP OAM for PWs)

This section uses an example to describe how to plan and configure MPLS-TP PW
OAM according to network conditions.

On a PSN shown in Figure 5-13, LB tests are used to test the connectivity of the
PW between NE1 and NE3.
Figure 5-13 Networking diagram for MPLS-TP PW OAM

Data Preparation
OAM standard MPLS-TP OAM An NE must be allocated

a unique carrier ID.

OAM configurations Figure 5-14 provides the ● 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.
● The recommended
setting for the MEG
level is 7.
that 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 5-14 OAM configurations

Procedure
Step 1 Change the OAM standard to Y.1731 for NE1 and NE3.

Step 3 Configure MEP parameters for MPLS-TP PW OAM.


Step 4 Start a CC test of MPLS-TP PW OAM.

Step 5 Start an LB test of MPLS-TP PW OAM.


----End
5.21 Configuration Example (IMA)

This section uses an example to describe how to plan and configure IMA according

This section describes the networking information about NEs.
As shown in Figure 5-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 5-15 Network diagram of IMA


Data Preparation
Bound port 6-ML1-1 to 6-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
IMA frame length 128 frame length, IMA
IMA symmetric mode Symmetrical mode and symmetric mode, and
symmetrical operation differential delay
tolerance of an NE (with
Differentiated delay 25 IMA protocol enabled)
tolerance consistently as those of
its 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.
Step 2 Configure an IMA group.
Step 3 Set ATM port parameters.
----End

5.22 Configuration Example (ATM OAM)

This section uses an example to describe how to plan and configure ATM OAM

As shown in Figure 5-16, one ATM service is present between the NodeB and the
RNC. The details are provided as follows.
● The 6-ML1-1(TRUNK1) port on NE1 (NE ID: 120-1) receives an ATM service
from the NodeB. VPI = 1, and VCI = 15.
● The 6-ML1-1(TRUNK1) port on NE2 (NE ID: 120-2) receives the ATM service
from the RNC. VPI = 1, and VCI = 15.
● 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.
Figure 5-16 Network diagram

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.
Step 3 Start an LB test on NE1.

----End
5.23 Configuration Example (ATM Traffic

Management)
This section uses an example to describe how to plan and configure ATM traffic
management according to network conditions.
This example describes the configurations of ATM traffic management. For a
complete configuration example, see Configuration Example (ATM Connection-
based ATM Services).

As shown in Figure 5-17, one ATM service is present between the NodeB and the
RNC. The details are provided as follows.
● The 6-ML1-1(TRUNK1) port on NE1 receives an ATM service from the NodeB.
● The 6-ML1-1(TRUNK1) port on NE2 receives the ATM service from the RNC.
● The PW between NE1 and NE2 transmits the ATM service in the N-to-one
encapsulation mode.
● 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.

Figure 5-17 Network diagram

Data Preparation
ATM policy information Table 5-16 provides the ● It is recommended to

details. configure the ATM
traffic management
policy for the PE
according to the
traffic management
policy configured for
the CE.
● The ATM traffic
management policy
must match the ATM
service bandwidth
between the PE and
CE.
Table 5-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 ClpTransparen ClpTransparen NoClpScr NoClpNoScr

tNoScr tScr
Clp01Pcr(cell 175 1859 1859 1859

/s)

Parameter NE1 and NE2
CBR Service rt-VBR nrt-VBR UBR Service

Service Service
Clp01Scr(cell - 1685 1685 -

/s)
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.
● Specify upstream and downstream ATM policy 1 for the ATM connections of
real-time voice services and signaling (CBR services).
OM services and HSDPA real-time services (rt-VBR services).
R99 non-real-time services (nrt-VBR services).
HSDPA data services (UBR services).
Take CBR services of NE1 as an example.

----End

Feature Configuration Guide 6 Configuring Clock Features
6 Configuring Clock Features

examples of various clock features.
6.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.
6.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.
6.3 Configuration Procedure (CES ACR)
Configurations of CES ACR at master equipment are different from those at slave
equipment.
6.4 Configuration Procedure (IEEE 1588 ACR)
Configuration of IEEE 1588 ACR at master equipment is totally different from that
at slave equipment.
When G.8265.1 is configured, the OptiX RTN equipment can only function as the
slave equipment.
6.6 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.
6.7 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.
6.8 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.
6.9 Configuration Example (CES ACR)
This section uses an example to describe how to plan and configure CES ACR
6.10 Configuration Example (IEEE 1588 ACR)

This section uses an example to describe how to plan and configure IEEE 1588
ACR according to network conditions.
6.11 Configuration Example (G.8265.1)
This section uses an example to describe how to plan and configure G.8265.1
clock synchronization based on network conditions.
6.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
When the system control board is CSHUF, the RTN 950's IF board in slot 1/2 does not
support IEEE 1588v2.
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).
If the Atom GPS timing system is used as the clock source, set the AE 905S module's port to
Atom GPS mode so that the NE (where the port resides) can serve as the grandmaster NE.
When the system control board is CST/CSHUF, the OptiX RTN 950 does not support Atom
GPS.
When the system control board is CSHOF, the OptiX RTN 950A does not support Atom GPS.
Table 6-1 Flow for configuring IEEE 1588v2

1 Configuring the Atom GPS Optional.

When the Atom GPS timing system is
used as the clock source, set the port to
the Atom GPS mode and configure
parameters on the Atom GPS page.
2 A.12.3.2 Changing the Mode for Optional.

Selecting the Frequency Source When frequency synchronization by
means of IEEE 1588v2 is required, set
Select Frequency Source Mode to PTP
Synchronization.

3 A.12.3.4 Setting the PTP NE Attributes Required.

● 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.
● Time synchronization can be achieved
only when PTP Time Adjustment is set
to Enabled.
● It is recommended that you set Packet
Multicast Mode to Fully Multicasted.
● When Static BMC is set to Disabled,
the NE uses the BMC algorithm to
establish the master-slave hierarchy.
When Static BMC is set to Enabled,
static PTP clock selection method is
used. In this case, the PTP port status
needs 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 Modifying the PTP Optional.

System Time ● The PTP system clock must be set only
when the NE functions 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.
● 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 Clock Ports Required.

Set an FE/GE/IF port that is used to
transmit/receive IEEE 1588v2 packets as a
PTP port.
● When NE Clock Type is set to OC, only
one PTP port can be created.
● When NE Clock Type is set to BC,
multiple PTP ports working in BC mode
can be created.
● When Work Mode is TC, the Ethernet
port can be created as a PTP port
whose working mode is TC.
● 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 Clock Port Required.

Attributes Associated attributes must be set for each
PTP port.
● Set a VLAN ID for PTP packets
according to a related plan.
● 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).
● 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.
7 A.12.3.7 Setting Parameters for PTP Required.

Clock Packets Associated PTP packet parameters must
be set for each PTP port.
● P/E Mode specifies the delay
measurement mode of a port.
● The P/E Mode at both ends of a PTP
link must be set to the same.
● For an IF port, P/E Mode can only be
set to P2P.
● 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.
● Set periods for PTP packets according
to a related plan.

8 A.12.3.8 Configuring the Cable Optional.

Transmission Offset Between NEs ● When propagation delay of a PTP link
in Tx direction is different from that in
Rx direction, set Cable Transmitting
Distance parameters to compensate
for the time difference.
● 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.
● 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).
● Compensation for propagation
asymmetry takes effect only for slave
ports.
9 A.12.3.9 Configuring a PTP Clock Subnet Optional.

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 BMC Algorithm Optional.

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.

11 A.12.3.11 Setting Basic Attributes of Required when an NE needs to receive or

External Time Ports transmit external time signals.
● Set Interface Mode to External Time
Interface.
● 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.
● 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 Required when an NE receives time

Parameters for 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 Required when an NE needs to receive or

Offset for External Time Ports transmit external time signals.
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. 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 Attributes Required when an IF port functions as a

PTP port.
When air-interface synchronization or
transparent transmission of IEEE 1588v2
time signals is used, set Enable IEEE-1588
Timeslot to Enabled.

15 Configuring Ethernet services Optional.

● 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.

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

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).
If the Atom GPS timing system is used as the clock source, set the AE 905S module's port to
Atom GPS mode so that the NE (where the port resides) can serve as the grandmaster NE.
When the system control board is CST/CSHUF, the OptiX RTN 950 does not support Atom
GPS.
When the system control board is CSHOF, the OptiX RTN 950A does not support Atom GPS.
Table 6-2 Process of configuring ITU-T G.8275.1

1 Configuring the Atom GPS Optional.

When the Atom GPS timing system
is used as the clock source, set the
port to the Atom GPS mode and
configure parameters on the Atom
GPS page.
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.

● Time synchronization is possible
only when PTP Time Adjustment
is set to Enabled.
● 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 Optional.

System Time ● 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.
● 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.

● Only a PTP port can transmit,
receive, and process PTP packets,
thereby obtaining and providing
time synchronization information.
● An FE, GE, or IF port can be
configured as a PTP port.
● 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.

● Set Not Slave to Enable.
● 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.
● 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 Optional.

Packets ● It is advised to retain the default
values of PTP packet parameters.
● If necessary, modify PTP packet
parameters according to the
network plan and ensure that
they are consistently configured
for interconnected PTP ports.
● 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 Optional.

Offset Between NEs ● 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.
● 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.
● 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).
● Compensation for propagation
asymmetry takes effect only for
slave ports.
9 A.12.3.9 Configuring a PTP Clock Subnet Optional.

● 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.
● 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 Required when an NE needs to

Time Ports receive or transmit external time
signals.
● Set Interface Mode to External
Time Interface.
● 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.
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 Required when an NE receives time

for 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 Required when an NE needs to

Offset for External Time Ports receive or transmit external time
signals.
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. Set the parameters on
Tx equipment only when Rx
equipment does not support
compensation for propagation
delay on cables.
6.3 Configuration Procedure (CES ACR)

Configurations of CES ACR at master equipment are different from those at slave
equipment.
NOTE
The OptiX RTN 905 s, the RTN 905 2F, and the RTN 950 (housing CSHUF) do not support
this configuration.
The E1 and SDH ports on a CSHO/CSHOF board can be configured as smart E1 and
channelized STM-1 ports, only when an MN1 board is configured and the service mode is
CES.
Table 6-3 Flow for configuring CES ACR (Master)

Configuring a CES NOTE
Transmit Clock 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 6-4 Flow for configuring CES ACR (Slave)

1 A.12.2.2 Configure the primary clock for an ACR clock

Configuring the domain. Set the major parameters as
Primary Clock for follows.
an ACR Clock Set CES Service corresponding to ACR Clock
Domain Source.
2 A.12.2.3 Group the E1 ports with the same clock

Configuring Ports source and from the same Master into one
Using the Clock clock domain.
Domain
3 A.8.6.2 Setting Required when slave PEs use Smart E1 ports

Advanced to restore E1 clocks.
Attributes of Smart Set Re-timing Mode of a Smart E1 port
E1 Ports restoring E1 clocks to Slave Mode.
NOTE
Only OptiX RTN 905 can use channelized STM-1
ports to restore E1 clocks.
6.4 Configuration Procedure (IEEE 1588 ACR)

Configuration of IEEE 1588 ACR at master equipment is totally different from that
at slave equipment.
NOTE

When the system control board is CSHUF, the OptiX RTN 950's IF board in slot 1/2 does not
support 1588 ACR.
Table 6-5 Flow for configuring IEEE 1588 ACR

1 A.12.3.2 Changing Optional.

the Mode for ● Regarding master equipment, set Select
Selecting the Frequency Source Mode to Physical
Frequency Source Synchronization.
● 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

Basic Attributes of transmit external clock signals.
External Time ● Set Interface Mode to External Time
Ports Interface.
● When master equipment needs to
synchronize with an external clock, set
Direction to Ingress.
● When slave equipment needs to provide its
interconnected equipment with external clock
signals, set Direction to Egress.
Configuring a PTP ● Frequency synchronization by means of IEEE
Clock Subnet 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.
● 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 Required.

the PTP NE It is recommended that you set this parameter
Attributes 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 Required for master NEs.

Modifying the The clock source priority of the master NE must
BMC Algorithm be higher than that of the slave NE. It is
Parameters for NE recommended that you set Clock Source
Clocks 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 Required.

PTP Clock Port Associated attributes must be set for each PTP
Attributes port.
● Set a VLAN ID for PTP packets according to a
related plan.
● 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).
● Set Enable ACR to Enabled for a PTP port on
slave equipment.
8 A.12.3.7 Setting Optional.

Parameters for The same interval must be set for PTP packets
PTP Clock Packets of the master and slave devices.

When G.8265.1 is configured, the OptiX RTN equipment can only function as the
slave equipment.
NOTE
The OptiX RTN 905/OptiX RTN 910A/OptiX RTN 950 (housing CSHUF)/OptiX RTN 950A
(housing CSHOF) does not support ITU-T G.8265.1 clock synchronization.
Table 6-6 Process for configuring ITU-T G.8265.1

1 Change the Required.

frequency source Frequency Source Mode must be set to PTP
selection mode. ACR Synchronization.

2 Configure the Required.

bearer mode. Select a bearer mode based on the service type
of the traversal network. In addition, configure
parameters such as the local IP address, unicast
packet C-VLAN, and clock domain.
● If QinQ services are transmitted over the
traversal network, set Carry Mode to QinQ.
● If VLAN services are transmitted over the
traversal network, set Carry Mode to VLAN.
● If L2VPN services are transmitted over the
traversal network, set Carry Mode to L2VPN.
● If L3 services are transmitted over the
traversal network, set Carry Mode to L3.
● If L3VPN services are transmitted over the
traversal network, set Carry Mode to L3VPN.
NOTE
When Carry Mode is set to L3 or L3VPN, Local IP
Address must be set to the termination route IP
address of the local NE.
3 Bind a physical Required.

port. Before enabling G.8265.1, you must bind a
physical port. The port attributes vary
depending on the bearer mode. In addition, you
must set Clock Source Port Address and Clock
Source IP Mask.
● When Carry Mode is set to L2VPN, L3, or
L3VPN, Port Mode must be set to Layer 3 or
Layer Mix.
● When Carry Mode is set to VLAN, Port
Mode must be set to Layer 2 or Layer Mix
and Encapsulation Type must be set to
802.1Q.
● When Carry Mode is set to QinQ,
Encapsulation Type must be set to QinQ.

4 Set the bearer Optional.

attributes. Different attributes need to be configured for
different bearer modes.
● When Carry Mode is set to L3VPN, you need
to add the bound port to the L3VPN VRF. On
the ACR Unicast Port Configuration tab
page, configure VRF NAME.
● When Carry Mode is set to QinQ, the QinQ
tpid and SVLANID of the slave device must
be the same as those of the interconnected
NE on the traversal network. Perform these
settings on the Global Configuration tab
page.
● When Carry Mode is set to L2VPN, a tunnel
and a PW need to be configured on the slave
NE to interconnect with the MPLS service on
the traversal network. During the
configuration, the PW control word
configured on the slave NE must be the same
as that on the traversal network. After
creating a PW on the ACR Unicast Port
Configuration tab page, configure the PW
control word and PW type on the Global
Configuration tab page, and configure
attributes such as the destination MAC
address and tunnel egress/ingress labels on
the ACR Unicast Port Configuration tab
page. The tunnel VLAN must be configured.
● When Carry Mode is set to VLAN or L3, this
configuration is not required.
5 Configure clock Optional.

attributes. Set the parameters, such as the parameter used
to query the clock sending frequency, based
actual conditions. You can also use he default
values. Perform the setting on the Clock
Configuration tab page.
6.6 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 6-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:
● NE11 achieves frequency synchronization with BSC2 by means of synchronous
Ethernet.
● NE11 achieves time synchronization with the BITS through its 1PPS+ToD time
port.
● NE12 and NE13 achieve frequency synchronization with NE11 through air-
interface links.
● NE12 and NE13 achieve time synchronization with NE11 by means of IEEE
1588v2.
● 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).
● 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 6-1 Network diagram of IEEE 1588v2

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 Enabled (default

adjustment value)
Packet multicast Fully multicasted

mode (default value)
PTP clock port parameters See the following -

figure.
IEEE 1588v2 P/E Mode IF board: P2P -

packet Ethernet board:
parameters E2E
SYNC packet 8/1024

period (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 IEEE-1588 Enabled -

timeslot

Figure 6-2 Parameters for configuring PTP clock ports
Procedure
Step 1 (Optional) Configure the Atom GPS.
1. Select an Atom GPS module.
Follow the instruction in A.3.1.7 Configuring an SFP Port to change the port
mode to ATOM GPS mode.
2. Configure parameters on the Atom GPS page.
Step 2 Change the mode for selecting the frequency source.


Step 3 Set PTP system time.
Step 4 Creating PTP clock ports.

Step 5 Set PTP clock port attributes.
Step 6 Set IEEE 1588v2 packet parameters.
Step 7 Set basic attributes of external time ports.

Step 8 Modify BMC algorithm parameters for external time ports.
Step 9 Set the cable transmission offset for external time ports.
Step 10 Set IF attributes.


----End
6.7 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 6-3 shows a mobile backhaul network commonly used by multiple carriers.
● A mobile backhaul network needs to provide service backhaul links for base
stations, as well as frequency synchronization signals and time
synchronization signals.
● RNC1, NodeB 101, NodeB 102, and BITS1 belong to carrier A.
● RNC2, NodeB 201, NodeB 202, and BITS2 belong to carrier B.
● 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 6-3 Networking diagram of IEEE 1588v2

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

adjustment value)


figure.
IEEE 1588v2 P/E Mode IF board: P2P -

packet Ethernet board:
parameters E2E


Example Principle
PDELAY packet 1
period (s)
IF attributes Enable IEEE-1588 Enabled -

timeslot
Figure 6-4 Parameters for configuring PTP clock ports
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
6.8 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 6-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:

● NE11 implements frequency synchronization with BSC2 through synchronous

Ethernet.
● NE11 implements time synchronization with the BITS through its 1PPS+ToD
time port.
● NE12 and NE13 implement frequency synchronization with NE11 through air-
interface links.
● NE12 and NE13 implement time synchronization with NE11 through ITU-TG.
8257.1.
● BTS201 implements frequency synchronization with NE13 through
synchronous Ethernet over FE ports, and time synchronization with NE13
through ITU-T G.8257.1.
● 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 6-5 Networking diagram for ITU-T G.8257.1-compliant time

synchronization

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)

Parameter Value in This Planning

Example Principle
PTP system clock NE clock type T-BC -

information
Static BMC Disabled

adjustment value)


figure.
G.8275.1 packet P/E Mode Ethernet board: -

parameters E2E
SYNC packet 64/1024

period (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 6-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 NE11.
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
6.9 Configuration Example (CES ACR)

This section uses an example to describe how to plan and configure CES ACR

As shown in Figure 6-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 6-7 Network diagram of CES ACR


This section describes the procedure for configuring CES ACR.
Data Preparation
Figure 6-8 Parameters for configuring CES ACR
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
6.10 Configuration Example (IEEE 1588 ACR)

This section uses an example to describe how to plan and configure IEEE 1588
ACR according to network conditions.

On the mobile backhaul network as shown in Figure 6-9, NodeBs need to be
clock-synchronized with the RNC. The plan for achieving clock synchronization is
provided as follows:

● The OptiX RTN equipment achieves clock synchronization with the RNC/
NodeB by means of synchronous Ethernet.
● The OptiX RTN equipment with microwave links in between achieves clock
synchronization with each other through air-interface links.
● 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 6-9 Network diagram of IEEE 1588 ACR

This section describes the procedure for configuring 1588 ACR.

Data Preparation
Figure 6-10 Parameters for configuring 1588 ACR
Procedure

Step 2 Set PTP NE attributes.
Step 3 Modify the BMC algorithm parameters for NE clocks.
Step 4 Create PTP clock ports.




----End
6.11 Configuration Example (G.8265.1)

This section uses an example to describe how to plan and configure G.8265.1
clock synchronization based on network conditions.

As shown in Figure 1, Node B needs to trace the BITS clock. Layer 2 services are
transmitted between RTN devices, and Layer 3 services are transmitted between
routers. Services on the RTN device are different from those on the router
network. The clock synchronization protocol of the RTN device is based on Layer 2
multicast. Therefore, clock synchronization between the RTN device and the router
cannot be implemented. G.8265.1 is a protocol based on Layer 3 unicast. When
both RTN devices and routers support G.8265.1, G.8265.1 can be used to
implement clock synchronization.

Figure 6-11 Network diagram of G.8265.1

This section describes the procedure for configuring G.8265.1 clock
synchronization.
Data Preparation
Item Parameter Value in this Example Planning Principle
Change the Frequency PTP ACR Set this parameter to

frequency source mode Synchronization PTP ACR
source Synchronization.
selection
mode.
Configure Carry Mode L3 Set the bearer mode

the bearer based on the traversal
mode. network type.
Clock 4 -
domain
Local IP 10.10.1.10 Set this parameter to

Address the IP address and
subnet mask of the
Local IP 255.255.255.0 port to be bound.
Mask
Unicast User 1001 -

VLAN
Unicast User 6 -
VLAN Priority
Bind a Negotiation Enabled Set this parameter to

physical port. Status Enabled.
Bond Port 17-EG6-1(PORT-1) -
Clock Source 10.10.2.20 Set this parameter to

IP Address the IP address and

Item Parameter Value in this Example Planning Principle
Clock Source 255.255.255.0 subnet mask of the

IP Mask master device.
Configure - Default value -

clock
attributes.
Procedure
Step 1 Change the frequency source selection mode.
Step 2 Configure the bearer mode.

Step 3 Bind a physical port.
Step 4 Configure clock attributes.

----End

Feature Configuration Guide 7 Configuring Maintenance Features
7 Configuring Maintenance Features
This section provides hyperlinks to the configuration processes and examples for
maintenance features.
7.1 Configuration Procedure (RMON)

When applying the RMON, you need to perform different operations as required.
7.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.
7.3 Configuration Process (TWAMP Light)
When Layer 2 forwarding E-Line or L3VPN services are configured on microwave
devices, performance statistics collection based on TWAMP Light is supported. In
this case, microwave devices can function only as reflectors.
7.4 Configuration Example (RMON)
By using an example, this topic describes how to plan and configure the RMON
7.5 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.
7.6 Configuration Example (TWAMP Light)
This section exemplifies how to plan and configure TWAMP Light–based
performance statistics collection according to network conditions.
7.1 Configuration Procedure (RMON)

When applying the RMON, you need to perform different operations as required.

Table 7-1 Procedure of configuring the RMON

1 A.13.1 Browsing Required if the current performance events of the

Current Ethernet port need to be browsed.
Ethernet ● Select the Ethernet port and performance events
Performance for the browsing operation.
● Set Sampling Period as required.
● If you need to browse over 10 performance
events, set Display Mode to List.
2 A.13.4 Browsing Required if the historical performance events of the

Historical Ethernet port need to be browsed.
Ethernet ● Set History Table Type as required.
Performance
Data ● 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 historical performance
Monitoring events or historical alarm group in a self-defined
Historical period, set the history control group with a self-
Ethernet defined period.
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
7.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 the OptiX RTN 950 (housing CSHU/CSHUA), OptiX RTN 950A (housing CSHO), OptiX RTN
905 1E/2E, and OptiX RTN 910A support this configuration.

Table 7-2 Process of configuring IP packet coloring and statistics collection

1 A.9.13 Required.
Configuring IP ● Ensure that service flow characteristics are
Packet Coloring consistently configured on upstream,
and Statistics intermediate, and downstream nodes.
Collection
● Verify that coloring bits are available before
starting IP packet coloring and statistics
collection.
● The mark bit on the intermediate and
downstream nodes must be the same as that
on the upstream node.
● 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.
7.3 Configuration Process (TWAMP Light)

When Layer 2 forwarding E-Line or L3VPN services are configured on microwave
devices, performance statistics collection based on TWAMP Light is supported. In
this case, microwave devices can function only as reflectors.
NOTE
Only the RTN 910A equipped with the CSHRF, RTN 950A equipped with the CSHOF, and RTN
905 2F equipped with the SL93CSHUF support IP network performance statistics collection for
L3VPN services based on TWAMP Light.
Table 7-3 Process of configuring IP packet coloring and statistics collection

1 Configuring Mandatory
TWAMP Light– Services for which statistics are to be collected
based must be Layer 2 forwarding E-Line or L3VPN
performance services.
statistics
collection
7.4 Configuration Example (RMON)

By using an example, this topic describes how to plan and configure the RMON


As shown in Figure 7-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.
7.4.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.
● 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.
● 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
7.4.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:
● 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.
● 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.
● The traffic transmitted from 4–ISU2–1 on NE2 is almost equal to the traffic
received at 4–ISU2–1 on the opposite NE1.
● The traffic transmitted from 4–ISU2–1 on NE1 is almost equal to the traffic
received at 1-EM6F-5 on NE1.
● 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:
● The devices at both ends work in different modes.
● 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
7.5 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.


The network shown in Figure 7-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:
● 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).
● 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 7-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 7-4 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 7-5 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- 3-
ISV3-1(RTNIF-1) 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
7.6 Configuration Example (TWAMP Light)

This section exemplifies how to plan and configure TWAMP Light–based
performance statistics collection according to network conditions.

This section describes service requirements and service planning.
On the mobile backhaul network shown in Figure1 Networking for TWAMP
Light–based performance statistics collection, performance statistics collection
is achieved through packets exchanged between the RTN NE and the upper-layer
router. The RTN NE functions as a reflector and is configured with Layer 2
forwarding E-Line services or L3VPN services. The upper-layer router functions as a
controller to initiate a measurement session and start performance statistics

collection. The RTN NE (reflector) only responds to the measurement session. The
router (controller) reports the collected performance statistics to the NMS.
Figure 7-3 Networking for TWAMP Light–based performance statistics collection

This section describes the procedure for data configuration.
Data Preparation
The following table lists the parameters related to E-Line services in this example.
Table 7-6 Parameters related to E-Line services

Parameter Example Value Planning Principle
Test Session ID Automatically Assign Indicates a test session

ID.
You can configure this
parameter as required
to differentiate sessions
or select Automatically
Assign to enable the
system to automatically
assign an ID.
Source IP 192.0.0.2 Indicates the source IP

address, which is the IP
address of the local NE.
Sink IP 192.1.0.4 Indicates the

destination IP address,
which is the IP address
of the NE functioning
as the controller.

Parameter Example Value Planning Principle
Source UDP Port 1025 Indicates the UDP port

ID of the local NE. The
default value is 1025.
Sink UDP Port 1025 Indicates the UDP port

ID of the NE
functioning as the
controller. The default
value is 1025.
Relevant Service type E-LINE Indicates the service

type. The default value
is E-LINE.
Currently, only E-LINE
is available on the
NMS.
Relevant Service service01 Indicates the service for

which statistics are to
be collected.
Interface 1- Indicates the IF port or

ISV3-1(RTNIF-1[L(TID1] Ethernet port related to
)) the service for which
statistics are to be
collected.
Procedure
Step 1 Create a test session.
The following figure uses the Layer 2 E-Line service as an example.

----End

Feature Configuration Guide A Task Collection
A Task Collection
This document describes various tasks involved in this document.
A.1 NCE Quick Start

The NCE quick start guide helps to learn about basic operations on the NCEclient.
A.1.1 Logging In to the NCE Client

The NCE uses the client/server architecture and allows multiple clients. You can
log in to the NCE client with a PC.
Prerequisites
● The local PC is connected properly to the NCE server, and the NCE server is
running properly.
● You have obtained the account and password for login.
Context
Tools, Equipment, and Materials

PC
● The PC and web browser must meet the requirements listed in the following
table.
Table A-1 O&M-plane configuration requirements
Item Basic Configuration Requirement
Memory 4 GB or larger
Hard disk Idle hard disk: 8 GB or larger

Item Basic Configuration Requirement
Operating ● Windows 7 (32-bit or 64-bit)

system ● Windows 10 (32-bit or 64-bit)
Web browser ● Internet Explorer 11 or later (32-bit or 64-bit)

● Google Chrome 50 or later (32-bit or 64-bit)
● Firefox 40 or later (32-bit or 64-bit)
● Edge 20 or later (64-bit)
Resolution 1366 x 768 or higher (1920 x 1080 is recommended.)
● On the NCE O&M plane, the default user admin serves as the system
administrator who can manage all resources and has all operation
permissions. The default password for admin is Changeme_123. If you enter
incorrect passwords for user admin for five consecutive times within 10
minutes, the login IP address will be locked for 10 minutes.
● If three accounts using a login IP address are locked within 10 minutes, this IP
address will be locked for 30 minutes.
● If the login using an IP address meets the IP address lockout conditions
specified on the Account Policy page, this IP address will be locked.
● If the login using a local account meets the account lockout conditions
specified on the Account Policy page, this account will be locked for 30
minutes by default.
● You can wait until the account is unlocked or contact the security
administrator to unlock the account and then log in to the NCE client again.
Procedure
Step 1 Enter https://IP address of the O&M plane:Port number in the address box of the
web browser, and press Enter.
NOTE
● The IP address of the O&M plane is the client login IP address configured on the
Common_Service node. If the Common_Service node is deployed in a cluster, this IP
address is the floating IP address of the Common_Service node cluster. If the
Common_Service node is a single instance, this IP address is the client login IP address
of the Common_Service node.
● The port number is that of the system server and its default value is 31943.
Step 2 In the Login dialog box, fill in Username and Password.

NOTE
You need to change the initial password on your first login. If you forget the password for
user admin, you can reset the password only by reinstalling the system.
Step 3 Click Log In.
----End

A.1.2 Logging Out of the NCE Client

You need to log out of the NCE client after you are done using it.
Prerequisites
You must be an NM user with NE operator authority or higher.

PC
Procedure
Step 1 In the upper right corner of the window, click the username and choose Log Out.
NOTE
● If Auto-logout if no activity within is configured, the user session is automatically

logged out if no operation is performed within the period specified by this parameter.
● If the web browser is forcibly closed, the session will not be logged out immediately but
30 minutes later. Therefore, do not forcibly close the web browser.
● Sessions are forcibly logged out under attacks.
----End
A.1.3 Using Online Help

Online Help provides help information about the NCE.
Prerequisites

NCE
NOTE
The Web LCT does not support this operation.
Procedure
Step 1 Click in the upper right corner of the NCE window.
----End
A.1.4 Navigating to Common Views

This section describes the main views on the NCE and their functions.

A.1.4.1 Navigating to the Main Topology

On the NCE, you can manage the network topology in the main topology view.
Prerequisites

NCE
NOTE
Procedure
Step 1 In the NCE window, click Network Management.
The main topology view is displayed.
Step 2 Optional: Click on the left in the main topology view.

The subnet and NE information in the current network topology is displayed on
the left in the main topology view.
----End
A.1.4.2 Navigating to the NE Explorer

The NE Explorer provides the main GUI for device management on the NCE. In the
NE Explorer view, there is the function tree, object tree, and configuration pane.
Prerequisites

NCE
Procedure
Step 1 Optional: On the Physical Topology page, double-click the subnet where the
target NE is located. In the topology view, select the NE icon.

NOTE
You can also select the target NE using either of the following methods:
● Click on the left in the main topology view and select the target NE from the
displayed subnet and NE information. An NE information drop-down list is displayed on
the right.
● In the search box in the upper right corner of the main topology view, enter the key
information about the target NE and click the target NE in the search result list.
Step 2 Click Show information panel in the search box in the upper right corner. Select
NE Explorer from the drop-down list.
The NE Explorer view is displayed.
----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

NCE
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
● To quickly navigate to the NE Explorer view, click .
● 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 NCE 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 NCE 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
● To quickly navigate to the view displaying current alarms, click .
● To quickly navigate to the NE List view, click .
● To quickly navigate to Online Help, click .
NOTE
You can also navigate to the NE Explorer view using the following methods:
● In NE List, right-click the NE to which you are logged in and choose NE Explorer from the
shortcut menu.
● 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 (NCE)

The NCE 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 NCE 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
● The NMS must have proper communication with NEs.
● You must be an NM user with NE operator authority or higher.

NCE
Procedure
Step 1 Choose Topology > Discovery > NE from the Main Menu.
Step 2 Select Transport NE Search tab.
Step 3 Select Search Mode.
NOTE
● If the NCE server and the gateway NE are in the same network segment, it is recommended
that you set Search Mode to IP auto discovery.
● 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
NCE server and gateway NE are not in the same network segment, ensure that the IP
routes of the network segments to which the NCE server and gateway NE belong are
configured on the NCE 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
● If Create NE after search is selected, you need to specify NE User and Password.
● 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
● 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 Perform Step 2 to Step 5.
through Ethernet cables
Not all NEs are directly connected to the NMS Perform Step 6 to Step 11.
server through Ethernet cables
Step 2 Select NE Search.

The Search NE dialog box is displayed.
NOTE
The default user name is lct, and its corresponding password is Changeme_123.
Step 3 Set Local IP Address based on the network planning information.

NOTE
Local IP Address indicates the IP address of an Ethernet port on the NMS server. There may be
multiple Local IP Address values because an NMS server may have multiple network adapters.
Step 4 Set NE IP Address based on the network planning information.

NOTE
NE IP Address indicates the IP addresses of all NEs (searched out by the system automatically)
that are connected to the NMS server directly through Ethernet cables.
Step 5 Click OK.

NOTE
When NE Search is selected, the system can directly log in to NEs. You do not need to enter
the user name and password.

Step 6 Select Advanced Search.

The Search NE dialog box is displayed.
Step 7 Optional: If you select IP auto discovery, then:

1. 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 (NCE)

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
● The NMS must have proper communication with the NE to be created.
● If the NE to be created is a non-gateway NE, the gateway NE to which the NE
to be created belongs must be created.

NCE
Procedure
Step 1 In the main topology, right-click, choose New > NE.
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 Select the gateway to which the NE
Non-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
● The NMS must have proper communication with the NE to be created.
● If the NE to be created is a non-gateway NE, the gateway NE to which the NE
to be created belongs must be created.

Web LCT

Procedure
Step 1 In NE List, click Add NE. Then, select Europe.
Step 2 Set the NE parameters.
NOTE
● The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.

● 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.
● Do not change the Extended ID when the number of actual NEs does not exceed the range
permitted by the basic NE ID.
● Set the parameters according to the network plan.
● The default user name is lct, and its corresponding password is Changeme_123.
NOTE
● 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 opt/oss/NCE/etc/ssl/nemanager/default directory on the NCE 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.
● Install the SSL certificate to the NE using the NCE. 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
● 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
● The default User Name is lct.

● 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
● To quickly start the NE Explorer, double-click the NE to be managed in the NE list.

● Check the legend to learn the specific meanings of different colors and symbols in the
slot layout diagram.
● 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
● All the boards must be installed correctly.

NCE
NOTE
Web LCT also supports this operation and the steps are the similar to those on the NCE.
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
● All the boards and their SFP modules have been installed correctly.

NCE
NOTE

Context
The following table lists the boards and the supported SFP module types.
Table A-2 RTN 910A
Board Supported SFP Module Type
EG6 FE optical module

GE optical module
GE electrical module
Ports supported by the AE 905S
module: GE5 and GE6
EG4/EG4P FE optical module

GE optical module
SL1DA/CQ1 STM-1 optical module

STM-1 electrical module
EM6 FE optical module

FE electrical module
GE optical module
Table A-3 RTN 905

GE optical module
module: COMBO1 and COMBO2
CD1 STM-1 optical module


GE optical module

GE optical module

Table A-4 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
module: GE5 and GE6

GE optical module
EX1F 10GE optical module

GE optical module
EX1 10GE optical module
Table A-5 RTN 950A


GE optical module



GE optical module


GE optical module
module: GE5 and GE6

GE optical module
Table A-6 RTN 980


GE optical module

SL1D/SL1DA/CQ1 STM-1 optical module


GE optical module
module: GE5 and GE6
SL4D STM-1 optical module

STM-4 optical module
EG2D GE optical module

NOTE
Only RTN 980 housing CSHNA boards
support EX1 boards.
EX1(logical board) 10GE optical module


GE optical module
Table A-7 RTN 980L
EM6F FE optical module

GE optical module



GE optical module
module: GE5 and GE6
SL4D STM-1 optical module

STM-4 optical module

GE optical module
NOTE
● SL91EM6 and SL91EG4 boards support only one AE 905S 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
● It is recommended that you delete the ports that have no SFP module, to prevent the NMS
from reporting alarms related to SFP modules.
● For an SDH port, you can set the SFP module type in Modify 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.
● 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 are used as system control, timing, and switching boards, the backplane bus
rate can be 1 Gbit/s or 2.5 Gbit/s.
Prerequisites
● For the RTN 950 using CSH, the default backplane bus rate is 2.5 Gbit/s.
● All the boards have been installed correctly.

NCE
NOTE
Web LCT also supports this operation and the steps are the same as those on the NCE.
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.

NCE
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.
----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

NCE

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 NCE topology when the NE can communicate with the NCE.
Prerequisites

NCE

NOTE
Context
NOTE
To perform batch NE configurations on the NCE, choose Configuration > NE Configuration

Data Management > Transport Network > Auto NE 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 NCE server based on the network plan.
NOTE
● For a single NMS server, you only need to set Server IP1.
● For dual NMS servers, set Server IP1 and Server IP2.
Step 4 Click Apply.
----End
A.3.1.12 Synchronizing the NE Time (NCE)

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
● When you need to synchronize the NE time with the time on the NMS server,
the time zone and time must be set correctly on the PC or server running the
NMS software.
● When you need to synchronize the NE time with the time on the NTP server,
the time on the NTP server must be set correctly and the NTP protocol must
be normal.

NCE

Procedure
Step 1 Choose Configuration > > Common > NE Time Sync 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
● When you need to synchronize the NE time with the NMS time, set Synchronous Mode to
NM.
● 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.
NOTE
Two devices cannot be configured as a standard NTP server to each other.

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
● When you need to synchronize the NE time with the time on the NMS server,
the time zone and time must be set correctly on the PC or server running the
NMS software.
● When you need to synchronize the NE time with the time on the NTP server,
the time on the NTP server must be set correctly and the NTP protocol must
be normal.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose
Configuration > NE Time Synchronization from the Function Tree.
Step 2 Set the synchronous mode.
If... Then...
You set Synchronous Mode to Set the relevant parameters, and then click
NULL 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
Standard NTP Apply to perform Step 3.
NOTE
If you only need to synchronize the NE time and do not need to change the type of
synchronization or parameters, select the synchronization option corresponding to the NE, right-
click, and choose Synchronize with NM Time.

Step 3 Configure the upper-layer standard NTP server of the NE.

1. Click the Standard NTP Server tab. In the Standard NTP Server tab page,
click Add.
2. After setting the parameters of the standard NTP server, click OK.
NOTE
● If the NE is a gateway NE, set the external NTP server as the standard NTP server.
● 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

NCE
NOTE
Context
NOTE
To perform batch NE configurations on the NCE, choose Configuration > Common > NE Time
Localization from the main menu.

Procedure
Step 1 Choose Configuration > Common > NE Time Localization 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
● You must be an NM user with NE administrator authority or higher.
● Synchronous Mode must be set to Standard NTP and Standard NTP
Authentication must be set to Enabled.
● The NTP protocol must be running properly and the NTP identity
authentication must be enabled on the NTP server.

NCE
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 > Common > NE Time Sync 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
● The NE supports anti-theft. For details, see Availability.
Tools, Instruments, and Materials

NCE
NOTE

Context
The OptiX RTN 950 (housing CST/CSH/CSHUF)/OptiX RTN 980/RTN 905 s
(housing CSHN), and OptiX RTN 905 1C/1A/2A (housing CSHN) do not support
NE anti-theft.
Procedure
Step 1 Choose Security > NE Security > NE Antitheft 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, 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 NCE
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

NCE
NOTE
Context
The OptiX RTN 950 (housing CST/CSH/CSHUF)/OptiX RTN 980/RTN 905 s
(housing CSHN), and OptiX RTN 905 1C/1A/2A (housing CSHN) do not support
NE anti-theft.
Procedure
Step 1 Choose Security > NE Security > NE Antitheft 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 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 (NCE)

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
● An NE must be logged in to successfully.

NCE
NOTE
Procedure
Step 1 Select the corresponding operation steps according to the NE status.
If... Then...
An NE is not configured and the NE In the Main Topology, double-click the

data needs to be uploaded. NE that is not configured, and then
perform Step 2 through Step 4.
An NE is configured with data and Perform Step 5 through Step 8.

NE 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
Step 8 Click Close.
----End

A.3.2.2 Synchronizing NE Data (NCE)

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
● You must be an NM user with NE maintainer authority or higher.
● The NE is created.
● The NE is in unsynchronized state.
NOTE
When an NE is in unsynchronized state, it carries the mark.

NCE
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

NCE
NOTE
Context
NOTE
To perform batch NE configurations on the NCE, choose MonitorPerformance > Mornitoring

Time Settings 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

NCE
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 Managing 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
● The SDH/IF boards of various NEs must be created on the NMS.

NCE

NOTE
Procedure
Step 1 Choose Topology > 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
● 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.
● 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.
● 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
● 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.
● 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
● The relevant boards of various NEs must be created on the NMS.
● The resources of port IP addresses must be created if the automatic allocation
of port IP addresses is enabled.

NCE
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.
If a fiber/cable carries an MPLS link, set "Auto Assign IP Address" to "Yes". The
NCE splits an unused network segment with a length of 30 bits from the IP
address resource to the MPLS link. The two IP addresses except the network
address and the broadcast address in the network segment are allocated to the
interfaces at both ends of the cable.
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
● The boards of all NEs have been created on the NMS.
● All Ethernet links are functioning properly.
● Port Mode at both ends of each Ethernet link is Layer 2 or Layer 3.


NCE
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 Topology > Discovery > Fiber/Cable/Microwave
Link from the main menu.
Procedure
Step 1 Choose Topology > 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

NCE
NOTE
Procedure
Step 1 In the Main Topology, right-click, choose New > Link.
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
● The corresponding IF board must be added on the NE Panel.

NCE
NOTE
Procedure
Step 1 In the Main Topology, right-click, choose 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.5.6 Deleting Fibers

You can delete an unwanted fiber on the NCE through the main menu.

Prerequisites

NCE
NOTE
Procedure
Step 1 Delete the fiber.
----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

NCE
NOTE
Procedure
Step 1 In the Main Topology, right-click, and then choose New > Subnet.
The Create Subnet dialog box is displayed.
Step 2 Enter the attributes of the subnet.
Step 3 Click the Select Object button, select a created NE from Available Objects, and
then the NE will be added to Selected Objects.
Step 4 Click OK.
Step 5 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

NCE
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE that needs to be copied.
Step 2 Choose Copy to.
The Copy to dialog box is displayed.
Step 3 Select the subnet that the NE 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

NCE
NOTE
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be moved.
Step 2 Choose Move to.
The Move to 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

NCE
NOTE
Context
NOTE
● Do not use the default NE IP address to access the public network (such as Internet).
● 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
Communication Parameters from the Function Tree.
Step 2 Configure the communication parameters of the NE.

NOTE
● When modifying IP addresses and subnet masks of neighboring NE, you are advised not to
set the network segment of one NE to contain that of another NE. For example: If
192.168.1.2/255.255.0.0 is set for one NE and 192.168.1.3/255.255.255.0 is set for another
NE, the 192.168.0.0 network segment contains the 192.168.1.0 network segment.
● If configuring multiple parameters, click Apply for each instance.
● 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

NCE
NOTE
Procedure
DCC Management from the Function Tree.
Step 2 Click the DCC Rate Configuration tab.
Step 3 Optional: Change the enable status of the DCC.
1. Double-click the cell in the Enabled/Disabled column to which the DCC
corresponds. Select the required state from the drop-down list.
2. Click Apply.
Step 4 Optional: Change the protocol type of the DCC.
1. Double-click the cell in the Protocol Type column to which the DCC
corresponds. Select the required protocol type from the drop-down list.
2. Click Apply.

NOTE
– For OptiX RTN 905, the 16th E1 is configured as a 2 Mbit/s external clock port, and
external clock source 2 refers to this 2 Mbit/s external clock port. For OptiX RTN
950/980, external clock source 1 refers to the external clock port on the system control
board with a smaller slot ID, and external clock source 2 refers to the external clock
port on the system control board with a larger slot ID.
– When Protocol Type is set to TCP/IP for a port that is an ABR's port in a non-backbone
area, IP Address and Subnet Mask must be specified for the port (ABR stands for area
border router). In addition, it is recommended that the IP address of the port and the IP
address of the port-located NE be on different network segments.
– When Protocol Type is TCP/IP for a port and the port does not belong to the default
process, you need to set IP Address, Subnet Mask, and OSPF Subnet to which the port
belongs.
– If a static route exists, the value of Protocol stack type must match the protocol type of
the static route.
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.


NCE
NOTE
Procedure
DCC Management from the Function Tree.
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

NCE
NOTE
Procedure
DCN Management from the Function Tree.

Step 2 Click the Bandwidth Management tab.
Step 3 Set the VLAN ID and bandwidth used by an inband DCN.
NOTE
● 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.
● 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.
● Bandwidth(kbit/s) specifies the bandwidth for inband DCN messaging on the Ethernet link.
● IF Port Bandwidth(kbit/s) specifies the bandwidth for inband DCN messaging on the radio
link.
● 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

NCE
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

NCE
NOTE
Context
NOTE
● Enabled Status specifies the enabling status of the port.

● 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.
● 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.
● 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.
● 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.
● If a static route exists, the value of Protocol stack type must match the protocol type of the
static route.

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

NCE

NOTE
Context
NOTE
● Do not use the default NE IP address to access the public network (such as Internet).
● 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
● If the Enabled Status is set to Enabled, this port can be used to support access of the
management information from the NMS.
● 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

NCE
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

NCE
NOTE
Procedure
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 NCE 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

NCE
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

NCE
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

NCE
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Communication > IP
Protocol Stack Management from the Function Tree.
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.

NCE
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

NCE
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

NCE
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
● If Authentication Type is set to none, all preset authentication passwords are cleared.
● 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

NCE
NOTE
Procedure

Step 2 Click the Proxy ARP tab.
Step 3 Set the enable status of the proxy ARP.
NOTE
● The proxy ARP enables the NEs in the same network segment but different domains to
communicate with each other.
● 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

NCE
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.

NCE
NOTE
Procedure
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


NCE
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

NCE
NOTE
Procedure
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

NCE
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

NCE
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

NCE
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

NCE
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
● 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.
● 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.
● 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.
● It is recommended that Port take the default value.
● 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

NCE
NOTE
Procedure
Step 1 Choose Topology > NE Onboarding > 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
● 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.
● 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
● If more than one standby gateway NE is required, set GNE3 and GNE4.
● If the main gateway NE fails, GNE2 takes over. If GNE2 fails, GNE3 takes over. If GNE3
fails, GNE4 takes over.
● 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

NCE
Background Information
● It is recommended that the LCT accesses an NE through Ethernet ports.
● If you need to initialize an NE or perform software loading by using the LCT,
the LCT needs to access the NE through Ethernet ports.
● OptiX RTN 910A does not support the extended NMS port.
Procedure
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

NCE
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

NCE
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

NCE
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 Serial Port Access Control 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

NCE
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 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
● An online user can create a user at a lower level.

NCE
NOTE
● The default NE user is at the monitoring level.
● For security of NE data, NE users are assigned operation rights based on their
responsibilities.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security >
NE User Management from the Function Tree.A dialog box is displayed,
indicating that the operation is successful.
Step 2 Close the dialog box.
NOTE
Step 3 Click Add.

The Add NE User Attribute/Value dialog box is displayed.
Step 4 Set the parameters of the NE user according to the network plan.

NOTE
● A Debug Level NE user has all security and configuration authorities, and has the right
to run debugging commands.
● A System Level NE user has all security and configuration authorities.
● A Maintenance Level NE user has some security authorities, some configuration
authorities, the communication setting authority, and the log management authority.
● An Operation Level NE user has all fault performance authorities, some security
authorities, and some configuration authorities.
● 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
● The NE user is created.
● An online user can change the password of a user at a lower level.


NCE
NOTE
NOTE
Periodically change the password of an NE user to avoid password leaks.
Procedure

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
● An NE user has been created.
● The current online NE user is of a higher level than the NE user whose
additional user information will be configured.

NCE
NOTE
Procedure

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

NCE
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

NCE
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

NCE
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
● An NE user is created.

NCE
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 LCT Access to NEs

When an NE is managed by the NMS, the LCT can access this NE by default.
Prerequisites


NCE
NOTE
Context
● If the LCT requests to log in to an NE to which the NMS has logged in, the NE
determines whether to permit the login of the LCT according to the status of
LCT Access Control Switch.
● If the LCT requests to log in to an NE to which the NMS has not logged in,
the NE permits the login of the LCT regardless of the status of LCT Access
Control Switch. The NMS, however, can log in to an NE to which the LCT has
logged in. That is, the login of the LCT does not affect the login of the NMS.
After the NMS user logs in to the NE successfully, the logged LCT user is not
affected. If LCT Access Control Switch is set to Disable Access, the logged
LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security >
LCT Access Control from the Function Tree.
Step 2 Select the required NE from the list, and click Access Allowed to enable the LCT
access function.
NOTE
To disable the LCT access function, click Disable Access.
----End
A.4.3 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.3.1 Configuring the Connection Mode Between an NCE and Its Gateway
NE
Two connection modes are supported between an NCE and its gateway NE,
namely common connection mode and Secure Sockets Layer (SSL) connection
mode.
Prerequisites
● You must be an NM user with NE maintainer authority or higher.

● SSL licenses have been deployed on the gateway NE and the NCE according
to the SSL loading guide.

NCE
NOTE
Procedure
Step 1 Configure the connection mode of the NCE.
1. ChooseTopology > NE Onboarding > DCN Management for Transport NEs
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 NCE logs in to
an NE in common mode, data is transmitted between the NCE 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 > Communication Parameters from the Function Tree.
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.4 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.4.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

NCE
NOTE
Procedure
Step 1 In the NE Explorer, select the desired NE from the Object Tree and choose Security
> NE RADIUS Function Configurations 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.4.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
● The RADIUS function has been enabled for the NE.

NCE

NOTE
Procedure
> NE RADIUS Configuration from the Function Tree.
Step 2 Click the RADIUS Server Configuration button.
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.
● 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.
● If an NE uses RADIUS authentication in the proxy NAS mode, set the

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.4.3 Configuring RADIUS Server Parameters

This section describes how to configure RADIUS server parameters.
Prerequisites
● The RADIUS server or RADIUS proxy server have been configured for the NE.

NCE
NOTE
Procedure
> NE RADIUS Configuration from the Function Tree.
Step 2 Click New.
The New NE RADIUS Configuration 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.

● If an NE uses RADIUS authentication in the NAS mode or functions as a proxy
server:
● If an NE uses RADIUS authentication in the proxy NAS mode:
NOTE
● If no standby server is required, set Server Status to Active.

● 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.
● Set Shared Key to the same value on the NE and on the RADIUS server.
● It is recommended that Interval of Packet Transmission and Packet Retransmission
Attempts take their default values.
----End
A.4.4.4 Configuring a KMC Key

A KMC key can enhance NE data security.
Prerequisites

NCE

Procedure
Step 1 Configure a KMC key.
----End
A.4.5 Configuring LLDP

Configuring LLDP to transmit equipment information between neighboring NEs
and to achieve automatic discovery of topology.
A.4.5.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

NCE
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.5.2 Configuring LLDP for an Ethernet Port

Configuring LLDP for Ethernet ports connected to neighbor equipment is a
prerequisite for using LLDP.
Prerequisites

NCE
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.5.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
● LLDP has been enabled for related Ethernet ports.

NCE
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:

1. Choose Resource > Inventory Report > Microwave Report > 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
● The IF boards and the ODUs/RFUs to which the IF boards are connected have
been added in NE Panel.

NCE
NOTE

● This task configures a 1+0 radio link, a cross polarization interference
cancellation (XPIC) radio link, or a 1+1 radio link. To configure N+0 radio
links, they must be configured as N 1+0 radio links.
● For OptiX RTN 905 1E, this task configures a 1+0 radio link or an XPIC radio
link. The method for configuring an XPIC radio is different from the method
for configuring an XPIC radio link between other OptiX RTN 900 products.
● To configure 1+1 radio links between interconnected OptiX RTN 905 1E,
perform the operation A.5.2 Creating an IF 1+1 Protection Group and then
configure a 1+0 radio link between the two main OptiX RTN 905 1Es and a
1+0 radio link between the two standby OptiX RTN 905 1Es.
● 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
● If the radio link is in a 1+1 or XPIC group, select any IF board connected to the radio
link.
● If the radio link is not working correctly, the basic information of the peer NE is not
displayed.
● 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.
● 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.
● To configure 1+1 protected radio links:
a. Select 1+1.
c. Optional: Click Advanced, and configure the advanced attributes of the

radio links.
● To configure XPIC radio links for OptiX RTN 905 1E:
a. Select XPIC.
c. After the configuration is complete on the local NE, click Synchronize to

synchronize the radio link configurations to the adjacent NE.
● To configure XPIC radio links for other OptiX RTN 900 products:
a. Select 1+0 and XPIC.
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/IS6/IS6–PLUS/IS8 runtime mode, the transmit power can reach the configured maximum
value in the corresponding modulation scheme only after the microwave link is available.
● Configure a 1+0 non-protected radio link.
● Configure 1+1 protected radio links.
● 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
● The IF boards and the ODUs to which the IF boards are connected have been
added on the NE Panel.
● The IF boards of an IF 1+1 FD/SD protection group have been configured in
two paired slots.
● The two RTN 905 1Es are connected using a service cascade cable.

NCE
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
● 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.
● 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.
● 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.
● 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.
● 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.
● You can set WTR Time(s) only when Revertive Mode is set to Revertive Mode. It is
recommended that you use the default value.
● Enable Reverse Switching is valid only when Working Mode is set to HSB or SD.
● Generally, it is recommended that you set Enable Reverse Switching to Enabled.
● 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.
● 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.
● 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
● An IF 1+1 protection group has been configured.

NCE
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
● Enable Reverse Switching is valid only when Working Mode is set to HSB or SD.
● Generally, it is recommended that you set Enable Reverse Switching to Enabled.
● 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.
● 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.
● It is recommended that Anti-jitter Time(s) take its default value.
● 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 IF board works in SDH, Hybrid (Native E1 + Ethernet) or Hybrid (STM-1 +
Ethernet) mode.

NCE
NOTE
● OptiX RTN 905 does not support this operation.
● When an N+0 service is converted into an N+1 service through the
configuration of the N+1 protection group, the original service is not
interrupted.
● N+1 protection for OptiX RTN 980 using CSHNA/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.

● 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 Protection from the Function Tree.
NOTE
If you create an N+1 protection group using the Web LCT, perform the following operations:
Configuration from the Function Tree. Click the N+1 Protection tab.
Step 2 Click Create.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
● The IF 1+1 protection must be configured.

NCE
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
● The IF N+1 protection must be configured.

NCE
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
● The IF 1+1 protection must be configured.

NCE
NOTE
Context
Two RTN 905 1E NEs are cascaded through a cascade cable and form a 1+1
protection group. Switching operations are conducted only on the main NE.
Procedure
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Step 2 In Protection Group, select the protection group for protection switching.
Step 3 In Slot Mapping Settings, select a working unit or the protection unit of the
protection group, and then right-click the selected unit.
Step 4 Choose the required switching mode from the shortcut menu.
The system displays the dialog box that indicates the successful operation.
Step 5 Click Close.
Step 6 Click Query Switching Status and check whether the switching is successful, and
then close the displayed prompt dialog box.
NOTE
If you perform IF 1+1 protection switching using the Web LCT, perform the following operations:
Select the working unit or the protection unit, right-click Query Switching Status and check
whether the switching is successful.
----End
A.5.8 IF N+1 Protection Switching

You can perform external switching on the IF N+1 protection by performing IF N+1
protection switching.

Prerequisites
● The N+1 protection protocol is enabled.

NCE
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

NCE

NOTE
Precautions
● Stopping the N+1 protection protocol causes a failure of the N+1 protection.
● When services are switched onto the protection channel, stopping the N+1
protection protocol causes switchover of the services back to the working
tunnel. At this time, if the working channel is normal, the services are
transiently interrupted. If the working channel is faulty, the services are
interrupted until the working channel is restored to normal or the N+1
protection protocol is started.
Procedure
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

NCE
NOTE

● OptiX RTN 910A, OptiX RTN 905 1E/2E/2F, OptiX RTN 950A, OptiX RTN 950
using CSHU/CSHUA/CSHUF, and OptiX RTN 980 using CSHNA/CSHNU support
EPLA.
● Only OptiX RTN 910A, OptiX RTN 950A, and OptiX RTN 950 using CSHU/
CSHUA boards support EPLA+.
● Only OptiX RTN 905 2F, OptiX RTN 950 using CSHU/CSHUA/CSHUF and RTN
950A using SLF2CSHO support super EPLA.
● Cascaded RTN 905 1E/2E/2F NEs support PLA/EPLA.
● For the limitations of PLA/EPLA/EPLA+, see Feature Dependencies and
Limitations of PLA/EPLA/EPLA+ in the Feature Description.
● When you create or delete a PLA group on an ISU2 or ISX2 board, the board is
cold reset.
Procedure
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.
● RTN 910A

● OptiX RTN 950A and OptiX RTN 950

PLA/EPLA/EPLA+
Super EPLA

NOTE
– When Scheduling Mode is Mode B, 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 set to Mode A, high-priority and low-priority services are
transmitted on both common-band links and E-band links. In this mode, implementing
inter-frequency AM.
– When Scheduling Mode is set to Mode A Access, it is similar to Mode A, but only
connect with Mode A Access.
– When Scheduling Mode is set to Mode B, a threshold can be set to determine the
priority of a service. 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.
● RTN 980L

● RTN 980

● RTN 905 1E/2E/2F


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 2F needs to be configured with cascade EPLA, the GE port on the
EM10 board can serve as the cascade port. It is recommended that the 10GE port serve
as the cascade port. The cascade port has two internal channels: channel 1 and channel
2. Channel 1 must connect to port 3-ISV8-1, and channel 2 must connect to port 3-
ISM8-2.
– 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
● A PLA/EPLA/EPLA+/Super EPLA group has been configured.

NCE
NOTE

Procedure
Step 2 Click Query. View the information about the PLA/EPLA/EPLA+/Super EPLA group
in Physical Link Aggregation List.
NOTE
● Minimum Active Links specifies the minimum number of available links in a PLA group and
helps to trigger ERPS switching even if not all members in the PLA group fail.
----End
A.5.12 Configuring Ethernet Frame Header Compression over

Air Interfaces
By default, the Ethernet frame header compression function is disabled.
Prerequisites
● The corresponding IF board has been added in the NE Panel.

NCE
NOTE
Procedure
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
● 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.
● The settings of Speed Transmission at L2 must be the same at both ends of a radio link.
● If Speed Transmission at L3 is set to Enabled, the IP packets transmitted at microwave
ports will be compressed to improve transmission efficiency.
● 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
● 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.

NCE
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

NCE
NOTE
Context
● RTN 910A/RTN 980/RTN 950A: AES-based encryption at air interfaces is
supported only by ISV3 boards in IS3 mode.
● RTN 950: AES-based encryption at air interfaces is supported only when
CSHU/CSHUA boards work with ISV3 boards in IS3 mode.
● RTN 980L: AES-based encryption at air interfaces is supported only by ISV3
boards in IS3 mode or LH ACCP mode.
● RTN 905 does not support AES-based encryption at air interfaces.
● AES-based encryption at air interfaces cannot be enabled when an ISV3
interconnects with an ISM6 board or an RTN 905.
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:

● Eight to 32 characters
● At least two types of the following characters:
Digit, uppercase letter, lowercase letter, and special character

Step 6 Click Apply.
----End
A.6 Managing the MSP

This section provides the operation tasks associated with MSP. Only the OptiX RTN
980 supports the Two-Fiber Bidirectional Ring MSP.
A.6.1 Configuring Linear MSP

You can configure linear MSP to protect services over the optical fibers between
two nodes.
Prerequisites
● The corresponding board must be added on the NE Panel.

NCE
NOTE
When an unprotected service is converted into a linear MSP service by configuring
the linear MSP, the original services are not interrupted.
Procedure
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
● In the case of the 1:N linear MSP, you need to configure bidirectional cross-
connections between the services and the working channels later. If extra
services need to be transmitted, it is necessary to configure bidirectional
cross-connections between the extra services and the protection channels.
● In the case of the 1+1 linear MSP, you need to configure bidirectional cross-
connections between the services and the working channels later.
A.6.2 Querying the Status of the Linear MSP

By using this operation, you can know the current information about the linear
MSP.
Prerequisites
● The linear MSP must be configured.


NCE
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
● The protection protocol is enabled.

NCE
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

NCE
NOTE
Precautions
● Stopping the ring MSP protocol causes failure of ring MSP.
● When services are switched onto the protection channel, stopping the ring
MSP protocol causes the services to switch back to the working channel. At
this time, if the working channel is normal, the services are transiently
interrupted; if the working channel is faulty, the services are interrupted until
the working channel is restored to normal or the protocol is started.
Procedure
Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to
be stopped.

Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that
is displayed.
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

NCE
NOTE
● Only OptiX RTN 980 support this operation.
● The number of nodes on an MSP ring should not exceed 16.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose
Configuration > Ring MS from the Function Tree.
Step 3 Click Yes.
The Create a Multiplex Section Ring dialog box is displayed.
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
● A ring MSP protection group has been configured.

NCE
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
● MSP Ring has been configured for a service.
● The MSP ring protocol has been enabled.

NCE
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.
box that is 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
● MSP Ring has been configured for a service.

NCE
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
● The corresponding boards have been added in the NE Panel.

NCE
NOTE
● When an unprotected service is converted into a linear MSP service by
configuring the packet-based linear MSP, the service is not interrupted.
● Only the 1:1 packet-based linear MSP can be created.
Procedure
Step 1 In the NE Explorer, select an NE from the Object Tree and choose Configuration >
Packet-based linear MS from the Function Tree.
The Create a 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
● A packet-based linear MSP group has been configured.


NCE
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
● The linear MSP protocol has been enabled.

NCE
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

NCE
NOTE
Precautions
● Disabling the linear MSP protocol causes the failure of the linear MSP.
● When services are switched to the protection channel, disabling the linear
MSP protocol switches the services back to the working channel. At this time,
if the working channel is normal, the services are transiently interrupted. If
the working channel is faulty, the services are interrupted until the working
channel is restored to normal or the linear MSP 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
● The corresponding source and sink boards must be added on NE Panel.

NCE
NOTE
Procedure
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
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
● The corresponding source and sink boards must be added on NE Panel.

NCE
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
● The corresponding source and sink boards must be added in the NE Panel.
● The E1 cross-connections must be created. The IF boards in the cross-
connections must support the E1 priority function. The E1 priorities must be
set already and need to be modified.

NCE

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

NCE
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
● The SNCP protection group must be configured.

NCE
NOTE
Procedure
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
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
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
● The cross-connections of the service must be configured and the service must
not be used.

NCE
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 Configuration from the Function Tree.
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
● The unidirectional cross-connection of the normal service must be configured
and the source of the cross-connection must be a line board.

NCE
NOTE
When this task is performed to convert a normal service into an SNCP service, the
original services are not interrupted.

Procedure
SDH/PDH 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 Configuration from the Function Tree.
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
operations:
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
operations:
Select the unidirectional service. Right-click the selected service and choose Convert to SNCP
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
● The SNCP cross-connection in the receive direction must be configured.
● The current service must be transmitted on the working path.

NCE
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
● TDM services must be configured.

NCE
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

NCE
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

NCE
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

NCE
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.

operation result.
----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

NCE
NOTE
Context
NOTE
● 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.
● 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

NCE
NOTE
Procedure
Configuration > PDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel).
Step 3 Select Port from the list box.
Step 4 Configure the parameters of PDH ports.
Step 5 Click Apply.

Step 6 Click 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

NCE
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

NCE
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.
operation result.
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.
operation result.
----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

NCE
NOTE

Procedure
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. Configure the signal flag in the V5 byte.
3. Click Apply.
4. 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
● The corresponding boards must be added in the NE Panel.

NCE
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
● 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.

● 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.

NCE
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
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.
● 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.

NCE
NOTE
Procedure
Configuration > Interface Management > PDH Interface from the Function
Tree.
Step 3 Select the required port and set the parameters for its advanced attributes.
Step 4 Click Apply.

----End
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
● The ports that travel services are set to Layer 1.

NCE
NOTE
Procedure
Configuration > 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
● Serial ports are added.

NCE

NOTE
Procedure
Configuration > 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
----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
● The Ethernet board must be added on the NE Panel.

NCE
NOTE
Procedure
Interface Management > Ethernet Interface from the Function Tree.
Step 3 Set basic Ethernet port attributes.

NOTE
● Specifies the level of services that a port carries.

● If Port Mode is Layer 2, the port can carry native Ethernet services.
● If Port Mode is Layer 3, the port can carry MPLS tunnels.
● If Port Mode is Layer Mix, the port can carry both native Ethernet services and MPLS
tunnels.
● This parameter specifies the method of the port to process the received packets.
● This parameter is valid only when Port Mode is Layer 2.
● If you set Encapsulation Type to Null, the port transparently transmits the received
packets.
● If you set Encapsulation Type to 802.1Q, the port identifies the packets that comply
with the IEEE 802.1q standard.
● If you set Encapsulation Type to QinQ, the port identifies the packets that comply with
the IEEE 802.1ad QinQ standard.
● The Ethernet ports of different types support different Working Mode. For details, see
the IDU Hardware Description.
● 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.
● 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.
● 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.
● 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

NCE
NOTE
Procedure

Step 2 Click the Flow Control tab.

Step 3 Configure the Ethernet port traffic control.
NOTE
● Auto-Negotiation Flow Control Mode is valid only when Working Mode is set to
Auto-Negotiation.
● 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
● OptiX RTN 900 supports only two auto-negotiation flow control modes, namely,
Disabled mode and Enable Symmetric Flow Control mode.
● An EM6D board supports only two auto-negotiation flow control modes, namely,
Disabled mode and Enable Symmetric/Dissymmetric Flow Control mode.
● Non-Autonegotiation Flow Control Mode is valid only when Working Mode is not set
to Auto-Negotiation.
● 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
● OptiX RTN 900 supports only two non-auto-negotiation flow control modes, namely,
Disabled mode and Enable Symmetric Flow Control mode.
● 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

NCE
NOTE

Procedure
Step 2 Click the Layer 2 Attributes tab.
Step 3 Set Ethernet port Layer 2 attributes.
NOTE
● 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.
● 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.
● If all the accessed services are frames with the VLAN tag (tagged frames), set TAG to
Tag Aware.
● If all the accessed services are frames without the VLAN tag (untagged frames), set TAG
to Access.
● If the accessed services contain tagged frames and untagged frames, set TAG to Hybrid.
● Default VLAN ID is valid only when TAG is set to Access or Hybrid.
● 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
● Port Mode of Ethernet ports are set to Layer 3.

NCE
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

NCE
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
● The corresponding IF board must be added to NE Panel.

NCE
NOTE
Procedure
Step 3 Set basic IF_ETH port attributes.
NOTE
● This parameter specifies the level of services that a port carries.

● If Port Mode is Layer 2, the port can carry native Ethernet services.
● If Port Mode is Layer 3, the port can carry tunnels.
● If Port Mode is Layer Mix, the port can carry both tunnels and Native Ethernet services.
● Encapsulation Type specifies the method of the port to process the received packets.
● This parameter is valid only when Port Mode is Layer 2.
● If Encapsulation Type is set to Null, the port transparently transmits the received
packets.
● If Encapsulation Type is set to 802.1Q, the port identifies the packets that comply with
the IEEE 802.1Q standard.
● 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

NCE
NOTE
Procedure
Step 3 Set IF_ETH port Layer 2 attributes.
NOTE
● 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.
● 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
● If all the accessed services are frames that contain the VLAN tag (tagged frames), set
Tag to "Tag Aware".
● If all the accessed services are frames that do not contain the VLAN tag (untagged
frames), set Tag to "Access".
● If the accessed services contain tagged frames and untagged frames, set Tag to
"Hybrid".
● Default VLAN ID is valid only when TAG is set to Access or Hybrid.
● 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
● Port Mode of the ports on IF boards are set to Layer 3.

NCE
NOTE
Procedure
Configuration > 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
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

NCE
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

NCE
NOTE
Procedure
Step 1 In the NE Explorer, select the desired board from the object tree. Choose
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
● 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.
● To disable XPIC on an XPIC-capable IF board, set this parameter to Disabled.
● This parameter must be set to the same value for both ends of a microwave link.
● If an NE needs to transmit IEEE 1588V2 packets, set this parameter to Enabled. If an NE
does not need to transmit IEEE 1588V2 packets, set this parameter to Disabled.
● Alarm And Performance Report can be specified for the RTN 905, RTN 910A, RTN 905
2F, and ISV3/ISM6/ISM8 boards on the RTN 980/RTN 980L/RTN 950/RTN 950A. If Alarm
And Performance Report is set to Disabled, alarms pertaining to the IF port and the
corresponding ODU will not be reported.
● The IF port on an ISU2/ISX2 board can interconnect only with the IF port that supports
the IS2 mode.
● The RTN 905 1E/2E supports the IS2 and IS3 modes. By default, it works in IS3 mode.
Running Mode must be set to the same value for the two IF units on an RTN 905 2E.
● The RTN 905 2F supports the IS8, IS6, and IS3 modes. By default, it works in IS8 mode.
Running Mode can be set to different values for the two IF units on an RTN 905 2F.
● The ISV3 board supports the IS2 and IS3 modes. By default, it works in IS3 mode.
● The IF ports on an ISM6 board support the IS2, IS3, IS6–PLUS, and IS6 modes. By
default, they work in IS6 mode. The two IF ports on an ISM6 board must work in the
same mode.
● The IF ports on an ISM8 board support the IS3, IS6, and IS8 modes. By default, they
work in IS8 mode. The two IF ports on an ISM8 board can work in different modes.
● It is recommended that two interconnected IF ports work in the highest-order mode
that they both support.
● Before changing the running mode of an IF port, remove services on the port.
● If IF ports are configured with services or 1+1, N+1, PLA/EPLA/EPLA+, or LAG protection,
Running Mode cannot be modified for them.
● 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
● 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.
● When AM Enable Status is set to Enabled, the radio link uses the corresponding
modulation scheme according to the channel conditions.
● 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.
● 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.
● 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
● For the IF boards that are configured with 1+1 protection, configure only the
ATPC attributes of the main IF board.
● The following procedure describes the ATPC parameter configurations in the
IF port configuration dialog box for the IF board. You can also configure ATPC
parameters in the Create XPIC Protection Group window.

NCE
NOTE
Procedure
Configuration > IF Interface from the Function Tree.
Step 2 Click the ATPC Attributes tab.

Step 3 Set the parameters of ATPC attributes.
NOTE
● The settings of the ATPC attributes must be consistent at both ends of a radio link.
● In the case of areas where fast fading severely affects the radio transmission, it is
recommended that you set ATPC Enable Status to Disabled.
● 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.
● 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).
● 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
● The corresponding IF boards must be added in the NE Panel.

NCE
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
● The corresponding IF boards must be added in the NE Panel.

NCE
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
● The corresponding IF board must be added.

NCE
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
● The corresponding IF boards have been added in the NE Panel.

NCE
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

NCE
NOTE
Context
● The IF port on an ISU2/ISX2 board can interconnect only with the IF port that
supports the IS2 mode.
● The RTN 905 1E/2E supports the IS2 and IS3 modes. By default, it works in IS3
mode. Running Mode must be set to the same value for the two IF units on
an RTN 905 2E.
● The RTN 905 2F supports the IS8, IS6, and IS3 modes. By default, it works in
IS8 mode. Running Mode can be set to different values for the two IF units
on an RTN 905 2F.
● The ISV3 board supports the IS2 and IS3 modes. By default, it works in IS3
mode.

● The IF ports on an ISM6 board support the IS2, IS3, IS6–PLUS, and IS6 modes.
By default, they work in IS6 mode. The two IF ports on an ISM6 board must
work in the same mode.
● The IF ports on an ISM8 board support the IS3, IS6, and IS8 modes. By
default, they work in IS8 mode. The two IF ports on an ISM8 board can work
in different modes.
● It is recommended that two interconnected IF ports work in the highest-order
mode that they both support.
● Before changing the running mode of an IF port, remove services on the port.
● If IF ports are configured with services or 1+1, N+1, PLA/EPLA/EPLA+, or LAG
protection, Running Mode cannot be modified for them.
● 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
● The corresponding ISX2 board has been added on the NE Panel.
● The AM function has been enabled by A.5.1 Configuring a Single-Hop Radio
Link.

NCE

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

NCE
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 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 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 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

Modulation Mode of change Manually Modulation Mode to the
the Guarantee AM lowered 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 unnecessary E1 services.
high-priority E1 2. Decrease Guarantee E1 Capacity.
services 3. Click Apply.

If... Then...
You need to 1. Increase Guarantee E1 Capacity.

increase the 2. If Enable E1 Priority is Enabled, increase Full E1
number of high- Capacity accordingly.
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.
NOTE
● Full E1 Capacity is the total number of high-priority E1
services and low-priority E1 services.
● 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 unnecessary E1 services.
low-priority E1 2. Decrease Full E1 Capacity.
services 3. Click Apply.
You need to 1. If Enable E1 Priority is Disabled, change Enable E1

increase the Priority 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.
● Full E1 Capacity is the total number of high-priority E1
services and low-priority E1 services.
● Adding low-priority E1 services does not affect original
E1 services.
----End
A.8.11 Setting ODU Port Parameters

This section describes how to set ODU port parameters, including the transmit
frequency attributes, power attributes, RFU/RFU-SD/ODU information, and
advanced attributes.

Prerequisites
NOTE
The two ports of the dual-channel ODU can be configured separately.
A.8.11.1 Setting ODU Transmit Frequency Attributes

The ODU transmit frequency attributes define the DOU transmit frequency and
T/R spacing.
Prerequisites
● The IF boards and the ODU to which the IF boards are connected must be

NCE
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
● 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.
● The difference between the transmit frequencies at both ends of a radio link by ODU
should be one T/R spacing.
● 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.
● 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.
● 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
● The IF boards and theODUs to which the IF boards are connected must be

NCE
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
● The IF boards and the ODUs to which the IF boards are connected must be

NCE
NOTE
Procedure
Step 1 Customize the configuration procedure by equipment.
Option Description
If the Equipment Type Is... Then...

Option Description
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
● 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.
● The maximum transmit power adjusted by using the ATPC function should not exceed
Maximum Transmit Power(dBm).
● 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
● 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.
● Power to Be Received(dBm) is set according to the network plan. When this parameter
takes the default value, the antenna misalignment indicating function is disabled.
● TX High 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
● The IF boards and the ODU to which the IF boards are connected must be

NCE
NOTE

Procedure
Step 3 Configure the ODU parameters, such as Configure Transmission Status.
NOTE
● 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.
● In normal cases, RF Loopback is set to Non-Loopback.
● 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
● Ethernet boards and IF boards have been added on the NE Panel.
● Port Mode has been set to Layer Mix for Ethernet boards and IF boards.

NCE
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
Configuration > Interface Management > Ethernet Virtual Interface from the
Function Tree.
Step 3 Choose New > Create Ethernet Virtual Interface.

The Create Ethernet Virtual Interface dialog box is displayed.
Step 4 Set VLAN sub-interface parameters.
Step 5 Click OK.
----End
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
● The Ethernet boards, or IF boards must be added to the NE Panel.

NCE
NOTE
Procedure
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
● 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.
● Set East Port or West Port to - for the sub-ring ERPS instance on an interconnection node.
● 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.
● This parameter generally takes the default value Revertive. You can set this parameter to
Non-Revertive according to the network plan.
● 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.
● To configure VLAN-based ERPS protection, configure VLAN List. The value must be a subset
of the ring network service VLAN. When more than two 802.1Q services are configured, this
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
● The ERPS protection instance must be created.

NCE
NOTE
Procedure
Ethernet 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 (Optional) Bind the ERPS multi-instance east-west port to the MEP.
NOTE
When you perform this step, you need to configure the MEPs as egress ports in advance.
Step 4 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
● Ethernet boards and IF boards have been added to the NE Panel.

NCE
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.
● For multi-ring networks, Compatible_Version for all ring nodes must be ver2.
● 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.
● 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
● A multi-ring ERPS instance has been created.

NCE
NOTE
NOTE
● 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.
● 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
● 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.
● Set Virtual Channel VLAN to the control VLAN ID of the sub-ring R-APS virtual channel.
● 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
● The mapping IF boards and RFUs have been added on the NE Panel.

NCE
NOTE
Precautions
● Understand the network topology and properly configure parameters for
switching upon multiple failures to ensure that proper switching can be
triggered on an ERPS sub-ring. Otherwise, normal services may be
interrupted. For details about the switching principles for minimization of
segmentation, see Feature Description.
● It is advised to configure a bound MEP for an interconnection node sub-ring
port when the network is normal.
● Modify Interconnected Node and Multi-point Failure only after multiple
failures occur. Restore the two parameters to default values immediately after
faults are rectified.

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

NCE
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

NCE
NOTE
Procedure
Step 2 Click Query.
Step 3 Query the status of the Ethernet ring protocol.
----End
A.9.2 Managing SEP

Ethernet ring protection switching (SEP) can be configured on the FE/GE ring or
Integrated IP microwave ring to protect the Ethernet service.
A.9.2.1 Creating SEP Protection Instances

SEP protection is configured by creating SEP instances.

Prerequisites

NCE
NOTE
Procedure
Ethernet Protection > SEP Management.
Step 2 Click New.The Create SEP Protected Instance dialog box is displayed.
Step 3 Set the parameters for the SEP protection instance.
Step 4 Click OK.
----End
A.9.2.2 Configuring the Port Blocking Mode

This topic describes how to configure the blocking mode for a port.

Prerequisites

NCE
NOTE
Procedure
Step 2 Click the Blocking Mode tab and set the priority of the port blocking mode.
Step 3 Click Apply.
----End
A.9.2.3 Configure the port priority

This topic describes how to Configure priority for a port.
Prerequisites

NCE
NOTE

Procedure
Step 2 Click the porttab and set the priority of the port.
Step 3 Click Apply.
----End
A.9.2.4 Configuring the Preemption Mode

This topic describes how to configure the preemption mode for port blocking after
an NE is reset.
Prerequisites

NCE
NOTE
Procedure
Step 2 Click Preemption Mode and select a preemption mode.

Step 3 Click Apply.
----End
A.9.2.5 Querying the Status of the Ethernet Ring Protocol

By performing this operation, you can discover the current status of Ethernet ring
protection switching (SEP).
Prerequisites
● The SEP configuration has been completed.

NCE
NOTE
Procedure
Step 2 Click Topology, Query the status of the Ethernet ring protocol.

----End
A.9.3 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.3.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
● The board on which the LAG port to be created must be added to the NE
Panel.

NCE
NOTE
Procedure
Interface 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
● When Automatically Assign is selected, LAG No. cannot be set.

● Revertive Mode can be set only when Load Sharing is set to Non-Sharing.
● 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.
● 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.
● System Priority indicates the priority of a LAG. The smaller the value of System Priority,
the higher the priority.
● WTR Time(min) takes effect only when Revertive Mode is Revertive Mode.
● 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; 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.3.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
● The board on which the LAG to be created must be added to NE Panel.

NCE
NOTE

Procedure
Function Tree.
Step 2 Click the Link Aggregation Parameters tab.
Step 3 Set Port Priority and System Load Sharing Hash Algorithm.
NOTE
● System Load Sharing Hash Algorithm is valid only when Load Sharing of a LAG is set to
Sharing.
● After the configuration data is deployed, System Load Sharing Hash Algorithm takes effect
for the entire NE.
----End
A.9.3.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
● The LAG must be created.

NCE

NOTE
Procedure
Function Tree.
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.4 Configuring Ethernet Services

The Ethernet service is classified into two types, namely, E-Line service and E-LAN
service.
A.9.4.1 Configuring the QinQ Link

Configuring the QinQ link is the prerequisite for configuring QinQ private line
services.

Prerequisites
● On associated ports, the Encapsulation Type is set to QinQ.

NCE
NOTE
Procedure
Ethernet 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.4.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

NCE

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.
● When the centralized forwarding mode is used, intra-board Native E-Line

services must be forwarded through the packet switching unit of a system
control board. Therefore, double backplane bandwidth resources of the
system control board are consumed.
● When the distributed forwarding mode is used, intra-board Native E-Line
services are directly forwarded by the switching units of the board. However,
this will restrict the functions of some packet switching units that depend on
system control boards. The restrictions include:
– Intra-board Native E-Line services do not support the LM function of
ETH-OAM. Therefore, the packet loss rate of the Native E-Line services
could not be tested using meter-free tests.
– The source and sink ports of intra-board Native E-Line services do not
support the LAG function. If the source or sink ports are configured with
the LAG function, the forwarding mode is automatically switched to
centralized mode.
● The default forwarding mode configured for an EM6T, EM6TA, EM6F, or
EM6FA board is centralized forwarding.
Other types of Ethernet services on an EM6T, EM6TA, EM6F, or EM6FA board and
all types of Ethernet services on other types of Ethernet boards are forwarded in
centralized mode.
Procedure
Step 1 Select an NE from the object tree in the NE Explorer. Choose Configuration >
Ethernet Service Forwarding Mode Management from the function tree.
Step 2 Modify the value of Ethernet Service Forwarding Mode.
Step 3 Click Apply.
----End
A.9.4.3 Configuring UNI-UNI E-Line Services (NCE)

This section describes how to create an E-Line service that is transparently
transmitted end to end or is transmitted based on VLANs.

Prerequisites
● The parameter Port Mode is set to Layer 2 for the UNI port that carries the
E-Line service.

NCE
Context
NOTE
● 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.
● 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.
● 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
Ethernet 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.4.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
● The parameter Port Mode is set to Layer 2 for the UNI port that carries the
E-Line service.

Web LCT
Context
NOTE
exceed 256.
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.4.5 Configuring NNI-NNI E-Line Services (Carried by QinQ Links)(NCE)

This topic describes how to configure QinQ-based E-Line services.
Prerequisites
● Ethernet boards have been added on the NE Panel.
● For ports that carry services, Port Mode has been set to Layer 2 and
Encapsulation Type has been set to QinQ.

NCE
Context
NOTE
exceed 256.

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.4.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
● For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Context
NOTE
exceed 256.

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.4.7 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)(NCE)

This topic describes how to configure E-Line services carried by QinQ links.
Prerequisites
● 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.

NCE
Context
NOTE
exceed 256.
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.4.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
● For ports that carry services, Encapsulation Type has been set to QinQ.

Web LCT
Context
NOTE
exceed 256.
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.4.9 Configuring UNI-NNI E-Line Services (Carried by PWs)(NCE)

This section describes how to configure E-Line services carried by PWs.
Prerequisites
● The Ethernet board is added on the NE Panel.
● For the UNI port that carries the service, Port Mode has been set to Layer 2.
For the NNI port that carries the service, Port Mode has been set to Layer 3.
● The tunnel that carries PWs is configured.

NCE
Context
NOTE
● 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.
● 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.
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.4.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
● The Ethernet board is added on the NE Panel.
● Port Mode is set to Layer 2 for the UNI ports that carry services.

Web LCT
Context
NOTE
by UNI-carried E-Line, VPLS, E-Aggr, and IEEE 802.1ad bridge-based E-LAN services must not
exceed 1024.
● 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.
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.4.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


● For the UNI ports that carry the service, Port Mode has been set to Layer 2
and Encapsulation Type has been set to 802.1Q or QinQ. For the NNI port
that carries the service, Port Mode has been set to Layer 3.
● The MPLS tunnels that carry PWs have been configured.

NCE
NOTE
Context
● Regardless of whether VLAN ID swapping is required by an E-AGGR service, a
VLAN forwarding table needs to be configured, specifying the source and sink
VLAN IDs of each VLAN service.
● If VLAN ID swapping is required for PW-based E-Line services, change the E-
Line services to an E-AGGR service.
● For an E-AGGR service aggregating services from multiple UNI ports to a PW,
the NNI port must be configured as the sink. For an E-AGGR service
aggregating services from multiple PWs to a UNI port, the UNI port must be
configured as the sink.
Procedure
Configuration > 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.4.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
● A UNI-UNI E-Line service has been created.
● When the SL91CSHUF is used, the VLAN forwarding tables can be configured
for the NE only when the tag attribute of the port is tag-aware.

NCE
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.4.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


NCE
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.4.14 Configuring IEEE 802.1d Bridge-Based E-LAN Services (NCE)

The E-LAN service refers to Ethernet service dynamic transmission in the
multipoint-to-multipoint mode by means of MAC addresses.
Prerequisites
● 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.

NCE
Context
An IEEE 802.1d bridge-based E-LAN service must be configured according to the
service model described in 802.1D Bridge-based E-LAN Service Models.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree. Choose Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
Step 2 Click New.

The New E-LAN Service dialog box is displayed.
Step 3 Set the basic attributes of the E-LAN service according to the network plan.

Step 4 Configure the ports mounted to the bridge on the UNI side.
1. Click UNI.
2. Click Configuration.
3. Configure the ports mounted to the bridge on the UNI side.
a. Select the port to be mounted to the bridge.
b. Click to mount the port to the bridge.

4. Click OK.
Step 5 Optional: Configure split horizon groups.

NOTE
● The port members that are added to the same split horizon group cannot communicate with
each other.
● You are advised to configure split horizon groups when two PWs do not need to
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.4.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.4.16 Configuring IEEE 802.1q Bridge-Based E-LAN Services (NCE)

An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into
several switching domains.
Prerequisites
● 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.

NCE
Context
● Configure services based on the service model described in 802.1Q Bridge-
based E-LAN Service Models.
● For the OptiX RTN 905, OptiX RTN RTN 910A, the OptiX RTN 950A and the
OptiX RTN 950 that houses CSHU/CSHUA boards, the total number of VLAN
IDs configured for all Ethernet services cannot exceed 1024. The total number
of VLAN IDs configured 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
each other.
3. Click .
4. Click OK.
----End
A.9.4.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
● 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.

network plan.

3. Click OK.

NOTE
each other.
2. Click New.

NOTE
4. Click OK.
Step 6 Click OK.
----End
A.9.4.18 Configuring IEEE 802.1ad Bridge-Based E-LAN Services (NCE)

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN
into several switching domains.
Prerequisites
● For the board that transmits the IEEE 802.1ad bridge-based E-LAN service,
Port Mode has been set to Layer 2.

NCE
Context
● 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
each other.
3. Click .

4. Click OK.
----End
A.9.4.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
● 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.

network plan.
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
each other.
2. Click New.

NOTE
4. Click OK.
Step 7 Click OK.
----End
A.9.4.20 Configuring PW-Carried E-LAN Services (NCE)

This topic describes how to configure PW-carried E-LAN services (VPLS services).
Prerequisites

● 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.

NCE
Context
● 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.4.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 transmit other Ethernet
services.
● For the OptiX RTN 905/950A/910A and the OptiX RTN 950 that houses CSHU/
CSHUA boards, the total number of VLAN IDs configured for all Ethernet
services cannot exceed 1024. The total number of VLAN IDs configured for all
Ethernet services does not include the number of VLAN IDs for E-LAN services
configured in VLAN Filtering Table. Ports in VLAN Filtering Table cannot be
used to transmit other Ethernet services.
● Only some system control, switching, and timing boards of the RTN 950/980
support VPLS, as listed in the following table.
Table A-8 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
● 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
each other.
3. Click .
4. Click OK.
----End
A.9.4.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


NCE
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-9 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
Configuration > VPLS Management from the Function Tree.
Step 2 Set the parameters according to the network plan.
NOTE
The default value of TPID (PW S-TAG) is 88A8.
----End
A.9.4.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
● The E-LAN services must be created.


NCE
NOTE
Procedure
Step 2 Add or delete logical ports connected to a VB.

NOTE
● To add or delete ports connected to the VB on the UNI side, click the UNI tab.
● 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.4.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
● The E-Line service is configured and this service is not used.

NCE
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.4.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
● A configured E-LAN service is not required.

NCE
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.5 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.5.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
● The E-LAN service must be created.

NCE
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.5.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


NCE
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.5.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

NCE
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.5.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

NCE
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.6 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

NCE
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.7 Managing the MSTP

The OptiX RTN 900 supports only the MSTP that generates the CIST.
A.9.7.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
● The boards where the member ports are located must be added in NE Panel.


NCE
NOTE
Procedure
Ethernet 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.7.2 Setting the Bridge Parameters of the MSTP

This topic describes how to set the bridge parameters and port parameters of the
MSTP.
Prerequisites
● The port group must be created.

NCE
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.7.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
● The port group must be created.

NCE
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.7.4 Querying the CIST Running Information

By querying the CIST running information, you can be familiar with the current
information of the CIST.

Prerequisites
● The MSTP port group must be created.

NCE
NOTE
Procedure
Step 2 Click the CIST Running Information tab.
Step 3 Click Query.
Step 4 Query the CIST running information.
----End
A.9.7.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

NCE
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.7.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

NCE
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.7.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

NCE
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
be added located from the drop-down list of Board.
2. Select the port to be added from Available Port
List.
3. Click .
A member port needs to 1. Select the port to be deleted from Selected Port
be deleted List.
2. Click .
NOTE

Step 5 Click OK.
----End
A.9.8 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.8.1 Configuring the IGMP Snooping Protocol

This topic describes how to configure the IGMP Snooping protocol for a specific E-
LAN service.
Prerequisites
● OptiX RTN 950A and RTN 950 (housing CSHU/CSHUA) does not support this
operation.

NCE
Procedure
Ethernet 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 V2 protocol or IGMP Snooping V3
protocol.
Step 4 Click Apply.
----End
A.9.8.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

NCE
Procedure
Function Tree.
Step 2 Click the Route Management tab.
Step 3 Click Query.
Step 4 Query the port information of the routers.
----End
A.9.8.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

NCE

Procedure
Function Tree.
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.8.4 Creating Static Router Ports

Static router ports are not aged.
Prerequisites
● The NNI port must be configured for the E-LAN service.

NCE
Procedure
Function Tree.
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.
2. 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.

3. Click OK.
----End
A.9.8.5 Creating a Member of a Static Multicast Group for V2

The members of a static multicast group are not aged.
Prerequisites
● The UNI port must be configured for the E-LAN service.

NCE
Procedure
Function Tree.
Step 2 Click the Route Member Port Management or Route Member Port
Management for V3 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

3. Click OK.
----End
A.9.8.6 Creating a Member of a Static Multicast Group for V3

The members of a static multicast group are not aged.
Prerequisites

NCE
Procedure
Function Tree.
Step 2 Click the Route Member Port Management or Route Member Port
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
3. Click OK.
----End
A.9.8.7 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

NCE
Procedure
Function Tree.

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.8.8 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
● Dynamic or static multicast member ports must be configured.

NCE
Procedure
Function Tree.
Step 2 Click the Data Count tab.
Step 3 Click Query.
Step 4 Calculate the IGMP packets.
----End
A.9.8.9 Adding SSM Mapping

By adding SSM Mapping, V2 can be compatible with the source selection function
of V3.
Prerequisites
● Dynamic or static multicast member ports must be configured.


NCE
Procedure
Function Tree.
Step 2 Click the SSM Mapping tab.
Step 3 Click New.
Step 4 Set the attributes of SSM mapping.

1. Set Service ID and Multicast IP Address and Multicast Address Mask.
2. Click Add and set the IP address of Multicast Source.
Step 5 Click OK.
----End
A.9.9 Managing the QoS

By managing the QoS, you can provide the services of different levels for different
service types.
A.9.9.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

● The board of the Ethernet ports must be added on NE Panel.

NCE
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
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.9.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

NCE
NOTE
and Mapping Relation Name is default map.
Procedure

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.9.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

NCE
NOTE

and Mapping Relation Name is default map.
Procedure
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 1. Select the board where the application port is
that uses the DS domain located from the drop-down list of Board.
2. Select the port to be added from the drop-down
list of Available Port.
3. Click .
You need to delete a port 1. Select the board where the application port is
that uses the DS domain located from the drop-down list of Board.
2. Select the port to be deleted from the port list
of Selected Port.
3. Click .
You need to change the Select a new packet type from the drop-down list
packet type identified by of Packet Type.
the port
NOTE

NOTE
● C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
● S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
● 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.
● 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.9.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

NCE
NOTE
Procedure
QoS Management > Diffserv Domain Management > Egress DSCP Mapping

Step 2 Choose Enabled or Disabled.
Step 3 Click Apply.
----End
A.9.9.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

NCE
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 >
Management from the function tree.

Step 4 Select the desired port and modify Enable Outbound Mapping.

Step 5 Click Apply.
----End
A.9.9.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

NCE
NOTE
Procedure
QoS 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
● 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.
● 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.
● 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.9.7 Modifying the Port Policy

This section describes how to change the parameter values of a created port
policy.
Prerequisites
● The port policy must be created.

NCE
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
----End
A.9.9.8 Creating Traffic

By creating traffic, you can configure ACL, CoS, CAR and shaping for a specified
traffic stream on a specified port.
Prerequisites

NCE
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.9.9 Creating a Port WRED Policy

This section describes how to create a port WRED policy (WRED stands for
weighted random early detection).
Prerequisites

NCE
NOTE
Procedure
QoS 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.9.10 Creating a Service WRED Policy

This section describes how to create a service WRED policy (WRED stands for
weighted random early detection).
Prerequisites

NCE
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
QoS 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.9.11 Creating a WRR Policy

This section describes how to create a WRR policy.
Prerequisites

NCE
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
QoS 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.9.12 Setting the Port That Uses the Port Policy

This section describes how to set the port that uses the port policy.
Prerequisites

NCE
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.9.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

NCE
NOTE
Context
Procedure
QoS 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
----End
A.9.9.14 Creating a V-UNI Group

This section describes how to create a V-UNI group and set bandwidth limitation
for the group.
Prerequisites
● The board on which the Ethernet port resides has been added on the NE
Panel.

NCE
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.9.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

NCE
NOTE
Context
Procedure
QoS 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
----End
A.9.9.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

NCE
NOTE
Context
Procedure
QoS 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
----End
A.9.9.17 Applying policies for Ethernet services

This section describes how to apply policies for Ethernet services.
Prerequisites
● An Ethernet service has been created.
● An policy has been created.

NCE
NOTE

Context
Procedure
Step 2 Select the Ethernet service and click QoS.
Step 3 Apply policies for Ethernet services.
Step 4 Click Apply and close the dialog box that is displayed.
----End
A.9.9.18 Configuring Port Shaping

This section describes how to configure traffic shaping for an egress port.
Prerequisites
● The Ethernet board must be created on the NE Panel.

NCE
NOTE
Procedure
QoS 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.
● 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.
● 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.
● 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.9.19 Configuring Bandwidth Limitation for MPLS Tunnels

This section describes how to configure bandwidth limitation for MPLS tunnels.
Prerequisites
● An MPLS tunnel has been created.

NCE
NOTE
Procedure
Configuration > 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.9.20 Configuring Bandwidth Limitation for PWs

This section describes how to configure bandwidth limitation for PWs carrying ETH
PWE3 services.
Prerequisites
● An ETH PWE3 service has been created.

NCE
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.9.21 Configuring Bandwidth Limitation for QinQ Links

This section describes how to configure bandwidth limitation for QinQ Links
carrying QinQ services.
Prerequisites
● An QinQ service has been created.

NCE

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.10 Using the ethernet service OAM

By using the ethernet service OAM, you can maintain Ethernet services in an end-
to-end manner.
A.9.10.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

NCE
NOTE
Procedure
Ethernet 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
● Maintenance Domain Level specifies the level of the maintenance domain.

● The values 0 to 7 indicates maintenance domain levels in an ascending order.
● MEPs transparently transmit OAM protocol packets if the packets have a higher level
than the parameter value.
● MEPs discard OAM protocol packets if the packets have a lower level than the
parameter value.
● 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.10.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
● The MD must be created.
● The Ethernet service must be created.

NCE
NOTE
Procedure
Function Tree.


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.10.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
● The MA must be created.

NCE
NOTE
Procedure
Function Tree.


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
● 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 specifies the direction of the MEP.
● 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.
● In the case of the tests based on the MP IDs, CC Status must be set to Active.
----End
A.9.10.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

NCE
NOTE

Procedure
Function Tree.
Step 3 Choose OAM > Manage Remote MEP Point. The Manage Remote MEP Point
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.10.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

NCE
NOTE

Procedure
Function Tree.
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
● 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.
● 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.10.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
● The MEP must be created.
● The remote MEPs must be created.

NCE
NOTE

● Only the MEP can enable the CC test and function as the receiving and
responding end in the test.
● During the CC check, the source MEP constructs and transmits continuity
check message (CCM) packets periodically. After receiving the CCM packets
from the source MEP, the sink MEP directly enables the CC function for this
source MEP. If the sink MEP fails to receive the CCM packets from the source
MEP within the check period (that is, 3.5 times of the transmit period), it
reports the alarm automatically.
● Performing a CC test does not affect the services.
Procedure
Function Tree.
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
● Before the CC test, you can set CC Test Transmit Period according to the actual
requirements.
● To disable a CC test, select the MEP where the CC test is performed and then choose
OAM > Deactivate.
NOTE
● Alternatively, you can enable a CC test by right-clicking an MEP and then choosing
Activate CC from the shortcut menu.
● Alternatively, you can disable a CC test by right-clicking an MEP and then choosing
Deactivate CC from the shortcut menu.
Step 4 Click Close.
----End
A.9.10.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
● The source and sink MEPs in the same maintenance domain must be created.
● The CC function must be enabled.


NCE
NOTE
● Only MEPs can initiate the LB test and function as the receive end in the test.
● During the LB test, the source MEP constructs and transmits the LBM frames
and starts the timer. If the sink MP receives the LBM frames, it sends the LBR
frames back to the source MEP. This indicates that the loopback is successful.
If the source MEP timer times out, it indicates that the loopback fails.
● Performing an LB test does not affect the services.
Procedure
Function Tree.
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
● 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.
● 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.10.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
● The source and sink MEPs in the same MD must be created.
● The CC function must be enabled.

NCE
NOTE
● Only MEPs can initiate the LT test and work as the termination point in the
test.
● During the LT test, the source MEP constructs and transmits the LTM frames
and starts the timer. All the MPs that receive the LTM frames send the LTR
frame response. According to the LTR frame response, you can verify all the
MIPs that pass from the source MEP to the sink MEP.
● Performing an LT test does not affect services.
Procedure
Function Tree.
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
● 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.
● 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 LT test result is displayed in the Detection Result
window.
----End
A.9.10.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

NCE
NOTE
Procedure
Function Tree.
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.10.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
● Source and sink maintenance end points (MEPs) in the same maintenance
domain (MD) have been created.

NCE
Context
For details about restriction on the features related to the operation, see Feature
Dependencies and Limitations.
Procedure
Configuration > Ethernet OAM Management > Ethernet Service OAM
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 Click the Statistics Group tab
ratio, delay, or delay variation and set required parameters.
You want to query the historical packet Click the History Group tab and
loss ratio, delay, or delay variation set 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 Click the RMON Setting tab.
the packet loss ratio, delay, or delay Then click the Event tab and set
variation required parameters.
You want to set the historical performance Click the RMON Setting tab.
monitoring period for the packet loss ratio, Then click the Object tab and set
delay, or delay variation required parameters.
----End
A.9.10.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
● E-LAN services have been created.

NCE
NOTE
Context
● Creation of MEPs is not a prerequisite for service loopback detection.
● During an E-LAN service loopback test, if a node on the network to which the
tested port is connected reports a loopback packet threshold-crossing event,
there is an E-LAN service loop on this node.
● This task can also be completed by choosing Service > Service Path View
from the main menu.
Procedure
Step 1 In the NE Explorer, select the desired NE and choose Configuration > Ethernet
Service Management > E-LAN Service from the Function Tree.
Step 2 Click Manual Loopback Detection tab.
Step 3 Select the services where service loopback detection will be performed and click
Start.
The Start Loopback dialog box is displayed.
Step 4 Set the desired parameters.

NOTE
● Vlans/CVLAN displays the VLAN ID of a loopback service. Loopback detection can be

performed for only one service one time.
● Loopback detection stops if no loopback detection packets are received until Packet
Timeout Period(s) expires.
● 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.10.12 Reactivating E-LAN Services

This section describes how to reactivate E-LAN services that are deactivated during
a service loopback detection process.

Prerequisites
● An E-LAN service port has been shut down due to a service loopback.

NCE
NOTE
Procedure
Step 2 Click the Loopback tab.
Step 3 Click Service Status List.
The Service Status List dialog box is displayed.
Step 4 Select the port where an E-LAN service needs to be reactivated and click Enable.
Close the dialog box that is displayed.
----End
A.9.10.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

NCE
NOTE
Context
● 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.
● Automatic loop detection is enabled by default upon service creation and the
port status change.
● 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.
● 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

● 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.
● 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.
● 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.
● 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.
● 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.
● 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.
● For VPLSs in IVL mode, when no UNI is configured, the NNI does not support automatic
service loop detection.
● 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 for handling the service is shutdown

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 the following figure,
the alarm location information indicates that the VUNI on port 3 on
board 5 in E-LAN 2 on NEs (9–44042) is disabled.
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
● Check the services before re-enabling the blocked services. If a loop exists, disrupt the
loop before re-enabling the blocked service.
● Service interruption persisting after the service is re-enabled indicates that a loop exists.
Delete the service and check the physical loop.
A.9.10.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
● An egress MEP has been created.

NCE
NOTE
Background
● Bandwidth notification can be configured only on an egress MEP.
● Bandwidth notification packets do not affect services.
Procedure
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.11 Using the ethernet port OAM

By using the ethernet port OAM, you can maintain the point-to-point Ethernet
links.
A.9.11.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

NCE

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
Ethernet 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
● 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.
● 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.11.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
● The OAM auto-discovery operation must successful on the equipment at both
ends.


NCE
NOTE
Procedure
Function Tree.
Step 3 Select the corresponding port and set Link Event Notification to Enabled.
----End
A.9.11.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
● 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.

NCE
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
Function Tree.
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.11.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
● The OAM auto-discovery operation must be successful at both ends of the
link.
● On the equipment that initiates the loopback, OAM Working Mode must be
set to Active.
● The equipment that responds to the loopback must support the remote
loopback.

NCE
NOTE
● If a port is capable of responding to loopbacks, it enters the loopback
responding state and reports the loopback responding alarm after receiving
the command of enabling the remote loopback function sent from the
opposite OAM port. In this case, the equipment that initiates the loopback
enters the loopback initiation state and reports the loopback initiation alarm.
● Generally, after the remote loopback function is enabled, service packets,
except the OAMPDU, are looped back at the remote end.

● After using the remote loopback function to complete the fault locating and
the link performance detection, you need to disable the remote loopback
function at the end where the loopback is initiated and then restore the
services. The alarm is automatically cleared.
Procedure
Function Tree.
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.11.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
● The required board is already added on the NE Panel.
● All the external physical ports on the Ethernet service processing board must
be enabled.

NCE
NOTE

Procedure
Step 3 Set Loopback Check to Enabled.
----End
A.9.12 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.12.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
● 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.

NCE
NOTE
Procedure
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.12.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
● QinQ services exclusively occupying UNI ports have been configured.
● E-Line services carried by PWs exclusively occupying UNI ports have been
configured.
NOTE
● For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and
Model 2 in QinQ-Based E-Line Service Models.
● For the service models of E-Line services carried by PWs exclusively occupying UNI ports, see
Model 3 in PW-Carried E-Line Services.

NCE
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.12.3 Configuring Point-to-Multipoint LPT

When you configure point-to-multipoint LPT, it is necessary to configure the
primary and secondary points.
Prerequisites
● 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
● L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a
point-to-multipoint manner.
● For the service models of QinQ services sharing UNI ports, see Model 3 in QinQ-Based E-
Line Service Models.
● 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.

NCE
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.12.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
● The corresponding board must be added to the NE Panel.

NCE
NOTE
Procedure
LPT 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.13 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
● Only the OptiX RTN 950 (housing CSHU/CSHUA), OptiX RTN 950A (housing
CSHO), OptiX RTN 905 1E/2E, and OptiX RTN 910A support this configuration.
● You are an NMS user with administrator rights or higher rights.
● Native Ethernet services or PW-carried Ethernet services have been created.

NCE
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
● Uplink/Downlink nodes can be set as VUNI or QinQ measurement points.

● Intermediate nodes can be set as VUNI, QinQ, or tunnel measurement points.
● For a VUNI measurement point, set the following parameters: Direction,
Service, Port, VLAN, and Priority.
● For a QinQ measurement point, set Direction, Service, and QinQ Link.
● For a tunnel measurement point, set Direction, Tunnel ID, Port, PW Label,
Service Tag Role, and PW Type.

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
● To stop a test, stop the test for an uplink node and then for a downlink node.
● 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 905does 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
● An EMS6 board has been added to the NE Panel.

NCE
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
● An ERPS instance has been created.

NCE
Procedure
Protection > 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

NCE
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
● The EFP8/EMS6 board where the LAG ports are located must be added in the
NE Panel.

NCE

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

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
NE Panel.

NCE
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
NE Panel.

NCE
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
● The EFP8/EMS6 board must be added in the NE Panel.

NCE
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


NCE
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.
● Set the attributes of the IEEE 802.1q bridge.
● 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.
the bound path.


click .
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
● Ethernet LAN services must be created.


NCE
Procedure
Tree.
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
● The IEEE 802.1q/802.1ad bridge-based Ethernet LAN services must be created.
● In the case of IEEE 802.1ad bridge-based Ethernet LAN services, the learning
mode of the VB must be IVL.
Procedure
Tree.
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

NCE
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.

the bound path.


click .
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


NCE
Procedure
Tree.
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.
the bound path.


click .
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
● The Ethernet private line service must be configured and the service is not
used.


NCE
Procedure
Tree.
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
● The Ethernet LAN services must be configured and the service is not used.

NCE
Deleting an Ethernet LAN service involves the following tasks:
1. Deleting the VLAN filtering table
2. Deleting the service mounting configuration
Procedure
Tree.
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
● The Ethernet LAN services must be created.

NCE
Procedure
Tree.
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

NCE
Procedure
Tree.
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


NCE
Procedure
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

NCE
Procedure
Tree.
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

NCE
Precautions
● In the case of EVPLAN services, you can query the capacity of a MAC address
table where MAC addresses are queried based on VLAN IDs and the capacity
of a MAC address table where MAC addresses are queried based on VB logical
ports.
● In the case of EPLAN services, you can query the capacity of a MAC address
table where MAC addresses are queried based on VB logical ports.
Procedure
Tree.
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

NCE
Precautions
Ethernet ports FE1 to FE8 on an EFP8 board correspond to PORT1 to PORT8
respectively. PORT9 on an EFP8 board is used to connect the EoPDH plane to the
packet plane. PORT9 is provided by the Ethernet switching unit of an EFP8 board
and is connected to the EoPDH plane. PORT9 forwards Ethernet services from the
packet plane to FE ports or VCTRUNKs on an EFP8 board.
Ethernet ports GE1 and GE2 on the EMS6 board correspond to PORT1 and PORT2
respectively; Ethernet ports FE1 to FE4 on an EMS6 board correspond to PORT3 to
PORT6 respectively. PORT7 on an EMS6 board is used to connect the EoS plane to
the packet plane. PORT9 is provided by the Ethernet switching unit of an EMS6
board and is connected to the EoS plane. PORT9 forwards Ethernet services from
the packet plane to FE/GE ports or VCTRUNKs on an EMS6 board.
Procedure
Step 1 In the NE Explorer, select the EFP8/EMS6 board and then choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree.
Step 2 Select External Port.
Step 3 Set the basic attributes of the port.
1. Click the Basic Attributes tab.
2. Set the basic attributes of the port.
3. Click Apply. Then, close the dialog box that is displayed.

Step 4 Set the flow control mode of the port.
1. Click the Flow Control tab.
2. Set the flow control mode of the port.

Step 5 Set the TAG attribute of the port.
1. Click the TAG Attributes tab.
2. Set the TAG attribute of the port.

Step 6 Set the network attributes of the port.

1. Click the Network Attributes tab.
2. Set the network attributes of the port.
Step 7 Set the advanced attributes of the port.

1. Click the Advanced Attributes tab.
2. Set the advanced attributes of the port.
----End
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

NCE
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.
the bound path.


click .
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

NCE

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

NCE
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.
click .

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

NCE
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

NCE
Procedure
Configuration > Layer-2 Switching Management > Spanning Tree from the
Function Tree.
Step 2 Set bridge parameters.
1. Click the Bridge Parameters tab.
2. Set bridge parameters.

3. Click Apply.
Step 3 Set port parameters.
1. Click the Port Parameters tab.
2. Set port parameters.
3. Click Apply.
Step 4 Optional: If Protocol Type is set to RSTP, specify the point-to-point attribute of
the Ethernet port.
1. Click the Point to Point Attribute tab.
2. Set the point-to-point attribute of the port.
3. Click Apply.
----End
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
● The STP or RSTP must be enabled for the bridge.

NCE
Procedure
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
● The VLAN filtering table must be created.

NCE
Procedure
Configuration > Layer-2 Switching Management > IGMP Snooping Protocol
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
● The VLAN filtering table must be created.
● The IGMP Snooping protocol must be enabled for the bridge.

NCE
Procedure
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

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

NCE
Procedure
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

NCE

Procedure
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
● The associated Ethernet services must be created.

NCE
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

NCE
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

NCE
Procedure
Configuration > QoS Management > Flow Management from the Function Tree.
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
● The flow must be created.
● The CAR/CoS must be created.

NCE

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

NCE
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object
Tree and choose Configuration > QoS Management > Port Shaping
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

NCE
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

NCE
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board from the Object
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

NCE
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
● The MD must be created.

NCE
Procedure
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 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
● The Ethernet services must be created and activated.
● The MD and MA must be created.

NCE
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
Function Tree.
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:
● Activate the CC and set the sending period of the CC test.
● 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
● The Ethernet services must be created and activated.
● The MD and MA must be created.
● The MEPs must be created.

NCE
● Only the MEP can enable the continuity test and function as the receive
respond end for the test.
● The source MEP constructs CCM packets and transmits them periodically.
After receiving the CCM packet from the source MEP, the sink MEP directly
enables the CC function for this source MEP. If the sink MEP fails to receive
the CCM packet from the source MEP within the check period (that is, 3.5
times of the transmission interval), it reports the specific alarm automatically.
● Performing a CC test does not affect the services.
Procedure
Function Tree.

Step 2 Select the node to be monitored, click OAM Operation, and select Activate CC.
NOTE
● Before the CC test, you can set CCM Sending Period(ms) according to the actual
requirements.
● 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
● Alternatively, you can enable a CC test by right-clicking an MEP and then choosing
Activate CC from the shortcut menu.
● Alternatively, you can disable a CC test by right-clicking an MEP and then choosing
Inactivate CC from the shortcut menu.
----End

the source MEP and any MP in the same maintenance association (MA).
Prerequisites
● In the case of a standard MP, you must activate CC before an LB test.

NCE
● Only an MEP can initiate an LB test.
● During the LB test, the source MEP constructs and transmits the LBM frames
and starts the timer. If the sink MP receives the LBM frames, it sends the LBR
frames back to the source MEP. This indicates that the loopback is successful.
If the source MEP timer times out, it indicates that the loopback fails.
● Performing an LB test does not affect the services.
Procedure
Function Tree.
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
● 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.
● 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
● In the case of a standard MP, you must activate CC before an LT test.

NCE
● Only an MEP can initiate the LT test, and the MEP can work as the receive
end in the test.
● During the LT test, the source MEP constructs and transmits the LTM frames
and starts the timer. All the MPs that receive the LTM frames send the LTR
frame response. According to the LTR frame response, you can verify all the
MIPs that pass from the source MEP to the sink MEP.
● Performing an LT test does not affect the services.
Procedure
Function Tree.

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
● Only a standard MP supports this function.

NCE
Procedure
Function Tree.
Step 2 Select the node to be monitored. Double-click or right-click AIS Active Status and
then select Active or Inactive.

NOTE
● 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.
● 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.
● 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.
● 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
● You must be aware of the IP addresses of the source MP and the sink MP in
the ping test.

NCE
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
Function Tree.
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

NCE
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
Function Tree.
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

NCE
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
● 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.
● 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
● The OAM auto-discovery operation must be successful on the equipment at
both ends.

NCE
After the OAM auto-discovery operation is successful at both ends, the link fault
detection and performance detection are automatically started.
● The local end can notify the opposite end of link fault events only if Remote
Alarm Support for Link Event is set to Enabled at the local end.
● The local end can notify the opposite end of link performance events only if
Remote Alarm Support for Link Event is set to Enabled and if the
monitoring time and error frame thresholds are configured at the local end.
● After Remote Alarm Support for Link Event is set to Enabled at the
opposite port, if the opposite end detects link performance degradation, you
can query the ETHOAM_RMT_SD alarm, which is reported on the local end, by
using the NMS. According to the alarm, you can determine the type of the
link performance event.
● After Remote Alarm Support for Link Event is set to Enabled at the
opposite port, if the opposite equipment detects a link fault event or
encounters a fault that makes the equipment fail to be restored (such as a
power failure), you can query the ETHOAM_RMT_CRIT_FAULT alarm, which is
reported at the local end, by using the NMS. Based on the alarm, you can
determine the fault type.

Procedure
Tree.
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
● 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.

NCE
The local end notifies the opposite end after detecting a link event in the receive
direction under the following conditions:
● The OAM auto-discovery operation is successful.
● Remote Alarm Support for Link Event is set to Enabled and the monitoring
time and error frame thresholds have been configured at the local end.
If Remote Alarm Support for Link Event is also set to Enabled at the opposite
end, the opposite end notifies the local end after detecting a link event, and then
the local end generates the corresponding alarm.
Procedure
Tree.

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
● The OAM auto-discovery operation must be successful on the equipment at
both ends.
● On the equipment where the loopback is initiated, OAM Working Mode must
be set to Active.
● The equipment that responds to the loopback must support remote
loopbacks.

NCE
● If a port is capable of responding to loopbacks, it enters the Respond
Loopback of Remote state and reports the loopback responding alarm when
receiving the command of enabling the remote loopback function sent from
the opposite OAM port. In this case, the equipment that initiates the loopback
enters the loopback initiating state and reports the loopback initiating alarm.
● Generally, after the remote loopback function is enabled, service packets,
except the OAMPDU packets, are looped back at the remote end.
● After using the remote loopback function to locate faults and test link
performance, you should disable the remote loopback function at the end
where the loopback is initiated and then restore the services. At this time, the
alarm clears automatically.
Procedure
Tree.

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
● The PORT-based Ethernet private line services must be created and activated.
● The data services must be configured as EPL services that are transmitted
from PORTs to VCTRUNKs and do not carry any VLAN tags.
● An Ethernet port on which the LPT function is enabled must be in auto-
negotiation mode.

NCE
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
● The VLAN-based EVPL services must be created and activated.
● An Ethernet port on which the LPT function is enabled must be in auto-
negotiation mode.

NCE
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.
● The data services are displayed in the tree topology.
● The data service topology is consistent with the topology of the LPT.
Procedure
Configuration > Ethernet Interface Management > LPT Management from the
Function Tree.
Step 2 Click PtoMP LPT. Then, the LPT Management dialog box appears.

Step 3 Click New.

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

NCE
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

NCE
NOTE

Procedure
Tree.
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

NCE
NOTE
Procedure
Tree.
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


NCE
NOTE
Procedure
Tree.
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

NCE
NOTE
Procedure
> 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

NCE
NOTE
Procedure
Configuration > 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

NCE
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer. Choose
Tree.
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
● Tunnels/PWs have been created.

NCE
NOTE

Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer.
If... Then...
The MPLS tunnel 1. In the NE Explorer, select the required NE from the
OAM standard needs Object Tree and choose Configuration > MPLS
to be changed Management > 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
standard needs to be Object Tree and choose Configuration > MPLS
changed Management > 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
● MEG IDs adopt the IP-based format after the OAM standard is changed from Y.1711 to Y.
1731.
● 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
● The port attributes are set correctly.
● The LSR ID of each NE is set correctly.

NCE
NOTE
Procedure
Function Tree.
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
● The port attributes have been correctly configured.
● The LSR ID of each NE has been correctly configured.

NCE

NOTE
Procedure
Function Tree.
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
● MPLS tunnels are configured correctly.

NCE
NOTE
Procedure
Function Tree.
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
● The MPLS tunnel has been created.

NCE
NOTE

Procedure
Function Tree.
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
● An MPLS tunnel is configured correctly and is no longer used to transmit
services.

NCE
NOTE
Procedure
Function Tree.
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
● MPLS tunnels are created and enabled.
● Node Type is set to Ingress or Egress for tunnels.

NCE
NOTE

Procedure
Function Tree.
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
● MPLS tunnels are created and enabled.

NCE
NOTE
Procedure
Function Tree.
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
● The MPLS OAM (Y.1711) function has been enabled and related parameters
have been configured.

NCE
NOTE
Procedure
Function Tree.
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
● For unidirectional tunnels, this operation task can be performed only for a tunnel whose
Node Type is Ingress.
● For bidirectional tunnels, this operation task cannot be performed if Node Type is
Transit.
● After the MPLS OAM (Y.1711) function is enabled, CV/FFD detection is enabled by
default.
NOTE
● You can select more than one tunnel at a time by pressing and holding down the Ctrl
key.
● 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
● The MPLS OAM detection function has been enabled.

NCE
NOTE
Procedure
Function Tree.
Step 2 Select a navigation path based on the OAM protocol type used by a tunnel.
● If the tunnel uses MPLS OAM (Y.1711), query the LSP running status
according to Click the OAM Parameter tab..
● If the tunnel uses MPLS-TP OAM, click the MPLS-TP OAM tab page.
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
key.
● 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
● The MPLS OAM (Y.1711) detection function has been enabled.
● The tunnel is not configured in any protection group.

NCE
NOTE
Procedure
Function Tree.
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
key.
● 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

NCE

NOTE
Procedure
Function Tree.
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
● If LSP ping uses the IPv4 UDP response mode, all the nodes on the tunnel must support
DCN communication over IP protocols.
● 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


NCE
Procedure
Function Tree.
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
● If LSP traceroute uses the IPv4 UDP response mode, all the nodes on the tunnel must
support DCN communication over IP protocols.
----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
● The MPLS tunnel has been configured, with its ingress/egress node as an MEP.
● The MPLS-TP tunnel OAM standard has been changed to Y.1731.

NCE
NOTE
Procedure
Function Tree.
Step 2 Click the MPLS-TP OAM tab.
Step 3 Click the MEP tab.
Step 4 Set OAM Status to Enabled and set other OAM parameters.
----End
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
● The MPLS tunnel has been created and the newly created MIP node is a
transit node.
● The MPLS-TP tunnel OAM standard has been changed to Y.1731.
● Global OAM parameters have been configured.

NCE
NOTE

Procedure
Function Tree.
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
● An NE allows for only one MIP for one tunnel.

● 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
● The MPLS-TP tunnel OAM has been enabled and OAM parameters have been
configured.

NCE
NOTE
Procedure
Function Tree.

Step 4 Select one or more tunnels and choose OAM Operation > Start CC.
NOTE
● Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual
requirements.
● 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

the source MEP and the sink MEP or an MIP.
Prerequisites
● MPLS-TP tunnel OAM has been enabled for both the source MEP and the sink
MEP/MIP and OAM parameters have been configured.

NCE
NOTE
Procedure
Function Tree.
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
● MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and
OAM parameters have been configured.

NCE
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
● MPLS-TP tunnel OAM has been enabled for both the source and sink MPs and

NCE
This task is supported only when the configuration is performed in end-to-end
mode on the NCE.
RTN 950A housing CSHOF and RTN 905 2F does not support this operation.

NOTE
● 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 Searching for MPLS Tunnels and PWE3 Services.
● 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 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu.
The tunnels that meet the criteria are listed in the query result.
Step 3 Right-click the desired tunnel and choose Performance > Create Monitoring
Instance from the shortcut menu.
Step 4 Query the variation of an MPLS tunnel according to testing instances in the NCE
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
● The MPLS-TP tunnel OAM has been enabled and OAM parameters have been
configured.

NCE
NOTE
Context
operation.
RTN 905 2F does not support this operation.

Procedure
Function Tree.
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
● MPLS-TP tunnel OAM has been enabled for both the source MP and the sink
MP and OAM parameters have been configured.

NCE
● This task is supported only when the configuration is performed in end-to-end
mode on the NCE.
● OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support
this operation.
● RTN 905 2F does not support this operation.
Procedure
Step 1 Choose Service > Static Tunnel > Manage Tunnel from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all
MPLS tunnels that meet the filter conditions.
Step 3 Right-click the desired tunnel and choose OAM > MPLS-TP OAM Test from the
shortcut menu.

Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.
Step 6 View the test result in Test Statistics.
----End
A.11.3 Managing MPLS APS Protection Groups

MPLS APS is the commonest protection mode for MPLS tunnels.
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
● The working and protection MPLS tunnels have been created.
● MPLS OAM as been enabled for both working and protection MPLS tunnel in
the protection group.
● The protection tunnel cannot carry extra services.
● PW APS protection is not configured for the service.

NCE
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
> 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
● The MPLS APS protection group has been created.
● The MPLS APS protocol has been enabled.

NCE
NOTE
Procedure
Configuration > 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.
box that is 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
● The MPLS APS protocol has been enabled.

NCE
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.
box that is 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

NCE
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


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
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
● PW-carried services have been configured.

NCE
NOTE
Procedure
Configuration > 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

NCE
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
Tree.
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
● PW-carried services have been configured.

NCE
NOTE
Procedure
Tree.
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
● A PW has been created and enabled.


NCE
NOTE
Procedure
Tree.
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
● If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must
----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
● A PW has been created and enabled.

NCE
NOTE
Procedure
Tree.
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
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
● If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must
----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
● The PW has been configured, with its T-PE as an MEP.
● The MPLS-TP PW OAM standard has been changed to Y.1731.

NCE
NOTE
Procedure
Tree.
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
● The MS-PW has been created and the newly created MIP node is an S-PE
node.
● The MPLS-TP PW OAM standard has been changed to Y.1731.
● Global OAM parameters have been configured.

NCE
NOTE

Procedure
Tree.
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
● An NE allows for only one MIP for one MS-PW.

● 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
● The MPLS-TP PW OAM has been enabled and OAM parameters have been
configured.

NCE
NOTE

Procedure
Tree.
Step 4 Select one or more PWs and choose OAM Operation > Start CC.
NOTE
● Before the CC test, set CC Packet Priority and CC Packet Interval (ms) based on actual
requirements.
● 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

the source MEP and the sink MEP or an MIP.
Prerequisites
● MPLS-TP PW OAM has been enabled for both the source MEP and the sink
MEP/MIP and OAM parameters have been configured.

NCE
NOTE
Procedure
Tree.


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
● MPLS-TP PW OAM has been enabled for both the source and sink MPs and

NCE
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
● MPLS-TP PW OAM has been enabled for both the source and sink MPs and

NCE
This task is supported only when the configuration is performed in end-to-end
mode on the NCE.
RTN 950A housing CSHOF and RTN 905 2F does not support this operation.

NOTE
● 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 Searching for
MPLS Tunnels and PWE3 Services.
● To perform performance measurement for an PW in the NE Explorer, select the desired PW,
right-click, and choose Performance Statistics Management from the shortcut menu. In
the displayed dialog box, create the corresponding monitoring instance. Note that the PE at
both ends must be configured with the corresponding performance monitoring instance for
this PW. Otherwise, errors occur during performance measurement.
Procedure
Step 1 Choose Service > PWE3 Sevice > Manage PWE3 Sevice from the Main Menu.
The PWs that meet the criteria are listed in the query result.
Step 3 Right-click the desired PW and choose Performance > Create Monitoring
Instance from the shortcut menu.
Step 4 Query the variation of a PW according to the testing instances in the NCE 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
● The MPLS-TP PW OAM has been enabled and OAM parameters have been
configured.

NCE
NOTE
Context
operation.
RTN 905 2F does not support this operation.

Procedure
Tree.
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
● MPLS-TP PW OAM has been enabled for both the source MP and the sink MP
and OAM parameters have been configured.

NCE
● This task is supported only when the configuration is performed in end-to-end
mode on the NCE.
● OptiX RTN 950 housing CSHU/CSHUA and OptiX RTN 950A do not support
this operation.
● RTN 905 2F does not support this operation.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the dialog box that is displayed, click Filter to set filter conditions. Query all
PWs that meet the filter conditions.
Step 3 Right-click the desired PW and choose PW OAM > TP OAM Test from the
shortcut menu.

Step 4 Select Test from the drop-down menu. Click Parameter to set the test parameters.
Step 5 Select the NE to initiate the TST test and click Run.
Step 6 View the test result in Test Statistics.
----End
A.11.5 Managing a PW APS/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
● MPLS APS protection is not configured for the service.
● The tunnel carrying the working and protection PWs has been created.

NCE
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.
● During initial service configuration, set Protection Type to PW APS, create

the working and protection PWs, use the PWs to configure a PW APS
protection group.
● If services are already configured, create the PW APS protection group in the
Protection Group tab page.
● For SS-PWs and MS-PWs, configuration of the PW APS protection group
needs to be done on both source NE and sink NE.
NOTE
● This topic describes how to configure PW APS after services are configured.
● 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
● When the PW APS protection group is created, the PW OAM function is automatically
enabled to detect the PW status.
● 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
● MPLS FPS protection is not configured for the services.
● The tunnels carrying the working and protection PWs have been created.

NCE
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.
● During initial service configuration, set Protection Type to PW APS, create

the working and protection PWs, use the PWs to configure a PW FPS
protection group.
● If services are already configured, create the PW FPS protection group on the
Protect Group tab page.
● For SS-PWs and MS-PWs, configuration of the PW FPS protection group needs
to be done on the both source NE and sink NE.

NOTE
● This topic only describes how to configure PW FPS after services are configured.
● 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 Protection 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
● When the PW FPS protection group is created, the MPLS-TP OAM function is
automatically enabled to detect the PW status.
● 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
● The mapping between a slave protection pair and a PW APS protection group
has been specified.
● MPLS APS protection is not configured for the service.
● The tunnel carrying the working and protection PWs has been created.

NCE
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.
● During initial service configuration, set Protection Type to Slave Protection

Pair, create the working and protection PWs, use the PWs to configure a slave
protection pair.
● If services are already configured, create the slave protection pair in the
Protection Group tab page.
● For SS-PWs and MS-PWs, binding of a slave protection pair to a PW APS
protection group requires that the slave protection pair is added on both the
source NE and sink NE.
NOTE
● This topic describes how to configure a slave protection pair after services are configured.
● 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
● The PW APS protection group has been created.
● The PW APS protocol has been enabled.

NCE

NOTE
Procedure
Step 2 Click the PW APS Management tab.
Step 3 Click Query, and then close the dialog box that is displayed. Check basic
information about the protection group.
NOTE
If a slave protection pair is configured, information about the slave protection pair is
displayed at the lower part of the main interface after you select the protection group.
Step 4 Select the required protection group. Click Function > Query Switching Status,
and then close the dialog box that is displayed. Check the status of the protection
group.
----End
A.11.5.5 Triggering PW APS Switching

This topic describes how to trigger an external PW APS switching.
Prerequisites
● The PW APS protocol has been enabled.

NCE
NOTE
Procedure
Step 3 Select the required protection group, click Function, and then select the required
switching mode from the drop-down list.
NOTE
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

NCE
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

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:
● Select the required protection group, right-click the protection group, and choose Start
Protocol or Stop Protocol from the short-cut menu.
● 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
● The attributes of the UNI port that carries the CES service have been
configured. That is, Port Mode has been set to Layer 1, and Frame Format
and Frame Mode have also been configured.
● The MPLS tunnel that carries the PW has been configured.

NCE
NOTE
● Generally, UNI-NNI CES services are configured on the equipment. Therefore,
this topic uses a UNI-NNI CES service as an example to describe how to
configure CES services.

● It is recommended that you create protection information before creating a

CES service. In this configuration example, Protection Type is set to No
Protection. For details on how to configure protection information, see A.
11.5.1 Creating a PW APS Protection Group and A.11.5.3 Configuring Slave
Protection Pairs of PW APS.
Procedure
> CES Service Management from the Function Tree.
Step 2 Click New.
The Create CES Service dialog box is displayed.
Step 3 Set Mode to UNI-NNI. Configure basic information about the CES service carried
by a PW.
NOTE
● If Mode is UNI-NNI, you can configure advanced attributes of the PW.

● 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 QoS and set the EXP value for the CES service.
NOTE
It is recommended that you set EXP to None.

Step 6 Click Advanced Attributes and set parameters for the advanced attributes.
Step 7 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
● CES services have been created.

NCE
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
● CES services have been created.

NCE
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
● The CES service has been created and will no longer be used.
● No ACR clock has been configured for the CES service.

NCE

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

NCE
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
● For ATM/IMA E1 services, set Port Mode in PDH Interface to Layer 2.
● For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1
and configure A.8.7 Setting Serial Port Parameters.

NCE

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
● If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more
E1 ports, select E1 in Level.
● 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

NCE
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
● 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.
● 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.
● 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.
● 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.
● 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

NCE
NOTE
Context
NOTE
Procedure
Step 2 Click the ATM Interface Management tab.
Step 3 Configure and adjust the ATM port attributes.

NOTE
● 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.
● NNI: the port connecting network-side devices. For example, the NNI port applies to the
network-side interface on the common ATM network.
● 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.
● 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

NCE
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

NCE
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
● Generally, UNIs-NNI ATM services are configured on the OptiX RTN 900.
Therefore, this topic uses a UNIs-NNI ATM service as an example to describe
how to configure ATM PWE3 services.
● Before creating ATM PWE3 services, you need to bind member links to the
ATM TRUNK, set the parameters of the IMA group, and create the MPLS
tunnels that carries PWs.

NCE

NOTE
● The OptiX RTN 905 does not support ATM/IMA services.
● To create ATM PWE3 services (UNIs-NNI), it is recommended that you create
services before configuring PW protection. Configuration will be simplified in
this manner.
● In this configuration example, Protection Type is set to No Protection. For
details on how to configure PW protection, see A.11.5.1 Creating a PW APS
Protection Group and A.11.5.3 Configuring Slave Protection Pairs of PW
APS.
Procedure
> ATM Service Management from the Function Tree.
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 Basic 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
● ATM PWE3 services are already created and their parameters need to be
modified according to the planning information.

NCE
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


NCE
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

NCE
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

NCE
NOTE
Context
NOTE
The OptiX RTN 905 does not support ATM traffic management.
Procedure
> 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
● 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.
● CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
● EF: fast forwarding, applicable to services of low transmission delays and low packet loss
rates.
● 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.
● 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


NCE
NOTE
Context
NOTE
Procedure
Step 3 Select the required ATM-Diffserv domain and modify its parameters according to
the planning information.
NOTE
● 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.
● CS6 to CS7: highest service classes, mainly applicable to signaling transmission.
● EF: fast forwarding, applicable to services of low transmission delays and low packet loss
rates.
● 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.
● BE: best effort, applicable to services that do not require special processing.

----End
A.11.9.3 Creating an ATM Policy

This topic describes how to create an ATM policy for an ATM connection.
Prerequisites

NCE
NOTE
Context
NOTE
Procedure
> QoS 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

NCE
NOTE
Context
NOTE

Procedure
> QoS Management > Policy Management > ATM Policy from the Function
Tree.
Step 3 Select the required ATM policy and modify its parameters according to the
----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

NCE
NOTE
Context
NOTE
The OptiX RTN 905 does not support ATM OAM.
Procedure
> ATM 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
● ATM services have been configured.

NCE
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


NCE
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

NCE
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

NCE
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
● Multiple serial ports or E1 ports have been configured with the PPP protocol
activated.

NCE
NOTE
Procedure
Configuration > 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
● An MP group has been created.

NCE
NOTE

Procedure
Configuration > 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
● The corresponding boards have been added in the NE Panel.

NCE
NOTE
Procedure
Tree and choose Configuration > Clock Transparent Transmission > Clock
Transparent Transmission.
Step 2 Set the SDH retiming function.
1. Set Retiming Mode to Line Clock.

2. Select the SDH port for receiving clock signals from the third-party network
from the drop-down list of Line Clock Port according to the network plan.
Set all SDH ports on the 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
● The channelized STM-1 interface board has been added in the NE Panel.

NCE
NOTE
Procedure
Tree and choose Configuration > Clock Transparent Transmission > Clock
Transparent Transmission.
Step 2 Set the E1 clock source for a CQ1.
1. Set Retiming Mode to System Clock.
2. Select the 5th and 6th E1 clock sources for the 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

NCE
NOTE
Procedure
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
● The priority list of the clock source must be configured.

NCE
NOTE
Procedure
Clock > Physical Clock > Physical 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
● The priority level of a clock source must be set.

NCE
NOTE
Procedure
Clock > Physical Clock > Physical Clock Subnet Configuration.
Step 2 Click the Clock 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
● Clock sources have been configured.
● SSM protocols have been configured.

NCE
NOTE
Procedure
Clock > Physical Clock > Clock 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
● The standard SSM or extended SSM protocol is enabled.

NCE
NOTE
Procedure
Step 2 Click the SSM Output tab.
Step 3 Set the SSM control status.

NOTE
● Output S1 Byte Info is valid only when the SSM protocol or the extended SSM protocol is
started.
● Output S1 Byte Info indicates whether the SSM is output at the line port.
● 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
● The extended SSM protocol must be enabled.

NCE
NOTE
Procedure
Step 2 Click the Clock ID Output tab.
Step 3 Set the clock ID control status.

NOTE
● Output Clock ID is valid only when the extended SSM protocol is started.
● Output Clock ID indicates whether the clock source ID is output at the line port.
● 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

NCE
NOTE
Procedure
Clock > 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

NCE

NOTE
Procedure
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
● 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.
● 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
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

NCE
NOTE
Procedure
Clock > 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

NCE
NOTE
Procedure
Clock > 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

NCE
NOTE
Context
OptiX RTN 905 does not support circuit emulation service (CES) adaptive clock
recovery (ACR) clocks.
Procedure
Clock > 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
has been set to CES.

NCE
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.
Tree.
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
● CES services are configured.
Precautions
NOTICE
● An ACR clock domain can bind only the CES services on a local board.
● 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.
● A maximum of four ACR clock domains can bind CES services.

NCE
NOTE
Procedure
Step 1 In the NE Explorer, select the requiredNE from the Object Tree and choose
Configuration > Clock > ACR/DCR 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
● CES services are configured.
Precautions
NOTICE
● 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.
● The ACR clock domain cannot contain ports from different boards.
● 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.
● 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.

NCE
NOTE
Procedure
Configuration > 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
● The CES ACR clock has been configured.


NCE
NOTE
Procedure
Step 1 In the NE Explorer, select the requiredNE from the Object Tree and choose
Configuration > Clock > ACR/DCR 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

NCE
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

NCE
NOTE
Procedure
Configuration > 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

NCE
NOTE

Procedure
Configuration > 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

NCE
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-1 PTP NE attributes if IEEE 1588v2 is used
Figure A-2 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

NCE
NOTE
Procedure
Configuration > 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
● PTP clock ports are added.

NCE
NOTE

Procedure
Configuration > 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-3 PTP clock port attributes if IEEE 1588v2 is used
Figure A-4 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

NCE
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

NCE
NOTE
Procedure
Step 2 Click the Cable Transmitting Warp tab.
Step 3 Set parameters for configuring the cable transmission offset of PTP clock signals
according to the planning information.
Step 4 Click Apply.
----End
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
● If IEEE 1588v2 is used, NE Clock Type is OC, BC, or TC+BC.
● If ITU-T G.8275.1 is used, NE Clock Type is T-BC.

NCE

NOTE
Procedure
Configuration > 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
● If IEEE 1588v2 is used, NE Clock Type is OC, BC, or TC+BC.

NCE
NOTE
Procedure
Function Tree.
Step 2 Click the BMC tab.
Step 3 Set the parameters for the BMC algorithm according to the planning information.
Figure A-5 BMC algorithm parameters if IEEE 1588v2 is used

Figure A-6 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

NCE
NOTE
Procedure
Configuration > 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
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
● 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
● If IEEE 1588v2 is used, NE Clock Type is BC, OC, or TC+BC.


NCE
NOTE
Procedure
Tree.
Step 2 Click the BMC tab.
Step 3 Set parameters for the BMC algorithm of external time ports according to the
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.13 Setting the Cable Transmission Offset for External Time Ports
This section describes how to compensate transmission delay of external time
ports.
Prerequisites
● 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
● If IEEE 1588v2 is used, NE Clock Type is BC, OC, or TC+BC.



NCE
NOTE
Procedure
Tree.
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
● The corresponding board must be added in the NE Panel.

NCE

NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different
objects according to the following tables.
Table A-10 Packet plane

Performa Browsed Navigation Path
nce Object
Object
Basic Ethernet Select the corresponding board from the Object Tree in
performa porta the NE Explorer. Choose Performance > RMON
nce/ Performance from the Function Tree.
Extended NOTE
performa a: Packet Ethernet ports include FE/GE ports, Integrated IP
nce microwave ports, PORT8 on the EMS6 board, and PORT10 on
the EFP8 board.
PLA PLA 1. In the NE Explorer, select the required NE from the

group group Object Tree and choose Configuration > Physical
performa Link Aggregation.
nce 2. Select the desired PLA group, right-click, and choose
XPIC XPIC 1. In the NE Explorer, select the required NE from the

group group Object Tree and choose Configuration > Link
performa Configuration.
nce 2. Select the desired XPIC group, right-click, and choose
1+1 1+1 1. In the NE Explorer, select the required NE from the

group group Object Tree and choose Configuration > IF 1+1
performa Protection.
nce 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

tunnel Tunnel Object Tree and choose Configuration > MPLS
performa Management > Unicast Tunnel Management from
nce the Function Tree.
3. Select one or more tunnels, right-click the tunnel(s),
menu.


nce Object
Object
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE

PW PWE3 Explorer. Choose Configuration > Ethernet Service
performa service Management > E-Line Service from the Function
nce Tree.
2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE

performa E-Line Explorer. Choose Configuration > Ethernet Service
nce service Management > E-Line Service from the Function
Tree.
2. Select one or more UNI-UNI E-Line services, right-
click the service(s), and choose Browse Performance
CES-PW CES 1. In the NE Explorer, select the NE from the Object Tree
performa service and choose Configuration > CES Service
nce Management from the Function Tree.
CES 2. Select one or more CES services, right-click the
performa service(s), and choose Browse Performance from the
nce shortcut menu.
ATM/IMA Smart E1 Select the corresponding board from the Object Tree in
(access port the NE Explorer. Choose Performance > RMON
side) Performance from the Function Tree.
performa
nce
ATM-PW ATM 1. In the NE Explorer, select the NE from the Object Tree
performa PWE3 and choose Configuration > ATM Service
nce service Management from the Function Tree.
ATM 2. Select one or more ATM PWE3 services, right-click
PWE3 the service(s), and choose Browse Performance from
performa the shortcut menu.
nce
Port Ports 1. Select the NE from the Object Tree in the NE

traffic that Explorer. Choose Configuration > QoS Management
classificat perform > Policy Management > Port Policy from the
ion complex Function Tree.
performa traffic 2. Click the Application Object tab.
nce classifica
tion 3. Select one or multiple ports, right-click and choose
NOTE
Complete the operation of A.9.9.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
performa Explorer. Choose Configuration > Interface
nce Management > Ethernet Interface from the
Function Tree.
3. Select one or multiple ports, right-click and choose
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.
down list.
Port DS Ports in 1. Select the NE from the Object Tree in the NE

domain a DS Explorer. Choose Configuration > QoS Management
performa domain > Diffserv Domain Management > Diffserv Domain
2. Select the desired DS domain.
3. Click the Application Object tab.
ETHOAM E-Line 1. In the NE Explorer, select the required NE from the

802.1ag service Object Tree and choose Configuration > Ethernet
OAM Management > Ethernet Service OAM
Management.
2. Select the desired MEP, right-click, and choose


nce Object
Object
ETH OAM E-LAN 1. In the NE Explorer, select the required NE from the
performa service Object Tree and choose Configuration > Ethernet
nce (E- OAM Management > Ethernet Service OAM
LAN)b Management.
2. Select the desired test ID, right-click, and choose
NOTE
b: Only an NE housing CSHU or CSHUA boards supports ETH
OAM E-LAN service performance.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the

OAM Object Tree and choose Configuration > MPLS
Management > Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
PW 1. In the NE Explorer, select the required NE from the

Object Tree and choose Configuration > MPLS
Management > PW Management.
Table A-11 EoS/EoPDH plane

Performa Browse Navigation Path
nce Object
Object
Basic Ethernet In the NE Explorer, select the EFP8 or EMS6 board from
performa porta the Object Tree and choose Performance > RMON
nce Performance from the Function Tree.
NOTE
Extended a:
performa ● EoS Ethernet ports include PORT1 to PORT7 on the EMS6
nce board.
● EoPDH Ethernet ports include PORT1 to PORT9 on the EFP8
VCG- VCTRUN
board.
other K port
performa
nce

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

NCE
NOTE
Procedure


nce Object
Object
Extended NOTE
the EFP8 board.



menu.

menu.

nce Tree.
shortcut menu.


nce Object
Object

Tree.
nce shortcut menu.
performa
nce
nce

nce classifica
NOTE


nce Object
Object

Function Tree.
down list.
Function Tree.
down list.


Management.


nce Object
Object
LAN)b Management.
NOTE



nce Object
Object
NOTE
Extended a:
nce board.
VCG- VCTRUN
board.
other K port
performa
nce

NOTE
Function Tree.
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

NCE
NOTE
Context
NOTE
To set parameters for monitoring historical Ethernet performance of multiple NEs on the NCE,
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
● The objects and performance events to be monitored must be set.

NCE
NOTE
Procedure

nce Object
Object
Extended NOTE
the EFP8 board.



menu.


nce Object
Object

menu.

nce Tree.
shortcut menu.

Tree.
nce shortcut menu.
performa
nce
nce


nce Object
Object

nce classifica
NOTE

Function Tree.
down list.
Function Tree.
down list.



nce Object
Object

Management.
LAN)b Management.
NOTE



nce Object
Object
NOTE
Extended a:
nce board.
board.


nce Object
Object
VCG- VCTRUN
other K port
performa
nce
NOTE
Function Tree.
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
● The RTN 980 housing CSHNU boards,The RTN 980L housing CSHLU boards
and OptiX RTN 905 do not support this operation.

NCE

NOTE
Procedure
Orderwire from the Function Tree.
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
● The AUX board exists on the NE Panel.


NCE
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
● The AUX board exists on the NE Panel.

NCE

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
● The IF1 board must be added on the NE Panel.
● The DCC channels corresponding to external clocks must be disabled.

NCE
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
● The AUX,CSHL,CSHNA board exists on the NE Panel.

NCE
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
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

NCE
NOTE
Procedure
Configuration > Auxiliary Interface from the Function Tree.
Step 2 Specifies the function of an auxiliary port.

NOTE
● For OptiX RTN 950/950A(CSHO)/980/980L, the ID of the outdoor cabinet monitoring

port is 2.
● For OptiX RTN 905/910A/950A(CSHOF), the ID of the outdoor cabinet monitoring port
is 1.
● 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.
● 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
● Interface Mode has been configured correctly under Auxiliary Interface.

NCE
NOTE
Context
NOTE
● An OptiX RTN 980 and OptiX RTN 980L can be installed in any of the following outdoor
cabinets: APM30 AC and APM30 DC cabinets.
● 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
● The TCU logical board has been added to the NE Panel.

NCE
NOTE
Procedure
Step 1 In the NE Explorer, select TCU from the Object Tree and choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the
Function Tree.
Step 2 Select Outdoor cabinet interface from the drop-down list.
Step 3 Optional: Click Query to view the temperature and fan information.
Step 4 Optional: Set the working mode of the fan.

1. Set Work mode.
2. Set other parameters according to the value of Work mode.
– 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
● The PMU logical board has been added to the NE Panel.

NCE
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

NCE
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
● The TCU has been added to the NE Panel.

NCE
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

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.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 (NCE)

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Choose Topology > 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 ● If the IP protocol is

IP Address Range of GNE used on the DCN,
GNE you can search for
an NE based on IP
Address of GNE or
IP Address Range
of GNE.
● To search for all
the NEs that
communicate with
the gateway NE,
select IP Address
Range of GNE.
● 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 NCE
(server) and the
gateway NE are located
in different network
segments, ensure that
the NCE and relevant
routers are configured
with the IP routes for
the network segment in
which the NCE and
gateway NE are located.

Search Address - - ● If Address Type is

set to IP Address
of GNE, enter the
IP address of the
gateway NE, such
as 192.168.x.x.
● 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
192.168.255.255.
● 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 Selected Deselected ● To create NEs in

search Deselected batches, it is
recommended that
you select Create
NE after search.
The NEs are
automatically
created after they
are found.
● 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 - - ● This parameter

specifies the user
name to be entered
when an NE is
created.
● This parameter is
valid only when
Create NE after
search is selected.
Password - - ● This parameter

specifies the
password to be
entered when an
NE is created.
valid only when
Create NE after
search is selected.

Upload after create Selected Deselected ● This parameter

Deselected specifies whether
to automatically
upload the NE data
after the NE is
found and created.
● 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

gateway NE that is
connected to the
found NE.
Created As GNE Yes Yes ● This parameter

No specifies the
password to be
entered when an
NE is created.
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

Uncreated indicates 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.
displays the ID of the
found NE.
Gateway GNE - This parameter

Non-GNE displays 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 ● To search for all

GNE IP Address the NEs that
communicate with
the GNE, select
GNE IP Domain.
● To search for the
GNE only, select
GNE IP Address.
Domain Address - - ● When Domain

Type is GNE IP
Domain, enter the
IP network
segment where the
GNE is located, for
example,
192.168.255.255.
● When Domain
Type is GNE IP
Address, enter the
IP address of the
GNE, for example,
192.168.x.x.
B.1.1.3 Parameter Description: NE Creation (NCE)

This topic describes the parameters that are related to NE creation.
Navigation Path
1. In the main topology, right-click, choose New > NE.
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 - ● 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.
● This
parameter
is set
according
to the
planning
information
.
● 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 - - ● This
parameter
specifies
the name
of the NE.
● 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 ● This

Gateway parameter
is set to
Gateway if
the new NE
is a
gateway
NE.
● This
parameter
is set to
Non-
Gateway if
the new NE
is a non-
gateway
NE.
● 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 ● This
parameter
needs to be
set when
Gateway
Type is set
to
Gateway.
● 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 communicatio
n between the
client and the
server is
encrypted if
this parameter
is set to
Security SSL.
Port - 5432 This

parameter
specifies the
communicatio
n 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 - ● 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.
● Set this parameter according to
the DCN planning information.
● The NE ID consisting of the basic
ID and extended ID identifies an
NE on the NMS.
Extended ID 1 to 254 9 ● Do not change the Extended ID

when the number of actual NEs
does not exceed the range
● It is recommended that this
parameter takes the default value.
Gateway Type IP Gateway IP Gateway This parameter specifies the type of

Serial Port the gateway that is used for the
communication between the Web
SSL Gateway LCT and the NEs.
USB

IP Address - This parameter is This parameter specifies the IP

set to 129.9.0.x address of the gateway NE to which
when the NE is the NE to be created belongs. This
delivered from parameter is displayed only when
the factory. "x" Gateway Type is set to IP Gateway.
indicates the
basic NE ID that
is set when the
NE is delivered
from the factory.
Port ● 1400 (when ● 1400 (when This parameter specifies the port
Gateway Type Gateway Type corresponding to the gateway NE to
is set to IP is set to IP which the NE to be created belongs.
Gateway) Gateway)
● COM1-COM32 ● COM1 (when
(when Gateway Type
Gateway Type is set to Serial
is set to Serial Port)
Port)
Baud Rate 1200bps 115200bps This parameter specifies the

2400bps communication rate between the NE
to be created and the corresponding
4800bps gateway NE. This parameter is
9600bps displayed only when Gateway Type
19200bps is set to Serial Port.
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,

name and Deselected enter User Name and Password to
password to log in to all the selected NEs.
login
Use the user Selected Deselected When this parameter is selected,

name and Deselected enter User Name and Password that
password that were used for the latest login to log
was used last in to the NE.
time
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 - ● 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.
set according to
the network plan.
NOTE
● The NE ID consisting
of the basic ID and
extended ID
identifies an NE on
the NMS.
● 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 (NCE)

This topic describes the parameters that are used for synchronizing the time of
NEs.
Navigation Path
1. Choose Configuration > > Common > NE Time Sync from the Main Menu.
2. Click the NE Time Synchronization tab.

Parameters for NE Time Synchronization


indicates the name of
the NE.
NE.
Synchronous Mode Standard NTP Null ● If this parameter is

NM set to NM, the NE
synchronizes the
Null time of the NMS
server.
● 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 ● If the NE functions

Identifier IP as the gateway NE,
this parameter is
set to IP.
● 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.
as a non-gateway
NE and
communicates with
the gateway NE
through the IP
protocol, this
parameter is set to
IP.
Standard NTP Server - - ● If the NE functions

as the gateway NE,
this parameter is
set to the IP
address of the
external NTP
server.
as a non-gateway
NE, this parameter
is set to the ID or
IP address of the
gateway NE.
● Two devices cannot
be configured as a
standard NTP
server to each
other.

Standard NTP Server 0 to 1024 0 ● If the NTP server

Key does not need to
authenticated, this
parameter is set to
the value "0".
● 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 - - ● 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).
that you use the
default value.

DST Selected Deselected ● This parameter

Deselected indicates whether
Synchronization
Starting Time is
the daylight saving
time.
set according to
the actual
situation.
Synchronization 1 to 300 1 ● This parameter

Period(days) indicates the period
of synchronizing
the time of the NE
with the time of
the NMS.
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


the NE.
NE.

Synchronous Mode Standard NTP Null ● If this parameter is

NM set to NM, the NE
synchronizes the
Null time of the NMS
server.
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 ● If the NE functions

Flag IP as the gateway NE,
this parameter is
NE IP set to IP.
as a non-gateway
NE and
communicates with
the gateway NE
through the
HWECC protocol,
this parameter is
set to NE ID.
as a non-gateway
NE and
communicates with
the gateway NE
through the IP
protocol, this
parameter is set to
IP.

Standard NTP Server - - ● If the NE functions

as the gateway NE,
this parameter is
set to the IP
address of the
external NTP
server.
as a non-gateway
NE, this parameter
is set to the ID or
IP address of the
gateway NE.
Standard NTP Server 0 to 1024 0 ● If the NTP server

Key does not need to
authenticated, this
parameter is set to
the value "0".
● 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 2 2 Set this parameter

Version 3 according to the
settings for the
standard NTP protocol
version used at the
peer end.
Used First Yes No This parameter

No specifies 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 ● When ECC is used to communicate

NE IP with the standard NTP server, set
the parameter to NE ID.
● 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
server equipment, the request is matched
peer with the levels from the minimum
access limit to the maximum access
limit, and the first matched level
prevails. The matching order is as
follows:
● 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.
● 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.
● Synchronization: The time query is
allowed for only the NTP service
of the local equipment.
● 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

No key is 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 - - ● 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)Perio
d(days).
that you use the
default value.
DST Selected Deselected ● This parameter

Synchronization
Starting Time is
the daylight saving
time.
set according to
the actual
situation.
Period(days) 1 to 300 1 ● This parameter

indicates the period
of synchronizing
the time of the NE
with the time of
the NMS.
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 > Common > NE Time Localization 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 - - ● After the time zone is changed,

the current time of the NE is
changed accordingly.
● This parameter is set according to
the place where the NE is located.
DST Selected Deselected ● The parameters related to daylight

Deselected saving time can be valid only
when this parameter is selected.
the situation whether daylight
saving time is used in the place
where the NE is located.
Offset 1 to 120 - This parameter specifies the offset

Unit: minute(s) value of the daylight saving time.
Start Rule WEEK WEEK This parameter specifies the method

DATE of adjusting the daylight saving time.
Start Time - - This parameter specifies the start

daylight saving time.
End Rule WEEK WEEK This parameter specifies the method

DATE of 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 > Common > NE Time Sync from the Main Menu.
2. Click the Standard NTP Key Management tab.

Key ID 1 to 1024 - ● This

parameter
indicates the
key for NTP
authenticatio
n.
● This
parameter is
set according
to the
requirements
of the
external NTP
server.
Password - - ● This
parameter
indicates the
password
that
corresponds
to Key ID.
● 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 ● When this

No parameter is
set to No,
the key
verification is
not trusted.
After
receiving the
key, the NE
rejects the
clock
synchronizati
on service.
● When this
parameter is
set to Yes,
the key
verification is
trusted. After
receiving the
key, the NE
provides the
clock
synchronizati
on service.
● After
receiving an
unknown or
incorrect key,
the NE
rejects the
clock
synchronizati
on service.
Hence, it is
recommende
d 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.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 >
Communication Parameters from the Function Tree.
Parameters for NE Communication Setting

IP Address - Before delivery, In the HWECC solution, an IP address

the IP address of is set according to the following
the NE is set to rules:
129.9.0.x. The ● The IP address, subnet mask, and
letter x indicates default gateway of the gateway
the basic ID. NE should meet the planning
requirements of the external DCN.
Gateway IP - 0.0.0.0
Address ● If an NE uses the extended ECC,
the IP address must be in the
same network segment.
● 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.

Subnet Mask - 255.255.0.0 ● 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 ● Do not change the extended ID

when the number of actual NEs
does not exceed the range
Connection Common + Common + ● Specifies the connection mode

Mode Security SSL Security SSL that the gateway NE allows the
Common NMS to use for connecting to the
gateway NE.
Security SSL
● If the gateway NE has no special
security requirement for
connection to the NMS,
Connection Mode can be set to
Common.
● 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.
● 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.
● The default parameter value is
recommended unless the gateway
NE requires that the NMS use the
SSL connection mode.
● 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
Communication > 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/ Enabled Enabled It is recommended that you use the

Disabled Disabled default value, except for the
following cases:
● If the port is connected to the
other ECC subnet, Enabled/
Disabled is set to Disabled.
● 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
D4-D12 PDH radio whose default value, except for the
transmission following cases:
D1-D12 capacity is less ● If the IP DCN solution is adopted,
D1-D1 than 16xE1) Channel for the SDH line ports is
D1-D3 (for other set to a value that is the same as
cases) the value for third-party network.
● 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 ● An established microwave link

TCP/IP uses TCP/IP if Protocol Type
retains the default value AUTO at
L2DCN both ends of the link. If Protocol
AUTO Type is set to TCP/IP or HWECC
at one end of the link and AUTO
at the other end, the link uses
TCP/IP or HWECC.
● If the IP DCN solution is adopted,
Protocol Type is set to TCP/IP.
● When the L2 DCN solution is used,
set Protocol Type to L2DCN.
IP Address - - ● IP Address is available only if

● 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.
● 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 - - ● Subnet Mask is available only if

this parameter specifies the subnet
mask of the non-backbone area
port on the ABR.
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
Communication > 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 - ● Only one overhead byte can be

Transmission of D2 selected each time.
Overhead Bytes ● X1, X2, X3, and X4 indicate the
at Source Port D3
customized overhead bytes that
D4 are used for transmitting
D5 asynchronous data services.
D6 ● An overhead byte cannot be a
D7 byte that is used. For example, an
overhead byte cannot be a byte in
D8 the used DCC channel.
D9 NOTE
D10 Only the ISU2/ISX2/ISV3/SL1DA /CD1/
ISM6board supports transparent
D11 transmission of the K1/K2 byte.
D12
E1
E2
F1
K1
K2
X1
X2
X3
X4
Sink Timeslot/ - - This parameter specifies the sink

Porta timeslot or port.

Transparent D1 - ● Only one overhead byte can be

Transmission of D2 selected each time.
Overhead Bytes ● An overhead byte cannot be a
at Sink Port D3
byte that is used. For example, an
D4 overhead byte cannot be a byte in
D5 the used DCC channel.
D6 ● Generally, Transparent
D7 Transmission of Overhead Bytes
at Sink Port can be set to a value
D8 that is the same as or different
D9 from the value in the case of
D10 Transparent Transmission of
Overhead Bytes at Source Port.
D11
NOTE
D12 Only the ISU2/ISX2/ISV3/SL1DA /CD1/
E1 ISM6board supports transparent
transmission of the K1/K2 byte.
E2
F1
K1
K2
X1
X2
X3
X4
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a
port functions the same regardless of the source port or sink port.
b. 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 It is recommended that you use the
Mode Specified mode mode default value.
NOTE
Autosensing
By default, the adaptive mode is enabled
mode 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 ● This parameter is valid only when

ECC Extended Mode is set to
Specified mode.
● This parameter can be set only
server of the extended ECC. In
normal cases, the NE that is close
to the NMS functions as the
server.
● This parameter can be set to any
value from 1601 to 1699.
Parameters for Setting the Client

Opposite IP - 0.0.0.0 ● This parameter is valid only when

ECC Extended Mode is set to
Specified mode.
client of the extended ECC. Except
for the NE that functions as the
server, all other NEs that use the
extended ECC can function as the
client.

Port 1601 to 1699 0 ● 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
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 - - ● 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.
● If the value is set to 0, it indicates
that the source NE is adjacent to
the destination NE.

Level - - ● 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.
● If the ECC route is generated
automatically, the priority is 4.
● 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 ● Specifies the test packet length.

(Byte) ● It is recommended that this
parameter take its default value.
Packet Quantity 1-65535 3 ● Specifies the number of test

packets.

Sending 0-65535 0 ● Specifies the test packet

Interval(ms) transmission interval.
To Be 1-65535 1000 ● Specifies the maximum time for

Translated(ms) test packet to wait until being
responded to.
Traceroute Parameters
Target NE - - Specifies the NE for which a

traceroute test will be performed.

responded to.
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
2. Click the IP Route Management tab.

Parameters for IP Route Management

Destination - - This parameter indicates the

Address destination address of the packets.
This parameter can be set to a valid
IP address of class A, B, or C only, but
cannot be set to the IP address of the
local host or the loopback address
with the 127 field.
Mask - - This parameter indicates the subnet

mask of the destination address of
the packets.
Gateway - - This parameter indicates the IP

address of the gateway on the
subnetwork where the NE is located,
namely, the IP address of the next
hop of the packets.
Protocol - - ● DIRECT: indicates the route

between the local NE and an
adjacent NE.
● STATIC: indicates the route that is
created manually.
● OSPF: indicates the route between
the local NE and a non-adjacent
NE.
● OSPF_ASE: indicates the route
whose Destination Address is
beyond the OSPF domain.
● OSPF_NSSA: indicates the route
whose Destination Address is in a
not so stubby area (NSSA).
● A route can be deleted in the case
of STATIC only, but cannot be
edited in the other cases.
● 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

Address destination address of the packets.
This parameter can be set to a valid
IP address of class A, B, or C only, but
cannot be set to the IP address of the
local host or the loopback address
with the 127 field.

Subnet Mask - - This parameter indicates the subnet

mask of the destination address of
the packets.
Gateway - - This parameter specifies the IP

address of the gateway on the
subnetwork where the NE is located,
namely, the IP address of the next
hop of the packets.
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
choose 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 ● Specifies the test packet length.

(Byte) ● It is recommended that this
Packet Quantity 1-65535 3 ● Specifies the number of test

packets.
Sending 0-65535 0 ● Specifies the test packet

Interval(ms) transmission interval.


responded to.
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 ● If only an OSPF area is configured

on an NE, set this parameter
according to the planning
information.
● 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 ● DCC Hello Timer(s) specifies the

Timer(s) Hello packet timer for the DCC
channel or inband DCN.
● 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.
● DCC Hello Timer(s) determines
the interval for the hello packet
timer to transmit the hello
packets.
● In the case of two interconnected
NEs, DCC Hello Timer(s) must be
set to the same value.
● Unless otherwise specified, it is
recommended that this parameter
take its default value.
DCC Neighbor 1 to 65535 40 ● DCC Neighbor Dead Time(s)

Dead Time(s) specifies the dead time of a
neighbor router for the DCC
channel or inband DCN.
● 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.
● DCC Neighbor Dead Time(s)
should be set to a value that is a
minimum of twice the value of
DCC Hello Timer(s).
● 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.

DCC 1 to 65535 5 ● DCC Retransmission Timer(s)

Retransmission specifies the interval for
Timer(s) transmitting a request through the
DCC channel or inband DCN to
retransmit the link state
advertisement (LSA) packets.
DCC Delay(s) 1 to 3600 1 ● DCC Delay(s) specifies the delay

time to transmit the LSA packets
through the DCC channel or
inband DCN.
● 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).
LAN Hello 1 to 255 10 ● DCC Hello Timer(s) specifies the

Timer(s) hello packet timer at the Ethernet
network management port or NE
cascading port.
● 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.
● LAN Hello Timer(s) determines
the interval for the hello packet
timer of the NE to transmit the
hello packets.
● In the case of two interconnected
NEs, LAN Hello Timer(s) must be
set to the same value.

LAN Neighbor 1 to 65535 40 ● LAN Neighbor Dead Time(s)

Dead Time(s) specifies the dead time of a
neighbor router at the LAN
interface.
● 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.
● 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).
● 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.
LAN 1 to 65535 5 ● LAN Retransmission Timer(s)

Retransmission specifies the time for transmitting
Timer(s) a request for retransmission of the
LSA packets through the Ethernet
cascading port.

LAN Delay(s) 1 to 3600 1 ● LAN Delay(s) specifies the delay

time to transmit the LSA packets
through the Ethernet network
management port or NE cascading
port.
● 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).
OSPF Status Enabled Enabled Specifies whether the OSPF protocol

Disabled is enabled. If an NE uses only static
routes with OSPF disabled, set this
parameter to Disabled.
STUB Area Enabled Disabled ● Specifies whether to enable the

Disabled STUB Area.
● Set this parameter as required.
● A backbone area cannot be a
STUB area.
NSSA Area Enabled Disabled ● Specifies whether to enable the

Disabled NSSA Area.
● A backbone area cannot be an
NSSA area.
Direct route Enabled Disabled ● Specifies whether the direct route

Disabled automatic flooding function is
enabled.
● Direct route: the route detected by
the link layer protocol.
Static route Enabled Disabled ● Specifies whether the static route

Disabled automatic flooding function is
enabled.
● Static route: the route manually
configured by the network
administrator.

Default route Enabled Disabled ● Specifies whether the default

Disabled route automatic flooding function
is enabled for ASBRs.
● 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 ● Specifies whether the Ethernet

External Disabled network management port or NE
Network Port cascading port transmits Type-10
LSAs.
● If this parameter is set to
Disabled, the Ethernet network
management port or NE cascading
port transmits network
management information.
LAN Interface Enabled Disabled ● Specifies whether the OSPF

Disabled protocol is enabled for the
Ethernet network management
port or NE cascading port.
● If this parameter is set to Enabled,
the OSPF protocol is
communicated with other
equipment through the Ethernet
cascading port.
OSPF authentication parameters

Interface Type - - ● Displays the DCN port types that

allow the OSPF authentication key
to be specified.
● LAN indicates the Ethernet
cascading port.
● DCC indicates the DCC channels or
inband DCN port.

Authentication none none ● Specifies the OSPF authentication

Type MD5 mode for which a key needs to be
set.
simple
● If Authentication Type is MD5, a
key needs to be set for the MD5
authentication mode.
● If Authentication Type is simple,
a key needs to be set for the
simple authentication mode.
● 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 ● The proxy ARP enables the NEs in
Enabled the same network segment but
different domains to communicate
with each other.
● 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
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 ● Specifies the OSPF authentication

Type MD5 type used by an area.
simple ● none indicates no authentication.
Automatic Enabled Disabled ● Specifies whether automatic route

Route Disabled aggregation is enabled for an
Aggregation area.
● 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 - - ● Set the area ID of a new OSPF

area according to the planning
information.
● An NE can be configured with a
maximum of four OSPF areas.
IP Address - - ● Set the IP addresses of the

Networks in an area according to
● 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 MD5 type used by an area according to
simple
● none indicates no authentication.
● MD5 indicates that authentication
is performed based on the preset
password, with the password
encrypted in MD5 mode.
● simple: indicates that
authentication is performed based
on the preset password, with the
password not encrypted.
Automatic Enabled Disabled ● Specifies whether automatic route

Route Disabled aggregation is enabled for an
Aggregation area.
● 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

STUB according to planning information.
NSSA ● For the backbone area, this
parameter must be set to NON-
STUB.
● 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
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 ● Specifies whether to enable the

Disabled OSPF.
Opaque LSA of Enabled Enabled ● Specifies whether DCCs support

External Disabled Type10 LSA.
Network Port ● 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

Name the destination NE.
Destination NE - - This parameter specifies the ID of the

ID destination NE.
Protocol Type - - Only IP protocols are supported.
Next Hop - - This parameter specifies the IP

Address address of the destination NE.
Routing - - This parameter specifies the number

Distance(hop) of hops between the source NE and
the destination NE.

B.1.2.17 Parameter Description: DCN Management_Bandwidth Management

This topic describes the parameters that are used for bandwidth management of
the inband DCN.
Navigation Path
2. Click the Bandwidth Management tab.
Parameters for Bandwidth Management

Ethernet Board 2 to 4094 4094 Specifies the VLAN ID used by inband

VLAN ID DCN channels.
● 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.
● 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/ 64 to 5000 512 Bandwidth(kbit/s) specifies the

s) 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/ parameter specifies the inband DCN
s) 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/ parameter.
s)
IF Port 64 to 5000 512 IF Port Bandwidth(kbit/s) specifies

Bandwidth(kbit/ the bandwidth for inband DCN
s) 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

ID VLAN ID of Huawei NMS and is used
to distinguish Huawei DCN packets
from third-party DCN packets on
NMS ports.
The OptiX RTN 950 using CSH/CST
boards, OptiX RTN 980, and OptiX
RTN 980L do not support this
parameter.
The OptiX RTN 950 using CSH/CST
boards and OptiX RTN 980 using
CSHN boards do not support this
parameter.
B.1.2.18 Parameter Description: DCN Management_Port Setting

This topic describes the parameters that are used for setting ports of the inband
DCN.
Navigation Path
2. Click the Port Settings tab.
Parameters for Setting Ports

Port Name - - This parameter indicates the port

name.

Enabled Status Enabled - ● Enabled Status specifies the

Disabled enabling status of the port.
● 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 ● Specifies the DCN protocol used by

HWECC the inband DCN.
L2DCN ● 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 - - ● This parameter is available only

when Protocol Type is set to IP.
interface IP address of the non-
backbone area port on the ABR.
the IP address for a port that does
not belong to the default process.
Subnet Mask - - ● This parameter is available only

when Protocol Type is set to IP.
this parameter specifies the subnet
mask of the non-backbone area
port on the ABR.
the subnet mask for a port that
does not belong to the default
process.

ATN Enabled Disabled This parameter enables or disables

Compatibility Disabled the ATN compatibility mode for an
Mode NE. When this parameter is set to
Enabled, RTN equipment can auto-
negotiate its DCN mode to the ATN
mode or the transmission equipment
mode, based on the format of inband
DCN packets received from the
opposite end.
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

Status Disabled OSPF for a port.
B.1.2.19 Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Navigation Path
● In the NE Explorer, select the desired NE from the Object Tree and then
choose Communication > DCN Management from the Function Tree.
● Click the Access Control tab.
Parameters
Parameter Value Default Description
Range Value
Port Name - - Displays the Ethernet

ports that support this
function.


Range Value
Enabled Status Disabled Disabled ● Specifies the enabling

Enabled status of the port.
● If the Enabled Status
is set to Enabled, this
port can be used to
support access of the
management
information from the
NMS.
● 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.
Subnet Mask - 0.0.0.0 Specifies the submask of

the port.
OSPF Enabled Status Disabled Disabled Specifies the enabling

Enabled status of the OSPF.
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
choose Communication > DCN Management from the Function Tree.
● 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 Specifies the VLAN priorities of

EF Type is VLAN) inband DCN packets or the PHBs
BE (Packet Type corresponding to the DSCP values of
AF4 the inband DCN packets.
is 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
choose Communication > L2DCN Management from the Function Tree.
● 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 - ● Real Status is queried to be

Enabled Disabled 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.
● 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
Access Control from the Function Tree.
Parameters for Ethernet Access Control

Enable Ethernet Selected - After The First Network Port is set

Access Deselected to Enabled for Ethernet access, the
NE can access the NMS through the
Ethernet port.
PORT - - This parameter displays the NMS port

and the NE cascading port on the
system control, switching, and timing
board.
Work Mode adapt - This parameter specifies the working

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/ Enabled - Specifies whether the Ethernet

Disabled Disabled network management port or NE
cascading port is enabled.
Parameters for Access Control over Serial Ports

Enable Serial Selected Selected After Enable Serial Port Access is

Port Access Deselected selected, the NE can access the NMS
or command lines through the serial
port.
Access Selected Deselected If Access Command Line is selected,

Command Line Deselected the 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 ● This parameter specifies the data

2400 transmission rate in the
communications through serial
4800 ports.
9600 ● This parameter is set according to
the 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,

Access Deselected the NE can access the NMS or
command lines through the mini USB
port.
Access Selected Deselected If Access Command Line is selected,

Command Line Deselected the 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
Communication > SNMP Communication Parameters from the Function
Tree.
Parameters
Community Enabled Enabled Set whether to verify the complexity

Complexity Disabled of a community name.
Verify If this parameter is set to Enabled,
the community name must meet the
following rules:
● The community name is a
character string consisting of at
least six characters.
● 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

Permissions Read/Write the SNMP server based on the
network plan. Read/Write
Permissions must take the same
values as the right parameters set on
the SNMP server.
Report SDH - - Set Report SDH Performance Trap

Performance to Report if an SNMP server is
Trap 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 Report if an SNMP server is required
Trap 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

Trap an SNMP server is required to
automatically report trap packets
when the SDH performance crosses
the threshold, the data performance
crosses the threshold, or an alarm is
generated on the NE.
Trap Port - - It is recommended that Port take the

default value.

Read - - Verify Read Community Name of

Community the SNMP server based on the
Name network plan. Read Community
Name must take the same values as
the right parameters set on the
SNMP server.
Write - - Verify Write Community Name of

Community the SNMP server based on the
Name network plan. Write Community
Name must take the same values as
the right parameters set on the
SNMP server.
Report Trap SNMPV1 SNMPV3 Set the Report Traps Version

Version SNMPV2C parameter based on the SNMP
protocol version running on the
SNMPV3 SNMP server.
Report Trap - - Set Report Trap Community Name

Community according to the network plan.
Name
Report Trap User - - Set Report Trap User Name

Name according to the network plan.
B.1.2.24 Parameter Description: LLDP

This section describes the LLDP parameters.
Navigation Path
Select the desired NE from the object tree in the NE Explorer and choose
Packet Parameter Description

Packet 1 to 3600 30 ● Set the transmission interval for

Transmission LLDP packets.
Interval(s) ● It is recommended that you retain
the default value for this parameter.

TTL Multiplier 4 to 100 4 ● Set the TTL multiplier.

● If no information is received from a
neighbor in the TTL multiplier time,
delete all information about the
neighbor.
● It is recommended that you retain
Re-initialization 1 to 10 2 ● Set the re-initialization delay time,

Delay(s) that is the time before a port can
change from disabled to other
status.
Packets 1 to 8 4 ● Set the number of packets that are

Transmitted in continuously transmitted in Fast
Fast Mode mode.
Port Parameter Description

Port - - Displays port information.
Mode Disable Disable ● Generally, set Mode to

Transmit Transmit&Receive for a port for
which the LLDP has been enabled.
Receive
● If unidirectional Ethernet connection
Transmit&Receiv is set up between a port for which
e the LLDP has been enabled and its
neighbor equipment, set Mode to
Transmit or Receive based on the
service direction.
● 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 - - Displays the latest update time of a

Holding Time(s) neighbor, that is the latest time a device
receives information from its neighbor.
Neighbor - - Displays the remaining survival time of

Remaining a 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 ID - - server type.
Server Type - - ● Function, Server ID, and Server
Type are associated with the servers
that are configured in A.4.4.2
Creating a RADIUS Server or a
RADIUS Proxy Server.
● Select the desired RADIUS server or
proxy server according to planning
information.

Server Status Active Active Specifies the active/standby status of

Standby the RADIUS server or proxy server.
● If no standby server is required, set
Server Status to Active.
● 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.
● Set Shared Key to the same value
on the NE and on the RADIUS server.
Interval of 3-10 5 Specifies the number of packet

Packet retransmission attempts and the
Transmission interval between the attempts.
Packet 1-5 3 ● If an NE does not receive the

Retransmission response from the RADIUS server
Attempts within a specific period, the NE re-
transmits the authentication request
for the configured attempt times and
at the configured interval.
● 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
Security > NE RADIUS Configuration from the Function Tree.
2. Click the RADIUS Server Configuration button.
The RADIUS Server Information dialog box is displayed.
3. Click New.

Parameters
Function Authentication Authentication Specifies the RADIUS function that an

Accounting NE needs to use.
Authentication + ● For NE RADIUS authentication,
Accounting select Authentication.
● 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.
● 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

NE ID is used for NE RADIUS authentication.
● If Server Type is RADIUS Server, set
Server ID to IP Address and specify
the IP address of the RADIUS server.
● 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.
● 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 RADIUS Function Configurations from the Function Tree.
Parameters
NE - - Displays the NE name.
RADIUS Client Open Close Specifies whether an NE has the ability

Close to be a RADIUS client. The RADIUS
function can be enabled on an NE only
if RADIUS Client is set to Open for the
NE.
Proxy Server Open Close Specifies whether an NE has the ability

Close to be a proxy server.
● If an NE needs to function as a proxy
server, set Proxy Server to Open for
the NE.
● 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 Protection from the Function Tree.
2. Click Create.


WTR time(s) 300 to 720 600 ● This parameter specifies the wait-
to-restore (WTR) time.
● 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 ● This parameter specifies whether

Disabled the signal degradation switching
function of N+1 protection is
enabled.
● When this parameter is set to
Enabled, the signal degradation
condition is considered as a trigger
condition of protection switching.
this parameter to Enabled.
Protect Group Enhanced N+1 Standard N+1 ● Only OptiX RTN 980L supports this
Type Standard N+1 parameter. Enhanced N+1
protection can be configured for
only short-haul microwave links or
long-haul microwave links on ISV3
boards running in IS3 mode.
● Only OptiX RTN 980L and OptiX
980 using CSHNA boards support
enhanced N+1 protection.
● 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.
● N+1 protection in enhanced mode
is implemented based on
enhanced physical link
aggregation (EPLA). The number
of TDM services carried by 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 specifies the
Unit mapping direction
of N+1 protection.
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
> N+1 Protection from the Function Tree.
Protection Group Parameters

Protection - - This parameter indicates the ID of the

Group ID protection group.

Protect Group Enhanced N+1 Standard N+1 ● Only OptiX RTN 980L supports this
Type Standard N+1 parameter. Enhanced N+1
protection can be configured for
only short-haul microwave links or
long-haul microwave links on ISV3
boards running in IS3 mode.
● Only OptiX RTN 980L and OptiX
980 using CSHNA boards support
enhanced N+1 protection.
● 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.
● N+1 protection in enhanced mode
is implemented based on
enhanced physical link
aggregation (EPLA). The number
of TDM services carried by each
member link in an enhanced N+1
protection group can be flexibly
configured.
WTR Time(s) 300 to 720 - ● This parameter indicates or

specifies the WTR time.
SD Switching Enabled - ● This parameter indicates or

Disabled specifies whether the SD switching
function of N+1 protection is
enabled.
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 - - This parameter indicates the local

End Indication end or remote end.
B.2.3 Parameter Description: IF 1+1 Protection_Create

This topic describes the parameters for creating an IF 1+1 protection group.
Navigation Path
> IF 1+1 Protection from the Function Tree.
2. Click Create.

Parameters
Working Mode HSB HSB ● This parameter specifies the

FD working mode of the IF 1+1
protection.
SD
● 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.
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.
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.
● The FD mode and SD mode are
compatible with the HSB
switching function.

Revertive Mode Revertive Mode Revertive Mode ● This parameter specifies the
Non-Revertive revertive mode of the IF 1+1
protection.
● 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.
● 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 ● This parameter specifies the

wait-to-restore (WTR) time.
normal reaches the set WTR
Time(s), a revertive switching
occurs.
● You can set WTR Time(s) only
when Revertive Mode is set to
Revertive Mode. It is
recommended that you use the
default value.

Enable Reverse Enabled Enabled ● This parameter indicates

Switching Disabled whether the reverse switching
● 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.
● Enable Reverse Switching is
valid only when Working Mode
is set to HSB or SD.
● 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 Type to 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 ● When Alarm Report Mode is
Mode Only protection alarms set to Only board alarms, only
group alarms IF board alarms are reported.
Protection group and ● When Alarm Report Mode is
board alarms set to 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.
● When Alarm Report Mode is
set to Protection group and
board alarms, IF board alarms
and protection group alarms
are reported.
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 0 to 600 300 ● When Anti-jitter Time(s) is not

Time(s) 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.
● It is recommended that Anti-
jitter Time(s) take its default
value.
NOTE
Anti-jitter Time(s) is valid only for
alarms reported when a protection
group degrades.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s),Anti-jitter

Time(s), and Enable Reverse Switching must be set to the same value at both ends of a
radio hop.

B.2.4 Parameter Description: IF 1+1 Protection

This topic describes the parameters that are related to IF 1+1 protection.
Navigation Path
> IF 1+1 Protection from the Function Tree.


Working Mode HSB - ● This parameter indicates the

FD working mode of the created IF
1+1 protection group.
SD
● 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.
● 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
reduced.
● 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
reduced.
● The FD mode and SD mode are
compatible with the HSB switching
function.

Revertive Mode Revertive Mode - ● This parameter indicates or

Non-Revertive specifies the revertive mode of the
Mode protection group.
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.
Non-Revertive Mode, the NE that
is in the switching state keeps the
this parameter to Revertive Mode.

Revertive Mode.
Enable Reverse Enabled - ● This parameter indicates or

Switching Disabled specifies whether the reverse
switching function is enabled.
● 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.
● This parameter is valid only when
Working Mode is set to HSB or
SD.

NE Switching - - ● This parameter indicates the

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

Switching Status switching state on the channel
side.
● Unknown is displayed when the
switching state on the channel side
is not queried or not obtained
after a query.
Device Active - - This parameter indicates the current

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

Port working board on the channel side.
Alarm Report Only board - ● When Alarm Report Mode is set

Mode alarms to Only board alarms, only IF
Only Protection board alarms are reported.
group alarms ● When Alarm Report Mode is set
Protection group to Only protection group alarms,
and board alarms protection group alarms are
reported if a protection group fails
or degrades. Service alarms on IF
boards and radio links are
suppressed.
● When Alarm Report Mode is set
to Protection group and board
alarms, IF board alarms and
protection group alarms are
reported.
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 0 to 600 - ● When Anti-jitter Time(s) is not

(s) 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.
● It is recommended that Anti-jitter
Time(s) take its default value.
Alarm Deselected (no Deselected (no ● This parameter specifies whether

Suppression suppression) suppression) to 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 Enable Reverse Switching must be set to the same value at both ends of a radio
hop.
Slot Mapping Relation Parameters

Unit - - This parameter indicates the working

board and protection board.
Slot Mapping - - This parameter indicates the names

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

of Device state on the equipment side.
Signal Status of - - This parameter indicates the status of

Channel the link signal.
B.2.5 Parameter Description: Link Configuration_Creating a

PLA/EPLA/EPLA+/Super EPLA Group
This topic describes the parameters for creating a physical link aggregation (PLA)/
enhanced PLA (EPLA)/enhanced PLA Plus (EPLA+)/Super EPLA group.

NOTE
● Only OptiX RTN 950 using CSHU/CSHUA boards, OptiX RTN 910A, and OptiX RTN 950
support EPLA+.
● OptiX RTN 910A, OptiX RTN 905 1E/2E/2F, OptiX RTN 950A, OptiX RTN 950 using CSHU/
CSHUA/CSHUF, and OptiX RTN 980 using CSHNA/CSHNU boards support EPLA.
● Only RTN 905 2F, RTN 950 using CSHU/CSHUA/CSHUF and RTN 950As using SLF2CSHO
support super EPLA.
Navigation Path
2. Click New.
Parameters for Creating a PLA/EPLA Group (for OptiX RTN 905 1E/2E/2F)
Cascading Cascaded Cascade This parameter specifies the

Status Not Cascaded cascading 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 No NE-level Set the protection group type.

protection protection
NE Role Slave NE Master NE This parameter is valid only when

Master 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 PLA 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 - - This parameter is valid only when

Cascade Ports Cascading Status is set to Cascaded.
It is used to set the cascade boards
and ports of the PLA group.

Selected - - This parameter is valid only when

Cascade Ports Cascading Status is set to Cascaded.
It is used to display selected cascade
boards and ports.
Available Slave - - This parameter specifies slave boards

Ports and ports in a PLA group.
Selected Slave - - This parameter displays selected slave

Ports boards and ports.
Parameters for Creating a PLA/EPLA Group (for OptiX RTN 980L/OptiX RTN
980)
Cascading Not Cascaded Not Cascaded This parameter specifies the

Status cascading status.

PLA group.

bandwidth of a PLA group.

EPLA PLA group.

group.

group.

Ports and ports in a physical link
aggregation group.

Parameters for Creating a PLA/EPLA/EPLA+ Group (for OptiX RTN 910A)


PLA group.


EPLA physical link aggregation group.
EPLA+

group.

group.


Parameters for Creating a PLA/EPLA/EPLA+/Super EPLA Group (for OptiX

RTN 950/OptiX RTN 950A)

PLA group.

EPLA physical link aggregation group.
EPLA+
S-EPLA

Scheduling Mode A Mode A This parameter can be specified only

Mode Mode B when PLA Type is S-EPLA.
Mode A Access ● When Scheduling Mode is Mode
B, 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 set to
Mode A, high-priority and low-
priority services are transmitted on
both common-band links and E-
band links. In this mode,
implementing inter-frequency AM.
Mode A Access, it is similar to
Mode A, but only connect with
Mode A Access.
High-Priority BE EF ● When Scheduling Mode is set to

Service AF1 Mode B, a threshold can be set to
Threshold determine the priority of a service.
AF2 Only an SP queue can be
AF3 configured with a PHB. Services in
AF4 this SP queue and other queues
with higher-priorities are high-
EF priority services.
CS6
CS7
Main Port Auto Auto ● This parameter specifies the

Priority Low priority for a super EPLA group's
member link. This parameter
High generally takes the default value.
● This parameter can be specified
only when Scheduling Mode is
Mode B.

group.


group.


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
● Only OptiX RTN 950 using CSHU/CSHUA, OptiX RTN 910A, and OptiX RTN 950 support EPLA
+.
● OptiX RTN 910A, OptiX RTN 905 1E/2E/2F, OptiX RTN 950A, OptiX RTN 950 using CSHU/
CSHUA/CSHUF, and OptiX RTN 980 using CSHNA/CSHNU support EPLA.
● Only OptiX RTN 905 1E/2E/2F, OptiX RTN 950 using CSHU/CSHUA/CSHUF, OptiX RTN 950A
using SLF2CSHO, and OptiX RTN 980 using CSHNU support Super EPLA.
Navigation Path
choose Configuration > Physical Link Aggregation from the Function Tree.
PLA/EPLA Parameters (for OptiX RTN 980L)

Cascading - - This parameter displays the cascading

Status 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 displays the type of a

PLA group.

NE Role - - This parameter displays whether an

NE is the master or slave NE in a PLA
group.
Main Port - - This parameter displays the main port

in a PLA group.
Cascade Port - - This parameter displays a cascade

port in a PLA group.
Local NE - - This parameter displays the working

Working Status status of the local NE.
Minimum Active - - This parameter specifies the

Links minimum number of available links in
a PLA group and helps to trigger
Ethernet ring protection switching
(ERPS) switching even if not all
members in the PLA group fail.
For example, if you set Minimum
Active Links to 2, ERPS switching is
triggered when either PLA member
link fails.

Extendable - - This parameter displays the

Bandwidth(M) extendable bandwidth of 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 Enabled Disabled Hitless EPLA switching can be

Switching Disabled enabled for RTN 980L working as
long-haul microwave.

PLA/EPLA/Super EPLA Parameters (for OptiX RTN 905 1E/2E/2F and OptiX
RTN 980)

Status status.

PLA group.

PLA group.
Protection Type - - This parameter displays the type of a

PLA group.
NE Role - - This parameter displays whether an

NE is the master or slave NE in a PLA
group.

in a PLA group.
Cascade Port - - This parameter displays a cascade

port in a PLA group.
Local NE - - This parameter displays the working

Working Status status of the local NE.

link fails.

Extendable - - This parameter displays the

Bandwidth(M) extendable bandwidth of a PLA
group.
WTR Status Disabled Disabled The WTR time refers to the period
Enabled from the time when the faulty
channel is restored to normal to the
time when the switching is released.
This parameter is used together with
WTR Time.

WTR Time 0 0 If WTR Status is set to Disabled, this

30~1800 parameter cannot be set and its value
is 0.
This parameter is available when
WTR Status is set to Enabled. The
value ranges from 30 to 1800.
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 Enabled Disabled Hitless EPLA switching can be

Switching Disabled enabled for RTN 980L working as
long-haul microwave.
PLA/EPLA/EPLA+ Parameters (OptiX RTN 910A)


Status status.

PLA group.

PLA group.
Main Board - - This parameter displays the main

board in a PLA group.

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

Main Port status of the main port in a PLA
group.
Work Status of - - This parameter displays the work

group.

link fails.
Slave Board - - This parameter displays the slave

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 status of the slave port in a PLA
group.

group.
PLA/EPLA//EPLA+/Super EPLA Parameters (for OptiX RTN 950/RTN 950A)


Status status.

PLA group.

PLA group.

Scheduling Hitless Hitless ● When Scheduling Mode is Mode

Mode Common B, 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.
Mode A, high-priority and low-
priority services are transmitted on
both common-band links and E-
band links, implementing inter-
frequency AM.
Mode A Access, it is similar to
Mode A, but only connect with
Mode A Access.
High-Priority 0-7 5 ● When Scheduling Mode is set to

Service Mode B, a threshold can be set to
Threshold determine the priority of a service.
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 Auto Auto ● This parameter specifies the

Priority Low priority for a super EPLA group's
member link. This parameter
High generally takes the default value.
● This parameter can be specified
only when Scheduling Mode is
Mode B.
Main Board - - This parameter displays the main


in a PLA group.

of Main Port status of the main port in a PLA
group.


group.

group.

link fails.
WTR Status Disabled Disabled The WTR time refers to the period
Enabled from the time when the faulty
channel is restored to normal to the
time when the switching is released.
This parameter is used together with
WTR Time.
WTR Time 0 0 If WTR Status is set to Disabled, this

30~1800 parameter cannot be set and its value
is 0.
This parameter is available when
WTR Status is set to Enabled. The
value ranges from 30 to 1800.
Slave Board - - This parameter displays the slave

Slave Port - - This parameter displays the slave port

in a PLA group.

of Slave Port status of the slave port in a PLA
group.

group.

group.

B.2.7 Parameter Description: Microwave Link Management

This section describes the parameters related to microwave link management.
Navigation Path
In the NE Explorer, select the desired NE from the object tree. Choose
Configuration > Microwave Link Configuration from the function tree.
Basic Parameters
Protection 1+0 1+0 This parameter specifies the IF link

1+1 protection scheme.
This parameter is unavailable for the
RTN 905 1E.
XPIC Selected Deselected This parameter specifies whether to

Deselected enable XPIC on an XPIC-capable IF
board.
MIMO Selected Deselected This parameter specifies whether to

Deselected enable MIMO on an IF board.
MIMO Type 4*4 MIMO (Not 4*4 MIMO (Not ● This parameter is valid only when
Cascaded) Cascaded) MIMO is selected.
● This parameter specifies the MIMO
configuration type. 4*4 MIMO
(Not Cascaded) indicates that
four IF ports in paired slots on an
NE are configured as a 4x4 MIMO
group.
Local NE - - This parameter is valid only when

MIMO is selected.
This parameter is used to set the
polarization information about the IF
ports on the local NE in a MIMO
group.
Polarization-1 to H1 Polarization-1: These are sub-parameters under

Polarization-4 V1 H1 Local NE.
H2 Polarization-2: These parameters specify the IF port-
V1 specific polarization directions for a
V2 MIMO group.
Polarization-3:
H2
Polarization-4:
V2

Polarization-1 1 Polarization-1 These are sub-parameters under

Link ID to 2 Link ID: 1 Local NE.
Polarization-4 Polarization-2 These parameters specify the
Link ID 3
Link ID: 2 polarization direction-specific link IDs
4 for a MIMO group.
Polarization-3
Link ID: 3
Polarization-4
Link ID: 4
Link ID 1 to 4094 1 ● This parameter specifies the ID of

a microwave link.
● If the value of Received Link ID is
different from the value of Link
ID, the local NE sends alarm
indication signals (AISs) in the
downstream direction and reports
an alarm indicating a link ID
mismatch to the NMS.
● This parameter has an invalid
random value when a microwave
link fails.
● This parameter is unavailable
when MIMO is selected.
Received Link ID - - ● This parameter indicates the

received ID of a microwave link.
● If the value of Received Link ID is
different from the value of Link
ID, the local NE sends alarm
indication signals (AISs) in the
downstream direction and reports
an alarm indicating a link ID
mismatch to the NMS.
● This parameter has an invalid
random value when a microwave
link fails.
● This parameter is unavailable
when MIMO is selected.

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 the service types
supported by different IF boards, see IDU
SDH Hardware Description.
IF Channel - - This parameter specifies the channel

Bandwidth bandwidth of a microwave link. Set
this parameter according to the
network plan.
AM Status Selected Deselected ● When AM Status is deselected, the

Deselected microwave link always uses one
modulation scheme. In this case,
Modulation Mode must be
configured.
● When AM Status is selected, the
microwave link uses the
modulation scheme according to
the channel conditions.
● The AM function is supported only
by Integrated IP microwave.
● The AM function is not supported
when IF Channel Bandwidth is set
to 3.5MHz.
Modulation - - ● This parameter specifies the

Mode modulation scheme a microwave
link always uses for signal
transmission.
AM Status is deselected.
Guaranteed - - ● This parameter is valid only when

Capacity AM Status is selected.
Modulation ● This parameter specifies the lowest
modulation scheme that the AM
function supports. Set this
parameter according to the
network plan. Generally, the value
of this parameter is determined by
the service bandwidth that must
be guaranteed for microwave
transmission and the link
availability under the specified
modulation scheme.

Full Capacity - - ● This parameter is valid only when

Modulation AM Status is selected.
● This parameter specifies the
highest modulation scheme that
the AM function supports. Set this
the service bandwidth that is
required for microwave
modulation scheme.
Guaranteed E1 - - ● When Enable E1 Priority is set to

Capacity Disabled, this parameter specifies
the E1 service transmission
capacity of an IF port.
● When Enable E1 Priority is set to
Enabled, this parameter specifies
capacity under the modulation
scheme specified by Guaranteed
Capacity Modulation.
● This parameter is configurable
when IF Service Type is set to
Hybrid(Native E1+ETH).
STM-1 Capacity - - ● This parameter specifies the STM-1

service transmission capacity of an
IF port.
only when IF Service Type is set to
Hybrid(Native STM-1+ETH) or
SDH.
Data Service - - This parameter indicates the data

Bandwidth(Mbit service transmission bandwidth of an
/s) IF board.
Enable E1 Disabled Disabled ● This parameter specifies whether

Priority Enabled to enable the E1 priority function.
only when AM Status is selected
and IF Service Type is set to

RF Parameters
TX Frequency - - ● This parameter specifies the

(MHz) transmit frequency (namely,
channel central frequency) of an
ODU.
● The value of this parameter ranges
from the minimum transmit
frequency supported by an ODU
plus half of the channel bandwidth
to the maximum transmit
minus half of the channel
bandwidth.
● The difference in the ODU
transmit frequency between the
two ends of a microwave link
equals one T/R spacing.
the network plan.
Actual RX - - This parameter indicates the receive

Frequency(MHz) frequency of an ODU.
T/R - - ● This parameter specifies the

Spacing(MHz) spacing between the transmit and
receive frequencies of an ODU to
prevent interference between
them.
● If Station Type of an ODU is TX
high, the transmit frequency is one
T/R spacing higher than the
receive frequency. If Station Type
of an ODU is TX low, the transmit
frequency is one T/R spacing lower
than the receive frequency.
● 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.
● The valid T/R spacing is
determined by the ODU. Therefore,
set T/R Spacing(MHz) according
to ODU specifications.
● Set T/R Spacing(MHz) to the
same value for the ODUs at both
ends of a microwave link.

ATPC Selected Deselected ● This parameter specifies whether

Deselected to enable ATPC.
● When this parameter is selected, if
the RSL is beyond ±2 dB of the
center of the interval between the
upper and lower ATPC thresholds,
the receiver instructs the
transmitter to increase/decrease
the transmit power so that the
adjusted RSL agrees within ±2 dB
of the center.
● Set this parameter to the same
value for both ends of a
microwave link.
● It is recommended ATPC be
deselected for NEs in areas where
fast fading is severe.
● Deselect ATPC during
commissioning so that the
transmit power does not change.
After commissioning, reconfigure
this parameter.
ATPC Upper - -45.0 ● Ensure that the center of the

Threshold(dBm) interval between the ATPC upper
and lower thresholds equals the
ATPC Lower - -70.0 expected receive power.
Threshold(dBm)
● It is recommended that ATPC
Upper Threshold(dBm) be set to
the center of the interval between
the ATPC upper and lower
thresholds plus 10 dB, and ATPC
Lower Threshold(dBm) be set to
the difference between the center
of the interval between the ATPC
upper and lower thresholds and 10
dB.
TX Power(dBm) - - This parameter indicates the transmit

power of an ODU.
Actual TX Power - - ● This parameter indicates the actual

(dBm) transmit power of an ODU.
● If ATPC is enabled, the value of
Actual TX Power (dBm) may be
different from the value of TX
Power(dBm).
Power to Be - - This parameter specifies the receive

Received(dBm) power of an ODU.

Actual RX - - This parameter indicates the actual

Power(dBm) receive power of an ODU.
TX Status - - This parameter indicates the transmit

status of an ODU.
Equipment Information Parameters

Frequency(GHz) - - This parameter indicates the

operating frequency band of an ODU.
Station Type - - ● This parameter indicates whether

an ODU serves a Tx high site or a
Tx low site.
● The transmit frequency of a Tx
high site is one T/R spacing higher
than the transmit frequency of a
Tx low site.
RF Type - - This parameter indicates the level of

the output power of an ODU.
Equip Type - - This parameter indicates the ODU

type, indicating the ODU/RFU
transmission capability.
Product SN - - This parameter indicates the

manufacturing SN and the
manufacturer code of an ODU.
B.2.8 Parameter Description: Single Site MIMO_New

Deployment
This section describes the parameters for creating a single site at the local end in
MIMO configuration.
Navigation Path
1. In the NE Explorer, select the desired NE from the object tree. Choose
Configuration > MIMO Configuration from the function tree.
2. Click New.

Basic Parameters
MIMO Type 4*4 MIMO (Not 4*4 MIMO (Not ● This parameter is valid only when
Cascaded) Cascaded) MIMO is selected.
● This parameter specifies the MIMO
configuration type. 4*4 MIMO
(Not Cascaded) indicates that
four IF ports in paired slots on an
NE are configured as a 4x4 MIMO
group.
Synchronize Selected Deselected This parameter specifies whether to

Configuration to Deselected synchronize the local configurations
Adjacent NE to the peer NE.
Local NE - - This parameter is valid only when

MIMO is selected.
This parameter is used to set the
polarization information about the IF
ports on the local NE in a MIMO
group.
Polarization-1 to H1 Polarization-1: These are sub-parameters under

Polarization-4 V1 H1 Local NE.
H2 Polarization-2: These parameters specify the IF port-
V1 specific polarization directions for a
V2 MIMO group.
Polarization-3:
H2
Polarization-4:
V2
Polarization-1 1 Polarization-1 These are sub-parameters under

Link ID to 2 Link ID: 1 Local NE.
Polarization-4 Polarization-2 These parameters specify the
Link ID 3
Link ID: 2 polarization direction-specific link IDs
4 for a MIMO group.
Polarization-3
Link ID: 3
Polarization-4
Link ID: 4
Advanced Attribute Parameters


Bandwidth(MHz spacing of a microwave link. Set this
) parameter according to the network
plan.

AM Status Enabled Enabled ● When AM Status is set to

Disabled Disabled, the microwave link
always uses one modulation
scheme. In this case, Manually
Specified Modulation must be
configured.
● When AM Status is set to
Enabled, the microwave link uses
the modulation scheme according
to the channel conditions.
Guaranteed - - ● This parameter is valid only when

Capacity AM Status is set to Enabled.
Modulation ● This parameter specifies the lowest
modulation scheme.
Full Capacity - - ● This parameter is valid only when

Modulation AM Status is set to Enabled.
modulation scheme.
ATPC Enable Enabled Disabled This parameter specifies whether to

Status Disabled enable ATPC.
MIMO and ATPC are mutually
exclusive. Therefore, this parameter
cannot be set to Enabled.

Maximum - - ● This parameter specifies the

Transmit maximum transmit power of an
Power(dBm) ODU.
the network plan.

power of an ODU.
TX - - ● This parameter specifies the

Frequency(MHz) transmit frequency (namely,
ODU.
plus half of the channel spacing to
the maximum transmit frequency
supported by an ODU minus half
of the channel spacing.
the network plan.


them.
TX Status Mute Unmute This parameter indicates the transmit

Unmute status of an ODU.
B.2.9 Parameter Description: CA_New Deployment

This section describes the parameters for creating a CA group.
Navigation Path
1. In the NE Explorer, select the desired NE from the object tree. Choose
Configuration > Carrier Aggregation Management from the function tree.
2. Click New.
3. After setting the basic parameters, click Next Step to set the IF port
parameters for the CA group.

Basic Parameters
CA Type Not cascaded Not cascaded This parameter specifies the CA

configuration type. Not cascaded
indicates that two IF ports on the
same NE are configured as a CA
group. Currently, different NEs cannot
be cascaded to configure a CA group.
CA ID - - This parameter specifies the ID of a

CA group, which is used to
differentiate CA groups.
Position Local NE Local NE This parameter can only be set to

Local NE.
Main Port - - This parameter specifies the master

port in a CA group.
Local NE - - Parameters under Local NE are used

to set the slave port in a CA group.
IF Port Parameters for a CA Group

Bandwidth(MHz - - This parameter specifies the channel

) bandwidth of a microwave link. Set
this parameter according to the
network plan.
AM Status Enabled Enabled ● When AM Status is set to

Disabled Disabled, the microwave link
scheme.

Guaranteed - - ● This parameter is configurable

Capacity only when AM Status is set to
Modulation Enabled.
● This parameter specifies the lowest
modulation scheme.
Full Capacity - - ● This parameter is configurable

Modulation only when AM Status is set to
Enabled.
modulation scheme.
TX - - ● This parameter specifies the

Frequency(MHz) transmit frequency (namely,
ODU.
plus half of the channel spacing to
the maximum transmit frequency
supported by an ODU minus half
of the channel spacing.
the network plan.


them.

power of an ODU.
Maximum - - ● This parameter specifies the

Transmit maximum transmit power of an
Power(dBm) ODU.
the network plan.

ATPC Enable Disabled - ● This parameter specifies whether

Status Enabled to enable ATPC.
Enabled, if the RSL is beyond ±2
dB of the center of the interval
between the upper and lower
ATPC thresholds, the receiver
instructs the transmitter to
increase/decrease the transmit
power so that the adjusted RSL
agrees within ±2 dB of the center.
● Set this parameter to the same
value for both ends of a
microwave link.
● It is recommended this parameter
be set to Disabled for NEs in areas
where fast fading is severe.
● Set this parameter to Disabled
during commissioning so that the
transmit power does not change.
After commissioning, reconfigure
this parameter.
ATPC Upper - -45.0 ● Ensure that the center of the

Threshold(dBm) interval between the ATPC upper
and lower thresholds equals the
ATPC Lower - -70.0 expected receive power.
Threshold(dBm)
● It is recommended that ATPC
Upper Threshold(dBm) be set to
the center of the interval between
the ATPC upper and lower
thresholds plus 10 dB, and ATPC
Lower Threshold(dBm) be set to
the difference between the center
of the interval between the ATPC
upper and lower thresholds and 10
dB.
ATPC Automatic Disabled Disabled This parameter specifies whether to

Threshold Enabled enable automatic ATPC threshold
Enable Status adjustment.
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
> Linear MS from the Function Tree.
2. Click Create.

Protection Type 1+1 Protection 1+1 Protection ● This parameter specifies the
1:N Protection protection type of the linear MSP
group.
● 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.
● 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.
● If extra services need to be
transmitted or several working
channels are required, select 1:N
Protection.

Switching Mode Single-Ended Single-Ended ● This parameter specifies the

Switching Switching (1+1 switching mode of the linear
Dual-Ended Protection) MSP.
Switching Dual-Ended ● In single-ended mode, the
Switching (1:N switching occurs only at one end
Protection) and the state of the other end
remains unchanged.
● In dual-ended mode, the
switching occurs at both ends at
the same time.
● 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 ● This parameter specifies the

Revertive (1+1 Protection) revertive mode of the linear MSP.
Revertive (1:N ● When this parameter is set to
Protection) Revertive, the NE that is in the
switching state releases the
former working channel is
restored to normal.
Non-Revertive, the NE that is in
the switching state keeps the
this parameter to Revertive.
● If the linear MSP type is set to
1:N Protection, Revertive Mode
can be set to Revertive only.

WTR Time(s) 300 to 720 600 ● This parameter specifies the WTR
time.
normal reaches the preset WTR
time, a revertive switching occurs.
Revertive.
● It is recommended that you use
the default value.
SD Switching Enabled Enabled ● This parameter indicates or

Disabled specifies whether the switching at
the SD alarm of the linear MSP is
enabled.
Enabled, the B2_SD alarm is
considered as a switching
condition.
Protocol Type New Protocol New Protocol ● The new protocol is more mature,
Restructure and the restructure protocol
Protocol complies with the standard. It is
new protocol.
● You must ensure that the
interconnected NEs run the
protocols of the same type.

Select Mapping Direction West Working West Working This parameter

Unit Unit specifies the
West Protection mapping direction
Unit of the linear MSP.

Available Boards - - ● This parameter

specifies the
mapping board
and port in the
mapping
direction.
● If the
protection type
is set to 1+1
Protection,
only one line
port can be
mapped as
West Working
Unit.
● Only one line
port can be
mapped as
West
Protection
Unit.
● 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 >


Protection Type - - This parameter indicates the

protection type of the linear MSP
group.
Switching Mode Single-Ended - ● This parameter indicates or

Switching specifies the switching mode of
Dual-Ended the linear MSP.
Switching ● In single-ended mode, the
switching occurs only at one end
and the state of the other end
remains unchanged.
● In dual-ended mode, the switching
occurs at both ends at the same
time.
● 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 - ● This parameter indicates or

Revertive specifies the revertive mode of the
linear MSP.
Revertive, the NE that is in the
former working channel is restored
to normal.
Non-Revertive, the NE that is in
the switching state keeps the
● If the linear MSP type is set to 1:N
Protection, Revertive Mode can
be set to Revertive only.

Revertive.
the default value.
SD Switching Enabled - ● This parameter indicates or

Disabled specifies whether the reverse
switching function is enabled.
Enabled, the B2_SD alarm is
condition.

Protocol Type New Protocol - ● You must ensure that the

Restructure interconnected NEs run the
Protocol protocols of the same type.
● The new protocol is more mature,
and the restructure protocol
complies with the standard. It is
new protocol.
Protocol Status - - This parameter indicates the protocol

status of the linear MSP.
Protection - - This parameter displays the

Subnet 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 - - This parameter indicates the

Status-West switching status of the line.
Protected Unit - - This parameter indicates the working

channel protected by the current
protection channel.
Remote End/ - - When Switching Mode is set to

Local End Dual-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 ● Specifies the switching mode of

Switching Switching the packet-based linear MSP.
occurs at both ends
simultaneously.
Revertive Mode Revertive Revertive ● Specifies the revertive mode of the

packet-based linear MSP.
switching and enables the original
working channel to change to the
original working channel is
restored to normal.
WTR Time(s) 300-720 600 ● Specifies the WTR time.

● When the time after the original
Revertive.
this parameter to the default
value.

SD Switching Enabled Enabled ● Specifies whether an SD alarm of

Disabled the packet-based linear MSP can
trigger switching. You can set the
parameter value manually.
Enabled, a B2_SD alarm is
condition.
Protocol Type New Protocol New Protocol ● The new protocol is more mature,
Restructure and the restructured protocol
Protocol complies with the standard. It is
new protocol.
● Ensure that the interconnected
NEs run the protocols of the same
type.
SD/SF PRI Low priority Low priority ● Specifies whether an SD/SF alarm
Switching Tag High priority is a high-priority or low-priority
switching condition. You can set
the parameter value manually.
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.
● 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.
value.
Switching Mode Indication Indication Specifies whether the switching mode

Indication Not indication indication function is enabled for
packet-based linear MSP. You can set

Slot Mapping Parameters

Select Mapping West Working West Working Specifies the mapping direction of the
Direction Unit Unit linear MSP. You can set the
West Protection parameter value manually.
Unit
Available Boards - - ● Specifies the mapping board and

port in the mapping direction. You
can set the parameter value
manually.
● Only one line port can be mapped
as West Protection Unit.
● 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 >

Protection - - Specifies the ID of the protection

Group ID group.
Protection Type - - Specifies the protection type of a

packet-based linear MSP group.

Switching Mode Dual-Ended - ● Specifies the switching mode of

Switching the packet-based linear MSP. You
manually.
occurs at both ends at the same
time.
Revertive Mode Revertive - ● Specifies the revertive mode of the

packet-based linear MSP. You can
set the parameter value manually.
switching and enables the original
working channel to change to the
restored to normal.
WTR Time(s) 300-720 - ● Specifies the WTR time. You can

set the parameter value manually.
Revertive.
value.
SD Enable Enabled - ● Specifies whether the reverse

Disabled switching function is enabled. You
manually.
Enabled, a B2_SD alarm is
condition.

Protocol Type New Protocol - ● You must ensure that the

Restructure interconnected NEs run the
Protocol protocols of the same type.
● The new protocol is more mature,
and the restructured protocol
complies with the standard. It is
new protocol.
Protocol Status - - Specifies the protocol status of a

packet-based linear MSP.
SD/SF PRI High priority Low priority ● Specifies whether an SD/SF alarm
Switching Tag Low priority is a high-priority or low-priority
switching condition. You can set
● 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.
● 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
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 - - Specifies the switching status of the

Status-West line.
Protected Unit - - Specifies the working channel

protected by the current protection
channel.
Remote End/ - - When Switching Mode is set to

Local End Dual-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
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
Multiplex Multiplex always 2-fiber Bidirectional
Section Section Multiplex 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 ● 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.
● Prevents frequent service
switches. The default value is
recommended.
SD Switching Enabled Enabled ● 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.
● It is recommended that you
set this parameter to
Enabled.

Protocol Type New Protocol New Protocol ● The new MSP protocol is
Restructure supported from an early
Protocol stage, and is still widely used.
● Compared with the new MSP
protocol, the restructure MSP
protocol is optimized and
more stable, incorporating
better protection measures.
● 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.
● 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 - - ● Specifies the mapping board and

port in the mapping direction.
● 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

Protection - - Displays the ID of a ring MSP

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 - - ● Displays the protocol type used by

the local NE.
● The new MSP protocol is
supported from an early stage,
and is still widely used.
● 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 - - Displays the current protection

Subnet subnet.
Parameters for Slot Mapping Relationships

Mapping - - Displays the direction of an MSP ring.

Direction
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
> 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 ● This parameter specifies the level

VC3 of the service to be created.
VC4 ● If the service is an E1 service or a
data service that is bound with
VC-12 channels, set this parameter
to VC12.
● If the service is a data service that
is bound with VC-3 channels, set
this parameter to VC3.
● If all the services on a VC-4
channel pass through the NE, set
Direction Bidirectional Bidirectional ● 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.
● 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 ● This parameter specifies the

VC4–2 number of the VC-4 channel where
the service source is located.
● This parameter cannot be set
when Source Slot is set to the slot
of the tributary board.

Source Timeslot - - ● This parameter indicates the

Range(e.g.1,3-6) timeslot range of the service
source.
● 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 ● This parameter specifies the

the service sink is located.
when Sink Slot is set to the slot of
the tributary board.
Sink Timeslot - - ● This parameter specifies the

Range(e.g.1,3-6) timeslot range of the service sink.
3, 4, 5, and 6.

E1 Priority High - ● This parameter specifies the

Low priority of an E1 service. This
parameter is available only if the
None E1 priority function is enabled for
the ports configured in the cross-
connections.
● If E1 Priority is set to High,
transmission of the E1 service is
ensured in any modulation
scheme.
● If E1 Priority is set to Low,
ensured only in full-capacity
modulation scheme
● 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 ● This parameter specifies whether

Immediately No to immediately activate the
configured service.
● 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 ● 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-
connections from the SNCP service
source to the service sink and the
cross-connections from the SNCP
service sink to the service source.
Level VC12 VC12 ● This parameter specifies the level

VC3 of the SCNP service to be created.
VC4 ● If the service is an E1 service or a
data service that is bound with
VC-12 channels, set this parameter
to VC12.
● If the service is a data service that
is bound with VC-3 channels, set
● If all the services on a VC-4
channel pass through the NE, set

Hold-off 0 to 100 0 ● This parameter specifies the

Time(100ms) duration of the hold-off time.
● 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.
● 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.
● 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.
● 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.
● 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 ● This parameter specifies whether

Revertive to switch the service to the
original working channel after the
fault is rectified.
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.
time.
Revertive.
the default value.

the service source.
Source VC4 VC4–1 VC4–1 ● This parameter specifies the



source.
3, 4, 5, and 6.

the service sink.
Sink VC4 VC4–1 VC4–1 ● This parameter specifies the


3, 4, 5, and 6.
Configure SNCP Selected Deselected ● After the Configure SNCP

Tangent Ring Deselected Tangent Ring checkbox is
selected, you can quickly configure
the SNCP service for the SNCP ring
tangent point.
recommended that you do not
select this checkbox.

Activate Selected Selected ● This parameter specifies whether

Immediately Deselected to immediately activate the
configured SNCP service.
● 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 from the shortcut menu.
3. Select the unidirectional service. Right-click the selected service and choose
Convert to SNCP Service from the shortcut menu.

Service Type SNCP SNCP This parameter indicates that the

type of the service to be created is
SNCP.
Direction Unidirectional - This parameter indicates the direction

of the SNCP service.
Level - - This parameter indicates the level of

the SNCP service.

Hold-off 0 to 100 0 ● This parameter specifies the

Time(100ms) duration of the hold-off time.
switching can be performed on the
NE after a delay of time to prevent
performs SNCP switching and
other protection switching at the
same time.
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
Time(100ms) is set to 200 ms.
● 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
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.
available, it is recommended that
you set the hold-off time to 0.

Revertive Mode Non-Revertive Non-Revertive ● This parameter specifies whether

Revertive to switch the service to the
original working channel after the
fault is rectified. If this parameter
is set to "Revertive", the service is
channel.
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
channel.
time.
Revertive.
the default value.

the service source.
Source VC4 - - ● This parameter specifies the

number of the VC-4 channel where


source.
3, 4, 5, and 6.

the service sink.
Sink VC4 - - ● This parameter specifies the

number of the VC-4 channel where

3, 4, 5, and 6.
Configure SNCP - - After the Configure SNCP Tangent

Tangent Ring Ring checkbox is selected, you can
quickly configure the SNCP service for
the SNCP ring tangent point.
Activate - - ● This parameter specifies whether

Immediately to immediately activate the
configured SNCP service.
● 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
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 - - This parameter indicates the timeslot or timeslot range

Timeslot/Path of the service source.
Sink Slot - - This parameter indicates the slot of the source sink.
Sink Timeslot/ - - This parameter indicates the timeslot or timeslot range

Path of the service sink.
Activation Yes - This parameter indicates whether to activate the

Status No service.
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 - ● This parameter specifies the priority of an E1

Low service. This parameter is available only if the E1
priority function is enabled for the ports configured
None in the cross-connections.
● If E1 Priority is set to High, transmission of the E1
service is ensured in any modulation scheme.
● If E1 Priority is set to Low, transmission of the E1
service is ensured only in full-capacity modulation
scheme
● 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 - - This parameter indicates the timeslot

Timeslot/Path or timeslot range of the service
source.
Sink Slot - - This parameter indicates the slot of

the source sink.
Sink Timeslot/ - - This parameter indicates the timeslot

Path or 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 - ● This parameter specifies the

Low priority of an E1 service. This
parameter is available only if the
None E1 priority function is enabled for
the ports configured in the cross-
connections.
● If E1 Priority is set to High,
ensured in any modulation
scheme.
● If E1 Priority is set to Low,
ensured only in full-capacity
modulation scheme
● 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

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 the protection
group.


Value
Revertive Mode Revertive - ● This parameter indicates or

Non-Revertive specifies the revertive
mode of the service.
● This parameter determines
whether to switch the
service from the protection
channel to the original
working channel after the
fault is rectified.
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.
you set this parameter to
Revertive.

● When the time after the
restored to normal reaches
the preset WTR time, a
revertive switching occurs.
● You can set WTR Time(s)
only when Revertive
Mode is set to Revertive.
you use the default value.


Value
Hold-off Time(100ms) 0 to 100 - ● This parameter specifies

the duration of the hold-
off time.
switching can be
performed on the NE after
a delay of time to prevent
performs SNCP switching
and other protection
switching at the same
time.
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
Time(100ms) is set to 200
ms.
● 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
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.
available, it is
the hold-off time to 0.


Value
Switching Condition - Null ● This parameter indicates or

specifies the conditions
that trigger the protection
switching of the service.
● After being selected as SD
Initiation Condition, an
alarm becomes a condition
for triggering switching of
an SNCP service.
you set SD Initiation
Condition to the same
condition for Working
Service and Protection
Service.
● The protection switching
conditions in SD Initiation
Condition are optional
values not included in the
default values, and they
are set according to the
Trail Status - - This parameter indicates the

status of the working service
and protection service of the
protection group.
Service Grouping - - The NE does not support this

parameter.
Group Type - - The NE does not support this

parameter.
Active Channel - - This parameter indicates

whether the working service
or protection service is
currently received by the
protection group.
Trail Name - - Displays the trail name.
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 ● 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
Auto of an E1_AIS alarm in the channel.
● 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.
● 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.
recommended that 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
● 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.
● 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.
● The value PDH
indicates that the
port transmits
Native E1 services
as a common PDH
port.
● 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
Tree.

NOTE
Before changing Port Mode for a port enabled with inband DCN, disable inband DCN.
Port - - Displays the ID of a

service port.
Name - - Specifies or displays

the customized port
name.
Port Mode Layer 1 Layer 3 ● Specifies the

Layer 2 working mode of a
PDH port.
Layer 3
● When this
parameter is set to
Layer 1, the port
can transmit TDM
signals. A port can
transmit CES and
serial services only
if this parameter is
set to Layer 1.
● When this
parameter is set to
Layer 2, the port
can transmit ATM
signals.
● When Port Mode is
Layer 3 for a port,
the port can carry
MLPPP signals.

Encapsulation Type - - ● Displays

Encapsulation
Type of a PDH
port.
Layer 1,
Encapsulation
Type takes its
default value Null.
Layer 2,
Encapsulation
Type takes its
default value ATM.
Layer 3,
Encapsulation
Type takes its
default value
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
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 ● Specifies the frame

Double Frame format.
CRC-4 Multiframe ● 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.
● If a CES service
uses the emulation
mode of SAToP, this
parameter needs to
assume the value
Unframe.
● The value of Frame
Format must be
the same at the
local and opposite
ends.
Line Encoding - - Displays the line

Format encoding format. The
parameter value is
always HDB3.

Re-timing Mode Master Mode Master Mode ● Master Mode: The

Slave Mode system clock is
used as the output
Line Clock Mode clock of services.
The master mode is
the re-timing
mode.
● 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.
● 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 ● Specifies the

Inloop loopback status for
a port.
Outloop
● Non-Loopback
indicates that
loopbacks are
canceled or not
performed.
● Inloop indicates
that the signals
that need to be
transmitted to the
opposite end are
looped back.
● Outloop indicates
that the received
signals are looped
back.
● 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.
● Generally, this
parameter is set to
Non-Loopback.
Impedance - - Displays the port

impedance.

Frame Mode 30(ATM,ML-PPP) - ● 30 timeslots: In an

31(ATM,CES,ML-PPP) E1 frame format,
timeslots 1 to 15
and 17 to 31 are
used to transmit
service data, and
timeslot 16 is used
to transmit
signaling.
● 31 timeslots: In an
E1 frame format,
timeslots 1 to 31
are used to
transmit service
data.
unavailable if
Frame Format is
Unframe.
● The port frame
modes need to be
the same at the
local and opposite
ends.
CES Encapsulation NULL NULL ● This parameter

Clock Mode Line Clock Mode specifies the source
of clock signals
transmitted by CES
services.
● When CES services
do not transmit any
clock signals, set
this parameter to
NULL.
● 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 ● Specifies whether

Disabled an Ethernet port is
enabled. An
Ethernet port can
receive, process,
and forward
Ethernet services
only if this
parameter is set to
Enabled.
according to the
planning
information.

Port Mode Layer 2 Layer 2 ● Specifies the level

Layer 3 of services that a
port carries.
Layer Mix
● If Port Mode is
Layer 2, the port
can carry native
Ethernet services.
● If Port Mode is
Layer 3, the port
can carry MPLS
tunnels.
● If Port Mode is
Layer Mix, the port
can carry both
native Ethernet
services and MPLS
tunnels.
Encapsulation Type Null - ● This parameter

802.1Q specifies the
method of the port
QinQ to process the
received packets.
valid only when
Port Mode is Layer
2.
● If you set
Encapsulation
Type to Null, the
port transparently
transmits the
received packets.
● If you set
Encapsulation
Type to 802.1Q,
the port identifies
the packets that
comply with the
IEEE 802.1q
standard.
● If you set
Encapsulation
Type to QinQ, the
port identifies the
packets that
comply with the
IEEE 802.1ad QinQ
standard.

Working Mode Auto-Negotiation Auto-Negotiation ● The Ethernet ports

10M Half-Duplex of different types
support different
10M Full-Duplex Working Mode.
100M Half-Duplex For details, see the
100M Full-Duplex IDU Hardware
Description.
1000M Full-Duplex
● When the
1000M Half-Duplex equipment on the
opposite side works
in auto-negotiation
mode, set the
Working Mode of
the equipment on
the local side to
Auto-Negotiation.
● 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.
● 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.

Max Frame Length 46 to 9600 1522 The value of Max

(bytes) Frame Length(byte)
should be greater
than the length of any
frame to be
transported.
NOTE
This parameter does
not take effect for
L3VPN services.
Auto-Negotiation 10M Half-Duplex FE: 100M Full-Duplex ● This parameter

Ability 10M Full-Duplex GE: 1000M Full- specifies the
Duplex optimal working
100M Half-Duplex mode that can be
100M Full-Duplex automatically
1000M Full-Duplex negotiated.
1000M Half-Duplex ● Auto-Negotiation
Ability is valid only
when Working
Mode is set to
Auto-Negotiation.
Logical Port Attribute Optical Port - ● This parameter

Electrical Port specifies the type
of the SFP module
that an Ethernet
port can house.
● If the specified and
actual SFP module
types are different,
the
LASER_MOD_ERR
alarm is reported.
● 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 - - This parameter

Attribute indicates the physical
type of an Ethernet
port.
Running Status - - This parameter

indicates the status of
the Ethernet link.

Traffic Policing Enabled Disabled Only after this

Status Disabled parameter is set to
Enabled for an
Ethernet port, the
Ethernet port is able
to report the
ETH_NO_FLOW alarm.
Traffic Policing 1 to 30 15 An Ethernet port

Period (min) reports an
ETH_NO_FLOW alarm
when the following
conditions are met:
● Both Enable Port
and Traffic
Monitoring Status
are set to Enabled.
● The Ethernet link is
working properly.
● 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 ● Non-

Flow Control Mode Enable Symmetric Autonegotiation
Flow Control Flow Control
Mode is valid only
Send Only when Working
Receive Only Mode is not set to
Auto-Negotiation.
● 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
● OptiX RTN 900
supports only two
non-auto-
negotiation flow
control modes,
namely, Disabled
mode and Enable
Symmetric Flow
Control mode.
● An EM6D board
supports only two
non-auto-
negotiation flow
control modes,
namely, Disabled
mode and Receive
Only mode.

Auto-Negotiation Disabled Disabled ● Auto-Negotiation

Flow Control Mode Enable Symmetric Flow Control
Flow Control Mode is valid only
when Working
Enable Dissymmetric Mode is set to
Flow Control Auto-Negotiation.
Enable Symmetric/ ● Auto-Negotiation
Dissymmetric Flow Flow Control
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
● OptiX RTN 900
supports only two
auto-negotiation
flow control
modes, namely,
Disabled mode
and Enable
Symmetric Flow
Control mode.
● An EM6D board
supports only two
auto-negotiation
flow 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.



indicates the port
name.
QinQ Type Domain - - ● 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.
● 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 ● If all the accessed

Access services are frames
with the VLAN tag
Hybrid (tagged frames),
set TAG to Tag
Aware.
● If all the accessed
services are frames
without the VLAN
tag (untagged
frames), set TAG to
Access.
● If the accessed
services contain
tagged frames and
untagged frames,
set TAG to Hybrid.

Default VLAN ID 1 to 4094 1 ● Default VLAN ID is

valid only when
TAG is set to
Access or Hybrid.
VLAN Priority 0 to 7 0 ● 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
Configuration > Interface Management > Ethernet Interface from the
Function Tree.

NOTE
Layer 3 Attributes is valid only if Port Mode is set to Layer 3.

name.
Enable Tunnel Disabled Enabled ● If Enable Tunnel is

Enabled set Enabled, a port
identifies and
processes MPLS
labels.
● Enable Tunnel is
available if you set
Port Mode to
Layer 3 in the
General Attributes
tab.

Specify IP Address Manually Unspecified ● Specifies the

Unspecified method of setting
the IP address of a
port.
● The value
Unspecified
indicates that the IP
addresses do not
need to be
configured.
● The value
Manually indicates
that the IP address
of the port can be
manually
configured.
IP Address - 0.0.0.0 ● Specifies the IP

address of a port.
available when
Specify IP Address
is Manually.
● 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 ● Specifies the subnet

mask of a port.
available when
Specify IP Address
is 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


indicates the
port name.
Port Physical Parameters - - This parameter

indicates the
physical
parameters of
the port.
MAC Loopback Non-Loopback Non-Loopback ● 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.
● In normal
cases, it is
recommend
ed that you
use the
default
value.

PHY Loopback Non-Loopback Non-Loopback ● 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.
● In normal
cases, it is
recommend
ed 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 ● 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.
● For ports
that carry
E-LAN
services, it is
recommend
ed that you
set this
parameter
to Enabled.

Broadcast Packet Suppression 0 to 100 30 When the

Threshold(%) 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 ● 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-
Negotiatio
n. In this
case, the
PoE port
will
automatical
ly 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.
● 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.
● Only the
PoE port on
OptiX RTN
905 2E
supports
auto-
negotiation.
● 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.



the port where a serial
port is configured.

the customized port
name.
Level - - ● Specifies the serial

port level.
● 64K Timeslot: 64
kbit/s timeslots of
E1 signals can be
bound.
● 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 that carries
the serial port.
Low Channel - - Displays the low

channel that carries
the serial port.
64K Timeslot - - Displays the timeslots

that a serial port
occupies. The timeslots
can be consecutive or
not.

Port Mode Layer 2 - ● Displays or specifies

Layer 3 the port mode.
● 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 - - ● Displays or specifies

the encapsulation
type of a serial
port.
carries ATM
services, set this
parameter to ATM.
carries ML-PPP
links, set this
parameter to PPP.
Max Data Packet - - ● This parameter is

Size(byte) valid only when
Encapsulation
Type is set to PPP.
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: - - Specifies the port

1,3-6) number of the serial
port.
Name - - Specifies the

customized port name.
Level 64K Timeslot VC12 ● Specifies the serial

VC12 port level.
● When this
parameter is set to
64K Timeslot, E1
timeslots can be
bound.
● 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: - - Specifies the VC-12

1,3-6) lower order paths
bound with the serial
port. The VC-12
timeslots can be not
consecutive.
64K Timeslot(e.g: - - Specifies the 64 kbit/s

1,3-6) 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 ● When this

Line Clock parameter is set to
System Clock, all
Line Clock Port Port 1 to Port 4 - ports on the
channelized STM-1
interface board are
used to receive and
transmit SDH
frames.
● 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 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 two tributary

Timeslot VC12-1 to VC12-63 - 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
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 ● Specifies the E1

Double Frame frame format
encapsulated in
CRC-4 Multiframe VC-12s.
● 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.
● In SAToP emulation
mode, VC12 Frame
Format needs to be
set to Unframe.
● If E1s are members
in an MP group, it
is recommended
that you set VC12
Frame Format to
CRC-4 Multiframe.
● Set VC12 Frame
Format to the
same value at both
ends.

Frame Mode 31 31 ● If Frame Mode is

30 set to 30, timeslots
1 to 15 and 17 to
31 are used to
transmit services
and timeslot 16 is
transmitted to
transmit signaling.
● If Frame Mode is
set to 31, timeslots
1-31 are used to
transmit services.
● Frame Mode is
unavailable when
VC12 Frame
Format is set to
Unframe.
● If E1s are members
in an MP group, it
is recommended
that you set Frame
Mode to 31.
● 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 ● Displays or

Inloop specifies the port
loopback status.
Outloop
● Non-Loopback
indicates that the
loopback is
canceled or not
performed.
● Inloop indicates
that the service
signals transmitted
to the opposite end
are looped back.
● Outloop indicates
that the received
service signals are
looped back.
used for port fault
locating. This
function affects
services on the
related port.
● 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
> Interface Management > Microwave Interface from the Function Tree.

Parameters
Port - - This parameter indicates the

corresponding IF port.
Name - - This parameter indicates or specifies

the customized port name.
Port Mode Layer 2 Layer 2 ● This parameter specifies the level

Layer 3 of services that a port carries.
Layer Mix ● If Port Mode is Layer 2, the port
can carry native Ethernet services.
● If Port Mode is Layer 3, the port
can carry tunnels.
● If Port Mode is Layer Mix, the
port can carry both tunnels and
Native Ethernet services.
Encapsulation Null 802.1Q ● Encapsulation Type specifies the

Type 802.1Q method of the port to process the
received packets.
QinQ
Port Mode is Layer 2.
● If Encapsulation Type is set to
Null, the port transparently
transmits the received packets.
802.1Q, the port identifies the
packets that comply with the IEEE
802.1Q standard.
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

Status Disabled is qualified for capability to report
alarms ETH_NO_FLOW.
Traffic Policing 1 to 30 15 When port the following conditions

Period(min) are met, Alarms will be reported
ETH_NO_FLOW.
● Traffic Policing Status and Port
Status are set to Enabled.
● Link connection is normal.
● 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
Navigation Path
Parameters for Layer 2 Attributes


QinQ Type - - ● 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.
● 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
Tag Tag Aware Tag Aware ● If all the accessed services are
Access frames that contain the VLAN tag
(tagged frames), set Tag to "Tag
Hybrid Aware".
● If all the accessed services are
frames that do not contain the
VLAN tag (untagged frames), set
Tag to "Access".
● 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 ● 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 ● 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 frame after
the VLAN tag the VLAN tag
that corresponds that corresponds
to "Default VLAN to "Default VLAN
ID" and "VLAN ID" and "VLAN
Priority" is added Priority" is added
to the frame. to the frame.

Status Type of Data Processing Method

Frame
Tag Aware Access Hybrid
Egress Port Tagged frame The port The port strips ● If the VLAN ID
transmits the the VLAN tag in the frame is
frame. from the frame "Default VLAN
and then ID", the port
transmits the strips the
frame. VLAN tag
from the
frame and
then transmits
the frame.
● 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
Navigation Path
Configuration > Interface Management > Microwave Interface from the
Function Tree.

Port - - Displays the


Enable Tunnel Disabled Enabled ● A port identifies and

Enabled processes MPLS
labels, if its Enable
Tunnel is set
Enabled.
● Enable Tunnel is
available if you set
Port Mode to Layer
3 in the General
Attributes tab.
Specify IP Address Manually Unspecified ● Specifies the method

Unspecified of setting the IP
address of a port.
● The value
Unspecified indicates
that the IP addresses
do not need to be
configured for a port.
● The value Manually
indicates that the IP
address of a port can
be manually
configured.
IP Address - 0.0.0.0 ● Specifies the IP

address for a port.
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 ● Specifies the subnet

mask of a port.
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
Navigation Path
Parameters for Advanced Attributes


Error Frame - - An Ethernet frame which has a CRC

Discard Enabled error will be discarded.
MAC Address - - This parameter indicates the MAC

address of the port.
Jitter Disabled Disabled This parameter indicates or specifies

Adjustment 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 ● If Speed Transmission at L2 is set

Transmission at Enabled to Enabled, the Layer-2 Ethernet
L2 packets transmitted at microwave
ports will be compressed to
improve transmission efficiency.
● The settings of Speed
Transmission at L2 must be the
same at both ends of a radio link.
Speed Disabled Disabled ● If Speed Transmission at L3 is set

Transmission at Enabled to Enabled, the IP packets
L3 transmitted at microwave ports
will be compressed to improve
transmission efficiency.
● 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

Enabled enable loop detection, which is used
to check whether a loop exists on the
port.
Loopback Port Disabled Disabled This parameter indicates whether to

Block Enabled enable the automatic shut-down of
looped ports.
Broadcast Disabled Disabled ● This parameter specifies whether

Packet Enabled to limit the traffic rate of the
Suppression 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.
● If Ethernet services are E-LAN
services, the recommended value
is Enabled.

Broadcast 0 to 100 30 When the proportion of the broadcast

Packet packets in the port bandwidth
Suppression exceeds the value of this parameter,
Threshold(%) 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 Disabled Disabled Specifies whether to enable switching

Switching Enabled triggered by bit errors.
Triggered by Bit
Error
Switching Mode SF SF Specifies the mode of switching

Triggered by Bit SD triggered 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 Port_IF Attributes

This section describes the parameters for configuring the IF attributes.
Navigation Path
1. In the NE Explorer, select the desired board from the object tree. Choose
2. Click the IF Attributes tab.
IF General Attribute Parameters

Port - - This parameter indicates an IF port.

Power Switch Open Open This parameter specifies whether to

Close turn on or turn off the ODU power
switch for an ISM6 board.
NOTE
This parameter is available only for ISM6
boards.
Alarm And Enabled Enabled Alarm And Performance Report can

Performance Disabled be specified for the RTN 905, RTN
Report 910A, RTN 905 2F, and ISV3/ISM6/
ISM8 boards on the RTN 980/RTN
980L/RTN 950/RTN 950A. If Alarm
And Performance Report is set to
Disabled, alarms pertaining to the IF
port and the corresponding ODU will
not be reported.
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 the service types
supported by different IF boards, see IDU
SDH Hardware Description.
Microwave Link 1 to 4094 1 ● This parameter specifies the ID of

ID a microwave link. It is used to
prevent incorrect connections of
microwave links between sites.
● If the value of Microwave Link ID
is different from the value of
Received Microwave Link ID, the
local NE reports the MW_LIM
alarm.
the network plan. Each microwave
link of an NE must have a unique
link ID, and the same link ID must
be configured at both ends of a
microwave link.
Received - - This parameter indicates the received

Microwave Link ID of a microwave link.
ID

IF Port Non-Loopback Non-Loopback ● This parameter specifies the

Loopback Inloop loopback status of an IF port.
Outloop ● Non-Loopback indicates that the
loopback is canceled or not
performed.
● Inloop indicates that the IF signals
transmitted to the peer NE are
looped back.
● Outloop indicates that the
received IF signals are looped
back.
● Generally, this parameter is set to
Non-Loopback.
2M Wayside Disabled Disabled ● This parameter specifies whether

Enable Status Enabled to enable wayside E1 services.
● Only SDH microwave supports
wayside E1 services.
2M Wayside - - ● This parameter specifies the slot

Input Board housing the system control,
switching, and timing board that
processes wayside E1 services.
only when 2M Wayside Enable
Status is set to Enabled.
● When 1+1 protection is configured
for the system control, switching,
and timing board on the RTN 950,
only the external clock port on the
system control, switching, and
timing board in slot 7 can carry
wayside E1 services. In this case,
set this parameter to 7.
● When 1+1 protection is configured
for the system control, switching,
and timing board on the RTN
980/RTN 980L, only the external
clock port on the system control,
switching, and timing board in slot
15 can carry wayside E1 services.
In this case, set this parameter to
15.

Consecutive Stop Stop ● This parameter specifies whether

Wave Status Start to enable an IF port to output 350
MHz consecutive waves without
modulated signals.
● Generally, this parameter is set to
Stop.
XPIC Enabled Enabled Enabled ● This parameter specifies whether

Disabled to enable XPIC on an XPIC-capable
IF board.
● To disable XPIC on an XPIC-
capable IF board, set this
parameter to Disabled.
Enable Enabled Disabled ● This parameter must be set to the

IEEE-1588 Disabled same value for both ends of a
Timeslot microwave link.
● If an NE needs to transmit IEEE
1588V2 packets, set this parameter
to Enabled. If an NE does not
need to transmit IEEE 1588V2
packets, set this parameter to
Disabled.

Running Mode IS2 – ● The IF port on an ISU2/ISX2 board

IS3 can interconnect only with the IF
port that supports the IS2 mode.
IS6
● The RTN 905 1E/2E supports the
IS8 IS2 and IS3 modes. By default, it
works in IS3 mode. Running Mode
must be set to the same value for
the two IF units on an RTN 905 2E.
● The RTN 905 2F supports the IS8,
IS6, and IS3 modes. By default, it
works in IS8 mode. Running Mode
can be set to different values for
the two IF units on an RTN 905 2F.
● The ISV3 board supports the IS2
and IS3 modes. By default, it
works in IS3 mode.
● The IF ports on an ISM6 board
support the IS2, IS3, IS6–PLUS, and
IS6 modes. By default, they work
in IS6 mode. The two IF ports on
an ISM6 board must work in the
same mode.
● The IF ports on an ISM8 board
support the IS3, IS6, and IS8
modes. By default, they work in
IS8 mode. The two IF ports on an
ISM8 board can work in different
modes.
● It is recommended that two
interconnected IF ports work in the
highest-order mode that they both
support.
● Before changing the running mode
of an IF port, remove services on
the port.
● If IF ports are configured with
services or 1+1, N+1, PLA/EPLA/
EPLA+, or LAG protection,
Running Mode cannot be
modified for them.
NOTE
For the RTN 950/980, IF Service Type, XPIC Enabled, Enable IEEE-1588 Timeslot, and Running
Mode cannot be configured for the IF1 board but Radio Working Mode can be configured for
the IF1 board.

Hybrid/AM Configuration Parameters

NOTE
For the RTN 950/RTN 980, the IF1 board does not support Hybrid/AM configuration.

Bandwidth spacing of a microwave link. Set this
parameter according to the network
plan.
AM Boost Status Disabled Disabled The AM booster function increases

Enabled the transmit power of an ODU by 1
to 3 dB when the full capacity
modulation scheme is used, further
increasing the fading margin and the
working time under the full capacity
modulation scheme.
NOTE
Only ISX2 boards support the AM booster
function.
AM Status Disabled Disabled ● When AM Status is set to

Enabled Disabled, the microwave link
scheme. In this case, Manual
Modulation Mode must be
configured.
● The AM function is not supported
when IF Channel Bandwidth is
set to 3.5MHz.

Modulation - - ● This parameter is valid only when

Mode of the AM Status is set to Enabled.
Guarantee AM ● This parameter specifies the lowest
Capacity modulation scheme that the AM
modulation scheme.
Modulation - - ● This parameter is valid only when

Mode of the Full AM Status is set to Enabled.
AM Capacity ● This parameter specifies the
modulation scheme.
Manual - - ● This parameter specifies the

Modulation modulation scheme a microwave
Mode link always uses for signal
transmission.
AM Status is set to Disabled.
STM-1 Capacity - - ● This parameter specifies the

STM-1 service transmission
only when IF Service Type is set to
Hybrid(Native STM-1+ETH) or
SDH.
Enable E1 Disabled Disabled ● This parameter specifies whether

Priority Enabled to enable the E1 priority function.
only when AM Status is set to
Enabled and IF Service Type is set
to Hybrid(Native E1+ETH).

Guaranteed E1 - - ● When Enable E1 Priority is set to

Capacity Disabled, this parameter specifies
● When Enable E1 Priority is set to
Enabled, this parameter specifies
capacity under the modulation
scheme specified by Guaranteed
Capacity Modulation.
Guaranteed E1 - - This parameter indicates the E1

Capacity Range capacity range of an IF board under
the guaranteed capacity modulation
scheme.
Data Service - - This parameter indicates the data

Bandwidth(Mbit service transmission bandwidth of an
/s) IF board.
Full E1 Capacity - - ● This parameter specifies the E1

service transmission capacity
under the modulation scheme
specified by Guaranteed Capacity
Modulation.
● This parameter is valid when
Enable E1 Priority is set to
Enabled.
● E1 service bandwidth in full
capacity modulation ≤ Service
bandwidth in full capacity
modulation - Service bandwidth in
guaranteed capacity modulation +
E1 service bandwidth in
guaranteed capacity modulation.
In addition, the number of E1
services in full capacity modulation
cannot exceed the maximum
number in full capacity
modulation.
● Full E1 Capacity must be set to
the same value for both ends of a
microwave link.

Full E1 Capacity - - This parameter indicates the E1

Range capacity range of an IF board under
the full capacity modulation scheme.
TX Modulation - - This parameter indicates the

Mode modulation scheme at the transmit
end.
RX Modulation - - This parameter indicates the

Mode modulation scheme at the receive
end.
Guaranteed AM - - This parameter indicates the service

Capacity(Mbit/s capacity under the guaranteed
) modulation scheme.
Full AM Service - - This parameter indicates the service

Capacity(Mbit/s capacity under the full capacity
) modulation scheme.
Transmitted AM - - This parameter indicates the

Service transmitted service capacity with AM
Capacity(Mbit/s enabled.
)
Received AM - - This parameter indicates the received

Service service capacity with AM enabled.
Capacity(Mbit/s
)
E1 Capacity For - - This parameter indicates the number

High Priority of the configured high-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
● Select the corresponding board from the Object Tree in the NE Explorer.
Choose Configuration > IF Interface from the Function Tree.
● Click the ATPC Attributes tab.
Parameters

corresponding IF interface.

ATPC Enable Disabled Disabled ● This parameter specifies whether

Status Enabled the ATPC function is enabled.
Enabled and if the RSL at the
receive end is 2 dB higher or lower
than the central value between the
ATPC upper threshold and the
ATPC lower threshold at the
receive end, the receiver notifies
the transmitter to decrease or
increase the transmit power until
the RSL is within the range that is
2 dB higher or lower than the
central value between the ATPC
upper threshold and the ATPC
lower threshold.
● The settings of the ATPC attributes
must be consistent at both ends of
a radio link.
● In the case of areas where fast
fading severely affects the radio
transmission, it is recommended
that you set ATPC Enable Status
to Disabled.
● 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 ● Set the central value between the

Threshold(dBm) ATPC upper threshold and the
ATPC lower threshold to a value
for the expected receive power.
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.
● You can set the ATPC upper
threshold only when ATPC

ATPC Lower - -70.0 Automatic Threshold(dBm) is set

Threshold(dBm) to Disabled.
ATPC Automatic Enabled Disabled ● This parameter specifies whether

Threshold Disabled the ATPC automatic threshold
Enable Status function is enabled.
● 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.
● 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 - - ● This parameter indicates that the

Automatic equipment automatically uses the
Threshold(dBm) preset ATPC upper and lower
thresholds.
ATPC Lower - -
Automatic ● This parameter is valid only when
Threshold(dBm) ATPC Automatic Threshold
Enable 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
● In the NE Explorer, select the IF board, and then choose Configuration > IF
● Click the AM Advanced Attributes tab.
Parameters

corresponding IF interface.
Modulation - - Displays the modulation schemes.

Mode

E1 Capacity/ - - ● You can specify the number of E1s

STM-1 Capacity that can be transmitted in
intermediate modulation scheme,
by setting the advanced attributes
correspondingly.
● 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.
● 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 - - This parameter indicates the time of

Time the ATPC adjustment.

Adjustment - - This parameter indicates the direction

Direction of the adjustment at the port.
Switchover - - This parameter indicates the

switching operation at the port.
Transmitted - - This parameter indicates the

Power(dBm) transmitted power of the port to be
switched.
Received - - This parameter indicates the received

Power(dBm) power of the port to be switched.
B.5.7.5 Parameter Description: IF Multiplexing Port Management

This section describes the parameters for IF multiplexing port management.
Navigation Path
In the NE Explorer, select the desired board from the object tree. Choose
Configuration > IF Conflux Port Management from the function tree.
Parameters
Role Source Port Source Port This parameter specifies the role of
Destination Port an IF port.
This parameter is configurable only
when Conflux Mode is set to Share
ODU.
Conflux Mode No Conflux No Conflux This parameter specifies whether to

Share ODU enable an IF port to share an ODU
with other IF ports. Currently, only
sharing an XMC-5D ODU is
supported.
Conflux Position Local NE Local NE This parameter specifies the NE

whose IF port shares an ODU with
the IF port specified by Role.
Currently, only IF boards on the local
NE can share an ODU.
Conflux Port - - This parameter specifies the IF port

which shares an ODU with the IF port
specified by Role.

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

● Select the ODU from the Object Tree in the NE Explorer. Choose
● Click the Radio Frequency Attributes tab.
Navigation Path of RFU/RFU-SD

● Select the RFU/RFU-SD from the Object Tree in the NE Explorer. Choose
Configuration > RF Interface from the Function Tree.
● Click the Radio Frequency Attributes tab.
Parameters
Board - - This parameter indicates the

corresponding RFU/RFU-SD/ODU.
Transmit - - ● This parameter indicates or

Frequency(MHz specifies the transmit frequency of
) the RFU/RFU-SD/ODU, namely, the
central frequency of the channel.
● 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.
● The difference between the
transmit frequencies at both ends
of a radio link by ODU should be
one T/R spacing.

Receive - - ● This parameter indicates or

Frequency(MHz specifies 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 - - ● This parameter indicates or

Spacing(MHz) specifies the spacing between the
transmit frequency and receive
frequency of the ODU to prevent
mutual interference of the
transmitter and receiver.
● 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.
● 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.
● 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.
● 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

Frequency(MHz receive frequency of the RFU/RFU-
) SD/ODU.

Actual T/R - - This parameter indicates the actual

Spacing(MHz) T/R spacing of the ODU.
NOTE
RTN 980L.
The range of - - This parameter indicates the working

Transmit range of the transmit frequency of
frequency the RFU/RFU-SD/ODU.
point(MHz)
The range of - - This parameter indicates the working

Receive range of the receive frequency of the
frequency RFU/RFU-SD.
point(MHz) 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.

● Click the Power Attributes tab.

● Select the RFU/RFU-SD from the Object Tree in the NE Explorer. Choose
Configuration > RFInterface from the Function Tree.
● Click the Power Attributes tab.
Parameters


Maximum - - ● Maximum Transmit Power(dBm)

Transmit is set according to the network
Power(dBm) 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.
● This parameter is set to limit the
maximum transmit power of the
RFU/RFU-SD/ODU within this
preset range.
● The maximum transmit power
adjusted by using the ATPC
function should not exceed
Transmit - - ● Transmit Power(dBm) is set

Power(dBm) according to the network plan.
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).
● It is recommended that you set the
SD/ODU to the same value at both
ends of a radio link.
● 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 ● Power to Be Received(dBm) is

Received(dBm) 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.
● 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.
● 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.
● 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

Received(dBm) of an RFU-SD.
NOTE
This parameter is supported only when
the SD combination function is enabled
for OptiX RTN 980L.
TX High - - ● If the value of the actual transmit

Threshold(dBm) power of the RFU/RFU-SD/ODU is
greater than the preset value of
TX High Threshold(dBm), the
system separately records the
duration when the value of the
actual transmit power of the RFU/
RFU-SD/ODU is greater than the

TX Low - - preset value of TX High

Threshold(dBm) Threshold(dBm) and the duration
when the value of the actual
SD/ODU is greater than the preset
value of TX Low Threshold(dBm)
in the performance events.
● If the value of the actual transmit
power of the RFU/RFU-SD/ODU is
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.
● If the value of the actual transmit
lower than the preset value of TX
Low Threshold(dBm), the system
does not record it.
● TX High Threshold(dBm) and TX
Low Threshold(dBm) are valid
only when the ATPC function is
enabled.
RX High - - ● If the value of the actual receive

Threshold(dBm) power of the RFU/RFU-SD/ODU is
lower than the preset value of RX
Low Threshold(dBm), the system
records the duration when the
value of the actual receive power
of the RFU/RFU-SD/ODU is lower
than the preset value of RX Low
Threshold(dBm) and duration
when the value of the actual
SD/ODU is lower than the preset
value of RX High Threshold(dBm)
in the performance events.
● If the value of the actual receive
RX Low Threshold(dBm) and is
lower than the preset value of RX
High Threshold(dBm), the system

RX Low - - records the duration when the

Threshold(dBm) value of the actual receive power
of the RFU/RFU-SD/ODU is Lower
than the preset value of RX High
Threshold(dBm) in the
performance events.
● If the value of the actual receive
RX High Threshold(dBm), the
system does not record it.
SD RX High -90.0 to -20.0 - Specifies the upper threshold of SD

Threshold(dBm) receive power of an RFU-SD.
NOTE
for OptiX RTN 980L.
SD RX Low -90.0 to -20.0 - Specifies the lower threshold of SD

Threshold(dBm) receive power of an RFU-SD.
NOTE
for OptiX RTN 980L.
Actual Transmit - - ● This parameter indicates the

Power(dBm) actual transmit power of the RFU/
RFU-SD/ODU.
● 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

Power(dBm) receive power of the RFU/RFU-SD/
ODU.
Actual SD - - Displays the actual SD receive power

Receive of an RFU-SD.
Power(dBm) NOTE
for OptiX RTN 980L.
Actual range of - - This parameter indicates the range of

Power(dBm) the actual transmit power of the
RFU/RFU-SD/ODU.
Transmission - - This parameter indicates the level of

Power Type the 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.

Choose Configuration > ODU Interface from the Function Tree.
● Click the Equipment Information tab.

Choose Configuration > RF Interface from the Function Tree.
● Click the Equipment Information tab.
Parameters

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(MHz) spacing of the ODU.
NOTE
RTN 980L.
Intermediate - - This parameter indicates the IF

Frequency frequency bandwidth of the RFU/
Bandwidth RFU-SD/ODU.
(MHz)
IF Bandwidth - - Displays the IF bandwidth type.

Type
Station Type - - ● This parameter indicates whether

the RFU/RFU-SD/ODU is a Tx high
station or a Tx low station.
● 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

Power Type the 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.

● Click the Advanced Attributes tab.
Parameters
Board - - Indicates the corresponding ODU.

RF Loopback Non-Loopback Non-Loopback ● This parameter indicates or

Inloop specifies the loopback status of
the RF interface of the ODU.
● Non-Loopback indicates that the
performed.
● Inloop indicates that the RF
signals transmitted to the opposite
end are looped back.
● 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.
● In normal cases, RF Loopback is
set to Non-Loopback.
Configure unmute unmute ● Indicates or specifies the transmit

Transmission mute status of the ODU.
Status ● If Configure Transmission Status
is set to mute, the transmitter of
the ODU does not work but can
normally receive microwave
signals.
● If Configure Transmission Status
is set to unmute, the ODU can
normally transmit and receive
microwave signals.
● 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

corresponding SDH interface.
Optical - - This parameter indicates or specifies

Interface Namea the name of the optical interface.
Laser Switcha On On ● This parameter indicates or

Off specifies the on/off state of the
laser.
● This parameter is set for SDH
optical interfaces only.
● In normal cases, this parameter is
set to On.

Optical(Electric Non-Loopback Non-Loopback ● This parameter indicates or

al) Interface Inloop specifies the loopback status on
Loopbacka the SDH interface.
Outloop
performed.
● Inloop indicates that the SDH
received SDH signals are looped
back.
● This function is used for fault
locating for the SDH interfaces.
The Optical(Electrical) Interface
Loopback function is used for
diagnosis and may affect the
precaution before starting this
function.
VC4 Loopbackb Non-Loopback Non-Loopback ● This parameter indicates or

Inloop specifies the loopback status in the
VC-4 path.
Outloop
performed.
● Inloop indicates that the VC-4
received VC-4 signals are looped
back.
locating for the VC-4 paths. The
VC4 Loopback function is used for
precaution before starting this
function.

NOTE
● a: Indicates the parameters that are supported when Port is selected from the list box.
● 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 - - This parameter indicates the

Interface corresponding optical interface.
Automatic Disabled Disabled ● This parameter indicates or

Shutdown Enabled specifies whether the Automatic
Laser Shutdown function is
enabled or disabled for the laser.
● 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.
● 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 2000 to 300000 90000 This parameter indicates or specifies

On-test the period when a shutdown laser is
Period(ms) 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
Choose Configuration > PDH Interface from the Function Tree.
2. Select By Board/Port(Channel).
3. Select Port from the list box.
Parameters

corresponding port.
Port Name - - This parameter indicates or specifies

the name of the port.
Tributary Non-Loopback Non-Loopback ● This parameter indicates or

Loopback Inloop specifies the loopback status in the
associated path of the tributary
Outloop unit.
performed.
● Inloop indicates that the PDH
received PDH signals are looped
back.
locating for the paths of the
tributary unit. The Tributary
Loopback function is used for
precautions before starting this
function.

Port Impedance - - This parameter indicates the

impedance of a path, which depends
on the tributary unit.
Service Load Load Load ● This parameter indicates or

Indication Non-Loaded specifies the service loading status
in a specific path.
Load, the board detects whether
alarms exist in the path.
Non-Loaded, the board does not
detect whether there are alarms in
the path.
● 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 ● This parameter indicates whether

Equalization Equalized the input signals are equalized.
this parameter to default value.

Retiming Mode Normal Normal ● This parameter indicates or

Retiming Mode specifies the retiming mode of a
of Tributary Clock specific path.
Retiming Mode ● By using the retiming function, the
of Cross-Connect retiming reference signal from the
Clock SDH network and the service data
signal are combined and then sent
to the client equipment, therefore
decreasing the output jitter in the
signal. In this way, the retiming
function ensures that the service
code flow can normally transfer
the retiming reference signal.
Normal, the retiming function is
not used.
Retiming Mode of Tributary
Clock, the retiming function is
used with the clock of the
upstream tributary unit traced.
Retiming Mode of Cross-Connect
Clock, the retiming function is
used with the clock of the cross-
connect unit traced.
● It is recommended that the
external clock, instead of the
retiming function, should be used
to provide reference clock signals
for the equipment.
● If the retiming function is required,
it is recommended that you set
this parameter to Retiming Mode
of Cross-connect Clock.
Port Service E1 E1 If the system control board is

Type T1 SLF2CSHO, the PDH ports of SP3S
and SP3D boards and the PDH port
integrated on SLF2CSHO boards can
work in T1 mode. On other RTN 900
series products, Port Service Type
can be set only to E1.
Output Signal Unequalized Unequalized ● This parameter indicates whether

Equalization Equalized the output signals are equalized.
the default value.

E1 Frame Unframe Unframe Specifies the E1 frame format for E1

Format Double Frame ports.
CRC-4 Multiframe ● To detect E1 BER performance on
an OptiX RTN 900, set E1 Frame
Format of the local E1 port to the
same value as that of the opposite
E1 port. It is recommended that E1
Frame Format of both the local
and opposite E1 ports be CRC-4
Multiframe.
● 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

Format Deselected in the text format.
Display in Selected Deselected This parameter specifies the display

Hexadecimal Deselected in the hexadecimal format.

Object - - This parameter indicates the object to

be set.
J0 to be - [16 If the NE at the opposite end reports

Sent([Mode]Con Bytes]HuaWei the J0_MM alarm, this parameter is
tent) SBS set according to the J0 byte to be
received at the opposite end.
J0 to be - [Disabled] ● This parameter specifies the J0

Received([Mode byte to be received.
]Content) ● If this parameter is set to
[Disabled], the board does not
monitor the received J0 byte.
the default value.
J0 - - This parameter indicates the J0 byte

Received([Mode that is actually received.
]Content)
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
Function Tree.




Parameters for the Trace Byte J1


be set.
J1 to be - [16 If the NE at the opposite end reports

Sent([Mode]Con Bytes]HuaWei the HP_TIM alarm, this parameter is
tent) SBS set according to the J1 byte to be
J1 to be - [Disabled] ● If this parameter is set to

Received([Mode [Disabled], the board does not
]Content) monitor the received J1 byte.
the default value.
J1 - - This parameter displays the J1 byte

Received([Mode that is actually received.
]Content)
Parameters for the Signal Flag C2


be 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
C2 to be - - If the NE at the local end reports the

Received 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


be set.
VC4 Overhead Termination Auto ● If this parameter is set to Pass-

Termination Pass-Through Through, the NE forwards the
original overhead after monitoring
Auto the VC-4 path overhead regardless
of the C2 byte.
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.
● 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.
the 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
Choose Configuration > Overhead Management > VC12 Path Overhead




Parameters for the Trace Byte


be set.
J2 to be Sent - [16 If the NE at the opposite end reports

Bytes]HuaWei the LP_TIM or LP_TIM_VC12 alarm,
SBS this parameter is set according to the
J2 byte to be received by the NE at
the opposite end.
J2 to be - [Disabled] ● If this parameter is set to

Received [Disabled], the board does not
monitor the received J2 byte.
the 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


be set.
Signal - - If the NE at the opposite end reports

Label(L1,L2,L3 the LP_SLM or LP_SLM_VC12 alarm,
of V5) to be this parameter is set according to the
Sent V5 byte to be received at the
opposite end.

Signal - - If the NE at the local end reports the

Label(L1,L2,L3 LP_SLM or LP_SLM_VC12 alarm, this
of V5) to be parameter is set according to the V5
Received byte to be sent at the opposite end.
NOTE
IF boards do not support this parameter.
Signal - - This parameter displays the V5 byte

Label(L1,L2,L3 that is actually received.
of 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

the port name of an
Ethernet virtual
interface.


Range Value
Port Type EoA EoA This parameter

Virtual Virtual displays or specifies
Interface Interface the port type of an
VLAN Sub Ethernet virtual
Interface interface.
OptiX RTN 900 allows
Port Type to be set to
VLAN Sub Interface
only.
Port Mode - Layer 3 This parameter

the port mode of an
Ethernet virtual
interface.
Associated Board - - This parameter

the board where an
Ethernet virtual
interface is located.
Associated Port - - This parameter

the port 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.
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.


Range Value
Specify IP Address Manually Unspecifi This parameter

Unspecifi ed specifies whether to
ed set the IP address for
a port.
● Unspecified:
indicates that the
IP address will not
be specified for a
port.
● 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.
● 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.2 This parameter

55.252 specifies the subnet
mask for a port.
set only when Specify
IP Address is
Manually.


Range Value
Enable Tunnel Enabled Disabled This parameter

Disabled specifies 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.
● Unspecified: indicates that the IP
address will not be specified for a
port.
● 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.
when Specify IP Address is
Manually.
● 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.5.13 Parameter Description: COMBO Port

This section describes the parameters for configuring the COMBO port.
Navigation Path
In the NE Explorer, select the desired NE from the object tree. Choose
Configuration > COMBO Interface from the function tree.
Basic Attribute Parameters

Port - - This parameter indicates a cascade

port on the ISM8 board.
COMBO Port Disable Disable This parameter specifies how a port

Status CA functions.
XPIC
MIMO
B.6 Parameters for Ethernet Services and Ethernet

Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet
features on the packet plane, including service parameters, protocol parameters,
OAM parameters, Ethernet port parameters, and QoS parameters.

B.6.1 Parameters for Ethernet Services

This topic describes the parameters that are related to Ethernet services.
B.6.1.1 Parameter Description: E-Line Service_Creation (NCE)

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 ● This parameter

UNI-NNI specifies the
direction of the
NNI-NNI E-Line service.
● Set this
parameter to
UNI-UNI.

BPDU Not Transparently Not Transparently ● RTN NEs support

Transmitted Transmitted only Not
Transparently
Transmitted.
● 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 - - ● Before setting

this parameter,
ensure that Port
Mode is Layer 2
or Layer Mix.
● The value of this
parameter
cannot be the
same as the
value of sink
port.
parameter
cannot be used
for the E-LAN
port.
set according to
the planning
information.

Source VLANs 1 to 4094 - ● 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.
● If this parameter
is set to null, all
the services at
the source port
are used as the
service source.
is not set to null,
only the service
that contains the
VLAN ID at the
source port can
be used as the
service source.

Sink Port - - ● Before setting

this parameter,
ensure that Port
Mode is Layer 2
or Layer Mix.
parameter
cannot be the
same as the
value of Source
Port.
parameter
cannot be used
for the E-LAN
port.
set according to
the planning
information.

Sink VLANs 1 to 4094 - ● 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.
is set to null, all
the services at
the sink port are
used as the
service sink.
is not set to null,
only 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)


specifies the ID of
the E-Line service.

specifies the name
of the E-Line
service.


direction of the
● Set this
parameter to
UNI-NNI.
BPDU Not Transparently Not Transparently ● RTN NEs

Transmitted Transmitted support only
Transparently Not
Transmitted Transparently
Transmitted.
● 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.

cannot be set here.

Service Tag Role User User This parameter

Service needs to be
specified only when
Direction is
UNI-NNI
and Bearer Type is
PW.

this parameter,
ensure that Port
Mode is Layer 2
or Layer Mix.
parameter
cannot be the
same as the
value of sink
port.
parameter
cannot be used
for the E-LAN
port.
● This parameter
is set according
to the planning
information.


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.
is set to null, all
the services at
the source port
are used as the
service source.
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 UNI-NNI ETH

PW PWE3 services, the
parameter value is
always PW.

Protection Type No Protection No Protection ● If this parameter

PW APS is set to PW
APS, working
Slave Protection and protection
Pair PWs need to be
configured.
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
simultaneously.
Table B-5 Service direction of UNI-NNI (carried by QinQ links)


specifies the ID of
the E-Line service.

specifies the name
of the E-Line
service.

direction of the
● Set this
parameter to
UNI-NNI.

BPDU Not Transparently Not Transparently ● RTN NEs

Transmitted Transmitted support only
Transparently Not
Transmitted Transparently
Transmitted.
● 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.
.

cannot be set
here.
Service Tag Role - - OptiX RTN 900

does not support
this parameter.


this parameter,
ensure that
Port Mode is
Layer 2 or
Layer Mix.
● The value of
this parameter
cannot be the
same as the
value of sink
port.
● The value of
this parameter
cannot be used
for the E-LAN
port.
● This parameter
is set according
to the planning
information.


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.
● If this
parameter is
set to null, all
the services at
the source port
are used as the
service source.
● 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


specifies the ID of the
E-Line service.

specifies the name of
the E-Line service.

direction of the E-
NNI-NNI Line service.
to NNI-NNI.

BPDU Not Transparently Not Transparently ● RTN NEs support

Transmitted Transmitted only Not
Transparently Transparently
Transmitted Transmitted.
● 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.

not support this
parameter.
PRI - - OptiX RTN 900 does

not support this
parameter.
Bearer Type 1 QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line
service.

QinQ Link ID 1 - - ● Selects the QinQ

link ID of the first
QinQ link.
● The QinQ link ID is
preset in QinQ
Link.
Bearer Type 2 QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line
service.
QinQ Link ID 2 - - ● Selects the QinQ

link ID of the
second QinQ link.
● The QinQ link ID is
preset in 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.
Parameters of PWs
NOTE
● Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type
is PW.
● 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 ● Specifies the type

Ethernet Tagged of the PW.
Mode ● 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
● This function limits
the bandwidth of
one or more PWs in
an MPLS tunnel.
● 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 support this
parameter.

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.
It is recommended
that you set this
parameter to the
same value as CIR.
PBS (byte) - - Specifies the peak

burst size (PBS) of a
PW.
EXP - - OptiX RTN 900 does

not support this
parameter.
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 ● Specifies the mode

Alert Label of PW continuity
check.
CW
● None indicates that
VCCV is not used.
● Alert Label
indicates VCCV
packets in Alert
Label
encapsulation
mode.
● CW: indicates that
VCCV packets
encapsulated based
on the control word
are used.
VCCV Verification Ping Ping ● Specifies the VCCV

Mode None verification mode.
The VCCV
verification is used
for PW continuity
check.
● If the VCCV-Ping
test is required, do
not set this
parameter to None.

Request VLAN - - ● Set this parameter

when PW Type is
Ethernet Tagged
Mode.
● 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 ● Specifies the

Enabled enabling status of
the PW protection
group.
● 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
dual-ended switching.
Revertive Mode Non-revertive Revertive ● This parameter

Revertive specifies whether
to switch services
back to the original
working PW after it
recovers.
● 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.
● The value
Revertive is
recommended.

Switchover 1 to 12 1 ● Specifies the WTR

Restoration Time time of the
(min) protection group.
● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.
● The default value is
recommended.
Switchover Delay 0 to 100 0 ● Specifies the hold-

Time (100 ms) off time of the
protection group.
set 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
● The OAM parameters of the PW APS protection group need to be configured if the
Protection Type of PWs is set to PW APS.
● 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 ● Specifies the

Manual detection mode of
OAM packets.
● Manual: The CC
packets are sent at
the interval
specified by the
user.
● Auto-Sensing: The
CC packets are sent
at the interval of
receiving PW OAM
packets.
● If Detection Mode
is set to Manual,
you need to set the
PW OAM detection
packets to be
received and
transmitted.
● The value Auto-
Sensing is
recommended.

Detection Packet CV CV ● CV: The detection

Type FFD packets are sent at
a fixed interval.
● FFD: The detection
packets are sent at
the interval
specified by the
user.
is set to Auto-
Sensing, this
parameter specifies
the PW OAM
detection packets
to be transmitted.
is set to Manual,
this parameter
specifies the PW
OAM detection
packets to be
received and
transmitted.
● The value FFD is
assumed for PW
APS and the value
CV is assumed for
continuous CC on
PWs.
Packet Detection 3.3 50 ● Specifies the period

Interval(ms) 10 of detection
packets.
20
50 configurable when
100 Detection Packet
200 Type is FFD and
assumes the fixed
500 value of 1000 when
Detection Packet
Type is CV.
to 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
of PWs is set to Slave Protection Pair.

protection 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

protection PW in the
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

E-Line service.


the E-Line service.

direction of the E-
to UNI-UNI.
BPDU Not Transparent Not Transparent ● RTN NEs support

Transparent only Not
Transparently
Transmitted.
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
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.

be set here.
Service Tag Role - - This parameter is not

supported when
Direction is UNI-UNI.

Source Port - - ● Before setting this

parameter, ensure
that Port Mode is
Layer 2 or Layer
Mix.
parameter cannot
be the same as the
value of sink port.
parameter cannot
be used for the E-
LAN port.
set according to
the planning
information.
Source VLAN ID 1 to 4094 - ● 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.
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 Interface - - ● Before setting this

parameter, ensure
that Port Mode is
Layer 2 or Layer
Mix.
parameter cannot
be the same as the
value of Source
Port.
parameter cannot
be used for the E-
LAN port.
set according to
the planning
information.
Sink VLAN ID 1 to 4094 - ● 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
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-8 Service direction of UNI-NNI (carried by PWs)


E-Line service.

the E-Line service.

direction of the E-
to UNI-NNI.

Transparently
Transmitted.
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
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.


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.
parameter cannot
be the same as the
value of sink port.
parameter cannot
be used for the E-
LAN port.
set according to
the planning
information.

Source VLANs 1 to 4094 - ● 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 ● 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-9 Service direction of UNI-NNI (carried by QinQ links)


E-Line service.

the E-Line service.

direction of the E-
to UNI-NNI.


Transparently
Transmitted.
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
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.

be set here.

supported when
Direction is UNI-NNI
and Bearer Type is
QinQ Link.


parameter, ensure
that Port Mode is
Layer 2 or Layer
Mix.
parameter cannot
be the same as the
value of sink port.
parameter cannot
be used for the E-
LAN port.
set according to
the planning
information.
Source VLANs 1 to 4094 - ● 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
and 6.
services at the
source port are
used as the service
source.
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.
Table B-10 Service direction of NNI-NNI


E-Line service.

the E-Line service.

direction of the E-
to NNI-NNI.


Transparently
Transmitted.
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
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.

be set here.

supported when
Direction is NNI-NNI.
PRI - - OptiX RTN 900 does

not support this
parameter.
Bearer Type QinQ Link QinQ Link Uses the QinQ link to
carry the E-Line
service.

Parameters for Port Attributes

Port Name - - This parameter

displays the UNI port.
Enable Port Enabled - ● This parameter

Disabled displays or specifies
whether the port is
enabled.
● Ethernet services
can be received,
processed, and
forwarded normally
only if Port Enable
is set to Enabled.
● Port Enable is
already set in
Ethernet Interface.
Port Mode Layer 2 - ● Specifies the

Layer 3 working mode of
an Ethernet port.
set 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.
● When this
parameter is set to
Layer 3, Ethernet
services over the
port can be carried
by PWs.


802.1Q displays or specifies
the method of the
QinQ port to process the
received packets.
● If you set this
parameter to Null,
the port
transparently
transmits the
received packets.
● If you set this
parameter to
802.1Q, the port
identifies the
packets that
comply with the
IEEE 802.1q
standard.
● If you set this
parameter to
QinQ, the port
identifies the
packets that
comply with the
IEEE 802.1ad
standard.

Working Mode Auto-Negotiation - ● The Ethernet ports

support different
10M Full-Duplex working modes.
100M Half-Duplex ● When the
100M Full-Duplex equipment on the
1000M Full-Duplex opposite side works
in auto-negotiation
mode, set the
working mode of
the equipment on
the local side to
Auto-Negotiation.
● 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.
● When the
equipment on the
opposite side works
in half-duplex
mode, set the
working mode of
the equipment on
the local side to
10M Half-Duplex,
100M Half-
Duplex, or Auto-
Negotiation
depending on the
port rate of the
equipment on the
opposite side.
● The GE optical
interface supports
the 1000M full-
duplex mode only.

Tag Tag Aware Tag Aware ● If all the accessed

with the VLAN tag
set TAG to Tag
Aware.
services are frames
without the VLAN
tag (untagged
frames), set TAG to
Access.
● If the accessed
services contain
tagged frames and
untagged frames,
set TAG to Hybrid.
Specify IP Address Unspecified - ● Displays or selects

Manually the method to
configure IP
addresses of ports.
● The value
Unspecified
indicates that the
IP addresses do not
need to be
configured for a
port.
● The value
Manually indicates
that the IP address
of a port can be
manually
configured.
available when
Port Mode is Layer
3.
IP Address - - ● Displays or
specifies the IP
address of the port.
available when
Specify IP Address
is Manually.

IP Mask - - ● Displays or
specifies the subnet
mask of the port.
available when
Specify IP Address
is Manually.
Parameters of PWs
NOTE
● Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type
is PW.
PW ID - - Specifies the ID of the

PW that carries
services.

need to be manually
assigned.

Ethernet Tagged Mode of the PW.
● 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 MPLS MPLS Displays the

Type encapsulation type of
the packets on the
PW.

Ingress label.

Egress label.

the tunnel that carries
the 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

Use existing resource 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.

Parameters of Advanced Attributes (PW)


words when
encapsulating ETH
PWE3 packets.
NOTE
control words when
encapsulating ETH

check.
CW
VCCV is not used.
● Alert Label
indicates VCCV
packets in Alert
Label
encapsulation
mode.
VCCV packets
encapsulated based
on the control word
are used.

The VCCV
for PW continuity
check.
not set this
parameter to None.


when PW Type is
Ethernet Tagged
Mode.
● 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.
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.

bandwidth limit
the bandwidth of
one or more PWs in
an MPLS tunnel.
● An ETH PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ETH
PWE3 services in an
MPLS tunnel.

not support this
parameter.


committed
of a PW.
It is recommended
that you set this
parameter to the
same value as PIR.

(CBS) of a PW.

of a PW.
It is recommended
that you set this
parameter to the
same value as CIR.

PW.

not support this
parameter.

MPLS tunnel labels
from packets, an
priority for the
packets.

NOTE

protection type.



the PW protection
group.
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.
NOTE

working PW.

protection PW.

mode to be used
when a PW fails.
NOTE


to switch services
working PW after it
recovers.
● 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.
● The value
Revertive is
recommended.

● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.
recommended.


protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.
recommended.

mode of the PW APS
protection group.
OAM Parameters
NOTE

status of PW OAM.


OAM packets.
● Manual: The CC
packets are sent at
the interval
specified by the
user.
CC packets are sent
at the interval of
receiving PW OAM
packets.
is set to Manual,
you need to set the
PW OAM detection
packets to be
received and
transmitted.
● The value Auto-
Sensing is
recommended.


a fixed interval.
packets are sent at
the interval
specified by the
user.
is set to Auto-
Sensing, this
parameter specifies
the PW OAM
detection packets
to be transmitted.
is set to Manual,
this parameter
specifies the PW
OAM detection
packets to be
received and
transmitted.
assumed for PW
APS and the value
CV is assumed for
continuous CC on
PWs.

packets.
20
200 Type is FFD and
assumes the fixed
Detection Packet
Type is CV.
to 3.3 for PW APS.

be received.

be received.


NOTE

protection mode.

master PW APS
protection group
of the slave PW APS
protection group
simultaneously.

working PW in the

B.6.1.3 Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
Navigation Path


E-Line service.


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 - ● RTN NEs support

Transmitted only Not
Transparently Transparently
Transmitted Transmitted.
Transparently
Transmitted, no
special channel is
established for
transparently
transmitting
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.

Deployment Status - - This parameter

indicates whether E-
Line service is
deployed.
Parameters Associated with UNI Ports


indicates the UNI port.

VLANs 1 to 4094 - This parameter

the VLAN ID of the
UNI port.
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
and 6.
valid only when
Direction is set to
UNI-UNI or UNI-
NNI in the process
of creating an E-
Line service.
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 - - This parameter

Type 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
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

Mode displays the VCCV
mode.
Local Operating - - Displays the working

Status status of the PW at
the local end.
Remote Operating - - This parameter

Status displays the working
status of the PW at
the remote end.
Overall Operating - - This parameter

Status displays the
comprehensive
working status of the
PW.
Request VLAN - - This parameter

displays the request
VLAN.

displays the
deployment status.
Tunnel for Auto - - This parameter

Selection displays 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 - ● This parameter

indicates the QinQ
link ID of the QinQ
link connected to
the NNI port.
valid only when
Direction is set to
UNI-UNI or UNI-
NNI in the process
of creating an E-
Line service.
Port - - ● This parameter

indicates the NNI
port.
valid only when
Direction is set to
UNI-UNI or UNI-
NNI in the process
of creating an E-
Line service.
S-VLAN ID - - ● This parameter

indicates or
specifies the VLAN
ID of the NNI port.
valid only when
Direction is set to
UNI-NNI or NNI-
NNI in the process
of creating an E-
Line service.
preset in QinQ
Link.
QoS Parameters
displays the PW ID.

Direction - - ● This parameter

displays the
direction of a PW.
● Egress: indicates
the egress direction
of a PW.
● Ingress: indicates
the ingress
direction of a PW.
Bandwidth Limit - - This parameter

whether the
bandwidth limit
a PW to prevent
network congestion.
● Regarding
transmission
channels, this
function can be
used to limit the
bandwidth of one
or more PWs in an
MPLS tunnel.
● 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 - - The OptiX RTN 900

does not support this
parameter.
CIR (Kbit/s) - - This parameter

the committed
for a PW.
It is recommended
that you set this
parameter to the
same value as PIR.

CBS (kbyte) - - This parameter

the committed burst
size (CBS) for a PW.
PIR (kbit/s) - - This parameter

the peak information
rate (PIR) for a PW.
It is recommended
that you set this
parameter to the
same value as CIR.
PBS (kbyte) - - This parameter

the peak burst size
(PBS) for a PW.
EXP - - The OptiX RTN 900

parameter.

MPLS tunnel labels
from packets, an
priority for the
packets.
Parameters for the Port Attributes


information.
Enable Port - - ● This parameter

indicates whether
to enable the port.
preset in General
Attributes of
Ethernet Interface.


802.1Q indicates the
encapsulation type
QinQ of the port.
valid only when
Direction is set to
UNI-UNI or UNI-
NNI in the process
of creating an E-
Line service.
set to Null, the
port transparently
transmits the
received packets.
set to 802.1Q, the
port identifies the
packets that
comply with the
IEEE 802.1Q
standard.
set to QinQ, the
port identifies the
packets that
comply with the
IEEE 802.1 QinQ
standard.
preset in General
Attributes of
Ethernet Interface.
TAG Tag Aware - ● This parameter

Access displays the tag of
the port.
Hybrid
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 to be
created.

working PW.

protection PW.
Protection Type - - Displays the

protection mode.
Enabling Status Enabled - ● Displays or

Disabled specifies the
enabling status of
the PW protection
group.
of a protection
group, set Enabling
Status to Disabled.
After the APS
protection group is
configured at both
ends, set Enabling
Status to Enabled.
Switchover Mode - - Displays the switching

mode to be used
when a PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.

Revertive Mode Non-revertive - ● Specifies whether

Revertive to switch services
to the original
working PW after
the fault is
rectified.
● 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.
● The value
Revertive is
recommended.
Switchover WTR 1 to 12 - ● Displays or

Time (min) specifies the WTR
time of the
protection group.
● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.

Switchover Hold-off 0 to 100 - ● Displays or

Time (100 ms) specifies the hold-
off time of the
protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.
Deployment Status - - Display the

deployment status of
Switchover Status - - Displays the

switchover status of
Protocol Status - - Displays the enabling

status of the protocol.
Working Path Status - - Displays the status of

the current working
path.
Protection Path - - Display the status of

Status the current protection
path.

NOTE
The following parameters are available only after the slave protection pair is configured.


master PW APS
protection group
of the slave PW APS
protection group
simultaneously.

working PW in the

DNI PW ID - - Displays the DNI PW

ID.
PW Type - - Displays the PW type.
Deployment Status - - Displays the

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

attribute of the source
interface.

Source Interface - - This parameter

specifies the source
interface.
Source VLAN ID 1 to 4094 - This parameter

of the source service.
Sink Interface Type V-UNI V-UNI This parameter

attribute of the sink
interface.
Sink Interface - - This parameter

specifies the sink
interface.
Sink VLAN ID 1 to 4094 - This parameter

of the sink service.
NOTE
● 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.
● 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.
● 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 (NCE)

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 - ● This parameter

specifies the ID of
the E-LAN service.
● OptiX RTN 900
supports
simultaneous
creation of an E-
LAN service only.

the E-LAN service.

BPDU - - ● In the case of an E-

LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
● 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.
● If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
transmitting
IEEE 802.1d-bridge
services (that is,
transparent bridge-
based 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.

Tag Type C-Aware C-Aware ● C-Aware indicates

S-Aware that the packets
are learnt
Tag-Transparent according to C-Tag
(the VLAN tag on
the client-side). To
create the 802.1q
bridge, set this
parameter to C-
Aware.
● 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.
● Tag-Transparent
indicates that the
packets are
transparently
transmitted. To
create the 802.1d
bridge, set this
parameter to Tag-
Transparent.
set according to
the planning
information.

Self-Learning MAC Enabled Enabled ● This parameter

Address Disabled specifies whether
to enable the MAC
address self-
learning function.
● 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.
learning function
of an Ethernet LAN
is disabled, a static
MAC address
forwarding table is
recommended to
be configured.
MAC Address IVL - ● This parameter

Learning Mode SVL indicates the mode
used to learn an
MAC address.
● 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.

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 ● If this parameter is

PW APS set to PW APS,
working and
Slave Protection Pair protection PWs
must be
configured. If this
parameter is set to
Slave Protection
Pair, ensure that a
PW APS protection
group to which the
slave protection
pair is bound has
been configured.
● 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


SVLAN/SVLANs 1 to 4094 - ● This parameter

specifies the S-
VLAN ID of the UNI
port.
valid only when
Tag Type is set to
S-Aware.
set according to
the planning
information.

VLANs/CVLAN 1 to 4094 - ● This parameter

specifies the VLAN
ID of the UNI port.
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
and 6.
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.
valid only when
Tag Type is set to
S-Aware.
SVLANs - - ● This parameter

specifies the S-
VLAN ID of the
NNI port.
valid only when
Tag Type is set to
S-Aware.
Parameters of NNIs (PW)

NOTE
● PW parameters need to be configured for only PW-carried E-LAN services.

PW ID - - Specifies the ID of
the PW that carries
services.

need to be manually
assigned.


Ethernet Tagged of the PW.
Mode ● 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

PW Encapsulation Type MPLS MPLS Displays the

encapsulation type
of the packets on
the PW.

Ingress label.

Egress label.
Tunnel selection mode - - Displays the method

to select tunnels.

the tunnel that
carries the PW.

of a PW will fail.


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.
Parameters for the Split Horizon Group

Split Horizon Group - 1 ● This parameter

ID indicates the ID of
the split horizon
group.
● The default split
horizon group ID is
1 and cannot be
set manually.

Split Horizon Group - - ● A split horizon

Member group member
indicates the
logical port
member in the split
horizon group.
● The port members
that are added to
the same split
horizon group
cannot
communicate with
each other.
● OptiX RTN 900
supports only the
division of the split
horizon group
members according
to the Ethernet
physical port.
● 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 - ● This parameter

specifies the ID of
the E-LAN service.
● The NE supports
simultaneous
creation of an E-
LAN service only.

the E-LAN service.


LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
Protocol (STP) is
configured, Not
Transparently
Transmitted
indicates that
BPDU packets are
considered as
protocol packets
the STP topology.
● If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
transmitting
IEEE 802.1d-bridge
services (that is,
transparent bridge-
based 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.


are learnt
(the VLAN tag on
create the 802.1q
bridge, set this
parameter to C-
Aware.
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.
● Tag-Transparent
indicates that the
packets are
transparently
transmitted. To
create the 802.1d
bridge, set this
parameter to Tag-
Transparent.
set according to
the planning
information.


Address Disabled specifies whether
to enable the MAC
address self-
learning function.
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.
learning function
of an Ethernet LAN
MAC address
forwarding table is
recommended to
be configured.
MAC Address IVL - ● This parameter

Learning Mode SVL indicates the mode
used to learn an
MAC address.
● When the bridge
uses the SVL mode,
all the VLANs share
one MAC address
uses the IVL mode,
each VLAN has an
MAC address table.

displays the port
name.

Port Type - - This parameter

displays the port type.
● 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.
● When the
parameter value is
NNI, the port
connected to the
bridge is an NNI
port. That is, this
port functions as
the NNI port
connected to the
IEEE 802.1ad
bridge.
● When the
parameter 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.
● When the
parameter 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 - ● This parameter is

valid only when
Tag Type is set to
C-Aware and Tag
is set to Access or
Hybrid.
● When the
parameter value is
null, it indicates
that the entire
physical port is
connected to the
bridge.
● You need to set this
parameter
according to the
planning
information.

C-VLAN 1 to 4094 - ● This parameter is

valid only when
Tag Type is set to
S-Aware.
● This parameter
specifies the VLAN
ID of the UNI port.
● You may 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.
● When the
parameter 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.
● When the
parameter 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 - ● This parameter is

valid only when
Tag Type is set to
S-Aware.
● This parameter
specifies the S-
VLAN 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.
● You need to set this
parameter
according to the
planning
information.

displays whether
the port is enabled.
can be received,
processed, and
forwarded normally
only if Enable Port
is set to Enabled.
● Enable Port is
already set in
Ethernet Interface.


support different
in auto-negotiation
mode, set the
working mode of
the equipment on
the local side to
Auto-Negotiation.
● 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.
● When the
equipment on the
opposite side works
in half-duplex
mode, set the
working mode of
the equipment on
the local side to
10M Half-Duplex,
100M Half-
Duplex, or Auto-
Negotiation
depending on the
port rate of the
equipment on the
opposite side.
● The GE optical
interface supports
the 1000M full-
duplex mode only.


method of the port
QinQ to process the
received packets.
● If you set this
parameter to Null,
the port
transparently
transmits the
received packets.
● If you set this
parameter to
802.1Q, the port
identifies the
packets that
comply with the
IEEE 802.1q
standard.
● If you set this
parameter to
QinQ, the port
identifies the
packets that
comply with the
IEEE 802.1ad QinQ
standard.

with the VLAN tag
this parameter is
set to Tag Aware.
services are frames
without the VLAN
tag (untagged
frames), this
parameter is set to
Access.
● If the accessed
services contain
tagged frames and
untagged frames,
this parameter is
set to Hybrid.

Default VLAN 1 to 4094 1 ● Default VLAN ID is

valid only when
TAG is set to
Access or Hybrid.
● Default VLAN ID is
set according to
the actual
situations.
Parameters on the Main Interface (Setting Service Parameters)

Split Horizon Group Selected Deselected This parameter

Deselected specifies whether to
create a split horizon
group.
Split Horizon Group - - ● This parameter

ID displays the ID of
the split horizon
group.
● The ID of the split
horizon group is 1
by default and
cannot be specified
manually.


Member group member
indicates the
logical port
member in the split
horizon group.
that are added to
the same split
horizon group
cannot
communicate with
each other.
● The NE supports
only the division of
the split horizon
group members
according to the
Ethernet physical
port.
● If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
member, the
mounted with the
logical port is
automatically
added to the split
horizon group
member.
B.6.1.7 Parameter Description: E-LAN Service(NCE)

This topic describes the parameters that are related to E-LAN services.
Navigation Path



E-LAN service.

the E-LAN service.


LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
Protocol (STP) is
configured, Not
Transparently
Transmitted
indicates that
BPDU packets are
considered as
protocol packets
the STP topology.
● If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
transmitting
IEEE 802.1d-bridge
services (that is,
transparent bridge-
based 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.


are learnt
(the VLAN tag on
create the 802.1q
bridge, set this
parameter to C-
Aware.
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.
● Tag-Transparent
indicates that the
packets are
transparently
transmitted. To
create the 802.1d
bridge, set this
parameter to Tag-
Transparent.


Address indicates whether
to enable the MAC
address self-
learning function.
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.
learning function
of an Ethernet LAN
MAC address
forwarding table is
recommended to
be configured.
MAC Address - - ● This parameter

Learning Mode indicates the mode
used to learn an
MAC address.
● When the bridge
uses the SVL mode,
all the VLANs share
one MAC address
uses the IVL mode,
each VLAN has an
MAC address table.
MTU(byte) - - This parameter cannot

be queried here.

not support this
parameter.


LAN service is
deployed.
Parameters for UNIs


SVLAN 1 to 4094 - ● This parameter

specifies the S-
VLAN ID of the UNI
port.
valid only when
Tag Type is set to
S-Aware.
set according to
the planning
information.

VLANs/CVLAN 1 to 4094 - ● This parameter

specifies the VLAN
ID of the UNI port.
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 en dash
(-) to represent a
consecutive
number. For
example, the
numbers 1, and 3-6
and 6.
set to null, the E-
LAN service
exclusively uses the
corresponding UNI
physical port. That
is, the entire port is
mounted to the
bridge.
set 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.
valid only when
Tag Type is set to
S-Aware.
SVLANs - - ● This parameter

specifies the S-
VLAN ID of the UNI
port.
valid only when
Tag Type is set to
S-Aware.
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 en dash
(-) to represent a
consecutive
number. For
example, the
numbers 1, and 3-6
and 6.
NNI Parameters (PW)

displays the PW ID.
Working Status - - This parameter

displays the working
status of a PW.


is enabled.

displays the PW
signaling type.
NOTE
static PWs only.

displays the
configured PW type.

of a PW.

Type displays the PW
encapsulation type.
NOTE
MPLS only.

displays the
configured PW ingress
label.

displays the
configured PW egress
label.
Tunnel Type MPLS MPLS This parameter

displays the type of
a PW.

displays the opposite
LSR ID.
Tunnel - - This parameter


ETH PWE3 service
uses Control Word.


channel type.

mode.

the local end.

status of the PW at
the remote end.

Status displays the
comprehensive
PW.

VLAN.

displays the
deployment status.


does not support
request VLAN TPID of
the PW level.

Parameters for Static MAC Addresses

VLAN ID - - ● This parameter is

invalid if MAC
Address Learning
Mode is SVL. That
is, the preset static
MAC address
entries are valid for
all VLANs.
● 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.
set according to
the planning
information.

indicates or
specifies the static
MAC address.
● A static MAC
address is an
address that is set
manually. It is not
aged automatically
and needs to be
deleted manually.
● 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 - - ● This parameter

specifies the
Ethernet port that
corresponds to the
MAC address.
set according to
the planning
information.
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.
● If MAC Address
Learning Mode is
set to IVL, the
preset self-learning
MAC address
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
set according to
the planning
information.


indicates or
specifies the self-
learning MAC
address. A self-
learning MAC
address is also
called a dynamic
MAC address.
● 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.

specifies the
Ethernet port that
corresponds to the
MAC address.
set according to
the planning
information.
Parameters Associated with MAC Address Learning Parameters

Aging Ability Enabled Enabled OptiX RTN 900

Disabled supports enabling/
disabling of the aging
function and aging
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

Aging Time(min) 1 to 640 5 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 0 to 16384 512 ● This parameter is

Table Capacity supported only by
the OptiX RTN
950A/905/
RTN910A and the
OptiX RTN 950 that
houses CSHU/
CSHUA boards.
● This parameter
specifies the MAC
address forwarding
table capacity for
E-LAN services.
Address Detection 80 to 100 95 ● This parameter is

Upper Threshold (%) supported only by
the OptiX RTN
950A/905/910A
and the OptiX RTN
950 that houses
CSHU/CSHUA
boards.
● When the MAC
address forwarding
table capacity for
E-LAN services is
greater than
Address Detection
Upper Threshold
(%), an
FDBSIZEALM_ELAN
alarm is reported.
When the MAC
address forwarding
table capacity for
E-LAN services is
less than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELAN
alarm

Address Detection 60 to 100 90 automatically

Lower Threshold (%) clears.
Parameters for Disabled MAC Addresses

VLAN ID - - This parameter

the VLAN ID of the
service. A disabled
MAC address is valid
for the VLAN whose
VLAN ID is equal to
the preset VLAN ID.

specifies or
indicates the
disabled MAC
address. A disabled
MAC address is
also called a
blacklisted MAC
address.
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.



the split horizon
group.
horizon group ID is
1 and cannot be
set manually.

Member group member
indicates the
logical port
member in the split
horizon group.
that are added to
different split
horizon groups
cannot
communicate with
each other.
● OptiX RTN 900
supports only the
division of the split
horizon group
members according
to the Ethernet
physical port.
● If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
member, the
mounted with the
logical port is
automatically
added to the split
horizon group
member.

Parameters for Unknown Frame Processing

Frame Type Unicast - This parameter

Multicast indicates 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


E-LAN service.

the E-LAN service.


LAN service, this
parameter supports
only Not
Transparently
Transmitted and
cannot be set
manually.
Protocol (STP) is
configured, Not
Transparently
Transmitted
indicates that
BPDU packets are
considered as
protocol packets
the STP topology.
● If no STP is
configured, Not
Transparently
Transmitted
indicates that no
special channel is
established for
transparently
transmitting
IEEE 802.1d-bridge
services (that is,
transparent bridge-
based 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.


are learnt
(the VLAN tag on
create the 802.1q
bridge, set this
parameter to C-
Aware.
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.
● Tag-Transparent
indicates that the
packets are
transparently
transmitted. To
create the 802.1d
bridge, set this
parameter to Tag-
Transparent.


Address indicates whether
to enable the MAC
address self-
learning function.
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.
learning function
of an Ethernet LAN
MAC address
forwarding table is
recommended to
be configured.

Learning Mode indicates the mode
used to learn an
MAC address.
● When the bridge
uses the SVL mode,
all the VLANs share
one MAC address
uses the IVL mode,
each VLAN has an
MAC address table.
Port Parameters

indicates the port
name.


displays the port type.
● 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.
● If the parameter
value is NNI, the
port connected to
the bridge is an
NNI port. That is,
this port functions
as the NNI port
connected to the
IEEE 802.1ad
bridge.
value is UNI (PORT
+S-VLAN), a
specified S-VLAN
ID is added to all
the traffic flows
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 - - 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.
can be received,
processed, and
forwarded normally
only if Enable Port
is set to Enabled.
● Enable Port is
already set in
Ethernet Interface.


support different
in auto-negotiation
mode, set the
working mode of
the equipment on
the local side to
Auto-Negotiation.
● 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.
● When the
equipment on the
opposite side works
in half-duplex
mode, set the
working mode of
the equipment on
the local side to
10M Half-Duplex,
100M Half-
Duplex, or Auto-
Negotiation
depending on the
port rate of the
equipment on the
opposite side.
● The GE optical
interface supports
the 1000M full-
duplex mode only.


method of the port
QinQ to process the
received packets.
● If you set this
parameter to Null,
the port
transparently
transmits the
received packets.
● If you set this
parameter to
802.1Q, the port
identifies the
packets that
comply with the
IEEE 802.1q
standard.
● If you set this
parameter to
QinQ, the port
identifies the
packets that
comply with the
IEEE 802.1ad QinQ
standard.

with the VLAN tag
set this parameter
to "Tag Aware".
services are frames
without the VLAN
tag (untagged
frames), set this
parameter to
"Access".
● If the accessed
services contain
tagged frames and
untagged frames,
set this parameter
to "Hybrid".

Default VLAN ID 1 to 4094 1 ● Default VLAN ID is

valid only when
Tag is set to Access
or Hybrid.
● Default VLAN ID is
set according to
the actual
situations.
Parameters for Static MAC Addresses


invalid if MAC
Address Learning
Mode is SVL. That
is, the preset static
MAC address
all VLANs.
● 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.
set according to
the planning
information.


indicates or
specifies the static
MAC address.
● A static MAC
address is an
address that is set
manually. It is not
aged automatically
and needs to be
deleted manually.
● 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.

specifies the
Ethernet port that
corresponds to the
MAC address.
set according to
the planning
information.

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.
● If MAC Address
Learning Mode is
set to IVL, the
preset self-learning
MAC address
only the VLANs
whose VLAN ID is
equal to the preset
VLAN ID.
set according to
the planning
information.

indicates or
specifies the self-
learning MAC
address. A self-
learning MAC
address is also
called a dynamic
MAC address.
● 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.


specifies the
Ethernet port that
corresponds to the
MAC address.
set according to
the planning
information.
Parameters Associated with MAC Address Learning

Aging Ability Enabled Enabled OptiX RTN 900

Disabled supports enabling/
disabling of the aging
Aging Time(min) 1 to 640 5 function and aging
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 0 to 65534 512 ● This parameter is

Table Capacity supported only by
the OptiX RTN
950A/905/
RTN910A and the
OptiX RTN 950 that
houses CSHU/
CSHUA boards.
● This parameter
specifies the MAC
address forwarding
table capacity for
E-LAN services.
Address Detection 80 to 100 95 ● This parameter is

Upper Threshold (%) supported only by
the OptiX RTN
Address Detection 60 to 100 90 950A and the
Lower Threshold (%) OptiX RTN 950 that
houses CSHU/
CSHUA boards.
● When the MAC
address forwarding
table capacity for
E-LAN services is
greater than
Address Detection
Upper Threshold
(%), an
FDBSIZEALM_ELAN
alarm is reported.
When the MAC
address forwarding
table capacity for
E-LAN services is
less than Address
Detection Lower
Threshold (%), the
FDBSIZEALM_ELAN
alarm
automatically
clears.

Parameters for Disabled MAC Addresses


the VLAN ID of the
service. A disabled
MAC address is valid
for the VLAN whose
VLAN ID is equal to
the preset VLAN ID.

specifies or
indicates the
disabled MAC
address. A disabled
MAC address is
also called a
blacklisted MAC
address.
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.


the split horizon
group.
horizon group ID is
1 and cannot be
set manually.


Member group member
indicates the
logical port
member in the split
horizon group.
that are added to
different split
horizon groups
cannot
communicate with
each other.
● The supports only
the division of the
split horizon group
members according
to the Ethernet
physical port.
● If a UNI or NNI
logical port of the
802.1ad bridge is
added to a split
horizon group
member, the
mounted with the
logical port is
automatically
added to the split
horizon group
member.
Parameters for Unknown Frame Processing

Frame Type Unicast - This parameter

Multicast indicates 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

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.

specifies the port
where the QinQ link is
located.

S-Vlan ID 1 to 4094 - ● This parameter

specifies the VLAN
ID (at the network
operator side) for
the QinQ link.
set according to
the planning
information.
B.6.1.10 Parameter Description: E-AGGR Services_Creation

This topic describes the parameters for creating E-AGGR services.
Navigation Path
Function Tree.
2. Click New.


specifies the ID of an
E-AGGR service.

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

Source specifies 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.

displays UNI ports.
VLANs 1 to 4094 - ● This parameter

specifies the VLAN
ID for a UNI port.
to a numeral or
several numerals.
When you set this
parameter to
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.
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

Source specifies whether a
port functions as a
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 ● This parameter

Ethernet Tagged Mode specifies whether
P-TAGs will be
added to Ethernet
frames when the
Ethernet frames
are encapsulated
on a PW.
● 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.

of a PW.
PW Encapsulation MPLS MPLS This parameter

Type 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 - - This parameter

Mode displays whether an
existing MPLS tunnel
or a new MPLS tunnel
is used.
Tunnel Type - - This parameter

displays the type of a
tunnel.

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

Egress Tunnel - - This parameter

displays the egress
tunnel.

the local end.

status of the PW at
the remote end.

Status displays the
comprehensive
PW.


Table B-12 Advanced attributes


words when
encapsulating ETH
PWE3 packets (PWE3
stands for pseudo wire
emulation edge-to-
edge).
NOTE
control words when
encapsulating ETH
Control Channel Type Alert Label Alert Label This parameter

None specifies the control
channel type, which
CW determines the PW
continuity check (CC)
mode.
● None: indicates
that virtual circuit
connectivity
verification (VCCV)
packets are not
used.
● Alert Label:
indicates that VCCV
packets in Alert
Label
encapsulation
mode are used.
VCCV packets
encapsulated based
on the control
word are used.

VCCV Verification Ping Ping ● This parameter

Mode None specifies the VCCV
verification mode,
which is used for a
PW CC test.
● 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


attribute for a source
port.

specifies a source port.

VLAN ID.

attribute for the sink
port.

specifies the sink port.

specifies the sink
VLAN ID.

NOTE
● 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.
● 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.
● 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.
● 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.
● 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)
displays the ID of a
PW.

displays the
direction of a PW.
of a PW.
the ingress
direction of a PW.

PW.


whether the
bandwidth limit
a PW to prevent
network congestion.
● For transmission
channels, the
bandwidth limit
function controls
the bandwidth of
one or more PWs
as required.
● For services, the
bandwidth limit
function controls
the 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.

the committed
for a PW.
The CIR is
recommended to be
the same as the PIR.
CBS (Kbit/s) - - This parameter

the committed burst
PIR (Kbit/s) - - This parameter

The PIR is
recommended to be
the same as the CIR.

PBS (Kbit/s) - - This parameter

the peak burst size
(PBS) for a 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
Function Tree.


specifies the ID of an
E-AGGR service.

an E-AGGR service.
MTU(byte) - - Setting this parameter

is not available.
Service Tag Role - - Setting this parameter

is not available.

displays whether an E-
AGGR service has been
deployed.

UNI Parameters
ID - - This parameter
UNI port.
Location - - This parameter

displays whether a
port functions as a

displays 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 as a
PW.

is enabled.

displays the signaling
type of a PW.

PW.


of a PW.

Type displays the
encapsulation type of
a PW.

displays the ingress
label of a PW.

displays the egress
label of a PW.

displays the LSR ID for
the NE at the opposite
end of a PW.
Tunnel Type - - This parameter

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.

channel type.

verification mode.
Local Operation - - This parameter

Status displays the PW
running status at the
local end.

Local Operation - - This parameter

Status displays the PW
running status at the
opposite end.
Overall Operation - - This parameter

Status displays the overall
PW running status.

VLAN ID.


does not allow TPIDs
in request VLANs to
be specified for a PW.
Parameters for a VLAN Forwarding Table


attribute for a source
port.

specifies a source port.

VLAN ID.

attribute for the sink
port.

specifies the sink port.

specifies the sink
VLAN ID.

NOTE
● 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.
● 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.
● 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.
● 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.
● 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)
PW.

displays the
direction of a PW.
of a PW.
the ingress
direction of a PW.

PW.


whether the
bandwidth limit
a PW to prevent
network congestion.
● For transmission
channels, the
bandwidth limit
function controls
the bandwidth of
one or more PWs
as required.
● For services, the
bandwidth limit
function controls
the 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.

the committed
for a PW.
The CIR is
recommended to be
the same as the PIR.
CBS (Kbit/s) - - This parameter

the committed burst
PIR (Kbit/s) - - This parameter

The PIR is
recommended to be
the same as the CIR.

PBS (Kbit/s) - - This parameter

the peak burst size
(PBS) for a 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
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 - ● This parameter specifies

the ID of the Ethernet
ring protection switching
(ERPS) instance.
● 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.
● Set East Port or West Port
to - for the sub-ring ERPS
instance on an
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.
● Set East Port or West Port
to - for the sub-ring ERPS
instance on an

ERP Ring Node Flag None None ● If the node is the RPL
RPL Port owner, set this parameter
to RPL Port.
Neighbor Port
● If the node is an RPL
Next Neighbor Port 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.
● Only one node on the
ring can be set as the
RPL owner or RPL
neighbor node for each
Ethernet ring.
● If the node on the ring is
not any of the preceding
nodes, set this parameter
to None.
Flag Port - - ● Set ERP Ring Node Flag

and Flag Port to
matching values
according to the network
plan.
● One ERPS ring has only
one RPL Port and one
Neighbor Port.
you set the east port of
the RPL owner to RPL
Port and the west port of
the RPL neighbor node to
Neighbor Port.
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.

Revertive Mode Revertive Revertive This parameter generally

Non-Revertive takes the default value
Revertive. You can set this
parameter to Non-
Revertive according to the
network plan.
Control VLAN 1 to 4094 - ● This parameter specifies

the VLAN ID of Control
VLAN.
● 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.
● 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 - - ● 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 - ● This parameter

indicates or
specifies the
VLAN ID of
Control VLAN.
● 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.
● The Control
VLAN must be
set to the same
value for all the
NEs on an ERPS
ring.

Destination Node 01-19- - This parameter

A7-00-00-01 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 ● This parameter

ver1 indicates the
configured
compatible
ERPS protocol
version and can
be reset.
● For multi-ring
networks,
Compatible_Ve
rsion for all
ring nodes
must be ver2.
● For single ring
networks,
Compatible_Ve
rsion for ring
nodes except
the RPL owner
can be either
ver1 or ver2.
Compatible_Ve
rsion for the
RPL owner
must be ver2.
Virtual Channel Status Enable Enable ● This parameter

Disable indicates the
configured
status and

Virtual Channel VLANs 1 to 4094 - VLAN ID of an

R-APS virtual
channel, and
can be reset.
● For details
about the value
of this
parameter, refer
to Planning
Guidelines for
R-APS Virtual
Channels in the
Feature
Description.
Major ERPS Ring ID - - Set this parameter
only for the sub-
ring ERPS instance
on an
interconnection
node to associate
the sub-ring ERPS
instance with the
major ring ERPS
instance.

ETH Type Domain Transfer mode Transfer mode ● 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.
● In other cases,
retain the
default value
Transfer mode
(Ox8809) for
this parameter.

Hold-Off Time(ms) - 0 ● This parameter

indicates or
specifies the
hold-off time of
the ERPS hold-
off timer.
● 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 ● This parameter

indicates or
specifies the
guard time of
the ERPS guard
timer.
● 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 5 ● This parameter

1 indicates or
specifies the
WTR time of
the WRT timer
in the case of
ERPS
protection.
● 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.

● 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

indicates or
specifies the level
of the
maintenance
entity.
Last Switching Request - - This parameter

indicates the last
switching request.
RB Status - - This parameter

indicates the RB
(RPL Blocked)
status of the
packets received
by the working
node.
● noRB: The RPL
is not blocked.
● RB: The RPL is
blocked.

DNF Status - - This parameter

indicates the DNF
status of the
packets received
by the working
node.
● 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.
● 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.
● 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.
● 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 - - This parameter

Packet 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 ● This parameter

Primary specifies the
interconnection
Secondary node attribute.
Multi-point Failure Disable Disable It applies to
only an ERPS
Primary sub-ring.
Secondary
● After multiple
failures occur,
an
interconnection
node triggers
manual ERPS
switching when
the following
conditions are
met: An MEP is
properly bound;
a loss of
connectivity
between the
interconnection
nodes is
detected; the
values of
Interconnected
Node and
Multi-point
Failure are
identical.
B.6.2.3 Parameter Description: SEP Management_Creation

This topic describes the parameters that are used for creating Smart Ethernet
Protection (SEP) management tasks.

Navigation Path
> Ethernet Protection > SEP Management.
2. Click New.
Parameters
Instance ID 1 to 8 - This parameter

specifies the ID of
the Smart
Ethernet
Protection (SEP)
instance.
NOTE
The IDs of SEP
instances on an NE
must be different
from each other.

specifies the
Name of the SEP
instance.

specifies the East
Port of the SEP
instance.
East Port Common Port Common Port This parameter

Configuration Primary Edge Port specifies the East
Role Port
Secondary Edge Configuration
Port Role of the SEP
No-neighbor instance.
Primary Edge Port NOTE
No-neighbor Normally, edge
Secondary Edge interfaces and no-
neighbor edge
Port interfaces belong
to different SEP
segments.

specifies the West
Port of the SEP
instance.

West Port Common Port Common Port This parameter

Configuration Primary Edge Port specifies the West
Role Port
Primary Edge Port
No-neighbor
Secondary Edge
Port
Control VLAN 1 to 4094 - This parameter

specifies the
Control VLAN of
the SEP instance.
VLAN Mapping 1 to 4094 - This parameter

Table specifies the
VLAN Mapping
Table of the SEP
instance.
Preemption - - This parameter

Delay(s) 15 to 600 specifies the
Preemption
Delay(s) of the
SEP instance.
TC Suppression 1 to 10 2 This parameter

Time Interval(s) specifies the TC
Suppression
Time Interval(s)
of the SEP
instance.
Notified SEP TC 1 to 8 - This parameter

List specifies the
Notified SEP TC
List of the SEP
instance.
Authentication HMAC-256 HMAC-256 This parameter

Type Authentication Authentication specifies the
No Authentication Authentication
Type of the SEP
instance.
Authentication - - This parameter

Password specifies the
Authentication
Password of the
SEP instance.

B.6.2.4 Parameter Description: SEP Management

This topic describes the parameters that are used for Smart Ethernet Protection
(SEP) management.
Navigation Path

Instance ID 1 to 8 - This parameter

specifies the ID of
the Smart
Ethernet
Protection (SEP)
instance.
NOTE
The IDs of SEP
instances on an NE
must be different
from each other.

specifies the
Name of the SEP
instance.

specifies the East
Port of the SEP
instance.
East Port Common Port Common Port This parameter

Configuration Primary Edge Port specifies the East
Role Port
Primary Edge Port NOTE
No-neighbor Normally, edge
Secondary Edge interfaces and no-
neighbor edge
Port interfaces belong
to different SEP
segments.


specifies the West
Port of the SEP
instance.
West Port Common Port Common Port This parameter

Configuration Primary Edge Port specifies the West
Role Port
Primary Edge Port
No-neighbor
Secondary Edge
Port
Control VLAN 1 to 4094 - This parameter

specifies the
Control VLAN of
the SEP instance.
VLAN Mapping 1 to 4094 - This parameter

Table specifies the
VLAN Mapping
Table of the SEP
instance.
Preemption Non-preemption Non-preemption This parameter

Mode Manual displays the
Preemption Preemption
Mode.
Delay Preemption
Preemption - - This parameter

Delay(s) 15 to 600 specifies the
Preemption
Delay(s) of the
SEP instance.
TC Suppression 1 to 10 2 This parameter

Time Interval(s) specifies the TC
Suppression
Time Interval(s)
of the SEP
instance.
Notified SEP TC 1 to 8 - This parameter

List specifies the
Notified SEP TC
List of the SEP
instance.

Authentication HMAC-256 HMAC-256 This parameter

Type Authentication Authentication specifies the
No Authentication Authentication
Type of the SEP
instance.
Authentication - - This parameter

Password specifies the
Authentication
Password of the
SEP instance.
Parameters for Topology

System Name - - This parameter

displays the
System Name.
Port Name - - This parameter

displays the Port
Name.

Configuration displays the Port
Role Configuration
Role.
Port Working - - This parameter

Role displays the Port
Working Role.
System MAC 2C-55-D3-89-7C- 2C-55-D3-89-7C- This parameter

EB EB displays the
System MAC.
Port ID - - This parameter

displays the Port
ID.
Port Priority - - This parameter

displays the Port
Priority.
Port Forwarding - - This parameter

Status displays the Port
Forwarding
Status.

Link Status - - This parameter

displays the Link
Status.
Brother Port - - This parameter

Name displays the
Brother Port
Name.
Neighbor Port ID - - This parameter

displays the
Neighbor Port ID.
Neighbor System - - This parameter

Name displays the
Neighbor System
Name.
Neighbor Port - - This parameter

Name displays the
Neighbor Port
Name.
Neighbor System 00-00-00-00-00-0 00-00-00-00-00-0 This parameter

MAC 0 0 displays the
Neighbor System
MAC.

displays the
Neighbor Port ID.
Neighbor Status - - This parameter

displays the
Neighbor Status.
Aging Time - - This parameter

displays the
Aging Time.
Sequence - - This parameter

Number displays the
Sequence
Number.
Hop Count - - This parameter

displays the Hop
Count.

Parameters for Blocking Mode

Port Blocking Optimal Optimal This parameter

Mode Middle specifies the Port
Blocking Mode of
Hop the SEP instance.
Name
Hop Count of a - - This parameter

Specified Blocked displays the Hop
Port Count of a
Specified Blocked
Port of the SEP
instance.
System Name of - - This parameter

a Specified displays the
Blocked Port System Name of
a Specified
Blocked Port of
the SEP instance.
Name of a - - This parameter

Specified Blocked displays the
Port Name of a
Specified Blocked
Port of the SEP
instance.
Parameters for Port


displays the Port
of the SEP
instance.

Configuration displays the Port
Role Configuration
Role of the SEP
instance.
Port Working - - This parameter

Role displays the Port
Working Role of
the SEP instance.

User-defined 1 to 128 64 This parameter

Priority displays the User-
defined Priority
of the SEP
instance.
Port Priority - - This parameter

displays the Port
Priority of the
SEP instance.
Port Status - - This parameter

displays the Port
Status of the SEP
instance.

System Name displays the
Neighbor Port
System Name of
the SEP instance.

Name displays the
Neighbor Port
Name of the SEP
instance.
Neighbor Port 00-00-00-00-00-0 00-00-00-00-00-0 This parameter

System MAC 0 0 displays the
Neighbor Port
System MAC of
the SEP instance.

displays the
Neighbor Port ID
of the SEP
instance.
Neighbor Status - - This parameter

displays the
Neighbor Status
of the SEP
instance.
B.6.2.5 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

STP specifies the protocol
type.
● MSTP: stands for
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports the CIST
MSTP only.
● STP: stands for
Spanning Tree
Protocol.
Enable Protocol Enabled Disabled This parameter

Disabled specifies whether to
enable the protocol of
the port group or a
member port in the
port group.
Parameters for Application Ports


specifies 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.6 Parameter Description: MSTP Configuration_Port Group

Configuration
This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
Tree.
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


specifies the board
where the member of
port group is located.
Available Port List - - This parameter

port list in which a
port needs to be
added to the port
group.
Selected Port List - - This parameter

ports that need to be
added to the port
group.
B.6.2.7 Parameter Description: MSTP Configuration_ Bridge Parameters

This topic describes the parameters that are related to MSTP bridges.

Navigation Path
Tree.

Port Group ID - - ● This parameter

indicates the ID of
the port group.
be set to only the
port group ID that
is automatically
allocated.
MST Domain Name - - The OptiX RTN 900

parameter.
Redaction Level - - The OptiX RTN 900

parameter.
Mapping List - - The OptiX RTN 900

parameter.
Bridge Parameters
Port Group ID - - ● This parameter

indicates the ID of
the port group.
be set to only the
port Group ID that
is automatically
allocated.
MST Domain Max - 20 Specifies the

Hop Count maximum hop count
of the MSTP.

Network Diameter 2 to 7 7 ● This parameter

specifies the MSTP
network diameter.
● If the value of
Network
Diameter is
greater, the
network is in a
larger scale.
Hello Time(s) 1 to 10 2 ● This parameter

specifies the
interval for
transmitting the
CBPDU packets
through the bridge.
● 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 ● This parameter

specifies the
maximum age of
the CBPDU packet
that is recorded by
the port.
● 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 ● This parameter

specifies the
holdoff time of a
port in the listening
state and in the
learning state.
● The greater the
value, 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

indicates the port in
the port group.
Enable Edge Disabled Disabled ● This parameter

Attribute Enabled specifies the
management edge
attributes of the
port.
be 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 false auto ● This parameter

Attribute true specifies the point-
to-point attribute
auto of the port.
● false: forced non-
point-to-point link
attribute
● true: forced point-
to-point link
attribute
● auto: automatically
detected point-to-
point link attribute
set 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. If
the actual working
mode is half-
duplex, Actual
Point-to-Point
Attribute is false.
● Only the
designated port
whose Actual
Point-to-Point
Attribute is "True"
can transmit the
rapid state
migration request
and response.
that you use the
default value.
Actual Point-to-Point - - This parameter

Attribute indicates the actual
point-to-point
attribute of the port.

Max Transmit Packet 1 to 255 3 ● This parameter

Count specifies the
maximum number
of packets to be
transmitted.
● 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.
● This parameter
needs to be set
according to the
planning
information.
B.6.2.8 Parameter Description: MSTP Configuration_CIST Parameters

This topic describes the parameters that are related to the MSTP CIST.
Navigation Path
Tree.
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 ● The most

4096 significant 16 bits
of the bridge ID
indicate the priority
of the bridge.
● When the value is
smaller, the priority
is higher. As a
result, the bridge is
more possible to be
selected as the root
bridge.
● 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

the port group.
Priority 0 to 240, in step of 16 128 ● The most

significant eight
bits of the port ID
indicate the port
priority.
is higher.

Path Cost 1 to 200000000 FE Port: 200000 ● This parameter

GE Port: 20000 indicates the status
of the network that
the port is
connected to.
● In the case of the
bridges on both
ends of the path,
set this parameter
to the same value.
B.6.2.9 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
Tree.
2. Click the CIST Running Information tab.

Port Group ID - - This parameter

port group.
Protocol Running MSTP - ● This parameter

Mode STP indicates the
running mode of
the protocol.
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
● STP: stands for
Spanning Tree
Protocol.

Bridge Priority 0 to 61440, in step of 32768 ● This parameter

4096 indicates the
priority of the
bridge.
● The most
significant 16 bits
of the bridge ID
of the bridge.
is higher. As a
more possible to be
bridge.
all the bridges in
the STP network
use the same
value, the bridge
whose MAC
address is the
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

4096 indicates the priority
of the root bridge.
Root Bridge MAC - - This parameter

Address indicates the MAC
address of the root
bridge.
External Path Cost - - The OptiX RTN 900

ERPC does not support this
parameter.
Domain Root Bridge - - The OptiX RTN 900

Priority does not support this
parameter.
Domain Root Bridge - - The OptiX RTN 900

MAC Address does not support this
parameter.

Internal Path Cost - - The OptiX RTN 900

IRPC does not support this
parameter.
Root Port Priority 0 to 240, in step of 16 128 ● This parameter

indicates the
priority of the root
port.
● The most
significant eight
bits of the ID of the
root port indicate
the priority of the
root port.
is higher.
Root Port - - This parameter

indicates the root
port.
Hello Time(s) - 2 ● This parameter

indicates the
interval for
transmitting
CBPDU packets
through the bridge.
● The greater the
value of this
parameter, the less
the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.


specifies the
maximum age of
the CBPDU packet
that is recorded by
the port.
● 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.

specifies the
holdoff time of a
state and in the
learning state.
● The greater the
value, 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.
MST Domain Max - - This parameter

Hop Count indicates the
maximum hop count
of the MSTP.
Topology Change - - This parameter

Identifier indicates the identifier
of the topology
change.

Last Topology - - This parameter

Change Time(s) indicates the duration
of the last topology
change.
Topology Change - - This parameter

Count indicates the count of
the topology changes.
Port Parameters

the port group.
Enable Protocol Enabled Disabled This parameter

Disabled indicates 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

Learning indicates the state of
a port.
Forwarding
● Discarding: receives
only BPDU packets
● Learning: only
receives or
transmits BPDU
packets
● Forwarding:
forwards user
traffic, and
transmits/receives
BPDU packets

Priority 0 to 240, in step of 16 128 ● The most

significant eight
bits of the port ID
indicate the port
priority.
is higher.
Path Cost 1 to 200000000 200000 ● This parameter

indicates the status
of the network that
the port is
connected to.
● 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 ● The most

4096 significant 16 bits
of the bridge ID
of the bridge.
is higher. As a
more possible to be
bridge.
all the bridges in
the STP network
use the same
value, the bridge
whose MAC
address is the
as the root bridge.
Bridge MAC Address - - This parameter

indicates the MAC
address of the bridge.

Designated Port 0 to 240, in step of 16 0 ● The most

Priority significant eight
bits of the port ID
indicate the port
priority.
is higher.
Design Port - 0 This parameter

indicates the
designated port.
Edge Port Attribute Disabled Disabled ● This parameter

Enabled specifies the
management edge
attributes of the
port.
● 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.
be 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

Attribute indicates the actual
management edge
attributes of the port.

Point to Point false auto ● This parameter

true specifies the point-
to-point attribute
auto of the port.
● false: forced non-
point-to-point link
attribute
● true: forced point-
to-point link
attribute
● auto: automatically
detected point-to-
point link attribute
set 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. If
the actual working
mode is half-
duplex, Actual
Point to Point
Attribute is false.
● Only the
designated port
whose Actual
Point-to-Point
Attribute is "True"
can transmit the
rapid state
migration request
and response.
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 ● This parameter

Transmitting indicates the
Message maximum number
of packets to be
transmitted.
● 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 STP - ● This parameter

Mode MSTP indicates the
running mode of
the protocol.
Multiple Spanning
Tree Protocol. The
OptiX RTN 900
supports only the
CIST-based MSTP.
● STP: stands for
Spanning Tree
Protocol.
Hello Time(s) 1 to 10 2 ● This parameter

indicates the
interval for
transmitting the
CBPDU packets
through the bridge.
● The greater the
value of this
parameter, the less
the network
resources that are
occupied by the
spanning tree. The
topology stability,
however, decreases.


specifies the
maximum age of
the CBPDU packet
that is recorded by
the port.
● 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.

specifies the
holding time of a
state and in the
learning state.
● The greater the
value, 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.
Remain Hop - - The OptiX RTN 900

parameter.

B.6.2.10 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).
operation.
Navigation Path
> Ethernet Protocol Configuration > IGMP Snooping Configuration from
the Function Tree.
2. Click the Protocol Configuration tab.

Service ID - - This parameter

ID.
Enabled Protocol Enabled Disabled ● This parameter

Disabled specifies whether
to enable the IGMP
Snooping protocol.
● 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 ● If an entry is not

Time(min) updated in a
certain period (that
is, no IGMP query
packet is received),
this entry is
automatically
deleted. This
mechanism is
called aging, and
this period is called
aging time.
set to a very large
value, the bridge
stores excessive
multicast entries
that are outdated.
Consequently, the
resources of the
multicast table are
exhausted.
set 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 ● This parameter

Times from Multicast specifies the
Members maximum number
of multicast group
members who do
not respond.
● 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 ● This parameter

Groups 128 specifies the
maximum number
256 of allowable
512 multicast groups.
Unlimited ● 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 ● This parameter

Multicast Group 128 specifies the
Members maximum number
256 of allowable
512 multicast group
1024 members.
Unlimited ● A multicast group
member refers to
the host that is
added to a
multicast group.
Actual Multicast - - This parameter

Count indicates the number
of actually used
multicast groups.
Actual Multicast - - This parameter

Members Count indicates the number
of actually used
multicast group
members.
B.6.2.11 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.
operation.

Navigation Path
the Function Tree.
2. Click the Protocol Config tab.
3. Click Add.
Parameters for Fast Leave Ports


ID.
VLAN ID 1 to 4094 1 ● This parameter

specifies the VLAN
where the port to
be quickly deleted
is located.
● This parameter
needs to be set
according to the
planning
information.
Port Type V-UNI V-UNI ● This parameter

V-NNI specifies the type
of the port to be
quickly deleted.
● This parameter
needs to be set
according to the
planning
information.

specifies the port to
be quickly deleted.
B.6.2.12 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).
operation.

Navigation Path
the Function Tree.
2. Click the Router Port Management tab.
Parameters for Router Port Management


created E-LAN service.

indicates the VLAN ID
of the router port.

indicates the type of
the router port.

indicates 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 - - This parameter

Aging Time(min) indicates the
remaining aging time
of the router port.
B.6.2.13 Parameter Description: IGMP Snooping Configuration_Static Router

Port Creation
This topic describes the parameters that are used for adding static router ports.
operation.

Navigation Path
the Function Tree.
2. Click the Route Management tab.
3. Click New.
Parameters for Router Port Creation


VLAN ID 1 to 4094 1 This parameter

of the router port.

ports.

indicates the specified
router port.
B.6.2.14 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).
operation.
Navigation Path
the Function Tree.
2. Click the Route Member Port Management tab.

Parameters for Multicast Groups Information



of the multicast
group.
Multicast MAC - - This parameter

Address indicates the multicast
MAC address.
Multicast Groups - - This parameter

Type indicates the type of
Multicast Group - - This parameter

Creating Time indicates the time
when the multicast
group is set up.
Parameters for Multicast Group Members Information



of the multicast group
member.

indicates the type of
the multicast group
member.

indicates the multicast
group member port.

Port Remainder - - This parameter

Aging Times indicates the
remaining non-
response times of the
multicast group
member port.
B.6.2.15 Parameter Description: IGMP Snooping Configuration_Static

Multicast Group Member Creation
This topic describes the parameters that are used for adding static multicast
groups.
operation.
Navigation Path
the Function Tree.
2. Click the Route Member Port Management or Route Member Port
3. Click New.
Parameters for Router Port Creation
Table B-14 Parameters for V2



of the multicast
group.
Multicast MAC - - This parameter

Address specifies the multicast
MAC address.


interfaces.

indicates the preset
port of the multicast
group members.
Table B-15 Parameters for V3


of the multicast
group.
Multicast IP Address - - This parameter

specifies the multicast
IP address.
Source IP Address - - This parameter

specifies the source IP
address.

interfaces.

indicates the preset
port of the multicast
group members.
B.6.2.16 Parameter Description: IGMP Snooping Configuration_Data Count

This topic describes the parameters that are used for collecting statistics for IGMP
operation.

Navigation Path
the Function Tree.
2. Click the Data Count tab.
Parameters for Routing Member Interface Management


ID.

of the service.

indicates the port
type.

indicates the port.
Packet Statistic Clear Clear This parameter

Status Start indicates or specifies
the status of
Stop collecting the packet
statistics.
IGMPv1 Query Packet - - This parameter

of received IGMPv1
query packets.

of received IGMPv2
query packets.

of received IGMPv3
query packets.
IGMP Leaving Packet - - This parameter

Count displays the number
of leaving packets
that are received.

IGMPv1 Member - - This parameter

Report Packet Count indicates the number
of received packets
that are reported by
the IGMPv1 members.

of received packets
the IGMPv2 members.

of received packets
the IGMPv3 members.
Unrecognized or - - This parameter

Unprocessed Packet indicates the number
Count of packets that cannot
be recognized or
processed.
Discarded Incorrect - - This parameter

Packet Count indicates the number
of discarded error
packets.
B.6.2.17 Parameter Description: IGMP Snooping Configuration_SSM Mapping

This topic describes the parameters that are used for SSM mapping for IGMP
operation.
Navigation Path
the Function Tree.
2. Click the SSM Mapping tab.

Parameters for Routing Member Interface Management


ID.
Multicast IP Address - - This parameter

specifies the multicast
IP address.
Multicast Address - - This parameter

Mask specifies the multicast
address mask.
Multicast Source - - This parameter

indicates the present
multicast source IP
address.
B.6.2.18 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 ● This parameter

specifies the LAG
number to be set
manually.
valid only when
Automatically
Assign is not
selected.

Automatically Assign Selected Selected ● This parameter

LAG No. is
allocated
automatically.
● When
Automatically
Assign is selected,
LAG No. cannot be
set.
LAG Name - - This parameter

specifies the LAG
name.

LAG Type Static Static ● Static: You can

Manual create a LAG.
When you add or
delete a member
port to or from the
LAG, the Link
Aggregation
Control Protocol
(LACP) protocol is
required. In a LAG,
a port can be in
selected, standby,
or unselected state.
The aggregation
information is
exchanged among
different
equipment through
the LACP protocol
to ensure that the
aggregation
information is the
same among all
the nodes.
● Manual: 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 support this
parameter.
Switch Mode - - OptiX RTN 900 does

not support this
parameter.

Link Detection Null Null This parameter is set

Protocol 802.3ah according to the
Revertive Mode Revertive Mode Non-Revertive Mode ● Revertive Mode

Non-Revertive Mode can be set only
when Load
Sharing is set to
Non-Sharing.
● 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.
● 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 ● Set Load Sharing

Non-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.
● 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.
● 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

Algorithm the Link Aggregation
Parameters tab page.
System Priority 0 to 65535 32768 ● System Priority

indicates the
priority of a LAG.
The smaller the
value of System
Priority, the higher
the priority.
● 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 ● Specifies the WTR

time for the LAG.
● WTR Time(min)
takes effect only
when Revertive
Mode is Revertive
Mode.
Switch LAG upon Air Disabled Disabled ● This parameter

Interface SD Enabled specifies whether
to enable the
switching triggered
by bit errors.
● 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.
● It is advisable to
set Switch LAG
upon Air Interface
SD to Enabled
when configuring
an air-interface
LAG.

Packet Receive Short period Short period ● A LAG switching is

Timeout Period Long period triggered if no
LACP packet is
received after
Packet Receive
Timeout Period
times out.
● 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.
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 - - ● This parameter

specifies the main
board in a LAG.
set according to
the planning
information.

Main Port - - ● This parameter

specifies the main
port in a LAG.
● 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 - - ● This parameter

Ports) specifies the slave
board in a LAG.
set according to
the planning
information.
Port (Available Slave - - ● This parameter

Ports) specifies the slave
port in a LAG.
● 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 - - This parameter

Ports indicates the selected
slave ports.
B.6.2.19 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.


indicates the port
whose priority can be
set.
Port Priority 0 to 65535 32768 ● 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.
● When ports are
added into a LAG,
the port of the
highest priority is
preferred for
service
transmission.

Load Sharing Hash Automatic Automatic ● System Load

Algorithm Source MAC Sharing Hash
Algorithm is valid
Destination MAC only when Load
Source and Sharing of a LAG is
Destination MACs set to Sharing.
Source IP Address ● The load sharing
Destination IP Address computation
methods include
Source and algorithm auto-
Destination IP Address sensing,
MPLS Label computation based
on MAC addresses
(based on the
source MAC
address, based on
the destination
MAC address, and
based on the
source MAC
address + sink MAC
address),
computation based
on IP addresses
(based on the
source IP address,
based on the
destination IP
address, and based
on the source IP
address and sink IP
address), and
computation based
on MPLS labels.
● After the
configuration data
is deployed,
System Load
Sharing Hash
Algorithm takes
effect for the entire
NE.
● For PW-carried
UNI-NNI E-Line
services, System
Load Sharing
Hash Algorithm
cannot be set to
MPLS Label.

B.6.2.20 Parameter Description: LPT Management_Creating Simple LPT

This parameter describes the parameters that are used for creating LPT
management.
Navigation Path
> 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.21 Parameter Description: LPT Management_Point-to-Point LPT

This topic describes the parameters that are related to point-to-point LPT.
Navigation Path
> LPT Management > LPT from the Function Tree.
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 - - This parameter

Point displays the port
where the primary
point of point-to-point
LPT resides.
Secondary Function - - This parameter

Point Type displays the type of
secondary point for
point-to-point LPT.

where the secondary
LPT resides.
LPT Instance Status - - This parameter

displays the status of
point-to-point LPT.
LPT Enabled Enabled Disabled This parameter

Disabled displays 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

the recovery time of
point-to-point LPT.
Hold-Off Times(ms) 0-10000 1000 This parameter

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 PW OAM LPT OAM This parameter

Mode LPT OAM displays the fault
detection mode of
point-to-multipoint
LPT.
● 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 switching is
triggered.
● 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

Period(100ms) displays or specifies
the fault detection
period of point-to-
point LPT.
User-Side Port Status - - This parameter

a user-side port.

L2 net ID-L2 Peer net - - This parameter

ID displays the NET IDs
of LPT packet out
ports at both ends.
B.6.2.22 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

LPT packet out port at
the opposite end.

Point specifies the port
where the primary
LPT resides.
VLAN ID 1-4094 - This parameter

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.23 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


primary point for
point-to-multipoint
LPT.

where the primary
point of point-to-
multipoint LPT resides.
LPT Instance Status - - This parameter

point-to-multipoint
LPT.
LPT Enabled Enabled Disabled This parameter

Disabled displays the enabling
status of point-to-
multipoint LPT.
Recovery Times(s) 1-600 1 This parameter

the recovery time of
point-to-multipoint
LPT.

Hold-Off Times(ms) 0-10000 1000 This parameter

the hold-off time of
point-to-multipoint
LPT.
Switching Mode Strict mode Strict mode This parameter

Non-strict mode displays the switching
mode of point-to-
multipoint LPT. Point-
to-point LPT is
available only in strict
mode.
● Strict mode
A primary point
triggers LPT
switching when all
its secondary points
detect faults.
● Non-strict mode
A primary point
triggers LPT
switching when
anyone of its
secondary points
detects a fault.

Fault Detection PW OAM LPT OAM This parameter

Mode LPT OAM displays the fault
detection mode of
point-to-multipoint
LPT.
● 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 switching is
triggered.
● 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

Period(100ms) displays or specifies
the fault detection
period of point-to-
multipoint LPT.

a user-side port.


of LPT packet out
ports at both ends,
when the service
network is an L2
network.
Parameters of Secondary Point


second point for point-
to-multipoint LPT.
Sencondary Function - - This parameter

Point displays the port or
PW ID for the
secondary point of
point-to-multipoint
LPT.

a user-side port.

of LPT packet out
ports at both ends,
when the service
network is an L2
network.
B.6.2.24 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

PW specifies the type of
primary point for
QinQ point-to-multipoint
L2 net LPT. The value range
of 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.
● If the service
network is a PSN,
select PW.
● If the service
network is a QinQ
network, select
QinQ.
● If the service
network is an L2
network, select L2
net.

specifies the board
where the primary
point of point-to-
This parameter is valid
only when Point Type
is set to UNI.


specifies the port
where the primary
point of point-to-
is set to UNI.
Point ID - - This parameter

specifies the service ID
for the primary point
of point-to-multipoint
LPT.
is set to PW or QinQ.

a local NE.
of the primary point is
set to UNI, and when
Point Type of the
secondary point is set
to L2 net.

an opposite NE.
is set to L2 net.

that is carried by an
LPT packet to traverse
an L2 network.
is set to L2 net.

LPT package out port - - This parameter

of an LPT packet.
is set to L2 net.
Parameters of secondary point

Point Type UNI - This parameter

PW displays or specifies
the type of secondary
QinQ point for point-to-
L2 net multipoint LPT.

specifies the board
where the secondary
point of point-to-
is 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.
L2 net.
Selected Points - - This parameter

displays the selected
port where the
secondary point of
point-to-multipoint
LPT resides.
L2 net.


a local NE.
is set to UNI.

an opposite NE.
Point Type of the
to L2 net.

that is carried by an
LPT packet to traverse
an L2 network.
Point Type of the
to L2 net.
LPT Package out port - - This parameter

of an LPT packet.
Point Type of the
to L2 net.
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 ● This parameter specifies the name

Domain Name of the maintenance domain.
● The maintenance domain refers to
the network for the Ethernet OAM.
● This parameter can contain a
maximum of eight bytes.
Maintenance 0 4 ● Maintenance Domain Level

Domain Level 1 specifies the level of the
maintenance domain.
2
● The values 0 to 7 indicates
3 maintenance domain levels in an
4 ascending order.
5 ● MEPs transparently transmit OAM
6 protocol packets if the packets
have a higher level than the
7 parameter value.
● MEPs discard OAM protocol
packets if the packets have a lower
level than the parameter value.
● 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
the 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

Domain Name maintenance domain of the created
maintenance association.
Maintenance - - ● This parameter specifies the name

Association of the maintenance association,
Name 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.
● 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 ● This parameter specifies the

Period 10ms interval for transmitting packets in
the CC.
100ms
● The CC is performed to check the
1s availability of the service.
10s
1m
10m
Protocol/ 802.1ag 802.1ag When the Ethernet service OAM

Standard Y.1731 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.
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
the Function Tree.
3. Select the maintenance association in which an MEP needs to be created.
Choose New > New MEP Point.


Domain Name maintenance domain of the created
MEP.

Association maintenance association of the
Name 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 ● This parameter specifies the MEP

ID.
● 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 ● Direction specifies the direction of

Egress the MEP.
● 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 ● This parameter specifies whether

Inactive to enable the CC function of the
MEP.
● 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
the Function Tree.
3. Choose OAM > Manage Remote MEP Point. The Manage Remote MEP
Point dialog box is displayed.
4. Click New.


Domain Name maintenance domain of the MEP.

Association maintenance association of the
Name created MEP.
Remote 1 to 2048 - ● This parameter specifies the ID of

Maintenance the remote MEP.
Point ID(e.g: ● If other MEPs will initiate OAM
1,3-6) 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
the 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 maintenance 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 ● This parameter specifies the MIP

ID.
● 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
the 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

Maintenance Deselected if the LB test is performed on the
Point ID basis of Destination Maintenance
Point IDs.
Destination Selected Selected This parameter needs to be selected

Maintenance Deselected if the LB test is performed on the
Point MAC basis of MAC addresses.
Address
Maintenance - - This parameter indicates the name of

Domain Name the maintenance domain for the LB
test.

Association the maintenance association for the
Name LB test.
Source - - ● This parameter specifies the

Maintenance source maintenance point in the
Point ID LB test.
● Only the MEP can be set to the
source maintenance point.
Destination - - ● This parameter specifies the

Maintenance destination maintenance point in
Point ID the LB test.
● Only the MEP ID can be set to the
Destination Maintenance Point
ID.
● Destination Maintenance Point
ID can be set only when MP ID is
selected.
Destination - 00-00-00-00-00-0 ● This parameter specifies the MAC

Maintenance 0 address of the port where the
Point MAC destination maintenance point is
Address located in the LB test.
● Only the MAC address of the MEP
can be set to the MAC address of
the Destination Maintenance
Point MAC Address.
MAC Address can be set only
when Sink Maintenance Point
MAC Address.

Transmitted 1 to 255 3 ● This parameter specifies the

Packet Count number of packets transmitted
each time in the LB test.
● When the value is greater, the
required duration is longer.
Transmitted 64 to 1400 64 ● This parameter specifies the length

Packet Length of a transmitted LBM packet.
● 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 ● This parameter specifies the

Packet Priority priority of transmitting packets.
● 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
the 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

Maintenance Deselected if the LT test is performed on the
Point ID basis of MP IDs.

Destination Selected Selected This parameter needs to be selected

Maintenance Deselected if the LT test is performed on the
Point MAC basis of MAC addresses.
Address

Domain Name the maintenance domain for the LT
test.

Association the maintenance association for the
Name LT test.
Source - - ● This parameter specifies the

Maintenance source maintenance point in the
Point ID LT test.
● Only the MEP can be set to the
source maintenance point.
Destination - - ● This parameter specifies the

Maintenance destination maintenance point in
Point ID the LT test.
● Only the MEP ID can be set to the
Destination Maintenance Point
ID.
ID can be set only when MP ID is
selected.
Destination - 00-00-00-00-00-0 ● This parameter specifies the MAC

Maintenance 0 address of the port where the
Point MAC destination maintenance point is
Address located in the LT test.
● Only the MAC address of the MEP
can be set to the MAC address of
the Destination Maintenance
Point MAC Address.
MAC Address can be set only
when Sink Maintenance Point
MAC Address.
Parameters for the Detection Result

Source - - This parameter indicates the source

Maintenance maintenance point in the LT test.
Point ID

Destination - - This parameter indicates the MAC

Maintenance address of the port where the
Point ID/MAC destination maintenance point is
located in the LT test.
Response - - This parameter indicates the MAC

Maintenance address of the port where the
Point ID/MAC responding maintenance point is
located in the LT test.
Hop Count 1 to 64 - ● 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.
● 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 >
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

Period(s) stops 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

Interval(s) displays 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.
Enable OAM Protocol Enabled Disabled ● This parameter

Disabled indicates or specifies
whether to enable the
OAM protocol.
● 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 ● This parameter

Passive indicates or specifies
the working mode of
the OAM.
● The port whose OAM
working mode is set
to Active can initiate
the OAM connection.
● The port whose OAM
working mode is set
to Passive can only
wait for the opposite
end to send the OAM
connection request.
● The OAM working
mode of the
equipment at only
one end can be
Passive.


Range Value
Link Event Notification Enabled Enabled ● This parameter

Disabled indicates or specifies
whether the local link
events can be notified
to the opposite end.
● 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.
● This parameter is set
according to the


Range Value
Remote Side Loopback Response Disabled Disabled ● This parameter

Enabled indicates or specifies
whether the port
responds to the
remote loopback.
● 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.
● If a port does not
support remote
loopback response,
this port does not
respond to the
loopback request from
the remote port
regardless of the OAM
port status.
Loopback Status Non- - This parameter indicates

Loopback the loopback status at
Initiate the local end.
Loopback NOTE
at 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.


corresponding port.
Error Frame 1000 to 60000, in 1000 This parameter specifies the duration
Monitor step of 100 of monitoring error frames.
Window(ms)
Error Frame 1 to 4294967295, 1 ● This parameter specifies the

Monitor in step of 1 threshold of monitoring error
Threshold(frame frames.
s) ● 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 This parameter specifies the window

Period 892800000, in of monitoring the error frame period.
Window(frame) step of 1
Error Frame 1 to 892800000, 1 ● This parameter specifies the

Period in step of 1 threshold of monitoring the error
Threshold(frame frame period.
s) ● 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 60 This parameter specifies the time

Second of 1 window of monitoring the error
Window(s) frame second.

Error Frame 10 to 900, in step 1 ● This parameter specifies the

Second of 1 threshold of monitoring error
Threshold(s) frame seconds.
● 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
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 ● Disable Disable Enables or disables

● Enable bandwidth
notification.

Client Layer Level 0-7 7 Specifies the client

layer level.
NOTE
● The client layer level
must be the same as
that on the
interconnected
equipment.
● The client layer level
is higher than or
equal to that of the
local MEP.
Periodic ● Period Period Specifies whether to

● Non-period periodically send
bandwidth notification
packets.
Periodic(s) ● 1 1 Specifies the interval

● 10 for sending bandwidth
notification packets.
● 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


Mapping Relation ID 1 to 8 1 This parameter

mapping relationship
between DS domains.
Mapping Relation - Default Map This parameter

Name indicates the name of
the mapping
relationship between
DS domains.
NOTE
If one default DS domain exists on the OptiX RTN 900 equipment, Mapping Relation ID is set
to 1, and Mapping Relation Name is set to Default Map. If these parameters are not set, all
the ports belong to this domain.
Parameters for Ingress Mapping Relation

CVLAN 0 to 7 - ● This parameter

indicates the
priority of the C-
VLAN of the
ingress packets.
● C-VLAN indicates
the client-side
VLAN, and the
value 7 indicates
the highest priority.

indicates the
priority of the S-
VLAN of the
ingress packets.
● S-VLAN indicates
the server-side
VLAN, and the
value 7 indicates

IP DSCP 0 to 63 - ● This parameter

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
● 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 - ● Displays the MPLS

EXP value of
ingress packets.
● 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 - ● This parameter

AF11 indicates the per-
hop behavior
AF12 (PHB) service class
AF13 of the DS domain.
AF21 ● The PHB service
AF22 class refers to the
forwarding
AF23 behavior of the DS
AF31 node on the
AF32 behavior aggregate
(BA) operation. The
AF33
forwarding
AF41 behavior can meet
AF42 the specific
requirements.
AF43
● The PHB service
EF
classes are BE, AF1,
CS6 AF2, AF3, AF4, EF,
CS7 CS6, and CS7. The
priorities (C_VLAN
priority, S_VLAN
priority, DSCP value
and MPLS EXP
value) contained in
the packets of the
DS domain and the
eight PHB service
classes meet the
requirements of the
specified or default
mapping
relationship.

Parameters for Egress Mapping Relation


AF11 indicates the PHB
service class of the
AF12 DS domain.
AF22 forwarding
behavior of the DS
AF23 node on the
AF32 (BA) operation. The
forwarding
AF33
behavior can meet
AF41 the specific
AF42 requirements.
EF
AF2, AF3, AF4, EF,
CS7 priorities (C_VLAN
priority, S_VLAN
and MPLS EXP
value) contained in
the packets of the
DS domain and the
eight PHB service
classes meet the
requirements of the
mapping
relationship.
CVLAN 0 to 7 - ● This parameter

indicates the
priority of the C-
VLAN of the egress
packets.
the client-side
VLAN, and the
value 7 indicates


indicates the
priority of the S-
VLAN of the egress
packets.
the server-side
VLAN, and the
value 7 indicates

indicates the DSCP
priority of the IP
addresses of the
ingress packets.
● 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 - ● Displays the MPLS

EXP value of egress
packets.
● When a packet
arrives at an NNI
port, the NNI port
obtains the packet
priority value
depending on its
trusted priority
type (MPLS EXP
value) and specifies
the PHB service
class of the packet
according to the
mappings between
packet priorities
and PHB service
classes.



indicates 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
MPLS-EXP that contain the
C_VLAN priority,
S_VLAN priority, DSCP
value or MPLS value.
By default, the
untrusted packets are
mapped to the BE
service class for best-
effort forwarding.
NOTE
● For the E-Line
services that are
transparently
transmitted end to
end (UNI-UNI), a
UNI port only trusts
DSCP value.
● An NNI port
carrying MPLS/
PWE3 services trusts
only packets with
MPLS EXP values.
● 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
> QoS Management > Diffserv Domain Management > Diffserv Domain
2. Click New.


Mapping Relation ID 2 to 8 - This parameter

mapping relationship
of a DS domain.
Mapping Relation - - This parameter

Name specifies the name of
the mapping
relationship of a DS
domain.
Parameters for Ingress Mapping Relation

C-VLAN 0 to 7 - ● This parameter

specifies the C-
VLAN priority of
the ingress packets.
the client-side
VLAN, and the
value 7 indicates
S-VLAN 0 to 7 - ● This parameter

specifies the S-
VLAN priority of
the ingress packets.
the server-side
VLAN, and the
value 7 indicates


specifies the DSCP
priority of the IP
addresses of the
ingress packets.
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 - - ● Displays the MPLS

EXP value of
ingress packets.
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
egress MPLS
packet.


AF12 DS domain.
AF22 forwarding
behavior of the DS
AF23 node on the
forwarding
AF33
behavior can meet
AF41 the specific
AF42 requirements.
EF
AF2, AF3, AF4, EF,
priority, S_VLAN
and MPLS EXP
value) contained in
the packets of the
DS domain and the
eight PHB service
classes meet the
requirements of the
mapping
relationship.

Parameters for Outbound Mapping Relationship


AF12 DS domain.
AF22 forwarding
behavior of the DS
AF23 node on the
forwarding
AF33
behavior can meet
AF41 the specific
AF42 requirements.
EF
AF2, AF3, AF4, EF,
priority, S_VLAN
and MPLS EXP
value) contained in
the packets of the
DS domain and the
eight PHB service
classes meet the
requirements of the
mapping
relationship.
C-VLAN 0 to 7 - ● This parameter

specifies the C-
VLAN priority of
the egress packets.
the client-side
VLAN, and the
value 7 indicates

S-VLAN 0 to 7 - ● This parameter

specifies the S-
VLAN priority of
the egress packets.
the server-side
VLAN, and the
value 7 indicates

specifies the DSCP
priority of the IP
addresses of the
egress packets.
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 - - ● Displays the MPLS

EXP value of egress
packets.
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
egress MPLS
packet.



specifies the board
that uses the mapping
relationships between
DS domains.

displays the available
port list from which
you can select the port
that uses the mapping
DS domains.

displays the selected
port list. The ports in
the list use the
mapping relationships
between DS domains.

Packet Type cvlan cvlan ● This parameter

svlan specifies the type of
the packet.
ip-dscp
● The packets trusted
mpls-exp by the OptiX RTN
900 are the
C_VLAN, S_VLAN, IP
DSCP and MPLS
packets that
contain the C_VLAN
priority, S_VLAN
or MPLS EXP value.
By default, the
untrusted packets
are mapped to the
BE service class for
best-effort
forwarding.
NOTE
● For the E-Line
services that are
transparently
transmitted end to
end (UNI-UNI), a
DSCP value.
● An NNI port carrying
MPLS/PWE3 services
trusts only packets
with MPLS EXP
values.
port trusts only
packets with 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
> QoS Management > Diffserv Domain Management > Diffserv Domain
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

Name indicates the name of
the mapping 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
● For the E-Line
services that are
transparently
transmitted end to
end (UNI-UNI), a
DSCP value.
● An NNI port
carrying MPLS/
PWE3 services trusts
only packets with
MPLS EXP values.
port trusts only
packets with DSCP
values or S-VLAN
priorities.

specifies the board
where the port is
located.

port.


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
> QoS Management > Policy Management > Port Policy from the Function
Tree.
2. Click the CoS Configuration tab.
Parameters
Policy ID - - This parameter

indicates the policy ID
of the port.
Policy Name - - This parameter

the policy name of the
port.
WRR Scheduling - - This parameter

Policy indicates the current
WRR scheduling
policy.

CoS CS7 - ● 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
AF1 policies for the
BE queues at different
service classes.
● CS6-CS7: indicates
the highest service
grade, which is
mainly involved in
signaling
transmission.
● EF: indicates fast
forwarding. This
service class is
applicable to the
traffic whose delay
is small and packet
loss ratio is low, for
example, voice and
video services.
● AF1-AF4: indicates
assured forwarding.
This service class is
applicable to the
traffic that requires
rate guarantee but
does not require
delay or jitter limit.
● BE: indicates that
the traffic is
forwarded in best-
effort manner
without special
processing.

Grooming Police SP CS7, CS6, EF, BE: SP ● The strict priority

After 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.
● 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.
● 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).
set according to
the planning
information.
Enable Bandwidth Disabled Disabled ● This parameter

Restriction Enabled indicates or
specifies whether
traffic shaping is
enabled for an
egress queue
corresponding to a
PHB service class.
● CIR (kbit/s), PIR
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit is
set to Enabled.
set according to
the planning
information.
CIR(kbit/s) - - This parameter is set

according to the
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

according to the

PBS(byte) - - ● 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.
set according to
the planning
information.
Tail Drop Threshold — — ● Two port

(256 bytes) congestion
avoidance
Port WRED Policy — — algorithms are
available: tail drop
and weighted
random early
detection (WRED).
● If tail drop is used,
set Tail Drop
Threshold (256
bytes) only.
● 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
Tree.
2. Click New. The Create Port Policy dialog box is displayed.

Parameters

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.

name of the port.

WRR Scheduling Policy - - ● This parameter

specifies the
desired WRR
scheduling policy.
● The WRR weight
set in the WRR
scheduling policy
only applies to
WRR queues.
● 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.
● 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
EF classes
AF4 respectively map
AF3 eight queuing
entities. The
AF2 OptiX RTN 900
AF1 provides different
BE QoS policies for
the queues at
different service
class.
● CS6-CS7:
indicates 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.
● AF1-AF4:
indicates ensured
forwarding. This
service class is
applicable to the
traffic that
requires rate
guarantee but
does not require
delay or jitter
limit.
the traffic is
forwarded in
best-effort
manner without
special
processing.

Grooming Police After SP CS7, CS6, EF, BE: SP ● 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.
● 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.
● 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).
set according to
the planning
information.
Bandwidth Limitation Disabled Disabled ● Bandwidth Limit

Enabled indicates or
specifies whether
traffic shaping is
enabled for an
egress queue
corresponding to
a PHB service
class.
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit
is set to Enabled.
set according to
the planning
information.
CIR(kbit/s) - - This parameter is

set according to the
planning
information.

PIR(kbit/s) - - ● 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.
● 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.
set according to
the planning
information.
CBS(byte) - - This parameter is

planning
information.


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.
set according to
the planning
information.
Tail Drop Threshold (256 - - ● Two port

bytes) congestion
avoidance
Port WRED Policy - - algorithms are
available: tail
drop and
weighted random
early detection
(WRED).
● If tail drop is
used, set Tail
Drop Threshold
(256 bytes) only.
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
Tree.

2. Click the Traffic Classification Configuration tab.

3. Click New.

Traffic Classification 1 to 512 - This parameter

ID specifies the ID of the
traffic classification.
ACL Action Permit Permit ● The access control

Deny list (ACL)
determines
whether to forward
or discard the
packets that enter
the port according
to the specified
matching rules.
● 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.
● 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 ● This parameter

Between Matched specifies the logical
Rules relationship
between the traffic
classification
matching rules.
● The OptiX RTN 900
supports the
setting of the
logical AND
between multiple
matching rules.
Match Type DSCP Value - ● After you click Add

CVlan ID or Delete, complex
traffic classification
CVlan priority can be performed
SVlan ID on the traffic that
SVlan priority enters the ingress
port according to
Source MAC Address the preset
Destination MAC matching rules.
Address ● Traffic type is
Destination IP Address based on the
Source IP Address associated Ethernet
packets. Therefore,
Protocol Type
this parameter is
Source Port set according to
Destination Port the packet type
and the planning
ICMP Packect Type
information.
Code
● 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 - - ● If the matching

value of the
packets is the same
as the preset
Match Value, the
packets match the
rules of complex
traffic
classification.
● If Match Value is
set to 0 for the
CVLAN ID, all
packets with
CVLAN IDs match
the rules of
complex traffic
classification. If
Match Value is set
to 0 for the SVLAN
ID, all packets with
SVLAN IDs match
the rules of
complex traffic
classification.
set according to
the planning
information.
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 ● This parameter

CS7 specifies the PHB
service class queue
CS6 mapped by the
EF traffic classification
AF4 packets.
AF3 ● If this parameter is
set to empty (-),
AF2 the traffic
AF1 classification
BE packets map the
PHB service class
queue according
the mapping
specified in the
topic about Diffserv
domain
management.
set according to
the planning
information.
Enable Bandwidth Disabled Enabled ● This parameter

Restriction Enabled indicates or
specifies whether
the CAR operation
is performed for
the flow in the
ingress direction.
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit is
set to Enabled.
set according to
the planning
information.

CIR(kbit/s) - - ● 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.
● 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
that the packets
are 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.
set according to
the planning
information.

PIR(kbit/s) - - ● When the rate of

the packets is more
than the PIR, the
packets that exceed
the rate restriction
are marked red and
directly discarded.
● 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
that the packets
are 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.
set according to
the planning
information.

CBS(byte) - - ● During a certain

period, if the rate
of the packets
whose processing
method is marked
"Pass" is not more
than the CIR,
certain burst
packets are
allowed and can be
first forwarded in
the case of
network
congestion. The
maximum traffic of
determined by the
CBS.
set according to
the planning
information.
PBS(byte) - - ● 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
determined by the
PBS.
set according to
the planning
information.

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
Green packets in red are first
discarded.
Processing Mode Discard - ● This parameter

Pass specifies the
method of
Remark handling the
packets.
● Discard: The
packets are
discarded.
● Pass: The packets
are forwarded.
● Remark: The
packets are
remarked.
"Remark" indicates
that the packets
are 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.

Re-Mark CoS CS7 - If the handling

CS6 method is set to
"Remark", you can
EF reset the CoS of the
AF4 packets.
AF3
AF2
AF1
BE
Egress Parameters
Bandwidth Limit Disabled Enable ● This parameter

Enable indicates or
specifies whether
the traffic shaping
is performed in the
egress function.
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit is
set to Enabled.
set according to
the planning
information.

CIR(kbit/s) - - ● In the case that no

packets exist in the
egress queue:
When the rate of
the packets is not
more than the CIR,
these packets
directly enter the
egress queue.
● In the case that
certain packets
exist in the 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.
set according to
the planning
information.

PIR(kbit/s) - - ● In the case that no

packets exist in the
egress queue: If the
rate of the packets
is more than the
CIR but is not more
than the PIR, the
packets whose rate
is more than the
CIR enter the
egress queue,
which forwards the
packets to the next
port at the CIR. If
the rate of the
packets is more
than the PIR, the
packets are directly
discarded.
● In the case that
certain packets
exist in the 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.
set according to
the planning
information.

CBS(byte) - - ● 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
determined by the
CBS.
set according to
the planning
information.
PBS(byte) - - ● If the rate of the

packets is more
than the CIR but is
not more than the
PIR during a
certain period, the
burst packets enter
the egress queue.
The maximum
traffic of the burst
packets is
determined by the
PBS.
set according to
the planning
information.
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
> QoS Management > Port Shaping Management from the Function Tree.
2. Click New.

Parameters for Port Shaping Management

Slot No. - - This parameter

specifies the slot ID.

specifies the port.
PIR (kbit/s) - - If the traffic shaping

OptiX RTN 900
processes the packets
in the buffer queue
through the following
methods when no
packets are available
in the queue.
● 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.
● 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
determined by the
PBS.
● When the buffer
queue is not empty,
the packets whose
rate passes the

PBS (bytes) - - 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
> QoS Management > Policy Management > Port WRED Policy from the
Function Tree.
2. Click New.
Parameters

specifies the policy ID
of the WRED policy.
Assign automatically Selected Deselected This parameter

automatically assign a
policy ID to the WRED
policy. If this
parameter is selected,
the policy ID for the
WRED policy is
automatically
assigned.

name of the WRED
policy.
Packet Color Green - Packets with different

Yellow colors have different
discard thresholds and
Red discard ratios. In the
case of congestion,
lower priority packets

Lower Discard 0 to 480 32 are discarded first so

Threshold (256 that higher priority
bytes) packets can pass.
Upper Discard 0 to 480 80

Threshold (256
bytes)
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
> QoS Management > Policy Management > Service WRED Policy from the
Function Tree.
2. Click New.
Parameters

specifies the policy ID
of the WRED policy.
Assign automatically Selected Deselected This parameter

automatically assign a
policy ID to the WRED
policy. If this
parameter is selected,
the policy ID for the
WRED policy is
automatically
assigned.

name of the WRED
policy.
Packet Color Green - Packets with different

Yellow colors have different
discard thresholds and
Red discard ratios. In the

Lower Discard 0 to 480 32 case of congestion,

Threshold (256 lower priority packets
bytes) are discarded first so
that higher priority
Upper Discard 0 to 480 80 packets can pass.
Threshold (256
bytes)
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
> QoS Management > Policy Management > WRR Scheduling Policy from
the Function Tree.
2. Click New.
Parameters
ault
Valu
e
Policy ID - - This parameter specifies the

policy ID of the WRR
scheduling policy.
Policy Name - - This parameter specifies the

policy name of the WRR
scheduling policy.
Assign automatically Selected Des This parameter specifies

Deselected elect whether to automatically
ed assign a policy ID to the
WRED policy. If this
parameter is selected, the
policy ID for the WRED policy
is automatically assigned.


ault
Valu
e
Scheduling Weight 1 to 100 - ● The eight classes of service

(CoSs), namely, BE, AF1,
AF2, AF3, AF4, EF, CS6,
and CS7 correspond to
eight queues.
● The Scheduling Weight
parameter indicates the
percentage of the
bandwidth resources
gained by the WRR queue.
● 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.
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
> QoS 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

ID of the port.

automatically
allocate the policy
is selected, the
system
automatically
ID, and then the
policy ID cannot be
set manually.

name of the port.


specifies the
desired WRR
scheduling policy.
● The WRR weight
set in the WRR
scheduling policy
only applies to
WRR queues.
● 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.
● 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
EF classes
AF3 eight queuing
entities. The
AF2 OptiX RTN 900
BE QoS policies for
the queues at
different service
class.
● CS6-CS7:
indicates 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.
● AF1-AF4:
indicates ensured
forwarding. This
service class is
applicable to the
traffic that
requires rate
guarantee but
does not require
delay or jitter
limit.
the traffic is
forwarded in
best-effort
manner without
special
processing.

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.
● 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.
● 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).
set according to
the planning
information.

specifies whether
traffic shaping is
enabled for an
egress queue
corresponding to
a PHB service
class.
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit
is set to Enabled.
set according to
the planning
information.

planning
information.


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.
● 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.
set according to
the planning
information.

planning
information.


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.
set according to
the planning
information.

bytes) congestion
avoidance
available: tail
drop and
weighted random
early detection
(WRED).
● If tail drop is
used, set Tail
Drop Threshold
(256 bytes) only.
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
> QoS Management > Policy Management > PW Policy from the Function
Tree.
2. Click New. The Create PW Policy dialog box is displayed.

Parameters

ID of the port.

automatically
allocate the policy
is selected, the
system
automatically
ID, and then the
policy ID cannot be
set manually.

name of the port.


specifies the
desired WRR
scheduling policy.
● The WRR weight
set in the WRR
scheduling policy
only applies to
WRR queues.
● 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.
● 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
EF classes
AF3 eight queuing
entities. The
AF2 OptiX RTN 900
BE QoS policies for
the queues at
different service
class.
● CS6-CS7:
indicates 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.
● AF1-AF4:
indicates ensured
forwarding. This
service class is
applicable to the
traffic that
requires rate
guarantee but
does not require
delay or jitter
limit.
the traffic is
forwarded in
best-effort
manner without
special
processing.

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.
● 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.
● 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).
set according to
the planning
information.

specifies whether
traffic shaping is
enabled for an
egress queue
corresponding to
a PHB service
class.
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit
is set to Enabled.
set according to
the planning
information.

planning
information.


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.
● 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.
set according to
the planning
information.

planning
information.


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.
set according to
the planning
information.

bytes) congestion
avoidance
available: tail
drop and
weighted random
early detection
(WRED).
● If tail drop is
used, set Tail
Drop Threshold
(256 bytes) only.
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
> QoS Management > Policy Management > QinQ Policy from the Function
Tree.
2. Click New. The Create QinQ Policy dialog box is displayed.

Parameters

ID of the port.

automatically
allocate the policy
is selected, the
system
automatically
ID, and then the
policy ID cannot be
set manually.

name of the port.


specifies the
desired WRR
scheduling policy.
● The WRR weight
set in the WRR
scheduling policy
only applies to
WRR queues.
● 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.
● 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
EF classes
AF3 eight queuing
entities. The
AF2 OptiX RTN 900
BE QoS policies for
the queues at
different service
class.
● CS6-CS7:
indicates 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.
● AF1-AF4:
indicates ensured
forwarding. This
service class is
applicable to the
traffic that
requires rate
guarantee but
does not require
delay or jitter
limit.
the traffic is
forwarded in
best-effort
manner without
special
processing.

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.
● 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.
● 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).
set according to
the planning
information.

specifies whether
traffic shaping is
enabled for an
egress queue
corresponding to
a PHB service
class.
(kbit/s), CBS
(byte), and PBS
(byte) can be set
only when
Bandwidth Limit
is set to Enabled.
set according to
the planning
information.

planning
information.


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.
● 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.
set according to
the planning
information.

planning
information.


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.
set according to
the planning
information.

bytes) congestion
avoidance
available: tail
drop and
weighted random
early detection
(WRED).
● If tail drop is
used, set Tail
Drop Threshold
(256 bytes) only.
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-16 Parameters on the Main Interface

Set IP mark bits ● IP FLAG BIT0 IP FLAG BIT0 Set the flag bit of the
● IP TOS BIT3 marked packets,
which is used to count
● IP TOS BIT4 the packets.
● IP TOS BIT5
● IP TOS BIT6
● IP TOS BIT7
ID 1 to 5 1 Display or set the ID.
Automatically Assign ● Checked Unchecked Set the automatically

● Unchecked assign.
The test ID will be
assigned
automatically if this
parameter is checked.
Name - - Display or set the

name.
Role ● Upstream Intermediate Display and set the

● Intermediate role of the test
packets.
● Downstream
Action ● Collect only Collect only Set the function of the

● Mark and collect testing.
● Restore and collect
Auto Stop After 1 to 10080 5 Display and set the

(minutes) time for automatically
stopping.

Logical Relation ● And And Specifies the logical

Between Matched ● Or relationships between
Rules matched rules.
● And indicates that
the packet matches
the flow only when
the packet matches
each traffic
classification rules.
● Or indicates that
the packet matches
the flow when the
packet matches
one of the traffic
classification rules.
NOTE
The equipment supports
only And.
Match Type ● Outer VLAN - Set the match type.

● Inner VLAN
● Outer VLAN Priority
● Inner VLAN Priority
● Outer VLAN Drop
Priority
● DSCP Value
● Destination MAC
Address
● Source MAC
Address
● Protocol Type
● Destination IP
Address
● Source IP Address
● Destination Port
● Source Port
● Inner VLAN Drop
Priority
● Ethernet Type
● 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 - Display and set the

VLAN:1:0}&{Inner rules for marking. The
VLAN:2:0} conformed packets
will be marked.
Status ● Stop Stop Display and set the

● Start testing status.
Number of Marked - - Display the number of

Packets the marked packets
after testing.
Number of Marked - - Display the number of

Bytes 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-17 VUNI parameters

Direction ● Transmit - Display the

● Receive direction 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-18 QinQ parameters


test packets.
Service - - Display and set

the service ID.
QinQ - - Display and set

the QinQ ID.
Table B-19 Tunnel parameters


test packets.
Tunnel ID - - Indicates the

tunnel ID.
Port - - Display and set

the port number.
PW Label - - Display and set

the PW label.
Service Tag Role ● User User Display the

● Service service tag role of
E-LAN service.
PW Type ● Ethernet Ethernet Set the PW type.

● 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 ● Not in use Not in use Display the

● Used first control word of
the PW.
● Use required
UNI Port ● NULL NULL Indicates the way

Encapsulation ● C-Tag in which the port
Type processes
● S-Tag accessed packets.
UNI Port TPID - - Specifies the type

field of the UNI
port TPID.
Service Type ● E-Line service E-LAN service Specifies the type

● E-LAN service field of the
Service Type.
● 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
This section describes the parameters for the Ethernet services and Ethernet
features on the EoS/EoPDH plane, including service parameters, protocol
parameters, OAM parameters, Ethernet port parameters, and QoS parameters.
NOTE
OptiX RTN 905/905e 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 Configuration > Ethernet Service > Ethernet Line Service from the
Function Tree.

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 ● 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.
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 - - ● Specifies the port of the service

source.
● 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 1-4095 - ● This parameter can be set to null,

VLAN(e.g. 1,3-6) a number, or several numbers.
When setting this parameter to
several numbers, use the comma
(,) to separate the discrete
numbers, or use the hyphen (-) to
represent consecutive numbers.
For example, the numbers 1, and
3-6 indicate 1, 3, 4, 5, and 6.
● The number of VLANs must be the
same as the value of Sink
VLAN(e.g. 1,3-6).
● If this parameter is set to null, all
the services at the source port are
used as the service source.
● 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 - - ● Specifies the port of the service

sink.
● This parameter cannot take the
same value as Source Port.
● 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 - ● This parameter can be set to null,

1,3-6) a number, or several numbers.
When setting this parameter to
several numbers, use the comma
(,) to separate the discrete
numbers, or use the hyphen (-) to
represent consecutive numbers.
For example, the numbers 1, and
3-6 indicate 1, 3, 4, 5, and 6.
● The number of VLANs must be the
same as the value of Source
VLAN(e.g. 1,3-6).
● If this parameter is set to null, all
the services at the sink port are
used as the service sink.
● 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-21 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 - ● When the source port or the sink

Disabled port is set to a PORT, set Port
Enabled to Enabled.
● This parameter need not be set
when the source port or sink port
is a VCTRUNK.

TAG Tag Aware - ● If all the accessed services are

Access frames with VLAN tags (tagged
frames), set this parameter to Tag
Hybrid Aware.
● If all the accessed services are
frames without VLAN tags
(untagged frames), set this
parameter to Access.
● If the accessed services contain
tagged frames and untagged
frames, set this parameter to
Hybrid.
Table B-22 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 ● Specifies the direction of the

Uplink bound path.
Downlink ● Set this parameter to
Bidirectional unless otherwise
specified.

Bound Path - - You need to plan and set this

parameter according to the following
principles:
● The capacity of the VCTRUNK is
determined by the actual
bandwidth required by the
services.
● 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.
● 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 - - Displays the number of the bound VC

Count 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

Rang lt
e Value
Board - - Displays the

board name.


Rang lt
e Value
Service Type EPL EPL Specifies the

EVPL( service type to
QinQ) EVPL(QinQ).


Rang lt
e Value
Service Direction Bidire Bidire ● When this

ctiona ctiona parameter
l l is set to
Unidir Unidirectio
ection nal, only
al the service
from the
service
source to
the service
sink is
created.
That is, the
service
source is
forwarded
only to the
sink port.
● When this
parameter
is set to
Bidirection
al, 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.


Rang lt
e Value
● It is
recommend
ed that you
set this
parameter
to
Bidirection
al.


Rang lt
e Value
Operation Type ● Ad Strip ● When used

d S- for private
S- VLAN line
VL services,
AN QinQ can
● Tra process
ns VLAN tags
par in different
ent manners as
ly required.
tra ● When
ns Service
mit Direction is
C- set to
VL Unidirectio
AN nal, you
● Tra can set
ns Operation
par Type to
ent Strip S-
ly VLAN.
tra ● Set this
ns parameter
mit according
S- to actual
VL situations.
AN
● Tra
ns
par
ent
ly
tra
ns
mit
S-
VL
AN
an
d
C-
VL
AN
● Tra
nsl
ate
S-


Rang lt
e Value
VL
AN
● Tra
nsl
ate
S-
VL
AN
an
d
tra
ns
par
ent
ly
tra
ns
mit
C-
VL
AN
● Stri
p
S-
VL
AN
Source Port - - ● Specifies

the port
where the
service
source
resides.
● When
creating a
bidirectiona
l Ethernet
service from
a PORT to a
VCTRUNK,
it is
recommend
ed that you
use the
PORT as
the source
port.


Rang lt
e Value
Source VLAN (e.g. 1, 3-6) 1-409 - ● You can set

5 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.
● 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).
● When you
set this
parameter
to null, all
the services
of the
source port


Rang lt
e Value
work as the
service
source.
● When you
set this
parameter
to a non-
null value,
only the
services of
the source
port whose
VLAN IDs
are included
in the value
range of
this
parameter
work as the
service
source.
Source S-VLAN 1-409 - ● This

5 parameter
must be set
to a
numerical
value.
● Only the
service of
the source
port whose
S-VLAN ID
is equal to
the value of
this
parameter
work as the
service
source.


Rang lt
e Value
Sink Port - - ● Specifies

the port
where the
service sink
resides.
● This
parameter
must be set
to be a
value
different
from
Source
Port.
● When
creating a
bidirectiona
l Ethernet
service from
a PORT to a
VCTRUNK,
it is
recommend
ed that you
use the
VCTRUNK
as the sink
port.


Rang lt
e Value
Sink VLAN(e.g. 1, 3-6) 1-409 - ● You can set

5 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.
● 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).
● When you
set this
parameter
to null, all
the services
of the sink
port work


Rang lt
e Value
as the
service sink.
● When you
set this
parameter
to a non-
null value,
only the
services of
the sink
port whose
VLAN IDs
are included
in the value
range of
this
parameter
work as the
service sink.
Sink S-VLAN 1-409 - ● This

5 parameter
must be set
to a
numerical
value.
● 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
y7 higher the
priority.

Table B-24 Parameters of port attributes

Range Value
Port - - Displays the ports

that are configured
to transmit the
service.
Port Type - - Displays the network

attribute of the
Ethernet port.
Port Enabled Enabled - ● When the source

Disabled port or the sink
port is set to a
PORT, set Port
Enabled to
Enabled.
● 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

VCTRUNK K1 VCTRUNK to bind
1- paths.
VCTRUNK
16
EMS6:
VCTRUNK
1-
VCTRUNK
8


Range Value
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 Bidirectio Bidirecti ● Specifies the

nal onal direction of the
Uplink bound path.
Downlink ● Set this
parameter to
Bidirectional
unless otherwise
specified.


Range Value
Bound Path - - You need to plan

and set this
parameter according
to the following
principles:
● The capacity of
the VCTRUNK is
determined by
the actual
bandwidth
required by the
services.
● 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.
● 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
Tree.

Table B-26 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 - - Displays whether to activate the

Status service.
Table B-27 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 - - ● Displays the S-VLAN ID of the

service source.
● 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 - - ● Displays the S-VLAN ID of the

service sink.
C-VLAN Priority - - ● Displays the priority of the C-

VLAN.
S-VLAN Priority - - ● Displays the priority of the S-

VLAN.
Activation - - Displays whether to activate the

Status service.
Table B-28 Parameters for port attributes
Port - - Displays the port name.

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.

paths.
Service Direction - - Displays the direction of the bound

VC paths.
Bound Path - - Displays the serial numbers of the

bound VC paths.

Number of - - Displays the number of the bound VC

Bound Paths paths.
Activation - - Displays whether the bound VC paths

Status 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
choose Configuration > Ethernet Service > Ethernet LAN Service from the
Function Tree.
2. Click New.

Board - - Displays the board that is configured

with a bridge.
VB name - - Describes the bridge. It is

parameter to a character string that
indicates the function of the bridge.
Bridge Type 802.1q 802.1q ● If this parameter is set to 802.1q,

802.1d an IEEE 802.1q bridge is created.
802.1ad ● If this parameter is set to 802.1d,
an IEEE 802.1d bridge is created.

Bridge Switch ● IVL/Ingress ● IVL/Ingress ● When the bridge uses the SVL
Mode Filter Enable Filter Enable mode, all the VLANs share one
(supported by (IEEE 802.1q MAC address table. When the
the IEEE bridge and the bridge uses the IVL mode, each
802.1q bridge IEEE 802.1ad VLAN has an MAC address table.
and IEEE bridge) ● When the filtering function is
802.1ad ● SVL/Ingress enabled at the ingress port, the
bridge, Filter Disable ingress port checks the VLAN tags
unsupported (IEEE 802.1d of all incoming packets. If the
by the IEEE bridge) VLAN ID contained in the VLAN
802.1d bridge) tag of a packet is not included in
● SVL/Ingress the VLAN filtering table, the
Filter Disable packet is discarded. When the
(supported by filtering function is disabled at the
the IEEE ingress port, the ingress port does
802.1d bridge not check any VLAN tag of the
and IEEE incoming packets.
802.1ad
bridge,
unsupported
by the IEEE
802.1q bridge)
Bridge Learning - - Displays the learning mode of the

Mode bridge.
Ingress Filter - - Displays whether the filtering

function is enabled at the ingress
port.
MAC Address - - Displays whether the MAC address

Self-learning self-learning of the bridge is enabled.
Active - - Displays whether to activate the

service.
Table B-31 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 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

Tag Aware of 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

10M Half-Duplex mode of the port mounted to the
bridge.
10M Full-Duplex
100M Half-
Duplex
100M Full-Duplex
GE port: 1000M
Full-Duplex

service.
Service Direction - - Displays the direction of the service.
C-VLAN - - The IEEE 802.1d/802.1q bridge does

not support this parameter.
S-VLAN - - The IEEE 802.1d/802.1q bridge does

S-VLAN Priority - - The IEEE 802.1d/802.1q bridge does

C-VLAN Priority - - The IEEE 802.1d/802.1q bridge does

Table B-32 Parameters for mounting configuration

Available - - Displays which physical port or

Mounted Ports VCTRUNK on the Ethernet switch
board can be mounted to the bridge.

Selected - - Displays which physical port or

Mounted Ports VCTRUNK on the Ethernet switch
board is mounted to the bridge.

VCTRUNK Port EFP8: VCTRUNK1 Specifies the VCTRUNK to bind

VCTRUNK1- paths.
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8

path.
parameter always takes the value
of VC12-Xv.

Uplink bound path.
specified.

following principles:
services.
bound VC-12 paths cannot
exceed 63.
● 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.
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
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
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.1d 802.1ad, create the IEEE 802.1ad
bridge.
802.1ad

Bridge Switch ● IVL/Ingress ● IVL/Ingress ● When the bridge uses the SVL
Mode Filter Enable Filter Enable mode, all the VLANs share one
(supported by (the 802.1q MAC address table. When the
the 802.1q bridge and the bridge uses the IVL mode, all the
bridge and 802.1ad VLANs correspond to their
802.1ad bridge) respective MAC address tables.
bridge, ● SVL/Ingress ● If the ingress filter is enabled, the
unsupported Filter Disable VLAN tag is checked at the ingress
by the 802.1d (the 802.1d port. If the VLAN ID does not
bridge) bridge) equal the VLAN ID of the port
● SVL/Ingress defined in the VLAN filtering table,
Filter Disable the packet is discarded. If the
(supported by ingress filter is disabled, the
the 802.1d preceding described check is not
bridge and conducted.
802.1ad
bridge,
unsupported
by the 802.1q
bridge)
Bridge Learning - - Displays the bridge learning mode.

Mode
Ingress Filter - - Displays whether the ingress filter


Self-learning self-learning function of the bridge is
enabled.
Table B-35 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

Enabled external 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

10M Half-Duplex mode of 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.
● 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.
Add S-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.
Mount Port, this parameter is
invalid.
Mount 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-36 Parameters of service mounting
Operation Type Add S-VLAN base Add S-VLAN base OptiX RTN 910/950/950A/980/980L:
for port for port For the meaning of each operation
Add S-VLAN base type, see Application of QinQ in
for Port and C- 802.1ad Bridge Services.
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 - ● 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.
Add S-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.
Mount Port, this parameter is
invalid.
Mount 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 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.


VCTRUNK Port EFP8: VCTRUNK1 Specifies the VCTRUNK to bind paths.

VCTRUNK1-
VCTRUNK16
EMS6:
VCTRUNK1-
VCTRUNK8

path.
parameter always takes the value of
VC12-Xv.

Uplink bound path.
specified.

parameter according to the following
principles:
services.
bound VC-12 paths cannot exceed
63.
● 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 - - Displays the number of the bound VC

Count path.
B.7.1.6 Parameter Description: Ethernet LAN Service

This section describes the parameters for creating an Ethernet LAN service.

Navigation Path
Tree.
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
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

Mode bridge.
Bridge Learning - - Displays the learning mode of the

Mode bridge.
Ingress Filter - - Displays whether the filtering

function is enabled at the ingress
port.

self-Learning self-learning of the bridge is enabled.

service.
Table B-39 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
● Hub ports can mutually
access each other.
● Hub ports and Spoke ports
can mutually access each
other.
● 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
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
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.
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.
● 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.
set to 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.
set to Mount Port, this
parameter is invalid.
set to Mount Port and
Base for Port and S-VLAN,
S-VLAN tag to be carried by
the data frames that enter
the IEEE 802.1ad bridge.
S-VLAN Priority - - Displays the priority of the S-

VLAN.

C-VLAN Priority - - Displays the priority of the C-

VLAN.
Table B-40 Parameters for VLAN filtering table

VLAN ID - - Displays the VLAN ID that needs to

be filtered in forwarding.

the bridge.
Forwarding - - Displays the actually specified

Physical Port forwarding port.
● Selected forwarding ports can
send packets only among
themselves.
● Selected forwarding ports can
only forward the packet that
carries the VLAN ID tag. These
ports discard the packet that
carries other VLAN tags.
● The broadcast packets transmitted
by any of Selected forwarding
ports can be forwarded only
among Selected forwarding
ports.
Activation - - Displays whether the VLAN ID entry

Status is valid.

Table B-41 Parameters for VLAN unicast

VLAN ID - - ● 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.
● 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 - - ● Displays or specifies the static

MAC address.
● A static MAC address is an address
that is set manually. It does not
age automatically and needs to be
deleted manually.
● 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.

the bridge.
Physical Port - - ● Specifies the Ethernet port that

corresponds to the MAC address.
Aging Status - - Displays the aging status of the

entries.
Table B-42 Parameters for disabling MAC addresses

VLAN ID(e.g. - - Displays or specifies the VLAN ID of

1,3-6) the service. A disabled MAC address
is valid for the VLAN with the ID as
specified by this parameter.

MAC Address - - ● Displays or specifies the disabled

MAC address. A disabled MAC
address is also called a blacklisted
MAC address.
● 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.

paths.
Service Direction - - Displays the direction of the bound

VC paths.
Bound Path - - Displays the bound paths.
Number of - - Displays the number of bound paths.

Bound Paths
Table B-44 Parameters for self-learned MAC addresses

MAC Address - - ● Displays or specifies the self-

learned MAC address. A self-
learned MAC address is also called
a dynamic MAC address.
● 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 - - ● 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.
● 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-45 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

Address Table are actually self-learned in the query
Capacity condition of a specific VLAN ID.
Table B-46 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

Address Table are actually self-learned in the query
Capacity condition 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
choose Configuration > Ethernet Service > Ethernet LAN Service from the
Function Tree.

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.
● You can set this parameter to a
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

forwarding ports bridge.
Selected - - Displays the selected forwarding

forwarding ports ports.
● The selected forwarding ports can
send packets only among
themselves.
● 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.
● 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 ● 1 to 120 Min 5 Min ● If one entry is not updated in a

Aging Time ● 1 to 120 Hour certain period, that is, if no new
packet from this MAC address is
● 1 to 12 Day received to enable the re-learning
of this MAC address, this entry is
deleted automatically. This
mechanism is called aging, and
this period is called the aging
time.
● 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.
● 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
Protection > ERPS Management.
2. Click New.
Parameters
ERPS ID 1 to 7 - ● This parameter

specifies the ID of
the Ethernet ring
protection
switching (ERPS)
instance.
● The IDs of ERPS
instances on an NE
must be different
from each other.

specifies the east port
of the ERPS instance.

specifies the west port
of the ERPS instance.

RPL Owner Ring Yes No ● This parameter

Node Flag No specifies whether
the node on the
ring is the ring
protection link
(RPL) owner.
● Only one node on
the ring can be set
as the RPL owner
for each Ethernet
ring.
● 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 - - ● This parameter

specifies the RPL
port.
● There is only one
RPL port and this
RPL port must be
the east or west
port on the RPL
owner node.
that you set the
east port on an RPL
owner as an RPL
Port.


specifies the VLAN
ID of Control
VLAN.
● 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.
● 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 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.
Loop Detect Enabled Enabled This parameter

Disabled specifies 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
Parameters
ERPS ID 1 to 7 - This parameter

indicates the ID of
the ERPS instance.

indicates the east
port of the ERPS
instance.

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.
● 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.
● The Control
VLAN must be
set to the same
value for all the
NEs on an ERPS
ring.

Destination Node 01-19- - This parameter

A7-00-00-01 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.

Hold-Off Time(ms) - 0 ● This parameter

indicates or
specifies the
hold-off time of
the ERPS hold-
off timer.
● 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 ● This parameter

indicates or
specifies the
guard time of
the ERPS guard
timer.
● 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 5 ● This parameter

1 indicates or
specifies the
WTR time of
the WRT timer
in the case of
ERPS
protection.
● 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.

● 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

indicates or
specifies the level
of the
maintenance
entity.
Last Switching Request - - This parameter

indicates the last
switching request.
RB Status - - This parameter

indicates the RB
(RPL Blocked)
status of the
packets received
by the working
node.
● noRB: The RPL
is not blocked.
● RB: The RPL is
blocked.

DNF Status - - This parameter

indicates the DNF
status of the
packets received
by the working
node.
● 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.
● 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.
● 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.
● 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 - - This parameter

Packet 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 Configuration > Layer-2 Switching Management > Spanning Tree
2. Click the Protocol Enabled tab.

VB - - Displays the created bridge.
Protocol Enabled Disabled ● Indicates whether to enable the

Enabled Disabled spanning tree protocol.
● Try to avoid Layer 2 service
loopbacks in the service
networking. If no loop occurs, you
need not start the STP/RSTP.
● If the loop is already formed in the
service networking, you must start
the STP or RSTP.
Protocol Type STP RSTP ● This parameter is valid only when

RSTP Protocol Enabled is Enabled.
● The protocol type should be set
according to the requirement of
the interconnected Ethernet
equipment. The default value is
recommended unless otherwise
specified.
B.7.2.4 Parameter Description: Spanning Tree_Bridge Parameters

This section describes the parameters for the spanning tree protocol.
Navigation Path
choose Configuration > Layer-2 Switching Management > Spanning Tree

Priority 0-61440 32768 ● The most significant 16 bits of the

bridge ID indicate the priority of
the bridge.
● When the value is smaller, the
priority is higher. As a result, the
bridge is more likely to be selected
as the root bridge.
● 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 ● Indicates the maximum age of the

CBPDU packet that is recorded by
the port.
● 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 ● Indicates the interval for

transmitting CBPDU packets
through the bridge.
● 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 4-30 15 ● Indicates the holding time of a

Delay(s) port in the listening state and in
the learning state.
● 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
2. Click the Port Parameters tab.

Port - - Displays the created bridge.
Priority 0-240 128 ● The most significant eight bits of

the port ID indicate the port
priority.
● The smaller the value of this
parameter, the higher the priority.
Port Path Cost 1-200000000 - ● Indicates the status of the network

to which the port is connected.
● 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 ● Is valid only when the RSTP is

Attribute Disabled used.
● 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.
● 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 ● Specifies whether the STP or RSTP

Enabled Disabled is enabled for the port.
Disabled, the port does not
process or transmit the BPDU.
Auto Edge Enabled Disabled ● Is valid only when Admin Edge

Detection Disabled Attribute is set to Enabled.
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.
● When Admin Edge Attribute is
set to Enabled, set this parameter
to Enabled. In other cases, it is
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

Bridge MAC specified 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 - - Displays the holding time of a port in

Delay(s) 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
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

Bridge Priority root bridge.
Designated Root - - Displays the MAC address of the

Bridge MAC specified root bridge.
Address
Designated Path - - Displays the specified path cost.

Cost
Designated - - Displays the priority of the specified

Bridge Priority bridge.
Designated - - Displays the MAC address of the

Bridge MAC specified bridge.
Address
Topology - - Displays the enabled status of

Detection topology detection.
Edge Port Status - - Displays the enabled status of the

edge port.
Running - - Displays the duration when the

Time(s) 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
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 ● This parameter is valid only when

Attribute connection connection the RSTP is used.
Link connection ● If this parameter is set to
Shared media Adaptive connection, the bridge
determines the actual point-to-
point attribute of the port
according to the actual working
mode of the port. If the port
works in full-duplex mode, the
actual point-to-point attribute of
the port is True. If the port works
in half-duplex mode, the actual
point-to-point attribute of the port
is False.
● If you set this parameter to Link
connection, the actual point-to-
point attribute of the port is True.
● If you set this parameter to
Shared media, the actual point-
to-point attribute of the port is
False.
● 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
choose 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 ● Specifies whether to enable the

Disabled IGMP snooping protocol.
● 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 Disabled Disabled ● This parameter specifies the

Tag of the method of the port to process
Packet Excluded unknown multicast packets. When
in the Multicast the IEEE 802.1q or 802.1ad bridge
Group 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.
Disabled, unknown multicast
packets are broadcast in the VLAN.
● Set this parameter as required by
the IGMP multicast server.

Max.Non- 1 to 4 3 If the bridge transmits an IGMP

Response Times group query packet to the multicast
member ports, the router port starts
the timer for the query of the
maximum response time. If the
bridge does not receive the IGMP
report packet within the maximum
response time, the bridge adds one to
the no-response times of the
multicast member port. When the
no-response times of the port exceed
the preset threshold, the bridge
deletes the multicast member from
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
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 - - ● Specifies the MAC address in the

static multicast table.
Multicast Port - - ● Specifies the port as an entry in

the static multicast table.
● 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
2. Click the Multicast Aging Time tab.

Multicast Aging 1-120 8 ● Specifies the aging time for

Time(Min) multicast table entries. When a
dynamic multicast table entry is
not updated in a certain period
(that is, no IGMP request from this
multicast address is received), this
entry is automatically deleted. This
mechanism is called aging, and
this period is called aging time.
● 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.
● 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.
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
choose Configuration > Ethernet Interface Management > Ethernet Link
Aggregation Management from the Function Tree.

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 ● Static: A static LAG is created by

Manual the user. To add or delete a
member port, you need to run the
Link Aggregation Control Protocol
(LACP) protocol. In a static LAG, a
port can be in selected, standby, or
unselected state. By running the
LACP protocol, devices exchange
aggregation information so that
they share the same aggregation
information.
● Manual: 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 ● Sharing: In a sharing LAG, all

Non-Sharing member ports always share the
traffic load. The sharing mode can
improve bandwidth utilization on
a link. When the member ports
are changed or some member
ports fail, the traffic load of each
member port is automatically re-
allocated.
● 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 ● You can set this parameter only
Non-Revertive when Load Sharing is Non-
Sharing.
Revertive, services are
automatically switched back to the
working path after the working
path recovers.
● 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 - - ● Specifies the main port in a LAG.

● 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.
● 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 - - ● Specifies the slave port in a LAG.

Standby Ports ● After a LAG is created, you need
to perform manual operations to
add or delete a slave port.
Selected - - Displays the selected slave ports.

Standby 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
choose Configuration > Ethernet Interface Management > Ethernet Link
Aggregation Management from the Function Tree.
2. Click the Link Aggregation Parameters tab.

Port Priority 0-65535 32768 ● This parameter is valid only when

LAG Type of a LAG is set to Static.
● 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 ● This parameter is valid only when

LAG Type of a LAG is set to Static.
● This parameter indicates the
priority of a LAG. The smaller the
value, the higher the priority.
● 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

Address system.
B.7.2.14 Parameter Description: LPT Management_Creation of Point-to-Point

Service LPT
This section describes the parameters for creating point-to-point service LPT.
Navigation Path
choose Configuration > Ethernet Interface Management > LPT
2. Click Query.

VCTRUNK Port - - Displays the VCTRUNK used by the

Ethernet service.

Direction - - ● Displays the direction of the

Ethernet service at the port.
● 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) ● Specifies the bearer mode of the

Ethernet LPT packets.
GFP-CSF ● The default value is
recommended.
PORT-Type Port 0-10000 100 ● When the link on which Ethernet

Hold-Off services are transmitted is
Time(ms) configured with other protection
schemes, you need to set the hold-
off time of LPT. This enables the
NE to notify the equipment at
both ends of a transmission
network of the fault on the
transmission link only when the
other protection schemes fail.
● This parameter is valid only in the
positive direction of LPT.
VCTRUNK Port 0-10000 100 ● When the link on which Ethernet

Hold-Off services are transmitted is
Time(ms) configured with other protection
schemes, you need to set the hold-
off time of LPT. This enables the
NE to notify the equipment at
both ends of a transmission
network of the fault on the
transmission link only when the
● 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
choose Configuration > Ethernet Interface Management > LPT
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) ● This parameter can be set only

Ethernet when the selected port is a
VCTRUNK.
GFP-CSF
recommended.
Port Hold-Off 0-10000 0 When the link on which Ethernet

Time(ms) services are transmitted is configured
with other protection schemes, you
need to set the hold-off time of LPT.
This enables the NE to notify the
equipment at both ends of a
transmission network of the fault on
the transmission link only when the
Parameters for Access Points

Port - - Specifies the port at the access node.
Bearer Mode GFP(HUAWEI) GFP(HUAWEI) ● This parameter can be set only

Ethernet when the selected port is a
VCTRUNK.
GFP-CSF
recommended.
B.7.2.16 Parameter Description: Port Mirroring_Creation

This section describes the parameters for creating port mirroring tasks.

Navigation Path
choose Configuration > Ethernet Interface Management > Port Mirroring
2. Click New.

Mirrored Port - - ● 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.
● Mirrored Port indicates the port
that sends the packets copied
from Mirrored Upstream Port
and Mirrored Downstream Port.
● Mirrored Port cannot be set to a
port that carries any service.
Mirrored - - ● Mirrored Upstream Port and

Upstream Port Mirrored Downstream Port
indicate the ports that copy
Mirrored - - packets for Mirrored Port.
Downstream
Port ● 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 Downstream Port can
be a PORT or a VCTRUNK. As a
PORT, the port copies the packets
that it transmits; as a VCTRUNK,
the port copies the packets that it
receives. Mirrored Port sends the
packets copied from Mirrored
Downstream Port.
NOTE
The transmit direction and receive
direction mentioned in this section are
related to the local NE.

B.7.3 Parameters for the Ethernet OAM

This section describes the parameters for the Ethernet OAM on the EoS/EoPDH
plane.
B.7.3.1 Parameter Description: Ethernet Service OAM_Creation of MDs

This topic describes the parameters for creating maintenance domains (MDs).
Navigation Path
choose Configuration > Ethernet Maintenance > Ethernet Service OAM
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

Name the MD.
Maintenance Domain Consumer High(7) Operator Low(0) Specifies the level of

Level Consumer Middle(6) the MD. The greater
the value, the higher
Consumer Low(5) the 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
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

Association Name specifies 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
2. Click New.

Maintenance - NULL Specifies the maintenance domain

Domain Name (MD) of 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 (MA) of the MP.
Name 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 - - ● 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
● 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 highest to the lowest, the first byte
FF-FF-1FFF indicates the network number, the
Common MP: second byte indicates the number of
00-00-0000 to the node in the local network, and
FF-FF-FF00 the third and forth bytes indicate the
ID of the MP on the network node.
The MP ID must be unique in the
entire network.
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 ● Specifies the MEP direction.

IP ● 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-58 Parameters for advanced attributes

Level Consumer Provider High(4) Specifies the level of a common MP.

High(7) The greater the value, the higher the
Consumer level.
Middle(6) NOTE
This parameter is valid only for a
Consumer Low(5) common MP (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 ● Specifies the timeout duration of

step of 100 an LB test.
an MEP.
LT Timeout(ms) 3000 to 60000, in 5000 ● Specifies the timeout duration of

step of 100 an LT test.
an MEP.
CCM Sending Standard MP: Standard MP Specifies the interval for sending the
Period(ms) 1000 1000 CCM packet at the MP where the CC
test is performed.
10000 Common MP:
● If this parameter takes a very
6000 5000 small value, service bandwidth
600000 decreases significantly.
Common MP: ● 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.
an MEP.
B.7.3.4 Parameter Description: Ethernet Service OAM_Enabling LB

This section describes the parameters for enabling the LB.

Navigation Path
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 Selected Not selected Select this parameter

MAC Address Not selected for 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
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
choose 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

Passive of Ethernet port OAM
includes active and
passive modes.
If this parameter is set
to Active, the port can
initiate an OAM
connection. If this
parameter is set to
Passive, the port can
only respond to the
OAM connection
requests from the
opposite end.
Link Event Enabled Enabled Specifies whether the

Notification 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
choose 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

PORT1 Ethernet 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, 2 Specifies the threshold of monitoring

Monitor in step of 1 error frames.
Threshold(frame
s)
Error Frame 1488 to GE port: 1488000 Within the specified value of Error
Period 89280000, in step FE port: 148800 Frame Period Window (frames), if
Window(frames of 1 the 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

Period step of 1 the error frame period.
Threshold(frame
s)

Error Frame 10 to 900, in step 60 If any error frame occurs in one

Second of 1 second, this second is called an error
Window(s) 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 2 Specifies the threshold of monitoring

Second of 1 error 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

the remote Ethernet
port.
Remote OAM - - Displays the working

Working Mode mode of the remote
Ethernet port.
Link Event - - Displays whether the

Notification remote Ethernet port
can notify link events
to the local port.
Remote Side - - Displays how the

Loopback Response remote Ethernet port
responds to a
loopback.

Field Value Range Default Value Description
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
choose Configuration > QoS Management > Flow Management from the
Function Tree.
2. Click the Flow Configuration tab.
3. Click New.


Flow Type Port Flow Port Flow ● Port flow: The packets from a
Port+VLAN Flow certain port are classified as a type
of flow. The Ethernet service
Port+SVLAN Flow associated with this flow type is
Port+CVLAN the line service or Layer 2
+SVLAN Flow switching service that uses this
Port+VLAN port as the service source.
+Priority Flow ● Port+VLAN flow: The packets that
are from a certain port and have a
specified VLAN ID are classified as
a type of flow. The associated
Ethernet service of this flow type
is the EVPL service (based on
VLAN) or EVPLAN service (based
on the 802.1q bridge) that uses
this PORT+VLAN as the service
source.
● 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.
● 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.
● 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 ● When the associated service is the

PORT9, line service, set this parameter to
VCTRUNK1 to the source port or sink port of the
VCTRUNK16 associated Ethernet service.
EMS6: PORT1 to ● When the associated service is the
PORT7, Layer 2 switching service, set this
VCTRUNK1 to parameter to a mounted port of
VCTRUNK8 the bridge.
VLAN ID 1 to 4095 1 ● This parameter is valid only when

Flow Type is set to Port+VLAN
Flow or Port+VLAN+Priority
Flow.
● Set this parameter to the source
VLAN of the associated Ethernet
service.
C-VLAN 1 to 4095 1 ● This parameter is valid only when

Flow Type is set to Port+CVLAN
+SVLAN Flow.
● Set this parameter to the source C-
service.
S-VLAN 1 to 4095 1 ● This parameter is valid only when

Flow Type is set to Port+SVLAN
Flow or Port+SVLAN+CVLAN
Flow.
● Set this parameter to the source S-
service.
Priority - - ● This parameter is valid only when

Flow Type is PORT+VLAN
+Priority Flow.
● 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
Configuration > 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/ Enabled Disabled Indicates whether to enable the CAR

Disabled Disabled operation performed on the flow
bound to the CAR.
Committed EFP8: 0 to 0 ● Indicates the CIR. When the rate

information Rate 100032, in steps of a packet is not more than the
(kbit/s) of 64 CIR, this packet passes the
EMS6 (FE ports): restriction of the CAR and is
0 to 102400, in forwarded first even in the case of
steps of 64 network congestion.
EMS6 (GE ports): ● The value of this parameter
0 to 1024000, in should not 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 0 ● Indicates the PIR. When the rate

Rate (kbit/s) 100032, in steps of a packet is more than the PIR,
of 64 the packet that exceeds the rate
EMS6 (FE ports): restriction is directly discarded.
0 to 102400, in When the rate of packets is more
steps of 64 than the CIR but is lower than or
equal to the PIR, these packets
EMS6 (GE ports): whose rate exceeds the CIR can
0 to 1024000, in pass the restriction of the CAR and
steps of 64 are marked yellow.
● 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
Size (kbyte) EMS6: 0 to 16384 the packet that passes the restriction
of the CAR is more than the CIR but
is not more than the PIR, some
packets can burst and are marked
yellow. The maximum traffic of the
burst packets is determined by the
MBS. Note that the MBS has an
inherent size, and this parameter
indicates the increment value only.
The inherent size of the MBS is
determined by the PIR. The greater
the PIR, the greater the MBS.
B.7.4.3 Parameter Description: QoS Management_Creation of CoS

This section describes the parameters for creating CoS.
Navigation Path
choose Configuration > QoS Management > Flow Management from the
Function Tree.
3. Click New.


CoS ID EFP8: 1-64 1 This parameter identifies a CoS

EMS6: 1-1054 operation, and is used to bind a flow
to an associated CoS operation.
CoS Type simple simple ● If the CoS type of a flow is set to

VLAN Priority simple, all the packets in this flow
are directly scheduled to a
IPTOS specified egress queue.
DSCP ● 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.
● 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.
● 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.
● 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.
● 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.
● 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
Configuration > 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 - - ● Displays the C-VLAN.

● This parameter is valid is Flow
Type is Port+VLAN Flow, Port
+CVLAN+SVLAN Flow, or Port
+VLAN+Priority Flow.
S-VLAN - - ● Displays the S-VLAN.

● This parameter is valid when Flow
Type is Port+SVLAN Flow or Port
+CVLAN+SVLAN Flow.
Priority - - ● Displays the priority of the flow.

● 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
Click the Port Queue Information tab.


Port Queue - - Displays the queue name.
Status Enabled Disabled Indicates whether to enable the

Disabled traffic shaping feature of an egress
queue.
CIR (kbit/s) EFP8: 0 to 0 ● When the rate of a packet is not

100032, in steps more than the CIR, this packet
of 64 directly enters the egress queue.
EMS6 (FE ports): ● The value of this parameter should
0 to 102400, in not be more than the PIR.
steps of 64
EMS6 (GE ports):
0 to 1024000, in
steps of 64
DCBS (kbyte) - 0 Displays the excess burst size.
PIR (kbit/s) EFP8: 0 to 0 ● When the rate of a packet is more

100032, in steps than the PIR, the packet that
of 64 exceeds the rate restriction is
EMS6 (FE ports): directly discarded. When the rate
0 to 102400, in of packets is more than the CIR
steps of 64 but not more than the PIR, the
packets that exceed the restriction
EMS6 (GE ports): of the CIR enter the buffer of the
0 to 1024000, in CIR. When the buffer overflows,
steps of 64 the packets are marked yellow and
enter the egress queue, which
enables the packets to be
discarded first in the case of queue
congestion.
● The value of this parameter should
not be more than the port
bandwidth.
DMBS (kbyte) - 0 Displays the maximum excess burst

size.

Scheduling SP Queue 1: WRR By default, queue 8 (with the CoS

Mode WRR Queue 2: WRR priority of 7) of the EMS6 board is
the SP queue, and queues 1-7 (with
Queue 3: WRR the respective CoS priority of 0-6) are
Queue 4: WRR the WRR queues and their weights
Queue 5: WRR are in the proportion of
1:2:8:16:32:64.
Queue 6: WRR
The scheduling principles of the SP
Queue 7: WRR +WRR are as follows:
Queue 8: SP ● A port immediately transmits the
packets in the SP queue and can
transmit the packets in the WRR
queue only when no packets exist
in the SP queue.
● 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).
● 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 Queue 1: 1 By default, queue 8 (with the CoS

ranging from 1 to Queue 2: 2 priority of 7) of the EMS6 board is
64 the SP queue, and queues 1-7 (with
Queue 3: 4 the respective CoS priority of 0-6) are
Queue 4: 8 the WRR queues and their weights
Queue 5: 16 are 1:2:4:8:16:32:64.
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

Disabled enable the traffic shaping at a port.
PIR (kbit/s) EMS6 (FE ports): 0 In the case of an EMS6 board, the PIR
0 to 102400, in of a port meets the following
steps of 64 constraints:
EMS6 (GE ports): ● The PIR of the port is equal to or
0 to 1024000, in more than the PIR of any queue at
steps of 64 this port.
● The PIR of the port is equal to or
more than the sum of the CIRs of
all the queues at this port.
B.7.5 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the EoS/EoPDH
plane.
B.7.5.1 Parameter Description: Ethernet Port_External Port

This section describes the parameters for Ethernet external ports.
Navigation Path
1. In the NE Explorer, select the EFP8/EMS6 board and then choose
Configuration > Ethernet Interface Management > Ethernet Interface
2. Select External Port.

Table B-70 Parameters for the basic attributes
Port - - Displays the name of the external

port.
Name - - Displays or specifies the name of the

external port.
Enabled/ Enabled Disabled ● If the port gains access to services,

Disabled Disabled set this parameter to Enabled.
Otherwise, set this parameter to
Disabled.
● 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.
on an EMS6 board.
Working Mode EFP8: Auto-Negotiation ● Different types of Ethernet ports

● Auto- support different working modes.
Negotiation ● If the opposite port works in auto-
● 10M Half- negotiation mode, set this
Duplex parameter to Auto-Negotiation.
● 10M Full- ● If the opposite port works in full-
Duplex duplex mode, set this parameter
to 10M Full-Duplex or 100M
● 100M Half-
Full-Duplex, depending on the
Duplex
rate of the opposite port.
● 100M Full-
Duplex ● If the opposite port works in half-
duplex mode, set this parameter
EMS6: to 10M Half-Duplex or 100M
● Auto- Half-Duplex, depending on the
Negotiation rate of the opposite port, or set
● 10M Half- this parameter to Auto-
Duplex Negotiation.
● 10M Full- ● GE optical ports on an EMS6

Duplex board support only Auto-
Negotiation and 1000M Full-
● 100M Half- Duplex modes.
Duplex
NOTE
● 100M Full- This parameter is invalid for PORT9 on an
Duplex EFP8 board.
● 1000M Full- This parameter is invalid for PORT7 on an
Duplex EMS6 board.

Maximum EFP8: 1518 to 1522 ● Set this parameter to a value

Frame Length 2000 greater than the maximum length
(bytes) EMS6: 1518 to of all the data frames to be
9600 transmitted.
● 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

Parameters a PORT.
on an EFP8 board.
on an EMS6 board.
MAC Loopback Non-Loopback Non-Loopback ● A MAC loopback is to loop back

Loopback the Ethernet frames transmitted to
the opposite port.
● Use the default value unless
otherwise specified.
PHY Loopback Non-Loopback Non-Loopback ● A PHY loopback is to loop back

Loopback the Ethernet physical signals
transmitted to the opposite port.
● Use the default value unless
on an EFP8 board.
on an EMS6 board.
Table B-71 Parameters for flow control


port.

Non- Disabled Disabled ● This parameter is valid only when

Autonegotiation Enable Working Mode is not set to Auto-
Flow Control Symmetric Flow Negotiation.
Mode Control Mode ● If this parameter is set to Enable
Send Only Symmetric Flow Control Mode,
the port can send PAUSE frames
Receive Only and process the received PAUSE
frames.
● 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.
● 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.
● Set this parameter to the same as
the non-autonegotiation flow
control mode of the opposite port.

Autonegotiation Disabled Disabled ● This parameter is valid only when

Flow Control Enable Working Mode is Auto-
Mode Dissymmetric Negotiation.
Flow Control ● If this parameter is set to Enable
Enable Symmetric Control, the port can
Symmetric send PAUSE frames and process
Control the received PAUSE frames.
Enable ● If this parameter is set to Enable
Symmetric/ Dissymmetric Flow Control, the
Dissymmetric port can send PAUSE frames in the
Flow Control case of congestion but cannot
process the received PAUSE
frames.
● 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.
the autonegotiation flow control
mode of the opposite port.
on an EFP8 board.
on an EMS6 board.
Table B-72 Parameters for the tag attributes


port.

TAG Tag Aware Tag Aware ● With different tag attributes, the
Access port processes frames in different
modes. For details, see Table B-75.
Hybrid
● Set this parameter to Tag Aware if
the port processes the frames with
VLAN tags (or tagged frames).
● Set this parameter to Access if the
port processes the frames without
VLAN tags (or untagged frames).
● Set this parameter to Hybrid if the
port processes the tagged frames
and untagged frames.
Default VLAN ID 1-4095 1 ● This parameter is valid only when

● For the usage of this parameter,
see Table B-75.
VLAN Priority 0-7 0 ● This parameter is valid only when

● For the usage of this parameter,
see Table B-75.
● 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 ● Indicates whether to check the

Disabled incoming packets according to the
tag attribute.
Table B-73 Parameters for the network attributes


port.

Port Attributes UNI UNI ● If this parameter is set to UNI, the

C-Aware port processes data frames
according to the tag attribute.
S-Aware
● If this parameter is set to C-
Awareor S-Aware, the port
processes the data frames by using
the processing method of QinQ
services.
● Set this parameter to C-Aware or
S-Aware when the port processes
QinQ services. Otherwise, this
Table B-74 Parameters for the advanced attributes


port.
Broadcast Disabled Disabled This parameter specifies whether to

Packet Enabled restrict the traffic of broadcast
Suppression 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 10%-100% 30% When the proportion of the received

Packet broadcast packets to the total
Suppression packets crosses the threshold, the
Threshold 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 EFP8: - Specifies the traffic threshold of the

Threshold ● 0 to 100 port. You can specify the traffic
(Mbit/s) (PORT1 to monitoring period by setting Port
PORT8) Traffic Threshold Time
Window(Min).
● 0 to 1000
(PORT9)
EMS6:
● 0 to 1000
(PORT1 and
PORT2)
● 0 to 100
(PORT3 to
PORT6)
● 0 to 1000
(PORT7)
Port Traffic 0-30 0 Specifies the traffic monitoring

Threshold Time period.
Window(Min) ● If Port Traffic Threshold Time
Window(Min) is set to 0, an
associated alarm is reported at the
moment when the traffic received
at the port crosses the value of
Traffic Threshold(Mbit/s).
● 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

Disabled enable loop detection, which is used
to check whether a loop exists on the
port.
Table B-75 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 Discards the Receives the
frame. frame. frame.


Frame
Untagged frame Discards the The port receives The port receives
frame. the frame after the frame after
adding to the adding to the
frame the VLAN frame the VLAN
tag that contains tag that contains
Default VLAN ID Default VLAN ID
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the The port strips ● If the VLAN ID
frame. the VLAN tag in the frame is
from the frame Default VLAN
and then ID, the port
frame. VLAN tag
from the
frame and
then transmits
the frame.
● 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
2. Select Internal Port.

Table B-76 Parameters for the tag attributes

Value
Port - - Displays the name of the

internal port.
Name - - Sets the name of the internal

port.
TAG Tag Aware Tag Aware ● With different tag

Access attributes, the port
processes frames in
Hybrid different modes. For
details, see Table B-81.
● Set this parameter to Tag
Aware if the port processes
the frames with VLAN tags
(or tagged frames).
● Set this parameter to
Access if the port processes
the frames without VLAN
tags (or untagged frames).
● Set this parameter to
Hybrid if the port
processes the tagged
frames and untagged
frames.
Default VLAN ID 1-4095 1 ● This parameter is valid only

when TAG is set to Access
or Hybrid.
● For the usage of this
parameter, see Table B-81.
● Set this parameter as
required.


Value
VLAN Priority 0-7 0 ● This parameter is valid only

when TAG is set to Access
or Hybrid.
● For the usage of this
parameter, refer to Table
B-81.
● When the VLAN priority is
required for traffic
classification or other
purposes, set this
parameter as required. The
default value is
recommended unless
Entry Detection Enabled Enabled ● Indicates whether to check

Disabled the incoming packets
according to the tag
attribute.
● Set this parameter as
required.
Table B-77 Parameters for encapsulation or mapping

Port - - Displays the name of the internal

port.
Mapping GFP GFP The default value is recommended.

Protocol HDLC The EFP8 board supports GFP only.
LAPS
Scramble Scrambling Mode Scrambling ● Indicates the scrambling

[X43+1] Mode[X43+1] polynomial used by the mapping
Scrambling Mode protocol.
[X48+1] ● The default value is
Unscrambled recommended.

Set Inverse - - ● This parameter indicates whether

Value for CRC the 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.
● Set Set Inverse Value for CRC to
the same value for the VCTRUNKs
at both ends.
Check Field FCS32 FCS32 ● When the Ethernet board uses the
Length No GFP mapping protocol, set this
parameter to FCS32 or No.
● When you set this parameter to
FCS32, a 32-bit FCS is used.
recommended.
FCS Calculated Big endian Big endian ● When you set this parameter to
Bit Sequence Little endian Big endian, the least significant
byte of the FCS is placed first and
the most significant byte is placed
last.
Little endian, the most significant
byte of the FCS is placed first and
the least significant byte is placed
last.
recommended.
Table B-78 Parameters for the network attributes


port.

Port Attributes UNI UNI ● If this parameter is set to UNI, the

C-Aware port processes data frames
according to the tag attribute.
S-Aware
● 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.
● Set this parameter to C-Aware or
S-Aware when the port processes
QinQ services. Otherwise, this
Table B-79 Parameters for the LCAS


port.
Enabling LCAS Disabled Disabled ● Indicates whether to enable the

Enabled LCAS function.
● 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 ● Indicates the sequence in which
Standard Mode the LCAS sink sends the MST
control packet and Rs-Ack control
packet.
Huawei Mode, the LCAS sink first
sends the Rs-Ack and then sends
the MST.
Standard Mode, the LCAS sink
first sends the MST and then sends
the Rs-Ack.
● 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 An integer 2000 ● When a member link is faulty, the

Time(ms) ranging from 0, LCAS performs switching after a
2000 to 10000, in delay of time to prevent the
the increments of situation where an NE
100 simultaneously performs a
protection switching such as SNCP
and performs an LCAS switching.
duration of the delay.
recommended.
WTR Time(s) 0-720 300 ● 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.
recommended.
TSD Disabled Disabled ● Indicates whether the TSD is used

Enabled as a condition for determining
whether a member link is faulty. In
the case of the VC-12, the TSD
refers to the BIP_SD. In the case of
the VC-3, the TSD refers to the
B3_SD_VC3.
recommended.
Table B-80 Parameters for bound path

Range Value
VCTRUNK Port EFP8: VCTRUNK1 Specifies the VCTRUNK

VCTRUNK1 to bind paths.
-
VCTRUNK1
6
EMS6:
VCTRUNK1
-
VCTRUNK8


Range Value
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 Bidirection Bidirection ● Specifies the direction

al al of the bound path.
Uplink ● Set this parameter to
Downlink Bidirectional unless
Bound Path - - You need to plan and set

this parameter according
to the following
principles:
● The capacity of the
VCTRUNK is
determined by the
actual bandwidth
required by the
services.
● 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.
● 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.
Used Channel - - Displays the number of

used VC paths.


Range Value
Activation Status - - Displays the activation

status of the bound VC
path.
Table B-81 Methods used by ports to process data frames

Frame
Ingress port Tagged frame Receives the Discards the Receives the
frame. frame. frame.
Untagged frame Discards the The port receives The port receives
frame. the frame after the frame after
adding to the adding to the
frame the VLAN frame the VLAN
tag that contains tag that contains
Default VLAN ID Default VLAN ID
and VLAN and VLAN
Priority. Priority.
Egress port Tagged frame Transmits the The port strips ● If the VLAN ID
frame. the VLAN tag in the frame is
from the frame Default VLAN
and then ID, the port
frame. VLAN tag
from the
frame and
then transmits
the frame.
● 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

Area(Hexadecim 88 A8 frames. Set this parameter according
al) to the type field of the accessed QinQ
91 00 frames.
0600 to FFFF
B.8 Parameters for MPLS/PWE3 Services

This topic describes parameters that are related to MPLS/PWE3 services.
NOTE
For parameters for PW-carried E-Line services, see B.6 Parameters for Ethernet Services
and Ethernet Features on the Packet Plane.
B.8.1 MPLS Tunnel Parameters

This topic describes parameters that are related to MPLS tunnels.
B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels

This topic describes parameters that are related to the basic configurations of
MPLS tunnels.
Navigation Path
Tree.


LSR ID - 0.0.0.0 ● Specifies or

displays the LSR
ID of an NE. On
a PSN, each NE
is assigned a
unique LSR ID.
● This parameter
must be set in
IPv4 address
format.
Start of Global Label Space 0-1015808 0 ● Specifies the

start value of a
global label
space. The OptiX
RTN 900
supports a step
of 2048.
● 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.
● On an MPLS-
enabled
network, global
label spaces of
NEs are
recommended to
overlap each
other if possible.
Global Label Space Size - - Displays the size of

a global label
space.
Start of Multicast Label - - The OptiX RTN 900

Space 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 > MPLS Management > Basic Configuration from the
Function Tree.
2. Click the Global OAM Parameters tab.
Parameters in the window for setting global OAM parameters

Default OAM - - Displays the default

Recommendation OAM standard. The
default OAM
standard is Y.1711.
Carrier ID - - ● Set Carrier ID

according to the
network plan if
MPLS-TP OAM
uses the ICC-
based format.
● 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 ● Specifies the

channel type in
an MPLS-TP
OAM packet.
● Set Channel
Type to the
same value for
all NEs on a
network.
● NEs can receive
OAM packets
from a channel
of the 8902 type
regardless of the
value of this
parameter.
● 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 Enabled Enabled -

Status 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.

the 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 - - ● Displays the node

type.
● For bidirectional
tunnels, this
parameter displays
the node types of
forward tunnels.

of a tunnel.
CIR(kbit/s) No Limit - ● Specifies or displays

1024-1024000 the committed
information rate
(CIR) of a tunnel.
recommended that
you set this
parameter to No
Limit. If you need
to enable the CES
CAC function or
limit the PW
bandwidth, set this
parameter to be
the same as the
planned tunnel
bandwidth.
PIR(kbit/s) - - The OptiX RTN 900

parameter.
CBS(byte) - - The OptiX RTN 900

parameter.

PBS(byte) - - The OptiX RTN 900

parameter.
Bandwidth - - The OptiX RTN 900

Remaining(kbit/s) does 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 - - Specifies the MPLS

Label 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 - - Displays the MPLS

Label label that a reverse
tunnel carries when
leaving a node.
Forward Next Hop - - Displays the IP address

Address of the next-hop port
of a forward tunnel.
Reverse Next Hop - - Displays the IP address

Address of 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 - ● Specifies or displays

None the value of the
EXP field in the
packets transmitted
through MPLS
tunnels.
● For unidirectional
tunnels, this
parameter is
available only if
Node Type is
Ingress.
tunnels, this
parameter cannot
be set if Node Type
is Transit.
set to a value from
0 to 7, the EXP field
takes its fixed
value.
takes its default
value None, the
EXP field varies
based on the
DiffServ mappings.

LSP Mode Pipe - ● Displays or specifies

the LSP mode.
● Pipe: When
stripping MPLS
tunnel labels from
packets, an egress
node does not
update the
scheduling priority
for the packets.
tunnels, this
parameter is
available only if
Node Type is
Egress.
tunnels, this
parameter 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

parameter.
Protection Group - - Displays the MPLS APS

protection group to
which a tunnel
belongs.

VLAN ID - - ● Specifies or displays

the VLAN ID that
Ethernet packets
carry when
transmitted over
MPLS tunnels.
● 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.
to the same value
for both ends of a
tunnel.

CoS CS7 - ● This parameter

CS6 specifies the PHB
service class of an
EF L-LSP, if the type of
AF4 an MPLS tunnel is
AF3 L-LSP.
AF2 ● CS6-CS7: indicates
the highest service
AF1 grade, which is
BE 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.
● 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.
the traffic is
forwarded in best-
effort manner
without special
processing.
Deployment - - Displays the

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
the 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 - ● Specifies the tunnel ID.

● 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 ● Specifies the committed

1024-1024 information rate (CIR) of a
000 tunnel.
this parameter to No
Limit. If you need to limit
the tunnel bandwidth, set
this parameter to be the
same as the planned
tunnel bandwidth.
CBS(kbit/s) - - The OptiX RTN 900 does not

support this parameter.


Range Value
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
In Port - - tunnel on a transit or egress
node.
NOTE
● If the MPLS port is an FE/GE
port, ensure that:
● 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.
● 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.
● If the MPLS port is an IF_ETH
port, ensure that:
● 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.
● 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-104857 - Specifies the MPLS label at

5 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


Range Value
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-104857 - Specifies the MPLS label at

5 the egress direction of a
forward tunnel on an ingress
or transit node.
Next Hop Address - - ● The Next Hop Address

parameter needs to be set
only for the egress port on
an ingress or transit node.
● 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 - - ● The Source Node

parameter needs to be set
only on an egress or transit
node.
● Set the LSR ID for the last
hop MPLS node to Source
Node according to the
network plan.
Sink Node - - ● The Sink Node parameter

needs to be set only on an
ingress or transit node.
● Set the LSR ID for the next
hop MPLS node to Sink
Node according to the
network plan.


Range Value
Tunnel Type E-LSP E-LSP ● Specifies the tunnel type.

L-LSP ● 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.
● The value L-LSP indicates
that the MPLS label value
is used to identify packet
scheduling priorities of
PWs. An L-LSP tunnel can
contain PWs of the same
packet scheduling priority.
EXP 0-7 None ● Specifies the value of the

None EXP field in the packets
transmitted through MPLS
tunnels.
● This parameter is available
only if Node Type is
Ingress.
● If this parameter is set to a
value from 0 to 7, the EXP
field takes its fixed value.
● If this parameter takes its
default value None, the
EXP field is set based on
the DiffServ mappings.
LSP Mode Pipe Pipe ● Pipe: When stripping MPLS

tunnel labels from packets,
an egress node does not
priority for the packets.
● 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 ● This parameter specifies

CS6 the PHB service class of an
L-LSP, if the type of an
EF MPLS tunnel is L-LSP.
AF4 ● CS6-CS7: indicates the
AF3 highest service grade,
AF2 which is mainly involved in
signaling transmission.
AF1
BE forwarding. This service
class is applicable to the
traffic whose delay is small
and packet loss ratio is low,
for example, voice and
video services.
● 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.
● 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
the Function Tree.
3. Click New and choose Bidirectional Tunnel from the drop-down list.


Tunnel ID 1 to 65535 - ● Specifies the tunnel ID.

● 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

Egress forward tunnel.
Transit
Direction - - Indicates the direction of a tunnel.
CIR(kbit/s) No Limit No Limit ● Specifies the committed

1024-1024000 information rate (CIR) of a
tunnel.
● 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

PIR(Byte) - - The OptiX RTN 900 does not

PBS(Byte) - - The OptiX RTN 900 does not

In Board/Logic - - Specifies the MPLS port at the

Interface Type ingress direction of a forward
tunnel on a transit or egress node.

In Port - - NOTE
● If the MPLS port is an FE/GE port,
ensure that:
● 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.
● 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.
● If the MPLS port is an IF_ETH
port, ensure that:
● 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.
● 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 - ● Specifies the MPLS label at the

egress direction of a reverse
tunnel on a transit or egress
node.
● 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

Interface Type egress direction of a forward
tunnel on an ingress or transit
Out Port - - 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.

Forward Out Label 16 to 1048575 - Specifies the MPLS label at the

egress direction of a forward
node.
Reverse In Label 16 to 1048575 - ● Specifies the MPLS label at the

ingress direction of a reverse
node.
● The Reverse In Label and
Forward Out Label
parameters can be set to either
the same value or different
values.
Forward Next Hop - - ● The Forward Next Hop

Address Address parameter needs to be
set only for the egress port on
an ingress or transit node.
● Set the IP address of the MPLS
ingress port on the next hop
LSR node to Forward Next
Hop Address according to the
network plan.
Reverse Next Hop - - ● The Reverse Next Hop

Address Address parameter needs to be
set only for the ingress port on
a transit or egress node.
● Set the IP address of the MPLS
ingress port on the next hop
LSR node to Reverse Next Hop
Address according to the
network plan.
Source Node - - ● The Source Node parameter

egress or transit node.
● Set the LSR ID for the last hop
MPLS node to Source Node
Sink Node - - ● The Sink Node parameter

ingress or transit node.
● Set the LSR ID for the next hop
MPLS node to Sink Node

Tunnel Type E-LSP E-LSP ● Specifies the tunnel type.

L-LSP ● 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
● 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 ● Specifies the value of the EXP

None field in the packets transmitted
through MPLS tunnels.
● This parameter cannot be set if
Node Type is Transit.
● If this parameter is set to a
value from 0 to 7, the EXP field
takes its fixed value.
● If this parameter takes its
default value None, the EXP
field is set based on the
DiffServ mappings.
LSP Mode Pipe Pipe ● Pipe: When stripping MPLS

tunnel labels from packets, an
egress node does not update
the scheduling priority for the
packets.
● 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


CoS CS7 BE ● This parameter specifies the

CS6 PHB service class of an L-LSP, if
the type of an MPLS tunnel is
EF L-LSP.
AF4 ● CS6-CS7: indicates the highest
AF3 service grade, which is mainly
AF2 involved in signaling
transmission.
AF1
● 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.
● 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.
● 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
the Function Tree.

Tunnel ID - - Displays the tunnel ID.
Tunnel Name - - Displays the tunnel

name.

Node Type - - ● Displays the node

type.
tunnels, this
parameter displays
the node types of
forward tunnels.
Tunnel Direction - - Displays the direction

of a tunnel.
OAM Status Enabled Disabled ● Specifies or displays

Disabled whether the local
node can perform
and respond to
OAM operations.
● If OAM Status is
Enabled, the local
NE can perform
and respond to
OAM operations.
Disabled, the local
NE cannot perform
and respond to
OAM operations.
● 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 ● Specifies or displays

Manual the MPLS OAM
detection mode.
● Manual: During a
CC test, MPLS OAM
packets are sent at
the interval
specified by the
user.
● Adaptive: During a
CC test, MPLS OAM
packets are sent at
the interval for
receiving MPLS
OAM packets.
● For a unidirectional
tunnel, this
parameter can be
set for its egress
node only.
● For a bidirectional
tunnel, if Detection
Mode is set to
Manual, you need
to set the MPLS
OAM detection
packets to be
received and
transmitted.
● Generally, the value
Adaptive is
recommended.


a fixed interval.
packets are sent at
the interval
specified by the
user.
● 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
packets to be
received and
transmitted.
assumed for MPLS
APS and the value
CV is assumed for
continuous
connectivity check
on MPLS tunnels.

Packet Detection 3.3 50 ● Displays or

Interval(ms) 10 specifies the OAM
detection period.
20
50 available only when
200 Type is FFD. It
takes its fixed value
500 of 1000 ms when
Detection Packet
Type is CV.
to 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 - - ● Specifies the

mapping reverse
tunnel of a forward
tunnel.
tunnel, this
parameter cannot
be set.
CV/FFD Status - - Displays whether

CV/FFD is enabled.
Local LSP Status - - Displays whether an

LSP is available.
Local LSP Defect - - Displays the LSP

Type defect type.
Local Disable LSP - - Displays the duration

Duration(ms) when an LSP is
unavailable.
Local LSP Defect - - Displays the LSR ID of

Location a node where LSP
defects are detected.

Remote LSP Defect - - Displays whether an

Type LSP is available.
Remote LSP Defect - - Displays the LSP

Type defect type.
Remote Disable LSP - - Displays the duration

Duration(ms) when an LSP is
unavailable.
Remote LSP Defect - - Displays the LSR ID of

Location a node where LSP
defects are detected.
SD Threshold(%) 0-100 0 ● Specifies or displays

the SD threshold.
When the OAM
packet loss ratio is
higher than the
parameter value,
the corresponding
alarm is reported.
tunnel, this
parameter can be
set for its egress
node only.
● When this
parameter is set to
0, SD threshold
detection is not
supported.

SF Threshold(%) 0-100 0 ● Specifies or displays

the SF threshold.
When the OAM
higher than the
parameter value,
the corresponding
alarm is reported.
tunnel, this
parameter can be
set for its egress
node only.
● When this
parameter is set to
0, SF threshold
detection is not
supported.
● 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
the Function Tree.
2. Click the FDI tab.


Enable FDI Selected Selected ● Specifies or displays

Not selected whether Enable
FDI is selected.
● 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.
● 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
the 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 ● Specifies the EXP

value of the MPLS
label in test request
packets. The value
7 indicates the
highest priority.
recommended.
TTL 1 to 255 255 ● Specifies the time-

to-live (TTL) value
of the MPLS label
in test request
packets.
recommended.
Transmit 1 to 1000 100 ● Specifies the

Interval(10ms) interval for
transmitting test
request packets.
recommended.
Packet Length 64 to 1400 64 ● Specifies the length

of test request
packets.
recommended.
Response Timeout 1 to 6000 300 ● Specifies the wait-

Period(10ms) to-response
timeout value.
recommended.

Response Mode IPv4 UDP Response IPv4 UDP Response ● Specifies the
No Response response mode of
test request
Application Control packets.
Channel Response
● The value No
Response indicates
that the test
performance event
is reported without
sending response
packets.
● The value
Application
Control Channel
Response indicates
that response is
performed through
the reverse
channel.
● The value IPv4
UDP Response
indicates that the
IPv4 UDP packets
encapsulating
MPLS echo reply
messages are sent
as response
packets.
● The value IPv4
UDP Response is
reserved for
scenarios where all
nodes on an LSP
communicate with
each other over a
DCN running IP
protocols.
based on the
situation of the
egress node. If the
egress node
supports reverse
channel response,
set this parameter
to Application
Control Channel
Response. If the
egress node does

not support reverse

channel response
but supports DCN
channel response
by means of IP
protocols, set this
parameter to IPv4
UDP Response.
NOTE
For a unidirectional
tunnel, Response
Mode cannot be set
to 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
the Function Tree.
2. Click the OAM Parameters tab.
3. Select the required tunnel, click OAM Operation in the lower right corner,
and choose Traceroute Test from the drop-down list.


value of the MPLS
packets. The value
7 indicates the
highest priority.
recommended.


to-live (TTL) value
of the MPLS label
in test request
packets.
recommended.

of test request
packets.
recommended.

timeout value.
recommended.

test request
Channel Response
● The value No
Response indicates
that the test
performance event
is reported without
sending response
packets.
● The value
Application
Control Channel
Response indicates
that response is
performed through
the reverse
channel.
● The value IPv4
UDP Response
indicates that the
IPv4 UDP packets
encapsulating
MPLS echo reply
messages are sent
as response
packets.
● The value IPv4
UDP Response is
reserved for
scenarios where all
nodes on an LSP
communicate with
each other over a
DCN running IP
protocols.
based on the
situation of the
egress node. If the
egress node
supports reverse
channel response,
set this parameter
to Application
Control Channel
Response. If the
egress node does

not support reverse

channel response
but supports DCN
channel response
by means of IP
protocols, set this
parameter to IPv4
UDP Response.
NOTE
For a unidirectional
tunnel, Response
Mode cannot be set
to 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
the Function Tree.
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 ● When all NEs

ICC Based connected to an
MPLS tunnel are
Customer Based Huawei devices that
supports I-based
MPLS-TP OAM
components, it is
recommended that
you set MEG ID
Type to IP Based.
In this case, you do
not need to
configure MEG ID,
MP ID, RMEP ID, or
MIP.
● If some MPLS-TP
tunnel OAM
components cannot
be set to IP Based
or have special
requirements, it is
recommended that
you set MEG ID
Type to ICC Based.
● For interconnection
with non-Huawei
devices, you can set
this parameter to
Customer Based.
MEG ID - - ● You need to set

MEG ID when MEG
ID Type is not IP
Based.
● Set MEG ID to the
same value for
nodes connected to
the same MPLS
tunnel.
● 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
RMEP ID 1 to 8191 - same value as RMEP
ID at the sink end.
Detection Mode Adaptive Adaptive ● Manual: tests

Manual whether a tunnel is
available based on
the user-defined
CCM transmission
interval.
● Adaptive: tests
whether a tunnel is
available based on
the interval at
which CCMs have
been received.
that you set this
parameter to
Adaptive.
● 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 ● It is recommended

that you set CC
Packet Priority to 7
to ensure that CC
packets are
forwarded with
priority.
● CC Packet Priority
cannot be specified
for the egress node
of a unidirectional
tunnel.

CC Packet Interval 3.3 1000 ● If the MPLS-TP

(ms) 10 OAM CC function is
used for only
100 continuity check, it
1000 is recommended
that you set CC
Packet Interval
(ms) to the default
value 1000.
● 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
tunnel exceeds 3.3
ms, set the
transmission
interval of CCMs to
a value greater
than the frame
delay variation.
● CC Packet Interval
(ms) cannot be
specified for the
egress node of a
unidirectional
tunnel.
AIS Status Disabled Disabled ● 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.
● AIS Status cannot
be specified for a
unidirectional
tunnel.

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 - - Indicates the type of

Type 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

Type the LSP defect at the
opposite end.
Remote LSP Disabled - - Displays the duration

Duration (ms) when the LSP at the
opposite end is
unavailable.
Remote LSP Defect - - Displays the LSR ID of

Location the node that has
detected the LSP
defect.

SD Threshold (%) 0 to 100 0 ● Displays or specifies

the SD threshold.
An alarm is
reported if the
OAM packet loss
ratio is larger than
the SD threshold.
tunnel, this
parameter can be
specified only for
the egress node.
set to 0, SD
threshold detection
is not supported.
SF Threshold (%) 0 to 100 0 ● Displays or specifies

the SF threshold. An
alarm is reported if
the OAM packet
loss ratio is larger
than the SF
threshold.
tunnel, this
parameter can be
specified only for
the egress node.
set 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
the Function Tree.
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 ● It is recommended

Customer Based that you set MEG
ID Type to ICC
Based.
with non-Huawei
this parameter to
Customer Based.
MEG ID - - ● Set MEG ID to the

same value for
nodes connected to
the same MPLS
tunnel.
● 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
the Function Tree.
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
Local MEP ID - - MEG 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 - - ● Set Remote

or IP Address MEP/MIP ID or IP
Address according
to the termination
node of an LB 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.
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 ● Specifies the

number of packets
that can be
transmitted each
time.
that this parameter
take its default
value.
Packet Priority 0 to 7 7 ● Specifies the packet

priority.
that this parameter
take its default
value.
TTL 1 to 255 355 ● If Node Type is

MIP, set TTL to the
number of hops
between the source
MEP and the
current MIP.
● 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 ● Specifies the packet

1s transmission
interval.
10s
that this parameter
take its default
value.

Packet length 128 to 1410 128 ● Specifies the packet

length.
that this parameter
take its default
value.
B.8.1.13 Parameter Description: PW Management_PW Management

This topic describes parameters that are related to PW management.
Navigation Path
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 - - Displays the PW signaling type.

Signaling NOTE
Type The RTN 900 uses only static PWs.

PW Type - - ● Displays the PW type. Different PW

types perform different service
processing modes.
● When a PW transmits E-Line
services, set PW Type to Ethernet
or Ethernet Tagged Mode.
● If a PW transmits circuit emulation
services (CESs), set PW Type to
CESoPSN or SATop.
● 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 - - Displays the direction of a PW.

Direction
PW - - Displays the ingress label at the source

Incoming port of a PW.
Label
PW - - Displays the encapsulation type of the

Encapsulatio packets on a PW.
n Type NOTE
The RTN 900 supports only MPLS
encapsulation.
PW - - Displays the egress label at the sink

Outgoing port of a PW.
Label
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

Operating at the local end.
Status
Remote - - Displays the working status of the PW

Operating at the remote end.
Status
Overall - - Displays the working status of the

Operating entire 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

Tunnel carries a PW.
Egress - -
Tunnel
Deployment - - Displays the deployment status of a

Status PW.
Tunnel - - The RTN 900 does not support this

Automatic parameter.
Selection
Policy
QoS Parameters
Table B-83 CES services

PW ID - - Displays the ID of the

PW that carries a
service.

of the PW that carries
a service.
CIR(kbit/s) - - The RTN 900 does not

support this
parameter.
EXP - - The RTN 900 does not

support this
parameter.
Table B-84 E-Line services


PW that carries a
service.


a service.
Bandwidth Limit - - Displays whether the

bandwidth is limited.
CIR(kbit/s) - - Displays the

committed
of a PW.
CBS(byte) - - Displays the

(CBS) of a PW.
PIR(kbit/s) - - Displays the peak

of a PW
PBS(byte) - - Displays the peak

PW.

support this
parameter.
LSP Mode - - Displays the LSP

mode.
NOTE
only Pipe.
Policy - - The RTN 900 does not

support this
parameter.
Table B-85 ATM services


PW that carries a
service.

a service.
Bandwidth Limit - - Displays whether the

bandwidth is limited.

CIR(kbit/s) - - Displays the

committed
of a PW.
CBS(byte) - - Displays the

(CBS) of a PW.
PIR(kbit/s) - - Displays the peak

of a PW
PBS(byte) - - Displays the peak

PW.

support this
parameter.
Policy - - The RTN 900 does not

support this
parameter.

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

Buffering Time(us) buffer time for the
received CES packets.
Ingress Clock Mode - - The RTN 900 does not

support this
parameter.
Egress Clock Mode - - The RTN 900 does not

support this
parameter.

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 - - Displays the threshold

Entering R bit of the packet loss ratio
Inserting Status of CES services. The
corresponding alarm
will be reported if the
actual packet loss
ratio crosses this
threshold.
Threshold of Exiting - - Displays the threshold

R bit Inserting Status of received CES service
packets. The
corresponding alarm
will 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 - - Displays the maximum

Cell 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
Tree.

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 ● Specifies the type of services carried
CES Service by the MS-PW.
ATM Service ● Set this parameter according to the
NOTE
OptiX RTN 905 does not support ATM
services.
Connection Port Transparent Port Transparent ● This parameter is available only

Type PVP when Service Type is ATM Service.
PVC ● PVP: Only the VPIs of the source
and sink are exchanged.
● PVP: The VPIs and VCIs of the
source and sink are exchanged.
● 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 that carries
services.
PW Signaling Type Static Static Specifies the signaling

type of the PW. Labels
for static PWs need to
be manually assigned.

PW Type - - ● Specifies the type

of the PW.
to 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.
● 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.
● 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 - - Displays the

the PW.

Ingress label.

PW Outging Label 16 to 1048575 - Specifies the PW

Egress label.
Tunnel Selection Manually Manually Specifies the method

Mode 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.

end. If an existing
LSR ID will be
automatically
assigned.

tunnel, the system will
configure the reverse
QoS Parameters
NOTE
OptiX RTN 905 does not support ATM services.
CES Services

support this
parameter.

Ethernet services

bandwidth limit
the bandwidth of
one or more PWs in
an MPLS tunnel.
● An ETH PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ETH
PWE3 services in an
MPLS tunnel.

not support this
parameter.

committed
of a PW.
It is recommended
that you set this
parameter to the
same value as PIR.

(CBS) of a PW.

of a PW.
It is recommended
that you set this
parameter to the
same value as CIR.

PW.

not support this
parameter.


MPLS tunnel labels
from packets, an
priority for the
packets.
ATM services


bandwidth limit is
enabled.
● 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.)
● An ATM PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ATM
PWE3 services in an
MPLS tunnel.

parameter.

CIR (Kbit/s) - - Specifies the

committed
of the PW.
It is recommended
that you set this
parameter to the
same value as PIR.
CBS (kbyte) - - Specifies the excess

burst size of the PW.

of the PW.
It is recommended
that you set this
parameter to the
same value as CIR.
PBS (kbyte) - - Specifies the

maximum excess burst
size of the PW.

parameter.
Parameters for the Advanced Attributes of PWs

NOTE
CES Services
RTP Header Disable Disable ● Specifies the RTP

Enable header.
● The RTP header
carries time
stamps.
recommended.

Jitter Compensation 375 to 16000 8000 ● Specifies the jitter

received CES
packets.
● 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 ● Specifies the length

Time(us) of fragments in the
TDM data stream.
Each fragment is
encapsulated into
one PW packet.
● A greater value of
this parameter
means higher
encapsulation
efficiency but
greater delays of
CES services.
recommended.
Ingress Clock mode - - The OptiX RTN 900

parameter.
Egress Clock mode - - The OptiX RTN 900

parameter.

Control Channel Type None CW ● Specifies the mode

CW of PW connectivity
check.
Alert Label
● The value None
indicates that the
control word is not
supported. That is,
the PW connectivity
check is not
supported.
● Alert Label
indicates VCCV
packets in Alert
Label encapsulation
mode.
● The value CW
indicates that the
control word is
supported.
VCCV Verification None Ping ● Specifies the VCCV

Mode Ping verification mode.
The VCCV
for PW connectivity
check.
not set this
parameter to
None.

64K Timeslot 1 to 31 1 ● Specifies the

Number 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.
● On the two ends of
a radio link, the
timeslot lists can be
different but the
numbers of
timeslots must be
the same.
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
encapsulating ETH


check.
CW
VCCV is not used.
● Alert Label
indicates VCCV
packets in Alert
Label
encapsulation
mode.
VCCV packets
encapsulated based
on the control word
are used.

The VCCV
for PW continuity
check.
not set this
parameter to None.

when PW Type is
Ethernet Tagged
Mode.
● 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.

ATM services
Control Word Must Use Must Use ● Specifies whether

No Use to use the control
word. In the MPLS
packet switching
network, the
control word is
used to transmit
packet information.
● Set Control Word
to Must Use if PW
Type is ATM 1:1.
Control Channel Type CW CW ● Specifies the mode

None of PW connectivity
check.
Alert Label
● The value None
indicates that the
control word is not
supported. That is,
the PW connectivity
check is not
supported.
● The value CW
indicates that the
control word is
supported.
● The value Alert
Label indicates
VCCV packets in
Alert Label
encapsulation
mode.

The VCCV
for PW connectivity
check.
not set this
parameter to None.

Max. Concatenated 1 to 31 10 ● Specifies the

Cell Count maximum number
of concatenated
cells.
● 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 ● 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.
● 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
Tree.
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 ● Specifies or displays

Disabled whether the local
node can perform
and respond to
OAM operations.
Enabled, the local
NE can perform
and respond to
OAM operations.
Disabled, the local
NE cannot perform
and respond to
OAM operations.
● 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

Status does not support this
parameter.

Detection Mode Adaptive Auto-Sensing ● Specifies or displays

Manual the detection mode
for PW OAM
packets.
● Manual: During a
CC test, PW OAM
packets are sent at
the interval
specified by the
user.
● Adaptive: During a
CC test, PW OAM
packets are sent at
the interval for
receiving PW OAM
packets.
is set to Manual,
you need to set the
type of PW OAM
detection packets
to be received and
transmitted.
● The value Adaptive
is recommended.


a fixed interval.
packets are sent at
the interval
specified by the
user.
is set to Adaptive,
this parameter
specifies the type
of PW OAM
detection packets
to be transmitted.
is set to Manual,
this parameter
specifies the type
of PW OAM
detection packets
to be received and
transmitted.
assumed for PW
APS and the value
CV is assumed for
continuous
connectivity check
on PWs.

Packet Detection 3.3 50 ● Displays or

Interval(ms) 10 specifies the OAM
detection period.
20
● If Detection
50 Packet Type is
100 FFD, this parameter
200 can be set; if
Detection Packet
500 Type is CV, the
value is always
1000.
to 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 ● Specifies or displays

the SD threshold.
When the OAM
higher than the
parameter value,
the corresponding
alarm is reported.
● When this
parameter is set to
0, SD threshold
detection is not
supported.

SF Threshold (%) 0-100 0 ● Specifies or displays

the SF threshold.
When the OAM
higher than the
parameter value,
the corresponding
alarm is reported.
● When this
parameter is set to
0, SF threshold
detection is not
supported.
not higher than the
SF threshold.
LSR ID to Be - - ● Specifies or displays

Received the LSR ID to be
received.
available only if
OAM Status is
Disabled.
PW ID to be Received - - ● Specifies or displays

the PW ID to be
received.
available only if
OAM Status is
Disabled.
Local PW Status - - Displays whether PWs

at the local end are
available.
Local PW-Defect - - Displays the local PW

Type 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

Type PW defect type.
Remote PW-Disabled - - Displays the duration

Duration(ms) when the remote PW
is unavailable.
Remote PW-Defect - - Displays the remote

Location PW defect location.
B.8.1.16 Parameter Description: PW Management_PW Ping

This topic describes the parameters that are related to the PW Ping test.
Navigation Path
Tree.
3. Select the required PW and click OAM Operation > Ping Test.

Packet Count 1 to 4294967295 3 Specifies the number

of test request
packets.

value of the PW
packets. The value
7 indicates the
highest priority.
recommended.

to-live (TTL) value
of the PW label in
test request
packets.
recommended.

Transmit 1 to 1000 100 ● Specifies the

Interval(10ms) interval for
transmitting test
request packets.
recommended.

of test request
packets.
recommended.

timeout value.
recommended.

test request
Channel Response
● The value No
Response indicates
that the test
performance event
is reported without
sending response
packets.
● The value
Application
Control Channel
Response indicates
that response is
performed through
the reverse
channel.
● The value IPv4
UDP indicates that
the IPv4 UDP
packets
encapsulating
MPLS echo reply
messages are sent
as response
packets.
● The value IPv4
UDP 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
remote PE. If the
remote PE supports
reverse channel
response, set this
parameter to
Application
Control Channel
Response. If the
remote PE does not
support reverse

channel response
but supports DCN
channel response
by means of IP
protocols, set this
parameter to IPv4
UDP Response.
Peer PW ID - - Specifies the PW ID of

the peer end.
Peer IP - - Specifies the IP

address of the peer
port.
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
Tree.
3. Select the required PW, click OAM Operation in the lower right corner, and


value of the PW
packets. The value
7 indicates the
highest priority.
recommended.

to-live (TTL) value
of the PW label in
test request
packets.
recommended.


of test request
packets.
recommended.

timeout value.
recommended.

test request
Channel Response
● The value No
Response indicates
that the test
performance event
is reported without
sending response
packets.
● The value
Application
Control Channel
Response indicates
that response is
performed through
the reverse
channel.
● The value IPv4
UDP indicates that
the IPv4 UDP
packets
encapsulating
MPLS echo reply
messages are sent
as response
packets.
● The value IPv4
UDP 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
remote PE. If the
remote PE supports
reverse channel
response, set this
parameter to
Application
Control Channel
Response. If the
remote PE does not
support reverse

channel response
but supports DCN
channel response
by means of IP
protocols, set this
parameter to 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
Tree.
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 ● When all NEs

ICC Based connected to a PW
are Huawei devices
Customer Based that support I-
based MPLS-TP
OAM components,
it is recommended
that you set MEG
ID Type to IP
Based. In this case,
you do not need to
configure MEG ID,
MP ID, RMEP ID, or
MIP.
● 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 - - ● You need to set

MEG ID when MEG
ID Type is not IP
Based.
● Set MEG ID to the
same value for
nodes connected to
the same PW.
● 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
RMEP ID 1 to 8191 - same value as RMEP
ID at the sink end.

Detection Mode Adaptive Adaptive ● Manual: tests

Manual whether a PW is
available based on
the user-defined
CCM transmission
interval.
● Adaptive: tests
whether a PW is
available based on
the interval at
which CCMs have
been received.
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 3.3 1000 ● If the MPLS-TP

(ms) 10 OAM CC function is
used for only
100 continuity check, it
1000 is recommended
that you set CC
Packet Interval
(ms) to the default
value 1000.
● 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
tunnel exceeds 3.3
ms, set the
transmission
interval of CCMs to
a value greater
than the frame
delay variation.
Lock Status Unlock Unlock Set Lock Status to

Lock Lock if a PW needs to
be locked.
NOTE
CSHU/CSHUA and
OptiX RTN 950A do not
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 - - Displays the position

Location of a PW fault.
SD Threshold (%) 0 to 100 0 ● Displays or

specifies the SD
threshold. An alarm
is reported if the
OAM packet loss
the SD threshold.
set to 0, SD
threshold detection
is not supported.
SF Threshold (%) 0 to 100 0 ● Displays or

specifies the SF
threshold. An alarm
is reported if the
OAM packet loss
the SF threshold.
set to 0, SF
threshold detection
is not supported.
smaller than or
equal to the SF
threshold.
LSR ID to be Received - - ● 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.
● LSR ID to be
Received and PW
ID to be Received
are available only
when OAM is
disabled.

GAL Enable Status Disabled Disabled ● Specifies whether

Enabled OAM packets carry
generic associated
channel header
labels (GALs).
● 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

Huawei Mode that you set LM
Packet Mode to
Standard.
NOTE
CSHU/CSHUA and
OptiX RTN 950A do not
GAL Mode RFC5586 RFC5586 When this parameter

Y.1711 is set to RFC5586, the
GAL label is 13. When
this parameter is set
to Y.1711, the GAL
label is 14.
B.8.1.19 Parameter Description: PW Management_Creating MIPs

This section describes the parameters that are used for creating an MIP in MPLS-
TP PW OAM.
Navigation Path
Tree.
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 ● It is recommended

Customer Based that you set MEG
ID Type to ICC
Based.
with non-Huawei
this parameter to
Customer Based.
MEG ID - - ● Set MEG ID to the

same value for
nodes connected to
the same PW.
● 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
Tree.
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
Local MEP ID - - MEG 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 - - ● Set Remote

or IP Address MEP/MIP ID or IP
Address according
to the termination
node of an LB test.
set to IP Based for
the termination
node, set Remote
MEP/MIP ID or IP
Address to the LSR
ID of the
termination node.
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 ● Specifies the

number of packets
that can be
transmitted each
time.
that this parameter
take its default
value.

Packet Priority 0 to 7 7 ● Specifies the packet

priority.
that this parameter
take its default
value.
TTL 1 to 255 355 ● If Node Type is

MIP, set TTL to the
number of hops
between the source
MEP and the
current MIP.
● 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 ● Specifies the packet

1s transmission
interval.
10s
that this parameter
take its default
value.
Packet length 128 to 1410 128 ● Specifies the packet

length.
that this parameter
take its default
value.
B.8.1.21 Parameter Description: MPLS APS Protection Management

This topic describes parameters that are related to MPLS APS protection
management.

Navigation Path
2. Click the Tunnel APS Management tab.

Protection Group ID - - ● Displays the

protection group
ID.
● The system
automatically
assigns IDs to the
protection groups
according to their
creation sequence.

protection group type.
Switching Mode Dual-Ended - ● Displays or

Single-Ended specifies the
switching mode of
a protection group.
● The value Single-
Ended indicates
that services are
switched only in
the direction where
faults occur.
● The value Dual-
Ended indicates
that services in
both positive and
reverse directions
are switched to
their protection
channels when
faults occur.
that you set this
parameter to Dual-
Ended.

BDI Status Disabled - ● Specifies or displays

Enabled whether the
protection
switching is
triggered upon
receiving BDI
packets.
available only when
Switching Mode is
set to Single-
Ended.
● 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
protection
switching.
Transmit and receive - - Displays the protocol

Status of Protocol packet status.
Packet
Revertive Mode Non-Revertive - ● Specifies or displays

Revertive whether to switch
services to the
original working
tunnel after the
fault is rectified.
● The value
Revertive indicates
to perform the
switching; the value
Non-Revertive
indicates not to
perform the
switching.
that you set this
parameter to
Revertive.

WTR Time(min) 1-12 - ● Specifies and

displays the WTR
time of the
protection group.
● When the preset
WTR time expires
after the original
working tunnel
recovers, services
are switched to the
original working
tunnel.
available only when
Revertive Mode is
Revertive.
that you set this
parameter to 5.
Hold-off 0-100 - ● Specifies the hold-

Time(100ms) off time of the
protection group.
than 0, the
protection group
does not trigger
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
switching is
triggered;
otherwise, no
switching is
triggered.
that you set this
parameter to 0.
Protocol Status - - Displays the protocol

status.

Switching Status - - Displays the switching

status of the
protection 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
1:1.
Switching Mode Single-Ended Dual-Ended ● Specifies the

Dual-Ended switching mode to
be adopted when a
tunnel fails.
● The value Single-
Ended indicates
that services are
switched only in
the direction where
faults occur.
● The value Dual-
Ended indicates
that services are
switched to the
protection channel
in both directions
when faults occur.
● The value Dual-
Ended is
recommended.

BDI Status Enabled Disabled ● Specifies whether

Disabled the protection
switching is
triggered upon
receiving BDI
packets.
available only when
Switching Mode is
set to Single-
Ended.
● 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
protection
switching.
Working Tunnel Type MPLS Tunnel MPLS Tunnel Specifies the type of
the working tunnel.
NOTE
The OptiX RTN 900
MPLS Tunnel.
Working Ingress - - ● Specifies the

Tunnel ID working tunnel of
the protection
group in the ingress
direction.
set for a
bidirectional tunnel,
a value is
automatically
assigned to the
parameter
Working Egress
Tunnel ID.
Working Ingress - - Displays the name of

Tunnel Name the working tunnel in
the ingress direction.

Working Egress - - ● Specifies the

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 - - Displays the name of

Tunnel Name the working tunnel in
the egress direction.
Protection Tunnel - - Displays the type of

Type protection tunnel,
which is the same as
the type of working
tunnel.
Protection Ingress - - ● Specifies the

the protection
group in the ingress
direction.
set for a
bidirectional tunnel,
a value is
automatically
assigned to the
parameter
Protection Egress
Tunnel ID.
Protection Ingress - - Displays the name of

Tunnel Name the protection tunnel
in the ingress
direction.

Protection Egress - - ● Specifies the

Tunnel ID protection tunnel
of the protection
group in the egress
direction.
tunnel, if the
parameter
Protection Ingress
Tunnel ID is set, a
value is
automatically
assigned to the
parameter
Protection Egress
Tunnel ID.
Protection Egress - - Displays the name of

Tunnel Name the protection tunnel
in the egress direction.
Revertive Mode Non-Revertive Non-Revertive ● This parameter

to switch services
working tunnel
after it recovers.
● The value
Revertive indicates
to switch services
working tunnel
after it recovers;
the value Non-
Revertive indicates
not to switch
services back to the
original working
tunnel after it
recovers.
● The value
Revertive is
recommended.

WTR Time(min) 1 to 12 5 ● Specifies the WTR

time of the
protection group.
● When the preset
WTR time expires
after the original
working tunnel
recovers, services
are switched to the
original working
tunnel.
available only when
Revertive Mode is
Revertive.
recommended.
Hold-off 0 to 100 0 ● Specifies the hold-

Time(100ms) off time of the
protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.
recommended.

Protocol Status Disabled Disabled ● Specifies the

Enabled protocol status.
of a protection
group, set Protocol
Status to Disabled.
After the APS
protection group is
configured at both
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:
Configuration > 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:
Configuration > ATM Service Management from the Function Tree.
4. Click New.



PW that carries
services.


of a PW.

the PW.

Ingress label.

Egress label.
Tunnel selection - - Displays the method

mode to select tunnels.

the PW.
Ingress Tunnel - - A tunnel needs to be

of a PW will fail.

end. If an existing
LSR ID will be
automatically
assigned.


QoS Parameters


parameter.

Bandwidth Limit Disabled - Specifies whether the

Enabled bandwidth limit
the bandwidth of
one or more PWs in
an MPLS tunnel.
● An ETH PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ETH
PWE3 services in an
MPLS tunnel.

parameter.
CIR(kbit/s) - - Specifies the

committed
of a PW.
It is recommended
that you set this
parameter to the
same value as PIR.
CBS(byte) - - Specifies the

(CBS) of a PW.

PIR(kbit/s) - - Specifies the peak

of a PW.
It is recommended
that you set this
parameter to the
same value as CIR.
PBS(byte) - - Specifies the peak

PW.

parameter.

mode.
NOTE
The OptiX RTN 900
supports only Pipe.


the bandwidth of
one or more PWs in
an MPLS tunnel.
● An ATM PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ATM
PWE3 services in an
MPLS tunnel.


committed
of a PW.
It is recommended
that you set this
parameter to the
same value as PIR.

(CBS) of a PW.

of a PW.
It is recommended
that you set this
parameter to the
same value as CIR.

PW.

parameter.

parameter.


CES service packets



Ingress Clock Mode - - The OptiX RTN 900

parameter.
Egress Clock Mode - - The OptiX RTN 900

parameter.
Control Channel Type - - Displays the mode of

PW continuity check.

Mode verification mode. The
VCCV verification is
used for PW continuity
check.

transmitted.

corresponding alarm
actual packet loss
ratio crosses this
threshold.

packets. The
corresponding alarm
threshold.

Mode number mode.


transfer packet
PWE3 services, this
parameter is always
not used.

channel type.

Mode mode.

Ethernet Tag, this
VLAN ID to be added
to packets that are
any VLAN IDs.

does not support
VLAN TPID of the PW
level.

transfer packet
information.

channel type.

Mode mode.

concatenated cells.




protection type.


the PW protection
group.
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.
NOTE

working PW.

protection PW.

mode to be used
when a PW fails.
NOTE


to switch services
working PW after it
recovers.
● 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.
● The value
Revertive is
recommended.

● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.
recommended.


protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.
recommended.

mode of the PW APS
protection group.
OAM Parameters

status of PW OAM.


OAM packets.
● Manual: The CC
packets are sent at
the interval
specified by the
user.
CC packets are sent
at the interval of
receiving PW OAM
packets.
is set to Manual,
you need to set the
PW OAM detection
packets to be
received and
transmitted.
● The value Auto-
Sensing is
recommended.


a fixed interval.
packets are sent at
the interval
specified by the
user.
is set to Auto-
Sensing, this
parameter specifies
the PW OAM
detection packets
to be transmitted.
is set to Manual,
this parameter
specifies the PW
OAM detection
packets to be
received and
transmitted.
assumed for PW
APS and the value
CV is assumed for
continuous CC on
PWs.

packets.
20
200 Type is FFD and
assumes the fixed
Detection Packet
Type is CV.
to 3.3 for PW APS.

be received.

be 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.


PW that carries
services.


of a PW.

the PW.

Ingress label.

Egress label.
Tunnel Selection - - Displays the method


the PW.

of a PW will fail.


end. If an existing
LSR ID will be
automatically
assigned.

QoS Parameters

the bandwidth of
one or more PWs in
an MPLS tunnel.
● An ETH PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ETH
PWE3 services in an
MPLS tunnel.

parameter.

committed
of a PW.
It is recommended
that you set this
parameter to the
same value as PIR.

(CBS) of a PW.


of a PW.
It is recommended
that you set this
parameter to the
same value as CIR.

PW.

parameter.

mode.
NOTE
The OptiX RTN 900
supports only Pipe.


transfer packet
PWE3 services, this
parameter is always
not used.

channel type.

Mode mode.

Ethernet Tag, this
VLAN ID to be added
to packets that are
any VLAN IDs.


does not support
VLAN TPID of the PW
level.


protection type.

Enabling Status Disabled Disabled Specifies the enabling

Enabled status of the PW
protection group.

protection mode.

working PW.

protection PW.

mode to be used
when a PW fails.


to switch services
working PW after it
recovers.
● 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.
● The value
Revertive is
recommended.

● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.
recommended.


protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.
recommended.

mode of the PW APS
protection group.
MPLS-TP OAM Parameters


status of PW OAM.

Detection Mode Adaptive Adaptive ● Specifies the

OAM packets.
● Manual: The CC
packets are sent at
the interval
specified by the
user.
● Adaptive: The CC
packets are sent at
the interval of
receiving PW OAM
packets.
is set to Manual,
you need to set the
PW OAM detection
packets to be
received and
transmitted.
● The value Adaptive
is recommended.
CC Packet Detection 3.33ms 1s ● Specifies the period

Interval(ms) 10ms of detection
packets.
100ms
1s configurable when
10s Detection Packet
1min Type is FFD and
assumes the fixed
10min value of 1000 when
Detection Packet
Type is CV.
to 3.3 for PW APS.

be received.

be received.
GAL Enable Status Enabled Enabled Set the GAL enable

Disabled status.


status of PW OAM.

OAM packets.
● Manual: The CC
packets are sent at
the interval
specified by the
user.
CC packets are sent
at the interval of
receiving PW OAM
packets.
is set to Manual,
you need to set the
PW OAM detection
packets to be
received and
transmitted.
● The value Auto-
Sensing is
recommended.


a fixed interval.
packets are sent at
the interval
specified by the
user.
is set to Auto-
Sensing, this
parameter specifies
the PW OAM
detection packets
to be transmitted.
is set to Manual,
this parameter
specifies the PW
OAM detection
packets to be
received and
transmitted.
assumed for PW
APS and the value
CV is assumed for
continuous CC on
PWs.

packets.
20
200 Type is FFD and
assumes the fixed
Detection Packet
Type is CV.
to 3.3 for PW APS.

be received.

be 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.


PW that carries
services.



of a PW.

the PW.

Ingress label.

Egress label.


the PW.

of a PW will fail.

end. If an existing
LSR ID will be
automatically
assigned.

QoS Parameters


parameter.



the bandwidth of
one or more PWs in
an MPLS tunnel.
● An ETH PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ETH
PWE3 services in an
MPLS tunnel.

parameter.

committed
of a PW.
It is recommended
that you set this
parameter to the
same value as PIR.

(CBS) of a PW.

of a PW.
It is recommended
that you set this
parameter to the
same value as CIR.

PW.

parameter.


mode.
NOTE
The OptiX RTN 900
supports only Pipe.


the bandwidth of
one or more PWs in
an MPLS tunnel.
● An ATM PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ATM
PWE3 services in an
MPLS tunnel.

committed
of a PW.
It is recommended
that you set this
parameter to the
same value as PIR.

(CBS) of a PW.

of a PW.
It is recommended
that you set this
parameter to the
same value as CIR.


PW.

parameter.

parameter.


CES service packets



parameter.

parameter.

PW continuity check.

used for PW continuity
check.

transmitted.


corresponding alarm
actual packet loss
ratio crosses this
threshold.

packets. The
corresponding alarm
threshold.

Mode number mode.


transfer packet
PWE3 services, this
parameter is always
not used.

channel type.

Mode mode.

Ethernet Tag, this
VLAN ID to be added
to packets that are
any VLAN IDs.


does not support
VLAN TPID of the PW
level.


transfer packet
information.

channel type.

Mode mode.

concatenated cells.



protection mode.

master PW APS
protection group
of the slave PW APS
protection group
simultaneously.

working PW in the


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.


displays the NE name.
T-PID (PW S-TAG) 8100 88A8 This parameter

88A8 specifies the value of
TPIDs in S-TAGs
9100 carried in QinQ-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

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 ● When this

SOH only parameter is set to
common, CES
services are used to
transmit common
CES packets.
● When this
parameter is set to
SOH only, CES
services are used to
transparently
transmit only
segment overhead
bytes.
SOH Byte D1-D12, E1-E2, F1, K1- - ● Specifies the

K2 and X1-X4 segment overhead
bytes transparently
transmitted by CES
services. This
parameter can be
set manually.
valid only when
Service Type is set
to SOH only.
Source Board - - Displays the source

board of the CES
service.
Source High Channel - - ● Specifies the source

higher order
channel of a CES
service.
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 - ● Specifies the

CS6 priority of a CES
service. This
EF parameter is
AF4 available only when
AF3 Mode is set to
UNI-NNI.
AF2
● This parameter
AF1 needs to be
BE configured if QoS
processing needs to
be performed for
different CES
services.
● CS6-CS7: indicate
the highest service
classes, which are
mainly involved in
signaling
transmission.
● 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.
● 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.
● 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 - - ● Specifies the sink

higher order
channel of a CES
service.
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
parameter is
meaningful when the
CES service type is
UNI-UNI.
Sink 64K Timeslot - - Displays the sink 64

kbit/s timeslot. This
parameter is
meaningful when the
CES service type is
UNI-UNI.


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 - - Displays the tunnel

Type 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

end.
Local Working Status - - Displays the working

status of the PW at
the local end.
Remote Working - - Displays the working

the remote end.
Compositive Working - - Displays the

Status compositive 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

tunnel that carries the
CES service.

the tunnel.
Tunnel Automatic - - The OptiX RTN 900

Selection Policy does not support this
parameter.
QoS Parameters


of a PW.
CIR(kbit/s) - - The OptiX RTN 900

parameter.

parameter.

RTP Header - - Displays the RTP

header. The RTP
header carries time
stamps.
Jitter Compensation - - Displays or specifies

Buffering Time(us) the jitter buffer time.


parameter.

parameter.

PW continuity check
(CC).

used for PW CC.

Enable CES Service Enabled - Displays or specifies

Alarm Transparent Disabled the enabling status of
Transmission the transparent
transmission of CES
service alarms. If this
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 1-65535 - Displays or specifies

Entering R Bit the threshold of
Inserting Status packet loss ratio of
CES services. The
corresponding alarm
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 1-65535 - Displays or specifies

R Bit Inserting Status the threshold of
packets. The
corresponding alarm
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.

protection mode.

enabling status of
the PW protection
group.
of a protection
group, set Enabling
Status to Disabled.
After the APS
protection group is
configured at both
ends, set Enabling
Status to Enabled.

mode to be used
when a PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.


to the original
working PW after
the fault is
rectified.
● 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.
● The value
Revertive is
recommended.

time of the
protection group.
● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.


off time of the
protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.




the current working
path.

path.

NOTE


master PW APS
protection group
of the slave PW APS
protection group
simultaneously.

working PW in the


ID.

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 - Specifies the

4294967295 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 ● When this

SOH only parameter is
set to
common,
CES services
are used to
transmit
common
CES packets.
● When this
parameter is
set to SOH
only, CES
services are
used to
transparently
transmit
only
segment
overhead
bytes.
Mode UNI-NNI UNI-NNI ● Specifies the

UNI-UNI mode of CES
service.
● 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, - ● Specifies the

F1, K1-K2 and segment
X1-X4 overhead
bytes
transparently
transmitted
by CES
services. This
parameter
can be set
manually.
● 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 - - ● Specifies the

source
higher order
channel of a
CES service.
● 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 ● 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.
● On the two
ends of a
radio link,
the timeslot
lists can be
different but
the numbers
of timeslots
must the
same.
● This
parameter
does not
need to be
set if Mode
is UNI-NNI
and PW
Type is
SAToP.

Priority List CS7 EF ● Specifies the

CS6 priority of a
CES service.
EF This
AF4 parameter is
AF3 available
only when
AF2 Mode is set
AF1 to UNI-NNI.
BE ● This
parameter
needs to be
configured if
QoS
processing
needs to be
performed
for different
CES services.
● CS6-CS7:
indicate the
highest
service
classes,
which are
mainly
involved in
signaling
transmission.
● 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.
● 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.
● BE: is
applicable to
services that
does not
need to be
processed in
a special
manner.
● The default
value is
recommende
d.

PW Type CESoPSN CESoPSN ● Specifies the

SAToP type of the
PW. This
parameter is
available
only when
Mode is
UNI-NNI.
● 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 ● Specifies the

PW APS protection
mode of the
Slave Protection PW. This
Pair parameter is
available
only when
Mode is
UNI-NNI.
● If this
parameter is
set to PW
APS,
working and
protection
PWs need to
be
configured.
● 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
simultaneou
sly.

Sink Board - - ● Specifies the

board where
the sink of
the CES
service is
located.
● This
parameter is
available
only when
Mode is set
to UNI-UNI.
Sink High Channel - - ● Specifies the

source
higher order
channel of a
CES service.
● 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) - - ● If Level is

set to E1,
this
parameter
indicates the
E1 port
where the
service sink
is located.
● This
parameter is
available
only when
Mode is set
to UNI-UNI.

Sink 64K Timeslot (e.g.1,3-6) 1-31 1-31 ● 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.
● 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

PW that carries
services.


of the PW.

the PW.


Ingress label.

Egress label.


the PW.

of a PW will fail.

end. If an existing
LSR ID will be
automatically
assigned.

QoS Parameters

support this
parameter.

Parameters for the Advanced Attributes of PWs

RTP Header Disable Disable ● Specifies the RTP

Enable Huawei RTP header.
● The RTP header
carries time
stamps.
recommended.
Jitter Compensation For OptiX RTN 8000 ● Specifies the jitter

Buffering Time (us) 910/910A/950/950A/ buffer time for the
980/980L: 375 to received CES
16000 packets. The step is
For OptiX RTN 905: 125.
875 to 16000 ● The larger the jitter
NOTE compensation
For OptiX RTN buffering time, the
910/910A/950/950A/ larger jitter CES
980/980L: services can bear,
● The minimum value and the larger the
for CES services on network latency.
Smart E1 boards is
375. ● The jitter
● The minimum value
compensation
for CES services on buffering time
channelized STM-1 should be larger or
boards is 875. equal to (3 * packet
loading time + 2 *
end-to-end
network jitter
time).
recommended.
Packet Loading Time 125 to 5000 1000 ● Specifies the length

(us) of fragments in the
TDM data stream.
The step is 125.
● 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

support this
parameter.
Control Channel Type None CW ● Specifies the mode

CW of PW continuity
check (CC).
Alert Label
● The value None
indicates that the
control word is not
supported. That is,
the PW CC is not
supported.
● Alert Label
indicates VCCV
packets in Alert
Label encapsulation
mode.
● The value CW
indicates that the
control word is
supported.
VCCV Verification None Ping ● Specifies the VCCV

Mode Ping verification mode.
The VCCV
for PW CC.
not set this
parameter to
None.
Enable CES Service Disabled Disabled If this function is

Alarm Transparent Enabled enabled, the fault on
Transmission 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 1-65535 100 ● The corresponding

Entering R Bit alarm will be
Inserting Status reported if the
number of
consecutive lost
packets crosses the
threshold specified
by this parameter.
available only
when the
transparent
transmission of CES
service alarms is
enabled.
Threshold of Exiting 1-65535 5 ● The corresponding

R Bit Inserting Status alarm will be
cleared if the
number of
consecutive
received packets
crosses the
threshold specified
by this parameter.
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


protection type.


the PW protection
group.
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.
NOTE

working PW.

protection PW.

mode to be used
when a PW fails.
NOTE


to switch services
working PW after it
recovers.
● 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.
● The value
Revertive is
recommended.

● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.
recommended.


protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.
recommended.

mode of the PW APS
protection group.
OAM Parameters
NOTE

status of PW OAM.


OAM packets.
● Manual: The CC
packets are sent at
the interval
specified by the
user.
CC packets are sent
at the interval of
receiving PW OAM
packets.
is set to Manual,
you need to set the
PW OAM detection
packets to be
received and
transmitted.
● The value Auto-
Sensing is
recommended.


a fixed interval.
packets are sent at
the interval
specified by the
user.
is set to Auto-
Sensing, this
parameter specifies
the PW OAM
detection packets
to be transmitted.
is set to Manual,
this parameter
specifies the PW
OAM detection
packets to be
received and
transmitted.
assumed for PW
APS and the value
CV is assumed for
continuous CC on
PWs.

packets.
20
200 Type is FFD and
assumes the fixed
Detection Packet
Type is CV.
to 3.3 for PW APS.

be received.

be received.


NOTE

protection mode.

master PW APS
protection group
of the slave PW APS
protection group
simultaneously.

working PW in the

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
Configuration > Interface Management > ATM IMA Management from the
Function Tree.
2. Click the IMA Group Management tab.


VCTRUNK - - Displays the ATM

TRUNK.
IMA Protocol Status Enabled Disabled ● Specifies the IMA

Disabled protocol enable
status.
● 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.
● 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 ● The links of the

Active Transmitting IMA group can
Links carry services only
when the number
of activated links in
the transmit/receive
direction is not
smaller than the
value of Minimum
Number of Active
Transmitting
Links/Minimum
Number of Active
Receiving Links.
● The values of
Minimum Number
of Active
Transmitting Links
and Minimum
Number of Active
Receiving Links
must be the same
because the OptiX

Minimum Number of 1 to 16 1 RTN 950 supports

Active Receiving Symmetrical Mode
Links 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.
recommended.
IMA Protocol Version 1.0 1.1 ● Specifies the IMA

1.1 protocol version.
● The parameter IMA
Protocol Version
must assume the
same value on the
two ends of an IMA
link.
recommended.

IMA Transmit Frame 32 128 ● Specifies the IMA

Length 64 transmit frame
length.
128
● Based on the IMA
256 frame format, the
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.
● The IMA Transmit
Frame Length
must assume the
same value on the
two ends of an IMA
link.
recommended.

IMA Symmetry Mode Symmetrical Mode Symmetrical Mode ● Specifies the

and Symmetrical and Symmetrical symmetrical mode
Operation Operation of the IMA group.
● 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 ● Specifies the

Between Links (ms) maximum
differential delay
that is allowed
between the
member links.
● 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.
set 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.
● The Maximum
Delay Between
Links (ms) must
assume the same
value on the two
ends of an IMA
link.
recommended.
Clock Mode CTC Mode CTC Mode ● Specifies the clock

ITC Mode mode of the IMA
group.
● 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
Function Tree.
2. Click the Binding tab.

Available Boards - - Selects the

available boards.
Configurable Ports - - Selects the

configurable ATM
trunks.
Level E1 E1 Specifies the level

Fractional E1 of bound paths.
● If ATM/IMA
services need
to be mapped
into the ATM
TRUNK that
binds one or
more E1 ports,
select E1 in
Level.
● 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 does not
support this
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 does not
support this
parameter.
Selected Bound Paths - - Displays the

bound paths.
VCTRUNK - - Displays the name

of the ATM
TRUNK.
Level - - Displays the level

of 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

Not selected to 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
Function Tree.
2. Click the IMA Group States tab.

VCTRUNK - - Displays the

VCTRUNK.
Near-End Group - - Displays the status of

Status the near-end group.
Far-End Group Status - - Displays the status of

the far-end group.
Transmit Rate - - Displays the cell

(cell/s) transmission rate.
Receive Rate (cell/s) - - Displays the cell

receiving rate.
Number of Transmit - - Displays the number

Links of transmit links.
Number of Receive - - Displays the number

Links of receive links.
Number of Activated - - Displays the number

Transmit Links of activated transmit
links.
Number of Activated - - Displays the number

Receive Links of 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
Function Tree.

2. Click the IMA Link States tab.


VCTRUNK.
E1 Link - - Displays E1 links.
Differential Delay - - Displays the status of

Check Status the deferential delay
check.
Near-End Receiving - - Displays the near-end

Status receiving status.
Near-End - - Displays the near-end

Transmission 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
Function Tree.
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.
● 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.
● 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.
● 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.
● ATM Cell Payload
Scrambling must
assume the same
value on the two
ends of an ATM
link. Otherwise,
packet loss will
occur.
Min. VPI - - The OptiX RTN 900

parameter.
Max. VPI - - The OptiX RTN 900

parameter.
Min. VCI - - The OptiX RTN 900

parameter.
Max. VCI - - The OptiX RTN 900

parameter.
VCC-Supported VPI - - The OptiX RTN 900

Count does 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

Mapping Relation ID - - Specifies the ID of the

mapping table.
Mapping Relation - - Specifies the name of

Name the mapping
relationship.
UBR BE UBR: BE Displays or specifies

AF11 CBR: EF the PHB service
CBR classes that
AF12 RT-VBR: AF31
RT-VBR correspond to
AF13 NRT-VBR: AF21 different ATM service
NRT-VBR AF21 types.
UBR+: AF11
AF22 ● Eight PHB service
UBR+ PORT-TRANS: BE
AF23 classes are
available: BE, AF1,
AF31
AF2, AF3, AF4, EF,
AF32 CS6, and CS7. The
AF33 OptiX RTN 900
AF42 QoS policies for the
queues of different
AF43 service classes.
EF ● CS6 to CS7: highest
CS6 service classes,
CS7 mainly applicable
to signaling
transmission.
● EF: fast forwarding,
applicable to
services of low
transmission delays
and low packet loss
rates.
● AF1 to AF4: assured
forwarding,

PORT-TRANS 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.
● BE: best effort,
applicable to
services 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
Configuration > QoS Management > Diffserv domain Management > ATM
COS Mapping Configuration from the Function Tree.
2. Click New.

Mapping Relation ID 2 to 8 - Specifies the ID of the

mapping table.
Mapping Relation - - Specifies the name of

Name the mapping
relationship.
UBR BE UBR: BE Specifies the PHB

AF11 CBR: EF service classes that

CBR AF12 RT-VBR: AF31 correspond to

AF13 NRT-VBR: AF21 different ATM service
RT-VBR types.
AF21 UBR+: AF11
NRT-VBR AF22 PORT-TRANS: BE ● Eight PHB service
classes are
UBR+ AF23 available: BE, AF1,
AF31 AF2, AF3, AF4, EF,
PORT-TRANS
AF32 CS6, and CS7. The
AF33 OptiX RTN 900
provides different
AF41 QoS policies for the
AF42 queues of different
AF43 service classes.
EF ● CS6 to CS7: highest
CS6 service classes,
mainly applicable
CS7
to signaling
transmission.
● EF: fast forwarding,
applicable to
services of low
transmission delays
and low packet loss
rates.
● 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.
● BE: best effort,
applicable to
services 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
Configuration > QoS Management > Policy Management > ATM Policy
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

CBR the type of the ATM
service.
RT-VBR
● The UBR service is
NRT-VBR characterized by
UBR+ non-real-time
applications and
many bursts. The
UBR service does
not specify traffic-
related service
guarantees. To be
specific, the UBR
service only
requires that the
network side
provides the service
with the best effort.
The network side
does not provide
any assured QoS
for the UBR service.
In the case of
network
congestion, the
UBR cells are
discarded first.
● 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.
● 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.
● 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.
● The UBR+ service is
supplementary to
the UBR service
and is intended for
applications that
require assured
minimum cell rate,
which is indicated
by the minimum
cell rate (MCR)
parameter. The
other
characteristics of
the UBR+ service
are the same as the
corresponding
characteristics of
the UBR service.
Traffic Type - - The Table B-102 lists

the ATM service type,
Clp01Pcr(cell/s) 90 to 74539 - traffic type descriptor,
Clp01Scr(cell/s) 90 to 74539 - and the related traffic
parameters. ATM
Clp0Pcr(cell/s) 90 to 74539 - policies are configured
based on these
Clp0Scr(cell/s) 90 to 74539 - mapping relationships.

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

Disabled the frame discarding
mark in ATM policies.
This parameter is
effective to AAL5
traffic.
UPC/NPC Enabled Disabled Displays or specifies

Disabled UPC/NPC.
● UPC is user-side
parameter control
and NPC is
network-side
parameter control.
● After UPC/NPC is
enabled, the cells
with a frame
discarding mark
will be discarded in
network
congestion.
Table B-102 Mapping relationship between ATM service types, traffic types, and traffic parameters
ATM ATM Traffic Type Traffic Traffic Traffic Traffic
Service Descriptor Parameter Parameter Parameter Parameter
Type 1 2 3 4
UBR NoTrafficDescriptor - - - -
NoClpTaggingNoScr Clp01Pcr CDVT - -
NoClpNoScr Clp01Pcr - - -
NoClpNoScrCdvt Clp01Pcr CDVT - -
CBR ClpTransparentNoScr Clp01Pcr CDVT - -
ClpNoTaggingNoScr Clp01Pcr Clp0Pcr - -
ClpTaggingNoScr Clp01Pcr Clp0Pcr - -


Type 1 2 3 4
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
ClpTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
UBR+ atmnotrafficdescrip- Clp01Mcr - - -

tormcr
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.

of 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
Configuration > QoS Management > Policy Management > ATM Policy
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

Signaling name of the ATM
service. The maximum
Voice length of the value is
Data 64 bytes.
Video NOTE
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

CBR the ATM service.
RT-VBR ● The UBR service is
characterized by
NRT-VBR non-real-time
UBR+ applications and
many bursts. The
UBR service does
not specify traffic-
related service
guarantees. To be
specific, the UBR
service only
requires that the
network side
provides the service
with the best effort.
The network side
does not provide
any assured QoS
for the UBR service.
In the case of
network
congestion, the
UBR cells are
discarded first.
● 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.
● 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.
● 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.
● The UBR+ service is
supplementary to
the UBR service
and is intended for
applications that
require assured
minimum cell rate,
which is indicated
by the minimum
cell rate (MCR)
parameter. The
other
characteristics of
the UBR+ service
are the same as the
corresponding
characteristics of
the UBR service.
Traffic Type - - For the mapping

Clp01Pcr(cell/s) 90 to 74539 - ATM service types,
Clp01Scr(cell/s) 90 to 74539 - ATM traffic type
descriptors, and traffic
Clp0Pcr(cell/s) 90 to 74539 - parameters, see Table
B-103. ATM policies
Clp0Scr(cell/s) 90 to 74539 - are configured based
on these mapping
Max. Cell Burst Size 2 to 200000 -
relationships.
(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 ● UPC is user-side

Disabled parameter control
and NPC is
network-side
parameter control.
● After UPC/NPC is
enabled, the cells
with a frame
discarding mark
will be discarded in
network
congestion.
Table B-103 Mapping relationship between ATM service types, ATM traffic types, and traffic
parameters
Type 1 2 3 4
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 -


Type 1 2 3 4
rtVBR ClpTransparentScr Clp01Pcr Clp01Scr MBS CDVT
NoClpScrCdvt Clp01Pcr Clp01Scr MBS CDVT
ClpNoTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
ClpTaggingScrCdvt Clp01Pcr Clp0Scr MBS CDVT
UBR+ atmnotrafficdescrip- Clp01Mcr - - -

tormcr
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

Service ID - - Displays the service ID.
Service Name - - Displays or specifies

the service name.
Service Type - - Displays the ATM

service type.

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

sink port of the ATM
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


VCTRUNK.
Level - - Displays the

level of bound
paths.

direction of
bound paths.
The fixed
value is
bidirectional.
Bound Paths - - Displays the

bound paths.
Number of - - Displays the

Bound Paths number of
bound paths.
IMA Group - - Displays the

Status 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.

PW Status - - Displays whether a

PW is enabled.
PW Signaling - - Displays the PW

Type signaling type.
NOTE
The OptiX RTN 900
uses static PWs only.
PW Type - - ● Displays the

configured PW
type.
● 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

PW - - Displays the
Encapsulation encapsulation type
Type of the packets on
the PW.
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 - - Displays the tunnel

No 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 - - Displays the remote

Operating Status running status of
PW.
Overall - - Displays the

Operating 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.


Bandwidth Limit - - Displays or specifies

whether the
bandwidth limit is
enabled.
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.)
● 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.
It is recommended
that you set this
parameter 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.
It is recommended
that you set this
parameter to the
same value as CIR.

PBS (kbyte) - - Displays or specifies

the maximum
excess burst size of
the PW.

does not support
this parameter.

does not support
this 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 control word is
used to transmit
packet information.
Control Channel CW - ● Displays or

Type None specifies the
mode of PW
Alert Label connectivity
check.
● The value None
indicates that the
control word is
not supported.
That is, the PW
connectivity
check is not
supported.
● The value CW
indicates that the
control word is
supported.
● The value Alert
Label indicates
VCCV packets in
Alert Label
encapsulation
mode.

VCCV Ping - ● Displays or

Verification None specifies the
Mode VCCV verification
mode. The VCCV
verification is
used for PW
connectivity
check.
● If the VCCV-ping
function is
required, do not
set VCCV
Verification
Mode of PWs to
None.
Max. 1 to 31 - ● Displays or
Concatenated specifies the
Cell Count maximum
number of
concatenated
cells.
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 100 to 50000 - ● 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.
● If Max.
Concatenated
Cell Count
assumes the
value 1, this
parameter is
ineffective. That
is, the packet will
be sent out once
the cell is loaded.
Parameters for CoS Mapping


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.

protection mode.

enabling status of
the PW protection
group.
of a protection
group, set Enabling
Status to Disabled.
After the APS
protection group is
configured at both
ends, set Enabling
Status to Enabled.

mode to be used
when a PW fails.
NOTE
The OptiX RTN 900
supports dual-ended
switching.


to the original
working PW after
the fault is
rectified.
● 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.
● The value
Revertive is
recommended.

time of the
protection group.
● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.


off time of the
protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.




the current working
path.

path.

NOTE


master PW APS
protection group
of the slave PW APS
protection group
simultaneously.

working PW in the


ID.

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 ● Specifies the type

UNI-UNI of the ATM service.
● UNIs-NNI: This
value applies to
ATM PWE3
services. The
attributes in
Connection, PW,
and CoS Mapping
need to be
configured.
● UNI-UNI: This value
applies to common
ATM services. Only
the attributes in
Connection need
to be configured.
Connection Type PVC PVC Specifies the

PVP connection type of the
ATM service.
Transparent
For common ATM
services (UNI-UNI):
● PVP: Only the VPIs
of the source and
sink are exchanged.
● PVC: The VPIs and
VCIs of the source
and sink are
exchanged.
For ATM PWE3
services (UNIs-NNI):
● PVP: This value
applies to the N-
to-1/1-to-1 VPC
encapsulation
mode.
● 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 ● Specifies the

PW APS protection mode of
the PW. This
Slave Protection Pair parameter is
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. UNI: 0 to 255 - Specifies the VPI of

35,36-39) NNI: 0 to 4095 the source port of the
ATM service.
Source VCI(eg. 32 to 65535 - Specifies the VCI of

35,36-39) the source port of the
ATM service.
PW ID 1 to 4294967295 - Specifies the ID of the

PW that carries
services.
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

NNI: 0 to 4095 the sink port of the
ATM service.
Sink VCI(eg.35,36-39) 32 to 65535 - Specifies the VCI of

the sink port of the
ATM 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.

PW that carries
services.
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 ● Specifies the type
type is PVC: type is PVC: of the PW.
● ATM n-to-one VCC ATM n-to-one VCC ● In the case of ATM
cell transport cell transport 1_to_1
● ATM one-to-one The ATM connection encapsulation, one
VCC Cell Mode type is PVP: PW carries one VPC
or VCC.
The ATM connection ATM n-to-one VPC cell
type is PVP: transport ● In the case of ATM
n_to_1
● ATM n-to-one VPC encapsulation, one
cell transport PW carries one or
● ATM one-to-one more VPCs or VCCs.
VPC Cell Mode
PW Direction Bidirectional Bidirectional Displays the direction

of the PW.
PW Encapsulation MPLS MPLS Displays the

the packets on the
PW.

Ingress label.

Egress label.
Tunnel Selection Manually Manually Displays the method


the PW.

of a PW will fail.


end. If an existing
LSR ID will be
automatically
assigned.
QoS Parameters


bandwidth limit is
enabled.
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.)
● An ATM PWE3
service corresponds
to a PW. Therefore,
this function can
also limit the
bandwidth of ATM
PWE3 services in an
MPLS tunnel.

parameter.

CIR (Kbit/s) - - Specifies the

committed
of the PW.
It is recommended
that you set this
parameter to the
same value as PIR.
CBS (kbyte) - - Specifies the excess

burst size of the PW.

of the PW.
It is recommended
that you set this
parameter to the
same value as CIR.
PBS (kbyte) - - Specifies the

maximum excess burst
size of the PW.

parameter.
Parameters of Advanced Attributes

Control Word Must Use Must Use ● Specifies whether

No Use to use the control
word. In the MPLS
packet switching
network, the
control word is
used to transmit
packet information.
● Set Control Word
to Must Use if PW
Type is ATM 1:1.

Control Channel Type CW CW ● Specifies the mode

None of PW connectivity
check.
Alert Label
● The value None
indicates that the
control word is not
supported. That is,
the PW connectivity
check is not
supported.
● The value CW
indicates that the
control word is
supported.
● The value Alert
Label indicates
VCCV packets in
Alert Label
encapsulation
mode.

The VCCV
for PW connectivity
check.
not set this
parameter to None.
Max. Concatenated 1 to 31 10 ● Specifies the

Cell Count maximum number
of concatenated
cells.
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 ● 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.
● If Max.
Concatenated Cell
Count assumes the
value 1, this
parameter is
ineffective. That is,
the packet will be
sent out once the
cell is loaded.

NOTE

protection type.


the PW protection
group.
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.
NOTE

working PW.

protection PW.

mode to be used
when a PW fails.
NOTE

to switch services
working PW after it
recovers.
● 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.
● The value
Revertive is
recommended.


● When the preset
WTR time expires
after the original
working PW
recovers, services
are switched to the
original working
PW.
available only when
Revertive Mode is
Revertive.
recommended.

protection group.
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,
the switching is
triggered;
otherwise, no
switching is
triggered.
recommended.

mode of the PW APS
protection group.

OAM Parameters
NOTE

status of PW OAM.

OAM packets.
● Manual: The CC
packets are sent at
the interval
specified by the
user.
CC packets are sent
at the interval of
receiving PW OAM
packets.
is set to Manual,
you need to set the
PW OAM detection
packets to be
received and
transmitted.
● The value Auto-
Sensing is
recommended.


a fixed interval.
packets are sent at
the interval
specified by the
user.
is set to Auto-
Sensing, this
parameter specifies
the PW OAM
detection packets
to be transmitted.
is set to Manual,
this parameter
specifies the PW
OAM detection
packets to be
received and
transmitted.
assumed for PW
APS and the value
CV is assumed for
continuous CC on
PWs.

packets.
20
200 Type is FFD and
assumes the fixed
Detection Packet
Type is CV.
to 3.3 for PW APS.

be received.

be received.


NOTE

protection mode.

master PW APS
protection group
of the slave PW APS
protection group
simultaneously.

working PW in the

Parameters for CoS Mapping


PW that carries
service.
CoS Mapping - - Specifies the policy for

mapping different
ATM service levels to
CoS priorities. By
setting this parameter,
different quality
measures are provided
for different ATM
services.

B.8.4.12 Parameter Description: ATM OAM Management_Segment and End

Attributes
This topic describes the parameters that are related to segment end attributes of
ATM OAM.
Navigation Path
Configuration > ATM OAM Management from the Function Tree.
2. Click the Segment End Attributes tab.

Source - - Displays the source

node of the ATM/IMA
service.
Sink - - Displays the sink node

of the ATM/IMA
service.

Connection Direction Source - Displays the direction

Sink of the ATM
connection.
● Source: indicates
the forward
direction.
– For common
ATM services
(UNI-UNI),
Source indicates
the direction
from the source
end to the sink
end of the ATM
connection.
– For ATM PWE3
services (UNI-
NNI), Source
indicates the
direction from
the UNI port
side to the MPLS
interface side.
● Sink: indicates the
backward direction.
– For common
ATM services
(UNI-UNI), Sink
indicates the
direction from
the sink end to
the source end
of the ATM
connection.
– For ATM PWE3
services (UNI-
NNI), Sink
indicates the
direction from
the MPLS
interface side to
the UNI port
side.

Segment and End Non segment and Non segment and Specifies the segment
Attribute Endpoint Endpoint and end attributes of
Segment point the source and sink of
the ATM connection.
Endpoint
● Non segment and
Segment and Endpoint endpoint:
intermediate point,
which refers to the
OAM node
between two
segment points or
two end points.
Therefore,
intermediate points
can be further
classified into
intermediate points
between segment
points, and
intermediate points
between end
points.
– Upon detecting
a fault, an
intermediate
point reports the
corresponding
alarms and
inserts segment
AIS cells and
end AIS cells to
the downstream.
Afterwards, the
intermediate
point
periodically
sends these
cells.
– An intermediate
point does not
catch any
AIS/RDI cells.
● Segment point: an
end point of a
segment. One ATM
link consists of
multiple segments.

– Upon detecting
a fault, a
segment point
reports the
corresponding
alarms and
inserts end AIS
cells to the
downstream.
Afterwards, the
segment point
periodically
sends these
cells.
– A segment point
catches segment
AIS/RDI cells
only.
● End point: an end
point of an ATM
link. It is usually an
edge point on the
ATM network.
– Upon detecting
a fault, an end
point reports the
corresponding
alarms but does
not insert any
AIS cells.
– An end point
catches end
AIS/RDI cells
only.
● Segment and
endpoint: a
segment-end point,
or an edge point of
a segment and an
end.
– Upon detecting
a fault, a
segment-end
point reports the
corresponding
alarms but does
not insert any
AIS cells.

– A segment-end
point catches
the AIS/RDI cells
of a segment
and an end.
B.8.4.13 Parameter Description: ATM OAM Management_CC Activation

Status
This topic describes the parameters that are related to the CC activation status of
ATM OAM.
Navigation Path
2. Click the CC Activation Status tab.


node of the ATM/IMA
service.

of the ATM/IMA
service.

Connection Direction Source - Specifies the

Sink connection direction.
the forward
direction.
– For common
ATM services
(UNI-UNI),
Source indicates
the direction
from the source
end to the sink
end of the ATM
connection.
– For ATM PWE3
services (UNI-
NNI), Source
indicates the
direction from
the UNI port
side to the MPLS
interface side.
backward direction.
– For common
ATM services
(UNI-UNI), Sink
indicates the
direction from
the sink end to
the source end
of the ATM
connection.
– For ATM PWE3
services (UNI-
NNI), Sink
indicates the
direction from
the MPLS
interface side to
the UNI port
side.

Segment and End - - Specifies the segment

Attribute and end attributes of
nodes.
● Segment point: an
end point of a
segment. One ATM
link consists of
multiple segments.
Segment CC cells
are terminated at
segment points.
● End point: an end
point of an ATM
link. It is usually an
edge point on an
ATM network. End-
to-end CC cells are
terminated at end
points.

CC Activate Flag Deactivate - ● Specifies the CC

Source activate activation flag.
Sink activate ● Deactivate: This
node does not
Source + sink activate transmit or receive
CC cells.
● Source activate:
This point transmits
but does not
receive CC cells.
● Sink activate: This
point receives but
does not transmit
CC cells. If this
point does not
receive any service
cells or CC cells
within a time
interval of 3.5
(±0.5) seconds, it
will report the LOC
alarm and transmit
AIS cells in the
forward direction.
● Source + sink
activate: This node
transmits and
receives CC cells. If
this point does not
receive any service
cells or CC cells
within a time
interval of 3.5
(±0.5) seconds, it
will report the LOC
alarm and transmit
AIS cells in the
forward direction.
● Once the node
receives any CC
cells or service cells,
the LOC alarm will
be cleared.

B.8.4.14 Parameter Description: ATM OAM Management_Remote End

Loopback Status
This topic describes the parameters that are related to the remote end loopback
status of ATM OAM.
Navigation Path
2. Click the Remote Loopback Test tab.


node of the ATM/IMA
service.

of the ATM/IMA
service.

Connection Direction Source - Displays the direction

Sink of the ATM
connection.
the forward
direction.
– For common
ATM services
(UNI-UNI),
Source indicates
the direction
from the source
end to the sink
end of the ATM
connection.
– For ATM PWE3
services (UNI-
NNI), Source
indicates the
direction from
the UNI port
side to the MPLS
interface side.
backward direction.
– For common
ATM services
(UNI-UNI), Sink
indicates the
direction from
the sink end to
the source end
of the ATM
connection.
– For ATM PWE3
services (UNI-
NNI), Sink
indicates the
direction from
the MPLS
interface side to
the UNI port
side.

Segment and End - - Specifies the segment

Attribute and end attribute.
● 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.
Loopback Point NE - - ● Specifies the NE

where the loopback
point is located.
● Before an end-to-
end LB test, you
need to set end
points in the test
domain. After the
test, remove the
end points.
● Before a segment-
to-segment LB test,
you need to set
segment points in
the test domain.
After the test,
remove the
segment points.
Test Result - - Displays whether the

loopback command is
successfully issued.
B.8.4.15 Parameter Description: ATM OAM Management_LLID

This topic describes the parameters that are related to LLID configuration.
Navigation Path
2. Click the LLID tab.


Country Code - 00 00 Displays or specifies

(Hexadecimal Code) the country code of
the ATM service. The
value is 2 bytes in
length.
Network Code - 00 01 Displays or specifies

(Hexadecimal Code) the network code of
the ATM service. The
value is 2 bytes in
length.
NE Code - 00 30 00 04 00 00 00 ● Displays or
(Hexadecimal Code) 00 00 00 00 specifies the NE
code of the ATM
service. The value is
11 bytes in length.
● The default NE
code can be used if
it is unique on the
network.
● NE code and NE ID
are associated.
Therefore, each NE
on the network has
a unique NE code.
B.8.4.16 Parameter Description: ATM OAM_ATM Cell Insertion Status

This section describes the parameters for configuring the ATM cell insertion status.
Navigation Path
1. Select a desired NE from the Object Tree in the NE Explorer. Choose
2. Click the Insert OAM Cell to ATM tab.


Insert OAM Cell to Enabled Enabled ● Normally, retain

ATM Disabled the default value
Enabled for this
parameter to
ensure normally
functioning of the
AIS/RDI function on
the ATM
connection for
which segment and
end attributes have
been configured.
to Disabled when
the AIS/RDI
function on the
ATM connection for
which segment and
end attributes have
been configured
needs to be
disabled.
B.8.5 MP Group Parameters

This section describes parameters that are used for configuring an MP group.
B.8.5.1 Parameter Description: MP Group Management_Creation

This parameter describes the parameters that are used for creating an MP group.
Navigation Path
Configuration > Interface Management > MP Group Management from
the Function Tree.
3. Click New.
Parameters in the Window for Setting MP Group Parameters

MP Group Number 0 to 255 - Specifies the MP group

ID.

Name - - Specifies the MP group

name.
Specify IP Address Manually Manually It is recommended

Borrow NE IP Address that you set Specify IP
Address to Manually.
Borrow Interface IP
Address
Unspecified
IP Address - 0.0.0.0 Set Specify IP Address

to Manually, and set
IP Mask - 255.255.255.252 IP Address and IP
Mask according to the
service plan.
Peer IP - - The OptiX RTN 900

does not allow this
parameter to be
specified.
Board for Borrowed - - The OptiX RTN 900

IP Address does not allow this
parameter to be
specified.
Port for Borrowed IP - - The OptiX RTN 900

Address does not allow this
parameter to be
specified.
Min Activated Link 1 to 16 1 ● If you want the

Count interruption of N
PPP links to trigger
MPLS APS of the
entire MP group,
set Min Activated
Link Count as
required.
● Generally, Min
Activated Link
Count takes its
default value 1.
● Set Min Activated
Link Count to the
same value for both
end of a radio link.

Enable Differential Disabled Disabled ● If you set Enable

Delay Enabled Differential Delay
to Enabled and a
member link has
excessive delay, this
link does not
perform the data
packet slicing.
that this parameter
take its default
value.
Max Differential 25 to 500 500 ● This parameter

Delay (100us) takes effect only
when Enable
Differential Delay
is set to Enabled.
that Max
Differential Delay
(100us) take its
default value at
both ends of the
radio link.
Enable Tunnel Disabled Disabled ● If you set Enable

Enabled Tunnel to Enabled,
the port identifies
and processes MPLS
labels.
that you set this
parameter to
Enabled.
● If services have
been configured, do
not set Enable
Tunnel to
Disabled.

MTU(byte) 960 to 1620 1450 ● Indicates the

maximum transport
unit. When the
length of a packet
received by a port is
greater than the set
MTU value, this
packet will be
discarded.
that you set this
parameter to 1620,
which is the same
as the MTU for
MPLS ports.
Fragmentation Unfragmented 64 ● Specifies the

64 fragmentation size.
If the
128 fragmentation size
256 is small, the
512 scheduling
efficiency of each
member link is
enhanced. In this
case, packet
overheads are
increased. As a
result, bandwidth
utilization of the
link is affected.
● Set Fragmentation
to the same value
for both ends of the
radio link.
that you set this
parameter to
Unfragmented.

Sequence Number Huawei mode Huawei mode ● Set Sequence

Type Long Serial Number Number Type to
the same value for
Short Serial Number both ends of the
radio link.
● When Short Serial
Number is
supported at both
ends of the radio
link, Short Serial
Number is
preferred.
OSICP Negotiation - - The OptiX RTN 900

does not allow this
parameter to be
specified.
Send CRC BER - - The OptiX RTN 900

Threshold-crossing does not allow this
Event parameter to be
specified.
B.8.5.2 Parameter Description: MP Group Management_Basic Attributes

This section describes the parameters that are used for configuring the MP group
attributes.
Navigation Path
Configuration > Interface Management > MP Group Management from
the Function Tree.
Parameters in the window for setting MP group attributes

MP Group Number - - Displays the MP group

ID.
Name - - Displays the MP group

name.

Link Status - - ● Displays the link

status.
● If Link Status is
Up, the MLPPP is
functional.
● If Link Status is
Down, the MLPPP
is abnormal. Locate
and handle the
fault.
Send Rate (kbit/s) - - Displays the send rate

of MP group.
Receive Rate (kbit/s) - - Displays the receive

rate of MP group.
Min Activated Link 1 to 16 1 ● If you want the

Count interruption of
some PPP links to
trigger MPLS APS
of the entire MP
group, set Min
Activated Link
Count as desired.
● Generally, Min
Activated Link
Count takes its
default value 1.
● Set Min Activated
Link Count to the
same value for both
end of a radio link.
Enable Differential Disabled - ● If you set Enable

Delay Enabled Differential Delay
to Enabled and a
member link has
excessive delay, this
link does not
perform the data
packet slicing.
that this parameter
take its default
value.

Max Differential 25 to 500 - ● This parameter

Delay (100us) takes effect only
when Enable
Differential Delay
is set to Enabled.
that Max
Differential Delay
(100us) take its
default value at
both ends of the
radio link.
Enable Tunnel Disabled - ● If you set Enable

Enabled Tunnel to Enabled,
the port identifies
and processes MPLS
labels.
that you set this
parameter to
Enabled.
● If services have
been configured, do
not set Enable
Tunnel to
Disabled.
Max.Reserved - - The OptiX RTN 900

Bandwidth (kbit/s) does not allow this
parameter to be
specified.
TE Measurement - - The OptiX RTN 900

does not allow this
parameter to be
specified.
Admin Group - - The OptiX RTN 900

does not allow this
parameter to be
specified.
IP Address - - Displays the IP address

Negotiation Result and mask of the MP
group.
IP Mask Negotiation - -
Result

MTU 960 to 1620 - ● The MTU indicates

the maximum
transport unit.
When the length of
a packet received
by a port is greater
than the set MTU
value, this packet
will be discarded.
that you set this
parameter to 1620,
which is the same
as the MTU for
MPLS ports.
Fragmentation Unfragmented - ● Specifies the

64 fragmentation size.
If the
128 fragmentation size
256 is small, the
512 scheduling
efficiency of each
member link is
enhanced. In this
case, packet
overheads are
increased. As a
result, bandwidth
utilization of the
link is affected.
● Set Fragmentation
to the same value
for both ends of the
radio link.
that you set this
parameter to
Unfragmented.

Sequence Number Huawei mode - ● Set Sequence

Type Long Serial Number Number Type to
the same value for
Short Serial Number both ends of the
radio link.
● When Short Serial
Number is
supported at both
ends of the radio
link, Short Serial
Number is
preferred.
OSICP Negotiation - - The OptiX RTN 900

does not allow this
parameter to be
specified.
Send CRC BER - - The OptiX RTN 900

Threshold-crossing does not allow this
Event parameter to be
specified.
B.9 Clock Parameters

This topic describes the parameters that are related to clocks.
B.9.1 Parameter Description: Frequency Selection Mode

This topic describes parameters that are related to frequency selection.
Navigation Path
Configuration > Clock > Frequency Selection Mode from the Function Tree.

NE Name - - Displays the NE name.

Select Frequency Physical Physical Specifies the clock

Source Mode Synchronization Synchronization synchronization mode
PTP Synchronization of an NE.
NOTE
● For equipment that
receives an external
clock, set this
parameter to
Physical
Synchronization.
● For a 1588 ACR
client or a PTP clock
used for frequency
synchronization, set
this parameter to
PTP
Synchronization.
B.9.2 Physical Clock Parameters

This topic describes physical clock parameters.
B.9.2.1 Parameter Description: Clock Source Priority Table

This topic describes the parameters that are related to the priority table of a clock
source.
Navigation Path
> Clock > Physical Clock > Clock Source Priority.
2. Click the System Clock Source Priority List tab.

Parameters
Clock Source - - ● For OptiX RTN 905,

External clock
source is the
external clock
source provided by
the CLK/TOD/MON
port on the front
panel of the
chassis.
● For OptiX RTN 950,
External clock
source 1 indicates
the external clock
source at the CLK/
TOD1 port on the
CST or CSH board
in physical slot 7.
External clock
source 2 indicates
the external clock
source at the CLK/
TOD1 port on the
CST or CSH board
in physical slot 8.
● For OptiX RTN
910A, External
clock source 1
indicates the
external clock
source at the CLK,
TOD, or MON port
on the CSHR board
in physical slot 1.
● For OptiX RTN
950A, External
clock source 1
indicates the
external clock
source at the CLK/
TOD1 port on the
CSHO board in
physical slot 7.
External clock
source 2 indicates
the external clock
source at the CLK/
TOD1 port on the

CSHO board in
physical slot 8.
External clock
source 1 indicates
the external clock
source at the CLK/
TOD1 port on the
CSHN board in
physical slot 15.
External clock
source 2 indicates
the external clock
source at the CLK/
TOD1 port on the
CSHN board in
physical slot 20.
● The internal clock
source is always at
the lowest priority
and indicates that
the NE works in
the free-run mode.
● The clock sources
and the
corresponding
clock source
priority levels are
determined
according to the
clock
synchronization
schemes.
External Clock Source 2 Mbit/s 2 Mbit/s ● This parameter

Mode 2 MHz indicates the type
of the external
clock source signal.
set according to
the external clock
signal. In normal
cases, the external
clock signal is a 2
Mbit/s signal.

Synchronous Status SA4 to SA8 SA4 ● This parameter is

Byte valid only when
External Clock
Source Mode is set
to 2 Mbit/s.
● This parameter
indicates which bit
of the TS0 in odd
frames of the
external clock
signal is used to
transmit the SSM.
● This parameter
needs to be set
only when the SSM
or extended SSM is
enabled. In normal
cases, the external
clock sources use
the SA4 to transmit
the SSM.
Clock Source Priority - - Displays the priority

Sequence (Highest: sequence of clock
1) sources. 1 indicates
the highest clock
source priority.
B.9.2.2 Parameter Description: Priority Table for the PLL Clock Source of the
External Clock Port
This topic describes the parameters that are related to the priority table for the
phase-locked loop (PLL) clock source of the external clock port.
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and then choose
Configuration > Clock > Physical Clock > Clock Source Priority from the
Function Tree.
2. Click the Priority for PLL Clock Sources of 1st External Output tab.

Parameters for configuring the priority table for the PLL clock source of the
external clock port
Clock Source - Internal Clock Source ● 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.
● When the PLL clock
source of the
external clock port
needs to extract
the clock from an
SDH line board,
clock from a radio
link, clock from a
PDH tributary
board, or
synchronous
Ethernet clock, set
Clock Source to
the corresponding
clock source
according to the
network planning
information.
Current Status - - Displays the valid

status of clock
sources.

Lock Status - - ● The PLL clock

source of the
external clock port
extracts only an
unlocked clock
source.
● If a clock source is
in locked state, the
PLL clock source of
the external clock
port does not
extract the clock
source until the
clock source is
changed from the
locked state to the
unlocked state.
● The internal clock
source should not
be in locked state.
Clock Source Priority - - Displays the priority

(Highest: 1) level of a clock source.
1 is the highest
priority.
B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Subnet

This topic describes the parameters that are related to a clock subnet.
Navigation Path
> Clock > Physical Clock > Clock Subnet Configuration.
2. Click the Clock Subnet tab.
Parameters for Setting a Clock Subnet

Affiliated Subnet - - The NE does not

support this
parameter.

Protection Status Start Extended SSM Stop SSM Protocol ● The SSM protocol
Protocol is a scheme used
Start Standard SSM for synchronous
Protocol management on an
SDH network and
Stop SSM Protocol indicates that the
SSM is passed by
the lower four bits
of the S1 byte and
can be exchanged
between the nodes.
The SSM protocol
ensures that the
equipment
automatically
selects the clock
source of the
highest quality and
highest priority,
thus preventing
mutual clock
tracing.
● After the standard
SSM protocol is
started, the NE first
performs the
protection
switching on the
clock source
according to the
clock quality level
information
provided by the S1
byte. If the quality
level of the clock
source is the same,
the NE then
performs the
protection
switching according
to the clock priority
table. That is, the
NE selects an
unlocked clock
source that is of
the highest quality
and highest priority
from all the current
available clock
sources as the

clock source to be
synchronized and
traced by the local
station.
● If the SSM protocol
is stopped, it
indicates that the
S1 byte is not used.
The NE selects and
switches a clock
source only
according to the
sequence specified
in the priority
table. The clock
source of the
highest priority is
used as the clock
source to be traced.
● After the SSM
protocol is stopped,
each NE performs
the protection
switching on the
clock according to
the preset priority
table of the clock
source only when
the clock source of
a higher priority is
lost.
Clock Source - - This parameter

indicates the clock
source that is
configured for an NE.
In Clock Source
Priority, you can set
whether to add or
delete a clock source.

Clock Source ID (None) (None) ● This parameter is

1 to 15 valid only when the
extended SSM
protocol is started.
● Clock source IDs
are allocated for
the following clock
sources only:
– External clock
source
– Internal clock
source of the
node that
accesses the
external clock
sources
– Internal clock
source of the
joint node of a
ring and a chain
or the joint node
of two rings
– Line clock
source that
enters the ring
when the intra-
ring line clock
source is
configured at
the joint node of
a ring and a
chain or the
joint node of
two rings
B.9.2.4 Parameter Description: Clock Subnet Setting_Clock Quality

This topic describes the parameters that are related clock quality.
Navigation Path
> Clock > Physical Clock > Physical Clock Subnet Configuration.
2. Click the Received Quality tab.

Parameters for Clock Source Quality


the configured clock
source. In Clock
Source Priority, you
can set whether to
add or delete a clock
source.
Configured Quality Unknown Automatic Extraction This parameter

Synchronization specifies the quality
Quality level that is
G.811 Clock Signal configured for the
clock source. This
G.812 Transit Clock function is required
Signal only in a special
G.812 Local Clock scenario or in a test.
Signal Generally, this
G.813 SDH Equipment parameter need not
Timing Source (SETS) be set.
Signal
Do Not Use For
Synchronization
Automatic Extraction
Received Quality - - This parameter

indicates the clock
source quality signal
received by the NE.
The NE extracts the
clock source quality
signal from the S1
byte of each clock
source.
Parameters for Manual Setting of 0 Quality Level


the NE.

Manual Setting of 0 Do Not Use For Do Not Use For This parameter
Quality Level Synchronization Synchronization specifies the clock
G.811 Reference Clock quality whose level is
manually set to zero.
Between G.811
Reference Clock and ● Do Not Use For
G.812 Transit Clock Synchronization:
the notification
G.812 Transit Clock information in the
Between G.812 Transit reverse direction of
Clock and G.812 Local the selected
Clock synchronization
G.812 Local Clock clock source to
avoid direct mutual
Between G.812 Local locking of adjacent
Clock and synchronous NEs.
equipment timing
source (SETS) ● G.811 Reference
Clock: the clock
SETS Clock signal specified in
Between synchronous ITU-T G.811.
equipment timing ● Between G.811
source(SETS) and Reference Clock
quality unavailable and G.812 Transit
Clock: lower than
the quality level of
the clock signal
specified in ITU-T
G.811 but higher
than the quality
level of the transit
exchange clock
signal specified in
ITU-T G.812.
● G.812 Transit Clock:
the transit
exchange clock
signal specified in
ITU-T G.812.
● Between G.812
Transit Clock and
G.812 Local Clock:
lower than the
quality level of the
transit exchange
clock signal
specified in ITU-T
G.812 but higher
than the quality
level of the local
exchange clock

signal specified in
ITU-T G.812.
● G.812 Local Clock:
the local exchange
clock signal
specified in ITU-T
G.812.
● Between G.812
Local Clock and
synchronous
equipment timing
source (SETS):
lower than the
local exchange
clock signal
specified in ITU-T
G.812 but higher
than the quality
level of the clock
signal of the SETS.
● SETS Clock: the
clock signal of the
SETS.
● Between
synchronous
equipment timing
source (SETS) and
quality unavailable:
lower than the
clock signal of the
SETS but higher
than the quality
level unavailable in
the synchronous
timing source.
B.9.2.5 Parameter Description: Clock Subset Setting_SSM Output Control

This topic describes the parameters that are related to SSM output control.
Navigation Path
2. Click the SSM Output tab.

Parameters
Line Port - - ● This parameter

indicates the name
of the line clock
port.
● Line Port: indicates
the SSM quality
information output
port of the current
available line clock
source and the
external clock
source. This output
port can transmit
the quality
information of the
clock source by
outputting the S1
byte to the
downstream NE.
Output S1 Byte Info Enabled Enabled ● Output S1 Byte

Disabled Info is valid only
when the SSM
protocol or the
extended SSM
● Output S1 Byte
Info indicates
whether the SSM is
output at the line
port.
● 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.
B.9.2.6 Parameter Description: Clock Subset Setting_Clock ID Enabling Status

This topic describes the parameters that are used for enabling the clock ID
function.

Navigation Path
2. Click the Clock ID Output tab.
Parameters
Line Port - - ● This parameter

indicates the name
of the line clock
port.
● Line Port: indicates
the SSM quality
information output
port of the current
available line clock
source and the
external clock
source. This output
port can transmit
the quality
information of the
clock source by
outputting the S1
byte to the
downstream NE.
Output Clock ID Enabled Enabled ● Output Clock ID is

Disabled valid only when the
extended SSM
● Output Clock ID
indicates whether
the clock source ID
is output at the line
port.
● If the line ports are
connected to the
NEs in the same
clock subnet and if
the extended SSM
protocol is started
on the opposite NE,
Output Clock ID is
set to Enabled.
Otherwise, this
parameter is set to
Disabled.

B.9.2.7 Parameter Description: Clock Source Switching_Clock Source

Restoration Parameters
This topic describes the parameters that are related to clock source restoration.
Navigation Path
> Clock > Clock Source Switching.
2. Click the Clock Source Reversion tab.
Parameters

the NE.

Higher Priority Clock Auto-Revertive Auto-Revertive ● When the quality

Source Reversion Non-Revertive of a higher-priority
clock source
degrades, the NE
automatically
switches the clock
source to a lower-
priority clock
source. If this
parameter is set to
Auto-Revertive,
the NE
automatically
switches the clock
source to the
higher-priority
clock source when
this higher-priority
clock source
restores. If this
parameter is set to
Non-Revertive, the
NE does not
automatically
switch the clock
source to the
higher-priority
clock source when
this higher-priority
clock source
restores.
● Correct setting of
Clock Source
Switching
Condition ensures
the reliability of the
clock source
switching. To
improve the clock
quality, select
Auto-Revertive.
Otherwise, to
prevent jitter of the
clock, generally, it
is recommended
that you set this
parameter to Non-
Revertive.

Clock Source WTR 0 to 12 5 ● This parameter

Time(min.) specifies the
duration from the
time when the
clock source
restoration is
detected to the
time when the
clock source
switching is
triggered. This
parameter is used
to avoid frequent
switching of the
clock source due to
instability of the
clock source state
within a short time.
valid only when
Higher Priority
Clock Source
Reversion is set to
Auto-Revertive.

Switching
This topic describes the parameters that are related to the switching status of a
clock source.
Navigation Path
> Clock > Physical Clock > Clock Source Switching.
2. Click the Clock Source Switching tab.
Parameters

the clock source.
Current Status Valid - This parameter

Invalid indicates whether the
clock source is valid.

Lock Status Lock - ● This parameter

Unlock specifies the
locking status of
the clock source in
the priority table.
● Lock: A clock
source in the
priority table is in
the locked state.
The clock source in
the locked state
cannot be
switched.
● Unlock: A clock
source in the
priority table is in
the unlocked state.
The clock source in
the unlocked state
can be switched.
Switching Source - - This parameter

indicates the clock
source to be traced by
the NE after the
switching.
Switching Status Normal - This parameter

Manual Switching indicates the
switching status of the
Forced Switching current clock source.

Switching Conditions
This section describes the parameters that are related to the switching conditions
of clock sources.
Navigation Path
Configuration > Clock > Clock Source Switching from the Function Tree.
2. Click the Clock Source Switching Conditions tab.

Parameters
NE Name - - Displays the name of

the NE.
Clock Source - - Displays the clock

source.
AIS Alarm Yes No ● The default value is

No recommended.
● When this
parameter is set to
Yes, it indicates
that clock source
switching occurs if
the clock source
reports the AIS
alarm.
● When this
parameter is set to
No, it indicates
that no clock
source switching
occurs if the clock
source reports the
AIS alarm.
B1 BER Threshold- - - The parameter is

Crossing invalid.
RLOS,RLOF and OOF/ Yes Yes This parameter

RLOC Alarms indicates that clock
switching occurs when
the clock source
reports the RLOS,
RLOF, OOF, or LOC
alarm.
CV Threshold- - - The parameter is

Crossing invalid.
CV Threshold - - The parameter is

invalid.

B2-EXC Alarm Yes No ● The default value is

No recommended.
● When this
parameter is set to
Yes, it indicates
that clock source
switching occurs if
the clock source
reports the B2-EXC
alarm.
● When this
parameter is set to
No, it indicates
that no clock
source switching
occurs if the clock
source reports the
B2-EXC alarm.
B.9.2.10 Parameter Description: Output Phase-Locked Source of the External

Clock Source
This topic describes the parameters of the output phase-locked source of the
external clock source.
Navigation Path
Clock > Physical Clock > Phase-Locked Source Output by External Clock.
Parameters
2M Phase-Locked External Clock Source - This parameter

Source Number 1 indicates the number
External Clock Source of the external clock
2 source output of the
NE.

External Clock 2 Mbit/s 2 Mbit/s ● This parameter

Output Mode 2 MHz specifies the mode
of the output clock.
set according to
the external clock
signal. In normal
cases, the external
clock signal is a 2
Mbit/s signal.
External clock
source 1 provides 2
MHz clock signals.
External clock
source 2 provides 2
Mbit/s clock
signals.
External Clock SA4 to SA8 ALL ● This parameter is

Output Timeslot ALL valid only when
External Clock
Output Mode is
set to 2 Mbit/s.
● This parameter
indicates which bit
of the TS0 in odd
frames of the
output clock signal
is used to transmit
the SSM.
set to ALL, it
indicates that all
the bits of the TS0
are used to
transmit the SSM.
that you use the
default value.

External Source Threshold Disabled Threshold Disabled ● This parameter

Output Threshold Not Inferior to G.813 specifies the lowest
SETS Signal quality of the
output clock. If the
Not Inferior to G.812 clock quality is
Local Signal lower than the
Not Inferior to G.812 value of this
Transit Clock Signal parameter, it
Not Inferior to G.811 indicates that the
Clock Signal external clock
source does not
output any clock
signal.
set to Threshold
Disabled, it
indicates that the
external clock
source always
outputs the clock
signal.
that you use the
default value.
2M Phase-Locked No Failure Condition No Failure Condition ● This parameter

Source Failure AIS specifies the failure
Condition condition of the 2
LOF Mbit/s phase-
AIS OR LOF locked clock source.
that you use the
default value.

2M Phase-Locked Shut Down Output Shut Down Output ● This parameter is

Source Failure 2M Output S1 Byte valid only when
Handing Unavailable 2M Phase-Locked
Source Failure
Send AIS Condition is not
set to No Failure
Condition.
● This parameter
specifies the
operation of the 2
Mbit/s phase-
locked loop (PLL)
when the 2 Mbit/s
phase-locked clock
source meets the
failure conditions.
that you use the
default value.
B.9.2.11 Parameter Description: Clock Synchronization Status

This topic describes the parameters that are related to the clock synchronization
status.
Navigation Path
Clock > Physical Clock > Clock Synchronization Status.
Parameters

the NE.
NE Clock Mode - - This parameter

indicates the working
mode of the NE clock.
S1 Byte - - This parameter

Synchronization indicates the
Quality Info synchronization
quality information of
the S1 byte.

S1 Byte Clock - - This parameter

Synchronous Source indicates the clock
synchronization source
of the S1 byte.
Synchronous Source - - This parameter

indicates the
synchronization
source.

Data Output Method Normal Data Output Normal Data Output ● When all the
in Holdover Mode Keep the Latest Data reference timing
signals are lost, the
slave clock changes
to the holdover
mode. At this time,
the slave clock
works based on the
latest frequency
information stored
before the
reference timing
signals are lost.
Then, the
frequency of the
oscillator drifts
slowly to ensure
that the offset
between the
frequency of the
slave clock and the
reference frequency
is very small. As a
result, the impact
caused by the drift
is limited within
the specified
requirement.
● Normal Data
Output: The slave
clock works based
on the latest
frequency
information stored
before the
reference timing
signals are lost,
and the holdover
duration depends
on the size of the
phase-locked clock
register on the
equipment. The
holdover duration
can be up to 24
hours.
● Keep the Latest
Data: The slave
clock works in

holdover mode all

the time based on
the latest
frequency
information stored
before the
reference timing
signals are lost.
B.9.3 CES ACR Clock Parameters

This topic describes CES ACR clock parameters.
B.9.3.1 Parameter Description: ACR Clock Source

This topic describes parameters that are related to the adaptive clock recovery
(ACR) clock source.
Navigation Path
Configuration > Clock > ACR Clock from the Function Tree.

ACR Clock Source - - Identifies the ACR

clock domain.
CES Service - - This parameter

the CES service that
the master ACR clock
source uses.
Track Mode - - This parameter

displays the trace
mode of an ACR clock
source.
Lock Status - - This parameter

displays whether an
ACR clock source is
locked.

Real ACR Clock - - This parameter

displays the CES
service from which the
current ACR clock
source is obtained.
B.9.3.2 Parameter Description: Clock Domain

This topic describes parameters that are related to clock domains.
Navigation Path

Clock Domain - - Displays the clock

domain.
Clock Domain Board - - Displays the board

where the clock
domain is located.
Clock Port - - Displays the Smart E1

ports that are bound
to a clock domain.
B.9.3.3 Parameter Description: Clock Domain_Creation

This topic describes the parameters for creating a clock domain.
Navigation Path
2. Click New.


Clock Domain System Clock Domain System Clock Domain Specifies the clock
CES ACR1 Clock domain to be bound.
Domain
CES ACR2 Clock
Domain
CES ACR3 Clock
Domain
CES ACR4 Clock
Domain
Clock Domain Board - - Displays the board

where the clock
domain is located.
Board - - Specifies the board

where the Smart E1
port is located.
Available Port - - Displays the Smart E1

ports that are not
bound to a clock
domain.
Selected Port - - Displays the Smart E1

ports that are bound
to a clock domain.
B.9.4 PTP Clock Parameters

This topic describes PTP clock parameters.
NOTE
OptiX RTN 905e does not support the configuration of PTP Clock.
B.9.4.1 Parameter Description: Clock Synchronization Attribute

This topic describes parameters that are used for creating a point to point (PTP)
clock port.
Navigation Path


PTP System Time - - Displays an upstream

clock source that the
selected PTP NE
traces. The traced time
can be transmitted to
a downstream NE
through a PTP port
(using IEEE 1588v2
messages) or an
external time port
(using 1PPS+ToD time
signals).
NOTE
● An OptiX RTN 900
NE supporting the
IEEE 1588v2 protocol
is a PTP NE.
● A PTP NE's port
supporting the IEEE
1588v2 protocol is a
PTP port.
● If an NE is not
tracing a PTP clock
source, you can
specify PTP System
Time for the NE. You
can specify PTP
System Time for an
NE only when
testing the IEEE
1588v2 function on
the NE. On a live
network, PTP
System Time
displays the
upstream clock
source that the
selected NE traces.

the local NE.

NE Clock Type OC BC ● An NE in OC mode

BC supports only one
PTP port and is
TC used at the
TC+BC network edge.
● An NE in BC mode
supports multiple
PTP ports and is
used as an
intermediate
network node.
● A TC provides
multiple PTP ports
for processing and
forwarding IEEE
1588 messages.
However, it does
not recover a clock
from the received
IEEE 1588
messages.
● The TC+BC mode
supports both time
transparent
transmission and
time
synchronization.
Static BMC Disabled Disabled Specifies the state of

Enabled the BMC algorithm.
set manually.
Slave_Only SLAVE_ONLY NON_SLAVE_ONLY ● This parameter can

NON_SLAVE_ONLY be set only in OC
mode.
● When this
parameter is set to
SLAVE_ONLY, the
NE can function
only as a slave
clock node.
● When this
parameter is set to
NON_SLAVE_ONLY
, the NE can
function as a
master clock node.

PTP Time Adjustment Enabled Enabled ● If the PTP system

Disabled time needs to be
adjusted (for
example, during
network-wide time
synchronization),
set this parameter
to Enabled.
● If the PTP system
time (for example,
1588 ACR clock)
does not need to
be adjusted, set this
parameter to
Disabled.
Packet Multicast Fully Multicasted Fully Multicasted ● If Packet Multicast

Mode Partially Multicasted Mode is set to
Fully Multicasted,
SYNC, ANNOUNCE,
and DELAY packets
are multicast.
● If Packet Multicast
Mode is set to
Partially
Multicasted, SYNC
and ANNOUNCE
packets are
multicast but
DELAY packets are
unicast.
Fully Multicasted
is recommended.

Protocol Packet NMEA UBX ● Specifies the

Format UBX protocol that an
external time port
uses for
transmitting TOD
signals.
● NMEA is an
international
protocol and the
commonest value.
● UBX is a protocol
defined by the
ULBOX company.
● This parameter
takes effect when
Interface Protocol
of the external time
port is 1PPS+Time.
be set but does not
take effect when
Interface Protocol
of the external time
port is DCLS.
Local Clock Source - - ● Displays the ID of

No the local PTP clock
source.
● The clock source ID
is comprised of the
enterprise code, NE
ID, and
supplementary
code.
● For a PTP clock
source ID of
Huawei equipment,
the enterprise code
is always 0x001E10,
the NE ID is in IPv4
format, and the
supplementary
code is 10.

Current Master Clock - - ● Displays the ID of

No the current PTP
clock that the NE
traces.
● If Current Master
Clock No is the
same as Local
Clock Source No,
the NE works in
free-run mode.
Ingress of Current - - Displays the input port

Master Clock of the current clock
source that the NE
traces.
Port Status Parameters

Port - - Displays the PTP ports.
Clock Type - - ● The working mode

of a PTP port can
be manually set to
BC or TC only when
NE Clock Type is
set to TC+BC and
the PTP port is an
Ethernet port.
● Set the parameter
according to the
service plan.

Step Mode Single Step Single Step ● Single Step

Double Step represents the one-
step mode. Single
Step indicates that
SYNC packets (in
Delay mode) and
PDELAY_RESP
packets (in PDELAY
mode) carry the
time stamps of
their transmission
moments.
● Double Step
represents the two-
step mode. Double
Step indicates that
SYNC packets (in
Delay mode) and
PDELAY_RESP
packets (in PDELAY
mode) do not carry
the time stamps of
their transmission
moments. The
packets only record
their transmission
moments and the
time stamps of
their transmission
moments are
carried by follow-
up packets
(namely,
FOLLOW_UP and
PDELAY_RESP_FOLL
OW_UP packets).
● This parameter
needs to be set to
the same value for
the local and
opposite NEs.
Generally, the one-
step mode is
preferred.

PTP Packet VLAN 1-4094 - ● Specifies or displays

the VLAN ID
carried by PTP
packets that travel
through a PTP port.
● The parameter at
both ends of a PTP
link must be set to
the same.
– In the case of
the OC/BC ports
of RTN
equipment
which are
directly
connected to
another RTN
equipment, it is
recommended
that PTP
messages adopt
Ethernet
encapsulation
without VLAN
ID.
– Set the VLAN
attribute of a TC
port in
compliance with
port L2 attribute
and the
requirement for
transparently
transmitting
services.
– In the case of
the PTP ports of
RTN equipment
which are
connected to
external PTP
equipment, set
the PTP packet
encapsulation
format and
VLAN ID
according to the
requirement of

external PTP
equipment.
PTP Packet PTP ETH PTP ETH ● If Layer 2

Encapsulation PTP IP encapsulation
Format needs to be
performed for PTP
packets, set this
parameter to PTP
ETH.
● If IP encapsulation
needs to be
performed for PTP
packets, set this
parameter to PTP
IP.
● This parameter
does not take effect
for microwave
interfaces.

Port Status MASTER+SLAVE MASTER+SLAVE ● Specifies or displays

MASTER the default status
of a PTP port.
SLAVE
● MASTER: When a
clock port is in
MASTER state, it
provides the clock
source to the
downstream
equipment.
● SLAVE: When a
port is in SLAVE
state, it functions
as the downstream
port to receive the
clock information
from its upstream
port.
● MASTER+SLAVE:
When a port is in
MASTER+SLAVE
state, it receives
clock information
from its upstream
port and functions
as a clock source
for its downstream
port.
recommended.
Current Port Status - - ● Displays the actual

port status.
● This parameter
value is determined
based on the BMC
algorithm.

Reference Clock 1-0xFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFF ● Specifies the

Source No FFFF F reference clock
source for a PTP
port.
● The reference clock
source is in "clock
ID+port ID" format.
A PTP NE allocates
its PTP ports each a
unique port ID
ranging from 0.
specified manually,
the PTP port uses
this parameter
value in the BMC
algorithm for clock
source selection.
● If the default
parameter value is
used, the PTP port
uses its first
received clock
source in the BMC
algorithm for clock
source selection.
● If a PTP port can
receive more than
one clock sources,
you need to specify
a reference clock
source for the port.
In other cases, this
parameter takes its
default value.
Enable ACR Enabled Disabled ● Specifies whether

Disabled the ACR is enabled.
valid only if the
ACR clock source is
configured.
● Not supported by
OptiX RTN 905.

Port Message Parameters

Port - - Displays the PTP port

names.
P/E Mode P2P P2P ● Set this parameter

E2E according to the
PTP NE type at the
opposite end. For
example, if the
opposite NE is an
E2E TC NE, set this
parameter to E2E.
● If the opposite NE
is a P2P TC NE, set
this parameter to
P2P.
● If the opposite NE
is an OC/BC node,
set this parameter
to E2E.
SYNC Packet Period - - ● Specifies the

(s) intervals for
transmitting SYNC
packets.
● This parameter
must be set to the
same value for the
local and opposite
PTP NEs. The
default value is
recommended.
DELAY Packet Period - - ● Specifies the

(s) intervals for
transmitting DELAY
packets.
● This parameter
must be set to the
same value for the
local and opposite
PTP NEs. The
default value is
recommended.
NOTE
set only if P/E Mode is
E2E.

PDELAY Packet - - ● Specifies the

Period (s) intervals for
transmitting
PDELAY packets.
● This parameter
must be set to the
same value for the
local and opposite
PTP NEs. The
default value is
recommended.
NOTE
set only if P/E Mode is
P2P.
ANNOUNCE Packet - - ● Specifies the

Period (s) intervals for
transmitting
ANNOUNCE
packets.
● This parameter
must be set to the
same value for the
local and opposite
PTP NEs. The
default value is
recommended.
ANNOUNCE Packet 2-10 3 ● Specifies the packet

Timeout Coefficient transmission
interval coefficient
for determining
that receiving of
ANNOUNCE
packets times out.
● If a port does not
receive ANNOUNCE
packets within the
parameter value, it
determines that the
link fails.
● This parameter
must be set to the
same value for the
local and opposite
PTP NEs. The
default value is
recommended.

Parameters for Cable Transmission Offset

Port - - Displays the PTP port

names.
Warp Direction Negative Positive ● Specifies the

Positive transmission
direction of PTP
packets.
● Specifies whether
asymmetric delay
compensation is
performed in the
transmit direction
or receive direction.
Warp Mode Length Length ● Specifies the

Time transmission delay
compensation
mode.
● Length indicates
that compensation
is provided based
on the distance
between the
receive end and the
transmit end.
● Time indicates that
compensation is
provided based on
the transmission
delay between the
receive end and the
transmit end.
Time is used.
Warp Length(m) - 0 ● Specifies the

distance to be
compensated.
be set when
Transmitting
Distance Mode is
Length.

Wrap Time (ns) - 0 ● Specifies the time

delay to be
compensated.
● This parameter
value can be
obtained by means
of GPS calibration.
be set when Warp
Mode is Time.
B.9.4.2 Parameter Description: Clock Synchronization Attribute_Creation of

PTP Clock Ports
This topic describes parameters that are used for creating a PTP clock port.
Navigation Path
Configuration > Clock > PTP Clock > Clock Synchronization Attribute from
the Function Tree.
2. Click the Port Status tab.
3. Click New.

Board - - Specifies boards to

support PTP clocks.
Available Port - - Displays all ports that

support PTP clocks.
Selected Port - - Displayed the selected

ports.
B.9.4.3 Parameter Description: Setting of a PTP Clock Subnet_Clock Subnet

This topic describes the parameters that are related to a PTP clock subnet.
Navigation Path
Function Tree.

2. Click the Clock Subnet tab.


the local NE.
Clock Subnet No. 0-255 0 ● This parameter

needs to be set
when a clock
subnet topology
needs to be created
on the NMS.
● NEs that trace the
same grandmaster
clock need to be
allocated the same
clock subnet ID.
B.9.4.4 Parameter Description: Setting of a PTP Clock Subnet_BMC

This topic describes the parameters that are related to the BMC in a PTP clock
subnet.
Navigation Path
Function Tree.
2. Click the BMC tab.


the local NE.
Time Quality Level 0-255 187 ● The smaller the

parameter value,
the higher the
quality.
recommended.

Time Precision 0-255 254 ● The smaller the

parameter value,
the higher the time
accuracy.
recommended.
Clock Source Type INTERNAL_OSCILLATO INTERNAL_OSCILLATO ● Specifies the type

R R of the local clock
ATOMIC_CLOCK source.
GPS ● The default value is
recommended.
TERRESTRIAL_RADIO
PTP
NTP
HAND_SET
OTHER
Clock Source Priority 0-255 128 ● The smaller the

1 parameter value,
the higher the
priority.
it is recommended
that you set this
parameter to the
default value.
● For other OptiX
RTN 900 products,
if the local NE
functions as the
master 1588 ACR
clock node, set this
parameter to 1. In
other cases, this
parameter takes its
default value.

Clock Source Priority 0-255 128 ● The smaller the

2 parameter value,
the higher the
priority.
recommended.
NOTE
Select the optimal clock
source according to the
following preference
sequence: Clock source
priority 1 > Time
precision > Time quality
level > Clock source
priority 2.
B.9.4.5 Parameter Description: External Time Port_Basic Attributes

This topic describes the parameters that are related to the basic attributes of the
external time port.
Navigation Path
Configuration > Clock > PTP Clock > External Time Interface from the
Function Tree.
2. Click the Basic Attribute tab.

External Time Interface - - Displays the

name of the
external time
port.
Interface Mode External Clock External Clock The NE

Interface Interface provides a port
External Time for external
Interface time/clock
input/output.
When this port
works as an
external time
port, set this
parameter to
External Time
Interface.

Direction Egress Egress ● Specifies

Ingress the time
transmissio
n direction.
● If the NE
receives
time
information
from its
external
clock port,
set this
parameter
to Ingress.
If the NE
receives
time
information
from its
external
time port,
set this
parameter
to Egress.
Interface Protocol Type DCLS DCLS ● Specifies or

1PPS+Time displays the
time
transmissio
n mode of
the external
time port.
● Set this
parameter
according to
the
parameter
setting of
the external
equipment.
Interface Level RS422 RS422 Specifies the

level of the
external time
port.
NOTE
For the NE, this
parameter can
be set to
RS422 only.

B.9.4.6 Parameter Description: External Time Port_BMC

This topic describes BMC parameters for an external time port.
Navigation Path
Function Tree.
2. Click the BMC tab.

External Time - - Displays the

Interface information about the
external time port.
Time Quality Level 0-255 187 ● The smaller the

parameter value,
the higher the
quality level.
recommended.
Time Precision 0-255 254 ● The smaller the

parameter value,
the higher the time
accuracy.
recommended.
Clock Source Type ATOMIC_CLOCK INTERNAL_OSCILLATO Specifies the source of

GPS R an external clock. For
example, if an external
TERRESTRIAL_RADIO clock is obtained by
PTP means of GPS, set this
NTP parameter to GPS.
HAND_SET
OTHER
INTERNAL_OSCILLATO
R
Clock Source Priority 0-255 128 The smaller the

1 parameter value, the
higher the priority.

Clock Source Priority 0-255 128 The smaller the

2 parameter value, the
higher the clock
priority.
NOTE
Select the optimal clock
source according to the
following preference
sequence: Clock source
priority 1 > Time
precision > Time quality
level > Clock source
priority 2.
B.9.4.7 Parameter Description: External Time Port_Cable Transmission

Distance
This topic describes parameters that are related to the transmission distances of
cables connected to external time ports.
Navigation Path
Function Tree.
2. Click the Cable Transmitting Distance tab.

External Time - - Displays the name of

Interface the external time port.
Transmitting Egress - Displays the time

Direction Ingress input/output direction.

Transmitting Length Length ● Specifies the

Distance Mode Time transmission delay
compensation
mode.
● If the parameter is
set to Length,
delay
compensation is
performed based
on the distance
between the
external time port
and the external
equipment.
● If the parameter is
set to Time , delay
compensation is
performed based
on the transmission
time between the
external time port
and the external
equipment.
Transmitting 0-300 0 ● Specifies the cable

Length(m) length between the
external time port
and the external
equipment.
be set when
Transmitting
Distance Mode is
Length.
Transmitting 0-1350 0 ● Specifies the

Time(ns) relevant
transmission delay
between the
external time port
and the external
equipment.
be set when
Transmitting
Distance Mode is
Time.

B.9.5 Parameter Description: Auxiliary Ports

This section describes the parameters required for configuring auxiliary ports.
Navigation Path
In the NE Explorer, select the desired NE from the Object Tree and choose
Configuration > Auxiliary Interface from the Function Tree.

Port - - Displays the port that

functions as the
auxiliary port.

Interface Mode - - ● For OptiX RTN

950/950A(CSHO)/
980/980L, the ID of
the outdoor cabinet
monitoring port is
2.
● For OptiX RTN
905/910A/
950A(CSHOF), the
ID of the outdoor
cabinet monitoring
port is 1.
● For OptiX RTN
950/950A/
980/980L/910A, if
the outdoor cabinet
of the NE is
monitored through
an outdoor cabinet
monitoring port,
set Interface Mode
to MON for the
outdoor cabinet
monitoring port.
if the outdoor
cabinet of the NE is
monitored through
an outdoor cabinet
monitoring port,
set Interface Mode
to External clock
(Hz)+outdoor
cabinet for the
outdoor cabinet
monitoring port.
B.10 Parameters for the Orderwire and Auxiliary

Interfaces
This topic describes the parameters that are related to the orderwire and auxiliary
interfaces.
B.10.1 Parameter Description: Orderwire_General

This topic describes the parameters that are used for general orderwire features.

Navigation Path
> Orderwire from the Function Tree.
2. Click the General tab.
Parameters
Call Waiting 1 to 9 9 ● This parameter indicates the

Time(s) waiting time after the local station
dials the number. If the calling
station does not receive the
response message from the called
station within the call waiting
time, it automatically removes the
communication connection.
● If less than 30 nodes exist in the
orderwire subnet, it is
parameter to five seconds. If more
than 30 nodes exist in the
orderwire subnet, it is
parameter to nine seconds.
● The call waiting time should be set
to the same for all the NEs.
Dialling Mode Pulse Dual-Tone This parameter indicates the dialing

Dual-Tone Frequency mode of the orderwire phone.
Frequency

Conference Call - 888 ● This parameter indicates the

telephone number of the network-
wide orderwire conference call.
● When an NE dials the telephone
number 888, the orderwire phones
of all the NEs on the orderwire
subnet ring. When an NE receives
the call, the orderwire phones on
the other NEs do not ring. In this
case, the orderwire point-to-
multipoint group call changes to a
point-to-point call between two
NEs.
● The telephone number of the
orderwire conference call should
be the same for all the nodes on
the same subnet.
● The telephone number of the
orderwire conference call must
have the same length as the
telephone number of the
orderwire phone (phone 1) at the
local site.
Phone 1 100 to 99999999 101 ● This parameter specifies the

orderwire phone number of the
local station. An addressing call
refers to a point-to-point call.
● The length of the orderwire phone
number of each NE should be the
same. It is recommended that you
set the phone number to a three-
digit number.
● The orderwire phone number of
each NE should be unique. It is
recommended that the phone
numbers are allocated from 101
for the NEs in a sequential order
according to the NE IDs.
● The orderwire phone number
cannot be set to the group call
number 888 and cannot start with
888.
Available - - This parameter indicates the available

Orderwire Port port for the orderwire phone.
Selected - - This parameter indicates the selected

Orderwire Port port for the orderwire phone.

B.10.2 Parameter Description: Orderwire_Advanced

This topic describes the parameters that are used for advanced orderwire features.
Navigation Path
2. Click the Advanced tab.
Parameters for Bytes Occupied by Orderwire Phones

Orderwire E1 E1 ● This parameter specifies the

Occupied Bytes E2 overhead byte that is used to
transmit the orderwire signals.
● Regardless the parameter value,
the radio link always uses a
customized overhead byte to
transmit the orderwire signals.
Hence, this parameter should be
set according to the occupied SDH
overhead bytes in the ordinary
SDH.
B.10.3 Parameter Description: Orderwire_F1 Data Port

This topic describes the parameters that are used for F1 data ports.
Navigation Path
2. Click the F1 Data Port tab.
Parameters
Available Data - - ● This parameter indicates the

Path available F1 data channel.
● Two data channels should be
selected for the configuration.
Number - - This parameter indicates the number

of the F1 data port.

Data Channel 1 - - ● If a synchronous data port

functions as the data channel, set
Data Channel 2 this parameter to F1.
● If an overhead byte of a
transmission line functions as the
data channel, set this parameter
to the associated line port.
B.10.4 Parameter Description: Orderwire_Broadcast Data Port

This topic describes the parameters that are used for broadcast data ports.
Navigation Path
2. Click the Broadcast Data Port tab.
Parameters for Broadcast Data Ports

Overhead Byte SERIAL1 to SERIAL1 ● In the case of an SDH optical/

SERIAL4 electrical line, the preset overhead
byte is used to transmit
asynchronous data services.
● In the case of a radio link, a
customized serial overhead byte in
the microwave frame is used to
transmit asynchronous data
services.
Broadcast Data - No Data ● If the service source is an

Source asynchronous data port, set this
parameter to SERIAL1.
● If the service source is an
overhead byte of a transmission
line, set this parameter to the
associated line port.
Available - - This parameter indicates the available

Broadcast Data broadcast data sink.
Sink

Selected - - ● If the service sink is an

Broadcast Data asynchronous data port, set this
Sink parameter to SERIAL1.
● If the service sink is an overhead
byte of a transmission line, set this
parameter to the associated line
port.
B.10.5 Parameter Description: Environment Monitoring

Interface
This topic describes the parameters that are used for environment monitoring
interfaces.
Navigation Path
Select the AUX board from the Object Tree in the NE Explorer. Choose
Configuration > Environment Monitor Configuration > Environment Monitor
Parameters for the Basic Attributes

Operation - - This parameter indicates the

Object operation object.
Relay Control Auto Control Auto Control ● Auto Control: If an alarm is

Mode Manual Control reported, the alarming relay is
started up automatically.
Otherwise, the alarming relay is
shut down.
● Manual Control: Relay Status in
Major Alarm(K0) and Relay
Status in Critical Alarm(K1) need
to be set.
Relay Status in Disabled Disabled ● This parameter indicates that the

Major Enabled status of the relay is set manually
Alarm(K0) for major alarms.
● Enable: The relay is set to the
"ON" status for major alarms.
● Disabled: The relay is set to the
"OFF" status for major alarms.
Relay Control Mode is set to
Manual Control.

Relay Status in Disabled Disabled ● This parameter indicates that the

Critical Enabled status of the relay is set manually
Alarm(K1) for critical alarms.
● Enable: The relay is set to the
enabled status for critical alarms.
● Disabled: The relay is set to the
disabled status for critical alarms.
Relay Control Mode is set to
Manual Control.
Parameters for the Input Relay


Path Name - - This parameter indicates or specifies

the name of the channel.
Using Status Unused Unused This parameter specifies whether the

Used alarm interface of the input relay is
used.
Alarm Mode Relay Turns Off/ Relay Turns Off/ ● If this parameter is set to Relay
High Level High Level Turns Off/High Level, an alarm is
Relay Turns generated when the relay is turned
On/Low Level off.
● If this parameter is set to Relay
Turns On/Low Level, an alarm is
generated when the relay is turned
on.
Using Status is set to Used.
Alarm Severity Critical Alarm Critical Alarm This parameter specifies the severity
Major Alarm of the alarm that is generated at the
input relay.
Minor Alarm
Warning Alarm

Parameters for the Output Relay


Path Name - - This parameter indicates or specifies

the name of the output channel.
Use or Not Unused Unused This parameter specifies whether the

Used alarm interface of the output relay is
used.
Parameters for the Temperature Attributes


Monitor Status - - This parameter indicates whether the

temperature attribute is monitored.
Temperature - - This parameter indicates the upper

Upper temperature threshold of the board.
Threshold(DEG.C When the actual temperature is
) higher than the preset value, an
alarm is generated.
Temperature - - This parameter indicates the lower

Lower temperature threshold of the board.
Threshold(DEG.C When the actual temperature is lower
) than the preset value, an alarm is
generated.
Parameters for the Alarm Relay


Alarm Severity Critical Alarm - This parameter indicates the severity

Major Alarm of the alarm.
Minor Alarm
Warning Alarm
Alarm Output CSK-1 CSK-1 This parameter specifies the channel

Channel CSK-2 of the output alarm relay.

Feature Configuration Guide C Glossary
C Glossary
Numerics
3G See Third Generation.
3GPP 3rd Generation Partnership Project
802.1Q in 802.1Q A VLAN feature that allows the equipment to add a VLAN tag to a tagged
(QinQ) frame. The implementation of QinQ is to add a public VLAN tag to a frame
with a private VLAN tag to allow the frame with double VLAN tags to be
transmitted over the service provider's backbone network based on the
public VLAN tag. This provides a layer 2 VPN tunnel for customers and
enables transparent transmission of packets over private VLANs.
A
A/D analog/digit
ABR See available bit rate.
ACAP See adjacent channel alternate polarization.
ACL See Access Control List.
ADM add/drop multiplexer
AF See assured forwarding.
AIS alarm indication signal
ALS See automatic laser shutdown.
AM See adaptive modulation.
APS automatic protection switching
ARP See Address Resolution Protocol.
ASBR See autonomous system boundary router.
ASIC See application-specific integrated circuit.
ATM Asynchronous Transfer Mode
ATPC See automatic transmit power control.

Access Control List A list of entities, together with their access rights, which are authorized to
(ACL) access a resource.
Address Resolution An Internet Protocol used to map IP addresses to MAC addresses. The ARP
Protocol (ARP) protocol enables hosts and routers to determine link layer addresses
through ARP requests and responses. The address resolution is a process by
which the host converts the target IP address into a target MAC address
before transmitting a frame. The basic function of ARP is to use the target
equipment's IP address to query its MAC address.
adaptive A technology that is used to automatically adjust the modulation mode
modulation (AM) according to the channel quality. When the channel quality is favorable, the
equipment uses a high-efficiency modulation mode to improve the
transmission efficiency and the spectrum utilization of the system. When
the channel quality is degraded, the equipment uses the low-efficiency
modulation mode to improve the anti-interference capability of the link
that carries high-priority services.
adjacent channel A channel configuration method, which uses two adjacent channels (a
alternate horizontal polarization wave and a vertical polarization wave) to transmit
polarization (ACAP) two signals.
alarm suppression A method to suppress alarms for the alarm management purpose. Alarms
that are suppressed are no longer reported from NEs.
analog signal A signal in which information is represented with a continuously variable
physical quantity, such as voltage. Because of this constant changing of the
wave shape with regard to its passing a given point in time or space, an
analog signal might have a virtually indefinite number of states or values.
This contrasts with a digital signal that is expressed as a square wave and
therefore has a very limited number of discrete states. Analog signals, with
complicated structures and narrow bandwidth, are vulnerable to external
interference.
application-specific A special type of chip that starts out as a nonspecific collection of logic
integrated circuit gates. Late in the manufacturing process, a layer is added to connect the
(ASIC) gates for a specific function. By changing the pattern of connections, the
manufacturer can make the chip suitable for many needs.
assured forwarding One of the four per-hop behaviors (PHB) defined by the Diff-Serv
(AF) workgroup of IETF. It is suitable for certain key data services that require
assured bandwidth and short delay. For traffic within the bandwidth limit,
AF assures quality in forwarding. For traffic that exceeds the bandwidth
limit, AF degrades the service class and continues to forward the traffic
instead of discarding the packets.
attenuator A device used to increase the attenuation of an Optical Fiber Link. Generally
used to ensure that the signal at the receive end is not too strong.
automatic laser A technique (procedure) to automatically shutdown the output power of
shutdown (ALS) laser transmitters and optical amplifiers to avoid exposure to hazardous
levels.
automatic transmit A method of adjusting the transmit power based on fading of the transmit
power control signal detected at the receiver
(ATPC)

autonomous system A router that exchanges routing information with other autonomous system
boundary router boundary routers.
(ASBR)
available bit rate A kind of service categories defined by the ATM forum. ABR only provides
(ABR) possible forwarding service and applies to the connections that does not
require the real-time quality. It does not provide any guarantee in terms of
cell loss or delay.
B
B-ISDN See broadband integrated services digital network.
BDI See backward defect indication.
BE See best effort.
BER bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIOS See basic input/output system.
BIP See bit interleaved parity.
BPDU See bridge protocol data unit.
BSC See base station controller.
BTS base transceiver station
Bidirectional A fast and independent hello protocol that delivers millisecond-level link
Forwarding failure detection and provides carrier-class availability. After sessions are
Detection (BFD) established between neighboring systems, the systems can periodically send
BFD packets to each other. If one system fails to receive a BFD packet
within the negotiated period, the system regards that the bidirectional link
fails and instructs the upper layer protocol to take actions to recover the
faulty link.
backbone network A network that forms the central interconnection for a connected network.
The communication backbone for a country is WAN. The backbone network
is an important architectural element for building enterprise networks. It
provides a path for the exchange of information between different LANs or
subnetworks. A backbone can tie together diverse networks in the same
building, in different buildings in a campus environment, or over wide
areas. Generally, the backbone network's capacity is greater than the
networks connected to it.
backward defect A function that the sink node of a LSP, when detecting a defect, uses to
indication (BDI) inform the upstream end of the LSP of a downstream defect along the
return path.
base station A logical entity that connects the BTS with the MSC in a GSM/CDMA
controller (BSC) network. It interworks with the BTS through the Abis interface, the MSC
through the A interface. It provides the following functions: radio resource
management, base station management, power control, handover control,
and traffic measurement. One BSC controls and manages one or more BTSs
in an actual network.

basic input/output Firmware stored on the computer motherboard that contains basic input/
system (BIOS) output control programs, power-on self test (POST) programs, bootstraps,
and system setting information. The BIOS provides hardware setting and
control functions for the computer.
baud rate The maximum rate of signal state changes per second on a
communications circuit. If each signal state change corresponds to a code
bit, then the baud rate and the bit rate are the same. It is also possible for
signal state changes to correspond to more than one code bit, so the baud
rate may be lower than the code bit rate.
best effort (BE) A traditional IP packet transport service. In this service, the diagrams are
forwarded following the sequence of the time they reach. All diagrams
share the bandwidth of the network and routers. The amount of resource
that a diagram can use depends of the time it reaches. BE service does not
ensure any improvement in delay time, jitter, packet loss ratio, and high
reliability.
bit interleaved A method of error monitoring. With even parity, the transmitting equipment
parity (BIP) generates an X-bit code over a specified portion of the signal in such a
manner that the first bit of the code provides even parity over the first bit
of all X-bit sequences in the covered portion of the signal, the second bit
provides even parity over the second bit of all X-bit sequences within the
specified portion, and so forth. Even parity is generated by setting the BIP-X
bits so that an even number of 1s exist in each monitored partition of the
signal. A monitored partition comprises all bits in the same bit position
within the X-bit sequences in the covered portion of the signal. The covered
portion includes the BIP-X.
bridge A device that connects two or more networks and forwards packets among
them. Bridges operate at the physical network level. Bridges differ from
repeaters because bridges store and forward complete packets, while
repeaters forward all electrical signals. Bridges differ from routers because
bridges use physical addresses, while routers use IP addresses.
bridge protocol data Data messages exchanged across switches within an extended LAN that
unit (BPDU) uses a spanning tree protocol (STP) topology. BPDU packets contain
information on ports, addresses, priorities, and costs, and they ensure that
the data reaches its intended destination. BPDU messages are exchanged
across bridges to detect loops in a network topology. These loops are then
removed by shutting down selected bridge interfaces and placing redundant
switch ports in a backup, or blocked, state.
broadband A standard defined by the ITU-T to handle high-bandwidth applications,
integrated services such as voice. It currently uses the ATM technology to transmit data over
digital network (B- SONNET-based circuits at 155 to 622 Mbit/s or higher speed.
ISDN)
broadcast A means of delivering information to all members in a network. The
broadcast range is determined by the broadcast address.
broadcast domain A group of network stations that receives broadcast packets originating
from any device within the group. The broadcast domain also refers to the
set of ports between which a device forwards a multicast, broadcast, or
unknown destination frame.

C
CAD See router.
CAR committed access rate
CBS See committed burst size.
CC See continuity check.
CCDP See co-channel dual polarization.
CDMA See code division multiple access.
CE See customer edge.
CES See circuit emulation service.
CGMP Cisco Group Management Protocol
CIST See Common and Internal Spanning Tree.
CLNP connectionless network protocol
CM connection management
CORBA See Common Object Request Broker Architecture.
CPU See Central Processing Unit.
CRC See cyclic redundancy check.
CSES consecutive severely errored second
CSMA/CD See carrier sense multiple access with collision detection.
CTC common transmit clock
CW control word
Central Processing The computational and control unit of a computer. The CPU is the device
Unit (CPU) that interprets and executes instructions. The CPU has the ability to fetch,
decode, and execute instructions and to transfer information to and from
other resources over the computer's main data-transfer path, the bus.
Common Object A specification developed by the Object Management Group in 1992 in
Request Broker which pieces of programs (objects) communicate with other objects in
Architecture other programs, even if the two programs are written in different
(CORBA) programming languages and are running on different platforms. A program
makes its request for objects through an object request broker, or ORB, and
therefore does not need to know the structure of the program from which
the object comes. CORBA is designed to work in object-oriented
environments.
Common and The single spanning tree jointly calculated by STP and RSTP, the logical
Internal Spanning connectivity using MST bridges and regions, and MSTP. The CIST ensures
Tree (CIST) that all LANs in the bridged local area network are simply and fully
connected.
cable tie A cable tie (also known as a wire tie, hose tie, steggel tie, or zip tie, and by
the brand names Ty-Rap) is a type of fastener, for holding items together,
primarily electrical cables or wires.

carrier sense Carrier sense multiple access with collision detection (CSMA/CD) is a
multiple access with computer networking access method in which: a carrier sensing scheme is
collision detection used. a transmitting data station that detects another signal while
(CSMA/CD) transmitting a frame, stops transmitting that frame, transmits a jam signal,
and then waits for a random time interval before trying to send that frame
again.
channel A telecommunication path of a specific capacity and/or speed between two
or more locations in a network. The channel can be established through
wire, radio (microwave), fiber, or any combination of the three. The amount
of information transmitted per second in a channel is the information
transmission speed, expressed in bits per second. For example, b/s (100
bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s (1012
bit/s).
circuit emulation A function with which the E1/T1 data can be transmitted through ATM
service (CES) networks. At the transmission end, the interface module packs timeslot
data into ATM cells. These ATM cells are sent to the reception end through
the ATM network. At the reception end, the interface module re-assigns the
data in these ATM cells to E1/T1 timeslots. The CES technology guarantees
that the data in E1/T1 timeslots can be recovered to the original sequence
at the reception end.
clock tracing The method of keeping the time on each node synchronized with a clock
source in the network.
co-channel dual A channel configuration method, which uses a horizontal polarization wave
polarization (CCDP) and a vertical polarization wave to transmit two signals. The Co-Channel
Dual Polarization has twice the transmission capacity of the single
polarization.
code division A communication scheme that uses frequency expansion technology to
multiple access form different code sequences. When the CDMA scheme is used, subscribers
(CDMA) with different addresses can use different code sequences for multi-address
connection.
committed burst A parameter used to define the capacity of token bucket C, that is, the
size (CBS) maximum burst IP packet size when information is transferred at the
committed information rate. This parameter must be greater than 0 but
should be not less than the maximum length of an IP packet to be
forwarded.
continuity check An Ethernet connectivity fault management (CFM) method used to detect
(CC) the connectivity between MEPs by having each MEP periodically transmit a
Continuity Check Message (CCM).
cross-polarization A technology used in the case of the Co-Channel Dual Polarization (CCDP)
interference to eliminate the cross-connect interference between two polarization waves
cancellation (XPIC) in the CCDP.
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly
connecting to the Service Provider (SP) network. A CE can be a router,
switch, or host.
cyclic redundancy A mathematical checksum that can be used to detect data corruption in
check (CRC) transmitted frames. The CRC is a linear hash function, and should not be
used for data security assurance.

D
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common A power system, in which the BGND of the DC return conductor is short-
(with ground) (DC- circuited with the PGND on the output side of the power supply cabinet and
C) also on the line between the output of the power supply cabinet and the
electric equipment.
DC-return isolate A power system, in which the BGND of the DC return conductor is short-
(with ground) (DC- circuited with the PGND on the output side of the power supply cabinet and
I) is isolated from the PGND on the line between the output of the power
supply cabinet and the electric equipment.
DCN See data communication network.
DDF digital distribution frame
DDN See digital data network.
DE discard eligible
DM See delay measurement.
DS boundary node A DS node that connects one DS domain to a node either in another DS
domain or in a domain that is not DS-capable.
DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary
node.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID
interior node.
DSCP See differentiated services code point.
DVMRP See Distance Vector Multicast Routing Protocol.
Distance Vector An Internet gateway protocol based primarily on the RIP. The DVMRP
Multicast Routing protocol implements a typical dense mode IP multicast solution and uses
Protocol (DVMRP) IGMP to exchange routing datagrams with its neighbors.
data communication A communication network used in a TMN or between TMNs to support the
network (DCN) data communication function.
delay measurement The time elapsed since the start of transmission of the first bit of the frame
(DM) by a source node until the reception of the last bit of the loopbacked frame
by the same source node, when the loopback is performed at the frame's
destination node.
differentiated According to the QoS classification standard of the Differentiated Service
services code point (Diff-Serv), the type of services (ToS) field in the IP header consists of six
(DSCP) most significant bits and two currently unused bits, which are used to form
codes for priority marking. Differentiated services code point (DSCP) is the
six most important bits in the ToS. It is the combination of IP precedence
and types of service. The DSCP value is used to ensure that routers
supporting only IP precedence can be used because the DSCP value is
compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB).
Therefore, terminal devices can identify traffic using the DSCP value.

digital data network A data transmission network that is designed to transmit data on digital
(DDN) channels (such as the fiber channel, digital microwave channel, or satellite
channel).
digital modulation A method that controls the changes in amplitude, phase, and frequency of
the carrier based on the changes in the baseband digital signal. In this
manner, the information can be transmitted by the carrier.
dual-polarized An antenna intended to simultaneously radiate or receive two independent
antenna radio waves orthogonally polarized.
E
E-Aggr See Ethernet aggregation.
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
ECC See embedded control channel.
EMC See electromagnetic compatibility.
EMI See electromagnetic interference.
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPLD See erasable programmable logic device.
ERPS Ethernet ring protection switching
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVPL See Ethernet virtual private line.
EVPLAN See Ethernet virtual private LAN service.
Ethernet A LAN technology that uses the carrier sense multiple access with collision
detection (CSMA/CD) media access control method. The Ethernet network
is highly reliable and easy to maintain. The speed of an Ethernet interface
can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s, or 10,000 Mbit/s.
Ethernet A type of Ethernet service that is based on a multipoint-to-point EVC
aggregation (E- (Ethernet virtual connection).
Aggr)
Ethernet line (E- A type of Ethernet service that is based on a point-to-point EVC (Ethernet
Line) virtual connection).
Ethernet local area A type of Ethernet service that is based on a multipoint-to-multipoint EVC
network (E-LAN) (Ethernet virtual connection).
Ethernet private A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server
LAN service layer networks. This service is carried over dedicated bandwidth between
(EPLAN) multipoint-to-multipoint connections.
Ethernet private line A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server
(EPL) layer networks. This service is carried over dedicated bandwidth between
point-to-point connections.

Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server
private LAN service layer networks. This service is carried over shared bandwidth between
(EVPLAN) multipoint-to-multipoint connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server
private line (EVPL) layer networks. This service is carried over shared bandwidth between
point-to-point connections.
European ETSI is a multinational standardization body with regulatory and
Telecommunications standardization authority over much of Europe. GSM standardization took
Standards Institute place under the auspices of ETSI.
(ETSI)
electromagnetic A condition which prevails when telecommunications equipment is
compatibility (EMC) performing its individually designed function in a common electromagnetic
environment without causing or suffering unacceptable degradation due to
unintentional electromagnetic interference to or from other equipment in
the same environment.
electromagnetic Any electromagnetic disturbance that interrupts, obstructs, or otherwise
interference (EMI) degrades or limits the performance of electronics/electrical equipment.
embedded control A logical channel that uses a data communications channel (DCC) as its
channel (ECC) physical layer to enable the transmission of operation, administration, and
maintenance (OAM) information between NEs.
engineering label A mark on a cable, a subrack, or a cabinet for identification.
erasable A logic array device which can be used to implement the required functions
programmable logic by programming the array. In addition, a user can modify and program the
device (EPLD) array repeatedly until the program meets the requirement.
F
FD See frequency diversity.
FDDI See fiber distributed data interface.
FDI See forward defect indication.
FEC See forward error correction.
FFD fast failure detection
FFD packet A path failure detection method independent from CV. Different from a CV
packet, the frequency for generating FFD packets is configurable to satisfy
different service requirements. By default, the frequency is 20/s. An FFD
packet contains information the same as that in a CV packet. The
destination end LSR processes FFD packets in the same way for processing
CV packets.
FIFO See first in first out.
FPGA See field programmable gate array.
FTP File Transfer Protocol
fiber distributed A standard developed by the American National Standards Institute (ANSI)
data interface for high-speed fiber-optic LANs. FDDI provides specifications for
(FDDI) transmission rates of 100 megabits per second on token ring networks.

field programmable A semi-customized circuit that is used in the Application Specific Integrated
gate array (FPGA) Circuit (ASIC) field and developed based on programmable components.
FPGA remedies many of the deficiencies of customized circuits, and allows
the use of many more gate arrays.
first in first out A stack management method in which data that is stored first in a queue is
(FIFO) also read and invoked first.
forward defect A packet generated and traced forward to the sink node of the LSP by the
indication (FDI) node that first detects defects. It includes fields to indicate the nature of the
defect and its location. Its primary purpose is to suppress alarms being
raised at affected higher level client LSPs and (in turn) their client layers.
forward error A bit error correction technology that adds correction information to the
correction (FEC) payload at the transmit end. Based on the correction information, the bit
errors generated during transmission can be corrected at the receive end. A
technique used for controlling errors in data transmission over unreliable or
noisy communication channels.
fragmentation A process of breaking a packet into smaller units when transmitting over a
network node that does not support the original size of the packet.
frequency diversity The signal is transmitted using several frequency channels or spread over a
(FD) wide spectrum that is affected by frequency-selective fading.
G
GCRA generic cell rate algorithm
GFC generic flow control
GFP See Generic Framing Procedure.
GNE See gateway network element.
GPS See Global Positioning System.
GTS See generic traffic shaping.
GUI graphical user interface
Generic Framing A framing and encapsulated method that can be applied to any data type.
Procedure (GFP) GFP is defined by ITU-T G.7041.
Global Positioning A global navigation satellite system that provides reliable positioning,
System (GPS) navigation, and timing services to users worldwide.
gateway A device that receives data via one protocol and transmits it via another.
gateway network An NE that serves as a gateway for other NEs to communicate with a
element (GNE) network management system.
generic traffic A traffic control measure that proactively adjusts the output speed of the
shaping (GTS) traffic. This is to adapt the traffic to network resources that can be provided
by the downstream router to avoid packet discarding and congestion.
H
HQoS See hierarchical quality of service.
HSDPA See High Speed Downlink Packet Access.

HSM hitless switch mode

High Speed A modulating-demodulating algorithm put forward in 3GPP R5 to meet the
Downlink Packet requirement for asymmetric uplink and downlink transmission of data
Access (HSDPA) services. It enables the maximum downlink data service rate to reach 14.4
Mbit/s without changing the WCDMA network topology.
hierarchical quality A type of QoS that controls the traffic of users and performs the scheduling
of service (HQoS) according to the priority of user services. HQoS has an advanced traffic
statistics function, and the administrator can monitor the usage of
bandwidth of each service. Hence, the bandwidth can be allocated
reasonably through traffic analysis.
I
I/O input/output
ICMP See Internet Control Message Protocol.
IDU See indoor unit.
IEEE See Institute of Electrical and Electronics Engineers.
IGMP See Internet Group Management Protocol.
IGP See Interior Gateway Protocol.
IP Internet Protocol
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
ISDN Integrated Services Digital Network
IST internal spanning tree
ITU See International Telecommunication Union.
Institute of A professional association of electrical and electronics engineers based in
Electrical and the United States, but with membership from numerous other countries.
Electronics The IEEE focuses on electrical, electronics, and computer engineering, and
Engineers (IEEE) produces many important technology standards.
Interior Gateway 1. A routing protocol that is used within an autonomous system. The IGP
Protocol (IGP) runs in small-sized and medium-sized networks. The IGPs are RIP, IGRP,
EIGRP, OSPF, and IS-IS. 2. The routing protocol spoken by the routers
belonging to an Autonomous system. Abbreviated as IGP. Each Autonomous
System has a single IGP. Separate Autonomous Systems may be running
different IGPs.
International A United Nations agency, one of the most important and influential
Telecommunication recommendation bodies, responsible for recommending standards for
Union (ITU) telecommunication (ITU-T) and radio networks (ITU-R).
Internet Control A network layer protocol that provides message control and error reporting
Message Protocol between a host server and an Internet gateway.
(ICMP)
Internet Group One of the TCP/IP protocols for managing the membership of Internet
Management Protocol multicast groups. It is used by IP hosts and adjacent multicast
Protocol (IGMP) routers to establish and maintain multicast group memberships.

Internet Protocol The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit
version 4 (IPv4) address which is assigned to hosts. An address belongs to one of five classes
(A, B, C, D, or E) and is written as 4 octets separated by periods and may
range from 0.0.0.0 through to 255.255.255.255. Each IPv4 address consists
of a network number, an optional subnetwork number, and a host number.
The network and subnetwork numbers together are used for routing, and
the host number is used to address an individual host within the network or
subnetwork.
Internet Protocol An update version of IPv4, which is designed by the Internet Engineering
version 6 (IPv6) Task Force (IETF) and is also called IP Next Generation (IPng). It is a new
version of the Internet Protocol. The difference between IPv6 and IPv4 is
that an IPv4 address has 32 bits while an IPv6 address has 128 bits.
indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements
accessing, multiplexing/demultiplexing, and intermediate frequency (IF)
processing for services.
L
L2VPN Layer 2 virtual private network
LACP See Link Aggregation Control Protocol.
LAG See link aggregation group.
LAN See local area network.
LAPS Link Access Protocol-SDH
LB See loopback.
LCAS See link capacity adjustment scheme.
LM See loss measurement.
LOS See loss of signal.
LPT link-state pass through
LSDB link state database
LSP tunnel An LSP over which traffic is transmitted based on labels that are assigned to
FECs on the ingress. The traffic is transparent to the intermediate nodes
LSR See label switching router.
LTE Long Term Evolution
Layer 2 switching A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet
switch transmits and distributes packet data based on the MAC address.
Since the MAC address is at the second layer of the OSI model, this data
forwarding method is called Layer 2 switching.
Link Aggregation A dynamic link aggregation protocol that improves the transmission speed
Control Protocol and reliability. The two ends of the link send LACP packets to inform each
(LACP) other of their parameters and form a logical aggregation link. After the
aggregation link is formed, LACP maintains the link status in real time and
dynamically adjusts the ports on the aggregation link upon detecting the
failure of a physical port.

label switching Basic element of an MPLS network. All LSRs support the MPLS protocol.
router (LSR) The LSR is composed of two parts: control unit and forwarding unit. The
former is responsible for allocating the label, selecting the route, creating
the label forwarding table, creating and removing the label switch path; the
latter forwards the labels according to groups received in the label
forwarding table.
laser A component that generates directional optical waves of narrow
wavelengths. The laser light has better coherence than ordinary light. Semi-
conductor lasers provide the light used in a fiber system.
line rate The maximum packet forwarding capacity on a cable. The value of line rate
equals the maximum transmission rate capable on a given type of media.
link aggregation An aggregation that allows one or more links to be aggregated together to
group (LAG) form a link aggregation group so that a MAC client can treat the link
aggregation group as if it were a single link.
link capacity LCAS in the virtual concatenation source and sink adaptation functions
adjustment scheme provides a control mechanism to hitless increase or decrease the capacity of
(LCAS) a link to meet the bandwidth needs of the application. It also provides a
means of removing member links that have experienced failure. The LCAS
assumes that in cases of capacity initiation, increases or decreases, the
construction or destruction of the end-to-end path is the responsibility of
the network and element management systems.
local area network A network formed by the computers and workstations within the coverage
(LAN) of a few square kilometers or within a single building, featuring high speed
and low error rate. Current LANs are generally based on switched Ethernet
or Wi-Fi technology and run at 1,000 Mbit/s (that is, 1 Gbit/s).
loopback (LB) A troubleshooting technique that returns a transmitted signal to its source
so that the signal or message can be analyzed for errors. The loopback can
be a inloop or outloop.
loss measurement A method used to collect counter values applicable for ingress and egress
(LM) service frames where the counters maintain a count of transmitted and
received data frames between a pair of MEPs.
loss of signal (LOS) No transitions occurring in the received signal.
M
MA maintenance association
MAC See Media Access Control.
MADM multiple add/drop multiplexer
MBS maximum burst size
MD See maintenance domain.
MDI medium dependent interface
MEP maintenance association end point
MIB See management information base.
MLPPP Multi-Link Point-to-Point Protocol

MP maintenance point
MPLS See Multiprotocol Label Switching.
MPLS L2VPN A network that provides the Layer 2 VPN service based on an MPLS
network. In this case, on a uniform MPLS network, the carrier is able to
provide Layer 2 VPNs of different media types, such as ATM, FR, VLAN,
Ethernet, and PPP.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MS multiplex section
MSP See multiplex section protection.
MST region See multiple spanning tree region.
MSTI See multiple spanning tree instance.
MSTP See Multiple Spanning Tree Protocol.
MTBF See mean time between failures.
MTTR See Mean Time to Repair.
MTU See maximum transmission unit.
Mean Time to The average time that a device will take to recover from a failure.
Repair (MTTR)
Media Access A protocol at the media access control sublayer. The protocol is at the lower
Control (MAC) part of the data link layer in the OSI model and is mainly responsible for
controlling and connecting the physical media at the physical layer. When
transmitting data, the MAC protocol checks whether to be able to transmit
data. If the data can be transmitted, certain control information is added to
the data, and then the data and the control information are transmitted in
a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is
transmitted correctly. If the information is correct and the data is
transmitted correctly, the control information is removed from the data and
then the data is transmitted to the LLC layer.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the
Tree Protocol MSTP blocks redundant paths so that the loop network can be trimmed as
(MSTP) a tree network. In this case, the proliferation and endless cycling of packets
is avoided in the loop network. The protocol that introduces the mapping
between VLANs and multiple spanning trees. This solves the problem that
data cannot be normally forwarded in a VLAN because in STP/RSTP, only
one spanning tree corresponds to all the VLANs.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in
Switching (MPLS) different link layers, and provides connection-oriented switching for the
network layer on the basis of IP routing and control protocols.
maintenance The network or the part of the network for which connectivity is managed
domain (MD) by connectivity fault management (CFM). The devices in a maintenance
domain are managed by a single Internet service provider (ISP).

management A type of database used for managing the devices in a communications

information base network. It comprises a collection of objects in a (virtual) database used to
(MIB) manage entities (such as routers and switches) in a network.
maximum The largest packet of data that can be transmitted on a network. MTU size
transmission unit varies, depending on the network-576 bytes on X.25 networks, for example,
(MTU) 1500 bytes on Ethernet, and 17,914 bytes on 16 Mbit/s token ring.
Responsibility for determining the size of the MTU lies with the link layer of
the network. When packets are transmitted across networks, the path MTU,
or PMTU, represents the smallest packet size (the one that all networks can
transmit without breaking up the packet) among the networks involved.
mean time between The average time between consecutive failures of a piece of equipment. It is
failures (MTBF) a measure of the reliability of the system.
multicast A process of transmitting data packets from one source to many
destinations. The destination address of the multicast packet uses Class D
address, that is, the IP address ranges from 224.0.0.0 to 239.255.255.255.
Each multicast address represents a multicast group rather than a host.
multiple spanning A type of spanning trees calculated by MSTP within an MST Region, to
tree instance (MSTI) provide a simply and fully connected active topology for frames classified as
belonging to a VLAN that is mapped to the MSTI by the MST Configuration.
A VLAN cannot be assigned to multiple MSTIs.
multiple spanning A region that consists of switches that support the MSTP in the LAN and
tree region (MST links among them. Switches physically and directly connected and
region) configured with the same MST region attributes belong to the same MST
region.
multiplex section A function, which is performed to provide capability for switching a signal
protection (MSP) between and including two multiplex section termination (MST) functions,
from a "working" to a "protection" channel.
multiprotocol label An Internet Protocol (IP) virtual private network (VPN) based on the
switching virtual multiprotocol label switching (MPLS) technology. It applies the MPLS
private network technology for network routers and switches, simplifies the routing mode of
(MPLS VPN) core routers, and combines traditional routing technology and label
switching technology. It can be used to construct the broadband Intranet
and Extranet to meet various service requirements.
N
N+1 protection A radio link protection system composed of N working channels and one
protection channel.
NE network element
NE Explorer The main operation interface, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query,
manage, and maintain NEs, boards, and ports.
NNI Network-to-Network Interface
NPE network provider edge
NSAP See network service access point.
NSF non-stop forwarding

network service A network address defined by ISO, at which the OSI Network Service is
access point (NSAP) made available to a Network service user by the Network service provider.
network storm A phenomenon that occurs during data communication. To be specific,
mass broadcast packets are transmitted in a short time; the network is
congested; transmission quality and availability of the network decrease
rapidly. The network storm is caused by network connection or
configuration problems.
non-GNE See non-gateway network element.
non-gateway A network element that communicates with the NM application layer
network element through the gateway NE application layer.
(non-GNE)
O
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
ODF optical distribution frame
OSPF See Open Shortest Path First.
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing
First (OSPF) that uses cost as its routing metric. A link state database is constructed of
the network topology, which is identical on all routers in the area.
operation, A set of network management functions that cover fault detection,
administration and notification, location, and repair.
maintenance (OAM)
orderwire A channel that provides voice communication between operation engineers
or maintenance engineers of different stations.
P
PDH See plesiochronous digital hierarchy.
PE See provider edge.
PHB See per-hop behavior.
PLA See physical link aggregation.
PLL See phase-locked loop.
PRBS See pseudo random binary sequence.
PRI Primary Rate Interface
PSN See packet switched network.
PTN packet transport network
PTP Precision Time Protocol
PTP clock See Precision Time Protocol clock.
PVP See permanent virtual path.
PW See pseudo wire.

PWE3 See Pseudowire Emulation Edge-to-Edge.

Precision Time A type of high-decision clock defined by the IEEE 1588 V2 standard. The
Protocol clock (PTP IEEE 1588 V2 standard specifies the precision time protocol (PTP) in a
clock) measurement and control system. The PTP protocol ensures clock
synchronization precise to sub-microseconds.
Pseudowire An end-to-end Layer 2 transmission technology. It emulates the essential
Emulation Edge-to- attributes of a telecommunication service such as ATM, FR or Ethernet in a
Edge (PWE3) packet switched network (PSN). PWE3 also emulates the essential
attributes of low speed time division multiplexing (TDM) circuit and
SONET/SDH. The simulation approximates to the real situation.
packet switched A telecommunications network that works in packet switching mode.
network (PSN)
per-hop behavior IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as
(PHB) per-hop behaviors (PHB), such as, traffic scheduling and policing. A device
in the network should select the proper PHB behaviors, based on the value
of DSCP. At present, the IETF defines four types of PHB. They are class
selector (CS), expedited forwarding (EF), assured forwarding (AF), and best-
effort (BE).
permanent virtual Virtual path that consists of PVCs.
path (PVP)
phase-locked loop A circuit that consists essentially of a phase detector that compares the
(PLL) frequency of a voltage-controlled oscillator with that of an incoming carrier
signal or reference-frequency generator. The output of the phase detector,
after passing through a loop filter, is fed back to the voltage-controlled
oscillator to keep it exactly in phase with the incoming or reference
frequency.
physical link Being a technology providing load balancing based on physical layer
aggregation (PLA) bandwidths, physical link aggregation (PLA) combines Ethernet
transmission paths in several Integrated IP radio links into a logical Ethernet
link for higher Ethernet bandwidth and Ethernet transmission reliability.
plesiochronous A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes
digital hierarchy the minimum rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and
(PDH) 565 Mbit/s.
polarization A kind of electromagnetic wave, the direction of whose electric field vector
is fixed or rotates regularly. Specifically, if the electric field vector of the
electromagnetic wave is perpendicular to the plane of horizon, this
electromagnetic wave is called vertically polarized wave; if the electric field
vector of the electromagnetic wave is parallel to the plane of horizon, this
electromagnetic wave is called horizontal polarized wave; if the tip of the
electric field vector, at a fixed point in space, describes a circle, this
electromagnetic wave is called circularly polarized wave.
provider edge (PE) A device that is located in the backbone network of the MPLS VPN
structure. A PE is responsible for managing VPN users, establishing LSPs
between PEs, and exchanging routing information between sites of the
same VPN. A PE performs the mapping and forwarding of packets between
the private network and the public channel. A PE can be a UPE, an SPE, or
an NPE.

pseudo random A sequence that is random in the sense that the value of each element is
binary sequence independent of the values of any of the other elements, similar to a real
(PRBS) random sequence.
pseudo wire (PW) An emulated connection between two PEs for transmitting frames. The PW
is established and maintained by PEs through signaling protocols. The
status information of a PW is maintained by the two end PEs of a PW.
Q
QPSK See quadrature phase shift keying.
QinQ See 802.1Q in 802.1Q.
quadrature phase A variation of BPSK, and it is also a Double Side Band Suppressed Carrier
shift keying (QPSK) (DSBSC) modulation scheme, which sends two bits of digital information at
a time, called as bigits.
R
RADIUS accounting An accounting mode in which the BRAS sends the accounting packets to
the RADIUS server. Then the RADIUS server performs accounting.
RDI remote defect indication
RED See random early detection.
REI remote error indication
RFC See Request For Comments.
RMEP remote maintenance association end point
RMON remote network monitoring
RNC See radio network controller.
RSL See received signal level.
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
RTN radio transmission node
RTSP Real-Time Streaming Protocol
Rapid Spanning Tree An evolution of the Spanning Tree Protocol (STP) that provides faster
Protocol (RSTP) spanning tree convergence after a topology change. The RSTP protocol is
backward compatible with the STP protocol.
Request For A document in which a standard, a protocol, or other information
Comments (RFC) pertaining to the operation of the Internet is published. The RFC is actually
issued, under the control of the IAB, after discussion and serves as the
standard. RFCs can be obtained from sources such as InterNIC.
Resource A protocol that reserves resources on every node along a path. RSVP is
Reservation Protocol designed for an integrated services Internet.
(RSVP)
RoHS restriction of the use of certain hazardous substances

radio network A device in a radio network subsystem that is in charge of controlling the
controller (RNC) usage and integrity of radio resources.
random early A packet loss algorithm used in congestion avoidance. It discards the packet
detection (RED) according to the specified higher limit and lower limit of a queue so that
global TCP synchronization resulting from traditional tail drop can be
prevented.
real-time variable A parameter intended for real-time applications, such as compressed voice
bit rate (rt-VBR) over IP (VoIP) and video conferencing. The rt-VBR is characterized by a peak
cell rate (PCR), sustained cell rate (SCR), and maximum burst size (MBS).
You can expect the source device to transmit in bursts and at a rate that
varies with time.
received signal level The signal level at a receiver input terminal.
(RSL)
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a
reference point at an input to a receiver optical connector) to achieve a
1x10-12 BER when the FEC is enabled.
regeneration The process of receiving and reconstructing a digital signal so that the
amplitudes, waveforms and timing of its signal elements are constrained
within specified limits.
route The path that network traffic takes from its source to its destination. On a
TCP/IP network, each IP packet is routed independently. Routes can change
dynamically.
router (CAD) A device on the network layer that selects routes in the network. The router
selects the optimal route according to the destination address of the
received packet through a network and forwards the packet to the next
router. The last router is responsible for sending the packet to the
destination host. Can be used to connect a LAN to a LAN, a WAN to a
WAN, or a LAN to the Internet.
rt-VBR See real-time variable bit rate.
S
SAI service area identifier
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SD See space diversity.
SDH See synchronous digital hierarchy.
SES severely errored second
SETS SDH equipment timing source
SF See signal fail.
SFP small form-factor pluggable
SLA See Service Level Agreement.
SNCP subnetwork connection protection
SNMP See Simple Network Management Protocol.

SNR See signal-to-noise ratio.

SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
STM See synchronous transport module.
STM-1 See Synchronous Transport Module level 1.
STM-4 Synchronous Transport Module level 4
STM-N Synchronous Transport Module level N
STP Spanning Tree Protocol
Secure Sockets A security protocol that works at a socket layer. This layer exists between
Layer (SSL) the TCP layer and the application layer to encrypt/decode data and
authenticate concerned entities.
Service Level A service contract between a customer and a (SLA) service provider that
Agreement (SLA) specifies the forwarding service a customer should receive. A customer may
be a user organization (source domain) or another DS domain (upstream
domain). A SLA may include traffic conditioning rules which constitute a
TCA in whole or in part.
Simple Network An IETF protocol for monitoring and managing systems and devices in a
Management network. The data being monitored and managed is defined by a MIB. The
Protocol (SNMP) functions supported by the protocol are the request and retrieval of data,
the setting or writing of data, and traps that signal the occurrence of
events.
Synchronization A message that carries the quality levels of timing signals on a synchronous
Status Message timing link. SSM messages provide upstream clock information to nodes on
(SSM) an SDH network or synchronization network.
Synchronous Synchronous transfer mode at 155 Mbit/s.
Transport Module
level 1 (STM-1)
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-
end defect condition (non-degrade defect) is active.
signal-to-noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise
(SNR) signals at a given point in time. SNR is expressed as 10 times the logarithm
of the power ratio and is usually expressed in dB.
single-polarized An antenna intended to radiate or receive radio waves with only one
antenna specified polarization.
space diversity (SD) A diversity scheme that enables two or more antennas separated by a
specific distance to transmit/receive the same signal and selection is then
performed between the two signals to ease the impact of fading. Currently,
only receive SD is used.
subnet mask The subnet mask is a binary pattern that is stored in the device and is
matched with the IP address. A subnet mask is used by the IP protocol to
determine to which network segment packets are destined. Subnet mask
(also known as netmask or address mask) is a 32-bit binary value used over
the TCP/IP network.

synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH
hierarchy (SDH) defines the transmission features of digital signals, such as frame structure,
multiplexing mode, transmission rate level, and interface code. SDH is an
important part of ISDN and B-ISDN.
synchronous An information structure used to support section layer connections in the
transport module SDH. It consists of information payload and Section Overhead (SOH)
(STM) information fields organized in a block frame structure which repeats every
125. The information is suitably conditioned for serial transmission on the
selected media at a rate which is synchronized to the network. A basic STM
is defined at 155 520 kbit/s. This is termed STM-1. Higher capacity STMs
are formed at rates equivalent to N times this basic rate. STM capacities for
N = 4, N = 16 and N = 64 are defined; higher values are under
consideration.
T
T1 A North American standard for high-speed data transmission at 1.544Mbps.
It provides 24 x 64 kbit/s channels.
TCI tag control information
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
TDM See time division multiplexing.
TDMA See time division multiple access.
TEDB See traffic engineering database.
TIM trace identifier mismatch
TMN See telecommunications management network.
TOS test operation system
TTL See time to live.
TUG tributary unit group
Telnet A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet
allows users to log in to remote systems and use resources as if they were
connected to a local system. Telnet is defined in RFC 854.
Third Generation The third generation of digital wireless technology, as defined by the
(3G) International Telecommunications Union (ITU). Third generation technology
is expected to deliver data transmission speeds between 144 kbit/s and 2
Mbit/s, compared to the 9.6 kbit/s to 19.2 kbit/s offered by second
generation technology.
Time Division- A 3G mobile communications standard found in UMTS mobile
Synchronous Code telecommunications networks in China as an alternative to W-CDMA. TD-
Division Multiple SCDMA integrates technologies of CDMA, TDMA, and FDMA, and makes
Access (TD-SCDMA) use of technologies including intelligent antenna, joint detection, low chip
rate (LCR), and adaptive power control. With the flexibility of service
processing, a TD-SCDMA network can connect to other networks through
the RNC.

Transmission The protocol within TCP/IP that governs the breakup of data messages into
Control Protocol packets to be sent using Internet Protocol (IP), and the reassembly and
(TCP) verification of the complete messages from packets received by IP. A
connection-oriented, reliable protocol (reliable in the sense of ensuring
error-free delivery), TCP corresponds to the transport layer in the ISO/OSI
reference model.
tail drop A congestion management mechanism, in which packets arrive later are
discarded when the queue is full. This policy of discarding packets may
result in network-wide synchronization due to the TCP slow startup
mechanism.
telecommunications A protocol model defined by ITU-T for managing open systems in a
management communications network. TMN manages the planning, provisioning,
network (TMN) installation, and OAM of equipment, networks, and services.
time division An approach used for allocating a single channel among many users, by
multiple access dividing the channel into different timeslots during which each user has
(TDMA) access to the medium.
time division A multiplexing technology. TDM divides the sampling cycle of a channel
multiplexing (TDM) into time slots (TSn, n is equal to 0, 1, 2, 3...), and the sampling value codes
of multiple signals engross time slots in a certain order, forming multiple
multiplexing digital signals to be transmitted over one channel.
time to live (TTL) A specified period of time for best-effort delivery systems to prevent
packets from looping endlessly. When writing data into Redis, there may be
a point at which data is no longer needed. We can remove the data
explicitly with DEL, or if we want to remove an entire key after a specified
timeout, we can use what's known as expiration. When we say that a key
has a time to live, or that it'll expire at a given time, we mean that Redis
will automatically delete the key when its expiration time has arrived.
traffic engineering A type of database that every router generates after collecting the
database (TEDB) information about TE of every links in its area. TEDB is the base of forming
the dynamic TE path in the MPLS TE network.
tributary loopback A fault can be located for each service path by performing loopback to each
path of the tributary board. There are three kinds of loopback modes: no
loopback, outloop, and inloop.
tunnel A channel on the packet switching network that transmits service traffic
between PEs. In VPN, a tunnel is an information transmission channel
between two entities. The tunnel ensures secure and transparent
transmission of VPN information. In most cases, a tunnel is an MPLS tunnel.
U
UART universal asynchronous receiver/transmitter
UAS unavailable second
UBR+ Unspecified Bit Rate Plus
UNI See User-to-Network Interface.
UPC See usage parameter control.

User-to-Network The interface between user equipment and private or public network
Interface (UNI) equipment (for example, ATM switches).
unicast The process of sending data from a source to a single recipient.
usage parameter During communications, UPC is implemented to monitor the actual traffic
control (UPC) on each virtual circuit that is input to the network. Once the specified
parameter is exceeded, measures will be taken to control. NPC is similar to
UPC in function. The difference is that the incoming traffic monitoring
function is divided into UPC and NPC according to their positions. UPC
locates at the user/network interface, while NPC at the network interface.
V
V-NNI virtual network-network interface
VB virtual bridge
VC See virtual container.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCI virtual channel identifier
VCTRUNK A virtual concatenation group applied in data service mapping, also called
the internal port of a data service processing board.
VLAN virtual local area network
VPI See virtual path identifier.
VPLS virtual private LAN segment
VPN virtual private network
VSWR voltage standing wave ratio
virtual channel A VC logical trail that carries data between two end points in an ATM
connection (VCC) network. A point-to-multipoint VCC is a set of ATM virtual connections
between two or multiple end points.
virtual circuit A channel or circuit established between two points on a data
communications network with packet switching. Virtual circuits can be
permanent virtual circuits (PVCs) or switched virtual circuits (SVCs) .
virtual A group of co-located member trail termination functions that are
concatenation connected to the same virtual concatenation link.
group (VCG)
virtual container An information structure used to support path layer connections in the
(VC) SDH. A VC consists of a payload and path overhead (POH), which are
organized in a block frame structure that repeats every 125 μs or 500 μs.
virtual path The field in the Asynchronous Transfer Mode (ATM) cell header that
identifier (VPI) identifies to which virtual path the cell belongs.

WCDMA See Wideband Code Division Multiple Access.

WEEE waste electrical and electronic equipment
WFQ See weighted fair queuing.
WRR weighted round robin
WTR See wait to restore.
Web LCT The local maintenance terminal of a transport network, which is located at
the NE management layer of the transport network.
Wideband Code A standard defined by the ITU-T for the third-generation wireless
Division Multiple technology derived from the Code Division Multiple Access (CDMA)
Access (WCDMA) technology.
wait to restore The number of minutes to wait before services are switched back to the
(WTR) working line.
weighted fair A fair queue scheduling algorithm based on bandwidth allocation weights.
queuing (WFQ) This scheduling algorithm allocates the total bandwidth of an interface to
queues, according to their weights and schedules the queues cyclically. In
this manner, packets of all priority queues can be scheduled.
winding pipe A tool for fiber routing, which acts as the corrugated pipe.
X
XPIC See cross-polarization interference cancellation.

RTN 900 V100R020C00 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 V100R020C00 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 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Product Name Version

OptiX RTN 900 V100R020C00

The intended audiences of this document are:

● Installation and commissioning engineer

Indicates a hazard with a high level of risk which, if not

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. ii

Indicates a hazard with a medium level of risk which, if

Indicates a hazard with a low level of risk which, if not

Indicates a potentially hazardous situation which, if not

Supplements the important information in the main text.

Boldface Buttons, menus, parameters, tabs, window, and

> Multi-level menus are in boldface and separated by

Updates in Issue 02 (2020-09-30) Based on Product Version V100R020C00

The document updates are as follows:

- Fixed the known bugs.

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. iii

Security Management Deleted the description of the USB

Updates in Issue 01 (2020-06-30) Based on Product Version V100R020C00

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. iv

About This Document................................................................................................................ ii

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. v

2 Configuring Microwave Features.......................................................................................84

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. vi

2.13.2 Configuration Procedure............................................................................................................................................ 121

3 Configuring SDH Protection Features............................................................................ 135

4 Configuring Native Ethernet Features........................................................................... 146

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. vii

4.16.1 Networking Diagram................................................................................................................................................... 186

5 Configuring MPLS/PWE3 Features.................................................................................. 239

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. viii

5.4 Configuration Procedure (PW OAM_Y.1711)............................................................................................................ 247

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. ix

5.23.1 Network Diagram......................................................................................................................................................... 298

6 Configuring Clock Features.............................................................................................. 302

7 Configuring Maintenance Features................................................................................ 348

A Task Collection.................................................................................................................... 361

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. x

A.1 NCE Quick Start.................................................................................................................................................................. 361

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xi

A.3.6 Managing Subnets......................................................................................................................................................... 407

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xii

A.4.1.5 Querying NE User Groups........................................................................................................................................ 446

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xiii

A.6.12 Enabling/Disabling the Linear MSP Protocol......................................................................................................494

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xiv

A.8.10.3 Setting Advanced AM Attributes......................................................................................................................... 529

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xv

A.9.4.10 Configuring UNI-NNI E-Line Services (Carried by PWs)(Web LCT)........................................................ 570

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xvi

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xvii

A.9.12.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network..................................................... 658

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xviii

A.10.8 Managing the QoS.......................................................................................................................................................700

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xix

A.11.2.9 Setting MPLS OAM (Y.1711) Parameters......................................................................................................... 736

Issue 02 (2020-09-30) Copyright © Huawei Technologies Co., Ltd. xx

A.11.6.1 Creating CES Services.............................................................................................................................................. 778