RTN 980 V100R009C10 Maintenance Guide 02 PDF

OptiX RTN 980 Radio Transport System
V100R009C10
Maintenance Guide
Issue 02
Date 2017-05-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2017-05-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Maintenance 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 980 V100R009C10
iManager U2000 V200R016C60
Intended Audience
This document provides the guidelines to maintaining the OptiX RTN 980. It also describes
the alarms and performance events that are required for troubleshooting during the
maintenance.
This document is intended for:
l Network planning engineer

l Data configuration engineer
l System maintenance engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation

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

Symbol Description
Indicates a potentially hazardous situation

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

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

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

best practices and tips.
NOTE is used to address information not
related to personal injury, equipment
damage, and environment deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Issue 02 (2017-05-20) Huawei Proprietary and Confidential iii

Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

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

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

This document is the second issue of the V100R009C10 product version.
Update Description
- Fixed known defects.
Issue 02 (2017-05-20) Huawei Proprietary and Confidential iv

Updates in Issue 01 (2016-12-30) Based on Product Version V100R009C10

This document is the first issue of the V100R009C10 product version.
Issue 02 (2017-05-20) Huawei Proprietary and Confidential v

Maintenance Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Safety Precautions......................................................................................................................... 1
1.1 General Safety Precautions.............................................................................................................................................2
1.2 Warning and Safety Symbols..........................................................................................................................................3
1.3 Electrical Safety..............................................................................................................................................................4
1.4 Environment of Flammable Gas.....................................................................................................................................7
1.5 Storage Batteries.............................................................................................................................................................7
1.6 Radiation.........................................................................................................................................................................9
1.6.1 Safe Usage of Optical Fibers....................................................................................................................................... 9
1.6.2 Electromagnetic Exposure......................................................................................................................................... 11
1.6.3 Forbidden Areas.........................................................................................................................................................11
1.6.4 Laser...........................................................................................................................................................................11
1.6.5 Microwave................................................................................................................................................................. 12
1.7 Working at Heights....................................................................................................................................................... 13
1.7.1 Hoisting Heavy Objects.............................................................................................................................................13
1.7.2 Using Ladders............................................................................................................................................................14
1.8 Mechanical Safety........................................................................................................................................................ 16
1.9 Other Precautions......................................................................................................................................................... 17
2 Notices for High-Risk Operations........................................................................................... 19

2.1 Operation Guide for the Toggle Lever Switch............................................................................................................. 20
2.2 Operation Guide for the IF Jumper...............................................................................................................................22
2.3 Operation Guide for the IF Cables............................................................................................................................... 23
2.4 Operation Guide for the IF Board.................................................................................................................................25
3 Routine Maintenance..................................................................................................................27
4 Network Monitoring...................................................................................................................31
4.1 Checking the NE Status................................................................................................................................................ 32
4.2 Checking the Board Status........................................................................................................................................... 33
4.3 Alarm and Performance Data Query............................................................................................................................ 34
4.3.1 Browsing Current Alarms..........................................................................................................................................34
4.3.2 Browsing Historical Alarms...................................................................................................................................... 39
4.3.3 Browsing Current Performance Events..................................................................................................................... 42
4.3.4 Browsing Historical Performance Events..................................................................................................................44
Issue 02 (2017-05-20) Huawei Proprietary and Confidential vi

4.3.5 Browsing the Performance Event Threshold-Crossing Records............................................................................... 45

4.3.6 Browsing UAT Events............................................................................................................................................... 47
4.4 Microwave Link Performance Query........................................................................................................................... 48
4.4.1 Querying the Historical Transmit Power and Receive Power................................................................................... 48
4.4.2 Querying the SNR Values of a Radio Link................................................................................................................49
4.4.3 Browsing Current Performance Events of the radio link...........................................................................................50
4.4.4 Browsing Historical Performance Data of a Radio Link...........................................................................................52
4.5 Ethernet Performance Query........................................................................................................................................ 53
4.5.1 Browsing Current Ethernet Performance.................................................................................................................. 53
4.5.2 Configuring Ethernet Performance Threshold-Crossing Parameters........................................................................ 58
4.5.3 Setting Parameters for Monitoring Historical Ethernet Performance........................................................................62
4.5.4 Browsing Historical Ethernet Performance Data...................................................................................................... 62
4.6 Ethernet Port Traffic Monitoring.................................................................................................................................. 66
4.6.1 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports....................................................67
4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization............................................................................ 68
4.7 Long-term Network Performance Monitoring............................................................................................................. 69
4.7.1 Creating a Performance Monitoring Template.......................................................................................................... 69
4.7.2 Creating a Performance Monitoring Instance............................................................................................................71
4.7.3 Browsing the Real-Time Data of a Performance Monitoring Instance..................................................................... 75
4.7.4 Browsing the Historical Data of a Performance Monitoring Instance...................................................................... 76
4.8 Report Query................................................................................................................................................................ 77
4.8.1 Querying the Microwave Link Information Report...................................................................................................77
4.8.2 Querying the Network-wide License Report.............................................................................................................78
4.8.3 Querying the Microwave Configuration Report........................................................................................................80
4.8.4 Querying the Board Information Report................................................................................................................... 81
4.8.5 Querying the Board Manufacturing Information Report...........................................................................................84
4.8.6 Querying the ODU Information Report.....................................................................................................................85
4.9 Alarm and Performance Management Setting..............................................................................................................86
4.9.1 Configuring the Performance Monitoring Status of NEs.......................................................................................... 86
4.9.2 Setting Severity and Auto Reporting Status of Alarms............................................................................................. 87
4.9.3 Suppressing Alarms for Monitored Objects.............................................................................................................. 88
4.9.4 Suppressing Alarms for NEs..................................................................................................................................... 89
4.9.5 Reversing Alarms for Service Ports.......................................................................................................................... 90
4.9.6 Setting the Reporting of Alarms and Performance Events for an IF Port and the Corresponding ODU.................. 91
4.9.7 Setting Trigger Conditions of AIS Insertion..............................................................................................................91
4.9.8 Setting Trigger Conditions of UNEQ Insertion.........................................................................................................92
4.9.9 Setting Bit Error Thresholds for Service Ports.......................................................................................................... 93
4.9.10 Setting the Alarm Threshold for Insufficient Fade Margin..................................................................................... 93
4.9.11 Setting Monitoring and Auto-Report Status of Performance Events...................................................................... 94
4.9.12 Setting Performance Thresholds..............................................................................................................................95
4.9.13 Resetting Performance Registers.............................................................................................................................96
5 Troubleshooting.......................................................................................................................... 98
Issue 02 (2017-05-20) Huawei Proprietary and Confidential vii

5.1 General Troubleshooting Procedure........................................................................................................................... 100

5.2 Troubleshooting Service Interruptions....................................................................................................................... 102
5.3 Troubleshooting the Radio Link................................................................................................................................. 109
5.4 Troubleshooting Bit Errors in TDM Services.............................................................................................................116
5.5 Troubleshooting Pointer Justifications....................................................................................................................... 121
5.6 Troubleshooting the Interconnection with SDH Equipment...................................................................................... 125
5.7 Troubleshooting the Interconnection with PDH Equipment...................................................................................... 128
5.8 Troubleshooting Native Ethernet Service Faults........................................................................................................ 132
5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane.................................................................................... 135
5.10 Troubleshooting MPLS Tunnels...............................................................................................................................140
5.11 Troubleshooting CES Services................................................................................................................................. 144
5.12 Troubleshooting ATM Services................................................................................................................................ 148
5.13 Troubleshooting Ethernet Services Carried by PWs................................................................................................ 155
5.14 Troubleshooting L3VPN Services............................................................................................................................ 158
5.15 Troubleshooting DCN Faults....................................................................................................................................161
5.16 Troubleshooting Orderwire Faults............................................................................................................................166
5.17 Typical Cases............................................................................................................................................................ 168
5.17.1 Transient Link Unavailability Due to Multi-path Fading......................................................................................168
5.17.2 Transoceanic Link Transient Unavailability Due to Insufficient Height Difference between Diversity Antennas
.......................................................................................................................................................................................... 170
5.17.3 Link Unavailability Due to Inter-building Reflection........................................................................................... 171
5.17.4 Unidirectional Link Availability Due to Interference............................................................................................172
5.17.5 Bit Errors on Microwave Links............................................................................................................................. 173
5.17.6 Poor Reliability Due to Network Planning Errors.................................................................................................174
6 Part Replacement....................................................................................................................... 176

6.1 Removing a Board...................................................................................................................................................... 178
6.2 Inserting a Board........................................................................................................................................................ 181
6.3 Replacing the SDH Optical Interface Board.............................................................................................................. 183
6.4 Replacing the Channelized STM-1 Processing Board............................................................................................... 184
6.5 Replacing the PDH Interface Board........................................................................................................................... 185
6.6 Replacing the Smart E1 Interface Board.................................................................................................................... 186
6.7 Replacing the Ethernet Interface Board......................................................................................................................187
6.8 Replacing an IF Board................................................................................................................................................ 188
6.9 Replacing the CF Card............................................................................................................................................... 190
6.10 Replacing the System Control, Switching and Timing Board..................................................................................192
6.11 Replacing the Auxiliary Board................................................................................................................................. 196
6.12 Replacing the Fan Board.......................................................................................................................................... 197
6.13 Replacing the Power Board...................................................................................................................................... 199
6.14 Replacing the SFP.................................................................................................................................................... 200
6.15 Replacing an ODU....................................................................................................................................................202
6.16 Replacing an IF Cable.............................................................................................................................................. 204
6.17 Erasing Data in the Repair Parts...............................................................................................................................206
Issue 02 (2017-05-20) Huawei Proprietary and Confidential viii

6.17.1 Board Storage Media............................................................................................................................................. 206

6.17.2 Removing the CF Card.......................................................................................................................................... 207
6.17.3 Formatting the Flash Memory............................................................................................................................... 207
7 Database Backup and Restoration......................................................................................... 209

7.1 NE Database............................................................................................................................................................... 210
7.2 Backing Up the Database Manually........................................................................................................................... 211
7.3 Setting the Database Backup Policy........................................................................................................................... 213
7.3.1 Setting the User-Defined Backup Policy................................................................................................................. 213
7.3.2 Enable the Backup Policy of the Device................................................................................................................. 215
7.3.3 Disable the Backup Policy of the Device................................................................................................................ 216
7.4 Restoring the Database by NMS................................................................................................................................ 218
7.5 Recovering Databases from a USB Flash Drive........................................................................................................ 222
7.6 Restoring Databases for an NE from Its Peer NE.......................................................................................................224
7.7 Restoring Databases from Local NEs.........................................................................................................................225
8 Common Maintenance Operations........................................................................................ 228

8.1 Microwave Link Troubleshooting.............................................................................................................................. 230
8.1.1 Monitoring Radio Link Indicators........................................................................................................................... 230
8.1.2 Scanning Interfering Signals................................................................................................................................... 231
8.1.3 Muting/Unmuting an ODU......................................................................................................................................232
8.1.4 Turning On/Off the Soft Power Switch of an ODU................................................................................................ 233
8.1.5 Performing a PRBS Test for the IF Board............................................................................................................... 234
8.2 Ethernet Service Troubleshooting.............................................................................................................................. 236
8.2.1 Querying the Attributes of an Ethernet Port............................................................................................................ 236
8.2.2 Searching for Service Paths Based on VLANs....................................................................................................... 237
8.2.3 Searching for Service Paths Based on MAC Addresses..........................................................................................239
8.2.4 Checking the Layer 2 Protocols Used by Ethernet Services................................................................................... 240
8.2.5 Performing Intelligent Service Fault Diagnosis for Ethernet Services....................................................................241
8.2.6 Performing E-LAN Service Loopback Detection....................................................................................................243
8.2.7 Monitoring Ethernet Service Performance and Traffic Volume Based on Service Paths........................................244
8.2.8 Querying Ethernet Service QoS Configurations Based on Service Paths............................................................... 246
8.2.9 Using IP Ping Commands to Locate Ethernet Service Faults................................................................................. 248
8.2.10 Monitoring Ethernet Packets Through Port Mirroring.......................................................................................... 253
8.2.11 Monitoring Ethernet Packets by Using Port Traffic Mirroring..............................................................................256
8.2.12 Capturing Headers of Specified Ethernet Packets................................................................................................. 258
8.2.13 Using the Ethernet Test Frames.............................................................................................................................260
8.3 TDM/CES Service Troubleshooting...........................................................................................................................262
8.3.1 Setting the On/Off State of the Laser...................................................................................................................... 262
8.3.2 Setting the ALS Function........................................................................................................................................ 263
8.3.3 Performing a PRBS Test for the Smart E1 Processing Board................................................................................. 263
8.3.4 Performing a PRBS Test for the Tributary Board....................................................................................................267
8.3.5 Querying the Impedance of an E1 Channel.............................................................................................................270
8.4 Software Loopback.....................................................................................................................................................271
Issue 02 (2017-05-20) Huawei Proprietary and Confidential ix

8.4.1 Setting Loopback for the SDH Optical Interface Board..........................................................................................271

8.4.2 Setting Loopback for the Channelized STM-1 Processing Board...........................................................................274
8.4.3 Setting Loopback for the Tributary Board...............................................................................................................275
8.4.4 Setting a Loopback for the Smart E1 Processing Board......................................................................................... 277
8.4.5 Setting a Loopback for the Packet-plane Ethernet Interface Board........................................................................ 278
8.4.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board............................................................... 280
8.4.7 Setting Loopback for the IF Board.......................................................................................................................... 283
8.4.8 Setting Software Loopback for the NE....................................................................................................................285
8.4.9 Setting Software Loopback for the Microwave Link.............................................................................................. 286
8.4.10 Locating a Fault by Performing Loopback Operations......................................................................................... 287
8.5 Hardware Loopback................................................................................................................................................... 288
8.6 Reset........................................................................................................................................................................... 289
8.6.1 Cold Reset................................................................................................................................................................289
8.6.2 Warm Reset..............................................................................................................................................................290
8.7 Setting the Automatic Release Function.................................................................................................................... 291
8.8 Querying Power Consumption of Boards...................................................................................................................292
8.9 Querying Optical Power and Alarm Thresholds of SDH Ports..................................................................................293
8.10 Preventing Service Loops......................................................................................................................................... 294
8.10.1 Setting the Enabling Status of Automatic Service Loop Detection for NEs......................................................... 294
8.10.2 Enabling the Automatic Broadcast Packet Suppression Function.........................................................................298
8.10.3 Enabling Loop Detection Upon MAC Address Flapping..................................................................................... 300
8.11 Switching the System Control Unit and the Cross-Connect Unit.............................................................................300
8.12 Cleaning Fiber Connectors and Adapters................................................................................................................. 301
8.12.1 Cleaning Fiber Connectors by Using Cartridge Cleaners..................................................................................... 301
8.12.2 Cleaning Fiber Connectors by Using Lens Tissue.................................................................................................304
8.12.3 Cleaning Fiber Adapters by Using Optical Cleaning Sticks................................................................................. 305
A Alarm Reference....................................................................................................................... 307

A.1 Alarm List (in Alphabetical Order)........................................................................................................................... 308
A.2 Alarm List (Classified by Logical Boards)................................................................................................................326
A.2.1 AUX........................................................................................................................................................................328
A.2.2 CQ1.........................................................................................................................................................................328
A.2.3 CSHN......................................................................................................................................................................329
A.2.4 CSHNA...................................................................................................................................................................331
A.2.5 CSHNU...................................................................................................................................................................333
A.2.6 EFP8....................................................................................................................................................................... 335
A.2.7 EG2D...................................................................................................................................................................... 336
A.2.8 EG4......................................................................................................................................................................... 337
A.2.9 EG4P.......................................................................................................................................................................338
A.2.10 EM6T.................................................................................................................................................................... 338
A.2.11 EM6TA..................................................................................................................................................................339
A.2.12 EM6F.................................................................................................................................................................... 339
A.2.13 EM6FA..................................................................................................................................................................340
Issue 02 (2017-05-20) Huawei Proprietary and Confidential x

A.2.14 EMS6.................................................................................................................................................................... 341

A.2.15 EX1....................................................................................................................................................................... 342
A.2.16 FAN.......................................................................................................................................................................342
A.2.17 IF1.........................................................................................................................................................................343
A.2.18 IFU2...................................................................................................................................................................... 343
A.2.19 IFX2...................................................................................................................................................................... 344
A.2.20 ISM6..................................................................................................................................................................... 345
A.2.21 ISU2...................................................................................................................................................................... 346
A.2.22 ISV3...................................................................................................................................................................... 347
A.2.23 ISX2...................................................................................................................................................................... 348
A.2.24 ML1/MD1.............................................................................................................................................................349
A.2.25 ODU......................................................................................................................................................................349
A.2.26 PIU........................................................................................................................................................................ 349
A.2.27 PMU......................................................................................................................................................................350
A.2.28 SL1D/SL1DA....................................................................................................................................................... 350
A.2.29 SL4D.....................................................................................................................................................................351
A.2.30 SP3S/SP3D........................................................................................................................................................... 351
A.2.31 TCU...................................................................................................................................................................... 351
A.3 Alarms and Handling Procedures.............................................................................................................................. 352
A.3.1 A_LOC................................................................................................................................................................... 352
A.3.2 ACR_LOCK_FAIL.................................................................................................................................................352
A.3.3 AES_MAC_ERR.................................................................................................................................................... 354
A.3.4 ALM_E1RAI.......................................................................................................................................................... 355
A.3.5 ALM_GFP_dCSF................................................................................................................................................... 356
A.3.6 ALM_GFP_dLFD...................................................................................................................................................357
A.3.7 ALM_IMA_LIF......................................................................................................................................................358
A.3.8 ALM_IMA_LODS................................................................................................................................................. 359
A.3.9 ALM_IMA_RE_RX_UNUSABLE........................................................................................................................360
A.3.10 ALM_IMA_RE_TX_UNUSABLE...................................................................................................................... 362
A.3.11 ALM_IMA_RFI....................................................................................................................................................363
A.3.12 AM_DOWNSHIFT.............................................................................................................................................. 365
A.3.13 APS_FAIL............................................................................................................................................................ 366
A.3.14 APS_INDI.............................................................................................................................................................368
A.3.15 APS_MANUAL_STOP........................................................................................................................................369
A.3.16 ARP_FAIL............................................................................................................................................................ 370
A.3.17 ARP_MAC_MISMATCH.................................................................................................................................... 371
A.3.18 ARP_SPOOF........................................................................................................................................................ 372
A.3.19 ATMPW_UNKNOWNCELL_EXC.....................................................................................................................373
A.3.20 AU_AIS................................................................................................................................................................ 374
A.3.21 AU_LOP............................................................................................................................................................... 375
A.3.22 B1_EXC................................................................................................................................................................376
A.3.23 B1_SD...................................................................................................................................................................378
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xi

A.3.24 B2_EXC................................................................................................................................................................380
A.3.25 B2_SD...................................................................................................................................................................382
A.3.26 B3_EXC................................................................................................................................................................384
A.3.27 B3_EXC_VC3...................................................................................................................................................... 386
A.3.28 B3_SD...................................................................................................................................................................389
A.3.29 B3_SD_VC3......................................................................................................................................................... 391
A.3.30 BAT1TEMP_SENSOR_FAIL.............................................................................................................................. 393
A.3.31 BAT2TEMP_SENSOR_FAIL.............................................................................................................................. 394
A.3.32 BD_NOT_INSTALLED....................................................................................................................................... 395
A.3.33 BD_STATUS........................................................................................................................................................ 396
A.3.34 BDTEMP_SENSOR_FAIL.................................................................................................................................. 398
A.3.35 BGPBACKTRANSITION................................................................................................................................... 399
A.3.36 BIOS_STATUS..................................................................................................................................................... 401
A.3.37 BIP_EXC.............................................................................................................................................................. 402
A.3.38 BIP_SD................................................................................................................................................................. 404
A.3.39 BOOTROM_BAD................................................................................................................................................ 405
A.3.40 BRDCASTRATIO_OVER................................................................................................................................... 406
A.3.41 BUS_ERR.............................................................................................................................................................408
A.3.42 CES_ACR_LOCK_ABN......................................................................................................................................411
A.3.43 CES_APS_INDI................................................................................................................................................... 413
A.3.44 CES_APS_MANUAL_STOP.............................................................................................................................. 415
A.3.45 CES_JTROVR_EXC............................................................................................................................................ 416
A.3.46 CES_JTRUDR_EXC............................................................................................................................................ 417
A.3.47 CES_K1_K2_M....................................................................................................................................................418
A.3.48 CES_K2_M...........................................................................................................................................................419
A.3.49 CES_LOSPKT_EXC............................................................................................................................................ 420
A.3.50 CES_MALPKT_EXC...........................................................................................................................................421
A.3.51 CES_MISORDERPKT_EXC...............................................................................................................................422
A.3.52 CES_RDI.............................................................................................................................................................. 423
A.3.53 CES_STRAYPKT_EXC.......................................................................................................................................424
A.3.54 CESPW_OPPOSITE_ACFAULT.........................................................................................................................425
A.3.55 CESPW_OPPOSITE_RAI................................................................................................................................... 426
A.3.56 CFCARD_FAILED.............................................................................................................................................. 426
A.3.57 CFCARD_FULL.................................................................................................................................................. 428
A.3.58 CFCARD_OFFLINE............................................................................................................................................ 429
A.3.59 CFCARD_W_R_DISABLED.............................................................................................................................. 430
A.3.60 CHCS.................................................................................................................................................................... 431
A.3.61 CLK_LOCK_FAIL...............................................................................................................................................432
A.3.62 CLK_NO_TRACE_MODE..................................................................................................................................434
A.3.63 COMMUN_FAIL................................................................................................................................................. 435
A.3.64 COM_EXTECC_FULL........................................................................................................................................437
A.3.65 CONFIG_NOSUPPORT...................................................................................................................................... 438
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xii

A.3.66 CPU_BUSY.......................................................................................................................................................... 440

A.3.67 DBMS_DELETE.................................................................................................................................................. 441
A.3.68 DBMS_ERROR....................................................................................................................................................442
A.3.69 DBMS_PROTECT_MODE................................................................................................................................. 443
A.3.70 DCNLINK_OVER............................................................................................................................................... 444
A.3.71 DCNSIZE_OVER.................................................................................................................................................445
A.3.72 DDN_LFA............................................................................................................................................................ 446
A.3.73 DOWN_E1_AIS................................................................................................................................................... 447
A.3.74 DEVICE_AUTH_FAIL........................................................................................................................................ 448
A.3.75 DROPRATIO_OVER........................................................................................................................................... 449
A.3.76 E1_LOC................................................................................................................................................................ 450
A.3.77 E1_LOS................................................................................................................................................................ 451
A.3.78 ELAN_SMAC_FLAPPING................................................................................................................................. 452
A.3.79 ENVHUM_SENSOR_FAIL.................................................................................................................................454
A.3.80 ENVTEMP_SENSOR_FAIL................................................................................................................................455
A.3.81 ENVTEMP1_SENSOR_FAIL..............................................................................................................................456
A.3.82 ENVTEMP2_SENSOR_FAIL..............................................................................................................................457
A.3.83 ERPS_IN_PROTECTION....................................................................................................................................458
A.3.84 ETH_APS_LOST................................................................................................................................................. 460
A.3.85 ETH_APS_PATH_MISMATCH...........................................................................................................................461
A.3.86 ETH_APS_SWITCH_FAIL................................................................................................................................. 462
A.3.87 ETH_APS_TYPE_MISMATCH.......................................................................................................................... 463
A.3.88 ETH_AUTO_LINK_DOWN................................................................................................................................464
A.3.89 ETH_CFM_AIS....................................................................................................................................................465
A.3.90 ETH_CFM_LOC.................................................................................................................................................. 466
A.3.91 ETH_CFM_MISMERGE..................................................................................................................................... 469
A.3.92 ETH_CFM_RDI................................................................................................................................................... 472
A.3.93 ETH_CFM_UNEXPERI...................................................................................................................................... 474
A.3.94 ETH_EFM_DF..................................................................................................................................................... 477
A.3.95 ETH_EFM_EVENT............................................................................................................................................. 478
A.3.96 ETH_EFM_LOOPBACK.....................................................................................................................................480
A.3.97 ETH_EFM_REMFAULT..................................................................................................................................... 481
A.3.98 ETH_LINK_DOWN.............................................................................................................................................482
A.3.99 ETH_LOS............................................................................................................................................................. 484
A.3.100 ETH_NO_FLOW............................................................................................................................................... 486
A.3.101 ETH_PWR_SUPPLY_FAIL...............................................................................................................................487
A.3.102 ETHOAM_DISCOVER_FAIL...........................................................................................................................488
A.3.103 ETHOAM_RMT_CRIT_FAULT....................................................................................................................... 489
A.3.104 ETHOAM_RMT_LOOP.................................................................................................................................... 491
A.3.105 ETHOAM_RMT_SD......................................................................................................................................... 492
A.3.106 ETHOAM_SELF_LOOP................................................................................................................................... 494
A.3.107 ETHOAM_VCG_SELF_LOOP......................................................................................................................... 495
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xiii

A.3.108 EX_ETHOAM_CC_LOS................................................................................................................................... 497

A.3.109 EX_ETHOAM_MPID_CNFLCT.......................................................................................................................498
A.3.110 EXT_SYNC_LOS...............................................................................................................................................500
A.3.111 EXT_TIME_LOC............................................................................................................................................... 501
A.3.112 FAN_AGING...................................................................................................................................................... 502
A.3.113 FAN_FAIL.......................................................................................................................................................... 503
A.3.114 FCS_ERR............................................................................................................................................................504
A.3.115 FDBSIZEALM_ELAN.......................................................................................................................................505
A.3.116 FLOW_EXC_LCS..............................................................................................................................................506
A.3.117 FLOW_OVER.................................................................................................................................................... 507
A.3.118 GSP_RSVP_NB_AUTH_ERR...........................................................................................................................508
A.3.119 GSP_RSVP_NB_DOWN................................................................................................................................... 509
A.3.120 GSP_TNNL_DOWN.......................................................................................................................................... 511
A.3.121 HARD_ERR....................................................................................................................................................... 513
A.3.122 HARD_BAD.......................................................................................................................................................514
A.3.123 HARD_NONSUPPORT..................................................................................................................................... 516
A.3.124 HP_CROSSTR................................................................................................................................................... 517
A.3.125 HP_LOM............................................................................................................................................................ 518
A.3.126 HP_RDI.............................................................................................................................................................. 519
A.3.127 HP_REI...............................................................................................................................................................520
A.3.128 HP_SLM............................................................................................................................................................. 521
A.3.129 HP_TIM.............................................................................................................................................................. 522
A.3.130 HP_UNEQ.......................................................................................................................................................... 523
A.3.131 HPAD_CROSSTR.............................................................................................................................................. 524
A.3.132 IF_CABLE_OPEN............................................................................................................................................. 525
A.3.133 IF_INPWR_ABN............................................................................................................................................... 526
A.3.134 IF_MODE_UNSUPPORTED.............................................................................................................................528
A.3.135 IGSP_ENTRIES_EXC....................................................................................................................................... 529
A.3.136 IMA_GROUP_LE_DOWN................................................................................................................................531
A.3.137 IMA_GROUP_RE_DOWN............................................................................................................................... 532
A.3.138 IMA_TXCLK_MISMATCH.............................................................................................................................. 533
A.3.139 IN_PWR_ABN................................................................................................................................................... 534
A.3.140 IN_PWR_HIGH................................................................................................................................................. 535
A.3.141 IN_PWR_LOW.................................................................................................................................................. 536
A.3.142 INSUFFCNT_MEM_SPACE............................................................................................................................. 538
A.3.143 INSUFFCNT_FLSH_SPACE.............................................................................................................................539
A.3.144 INTEMP_SENSOR_FAIL..................................................................................................................................540
A.3.145 ISIS_LSP_SEQ_EXCEED................................................................................................................................. 542
A.3.146 ISIS_SEQ_REACH_MAX.................................................................................................................................543
A.3.147 ISISADJACENCYCHANGE.............................................................................................................................544
A.3.148 J0_MM................................................................................................................................................................546
A.3.149 K1_K2_M........................................................................................................................................................... 547
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xiv

A.3.150 K2_M.................................................................................................................................................................. 548

A.3.151 KMC_KEY_SYNC_FAIL..................................................................................................................................550
A.3.152 L3V_TRAP_THRE_EXCEED...........................................................................................................................551
A.3.153 L3V_TRAP_VRF_DOWN.................................................................................................................................552
A.3.154 LAG_BWMM.....................................................................................................................................................553
A.3.155 LAG_DOWN......................................................................................................................................................554
A.3.156 LAG_MEMBER_DOWN.................................................................................................................................. 555
A.3.157 LAG_PORT_FAIL..............................................................................................................................................557
A.3.158 LAG_VC_PORT_FAIL...................................................................................................................................... 559
A.3.159 LAN_LOC.......................................................................................................................................................... 560
A.3.160 LASER_CHECK_ERR...................................................................................................................................... 562
A.3.161 LASER_CLOSED.............................................................................................................................................. 563
A.3.162 LASER_MOD_ERR...........................................................................................................................................563
A.3.163 LASER_MOD_ERR_EX................................................................................................................................... 565
A.3.164 LASER_MODULE_MISMATCH..................................................................................................................... 566
A.3.165 LASER_SHUT................................................................................................................................................... 567
A.3.166 LCAS_FOPR...................................................................................................................................................... 568
A.3.167 LCAS_FOPT...................................................................................................................................................... 570
A.3.168 LCAS_PLCR...................................................................................................................................................... 571
A.3.169 LCAS_PLCT...................................................................................................................................................... 573
A.3.170 LCAS_TLCR...................................................................................................................................................... 574
A.3.171 LCAS_TLCT...................................................................................................................................................... 576
A.3.172 LCD.................................................................................................................................................................... 577
A.3.173 LCS_DAYS_OF_GRACE..................................................................................................................................578
A.3.174 LCS_EXPIRED.................................................................................................................................................. 580
A.3.175 LCS_FILE_NOT_EXIST................................................................................................................................... 581
A.3.176 LCS_LIMITED...................................................................................................................................................581
A.3.177 LCS_TRIAL_PERIOD.......................................................................................................................................585
A.3.178 LFA..................................................................................................................................................................... 586
A.3.179 LICENSE_LOST................................................................................................................................................ 587
A.3.180 LINK_ERR......................................................................................................................................................... 588
A.3.181 LMFA..................................................................................................................................................................590
A.3.182 LOCAL_FAULT.................................................................................................................................................591
A.3.183 LOOP_ALM....................................................................................................................................................... 592
A.3.184 LP_CROSSTR.................................................................................................................................................... 596
A.3.185 LP_R_FIFO........................................................................................................................................................ 597
A.3.186 LP_RDI...............................................................................................................................................................598
A.3.187 LP_RDI_VC12................................................................................................................................................... 598
A.3.188 LP_RDI_VC3..................................................................................................................................................... 599
A.3.189 LP_REI............................................................................................................................................................... 600
A.3.190 LP_REI_VC12....................................................................................................................................................601
A.3.191 LP_REI_VC3......................................................................................................................................................602
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xv

A.3.192 LP_RFI............................................................................................................................................................... 603

A.3.193 LP_SLM............................................................................................................................................................. 604
A.3.194 LP_SLM_VC12.................................................................................................................................................. 605
A.3.195 LP_SLM_VC3.................................................................................................................................................... 606
A.3.196 LP_T_FIFO.........................................................................................................................................................607
A.3.197 LP_TIM.............................................................................................................................................................. 608
A.3.198 LP_TIM_VC12...................................................................................................................................................609
A.3.199 LP_TIM_VC3.....................................................................................................................................................610
A.3.200 LP_UNEQ...........................................................................................................................................................611
A.3.201 LP_UNEQ_VC12............................................................................................................................................... 612
A.3.202 LP_UNEQ_VC3................................................................................................................................................. 613
A.3.203 LPS_UNI_BI_M.................................................................................................................................................614
A.3.204 LPT_CFG_CLOSEPORT...................................................................................................................................616
A.3.205 LPT_INEFFECT.................................................................................................................................................617
A.3.206 LPT_RFI............................................................................................................................................................. 618
A.3.207 LSR_BCM_ALM............................................................................................................................................... 619
A.3.208 LSR_NO_FITED................................................................................................................................................ 620
A.3.209 LSR_WILL_DIE................................................................................................................................................ 621
A.3.210 LTI.......................................................................................................................................................................622
A.3.211 MAC_EXT_EXC................................................................................................................................................624
A.3.212 MAC_FCS_EXC................................................................................................................................................ 625
A.3.213 MAC_FCS_SD................................................................................................................................................... 626
A.3.214 MOD_COM_FAIL............................................................................................................................................. 627
A.3.215 MOD_TYPE_MISMATCH................................................................................................................................ 628
A.3.216 MP_DELAY....................................................................................................................................................... 630
A.3.217 MP_DOWN........................................................................................................................................................ 631
A.3.218 MPLSLDPSESSIONDOWN..............................................................................................................................633
A.3.219 MPLSLSP_TBL_LACK.....................................................................................................................................634
A.3.220 MPLS_PW_AIS................................................................................................................................................. 635
A.3.221 MPLS_PW_CSF.................................................................................................................................................636
A.3.222 MPLS_PW_BDI................................................................................................................................................. 637
A.3.223 MPLS_PW_Excess.............................................................................................................................................638
A.3.224 MPLS_PW_LCK................................................................................................................................................ 639
A.3.225 MPLS_PW_LOCK............................................................................................................................................. 639
A.3.226 MPLS_PW_LOCV............................................................................................................................................. 640
A.3.227 MPLS_PW_MISMATCH...................................................................................................................................642
A.3.228 MPLS_PW_MISMERGE...................................................................................................................................643
A.3.229 MPLS_PW_OAMFAIL...................................................................................................................................... 644
A.3.230 MPLS_PW_RDI................................................................................................................................................. 645
A.3.231 MPLS_PW_SD...................................................................................................................................................646
A.3.232 MPLS_PW_SF................................................................................................................................................... 647
A.3.233 MPLS_PW_UNEXPMEG..................................................................................................................................648
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xvi

A.3.234 MPLS_PW_UNEXPMEP.................................................................................................................................. 649

A.3.235 MPLS_PW_UNEXPPER................................................................................................................................... 649
A.3.236 MPLS_PW_UNKNOWN...................................................................................................................................650
A.3.237 MPLS_TUNNEL_AIS....................................................................................................................................... 651
A.3.238 MPLS_TUNNEL_BDI....................................................................................................................................... 652
A.3.239 MPLS_TUNNEL_EXCESS............................................................................................................................... 653
A.3.240 MPLS_TUNNEL_FDI....................................................................................................................................... 653
A.3.241 MPLS_TUNNEL_LOCV................................................................................................................................... 655
A.3.242 MPLS_TUNNEL_LOCK................................................................................................................................... 656
A.3.243 MPLS_TUNNEL_MISMATCH.........................................................................................................................657
A.3.244 MPLS_TUNNEL_MISMERGE.........................................................................................................................658
A.3.245 MPLS_TUNNEL_OAMFAIL............................................................................................................................ 659
A.3.246 MPLS_TUNNEL_RDI....................................................................................................................................... 660
A.3.247 MPLS_TUNNEL_SD.........................................................................................................................................661
A.3.248 MPLS_TUNNEL_SF......................................................................................................................................... 661
A.3.249 MPLS_TUNNEL_UNEXPMEG........................................................................................................................662
A.3.250 MPLS_TUNNEL_UNEXPMEP........................................................................................................................ 663
A.3.251 MPLS_TUNNEL_UNEXPPER......................................................................................................................... 664
A.3.252 MPLS_TUNNEL_UNKNOWN.........................................................................................................................665
A.3.253 MS_AIS.............................................................................................................................................................. 666
A.3.254 MS_CROSSTR...................................................................................................................................................667
A.3.255 MS_RDI..............................................................................................................................................................669
A.3.256 MS_REI.............................................................................................................................................................. 670
A.3.257 MSAD_CROSSTR............................................................................................................................................. 670
A.3.258 MULTI_RPL_OWNER...................................................................................................................................... 672
A.3.259 MW_AM_TEST................................................................................................................................................. 673
A.3.260 MW_BER_EXC................................................................................................................................................. 673
A.3.261 MW_BER_SD.................................................................................................................................................... 677
A.3.262 MW_CFG_MISMATCH.................................................................................................................................... 680
A.3.263 MW_CONT_WAVE........................................................................................................................................... 683
A.3.264 MW_E1_LOST...................................................................................................................................................684
A.3.265 MW_FEC_UNCOR............................................................................................................................................685
A.3.266 MW_LIM............................................................................................................................................................688
A.3.267 MW_LOF........................................................................................................................................................... 690
A.3.268 MW_RDI............................................................................................................................................................ 694
A.3.269 NEIP_CONFUSION...........................................................................................................................................695
A.3.270 NESF_LOST.......................................................................................................................................................696
A.3.271 NESOFT_MM.................................................................................................................................................... 698
A.3.272 NO_BD_SOFT................................................................................................................................................... 700
A.3.273 NP1_MANUAL_STOP...................................................................................................................................... 700
A.3.274 NP1_SW_FAIL...................................................................................................................................................701
A.3.275 NP1_SW_INDI...................................................................................................................................................702
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xvii

A.3.276 NTP_SYNC_FAIL..............................................................................................................................................703
A.3.277 OCD.................................................................................................................................................................... 704
A.3.278 ODC_BATTERY_CURRENT_ABN................................................................................................................. 705
A.3.279 ODC_BATTERY_PWRDOWN......................................................................................................................... 707
A.3.280 ODC_DOOR_OPEN.......................................................................................................................................... 709
A.3.281 ODC_FAN_FAILED.......................................................................................................................................... 711
A.3.282 ODC_HUMI_ABN.............................................................................................................................................712
A.3.283 ODC_LOAD_PWRDOWN................................................................................................................................713
A.3.284 ODC_MDL_ABN...............................................................................................................................................716
A.3.285 ODC_POWER_FAIL......................................................................................................................................... 718
A.3.286 ODC_SMOKE_OVER....................................................................................................................................... 720
A.3.287 ODC_SURGE_PROTECTION_FAIL............................................................................................................... 721
A.3.288 ODC_TEC_ALM............................................................................................................................................... 723
A.3.289 ODC_TEMP_ABN.............................................................................................................................................724
A.3.290 ODC_WATER_ALM..........................................................................................................................................726
A.3.291 OSPFNBRSTATECHANGE.............................................................................................................................. 727
A.3.292 OUT_PWR_ABN............................................................................................................................................... 729
A.3.293 OUT_PWR_HIGH............................................................................................................................................. 730
A.3.294 OUT_PWR_LOW.............................................................................................................................................. 732
A.3.295 OUT1TEMP_SENSOR_FAIL............................................................................................................................733
A.3.296 OUT2TEMP_SENSOR_FAIL............................................................................................................................734
A.3.297 PASSWORD_NEED_CHANGE........................................................................................................................735
A.3.298 PATCH_BD_EXCLUDE....................................................................................................................................736
A.3.299 PATCH_BD_MATCH_FAIL.............................................................................................................................. 737
A.3.300 PATCH_CHGSCC_NOTMATCH......................................................................................................................737
A.3.301 PATCH_PKGERR.............................................................................................................................................. 738
A.3.302 PG_LINK_FAIL................................................................................................................................................. 739
A.3.303 PG_PRT_DEGRADED...................................................................................................................................... 740
A.3.304 PLA_CFG_MISMATCH.................................................................................................................................... 741
A.3.305 PLA_DOWN...................................................................................................................................................... 744
A.3.306 PLA_MEMBER_DOWN................................................................................................................................... 745
A.3.307 PLA_MEMBER_DOWN_EXT......................................................................................................................... 746
A.3.308 PLA_PKT_ERR................................................................................................................................................. 749
A.3.309 PORTMODE_MISMATCH............................................................................................................................... 750
A.3.310 PORT_EXC_TRAFFIC...................................................................................................................................... 751
A.3.311 PORT_MODULE_OFFLINE............................................................................................................................. 752
A.3.312 POWER_ABNORMAL..................................................................................................................................... 754
A.3.313 POWER_ALM................................................................................................................................................... 755
A.3.314 PRO_PKT_FLOODING.....................................................................................................................................756
A.3.315 PPP_LCP_FAIL..................................................................................................................................................758
A.3.316 PPP_NCP_FAIL................................................................................................................................................. 759
A.3.317 PTP_SOURCE_SWITCH.................................................................................................................................. 759
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xviii

A.3.318 PTP_TIMESTAMP_ABN.................................................................................................................................. 761

A.3.319 PW_APS_DEGRADED..................................................................................................................................... 762
A.3.320 PW_APS_OUTAGE........................................................................................................................................... 763
A.3.321 PW_DOWN........................................................................................................................................................ 764
A.3.322 PW_DROPPKT_EXC........................................................................................................................................ 765
A.3.323 PW_NO_TRAFFIC............................................................................................................................................ 766
A.3.324 PWAPS_LOST................................................................................................................................................... 767
A.3.325 PWAPS_PATH_MISMATCH.............................................................................................................................768
A.3.326 PWAPS_SWITCH_FAIL....................................................................................................................................769
A.3.327 PWAPS_TYPE_MISMATCH............................................................................................................................ 770
A.3.328 PWD_ENCRYPT_RISK.................................................................................................................................... 771
A.3.329 R_LOC................................................................................................................................................................772
A.3.330 R_LOF................................................................................................................................................................ 773
A.3.331 R_LOS................................................................................................................................................................ 775
A.3.332 R_OOF................................................................................................................................................................777
A.3.333 RADIO_FADING_MARGIN_INSUFF.............................................................................................................779
A.3.334 RADIO_MUTE.................................................................................................................................................. 780
A.3.335 RADIO_RSL_BEYONDTH.............................................................................................................................. 781
A.3.336 RADIO_RSL_HIGH.......................................................................................................................................... 782
A.3.337 RADIO_RSL_LOW........................................................................................................................................... 783
A.3.338 RADIO_TSL_HIGH...........................................................................................................................................785
A.3.339 RADIO_TSL_LOW........................................................................................................................................... 786
A.3.340 RELAY_ALARM_CRITICAL...........................................................................................................................786
A.3.341 RELAY_ALARM_IGNORE..............................................................................................................................787
A.3.342 RELAY_ALARM_MAJOR............................................................................................................................... 788
A.3.343 RELAY_ALARM_MINOR................................................................................................................................789
A.3.344 REMOTE_FAULT..............................................................................................................................................789
A.3.345 RMFA................................................................................................................................................................. 790
A.3.346 RPS_INDI...........................................................................................................................................................791
A.3.347 RS_CROSSTR....................................................................................................................................................793
A.3.348 RTC_FAIL.......................................................................................................................................................... 794
A.3.349 RT_TBL_LACK................................................................................................................................................. 795
A.3.350 S1_SYN_CHANGE........................................................................................................................................... 796
A.3.351 SYNC_FAIL....................................................................................................................................................... 797
A.3.352 SEC_RADIUS_FAIL..........................................................................................................................................799
A.3.353 SECU_ALM....................................................................................................................................................... 800
A.3.354 SLAVE_BAD......................................................................................................................................................801
A.3.355 SOFTWARE_UNCOMMIT............................................................................................................................... 803
A.3.356 SRV_SHUTDOWN_LD.....................................................................................................................................804
A.3.357 SSL_CERT_DAMAGED................................................................................................................................... 804
A.3.358 SSL_CERT_NOENC..........................................................................................................................................805
A.3.359 SSL_CERT_TO_EXPIRE.................................................................................................................................. 806
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xix

A.3.360 STORAGE_FAIL............................................................................................................................................... 807

A.3.361 STORM_CUR_QUENUM_OVER.................................................................................................................... 809
A.3.362 SUBNET_RT_CONFLICT................................................................................................................................ 809
A.3.363 SWDL_ACTIVATED_TIMEOUT..................................................................................................................... 811
A.3.364 SWDL_AUTOMATCH_INH.............................................................................................................................812
A.3.365 SWDL_CHGMNG_NOMATCH....................................................................................................................... 813
A.3.366 SWDL_COMMIT_FAIL.................................................................................................................................... 814
A.3.367 SWDL_INPROCESS......................................................................................................................................... 815
A.3.368 SWDL_NEPKGCHECK.................................................................................................................................... 815
A.3.369 SWDL_PKG_NOBDSOFT................................................................................................................................ 816
A.3.370 SWDL_PKGVER_MM...................................................................................................................................... 817
A.3.371 SWDL_ROLLBACK_FAIL...............................................................................................................................818
A.3.372 SYN_BAD.......................................................................................................................................................... 819
A.3.373 SYNC_C_LOS................................................................................................................................................... 820
A.3.374 SYNC_DISABLE...............................................................................................................................................821
A.3.375 SYSLOG_COMM_FAIL....................................................................................................................................822
A.3.376 T_ALOS............................................................................................................................................................. 822
A.3.377 T_LOC................................................................................................................................................................ 824
A.3.378 TEM_HA............................................................................................................................................................ 825
A.3.379 TEM_LA.............................................................................................................................................................825
A.3.380 TEMP_ALARM................................................................................................................................................. 826
A.3.381 TEMP_OVER.....................................................................................................................................................828
A.3.382 TF........................................................................................................................................................................829
A.3.383 THUNDERALM................................................................................................................................................ 830
A.3.384 TIME_LOCK_FAIL........................................................................................................................................... 831
A.3.385 TIME_NO_TRACE_MODE.............................................................................................................................. 832
A.3.386 TR_LOC............................................................................................................................................................. 833
A.3.387 TU_AIS...............................................................................................................................................................834
A.3.388 TU_AIS_VC12................................................................................................................................................... 836
A.3.389 TU_AIS_VC3..................................................................................................................................................... 838
A.3.390 TU_LOP............................................................................................................................................................. 840
A.3.391 TU_LOP_VC12.................................................................................................................................................. 841
A.3.392 TU_LOP_VC3.................................................................................................................................................... 842
A.3.393 TUNNEL_APS_DEGRADED........................................................................................................................... 844
A.3.394 TUNNEL_APS_OUTAGE................................................................................................................................. 845
A.3.395 UHCS..................................................................................................................................................................846
A.3.396 UP_E1_AIS........................................................................................................................................................ 847
A.3.397 USB_FILE_UNSEC........................................................................................................................................... 848
A.3.398 USB_PROCESS_FAIL.......................................................................................................................................849
A.3.399 V5_VCAIS......................................................................................................................................................... 850
A.3.400 VC_AIS.............................................................................................................................................................. 851
A.3.401 VC_LOC.............................................................................................................................................................853
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xx

A.3.402 VC_RDI.............................................................................................................................................................. 855

A.3.403 VCAT_LOA........................................................................................................................................................856
A.3.404 VCAT_LOM_VC12........................................................................................................................................... 857
A.3.405 VCAT_LOM_VC3............................................................................................................................................. 859
A.3.406 VCAT_SQM_VC12............................................................................................................................................861
A.3.407 VCAT_SQM_VC3..............................................................................................................................................862
A.3.408 VOLT_LOS.........................................................................................................................................................863
A.3.409 VP_AIS...............................................................................................................................................................865
A.3.410 VP_LOC............................................................................................................................................................. 867
A.3.411 VP_RDI...............................................................................................................................................................868
A.3.412 W_R_FAIL......................................................................................................................................................... 870
A.3.413 WRG_BD_TYPE............................................................................................................................................... 871
A.3.414 XPIC_LOS..........................................................................................................................................................872
B Performance Event Reference.................................................................................................874

B.1 Performance Events (by Event Type)........................................................................................................................ 875
B.1.1 SDH/PDH Performance Event List........................................................................................................................ 875
B.1.2 Radio Performance Events......................................................................................................................................878
B.1.3 MPLS PW Performance Events..............................................................................................................................882
B.1.4 Other Performance Events...................................................................................................................................... 882
B.2 Performance Events (by Logical Board)....................................................................................................................884
B.2.1 CQ1......................................................................................................................................................................... 885
B.2.2 CSHN...................................................................................................................................................................... 889
B.2.3 CSHNA................................................................................................................................................................... 891
B.2.4 CSHNU................................................................................................................................................................... 892
B.2.5 EG2D...................................................................................................................................................................... 895
B.2.6 EG4P....................................................................................................................................................................... 895
B.2.7 EG4......................................................................................................................................................................... 896
B.2.8 EM6T...................................................................................................................................................................... 897
B.2.9 EM6TA....................................................................................................................................................................898
B.2.10 EM6F.................................................................................................................................................................... 898
B.2.11 EM6FA.................................................................................................................................................................. 898
B.2.12 EFP8......................................................................................................................................................................899
B.2.13 EMS6.................................................................................................................................................................... 900
B.2.14 EX1....................................................................................................................................................................... 902
B.2.15 IF1......................................................................................................................................................................... 903
B.2.16 IFU2/ISU2.............................................................................................................................................................906
B.2.17 IFX2/ISX2.............................................................................................................................................................910
B.2.18 ISV3...................................................................................................................................................................... 914
B.2.19 ISM6..................................................................................................................................................................... 919
B.2.20 ML1/MD1............................................................................................................................................................. 923
B.2.21 ODU...................................................................................................................................................................... 924
B.2.22 SL1D/SL1DA....................................................................................................................................................... 925
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xxi

B.2.23 SL4D..................................................................................................................................................................... 927

B.2.24 SP3S/SP3D........................................................................................................................................................... 930
B.3 Performance Events and Handling Procedures..........................................................................................................931
B.3.1 ATPC_P_ADJUST and ATPC_N_ADJUST.......................................................................................................... 931
B.3.2 AMDOWNCNT and AMUPCNT.......................................................................................................................... 932
B.3.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW..................................................................................................... 933
B.3.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR............................................................................................934
B.3.5 CPUUSAGEMAX, CPUUSAGEMIN, CPUUSAGECUR, and CPUUSAGEAVG..............................................935
B.3.6 CURPOSITIVEPDV and CURNEGATIVEPDV...................................................................................................935
B.3.7 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and E1_LSES_SDH............................................................. 936
B.3.8 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS.............................................................................................937
B.3.9 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and FEC_UNCOR_BLOCK_CNT............................................ 938
B.3.10 HPBBE, HPES, HPSES, HPCSES, and HPUAS................................................................................................. 939
B.3.11 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS.......................................................................... 941
B.3.12 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS............................................................................................... 942
B.3.13 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG.............................................................................................943
B.3.14 IF_MSE_MAX, IF_MSE_MIN, IF_MSE_AVG, and IF_MSE_CUR................................................................. 943
B.3.15 LPBBE, LPES, LPSES, LPCSES, and LPUAS....................................................................................................944
B.3.16 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS............................................................................ 945
B.3.17 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV.................................................................................... 946
B.3.18 MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY....................................947
B.3.19 MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET..........................................................947
B.3.20 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and AVGPOSITIVEDELAY...............................................948
B.3.21 MEMUSAGEAVG, MEMUSAGECUR, MEMUSAGEMAX, and MEMUSAGEMIN.....................................949
B.3.22 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and MPLS_PW_UAS...................................................949
B.3.23 MPLS_PW_LS_N, MPLS_PW_SLS_N, MPLS_PW_CSLS_N, and MPLS_PW_UAS_N............................... 950
B.3.24 MSBBE, MSES, MSSES, MSCSES, and MSUAS.............................................................................................. 951
B.3.25 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS.......................................................................952
B.3.26 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR........................................................................................953
B.3.27 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and PG_IF_UAS............................................................954
B.3.28 RPLMAX, RPLMIN, and RPLCUR.................................................................................................................... 955
B.3.29 RSBBE, RSES, RSSES, RSCSES, and RSUAS.................................................................................................. 956
B.3.30 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG........................................................................................... 957
B.3.31 RSOOF and RSOFS..............................................................................................................................................958
B.3.32 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16, QAMWS32, QAMWS64, QAMWS128, QAMWS256,
QAMWS512, QAM_L_WS512, QAMWS1024, QAM_L_WS1024, QAMWS2048, QAMWS4096........................... 959
B.3.33 TLBMAX, TLBMIN, and TLBCUR....................................................................................................................960
B.3.34 RLHTT, RLLTT, TLHTT, TLLTT........................................................................................................................ 960
B.3.35 TPLMAX, TPLMIN, and TPLCUR..................................................................................................................... 961
B.3.36 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG............................................................................................962
B.3.37 TUPJCHIGH, TUPJCLOW, and TUPJCNEW.....................................................................................................962
B.3.38 XPD_MAX, XPD_MIN and XPIC_XPD_VALUE..............................................................................................963
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xxii

C RMON Event Reference.......................................................................................................... 965

C.1 List of RMON Alarm Entries.................................................................................................................................... 966
C.2 RMON Performance Entries List on the Packet-Plane..............................................................................................970
C.2.1 EM6F/EM6T/EM6FA/EM6TA...............................................................................................................................970
C.2.2 EG2D...................................................................................................................................................................... 995
C.2.3 EX1....................................................................................................................................................................... 1019
C.2.4 EG4/EG4P.............................................................................................................................................................1047
C.2.5 IFU2/IFX2.............................................................................................................................................................1079
C.2.6 ISU2/ISX2/ISV3/ISM6......................................................................................................................................... 1102
C.2.7 ML1/MD1............................................................................................................................................................. 1133
C.2.8 CQ1....................................................................................................................................................................... 1149
C.2.9 CSHN.................................................................................................................................................................... 1156
C.2.10 CSHNA............................................................................................................................................................... 1182
C.2.11 CSHNU............................................................................................................................................................... 1235
C.2.12 EFP8/EMS6........................................................................................................................................................ 1261
C.3 RMON Performance Entries List on the EoS/EoPDH-Plane.................................................................................. 1264
C.3.1 EFP8......................................................................................................................................................................1264
C.3.2 EMS6.................................................................................................................................................................... 1272
C.4 RMON Events and Handling Procedures................................................................................................................ 1280
C.4.1 ETHDROP............................................................................................................................................................ 1281
C.4.2 ETHEXCCOL.......................................................................................................................................................1282
C.4.3 ETHLATECOL..................................................................................................................................................... 1283
C.4.4 RXBBAD.............................................................................................................................................................. 1284
C.4.5 TXDEFFRM......................................................................................................................................................... 1284
C.4.6 ETHUNDER......................................................................................................................................................... 1285
C.4.7 ETHOVER............................................................................................................................................................ 1286
C.4.8 ETHFRG............................................................................................................................................................... 1287
C.4.9 ETHJAB................................................................................................................................................................1288
C.4.10 ETHCOL.............................................................................................................................................................1288
C.4.11 ETHFCS..............................................................................................................................................................1289
C.4.12 ATMPW_LOSPKTS...........................................................................................................................................1290
C.4.13 ATMPW_MISORDERPKTS..............................................................................................................................1291
C.4.14 ATMPW_UNKNOWNCELLS...........................................................................................................................1292
C.4.15 ATM_CORRECTED_HCSERR.........................................................................................................................1292
C.4.16 ATM_UNCORRECTED_HCSERR................................................................................................................... 1293
C.4.17 CES_MISORDERPKTS.....................................................................................................................................1294
C.4.18 CES_STRAYPKTS.............................................................................................................................................1294
C.4.19 CES_MALPKTS.................................................................................................................................................1295
C.4.20 CES_JTRUDR.................................................................................................................................................... 1296
C.4.21 CES_JTROVR.................................................................................................................................................... 1296
C.4.22 CES_LOSPKTS.................................................................................................................................................. 1297
D Alarm Management............................................................................................................... 1299
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xxiii

D.1 NE Alarm Management........................................................................................................................................... 1300

D.2 Board Alarm Management...................................................................................................................................... 1300
D.2.1 Setting the Alarm Severity....................................................................................................................................1300
D.2.2 Alarm Suppression................................................................................................................................................1300
D.2.3 Alarm Auto-Report............................................................................................................................................... 1300
D.2.4 Alarm Reversion................................................................................................................................................... 1301
D.2.5 Setting Alarm Thresholds..................................................................................................................................... 1301
D.2.6 AIS Insertion.........................................................................................................................................................1326
D.2.7 UNEQ Insertion.................................................................................................................................................... 1327
E Performance Event Management......................................................................................... 1329

E.1 NE Performance Event Management.......................................................................................................................1330
E.2 Board Performance Event Management.................................................................................................................. 1330
F Alarm Suppression Relationship......................................................................................... 1331

F.1 Alarm Suppression on TDM Plane...........................................................................................................................1332
F.2 Alarm Suppression on the Data Plane...................................................................................................................... 1337
G Indicators of Boards............................................................................................................... 1343
Issue 02 (2017-05-20) Huawei Proprietary and Confidential xxiv

Maintenance Guide 1 Safety Precautions
1 Safety Precautions
About This Chapter
This topic describes the safety precautions that you must follow when installing, operating,
and maintaining Huawei devices.
1.1 General Safety Precautions

This topic describes essential safety precautions that instruct you in the selection of measuring
and testing instruments when you install, operate, and maintain Huawei devices.
1.2 Warning and Safety Symbols
Before using the equipment, note the following warning and safety symbols on the
equipment.
1.3 Electrical Safety
This topic describes safety precautions for high voltage, lightning strikes, high leakage
current, power cables, fuses, and ESD.
1.4 Environment of Flammable Gas
This topic describes safety precautions for the operating environment of a device.
1.5 Storage Batteries
This topic describes safety precautions for operations of storage batteries.
1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
1.7 Working at Heights
This topic describes safety precautions for working at heights.
1.8 Mechanical Safety
This topic describes safety precautions for drilling holes, handling sharp objects, operating
fans, and carrying heavy objects.
1.9 Other Precautions
This topic describes safety precautions for removing and inserting boards, binding signal
cables, and routing cables.
Issue 02 (2017-05-20) Huawei Proprietary and Confidential 1

1.1 General Safety Precautions

This topic describes essential safety precautions that instruct you in the selection of measuring
and testing instruments when you install, operate, and maintain Huawei devices.
All Safety Precautions

To ensure the safety of humans and a device, follow the marks on the device and all the safety
precautions in this document when installing, operating, and maintaining a device.
The "CAUTION", "WARNING", and "DANGER" marks in this document do not cover all
the safety precautions that must be followed. They are supplements to the safety precautions.
Local Laws and Regulations

When operating a device, always comply with the local laws and regulations. The safety
precautions provided in the documents are in addition/supplementary to the local laws and
regulations.
Basic Installation Requirements

The installation and maintenance personnel of Huawei devices must receive strict training and
be familiar with the proper operation methods and safety precautions before any operation.
l Only trained and qualified personnel are permitted to install, operate, and maintain a
device.
l Only certified professionals are permitted to remove the safety facilities, and to
troubleshoot and maintain the device.
l Only the personnel authenticated or authorized by Huawei are permitted to replace or
change the device or parts of the device (including software).
l The operating personnel must immediately report the faults or errors that may cause
safety problems to the person in charge.
Grounding Requirements
The grounding requirements are applicable to the device that needs to be grounded.
l When installing the device, always connect the grounding facilities first. When removing
the device, always disconnect the grounding facilities last.
l Ensure that the grounding conductor is intact.
l Do not operate the device in the absence of a suitably installed grounding conductor.
l The device must be connected to the PGND permanently. Before operating the device,
check the electrical connections of the device, and ensure that the device is properly
grounded.
Human Safety
l When there is a risk of a lightning strike, do not operate the fixed terminal or touch the
cables.
l When there is risk of a lightning strike, unplug the AC power connector. Do not use the
fixed terminal or touch the terminal or antenna connector.

NOTE
The preceding requirements apply to wireless fixed station terminals.
l To avoid electric shocks, do not connect safety extra-low voltage (SELV) circuits to
telephone-network voltage (TNV) circuits.
l Do not look into optical ports without eye protection. Otherwise, human eyes may be
hurt by laser beams.
l Before operating the device, wear an ESD protective coat, ESD gloves, and an ESD
wrist strap. In addition, you need to get off the conductive objects, such as jewelry and
watches, to prevent electric shock and burn.
l In case of fire, escape from the building or site where the device is located and press the
fire alarm bell or dial the telephone number for fire alarms. Do not enter the burning
building again in any situation.
Device Safety
l Before any operation, install the device firmly on the ground or other rigid objects, such
as on a wall or in a rack.
l When the system is working, ensure that the ventilation hole is not blocked.
l When installing the front panel, use a tool to tighten the screws firmly, if required.
l After installing the device, clean up the packing materials.
1.2 Warning and Safety Symbols

Before using the equipment, note the following warning and safety symbols on the
equipment.
Table 1-1 lists the warning and safety symbols of the OptiX RTN 980 and their meanings.
Table 1-1 Warning and safety symbols of the OptiX RTN 980
Symbol Indication
This symbol is for ESD protection.

A notice with this symbol indicates that you should wear
an ES wrist strap or glove when you touch a board.
Otherwise, you may cause damage to the board.
This symbol is for the laser class.

CLASS 1
LASER A notice with this symbol indicates the class of the laser.
PRODUCT Avoid direct exposure to the laser beams. Otherwise, it
may damage you eyes or skin.
LASER
RADIATION
DO NOT VIEW DIRECTLY

WITH OPTICAL
INSTRUMENTS
CLASS 1M LASER
PRODUCT

Symbol Indication
A notice with this symbol indicates where the subrack is

grounded.
A notice with this symbol indicates that the air filter

ATTENTION 警告 should be cleaned periodically.
CLEAN PERIODICALLY定期清洗
严禁在风扇高速旋转时接触叶片 This symbol is for fan safety.

DON'T TOUCH THE
FAN LEAVES BEFORE A notice with this symbol indicates that the fan leaves
THEY SLOW DOWN !
should not be touched when the fan is rotating.
1.3 Electrical Safety

This topic describes safety precautions for high voltage, lightning strikes, high leakage
current, power cables, fuses, and ESD.
High Voltage
DANGER
l A high-voltage power supply provides power for device operations. Direct human contact
with the high voltage power supply or human contact through damp objects can be fatal.
l Unspecified or unauthorized high voltage operations could result in fire or electric shock,
or both.
Thunderstorm
The requirements apply only to wireless base stations or devices with antennas and feeders.
DANGER
Do not perform operations on high voltage, AC power, towers, or backstays in stormy
weather conditions.

High Leakage Current
CAUTION
Before powering on a device, ground the device. Otherwise, the safety of humans and the
device cannot be ensured.
If a high leakage current mark is labeled near the power connector of the device, you must
connect the PGND terminal on the shell to the ground before connecting the device to an A/C
input power supply. This is to prevent the electric shock caused by leakage current of the
device.
Power Cables
DANGER
Do not install or remove the power cable with a live line. Transient contact between the core
of the power cable and the conductor may generate electric arc or spark, which may cause fire
or eye injury.
l Before installing or removing power cables, you must power off the device.
l Before connecting a power cable, you must ensure that the label on the power cable is
correct.
Device with Power On
DANGER
Installing or removing a device is prohibited if the device is on.
DANGER
Do not install or remove the power cables of the equipment when it is powered on.
Short Circuits
When installing and maintaining devices, place and use the associated tools and instruments
in accordance with regulations to avoid short-circuits caused by metal objects.

NOTICE
To avoid short-circuits when using a tool (such as a screwdriver), do not place the tool on the
ventilation plate of the subrack.
NOTICE
Prevent any screws from dropping into the subrack or chassis to avoid short-circuits.
Fuse
CAUTION
If the fuse on a device blows, replace the fuse with a fuse of the same type and specifications
to ensure safe operation of the device.
Electrostatic Discharge
NOTICE
The static electricity generated by the human body may damage the electrostatic sensitive
components on the board, such as the large-scale integrated circuit (LSI).
l The human body can generate static electromagnetic fields in the following situations:
physical movement, clothing friction, friction between shoes and the ground, plastics in
the hand. Such static electromagnetic effects can remain for an appreciable time.
l Before operating a device, circuit boards, or ASICs, wear an ESD wrist strap that is
properly grounded. The ESD wrist strap can prevent the electrostatic-sensitive
components from being damaged by the static electricity in the human body.
Figure 1-1 shows the method of wearing an ESD wrist strap.

Figure 1-1 Wearing an ESD wrist strap
1.4 Environment of Flammable Gas

This topic describes safety precautions for the operating environment of a device.
DANGER
Do not place or operate devices in an environment of flammable or explosive air or gas.
Operating an electronic device in an environment of flammable gas causes a severe hazard.
1.5 Storage Batteries

This topic describes safety precautions for operations of storage batteries.
DANGER
Before operating a storage battery, you must read the safety precautions carefully and be
familiar with the method of connecting a storage battery.
l Incorrect operations of storage batteries cause hazards. During operation, prevent any
short-circuit, and prevent the electrolyte from overflowing or leakage.
l If the electrolyte overflows, it causes potential hazards to the device. The electrolyte may
corrode metal parts and the circuit boards, and ultimately damage the circuit boards.
l A storage battery contains a great deal of energy. Misoperations may cause a short-
circuit, which leads to human injuries.

Basic Precautions
To ensure safety, note the following points before installing or maintaining the storage
battery:
l Use special insulation tools.
l Wear an eye protector and take effective protection measures.
l Wear rubber gloves and a protection coat to prevent the hazard caused by the
overflowing electrolyte.
l When handling the storage battery, ensure that its electrodes are upward. Leaning or
reversing the storage battery is prohibited.
l Before installing or maintaining the storage battery, ensure that the storage battery is
disconnected from the power supply that charges the storage battery.
Short-Circuit
DANGER
A battery short-circuit may cause human injuries. Although the voltage of an ordinary battery
is low, the instantaneous high current caused by a short-circuit emits a great deal of energy.
Avoid any short-circuit of batteries caused by metal objects. If possible, disconnect the
working battery before performing other operations.
Hazardous Gas
NOTICE
Do not use any unsealed lead-acid storage battery. Lay a storage battery horizontally and fix it
properly to prevent the battery from emitting flammable gas, which may cause fire or device
erosion.
Working lead-acid storage batteries emit flammable gas. Therefore, ventilation and
fireproofing measures must be taken at the sites where lead-acid storage batteries are placed.
Battery Temperature
NOTICE
If a battery overheats, the battery may be deformed or damaged, and the electrolyte may
overflow.
When the temperature of the battery is higher than 60°C, you need to check whether the
electrolyte overflows. If the electrolyte overflows, take appropriate measures immediately.

Battery Leakage
NOTICE
In the event of acid overflow or spillage, neutralize the acid and clean it up appropriately.
When handling a leaky battery, protect against the possible damage caused by the acid. When
you find the electrolyte leaks, you can use the following substances to counteract and absorb
the leaking electrolyte:
l Sodium bicarbonate (NaHCO3)

l Sodium carbonate (Na2CO3)
In the event of acid overflow or spillage, neutralize the acid and clean it up as recommended
by the battery manufacturer and any local regulations for acid disposal.
If a person contacts battery electrolyte, clean the skin that contacts the battery electrolyte
immediately by using water. In case of a severe situation, the person must be sent to a hospital
immediately.
1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
1.6.1 Safe Usage of Optical Fibers

The laser beam can cause damage to your eyes. Hence, you must exercise caution when using
optical fibers.
DANGER
When installing or maintaining an optical interface board or optical fibers, avoid direct eye
exposure to the laser beams launched from the optical interface board or fiber connectors. The
laser beam can cause damage to your eyes.
Cleaning Fiber Connectors and Optical Interfaces
NOTICE
If fiber connectors or flanges are contaminated, optical power commissioning is seriously
affected. Therefore, the two endfaces and flange of every external fiber must be cleaned
before the fiber is led into the equipment through the ODF for being inserted into an optical
interface on the equipment.

The fiber connectors and optical interfaces of the lasers must be cleaned with the following
special cleaning tools and materials:
l Special cleaning solvent: It is preferred to use isoamylol. Propyl alcohol, however, can
also be used. It is prohibited that you use alcohol and formalin.
l Non-woven lens tissue
l Special compressed gas
l Cotton stick (medical cotton or long fiber cotton)
l Special cleaning roll, used with the recommended cleaning solvent
l Special magnifier for fiber connectors
For cleaning steps, see Task Collection "Cleaning Fiber Connectors and Adapters" in the
OptiX RTN 980 Radio Transmission System Maintenance and Troubleshooting.
Replacing Optical Fibers

When replacing an optical fiber, cover the fiber connector of the unused optical fiber with a
protective cap.
Connecting Optical Fibers

l Use an attenuator if the optical power is excessively high. A high received optical power
damages the optical interface.
l Directly connect an attenuator to a slanting optical interface. Install the attenuator on the
IN port instead of the OUT port.
l Do not directly connect an attenuator to the level optical interface. Use the optical
distribution frame (ODF) to connect an attenuator to a level optical interface.
Figure 1-2 shows a slanting optical interface, and Figure 1-3 shows a level optical interface.
Figure 1-2 Slanting optical interface
Slanting optical
interface

Figure 1-3 Level optical interface
Level optical
interface
1.6.2 Electromagnetic Exposure

This topic describes safety precautions for electromagnetic exposure.
If multiple transmit antennas are installed on a tower or backstay, keep away from the
transmit directions of the antennas when you install or maintain an antenna locally.
NOTICE
Ensure that all personnel are beyond the transmit direction of a working antenna.
1.6.3 Forbidden Areas

The topic describes requirements for a forbidden area.
l Before entering an area where the electromagnetic radiation is beyond the specified
range, the associated personnel must shut down the electromagnetic radiator or stay at
least 10 meters away from the electromagnetic radiator, if in the transmit direction.
l A physical barrier and an eye-catching warning flag should be available in each
forbidden area.
1.6.4 Laser
This topic describes safety precautions for lasers.
CAUTION
When handling optical fibers, do not stand close to, or look into the optical fiber outlet
directly without eye protection.

Laser transceivers are used in the optical transmission system and associated test tools. The
laser transmitted through the bare optical fiber produces a small beam of light, and therefore it
has very high power density and is invisible to human eyes. When a beam of light enters eyes,
the eyes may be damaged.
In normal cases, viewing an un-terminated optical fiber or a damaged optical fiber without
eye protection at a distance greater than 150 mm does not cause eye injury. Eye injury may
occur, however, if an optical tool such as a microscope, magnifying glass, or eye loupe is used
to view an un-terminated optical fiber.
Safety Instructions Regarding Lasers

To avoid laser radiation, obey the following instructions:
l All operations should be performed by authorized personnel who have completed the
required training courses.
l Wear a pair of eye-protective glasses when you are handling lasers or fibers.
l Ensure that the optical source is switched off before disconnecting optical fiber
connectors.
l Do not look into the end of an exposed fiber or an open connector when you are not sure
whether the optical source is switched off.
l Use an optical power meter to measure the optical power and ensure that the optical
source is switched off.
l Before opening the front door of an optical transmission device, ensure that you are not
exposed to laser radiation.
l Do not use an optical tool such as a microscope, a magnifying glass, or an eye loupe to
view the optical connector or fiber that is transmitting optical signals.
Instructions Regarding Fiber Handling

Read and abide by the following instructions before handling fibers:
l Only trained personnel are permitted to cut and splice fibers.

l Before cutting or splicing a fiber, ensure that the fiber is disconnected from the optical
source. After disconnecting the fiber, cap to the fiber connectors.
1.6.5 Microwave
When installing and maintaining the equipment of Huawei, follow the safety precautions of
microwave to ensure the safety of the human body and the equipment.
CAUTION
Strong radio frequency can harm the human body.
When installing or maintaining an aerial on the tower or mast that is installed with multiple
aerials, switch off the transmitter in advance.

1.7 Working at Heights

This topic describes safety precautions for working at heights.
CAUTION
When working at heights, be cautious to prevent objects from falling down.
The requirements for working at heights are as follows:

l The personnel who work at heights must be trained.
l Carry and handle the operating machines and tools with caution to prevent them from
falling down.
l Safety measures, such as wearing a helmet and a safety belt, must be taken.
l Wear cold-proof clothes when working at heights in cold areas.
l Check all lifting appliances thoroughly before starting the work, and ensure that they are
intact.
1.7.1 Hoisting Heavy Objects

This topic describes the safety precautions for hoisting heavy objects that you must follow
when installing, operating, and maintaining Huawei devices.
CAUTION
When heavy objects are being hoisted, do not walk below the cantilever or hoisted objects.
l Only trained and qualified personnel can perform hoisting operations.

l Before hoisting heavy objects, check that the hoisting tools are complete and in good
condition.
l Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object
or wall with good weight-bearing capacity.
l Issue orders with short and explicit words to ensure correct operations.
l Ensure that the angle between the two cables is less than or equal to 90 degrees during
the lifting, as shown in Figure 1-4.

Figure 1-4 Hoisting heavy objects
1.7.2 Using Ladders

This topic describes safety precautions for using ladders.
Checking Ladders
l Before using a ladder, check whether the ladder is damaged. After checking that the
ladder is in good condition, you can use the ladder.
l Before using a ladder, you should know the maximum weight capacity of the ladder.
Avoid overweighing the ladder.
Placing Ladders
The proper slant angle of the ladder is 75 degrees. You can measure the slant angle of the
ladder with an angle square or your arms, as shown in Figure 1-5. When using a ladder, to
prevent the ladder from sliding, ensure that the wider feet of the ladder are downward, or take
protection measures for the ladder feet. Ensure that the ladder is placed securely.

Figure 1-5 Slanting a ladder
Climbing Up a Ladder
When climbing up a ladder, pay attention to the following points:
l Ensure that the center of gravity of your body does not deviate from the edges of the two
long sides.
l Before operations, ensure that your body is stable to reduce risks.
l Do not climb higher than the fourth rung of the ladder (counted from up to down).
If you want to climb up a roof, ensure that the ladder top is at least one meter higher than the
roof, as shown in Figure 1-6.
Figure 1-6 Ladder top being one meter higher than the roof

1.8 Mechanical Safety

This topic describes safety precautions for drilling holes, handling sharp objects, operating
fans, and carrying heavy objects.
Drilling Holes
CAUTION
Do not drill holes on the cabinet without prior permission. Drilling holes without complying
with the requirements affects the electromagnetic shielding performance of the cabinet and
damages the cables inside the cabinet. In addition, if the scraps caused by drilling enter the
cabinet, the printed circuit boards (PCBs) may be short-circuited.
l Before drilling a hole on the cabinet, remove the cables inside the cabinet.
l Wear an eye protector when drilling holes. This is to prevent eyes from being injured by
the splashing metal scraps.
l Wear protection gloves when drilling holes.
l Take measures to prevent the metallic scraps from falling into the cabinet. After the
drilling, clean up the metallic scraps.
Sharp Objects
CAUTION
Wear protection gloves when carrying the device. This is to prevent hands from being injured
by the sharp edges of the device.
Fans
l When replacing parts, place the objects such as the parts, screws, and tools properly. This
is to prevent them from falling into the operating fans, which damages the fans or device.
l When replacing the parts near fans, keep your fingers or boards from touching operating
fans before the fans are powered off and stop running. Otherwise, the hands or the
boards are damaged.
Carrying Heavy Objects

Wear protection gloves when carrying heavy objects. This is to prevent hands from being
hurt.

CAUTION
l The carrier must be prepared for load bearing before carrying heavy objects. This is to
prevent the carrier from being strained or pressed by the heavy objects.
l When you pull a chassis out of the cabinet, pay attention to the unstable or heavy objects
on the cabinet. This is to prevent the heavy objects on the cabinet top from falling down,
which may hurt you.
l Generally, two persons are needed to carry a chassis. It is prohibited that only one person
carries a heavy chassis. When carrying a chassis, the carriers should stretch their backs
and move stably to avoid being strained.
l When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not hold
the handles of the modules installed in the chassis, such as the power modules, fan
modules, and boards.
1.9 Other Precautions

This topic describes safety precautions for removing and inserting boards, binding signal
cables, and routing cables.
Removing and Inserting a Board
NOTICE
When inserting a board, wear an ESD wrist strap or ESD gloves, and handle the board gently
to avoid distorting pins on the backplane.
l Slide the board along the guide rails.

l Do not contact one board with another to avoid short-circuits or damage.
l When holding a board in hand, do not touch the board circuits, components, connectors,
or connection slots of the board to prevent damage caused by ESD of the human body to
the electrostatic-sensitive components.
Binding Signal Cables
NOTICE
Bind the signal cables separately from the high-current or high-voltage cables.
Routing Cables
In the case of extremely low temperature, heavy shock or vibration may damage the plastic
skin of the cables. To ensure the construction safety, comply with the following requirements:

l When installing cables, ensure that the environment temperature is above 0°C.
l If the cables are stored in a place where the ambient temperature is below 0°C, transfer
them to a place at room temperature and store the cables for more than 24 hours before
installation.
l Handle the cables gently, especially in a low-temperature environment. Do not perform
any improper operations, for example, pushing the cables down directly from a truck.
High Temperature
CAUTION
If the ambient temperature exceeds 55°C, the temperature of the front panel surface marked
the flag may exceed 70°C. When touching the front panel of the board in such an
environment, you must wear the protection gloves.
IF Cables
CAUTION
Before installing or removing an IF cable, you must turn off the power switch of the IF board.

Maintenance Guide 2 Notices for High-Risk Operations
2 Notices for High-Risk Operations
About This Chapter
This topic provides notices for the operations that may cause bodily injury or equipment
damage if they are not performed properly during the commissioning and maintenance of
microwave equipment.
2.1 Operation Guide for the Toggle Lever Switch

The ODU-PWR switch on the IF board is a toggle lever switch which must be turned on and
off according to the following instructions to avoid damaging the IF board.
2.2 Operation Guide for the IF Jumper
Before installing or removing IF jumpers, shut down the ODU power supply to prevent
personal injuries and damaged to the IF boards or ODU.
2.3 Operation Guide for the IF Cables
Before installing or removing IF cables, shut down the ODU power supply to prevent
2.4 Operation Guide for the IF Board
Before removing or installing an IF board, turn off the ODU-PWR switch to avoid bodily
injury or damage to the IF board and ODU.

2.1 Operation Guide for the Toggle Lever Switch

The ODU-PWR switch on the IF board is a toggle lever switch which must be turned on and
off according to the following instructions to avoid damaging the IF board.
Position and Description of the Toggle Lever Switch

The toggle lever switch is located on the IF board and controls the power that is fed to the
ODU, as shown in Figure 2-1.
NOTE
ISM6 boards do not have any toggle lever switches.
Figure 2-1 Toggle lever switch
Turning On the Toggle Lever Switch

1. Gently pull on the toggle lever switch out.

2. Turn it to the left.
3. Release the toggle lever switch.
Turning Off the Toggle Lever Switch

1. Gently pull on the toggle lever switch out.

2. Turn it to the right.
3. Release the toggle lever switch.
2.2 Operation Guide for the IF Jumper

Before installing or removing IF jumpers, shut down the ODU power supply to prevent
Precaution
NOTICE
l For an IF board with a power switch, do not disconnect/connect the IF jumper with power
on.
l For an IF board (ISM6) without a power switch, do not disconnect/connect the IF jumper
with no load; that is, ensure that the IF jumper is already connected to its IF cable and
ODU.
Procedure
Step 1 For an IF board with a power switch:
1. Follow instructions in 2.1 Operation Guide for the Toggle Lever Switch to power off
the ODU.

DANGER
Ensure that the ODU is completely powered off before removing or installing the IF
jumper.
2. Remove or install the IF jumper.

Step 2 For an IF board (ISM6) without a power switch:
1. Ensure that the IF jumper is already connected to its IF cable and ODU.
2. Disconnect/Connect the IF jumper.
----End
2.3 Operation Guide for the IF Cables

Before installing or removing IF cables, shut down the ODU power supply to prevent

Precautions
NOTICE
on.
ODU.
Procedure
1. Follow instructions in 2.1 Operation Guide for the Toggle Lever Switch to power off
the ODU.
DANGER
cable.
2. Install or remove the IF cables.


2. Connect/Disconnect the IF cable.

----End
2.4 Operation Guide for the IF Board

Before removing or installing an IF board, turn off the ODU-PWR switch to avoid bodily
injury or damage to the IF board and ODU.
Precautions
NOTICE
on.
ODU.
Procedure
1. Turn off the ODU-PWR switch on the IF board. For details, see 2.1 Operation Guide
for the Toggle Lever Switch.
1 2 3

DANGER
board.
2. Disconnect the IF jumper or IF cable.

3. Remove or install the IF board.
2. Disconnect the IF jumper/IF cable.
3. Disconnect/Connect the IF board.
----End

Maintenance Guide 3 Routine Maintenance
3 Routine Maintenance
Routine maintenance operations are performed to detect and rectify hidden faults before the
hidden faults cause damage to equipment and affect services. Routine maintenance operations
are preventive measures.
Routine maintenance items are classified into routine maintenance items carried out on the
NMS, field maintenance items for indoor equipment, and field maintenance items for outdoor
equipment.
NOTE
Microwave equipment requires professional preventive maintenance inspection (PMI) operations.

Contact Huawei engineers to carry out the PMI operations.
Routine Maintenance Items Carried Out on the NMS

Maintenance Item Recommen Check Point
ded
Maintenan
ce Cycle
4.1 Checking the NE Every day l If the NE icon is green, the NE operates
Status properly.
l If the NE icon is gray, the NE is
unreachable due to DCN faults.
l If the NE icon is in other colors, alarms
are reported or exceptions occur. You
need to troubleshoot in time.
4.3.1 Browsing Current Every day l Handle the alarms by referring to A.3
Alarms Alarms and Handling Procedures.
l For port alarms due to the interconnected
equipment, see 4.9.5 Reversing Alarms
for Service Ports to reduce the number
of alarms and prevent interference to
emergent alarms.


ded
Maintenan
ce Cycle
4.3.2 Browsing Historical Every week By finding causes of and solutions to

Alarms historical alarms, you can take precautions
to avoid related faults.
Browsing abnormal events Every week l Security events are generally records of
normal operations. Investigate the illegal
operations if there are any.
l Abnormal events about equipment have
been properly solved.
4.3.3 Browsing Current Every week l Gauge type performance events such as
Performance Events the board temperature and laser power
are stable.
4.3.4 Browsing Historical Every week
Performance Events l Bit error type performance events meet
requirements on link availability.
4.4.1 Querying the Every week l Historical received signal levels do not
Historical Transmit Power exceed the fade margin for a long time.
and Receive Power l When automatic transmit power control
(ATPC) is disabled, historical
transmitted signal levels are allowed to
be 3 dB larger or smaller than the
specified value.
Testing N+1 Protection Half a year For equipment that is configured with N+1
Switching protection, perform manual switching to
check whether the protection has taken
effect. After the test is completed, clear the
switching to restore to the normal protection
status.
NOTE
During the N+1 protection switching, the
protected services are interrupted. It is
recommended that you perform the N+1
protection switching when the traffic is light.
Maximum number of alarms and performance events that the NE can store
The NE can record and store NE alarm and performance data in a 15-minute or 24-hour
monitoring period.
NOTE
You can use the performance management system (PMS) on the U2000 to store historical performance
data for a long term.

Item Specifications
Historical alarms 1000

NOTE
An NE uses loop queues with priorities to store alarms. When the number of
alarms in a queue reaches 1000, new major alarms overwrite existing minor
alarms and suggestions.
Historical l Sixteen 15-minute historical performance events

performance events l Six 24-hour historical performance events
(excluding RMON
NOTE
performance events) For the following performance events, an NE can store thirty 24-hour
historical performance events and six hundred and seventy two 15-minute
historical performance events:
l IF_BBE, IF_ES, IF_SES, IF_UAS
l IF_SNR_AVG, IF_SNR_MAX, IF_SNR_MIN
l RSL_AVG, RSL_MAX, RSL_MIN
l TSL_AVG, TSL_MIN, TSL_MAX
l FEC_BEF_COR_ER, FEC_UNCOR_BLOCK_CNT
l MAXPHASEOFFSET
l MAXFREQDEV
l CURPOSITIVEPDV
You cannot perform the operation of browsing historical performance events
on the NMS to query the preceding long-period performance events stored
on an NE. You need to use a data collection tool to collect the performance
events.
Historical RMON l Sixteen 30-second historical performance events

performance events l Ninety-six 30-minute historical performance events
l Forty 15-minute historical performance events
l Six 24-hour historical performance events
NOTE
The preceding numbers are the default values. You can change them by
modifying historical Ethernet performance monitoring parameters. A
maximum of 50 historical performance events can be stored in each period.
Field Maintenance Items for Indoor Equipment

ded
Maintenan
ce Cycle
Checking the Every two The site environment meets equipment

telecommunications room months operation requirements.

Field Maintenance Items for Outdoor Equipment

Maintenance Item Recommended Check Point
Maintenance Cycle
Checking the ODUa Half a year The ODU is securely

NOTE mounted and its appearance
Perform a complete check is in good condition, without
after a level-8 or higher-level the coating being damaged
hurricane, an earthquake, or or corroded.
other unexpected
Checking the hybrid circumstances. The hybrid coupler is fixed
couplera NOTICE and secure, with intact
In high-corrosion areas, check appearance and free from
whether outdoor components
and fasteners are loose due to
damage or corrosion to the
corrosion. If yes, take rust- and paint.
corrosion-proof measures or
Checking the antennaa replace the corroded The antenna is tightly placed
components or fasteners. and does not deviate from
the designed angle.
Checking the IF cable and The exterior of the cable is

flexible waveguidea intact, and the connectors
are properly waterproofed.
The cable is fixed properly
with a feeder fastener or
cable ties, and the cable
bending degree meets the
requirement.
Checking the LOS condition A radio link is not blocked

by any visible object.
NOTE
a:An area close to a pollution source refers to the area that covers a radius within any of the following
values:
l 3.7 km away from salty waters (such as an ocean and salty water)
l 3 km away from severe pollution sources (such as iron refinery works, and coal mines)
l 2 km away from intermediate pollution sources (such as chemical plants, rubber processing works,
and electroplating workshops)
l 1 km away from light pollution sources (such as food processing works, leather working plants, and
heating boilers).

Maintenance Guide 4 Network Monitoring
4 Network Monitoring
About This Chapter
4.1 Checking the NE Status

You can learn about the basic information such as whether the NE fails to communicate with
the NMS and whether any alarms are reported by checking the NE status.
4.2 Checking the Board Status
You can learn about the board status in a visual manner by checking the slot diagram.
4.3 Alarm and Performance Data Query
This section describes how to query alarms and non RMON-based performance data, such as
SDH performance data and microwave link performance data. You can query real-time and
historical performance data, which are monitored based on a 15-minute or 24-hour monitoring
period.
4.4 Microwave Link Performance Query
This section describes operations related to microwave link performance query.
4.5 Ethernet Performance Query
This section describes operations related to Ethernet performance query.
4.6 Ethernet Port Traffic Monitoring
This section describes operations related to Ethernet traffic monitoring on Ethernet ports and
microwave ports.
4.7 Long-term Network Performance Monitoring
The U2000 centrally monitors long-term performance of various Huawei devices through the
Performance Management System (PMS).
4.8 Report Query
This section describes operations related to report query. You can obtain network information
from reports.
4.9 Alarm and Performance Management Setting
This section describes operations related to alarm and performance management.

4.1 Checking the NE Status

You can learn about the basic information such as whether the NE fails to communicate with
the NMS and whether any alarms are reported by checking the NE status.
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Tools, Equipment, and Materials

U2000
Precautions
NOTE
By default, the color of the NE icon on the U2000 indicates the NE status.
Procedure
Step 1 Query NE running status.
Select the View NE running

desired NE. status.
1
4

NOTE
You can also determine NE running status by referring to information on the Legend tab.
NOTE
Complete the following steps to check NE running status from the WebLCT:
1. Query Communication status and Login status of the NE in NE List.
2. If Login status is Offline, log in to the NE.
3. Select the NE and click Log in.
4. Set User Name and Password.
NOTE
The default user name is lct.

The lct account owns system-level rights.
The default password of the lct account is Changeme_123.
5. View NE status and alarm status.
----End
4.2 Checking the Board Status

You can learn about the board status in a visual manner by checking the slot diagram.
Prerequisites


U2000
Procedure
Step 1 Query board running status.
3
Determine the board
running status by referring
Right-click to legend information.
the desired
NE.
4
NOTE
Complete the following step to query board running status from the WebLCT:
Click the Slot Layout tab in NE Explorer.
----End
4.3 Alarm and Performance Data Query

This section describes how to query alarms and non RMON-based performance data, such as
SDH performance data and microwave link performance data. You can query real-time and
historical performance data, which are monitored based on a 15-minute or 24-hour monitoring
period.
4.3.1 Browsing Current Alarms

You can find the faults that occur on the equipment by browsing current alarms.
Prerequisites

U2000

Procedure
Step 1 Open the current alarm window.
1
2
Step 2 Specify filter conditions.

Configure the severity, type, and

maintenance status parameters of the
3 alarms to be queried.
Set the occurring time and clearing time

of the alarms to be queried.
4
Click the Alarm Source tab and

specify filter conditions.
5
6
Select the desired
8 NEs.
Configure the filter

type. For example,
you can filter alarms
by NE.
7
10
11
Step 3 View alarm information.

Select an alarm and view its details

and possible causes in the following
panes.
12
Alarm details: contain information

about the board and optical port that Alarm handling: contains possible
report the alarm as well as alarm causes for the alarm and reference
parameters. links to alarm handling suggestions
Step 4 Contact troubleshooting personnel in a timely manner for alarm handling.

For details about alarm handling, see A.3 Alarms and Handling Procedures.

NOTE
Complete the following steps to browse current alarms from the WebLCT:
Select the NE from the NE Explorer and click in the tool bar.
The Browse Current Alarms tab page is displayed by default.
----End
Related Information
A current alarm refers to an alarm that is not cleared.
By U2000, you can browse the network-wide alarms based on the alarm severity by clicking
the alarm indicators in the upper right corner.
l You can click (red) to browse the network-wide critical alarms.
l You can click (orange) to browse the network-wide major alarms.
l You can click (yellow) to browse the network-wide minor alarms.
l You can click (light-blue) to browse the network-wide warning alarms.

NOTE
By default, the number shown by each indicator indicates the number of current network-wide alarms, which
are not cleared, of the specific severity.
By Web LCT, you can also click an alarm indicator on the toolbar to display the NE alarms of
the specific severity.
From left to right, the alarm indicators and corresponding alarm severities are as follows:
l Red: critical alarm

l Orange: major alarm

l Yellow: minor alarm
l Purple: warning
l Light blue: event
4.3.2 Browsing Historical Alarms

You can know the faults that occur on the equipment in a past period of time by browsing
historical alarms. A historical alarm refers to an alarm that is already cleared.
Prerequisites
You must be an NM user with NE monitor authority or higher.

U2000
Procedure
Step 1 Open the historical alarm window.

Configure the severity, type, and maintenance

3 status parameters of the alarms to be queried.
Set the occurring time and clearing time

of the alarms to be queried.
4

Click the Alarm Source tab and

specify filter conditions.
5
6
Select the desired
8 NEs.
Configure the filter

type. For example,
you can filter alarms
by NE.
7
10
11
Step 3 View alarm information.

12 Select an alarm and view its details

and possible causes in the following
panes.
Alarm details: contain information about Alarm handling: contains possible

the board and optical port that report the causes for the alarm and reference
alarm as well as alarm parameters. links to alarm handling suggestions
NOTE
Complete the following steps to browse current alarms from the WebLCT:
Select the NE from the NE Explorer and click in the tool bar.
Click the Browse Historical alarms tab.
----End
4.3.3 Browsing Current Performance Events

You can know the running status of the equipment by browsing current SDH/PDH
performance events. The counter of current performance events measures all the performance
events that arise between the start time of the monitoring period and the current time.
Prerequisites
l The performance monitoring function must be enabled. For details about how to enable
the performance monitoring function, see Configuring the Performance Monitoring
Status of NEs.
l You must be an NM user with NE maintainer authority or higher.

U2000
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.

Procedure
Step 1 Open the performance data window.
1
Step 2 View current performance data.
Select performance event types and

4 specify the performance monitoring
6 period.
5
3
Configure the query type.
Select the desired For example, Measure is
NEs. selected here.
(Optional) Output the

performance data.
7 8

NOTE
Complete the following steps to query current performance data from the WebLCT:
Select the desired board in the NE Explorer and choose Performance > Current Performance from the
Function Tree.
----End
4.3.4 Browsing Historical Performance Events

You can know the faults that occur on the equipment in a past period of time by browsing
historical performance events.
Prerequisites
l The performance monitoring function must be enabled. For details about how to enable
the performance monitoring function, see Configuring the Performance Monitoring
Status of NEs.

U2000
NOTE
Procedure
Step 1 Open the performance data window.
1
2
3
Step 2 View historical performance data.

6
4
7
Select Data Source.
6 If you select Query from NMS, historical performance data will be obtained from
Configure the query type. For the U2000 database.
example, Count is selected here. 6 If you select Query from NE, a message will be sent through an interface to obtain
historical performance data from NEs.
6 Historical performance data of NEs changes with services. To query the latest
historical performance data of NEs and save the data to the U2000 database, set
Data Source to Query from NE and select Save to Database. Then the data is
saved to the U2000 database and you can query it from the database by selecting
Query from NMS next time.
NOTE
Complete the following steps to query historical performance data from the Web LCT:
Select the desired board in the NE Explorer and choose Performance > Historical Performance from the
Function Tree.
The Web LCT does not support data source selection.
----End
4.3.5 Browsing the Performance Event Threshold-Crossing

Records
You can learn about the threshold-crossing information of the performance events of an NE
by browsing the performance event threshold-crossing records.
Prerequisites

U2000
NOTE
Procedure
Step 1 Open the Performance Threshold-Crossing Record window.

2
3
Step 2 Query performance threshold-crossing records.
Select performance event types

5
and specify the performance
6 monitoring period.
Select the desired

NEs.
NOTE
Complete the following steps to query performance threshold-crossing records from the WebLCT:
Select a desired board in the NE explorer and choose Performance > Threshold-Crossing Record from the
Function Tree.
----End

4.3.6 Browsing UAT Events

Learn about the severe abnormalities on the transmission line by browsing UAT events.
Prerequisites
Tools, Instruments, and Materials

U2000
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
UAT refers to a period of 10 consecutive seconds during which the bit error ratio per second
of the digital signal in either of the transmission directions of a transmission system is inferior
to 10-3. These 10 seconds are considered to be part of the unavailable time.
Procedure
Step 1 Open the UAT window
1
2
3
Step 2 Query UAT events.

5
Specify the time period, data source
6 and functional block type.
Select the
desired board.
----End
4.4 Microwave Link Performance Query

This section describes operations related to microwave link performance query.
4.4.1 Querying the Historical Transmit Power and Receive Power

If the radio link requires troubleshooting, query the change trend for the historical transmit
power and receive power for reference.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.

U2000
NOTE
Procedure
Step 1 Query historical receive power or transmit power information.

Set the time range, monitoring period, and

3 power parameters.
In the NE Explorer,
select the desired
ODU. 4
Click Draw.
The power curve is
1 displayed.
----End
4.4.2 Querying the SNR Values of a Radio Link

This section describes how to query the signal-to-noise ratio (SNR) change curve of a radio
link, assisting in handling radio link faults.
Prerequisites
l The IF boards and the ODUs to which the IF boards are connected have been added in
the NE Panel.

U2000
NOTE
Procedure
Step 1 Query how the SNR or Root-mean-square (RMS) error changes on microwave links.

Set the time range, monitoring period, and

1 3 performance type (SNR or MSE).
In the NE Explorer,
select the desired IF 4
board.
Click Draw.
The SNR or MSE curve is
displayed.
----End
4.4.3 Browsing Current Performance Events of the radio link

You can learn about the current operating status of a radio link by browsing its current
performance data.
Prerequisites

U2000
Procedure
Step 1 Right-click a microwave link in the main topology and choose Microwave Link
Performance Statistics.

1
Right-click the desired
microwave link.

NOTE
Uncheck Auto Refresh. Click Save as to save current performance of the microwave link into a TXT file.
Complete the following steps to query current performance of the microwave link from the WebLCT:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave Link
Performance from the Function Tree.
----End
4.4.4 Browsing Historical Performance Data of a Radio Link

You can learn about the operating status of a radio link by browsing its historical performance
data over a specific period.
Prerequisites

U2000
NOTE
Procedure
Step 1 Query historical performance of the microwave link.
1
Right-click the desired
microwave link.

Specify the query period and

monitoring period of the the
3 4 desired performance data.
6 (Optional) Specify the data type to be

displayed. By default, link transmit power and
receive power are displayed. (Optional) Move the cursor
over the desired node to
check link information at a
specific time.
8
NOTE
Complete the following steps to query historical performance of the microwave link from the WebLCT:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave Link
Performance from the Function Tree.
----End
4.5 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).
4.5.1 Browsing Current Ethernet Performance

After setting the RMON statistics group. you can browse real-time Ethernet performance
statistics.
Prerequisites

l The corresponding board must be added in the NE Panel.

U2000
NOTE
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Table 4-1 Packet plane

Performa Browsed Navigation Path
nce Object
Object
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended NOTE
performan a: Packet Ethernet ports include FE/GE ports, Integrated IP microwave
ce ports, PORT8 on the EMS6 board, and PORT10 on the EFP8 board.
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
1+1 group 1+1 group 1. In the NE Explorer, select the required NE from the Object
performan Tree and choose Configuration > IF 1+1 Protection.
ce 2. Select the desired 1+1 protection group, right-click, and
choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and


nce Object
Object
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
shortcut menu.
CES-PW CES 1. In the NE Explorer, select the NE from the Object Tree and
performan service choose Configuration > CES Service Management from
ce the Function Tree.
CES 2. Select one or more CES services, right-click the service(s),
performan and choose Browse Performance from the shortcut menu.
ce
ATM/IMA Smart E1 Select the corresponding board from the Object Tree in the NE
(access port Explorer. Choose Performance > RMON Performance from
side) the Function Tree.
performan
ce
ATM-PW ATM 1. In the NE Explorer, select the NE from the Object Tree and
performan PWE3 choose Configuration > ATM Service Management from
ce service the Function Tree.
ATM 2. Select one or more ATM PWE3 services, right-click the
PWE3 service(s), and choose Browse Performance from the
performan shortcut menu.
ce
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation Creating Traffic before monitoring the port
traffic classification performance.


nce Object
Object
Port Egress For FE/GE ports:

priority queues 1. Select the NE from the Object Tree in the NE Explorer.
performan Choose Configuration > Interface Management >
ce Ethernet Interface from the Function Tree.
2. Click the Basic Attributes tab.
3. Select one or multiple ports, right-click and choose Browse
4. Select the desired egress queue in the Object drop-down list.
For Integrated IP microwave ports:
1. Select the NE from the Object Tree in the NE Explorer.
Choose Configuration > Interface Management >
Microwave Interface from the Function Tree.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse


nce Object
Object
PW 1. In the NE Explorer, select the required NE from the Object

Tree and choose Configuration > MPLS Management >
PW Management.
Table 4-2 EoS/EoPDH plane
Performa Browse Navigation Path

nce Object
Object
Basic Ethernet In the NE Explorer, select the EFP8 or EMS6 board from the
performan portb Object Tree and choose Performance > RMON Performance
NOTE
Extended b:
performan EoPDH Ethernet ports include PORT1 to PORT9 on the EFP8 board.
ce
EoS Ethernet ports include PORT1 to PORT7 on the EMS6 board.
VCG-other VCTRUN
performan K port
ce
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
Step 2 Click the Statistics Group tab.
Step 3 Set the required parameters for the statistics group.

1. Select the desired object or port from the drop-down list.
2. Select the performance items for which statistics need to be collected.
3. Set Sampling Period.
Sampling Period represents the time unit of the performance statistics.
Step 4 Click Resetting begins.

NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End

4.5.2 Configuring Ethernet Performance Threshold-Crossing

Parameters
After setting the RMON alarm group. you can monitor whether the Ethernet performance
value crosses its threshold for a long time.
Prerequisites
l The corresponding boards must be added in the NE Panel.

U2000
NOTE
Procedure

nce Object
Object
Extended NOTE
ce Aggregation.


nce Object
Object
shortcut menu.
shortcut menu.
ce
performan
ce
ce


nce Object
Object
ce classificati
NOTE



nce Object
Object

PW Management.

nce Object
Object
NOTE
Extended b:
ce
VCG-other VCTRUN
performan K port
ce
NOTE
Step 2 Click the RMON Setting tab.
Step 3 Click the Event tab and set the corresponding parameters.
Step 4 Click Apply. Close the displayed dialog box.
----End

4.5.3 Setting Parameters for Monitoring Historical Ethernet

Performance
After configuring a historical control group, you can specify how the historical Ethernet
performance data is monitored.
Prerequisites

U2000
NOTE
Context
NOTE
To set parameters for monitoring historical Ethernet performance of multiple NEs on the U2000, choose
Performance > RMON History Control Group Management from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON
History Control Group.
Step 2 Set the parameters of the historical control group.
Step 3 Click Apply. Close the displayed dialog box.
----End
4.5.4 Browsing Historical Ethernet Performance Data

After configuring an history group, you can browse the historical performance statistics.
Prerequisites
l The objects and performance events to be monitored must be set.

U2000
NOTE

Procedure

nce Object
Object
Extended NOTE
ce Aggregation.
shortcut menu.


nce Object
Object
shortcut menu.
ce
performan
ce
ce
ce classificati
NOTE


nce Object
Object



nce Object
Object

PW Management.

nce Object
Object
NOTE
Extended b:
ce
VCG-other VCTRUN
performan K port
ce
NOTE
Step 2 Click the History Group tab.

Step 3 Set the parameters of the historical group.
1. Select the desired object or port from the drop-down list.
2. Click and specify the required time span.
3. Select the performance items to browse.
4. Under History Table Type, set the time span for the performance items to be browsed.
Step 4 Click Query.
----End
4.6 Ethernet Port Traffic Monitoring

This section describes operations related to Ethernet traffic monitoring on Ethernet ports and
microwave ports.

4.6.1 Setting Traffic, Physical Bandwidth, or Bandwidth

Utilization of Ethernet Ports
To query the traffic, physical bandwidth, or bandwidth utilization of Ethernet ports within a
certain period, you need to enable the monitoring for the object before that period starts. The
FE/GE ports and the ports on the packet plane support this operation.
Prerequisites

U2000
NOTE
Background Information
After the flow monitoring function is enabled, the system saves the statistics about the
received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the
system stores the statistics that are collected in the last 30 days. In the system, every
measurement entry shows the average transmit rate and average receive rate within a period
of 15 minutes. You can query the statistics in the last 30 days.
Procedure
Step 1 Set Ethernet performance monitoring parameters.
1
Select the board where

the desired Ethernet
port resides. 3 Configure whether to flow
monitoring, physical bandwidth
monitoring, and bandwidth
utilization monitoring.
----End

4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth

Utilization
This section describes how to query the change curve of the traffic, physical bandwidth, or
bandwidth utilization within a certain period. The FE/GE ports and the ports on the packet
plane support this operation.
Prerequisites
The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoring
function on a port, see 4.6.1 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization
of Ethernet Ports.

U2000
NOTE
After the flow monitoring function is enabled, the system saves the statistics about the
received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the
system stores the statistics that are collected in the last 30 days. In the system, every
measurement entry shows the average transmit rate and average receive rate within a period
of 15 minutes. You can query the statistics in the last 30 days.
This operation allows only the queries about port-based Ethernet traffic by using U2000. To
collect statistics about the traffic based on Tunnel/PW/egress queue/VLAN, see 4.5.1
Browsing Current Ethernet Performance or 4.5.4 Browsing Historical Ethernet
Performance Data.
Procedure
Step 1 Query traffic, physical bandwidth, and bandwidth utilization.

Select the
desired board. 5
3
Select the port
of the board.
4
Specify the time
period and display
mode.
----End
4.7 Long-term Network Performance Monitoring

The U2000 centrally monitors long-term performance of various Huawei devices through the
Performance Management System (PMS).
4.7.1 Creating a Performance Monitoring Template

This section describes how to create a performance monitoring template. Performance
monitoring templates specify counters used by performance monitoring instances and their
thresholds (if any). When counter values collected exceed the preset thresholds, the system
reports corresponding threshold crossing alerts (TCAs).
Prerequisites
You must be an NM user with NE operator authority or higher.

U2000
NOTE
The Web LCT does not support this operation.
Context
NOTE
You can create data monitoring templates and remote network monitoring (RMON) TCA monitoring
templates. To monitor Ethernet performance counters supporting TCAs, create RMON TCA monitoring
templates. To monitor other counters, create data monitoring templates.

Procedure
Step 1 Create a data monitoring template.
2 3
Select the monitoring

resource type.
4
Set the parameters of the

6 data monitoring template.
7
Click Add, and select the
performance monitoring
indicators.
Step 2 Create an RMON TCA monitoring template.

2 3
Select the monitoring

resource type.
4
Enter the template name and

set the template type to RMON
6 TAC.
Click Add, and select the

indicators.
9 Set the monitoring

threshold parameters.
10
----End
4.7.2 Creating a Performance Monitoring Instance

This section describes how to create a performance monitoring instance. A performance
monitoring instance can monitor the performance of multiple objects at the same time. You
can associate a created performance monitoring template and a created performance statistics
collection policy to a performance monitoring instance.

Prerequisites

U2000
NOTE
Procedure
Step 1 Open the Create Monitoring Instance dialog box.
Step 2 Select monitoring resources.

Select the desired

NE. Select the desired
4 port.
6
Step 3 Select the monitoring template.
(Optional) Select the desired data (Optional) If there is no desired

monitoring template if it is available. If data monitoring template, create
there is no desired template, go to step one for the instances.
10.
10
11
(Optional) If there is no desired RMON

threshold monitoring template, create one
for the instances.
(Optional) Select the desired RMON
threshold monitoring template if it is
available. If there is no desired template, 12
go to step 12.
13
NOTE
Complete step 9 and step 10 when creating a data monitoring instance.

Complete step 11 and step 12 when creating an RMON TCA monitoring instance.
Step 4 Specify the monitoring time.

14
NOTE
Skip this step for the OptiX RTN 980, which does not support the setting of monitoring time.
Step 5 Close the dialog box.
15
NOTE
If a creation success message is displayed, the creation is successful.

If the creation fails, determine the failure cause according to the displayed error information and recreate the
instance.
----End

4.7.3 Browsing the Real-Time Data of a Performance Monitoring

Instance
This section describes how to browse the real-time performance data of objects monitored by
a performance monitoring instance.
Prerequisites
l There is at least one performance monitoring instance.

U2000
NOTE
Procedure
Step 1 Open the real-time monitoring window.
Step 2 View real-time performance data.

(Optional) Set the

3 performance display
mode. The default value is
(Optional) Set the timeline granularity. 4 line chart.
The default value is 10s.
----End
4.7.4 Browsing the Historical Data of a Performance Monitoring

Instance
This section describes how to browse the performance data of objects monitored by a
performance monitoring instance in a specific time range.
Prerequisites
l There is at least one performance monitoring instance.

U2000
NOTE
Procedure
Step 1 Open the historical performance data window.

1 Right-click the desired

instance.
Step 2 View historical performance data.
----End
4.8 Report Query

This section describes operations related to report query. You can obtain network information
from reports.
4.8.1 Querying the Microwave Link Information Report

You can obtain the current and recent transmit/receive power of microwave links by querying
the microwave link information report.
Prerequisites

U2000
NOTE
Procedure
Step 1 Query the microwave link information report.

2 3
5
Select the desired

NEs.
4
(Optional) Output the link report.
----End
4.8.2 Querying the Network-wide License Report

By querying the network-wide license report, you can check the license information of each
NE.
Prerequisites

U2000
NOTE
Procedure
Step 1 Query the license capacity report of NEs.

2
3
Select the desired

4 NEs.
(Optional) Output the microwave

capacity report.
Step 2 Query the air-interface license capacity report of the network.

(Optional) Output the air-interface

capacity report.
----End
4.8.3 Querying the Microwave Configuration Report

You can output the configuration report into an XLS file.
Prerequisites

U2000
NOTE
Procedure
Step 1 Export the microwave configuration report of an RTN NE.

Select the types of

configuration data to be
3 exported.
Select the desired NEs. You

can also click the icon in the
red circle to quickly locate
desired NEs.
4 Specify the directory for

saving the report.
----End
4.8.4 Querying the Board Information Report

You can obtain the logic version, and software version of each board by querying the board
information report.
Prerequisites

U2000
NOTE
Procedure
Step 1 Open the board information query window.

1
2
4
Set Physical
Inventory Type to
Board.
3

Specify filter conditions. For

example, you can filter board
information by NE. 6
Select the
7 desired NEs.
Step 3 View query results.

(Optional) Output the board

information report.
10
NOTE
Complete the following steps to query the board information report from the WebLCT:
Select the NE from in the NE Explorer and choose Report > Board Information Report from the Function
Tree.
Version information of all boards is displayed in Board Information Report.
----End
4.8.5 Querying the Board Manufacturing Information Report

You can obtain the manufacturing information about each board and the SFP module by
querying the board manufacturing information report.
Prerequisites

U2000
NOTE

Procedure
Step 1 Query the board manufacturing information report.
1
2 3
5
Select the desired

NEs.
4
(Optional) Output the board

manufacturing information report.
NOTE
Complete the following steps to query the board manufacturing information report from the WebLCT:
Select the NE from in the NE Explorer and choose Report > Board Details Information Report from the
Function Tree.
Manufacturing information of all boards is displayed in Board Details Information Report.
----End
4.8.6 Querying the ODU Information Report

You can query information (such as the production date and SN) about the ODUs on a
network by querying the ODU information report.
Prerequisites

U2000
NOTE

Procedure
Step 1 Query ODU information.
(Optional) Output the ODU

information report.
4
----End
4.9 Alarm and Performance Management Setting

This section describes operations related to alarm and performance management.
Context
NOTE
The performance management in this section does not cover Ethernet performance
4.9.1 Configuring the Performance Monitoring Status of NEs

By performing this operation task, you can manually enable or disable performance
monitoring for NEs, or set the performance monitoring period.
Prerequisites

U2000
NOTE

Context
NOTE
To perform batch NE configurations on the U2000, choose Performance > Set NE Performance
Monitoring Time from the main menu.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE
Performance Monitoring Time from the Function Tree.
Step 2 Configure the performance monitoring parameters of the NEs.
1. Select 15-Minute or 24-Hour.
2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
NOTE
– Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
– You can specify the start time of the performance monitoring function, only after selecting Enabled
in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
– You can specify the end time of the performance monitoring function, only after selecting Enabled
and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
4. Click Apply. Close the displayed dialog box.
----End
4.9.2 Setting Severity and Auto Reporting Status of Alarms

This section describes how to set the severity and auto reporting status of specific alarms.
Prerequisites
Tools, Instruments and Materials

U2000

NOTE
Procedure
Step 1 In the NE Explorer, select the desired object.
Step 2 Choose Alarm > Alarm Severity and Auto Reporting from the Function Tree.
Step 3 Select any items in the column Event and set Severity and Auto Reporting Status for them.
Step 4 Click Apply to save the settings.
Step 5 Close the dialog box that is displayed.
----End
4.9.3 Suppressing Alarms for Monitored Objects

This section describes how to suppress specific alarms for a specific monitored object.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.

Step 3 Set Monitored Object and click Query.

Step 4 Set Status in Alarm Suppression.
Step 5 Click Apply.
NOTE
----End
4.9.4 Suppressing Alarms for NEs

This section describes how to suppress certain alarms for NEs.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.

Step 3 Set Status in Alarm Suppression.
Step 4 Click Apply.

NOTE
----End
4.9.5 Reversing Alarms for Service Ports

This section describes how to reverse alarms for service ports.
Prerequisites

U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE.
Step 2 Choose Alarm > NE Alarm Attribute from the Function Tree.
Step 3 Set Alarm Reversion to Enable (Manually Restore).
Step 4 Click Apply.

NOTE
Step 7 Choose Alarm > Alarm Reversion from the Function Tree.
Step 8 Set Reversion Status for the required port.
Step 9 Click Apply.

NOTE
----End
4.9.6 Setting the Reporting of Alarms and Performance Events for

an IF Port and the Corresponding ODU
This section describes how to set the reporting of alarms and performance events for an IF
port and the corresponding ODU.
Prerequisites

U2000
NOTE
Procedure
Step 1 Set the reporting of alarms and performance events for an IF port and the corresponding
ODU.
----End
4.9.7 Setting Trigger Conditions of AIS Insertion

This section describes how to set the trigger conditions of AIS insertion for specific
monitored objects.

Prerequisites

U2000
NOTE
Procedure
Step 2 Choose Alarm > QoS Alarm > AIS Insertion from the Function Tree.
Step 3 Set the trigger conditions of AIS insertion. If you select Enabled under an alarm, the AIS
signal is inserted when this alarm occurs; otherwise, the AIS signal is not inserted when this
alarm occurs.
Step 4 Click Apply.

NOTE
----End
4.9.8 Setting Trigger Conditions of UNEQ Insertion

This section describes how to set the trigger conditions of UNEQ insertion for service ports.
Prerequisites

U2000
NOTE
Procedure
Step 2 Choose Alarm > QoS Alarm > UNEQ Insertion Switch from the Function Tree.
Step 3 Set the trigger conditions of UNEQ insertion. If you select Enabled under an alarm, the
UNEQ signal (all 0s) is inserted when this alarm occurs; otherwise, the UNEQ signal is not
inserted when this alarm occurs.

Step 4 Click Apply.

NOTE
----End
4.9.9 Setting Bit Error Thresholds for Service Ports

This section describes how to set bit error thresholds for service ports.
Prerequisites

U2000
NOTE
Procedure
Step 2 Choose Alarm > QoS Alarm > Bit Error Alarm Threshold from the Function Tree.
Step 3 Set bit error thresholds.
Step 4 Click Apply.

NOTE
----End
4.9.10 Setting the Alarm Threshold for Insufficient Fade Margin

This section describes how to set the alarm threshold for insufficient fade margin for an RF
port on an ODU.
Prerequisites


U2000
NOTE
Procedure
Step 1 Specify Alarm Threshold for Fade Margin Shortage.
----End
4.9.11 Setting Monitoring and Auto-Report Status of Performance

Events
This section describes how to set monitoring and auto-report status of specific performance
events for monitored objects.
Prerequisites

U2000
NOTE

Procedure
Step 2 Choose Performance > Performance Monitor Status from the Function Tree.
Step 3 Set the following parameters: Monitor Status, 15-Minute Auto-Report, and 24-Hour Auto-
Report.
Step 4 Click Apply.

NOTE
----End
4.9.12 Setting Performance Thresholds

This section describes how to set the thresholds of specific performance events for monitored
objects.
Prerequisites

U2000
NOTE

Procedure
Step 2 Choose Performance > Performance Threshold from the Function Tree.
Step 3 Set Threshold Value.
Step 4 Click Apply.
----End
4.9.13 Resetting Performance Registers

This section describes how to reset performance registers. After performance registers are
reset, their counts are cleared and they immediately start a new counting period.
Prerequisites

U2000
NOTE
Procedure
Step 2 Choose Performance > Reset Board Performance Register from the Function Tree.
Step 3 Set Monitored Object and register types.

Step 4 Click Reset.
Step 5 In the Hint dialog box that is displayed, click Yes.
----End

Maintenance Guide 5 Troubleshooting
5 Troubleshooting
About This Chapter
This guide describes the general troubleshooting procedure and the methods of rectifying the
common faults.
5.1 General Troubleshooting Procedure

When handling a fault, make a detailed record of the fault phenomena. The customers in
China can contact our 24-hour technical support center at 400-830-2118, and the customers in
areas outside China can contact the local Huawei offices.
5.2 Troubleshooting Service Interruptions
The service interruption fault indicates the service transmission failure due to an equipment
fault or a link fault.
5.3 Troubleshooting the Radio Link
When an NE reports MW_LOF, MW_BER_EXC, MW_BER_SD or MW_FEC_UNCOR due
to failure or performance deterioration of a radio link, there is a radio link fault.
5.4 Troubleshooting Bit Errors in TDM Services
When an NE reports an alarm or a performance event on the IF board, regenerator section
(RS), multiplex section (MS), higher order path (HP), or lower order path (LP), there are bit
errors in services.
5.5 Troubleshooting Pointer Justifications
When an NE reports a large number of justification events about the administrative unit (AU)
pointer or the tributary unit (TU) pointer, there are pointer justification faults.
5.6 Troubleshooting the Interconnection with SDH Equipment
An interconnection fault occurs when the NE fails in transmitting SDH services with other
SDH equipment.
5.7 Troubleshooting the Interconnection with PDH Equipment
An interconnection fault occurs when the NE fails in transmitting PDH services with other
PDH equipment.
5.8 Troubleshooting Native Ethernet Service Faults
An Ethernet service fault may be the Ethernet service interruption or Ethernet service
deterioration.

5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane

The Ethernet services transmitted on the EoS/EoPDH plane can be transmitted over a TDM
network. The faults of the EoS/EoPDH-plane Ethernet services include service interruption
and service degradation.
5.10 Troubleshooting MPLS Tunnels
This section describes how to troubleshoot MPLS tunnels by using the MPLS—TP OAM
function or MPLS Ping/Traceroute function.
5.11 Troubleshooting CES Services
This section describes how to troubleshoot CES services that are interrupted or degraded.
5.12 Troubleshooting ATM Services
This section describes how to troubleshoot ATM services that are interrupted or degraded.
5.13 Troubleshooting Ethernet Services Carried by PWs
This section describes how to troubleshoot Ethernet services that are carried by PWs and
transmitted in the PSN. These Ethernet services are considered faulty when they are
interrupted or deteriorate.
5.14 Troubleshooting L3VPN Services
L3VPN service faults means that services are unavailable after the L3VPN function is
configured. This section describes how to troubleshoot L3VPN services.
5.15 Troubleshooting DCN Faults
A data communication network (DCN) fault causes an NE to be unreachable due to failed or
unstable communications between the NE and the NMS.
5.16 Troubleshooting Orderwire Faults
If orderwire calls cannot get through when services are normal, there is an orderwire fault.
5.17 Typical Cases
This section describes typical microwave link troubleshooting cases.

5.1 General Troubleshooting Procedure

When handling a fault, make a detailed record of the fault phenomena. The customers in
China can contact our 24-hour technical support center at 400-830-2118, and the customers in
areas outside China can contact the local Huawei offices.

General Troubleshooting Procedure
Figure 5-1 General troubleshooting procedure
Start
Record the fault phenomena
2 Yes Other troubleshooting

Caused by external factors?
procedures
3 No
Analyze fault causes and locate
the fault
Is the fault Yes

rectified?
4 No
Report to Huawei
Make a solution together
Attempt to rectify the fault
No
Is the service restored?
Yes
Observe the operation
No Is the fault
rectified?
Yes
Fill in the troubleshooting
report
End

Table 5-1 General troubleshooting procedure

Comment Description
No.
1 When recording the fault phenomena, make a true and detailed record of
the entire process of the fault. Record the exact time when the fault occurs
and the operations performed before and after the fault occurs. Save the
alarms, performance events, and other important information. You can use
the click-to-collect function on the NMS to collect data.
2 Faults owing to external factors, including the power supply, cables,

environment, and terminal equipment (such as switch devices)
3 Determine the fault type according to preliminary analysis on alarms.

Handle different types of faults as follows:
l 5.2 Troubleshooting Service Interruptions
l 5.3 Troubleshooting the Radio Link
l 5.4 Troubleshooting Bit Errors in TDM Services
l 5.5 Troubleshooting Pointer Justifications
l 5.6 Troubleshooting the Interconnection with SDH Equipment
l 5.7 Troubleshooting the Interconnection with PDH Equipment
l 5.8 Troubleshooting Native Ethernet Service Faults
l 5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane
l 5.10 Troubleshooting MPLS Tunnels
l 5.11 Troubleshooting CES Services
l 5.12 Troubleshooting ATM Services
l 5.13 Troubleshooting Ethernet Services Carried by PWs
l 5.15 Troubleshooting DCN Faults
l 5.16 Troubleshooting Orderwire Faults
4 To provide feedbacks or obtain technical support, customers in China can

contact the 24-hour technical support center at 400-830-2118, and the
customers in areas outside China can contact the local Huawei offices.
5.2 Troubleshooting Service Interruptions

The service interruption fault indicates the service transmission failure due to an equipment
fault or a link fault.
Fault Causes
l The operation is improper.
The configuration data changes, the loopback is performed, the cable is replaced, or the
board is replaced.

l The transmission NE or link is faulty.

l The interconnection is improper.
If the transmission equipment functions normally and the connection is normal, check
whether the interconnection between the transmission equipment is proper and whether
the switch equipment is faulty.
Fault Locating Methods

1. Check the operations before the service interruption to determine whether the service
interruption results from an incorrect operation.
2. Query alarms on the centralized NMS or the NMS that is used on the site, and then
locate the fault based on the alarm analysis.
If multiple NEs report alarms, analyze the alarms in the following order: equipment
alarm, line alarm, higher order path alarm, and lower order path alarm.
3. If the fault cannot be located through the alarm analysis method, locate the fault by
performing loopback section by section or replacing the corresponding parts.
NOTICE
If the fault cannot be rectified immediately, restore the services quickly by adjusting the
service route or performing a forced switching.
Troubleshooting Procedure
Handle the fault by following the emergency maintenance process.

Figure 5-2 Description of the general procedure
Start
1 Yes
Is there an incorrect Cancel the operation
operation?
No
2 Service interruoted by Yes Contact related departments

external causes? to handle the problem
No
3
Query NE status and

alarms by using the NMS
4 Yes
NE access successful and Clear the alarm
alaarms cleared?
No
No Is the service
Proceed with the next step
Rectify the fault on site restored?
Yes
No
Is the service restored? Contact Huawei engineers
Yes
5
Check the troubleshooting result
End

Table 5-2 Description of the main procedure

Comment Description
No.
1 The common incorrect operations are as follows:

l Modifying data configuration
l Performing loopback operations
l Shutting down the laser
l Muting the ODU
l Replacing boards/cables
l Loading the software
2 Faults owing to external factors, including the power supply, cables,

environment, and terminal equipment (such as switch devices)
3 The procedure is as follows:

1. Check the NE status.
2. If the NE is unreachable to the NMS, perform field troubleshooting
according to Figure 5-3. If alarms are reported on the NE, browse the
current alarms.
4 Generally, the following alarms can be cleared on the NMS:

l APS_MANUAL_STOP, APS_FAIL
l ARP_FAIL
l BD_NOT_INSTALLED, DBMS_ERROR, NESOFT_MM,
NESF_LOST
l ETH_APS_LOST
l ETH_APS_SWITCH_FAIL, ETH_APS_TYPE_MISMATCH
l HP_TIM, HP_UNEQ
l IMA_GROUP_LE_DOWN, IMA_GROUP_RE_DOWN
l LOOP_ALM
l J0_MM
l LPS_UNI_BI_M
l LP_SLM, LP_TIM, LP_UNEQ
l RADIO_MUTE
l MW_CFG_MISMATCH
l WRG_BD_TYPE
l ETH_CFM_UNEXPERI, ETH_EFM_LOOPBACK

Comment Description
No.
5 After the fault is rectified, proceed as follows:

1. Check the alarms, and ensure that the system is running properly.
2. Assign personnel to monitor the operation of the system during the peak
service hour, ensuring that subsequent faults can be handled in time.
3. Fill in the field maintenance operation sheet, record the fault symptoms
and troubleshooting results, and then send them to Huawei. Table 5-3
shows the field maintenance operation sheet.
Table 5-3 Field maintenance operation sheet

Maintained on Maintained by
Actual Step Step in the Entire Troubleshooting Remarks

Procedure Result

Figure 5-3 Field troubleshooting sub-procedure
Start
Obvious equipment Yes Repair or replace

damage? the equipment
No
1
Is the PWR indicator No Troubleshoot the
on the PIU on? power input
2 Yes
Browse alarms
locally by using the
LCT
3 Yes
Equipment
Clear the alarm
alarm?
No
4 Yes
Radio link Clear the alarm
alarm?
No
5 High order Yes
Clear the alarm
path alarm?
No
6 Low order Yes
Clear the alarm
path alarm?
No
Faulty inter- 7 Troubleshoot the
connection with Yes
inter-connection
SDH/PDH equipment? faulty
No
8
Yes Troubleshoot the
Packet service packet service fault
fault?
No
Locate the fault by

Proceed to the next No Is the service
performing loopback
operations section by step restored?
section
Yes
End

Table 5-4 Description of the field troubleshooting sub-procedure

Comment Description
No.
1 The troubleshooting procedure is as follows:

1. Check whether the circuit breaker for the input power is off. If the
circuit breaker is automatically turned off, find the cause (such as short
circuits or insufficient fuse capacity), and rectify the fault accordingly.
2. Check the power cables, especially the connectors of the power cables.
If the power cables or connectors of the power cables are incorrect,
replace the power cables or re-prepare the connectors of the power
cables.
3. Check the voltage and polarization of the input power. If the voltage or
polarization of the input power does not meet the requirements, contact
power engineers for troubleshooting.
NOTE
The fuse capacity, which should meet actual power consumption requirements of the
equipment, can be calculated as follows:
Fuse capacity ≥ (Total power consumption x 1.5)/(Rated voltage x 87.5%)
The rated voltage of the input power is - 48 V/- 60 V, and the permitted voltage
ranges between - 38.4 V and - 72.0 V.

1. Logging In to the Web LCT (Through NMS Interface).
2. Creating NEs by Using the Search Method.
3. Logging In to an NE (Web LCT).
4. Checking Alarms.
NOTE
If you fail to log in to the created NE, ensure that the operations you performed are
correct, and then locate and rectify the fault according to the indicators of the system
control, switching, and timing board. For details about the indicators, see the IDU
Hardware Description.
3 Pay special attention to the following alarms:

l HARD_BAD, BD_STATUS, FAN_FAIL
l NESF_LOST
l POWER_ALM, TEMP_ALARM
l RADIO_TSL_HIGH, RADIO_TSL_LOW
l IF_INPWR_ABN, IF_CABLE_OPEN
l VOLT_LOS

Comment Description
No.

l PG_LINK_FAIL, PG_PRT_DEGRADED
l MW_LIM, MW_LOF
l MW_BER_EXC
l RADIO_RSL_HIGH, RADIO_RSL_LOW
l R_LOS, R_LOF, R_LOC
l MS_AIS, AU_AIS, AU_LOP
l B1_EXC, B2_EXC

l HP_LOM, HP_UNEQ
l B3_EXC

l T_ALOS, E1_LOC
l TU_AIS, TU_LOP, LP_UNEQ
l BIP_EXC
7 See Troubleshooting the Interconnection with SDH Equipment or

Troubleshooting the Interconnection with PDH Equipment.
8 See Troubleshooting Native Ethernet Service Faults, Troubleshooting

Ethernet Service on the EoS/EoPDH Plane, Troubleshooting ATM
Services, Troubleshooting CES Services, and Troubleshooting Ethernet
Services Carried by PWs.
Experience and Summary

The maintenance personnel need to perform the routine maintenance operations periodically,
to detect and rectify faults before the faults affect the services and therefore to reduce the
equipment fault rate.
5.3 Troubleshooting the Radio Link

When an NE reports MW_LOF, MW_BER_EXC, MW_BER_SD or MW_FEC_UNCOR due
to failure or performance deterioration of a radio link, there is a radio link fault.
Radio Link Faults

Radio link faults are classified into:
l Equipment faults, including outdoor component faults, cable faults, and power supply
faults
l Propagation faults, including fading, interference, and poor line of sight (LOS)

l Poor construction quality, including poor antenna/component installation, poor

grounding, and poor waterproofing
Figure 5-4 Radio link faults

Causes of radio
link faults
Propagation Poor construction Equipment

faults quality faults
Antenna Cables
Interference Fading Poor LOS installation
External Rain LOS not Antennas Poor Hardware

interference fading achieved not aligned grounding Faults
Over-reach Multipath Near-field Antennas Poor Power

interference fading blocking loosened or waterproofing faults
offset
Damaged
Reflection cable
components
Fading Phenomena and Causes

During microwave network maintenance, link fading is the main cause for radio link faults.
Link fading is more difficult to locate and handle than hardware faults.
Table 5-5 Fading phenomena and causes

Fading Type Fading Phenomena Fading Cause
Classifie Down The RSL is lower than the RSL l Multi-path fading
d by RSL fading after free space fading. The l Duct-type fading
difference can be tens of
decibels. l Rain fading
Up The RSL is higher than the RSL l Interference

fading in the free space. The difference l Long delay caused by terrain
can be 10-odd decibels. reflection
Classifie Fast The fading lasts from several l Multi-path fading

d by fading milliseconds to tens of seconds. l Duct-type fading
fading Generally, fast fading is caused
duration l Long delay caused by terrain
by multipath fading. It occurs reflection
periodically. To be specific, fast
fading occurs in the period from
18:00 to 20:00 of a day or in a
certain season of a year.

Fading Type Fading Phenomena Fading Cause
Slow The fading lasts from tens of l Generally, slow up fading is

fading seconds to several hours. caused by interference.
l Slow down fading is caused
by rain, and therefore is also
called rain fading. Rain
fading occurs on links
working at a frequency of 10
GHz or in areas where heavy
rain occurs.

Figure 5-5 Procedure for troubleshooting the radio link
Start
1 Yes
Is there an
Undo the operation.
incorrect operation?
No
2 Hardware Yes
alarms exist? Rectify equipment faults.
No
3 Yes
Are there IF or RF
alarms on the link?
4
No Analyze the historical RSL
records and the current
RSL value
Co-channel or adjacent-
5
RSL greater than the Yes channel interference
Troubleshoot the fault as
a non-radio link fault. receiver sensitivity? Long delay caused
by terrain reflection
No
The link is blocked.
6 Is the RSL value Yes
always less than the The antennas are offset.
designed value?
Passive components like
No hybrid couplers or flexible
waveguides are faulty.
7 Yes
Is it raining when the
Rain fading
fault occurs?
No
8 Multipath fading
Does the fault occur Yes
regularly?
Terrain reflection
No
9
Troubleshoot the fault by
replacing the suspected
faulty parts.
Yes
Is the fault rectified? End
No

Table 5-6 Description of the procedure for troubleshooting the radio link
Mark Description
1 Check whether any misoperation has been performed:

l Shutting down the power supply, which caused the local or remote NE to be
unreachable to the NMS
l Muting the radio transmitter, which caused the RADIO_MUTE alarm to be
reported
l Looping back IF ports, which caused the LOOP_ALM alarm to be reported
l Configuring incorrect radio link data, which caused the
MW_CFG_MISMATCH alarm to be reported
l Enabling an AM self-check, which caused the MW_AM_TEST alarm
l Enabling IF consecutive wave output
2 Hardware fault alarms include:

l HARD_BAD
l RADIO_TSL_HIGH, RADIO_TSL_LOW
3 IF and RF alarms include:

l MW_LOF, MW_LIM, MW_RDI
l MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR
l RADIO_RSL_HIGH, RADIO_RSL_LOW
l RADIO_RSL_BEYONDTH
l AM_DOWNSHIFT
4 RSL is the major reference for locating and handling propagation faults. Follow
instructions in 4.4.3 Browsing Current Performance Events of the radio link
and 4.4.1 Querying the Historical Transmit Power and Receive Power to
browse and analyze the historical RSL records and the current RSL value.

Mark Description
5 l If the receive power fluctuates within a range less than 10 dB, mute the
opposite ODU and check the RSL at the local NE.
After the opposite ODU is muted, if the RSL value is greater than -80 dBm
for the 112 MHz channel bandwidth or if the RSL value is greater than -90
dBm for the other channel bandwidth, there may be co-channel interference
that affects long-term availability and error-second performance of the
system.
1. Follow instructions in 8.1.2 Scanning Interfering Signals or use a
frequency spectrum analyzer to locate the possible interfering frequencies.
2. If a third-party RF device is the interfering source, contact the local
frequency spectrum management department to clear the interference.
3. If interference is caused due to improper route planning, modify the
frequency plan to minimize the interference impacts.
l If the receive power fluctuates dramatically and quickly (by more than ten
dBs to dozens of dBs over seconds), or fluctuates periodically (for example,
always at midnight), the fault may be caused by terrain reflection. Check
whether there are rivers or lakes on the propagation path.
If excessive reflection exists, adjust the antenna height to change the path
inclination to reduce the impact of the reflection, or replan the propagation
path.
6 If the RSL value had been smaller than the designed value for a long time before
the fault occurred, the propagation trail is faulty. Proceed as follows:
l Check whether the antenna connection is loose or the antenna is unaligned. If
yes, re-align the antenna.
NOTICE
In high-corrosion areas, check whether outdoor components and fasteners are loose due
to corrosion. If yes, take rust- and corrosion-proof measures or replace the corroded
components or fasteners.
l Check whether there are any blocks in the radio transmission trail or in the
near field of the antenna. If yes, adjust the mounting height of the antenna to
avoid blocks, replan the radio link route.
l Check whether the antenna, hybrid coupler, and flexible waveguide are
damaged or suffer from water leakage, which causes high attenuation. If any
of the preceding components is damaged or suffers from water leakage,
replace the component.

Mark Description
7 If a radio link fault occurred in poor weather conditions (such as rainy, snowy, or
foggy) and was rectified after the conditions disappeared, the fault cause was
weather fading. For a fault caused by weather fading, check whether the link
fading margin is insufficient.
1. Calculate the actual link availability. Calculate the total link fault time within
one year or half a year. Calculate the actual link availability using the
following formula: <Link availability> = <Total fault time>/<Calculation
period>.
l If the actual link availability is lower than the designed value by an order
of magnitude, the link fading margin is insufficient. Re-plan the radio link
parameters.
l If the difference between the actual link availability and the designed
value is small, no special handling operations are required.
2. Before re-planning a radio link, check whether the rain zone parameters, the
refractivity gradient, and the planning algorithm are incorrect. The practicable
measure could be as follows:
l Increase the transmit power or replace the original antenna with a new one
having a larger diameter to increase the system gain and the fading margin.
l Use a frequency band on which rain fading has smaller impacts.
8 If the receive power fluctuates greatly and fast (by more than 10 dB or several 10
dB within several seconds or several 10 seconds), fast fading occurs.
Fast fading may occur due to:
l Multi-path fading: Faults occur periodically, for example, at the day-and-night
alternating time period.
l Duct-type fading: random fast fading
To handle fast fading, proceed as follows:
l Increase the path inclination: That is, adjust the antenna mount heights at both
ends to increase the height differences between the antennas at both ends.
l Reduce surface reflection. For apparent strong reflection surfaces, for
example, large areas of water, flat lands, and bold mountain tops, adjust
antennas to move reflection points out of the strong reflection areas or mask
the reflection by using landforms.
l Reduce the path clearance. With LOS conditions guaranteed, lower antenna
mount heights as much as possible.
9 If all preceding actions cannot rectify the fault, replace the ODU at both ends.
Then, check whether services are functional. If the fault persists, replan the radio
link by changing the operating frequency, using antennas with a larger diameter,
changing the antenna heights, or changing the routes.

l During the commissioning, ensure that the antenna is aligned properly, to prevent
possible incipient faults.

l Periodically collect and analyze the data about the changes in the transmit power and
receive power so that you can detect and then rectify the incipient faults accordingly in
time.
5.4 Troubleshooting Bit Errors in TDM Services

When an NE reports an alarm or a performance event on the IF board, regenerator section
(RS), multiplex section (MS), higher order path (HP), or lower order path (LP), there are bit
errors in services.
Fault Phenomena
Table 5-7 Bit errors

Bit Error Description Related Alarm and Performance Event
Type
IF bit errors Refer to the bit errors that l MW_BER_EXC, MW_BER_SD

the IF board detects through l IF_BBE, IF_ES, IF_SES, IF_CSES,
the self-defined overhead IF_UAS
byte in the microwave frame
RS bit errors Refer to the bit errors that l B1_EXC, B1_SD

the line processing unit or l RS_CROSSTR
the IF board that works in
SDH mode through the B1 l RSBBE, RSES, RSSES, RSCSES,
overhead byte in the RS RSUAS
overhead NOTE
The IF board that works in PDH mode may also
detect the previous RS bit error alarms and
performance events. In this case, the IF board
detects bit error alarms and performance events
in the PDH microwave frame through the self-
defined B1 byte.
MS bit Refer to the bit errors that l B2_EXC, B2_SD

errors the line board detects l MS_CROSSTR
through the B2 byte in the
MS overhead l MSBBE, MSES, MSSES, MSCSES,
MSUAS
HP bit errors Refer to the bit errors that l B3_EXC, B3_SD

the line board detects l HP_CROSSTR
through the B2 byte in the
MS overhead l HPBBE, HPES, HPSES, HPCSES,
HPUAS
LP bit errors Refer to the bit errors that l BIP_EXC, BIP_SD

the tributary board or IF l LP_CROSSTR
board detects through the
V5 byte in the VC-12 l LPBBE, LPES, LPSES, LPCSES,
overhead LPUAS

Fault Causes
Table 5-8 Causes of bit errors

Fault Common Fault Cause
There are IF bit l The radio link is faulty.

errors. Check whether the MW_BER_EXC, MW_BER_SD,
MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes,
the radio link is faulty.
l The services are incorrectly configured.
Check whether the MW_CFG_MISMATCH alarm is
reported. If yes, the number of E1 services is inconsistent on
both ends of the radio link.
l The IF board at the local end or opposite end is faulty.
There are RS bit l The line is faulty.

errors. – The common causes for bit errors on the optical line are as
follows: the optical fiber line, the optical power is abnormal,
the fiber performance deteriorates, or the fiber connector is
not clean.
– In the case of bit errors on the radio link, check whether the
MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or
RPS_INDI alarm is reported. If yes, the radio link is faulty.
l The line processing unit or IF board is faulty.
l The clock unit is faulty.
l The quality of the clock over the network declines.
When the quality of the clock over the network declines, a
pointer justification event occurs.
There are not any RS l The line processing unit or IF board is faulty.
bit errors but there l The quality of the clock over the network declines.
are MS bit errors or
HP bit errors. When the quality of the clock over the network declines, a
pointer justification event occurs.
l The working temperature of the line processing unit or IF board
is excessively high.
There are only LP bit l The tributary board is faulty.

errors. l The cross-connect unit is faulty.
l The working temperature of the board is excessively high.
l The working temperature of the cross-connect unit is
excessively high.
l There is a power surge or an external interference source, or the
equipment is not properly grounded. (This cause does not need
to be considered during the troubleshooting of an IF board.)


1. Analyze the equipment alarms and performance events that are related to service
configuration errors and bit errors.
2. When there are many types of alarms and performance events on a service path, first
analyze RS bit errors, then MS bit errors, HP bit errors, and finally LP bit errors.
3. When multiple paths have bit errors, first check whether the overlapping part of the
service paths is faulty.
4. If you fail to locate the fault by analyzing the alarms and performance events, perform
loopback operations section by section.
5. Replace the parts whose performance may deteriorate with new ones.

Figure 5-6 Procedure for troubleshooting bit errors
Start
2
1
Is there an Yes
Clear the alarm
equipment alarm?
No
3
Is there a pointer Yes Troubleshoot the pointer
justification event? justification
No SDH optical
interface board Troubleshoot RS bit errors
on the SDH optical interface
board
Is there an If the
RS bit error alarm or a
Yes
alarming
performance board is
event?
4
No IF board Troubleshoot RS bit errors
on the IF board
Is there an
5
MS/ HP alarm or Yes Troubleshoot MS/HP bit
performance errors
event?
No
6
Is there an LP Yes Troubleshoot LP bit
alarm? errors
No
Locate the fault by performing No Is the fault
loopback operations section Proceed with the next step rectified?
by section
Yes
End

Table 5-9 Description of the procedure for troubleshooting bit errors

Comment Description
No.

l TEMP_ALARM
l HARD_BAD
2 See 5.5 Troubleshooting Pointer Justifications.

1. Check whether the line board reports the B1_EXC, B1_SD, or
RS_CROSSTR alarm.
2. Interchange the Tx fiber core and the Rx fiber core at both ends of the
service path. If bit errors change after the exchange, it indicates that the
fiber is faulty. Otherwise, the equipment at both ends of the service path
is faulty.
3. In the case of a fiber fault, check whether the fiber between the
equipment and the ODF and the section of the fiber that is led out of the
telecommunications room are pressed. In addition, check whether the
fiber connectors are clean.
4. In the case of faults at both ends of the service path, use a fiber jumper
to loop back the optical ports. If the fault persists after the loopback, the
line board may be faulty.
5. In the case of faults at both ends of the service path, you can also
replace the board where the line unit is located or interchange
between the board and another board of the same type that is working
normally. If the alarm changes after the exchange, it indicates that the
board is faulty.

1. Check whether the IF board reports the MW_BER_EXC,
MW_BER_SD, MW_FEC_UNCOR, MW_LOF, RPS_INDI,
B1_EXC, B1_SD, or RS_CROSSTR alarm.
2. If any of the alarms are reported, see 5.3 Troubleshooting the Radio
Link and rectify the fault.

1. Perform a loopback on the line board that reports the alarm.
If the fault persists after the loopback, replace the line board.
If the fault is rectified after the loopback, replace the line board at the
transmit end.
2. If you fail to rectify the fault by replacing the line board, check whether
there is a power surge or an external interference source or whether the
equipment is not properly grounded.

Comment Description
No.

1. Replace the board where the services are configured based on how
the service paths that have bit errors overlap each other.
2. If you fail to rectify the fault by replacing the board, check whether
there is a power surge or an external interference source or whether the
equipment is not properly grounded.

NOTE
The TDM services mentioned refer to Native TDM services.

The handling procedure applies when the STM-1e port is faulty
l During the routine maintenance, check bit error performance events periodically and
handle them in time.
l To locate a fault, prefer the method of analyzing alarms and performance events to the
method of performing loopback operations and the method of replacing the parts.
5.5 Troubleshooting Pointer Justifications

When an NE reports a large number of justification events about the administrative unit (AU)
pointer or the tributary unit (TU) pointer, there are pointer justification faults.
Fault Phenomena
When the position of the first byte of the VC-4 in the AU-4 payload changes, the AU pointer
makes a justification accordingly. The performance events related to the AU pointer
justification are as follows:
l AUPJCHIGH
l AUPJCLOW
l AUPJCNEW
NOTE
The AU pointer justification is made at an upstream NE but is detected and reported at a downstream
NE.
When the service is configured to be at the VC-12 level, apply the reframing process to
terminate the AU pointer justification. The terminating method is to transform the AU pointer
justification into the TU pointer justification. The performance events related to the TU
pointer justification are as follows:
l TUPJCHIGH
l TUPJCLOW
l TUPJCNEW

NOTE
The TU pointer justification is made at the NE where the AU pointer is transformed into the TU pointer,
but is detected and reported by the tributary board of the NE where services are terminated.
Fault Causes
l The clock sources or the clock source levels are configured incorrectly. As a result, there
are two clock sources on the same network or a timing loop occurs.
l The fiber connections are incorrect. As a result, a timing loop occurs.
l The quality of the clock source declines, the clock unit is faulty, or there are other clock-
related faults.
l The tributary board is faulty (only for the TU pointer justification).

When there are both AU pointer justifications and TU pointer justifications on a service path,
first handle the AU pointer justifications and then the TU pointer justifications.
Fault Fault Locating Method
AU pointer justification 1. Analyze and clear clock alarms.

2. Rectify the incorrect data configuration and incorrect
fiber connections.
3. Change the clock configuration to locate the station
whose clock is asynchronous with the entire network.
4. Replace the parts whose performance may deteriorate
with new ones.
TU pointer justification 1. Analyze and clear clock alarms.

2. Rectify the incorrect data configuration and incorrect
fiber connections.
3. Change the clock and service configuration to locate the
station whose clock is asynchronous with the entire
network.
4. Replace the parts whose performance may deteriorate
with new ones.

Figure 5-7 Procedure for troubleshooting pointer justifications
Start
1 Yes
Is there a clock-related Clear the alarm
alarm?
No
2
Check the clock
configuration
Incorrect Yes Modify the data

configuration? configuration
No
3
Check the fiber
connection
Incorrect fiber Yes

connection? Reconnect the fibers
No
4 5
An AU pointer Yes Locate the NE whose clock
justification event? Locate the faulty board
is out of synchronization
No
6 7
A TU pointer Yes Locate the NE whose clock
justification event? Locate the faulty board
is out of synchronization
No
Proceed with the No
Is the fault rectified?
next step
Yes
End

Table 5-10 Description of the procedure for troubleshooting pointer justifications

Comment Description
No.

l TEMP_ALARM
l HARD_BAD
l LTI
l SYNC_C_LOS
l S1_SYN_CHANGE
l EXT_SYNC_LOS
2 Check the following points:

l Check whether there are two clock reference sources on the entire
network.
l Check whether a timing loop is generated.
3 Query ECC routes to check whether the fibers are connected correctly.
Check the fiber connections in the east and west directions of the NE that
reports the pointer justification event.

1. Locate a VC-4 channel that reports an AU pointer justification event.
2. Along the service source direction of the VC-4 channel, locate the
source NE of the entire VC-4 service (not the source NE of a timeslot in
the VC-4).
3. Set the clock of the source NE to the free-run mode. Set the other NEs
to trace the clock of the source NE along the direction of the VC-4
service.
4. Along the clock tracing direction, locate the line board that is the first to
report the AU pointer justification of the VC-4 path.
The clock of the remote NE to which the line board is connected is
asynchronous with the reference clock. Hence, the line board on the
remote NE that receives the clock signal, the line board that sends the
clock signal to the remote NE, and the clock unit of the remote NE, may
be faulty.
5. Set the clock of the sink NE to the free-run mode. Set the other NEs to
trace the clock of the sink NE along the direction of the VC-4 service.
6. Along the clock tracing direction, locate the line board that is the first to
report the AU pointer justification of the VC-4 path.
The clock of the remote NE to which the line board is connected is
asynchronous with the reference clock. Hence, the line board on the NE
that receives the clock signal, the line board that sends the clock signal
to the NE, and the clock unit of the NE, may be faulty.
7. Compare the results and find out the common points.
5 Replace the possibly faulty boards.

Comment Description
No.

1. Modify the service configuration to ensure that the NE where the clock
reference source functions as the central NE and that the other NEs have
the E1 services of the central NE.
2. Along the clock tracing direction, locate the NE that is the first to report
the TU pointer justification event.
The clock of the NE is asynchronous with the reference clock. Hence,
the line board on the NE that receives the clock signal, the line board
that sends the clock signal to the NE, and the clock unit of the NE, may
be faulty.
3. Modify the configuration data to ensure that all the NEs trace the clock
along the other direction.
4. Along the clock tracing direction, locate the NE that is the first to report
the TU pointer justification event.
The clock of the NE is asynchronous with the reference clock. Hence,
the line board on the NE that receives the clock signal, the line board
that sends the clock signal to the NE, and the clock unit of the NE, may
be faulty.
5. Compare the results and find out the common points.
NOTE
This method is also applicable to locating an AU pointer justification event.
7 Replace the possibly faulty boards. In the case of a TU pointer justification

event, check whether the line board, the clock board, and the tributary
board are faulty.

On a properly synchronized network, there are few pointer justifications (less than six per day
on each port). Hence, monitoring the pointer of an SDH transmission system is an effective
way to check the synchronization status of the system.
5.6 Troubleshooting the Interconnection with SDH

Equipment
An interconnection fault occurs when the NE fails in transmitting SDH services with other
SDH equipment.
Fault Causes
l The VC-12 numbering method of the OptiX equipment is different from the numbering
method of the equipment of certain vendors.
The OptiX equipment applies the timeslot numbering method. The numbering formula
is: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x
21. This method is also called as the method of numbering by order.

Certain equipment applies the line numbering method. The numbering formula is: VC-12
number = (TUG-3 number - 1) x 21 + (TUG-2 number - 1) x 3 + TU-12 number. This
method is also called as the interleaved method.
l The overhead bytes at both ends are inconsistent.
l The indexes of the SDH interfaces do not meet the requirements.
NOTE
In the case of interconnection with ATM or Ethernet equipment, the common cause for an
interconnection failure is that the service is not set to the VC-4 pass-through service and thus the
overheads are processed in the terminating mode instead of the pass-through mode.

Analyze the fault phenomena and alarms that are generated on the equipment. Check the
possible fault causes one after another.

Figure 5-8 Procedure for troubleshooting the interconnection with SDH equipment
Start
Is the
Set the interconnection
interconnected equipment Yes
service to be the VC-4 pass-
the ATM/IP equipment?
through service
No
Query the VC-12 numbering
method of the interconnected
equipment
Is the Modify the data configuration.

Yes
numbering mode the Use the line numbering
line numbering? method to set the VC-12
No
1 Is there an overhead Yes

setting related alarm? Handle the alarm
No
2
Is the interface the Yes

Check the grounding
STM-1 electrical
interface?
3 No
Test the indexes of interfaces
Do the interfaces meet No Handle the faults of the

relevant standards? interconnected equipment
Yes Go to the next No

step Is the fault cleared?
Handle the faults of the local Yes

equipment
End

Table 5-11 Description of the procedure for troubleshooting the interconnection with SDH
equipment
Comment Description
No.

l J0_MM
l HP_TIM
l LP_TIM
l HP_SLM
l LP_SLM

l Check whether all the equipment and the DDF in the equipment room
are jointly grounded.
l Check whether the shield layer of the coaxial cable connector on the
DDF is connected to the protection ground.
l Check whether the shield layers of coaxial cables are grounded in the
same way.
NOTE
Disconnect all the signal cables between the interconnecting equipment. Use a
multimeter to measure the level between the shield layers of the coaxial cables at the
receive and transmit ends of the SDH equipment. In addition, measure the level
between the shield layers of the coaxial cables at the receive and transmit ends of the
opposite equipment. If the potential difference is large (about 0.5 V), the fault may be
caused by the grounding.
3 Common indexes of the optical interfaces are as follows:

l Mean launched optical power
l Receiver sensitivity
l Overload optical power
l Permitted frequency deviation of the input interface
Common indexes of the electrical interfaces:
l Allowed attenuation of the input interface

To rectify an interconnection fault, you must be familiar with the characteristics of the
interfaces on the interconnected equipment.
5.7 Troubleshooting the Interconnection with PDH

Equipment
An interconnection fault occurs when the NE fails in transmitting PDH services with other
PDH equipment.

Fault Causes
l There is an impedance mismatch between interfaces.
l The equipment is not grounded properly.
l The cable performance deteriorates.
l The indexes of the PDH interfaces do not meet the requirements.

Analyze the fault phenomena and alarms that are generated on the equipment. Check the
possible fault causes one after another.

Figure 5-9 Procedure for troubleshooting the interconnection with PDH equipment
Start
1
Check the impedance of
the interfaces.
Is there an Yes Replace the cable or the

impedance mismatch? tributary board
No
2
Is the cable a Yes
Check the grounding.
coaxial cable?
No
3
Check the cables.
No
Is in good conditions? Adjust the cables.
Yes
4
Test the indexes of
Interfaces.
Troubleshoot the faults on

Do the interfaces No
the interconnected
meet standards? Equipment.
Yes
No
Troubleshoot the faults Proceed with the next step. Is the fault rectified?
on the local equipment.
Yes
End

Table 5-12 Description of the procedure for troubleshooting the interconnection with PDH
equipment
Comment Description
No.
1 Check the impedance of the E1 path. Ensure that the impedance of the E1
path is consistent with the cable type.

l Check whether all the equipment and the DDF in the
telecommunications room are jointly grounded.
l Check whether the shield layers of the coaxial cable connectors on the
DDF are connected to the protection ground.
l Check whether the shield layers of coaxial cables are grounded in the
same manner.
NOTE
Disconnect all the signal cables between the interconnecting equipment sets. Use a
multimeter to measure the level between the shield layers of the coaxial cables at the
receive and transmit ends of the PDH equipment and the level between the shield
layers of the coaxial cables at the receive and transmit ends of the equipment at the
opposite end. If the potential difference is large (about 0.5 V), the fault may be caused
due to the improper grounding.

l Check whether the wires of the cable are correctly connected.
l Check whether the cable is broken or pressed.
l Check whether the cable signal is interfered (for example, when the
trunk cable is bound with the power cable, the cable signal is interfered
by the power signal).
NOTE
Checking the cables involves checking the cables from the DDF to the client side
and checking the cables from the DDF to the transmission equipment side.
4 Check the following indexes:

l Input jitter tolerance
l Output jitter
l Output frequency deviation

NOTE
The PDH services mentioned refer to Native E1 services.
In the case of interconnection with PDH equipment, improper grounding is the most common
cause for an interconnection failure.

5.8 Troubleshooting Native Ethernet Service Faults

An Ethernet service fault may be the Ethernet service interruption or Ethernet service
deterioration.
Fault Phenomena
The Ethernet service interruption indicates that the Ethernet service is interrupted. The
Ethernet service deterioration indicates that the Ethernet service is abnormal. For example, the
network access speed is low, the equipment delay is long, the packet loss occurs, or incorrect
packets exist in the received or transmitted data.
Table 5-13 Common faults of Ethernet services
Symptom Alarm
Ethernet Hardware Such as HARD_BAD, TEMP_ALARM,

services are alarms WRG_BD_TYPE, BD_STATUS, COMMUN_FAIL,
interrupted. and LASER_MOD_ERR.
Link alarms Such as ETH_LOS, ETH_LINK_DOWN,

ETH_EFM_LOOPBACK, LOOP_ALM,
PORTMODE_MISMATCH, and LAG_DOWN.
Service alarms Such as ETH_CFM_AIS, ETH_CFM_LCO, and

ETH_NO_FLOW.
Radio link Such as MW_LOF, MW_LIM.

alarms
Ethernet Hardware Such as HARD_BAD, and TEMP_ALARM.

services suffer alarms
degradation.
Link alarms Such as PORTMODE_MISMATCH, and
LAG_MEMBER_DOWN.
Service alarms Such as FLOW_OVER, MAC_EXT_EXC,

MAC_FCS_EXC, and DROPRATIO_OVER.
Radio link Such as AM_DOWNSHIFT, MW_BER_EXC, and

alarms MW_BER_SD.
Fault Causes
l The possible human factors are as follows:
– An Ethernet board loopback or a transmission line loopback occurs.
– The parameter settings of the Ethernet ports, such as the port enabled state, working
mode, and flow control, are different from the parameter settings of the Ethernet
ports on the interconnected equipment.
– The service configuration is incorrect.

l The equipment at the local end is faulty.

l The line board is faulty or has bit errors.
l A LAG or PLA group has faulty member links, resulting in decreased Ethernet
bandwidth.
l When the AM function is enabled, the Ethernet service bandwidth decreases due to the
downward AM switch.
l The interconnected equipment is faulty.
l The network cable is faulty.
l External electromagnetic interference is severe.

Locate the Ethernet service fault using the intelligent fault diagnosis function.
Troubleshooting Ethernet Services
Figure 5-10 Procedure for troubleshooting faults in Ethernet services

Table 5-14 Description of the procedure for troubleshooting Ethernet services configured in
an end-to-end manner
Comment Description
No.

l Whether a loopback is set for the Ethernet port
l Whether a loopback is set for the transmission line
l Whether the Ethernet port parameters, such as port enabling/disabling
status, working mode, and flow control, are configured consistently at
the local end and peer end
l Whether Ethernet protocol and Ethernet service configurations
(especially Ethernet port attributes) are correct
2 Intelligent fault diagnosis uses OAM to implement fault diagnosis over

services, PWs, and tunnels, and the physical layer, and supports the output
of diagnostic results for further troubleshooting.
3 Query Ethernet service rates on various ports to analyze the service

rates and locate faults.
l If the Ethernet port connecting the peer equipment has a too high or too
low receive rate, the peer equipment is faulty.
l If the rate of the port approaches or reaches the license capacity of the
IF port, the license capacity is too low and you need to apply for a
license allowing for a higher capacity.
l If the transmit rate of the port approaches or reaches the maximum
Ethernet bandwidth of the IF port, the bandwidth of the IF port is too
low and needs to be increased by the network planning personnel.
l If the transmit rate of the port is much lower than the receive rate of the
Ethernet port, or if the receive rate of the port is much higher than the
transmit rate of the Ethernet port, the local end is faulty. Locate the fault
as follows:
– Check the Ethernet service configuration and QoS configuration.
– By Querying port flow classification or packet loss performance
of egress queues on the NMS, check whether QoS settings are
correct according to the packet loss data.
– Check the Ethernet interface board, IF board, and system control,
switching and timing board by means of board replacement.
If the transmitted traffic is equal to the received traffic, create flows specific
to the VLANs in the port policy, and check if sufficient bandwidth is
available for the flows by querying flow traffic.

To troubleshoot an Ethernet service fault, you must be familiar with the characteristics,
working mode, and configured protocols of interfaces on the Ethernet equipment.

5.9 Troubleshooting Ethernet Service on the EoS/EoPDH

Plane
The Ethernet services transmitted on the EoS/EoPDH plane can be transmitted over a TDM
network. The faults of the EoS/EoPDH-plane Ethernet services include service interruption
and service degradation.
Fault Phenomena
The Ethernet service interruption indicates that the Ethernet service is completely interrupted.
The Ethernet service deterioration indicates that the Ethernet service is abnormal. For
example, the network access speed is low, the equipment delay is long, the packet loss occurs,
or incorrect packets exist in the received or transmitted data.
Symptom Alarm Board
Ethernet HARD_BAD, TEMP_ALARM, EMS6/EFP8

services are WRG_BD_TYPE, or BD_STATUS
interrupted.
ALM_GFP_dLFD or ALM_GFP_dCSF
ETH_LOS or LOOP_ALM
LAG_PORT_FAIL,
LAG_VC_PORT_FAIL, LCAS_TLCT, or
LCAS_TLCR
Ethernet HARD_BAD or TEMP_ALARM

services are
abnormal. FLOW_OVER
LCAS_FOPT, LCAS_FOPR, LCAS_PLCT,

or LCAS_PLCR
Fault Causes
l The possible human factors are as follows:
– An Ethernet board loopback or a transmission line loopback occurs.
– The parameter settings of the Ethernet ports, such as the port enabled state, working
mode, and flow control, are different from the parameter settings of the Ethernet
ports on the interconnected equipment.
– The configuration of the encapsulation/mapping protocol or the LCAS protocol is
inconsistent on both ends of the link.
– The timeslot binding of VCTRUNKs is inconsistent on both ends of the link
– The service configuration is incorrect.
l The equipment at the local end is faulty.

l The line board is faulty or has bit errors.

l The interconnected equipment is faulty.
l The network cable is faulty.
l The external electromagnetic interference is severe.

1. Rectify the human-caused faults such as a loopback and a data configuration error.
2. Locate the fault cause according to the equipment alarms.
3. Locate the fault cause according to the RMON performance events and alarms.
Figure 5-11 Procedure for troubleshooting Ethernet service faults
Start
11 Yes
Incorrect operation? Cancel this operation
No
2 An equipment alarm Yes

Clear the alarm
or alarm on the radio
link?
No
Yes Query the port and service

3 An Ethernet Clear the alarm traffic and analyze the fault
alarm? causes
No
4 A loop formed by the Yes

Release the loop
E-LAN service trails?
No
Any abnormal Yes Troubleshoot the fault according

5
RMON performance to the flow of handling RMON
events? performance events
No
Fault on the Yes Troubleshoot faults on the

opposite
opposite equipment
equipment?
No
Troubleshoot equipment
faults by performing Proceed No Is the fault
loopbacks section by with the rectified?
next step
section or replacing boards
Yes
En
d

Table 5-16 Description of the procedure for troubleshooting Ethernet service faults
Comment Description
No.

l Whether a loopback is set for the transmission line
l Whether the parameter settings of the Ethernet port, such as the port
enabled state, working mode, and flow control, are the same as the
parameter settings of the Ethernet port on the interconnected equipment
l The configuration of the encapsulation/mapping protocol or the LCAS
protocol is inconsistent on both ends of the link.
l The timeslot binding of VCTRUNKs is inconsistent on both ends of the
link.
l Check whether the Ethernet protocol and the Ethernet service
configuration (especially the attributes of the Ethernet port) are correct.
2 Pay special attention to the following equipment alarms:

l POWER_ALM
l FAN_FAIL
l HARD_BAD
l BD_STATUS
l NESF_LOST
l TEMP_ALARM
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l IF_INPWR_ABN
Pay special attention to the following line alarms:
l MW_LIM
l MW_LOF
l R_LOS
l R_LOF
l MS_AIS
l AU_AIS
l AU_LOP
l B1_EXC
l B2_EXC

Comment Description
No.

l ETH_LOS
l FLOW_OVER
l ALM_GFP_dCSF
l ALM_GFP_dLFD
l FCS_ERR
l LCAS_PLCT
l LCAS_TLCT
l LCAS_PLCR
l LCAS_TLCR
l LCAS_FOPT
l LCAS_FOPR
4 If the LOOP_ALM alarm is reported after the configuring the Advanced

Attributes of Ethernet Interfaces operation is performed, it indicates that the
network to which Ethernet ports are connected has loops.
5 For RMON performance events, see B Performance Event Reference.

Figure 5-12 Procedure for troubleshooting an RMON performance event
Start
1
View the statistics group
performance on an Ethernet port
2
Yes Rectify the fault of line bit
Is there any FCS error? errors
No
3
Is there any collision Yes Check the working mode
or fragment? of the port
No
4
Is there any Yes Handle the flow control
PAUSE frame? problem or increase the
bandwidth
No
5
Yes Handle the problem on
Are broadcast packets excessive broadcast
excessive? packets
No
Use a meter to perform the test
Yes
Is the test passed? Rectify the fault of the
interconnected equipment
No
6 Yes
Is it a MTU setting
Modify the MTU value
problem?
No
Proceed with No Is the fault
Rectify the equipment fault by the next step rectified?
loopback section by section or
replacing the board Yes
End
Table 5-17 Description of the procedure for troubleshooting an RMON performance event
Comment Description
No.
1 View the statistics group performance on an Ethernet port to obtain the

real-time performance statistics data of the Ethernet port.

Comment Description
No.

l Check the Ethernet cable. If the Ethernet cable is not qualified, replace it
with a new one.
l Change the Ethernet port that accesses the services on the Ethernet
board. If the new port does not have the RMON performance of an FCS
error, it indicates that the hardware of the original port is faulty.
Otherwise, the hardware of the Ethernet port on the equipment at the
opposite end is faulty.

l Whether the port operating rates on the equipment at both ends are the
same
l Whether the working modes (full duplex or half duplex) of the Ethernet
port on the equipment at both ends are the same
l Whether the Ethernet port is set to auto-negotiation mode at one end and
the Ethernet port is set to full duplex mode at the opposite end (When
the Ethernet port is set to auto-negotiation mode at one end, the Ethernet
port must not be set to full duplex mode at the opposite end.)

l Whether the flow control method is the same.
l Whether the Ethernet service traffic exceeds the bandwidth of the
VCTRUNK.
5 Check for the cause for excessive broadcast packets (for example, you have
set the loopback for the Ethernet interface board or set the VB filtering
table incorrectly) and solve the problem. If the problem is caused on the
equipment at the opposite end, set the threshold of broadcast packet
suppression for an Ethernet port to reduce broadcast packets.
6 Test the MTU of the network by using a test meter. The maximum frame
length that is set for a port should be longer than the MTU of the network.

To troubleshoot an Ethernet service fault, you must be familiar with the characteristics,
working mode, and configured protocols of interfaces on the Ethernet equipment.
5.10 Troubleshooting MPLS Tunnels

This section describes how to troubleshoot MPLS tunnels by using the MPLS—TP OAM
function or MPLS Ping/Traceroute function.
Fault Phenomena
Common faults of MPLS tunnels are as follows:

l MPLS tunnels fail to be created, and services are unavailable.

l MPLS tunnels are faulty, and services are interrupted.
l MPLS APS switching fails, services are interrupted, and packet loss or bit errors occur.
Table 5-18 Common faults of MPLS tunnels

Symptom Alarm Board
MPLS HARD_BAD, TEMP_ALARM, CSHN

tunnels are WRG_BD_TYPE, BUS_ERR,
faulty. BD_STATUS,
MPLS_TUNNEL_OAMFAIL,
MPLS_TUNNEL_LOCV,
MPLS_TUNNEL_Excess,
MPLS_TUNNEL_MISMATCH,
MPLS_TUNNEL_MISMERGE,
MPLS_TUNNEL_UNKNOWN,
MPLS_TUNNEL_BDI,
MPLS_TUNNEL_FDI,
MPLS_TUNNEL_SD,
MPLS_TUNNEL_SF,
MPLS_TUNNEL_AIS,
MPLS_TUNNEL_RDI,
MPLS_TUNNEL_UNEXPMEG,
MPLS_TUNNEL_UNEXPMEP,
MPLS_TUNNEL_UNEXPPER
MW_CFG_MISMATCH ISV3, ISU2, ISX2, IFU2 or

MW_LIM IFX2
MW_LOF
Fault Causes
l Incorrect operations are performed.
– The transmission link is looped back.
– Service configuration data is inconsistent between the local end and the opposite
end.
– Service configuration is incorrect.
l The local NE is faulty.
l The transmission link is faulty or has bit errors.
l Service bandwidth decreases due to an AM downshift.
l The opposite NE is faulty.

1. Check whether the data is modified, whether the line is looped back, and whether any
boards are replaced.

2. Handle the link alarms on the MPLS server trail.

3. Locate the faulty section by using the LSP Traceroute or MPLS-TP OAM function.
4. Locate the fault by replacing boards.
Figure 5-13 Procedure for troubleshooting MPLS tunnels
Start
1 Yes
Any incorrect Cancel the operation.
operation?
No
2 Yes
Any equipment- or
link-related alarm? Clear the alarm.
No
3 Yes
Clear the alarm using
Any alarm related to MPLS
LB/LT/LSP Ping/LSP Tracerout.
tunnel ?
No
Any fault in
Yes
interconnection
Handle the fault.
equipment?
No
Troubleshoot equipment faults by No

Contact Huawei Faults are rectified?
performing loopbacks on sections
technical engineers.
or replacing boards.
Yes
End
Table 5-19 Description of the procedure for troubleshooting MPLS tunnels
Comment Description
No.

l Whether a loopback is set for E1 ports
l Whether a loopback is set for the transmission link
l Whether the parameter settings such as the working mode of Ethernet
ports match those of the opposite NE
l Whether the parameter settings such as frame format and frame mode at
E1 ports match those of the opposite NE
l Whether MPLS service configuration is correct, especially whether
tunnel attributes are set correctly

Comment Description
No.

l POWER_ALM
l FAN_FAIL
l HARD_BAD
l BD_STATUS
l BUS_ERR
l NESF_LOST
l TEMP_ALARM
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l IF_INPWR_ABN
l AM_DOWNSHIFT
l MW_CFG_MISMATCH
l MW_LIM
l MW_LOF
l MW_BER_EXC
l MW_BER_SD
l MW_RDI
l MW_FEC_UNCOR

Comment Description
No.
3 Check whether the tunnel is faulty using LSP Ping, LSP Tracerout,
orMPLS-TP Tunnel OAM.
Pay special attention to the following alarms:
l ARP_FAIL
l MPLS_TUNNEL_BDI
l MPLS_TUNNEL_Excess
l MPLS_TUNNEL_FDI
l MPLS_TUNNEL_LOCV
l MPLS_TUNNEL_MISMATCH
l MPLS_TUNNEL_MISMERGE
l MPLS_TUNNEL_OAMFAIL
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_UNKNOWN
l MPLS_TUNNEL_AIS
l MPLS_TUNNEL_RDI
l MPLS_TUNNEL_UNEXPMEG
l MPLS_TUNNEL_UNEXPMEP
l MPLS_TUNNEL_UNEXPPER

Learn about the working principle and protocol configuration of MPLS tunnels before
troubleshooting MPLS tunnels.
5.11 Troubleshooting CES Services

This section describes how to troubleshoot CES services that are interrupted or degraded.
Fault Phenomena
CES services are interrupted if they are completely unavailable. CES services are degraded if
they have packet loss or incorrect packets.
Table 5-20 Common faults of CES services
Symptom Alarm Board
CES HARD_BAD, TEMP_ALARM, CSHN, ML1, MD1, CQ1

services are WRG_BD_TYPE, BUS_ERR,
interrupted. BD_STATUS, CES_LOSPKT_EXC

Symptom Alarm Board
AM_DOWNSHIFT ISV3, ISU2, ISX2, IFU2,

MW_CFG_MISMATCH IFX2
CES HARD_BAD, TEMP_ALARM, CSHN, ML1, MD1, CQ1

services are CES_JTROVR_EXC,
degraded. CES_JTRUDR_EXC,
CES_MALPKT_EXC,
CES_MISORDERPKT_EXC,
CES_STRAYPKT_EXC

Fault Causes
end.
l The clock source is asynchronous.
l Jitters and delays on the network are too great.

1. Check whether the data is modified, whether the line is looped back, and whether any
2. Check whether the PW works properly by using the PW ping function. If the PW is
faulty, check whether the MPLS tunnel works properly by using the LSP ping function.
If the MPLS tunnel works properly, check whether the PW has the same configuration at
both ends. If the configuration is the same, replace the board on the NNI side.
3. If the PW works properly, check whether the PE data configured at both ends is the
same. If the PE data is different, change the PE data to the same.
4. Check whether UNI-side data and CE-side data are consistent.
5. Analyze the RMON performance events of CES services.
6. Check whether there is impedance mismatch on channels and whether any electrical
cables are connected incorrectly.
7. Replace smart E1 interface boards.

Figure 5-14 Procedure for troubleshooting CES services
Start
1 Yes
Any incorrect Cancel the operation
operation?
No
2 Yes
Any equipment- or
link-related alarm? Clear the alarm
No
Yes
3
Any alarm related to Clear the alarm
tunnels/PWs?
No
4
Any alarm related to Yes
CES services? Clear the alarm
5 Yes
Any alarm on E1
ports? Clear the alarm
No
6
Any RMON Yes
performance event? Handle the performance event
No
7 Any fault of Yes

interconnection with
Handle the fault
PDH equipment
No

technical engineers
or replacing boards
Yes
End

Table 5-21 Description of the procedure for troubleshooting CES services

Commen Description
t No.

l Whether a loopback is set for the E1 port
l Check whether the parameter settings of CES services, PWs, and tunnels
are consistent at the source end and sink end.
l Check whether the parameter settings of physical ports (including frame
format, code, electrical port impedance, and overhead byte), are consistent.
l Check whether the network bandwidth is sufficient for the service traffic.

l POWER_ALM
l FAN_FAIL
l HARD_BAD
l BD_STATUS
l BUS_ERR
l NESF_LOST
l TEMP_ALARM
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l IF_INPWR_ABN
l AM_DOWNSHIFT
l MW_CFG_MISMATCH
l MW_LIM
l MW_LOF
l MW_BER_EXC
l MW_BER_SD
l MW_RDI
l MW_FEC_UNCOR
3 Check whether the PW is faulty using the PW ping function.

If the PW fails to be pinged, check the following:
l Check whether the hardware and cable connections on the UNI side are
normal.
l Check whether PWE3 service configurations on the UNI side are correct.
l Check whether port working mode and tag attribute configurations on the
UNI side are consistent with those at the peer end.

Commen Description
t No.
4 Run PW ping or LSP Tracerout to check whether the MPLS tunnel is faulty.
Handle the tunnel fault by referring to instructions in 5.10 Troubleshooting
MPLS Tunnels.
Check whether PW configurations are correct. If the configurations are
incorrect, re-configure the PW according to the network plan.

l CES_JTROVR_EXC
l CES_JTRUDR_EXC
l CES_LOSPKT_EXC
l CES_MALPKT_EXC
l CES_MISORDERPKT_EXC
l CES_STRAYPKT_EXC

l T_ALOS
l UP_E1_AIS
l LFA
l LMFA
l ALM_E1RAI

l CES_MISORDERPKT
l CES_LOSPKT
l CES_MALPKT
l CES_JTRUDR
l CES_JTROVR
l CES_STRAYPKT
8 Troubleshoot the interconnection with the PDH equipment.

Learn about the working principle and protocol configuration of CES services before
troubleshooting CES services.
5.12 Troubleshooting ATM Services

This section describes how to troubleshoot ATM services that are interrupted or degraded.

Fault Phenomena
ATM services are interrupted if they are completely unavailable. ATM services are degraded
if they have packet loss or incorrect packets.
Table 5-22 Common faults of ATM services

Symptom Alarm Board
ATM HARD_BAD, TEMP_ALARM, CSHN, ML1, MD1

services are WRG_BD_TYPE, BUS_ERR,
interrupted. BD_STATUS, ALM_IMA_LIF,
ALM_IMA_LODS,
ALM_IMA_RE_RX_UNUSABLE,
ALM_IMA_RE_TX_UNUSABLE,
IMA_GROUP_LE_DOWN,
IMA_GROUP_RE_DOWN, LCD

ATM HARD_BAD, TEMP_ALARM, CSHN, ML1, MD1

services are ALM_IMA_LIF, ALM_IMA_LODS,
degraded. ALM_IMA_RE_RX_UNUSABLE,
ALM_IMA_RE_TX_UNUSABLE, OCD

Fault Causes
end.

1. Check whether the data is modified, whether the link is looped back, and whether any
2. Check whether the PW works properly by using the PW ping function. If the PW is
faulty, check whether the MPLS tunnel works properly by using the LSP ping function.
If the MPLS tunnel works properly, check whether the PW has the same configuration at
both ends. If the configuration is the same, replace the board on the NNI side.

5. Analyze the RMON performance events of ATM services.
7. Replace smart E1 processing boards.


Figure 5-15 Procedure for troubleshooting ATM services
Start
1
Any incorrect Yes
Cancel the operation
operation?
No
2
Any equipment- or Yes
link-related alarm? Clear the alarm
No
3
Yes
Any alarm related to Clear the alarm
PWs?
No
4
tunnels? Clear the alarm
No
5
Clear the alarm
ATM services?
No
6
Any alarm on E1 Yes
ports? Clear the alarm
No
7
Any RMON Yes
performance event? Handle the performance event
No
8 Any fault of Yes

interconnection with
Handle the fault
PDH equipment
No

technical engineers
or replacing boards
Yes
End

Table 5-23 Description of the procedure for troubleshooting ATM services

Comment Description
No.

l Whether a loopback is set for the E1 port
l Whether the parameter settings of ATM VPI/VCI, PWE3 CW, PW, and
Tunnel are consistent between the source end and the sink end.
l Whether the parameter settings of interconnected ports are consistent
– Whether E1 frame format, coding, overhead bytes, and E1 timeslot
mode (30/31) are correctly configured
– Whether IMA parameters (including protocol version, clock mode,
frame length, and maximum differential delay) are correctly
configured
l Check whether the network bandwidth is sufficient for the service
traffic.

l POWER_ALM
l FAN_FAIL
l HARD_BAD
l BD_STATUS
l BUS_ERR
l NESF_LOST
l TEMP_ALARM
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l IF_INPWR_ABN
l AM_DOWNSHIFT
l MW_CFG_MISMATCH
l MW_LIM
l MW_LOF
l MW_BER_EXC
l MW_BER_SD
l MW_RDI
l MW_FEC_UNCOR

Comment Description
No.
3 Check whether the PW is faulty using the PW ping function.

If the PW fails to be pinged, perform the following checks:
l Check whether the hardware and cable connections on the UNI side are
normal.
l Check whether PWE3 service configurations on the UNI side are
correct.
l Check whether port working mode and tag attribute configurations on
the UNI side are consistent with those at the peer end.
4 Run LSP Ping or LSP Tracerout to check whether the MPLS tunnel is
faulty.
Handle the tunnel fault by referring to instructions in 5.10 Troubleshooting
MPLS Tunnels.
Check whether PW configurations are correct. If the configurations are
incorrect, re-configure the PW according to the network plan.

l ALM_IMA_LIF
l ALM_IMA_LODS
l ALM_IMA_RE_RX_UNUSABLE
l ALM_IMA_RE_TX_UNUSABLE
l IMA_GROUP_LE_DOWN
l IMA_GROUP_RE_DOWN
l OCD
l LCD

l T_ALOS
l UP_E1_AIS
l LFA
l LMFA

l ATMPW_UNKNOWNCELLS
l ATM_UNCORRECTED_HCSERR
8 Troubleshoot the interconnection with the PDH equipment.

Learn about the working principle and protocol configuration of ATM services before
troubleshooting ATM services.

5.13 Troubleshooting Ethernet Services Carried by PWs

This section describes how to troubleshoot Ethernet services that are carried by PWs and
transmitted in the PSN. These Ethernet services are considered faulty when they are
interrupted or deteriorate.
Fault Symptoms
Ethernet services are interrupted if they are unavailable. Ethernet services deteriorate if they
have great delays, packet loss, or incorrect packets.
Symptom Alarm Board
Ethernet HARD_BAD, TEMP_ALARM, EG4, EG4P, EG2D, EM6TA, EM6FA,

services are WRG_BD_TYPE, BUS_ERR, EM6F or EM6T
interrupted. BD_STATUS
COMMUN_FAIL, LAG_DOWN
ETH_LOS,
ETH_EFM_LOOPBACK, or
LOOP_ALM
LASER_MOD_ERR EG4, EG4P, EM6F or EG2D
Ethernet HARD_BAD or EG4, EG4P, EG2D, EM6TA, EM6FA,

services TEMP_ALARM EM6F or EM6T
deteriorate.
PORTMODE_MISMATCH, EG4, EG4P, EG2D, EM6TA, EM6FA,
FLOW_OVER or EM6F or EM6T
LAG_MEMBER_DOWN
MAC_FCS_EXC
MAC_EXT_EXC
DROPRATIO_OVER
AM_DOWNSHIFT ISV3, ISU2, ISX2, IFU2 or IFX2

MAC_FCS_EXC
MAC_EXT_EXC
DROPRATIO_OVER
Fault Causes
end.



1. Check whether the data is modified, whether the link is looped back, and whether any
2. Check whether the PW works properly by using the PW ping or MPLS-TP PW OAM
function. If the PW is faulty, check whether the MPLS tunnel works properly by using
the LSP ping or MPLS-TP Tunnel OAM function. If the MPLS tunnel works properly,
check whether the PW has the same configuration at both ends. If the configuration is the
same, replace the board on the NNI side.
5. Analyze the RMON performance events of Ethernet services.
7. Replace the Ethernet interface board.
Troubleshooting Ethernet Services
Figure 5-16 Procedure for troubleshooting Ethernet services

Table 5-25 Description of the procedure for troubleshooting Ethernet services configured in
an end-to-end manner
Comment Description
No.

l Whether the Ethernet port parameters, such as port enabling/disabling
status, working mode, and flow control, are configured consistently at
the local end and peer end
l Whether Ethernet protocol and Ethernet service configurations
(especially Ethernet port attributes) are correct
2 Intelligent fault diagnosis uses OAM to implement fault diagnosis over

services, PWs, and tunnels, and the physical layer, and supports the output
of diagnostic results for further troubleshooting.
3 Query Ethernet service rates on various ports to analyze the service

rates and locate faults.
l If the Ethernet port connecting the peer equipment has a too high or too
low receive rate, the peer equipment is faulty.
l If the rate of the port approaches or reaches the license capacity of the
IF port, the license capacity is too low and you need to apply for a
license allowing for a higher capacity.
l If the transmit rate of the port approaches or reaches the maximum
Ethernet bandwidth of the IF port, the bandwidth of the IF port is too
low and needs to be increased by the network planning personnel.
l If the transmit rate of the port is much lower than the receive rate of the
Ethernet port, or if the receive rate of the port is much higher than the
transmit rate of the Ethernet port, the local end is faulty. Locate the fault
as follows:
– Check the Ethernet service configuration and QoS configuration.
– By Querying port flow classification or packet loss performance
of egress queues on the NMS, check whether QoS settings are
correct according to the packet loss data.
– Check the Ethernet interface board, IF board, and system control,
switching and timing board by means of board replacement.
If the transmitted traffic is equal to the received traffic, Create flows
specific to the VLANs in the port policy, and check if sufficient bandwidth
is available for the flows by Querying flow traffic.

Learn about the working principle and protocol configuration of Ethernet services carried by
PWs before troubleshooting these services.

5.14 Troubleshooting L3VPN Services

L3VPN service faults means that services are unavailable after the L3VPN function is
configured. This section describes how to troubleshoot L3VPN services.
Fault Causes
l Data configurations are incorrect.
– VPN instance configurations are incorrect.
– BGP configurations are incorrect.
– IGP configurations are incorrect.
– Tunnel configurations are incorrect.
– Tunnel policy configurations are incorrect.
l Equipment is faulty.
– The local microwave equipment is faulty.
– The peer equipment is faulty.
l Links are faulty, or bit errors occur.
Fault Locating Method

1. Collect L3VPN-related alarms and analyze the causes. L3VPN-related alarms include
BGPBACKTRANSITION, GSP_RSVP_NB_AUTH_ERR,
GSP_RSVP_NB_DOWN, GSP_TNNL_DOWN, ISISADJACENCYCHANGE,
L3V_TRAP_THRE_EXCEED, L3V_TRAP_VRF_DOWN, and RT_TBL_LACK.
2. Check whether any alarms indicating Ethernet link, microwave link, or equipment faults
are reported. The following table lists these alarms.
Alarm Type Alarm
Alarms indicating Ethernet link faults ETH_LOS, ETH_NO_FLOW,

ETH_AUTO_LINK_DOWN,
ETH_PWR_SUPPLY_FAIL
Alarms indicating microwave link faults MW_LIM, MW_LOF,

MW_BER_EXC, MW_BER_SD,
MW_RDI, MW_FEC_UNCOR
Alarms indicating equipment faults POWER_ALM, FAN_FAIL,

HARD_BAD, BD_STATUS,
BUS_ERR, NESF_LOST,
TEMP_ALARM,
RADIO_RSL_HIGH,
RADIO_RSL_LOW,
RADIO_TSL_HIGH,
RADIO_TSL_LOW,
IF_INPWR_ABN, IF_CABLE_OPEN

Troubleshooting Processes
L3VPN service troubleshooting processes include the traffic-related fault troubleshooting
process and the route-related fault troubleshooting process.
Start
Yes Does the local VPN No

instance routing
table contain VPN
routes?
Traffic- Route-
related fault related fault
l Traffic-related fault troubleshooting process

Figure 5-17 Traffic-related fault troubleshooting process
Traffic-
related fault
Tracert the VPN IP

address at the local
1 end to locate the
fault.
2
Use LSP Ping
Yes to check whether the tunnel No
where a service fault has
occurred is working
properly.
3
Correct the tunnel
5 configurations.
No Is the VPN instance Yes
bound with a tunnel
policy?
Bind the VPN

4 with a tunnel
policy.
No No
Is the fault Is the fault
rectified? rectified?
6
Yes No Yes Yes
Is the tunnel
policy correct?
7 Correct the
tunnel policy.
Is the fault No
rectified?
Yes
Contact Huawei
technical
support.
End
l Route-related fault troubleshooting process

Figure 5-18 Route-related fault troubleshooting process
Route-
related fault
Yes Does the BGP routing No

table contain VPN routes?
1
3
Are the VPN No
instance Yes No
configurations Does the IGP routing table
correct? contain a route to the
peer?
2 Correct the VPN instance
configurations, such as RT.
4 6
No Are the BGP Yes Yes Are the IGP No

configurations configurations
correct? correct?
Correct the BGP Correct the IGP

5 9 configurations.
configurations. No Does the VPN instance
routing table on the peer 7
contain VPN routes?
No Are interfaces enabled Yes
or configured with IP
addresses?
Rectify the fault.
Enable the interfaces
8 and configure IP
addresses for them. Yes Are the No
Ethernet/
microwave links
faulty?
Rectify the link Yes

faults. Is the
equipment
faulty?
No
Rectify the
equipment fault.
Is the fault Is the fault Is the fault Is the fault

rectified? Yes rectified? Yes rectified? Yes rectified? Yes
No No No No
Contact Huawei
technical
support.
End
Summary
Learn about the principles and protocol configuration of the L3VPN feature before
troubleshooting L3VPN services.
5.15 Troubleshooting DCN Faults

A data communication network (DCN) fault causes an NE to be unreachable due to failed or
unstable communications between the NE and the NMS.
Context
If links or lines that bear DCN channels, including data communication channels (DCCs) and
inband DCN channels, are faulty, the DCN communication is interrupted. In this case, handle
the fault in the same manner as a service fault. In other cases, the DCN communication
between an NE and the NMS is interrupted or unstable, but the services between them are
normal for the moment. This fault also needs to be rectified in time, otherwise, you will fail to
check the NE information, obtain NE alarms, or change NE configurations when the services
become faulty.

Fault Symptoms and Causes
Table 5-26 Fault symptoms and causes

Symptom Possible Cause
NEs connected through their l Cause 1: Services are interrupted.

service ports like air l Cause 2: DCN parameters are incorrectly set.
interfaces and Ethernet ports
are unreachable to their l Cause 3: System control boards are faulty.
NMS.
NEs connected through their l Cause 1: The network cable of the NMS is disconnected
NMS ports are unreachable or damaged.
to their NMS. l Cause 2: DCN parameters are incorrectly set.
l Cause 3: System control boards are faulty.
A few NEs are unreachable l Cause 1: DCN parameters are incorrectly set.
or their connection to the l Cause 2: An NE ID or NE IP address conflict occurs
NMS is unstable. between NEs on the DCN subnet.
l Cause 3: The DCN subnet is too large.
l Cause 4: The system control unit of the NE is faulty.

Figure 5-19 Procedure for troubleshooting DCN faults
Start
1
Locate a
faulty NE
2
Icon of the Yes Yes Check for hardware
The NMS cannot Hardware
faulty NE in alarms and check
reach the NE fault? cable connections
gray
NO
NO 3
Settings Yes Check settings
incorrectly or undo
modified? modifications
NO
4
Yes
Large DCN Divide the DCN
subnet? subnet
5
NM Yes
否 Too low DCN Increase the DCN
Information channel bandwidth channel bandwidth
loss?
NO
6
No response to Yes Wait for the
SCC boards are
commands from the completion of SCC
being reset
NMS resetting
NO Fault
rectified
Yes
Contact Huawei
technical service End
engineers

Table 5-27 Procedure description for troubleshooting DCN faults

Mark Operation Typical Symptom Measures
1 Locate the Locate the faulty NE l If the faulty NE has a service fault, rectify the
faulty NE. based on a DCN service fault first.
networking diagram. l If an unreachable NE connects to its NMS through
l If all NEs within an an external DCN, verify that the external DCN
area are unreachable equipment or the cable used for DCN connection is
to their NMS, the working correctly.
unreachable NE
closest to a normal
NE is probably the
faulty NE.
l If only one NE is
unreachable to its
NMS, the NE is the
faulty NE.
2 Handle l The faulty NE reports l Handle hardware alarms based on the maintenance
hardware faults. hardware alarms like and fault management procedure.
HARD_BAD. l Remove and then install, or replace the network
l Check whether the cable and optical fibers.
NMS/COM port on
the faulty NE is
connected to a correct
cable or whether the
network cable of the
faulty NE is damaged.

3 Modify The following operations l Check for unplanned NE IDs and NE IP addresses
incorrect are performed before a in the ECC routing table of the faulty NE's
configurations. faulty NE becomes upstream NE. If there is an unplanned NE ID or IP
unreachable to its NMS: address in the ECC routing table, the faulty NE is
l Modifying NE incorrectly configured. To rectify the fault, log in
attributes or NE to the faulty NE using the unplanned NE ID and
communication NE IP address on the NMS and correct the
settings settings.
l Adding a new NE to l Change the DCC settings or inband DCN settings
the network, or of the faulty NE to interrupt the DCN channel
replacing the faulty between the faulty NE and its upstream NE. Then,
NE or its system check for the ID and IP address of the faulty NE in
control board the ECC routing table of the upstream NE. If the
ID and IP address of the faulty NE exist in the
ECC routing table of the upstream NE, another NE
on the ECC subnet has the same ID and IP address
as the faulty NE. In this case, correct the settings to
ensure that each NE on the ECC subnet has a
unique ID and IP address.
l If the inband DCN is enabled for the faulty NE and
its upstream NE, verify that the VLAN ID is
correctly set on the upstream NE.
l Verify that static routes are correctly set on the
faulty NE's upstream NE.
l Verify that OSPF parameters are correctly set on
the faulty NE's upstream NE. OSPF parameter
settings must be consistent for all NEs on the same
ECC subnet.
4 Analyze the Check the number of NEs If there is a large number of NEs in the routing table,
DCN subnet in the IP routing table or the DCN subnet is too large in size and some NEs on
size. ECC routing table of the the DCN subnet may occasionally become
faulty NE's upstream NE. unreachable to their NMS. It is recommended that an
DCN subnet consist of no more than 120 NEs, if a 192
kbit/s bandwidth is provided. If L2 DCN is used, an
L2 DCN subnet consists of not more than 30 NEs.

5 Troubleshoot Some NEs may l Verify that a minimum of 192 kbit/s bandwidth is
NMS occasionally become allocated to the inband DCN. If the allocated
information unreachable to their bandwidth is lower than 192 kbit/s, packets from
loss. NMS. the NMS may be lost.
l Check whether the QoS priority allocated to the
inband DCN by a third-party network is high
enough if inband DCN packets are transmitted
over the third-party network. Lower QoS priority
of inband DCN packets may cause NEs
unreachable to the NMS due to congestive packet
loss. The per-hop behavior (PHB) priority of
inband DCN packets must not lower than
expedited forwarding (EF).
6 Troubleshoot l The NE fails to be l Search for the IP address of the faulty NE on the
no-response logged in to onsite. NMS.
problems. l The NE does not l If the IP address is not found, or if the IP address is
respond to commands. found but the NMS still cannot reach the faulty
NE, restart the OptiX RTN 980 after a power-off,
in a authorized maintenance window which service
can be interrupted.
5.16 Troubleshooting Orderwire Faults

If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Fault Causes
l The phone set is set incorrectly.
l The phone line is connected incorrectly.
l The orderwire is configured incorrectly.
l The orderwire unit is faulty.
l The system control unit is faulty.
l The line unit or radio link is faulty.

l Check whether the phone set is set correctly, whether the phone line is connected
correctly, and whether the orderwire is configured correctly.
l Replace the possibly faulty board to locate the fault.

Figure 5-20 Procedure for troubleshooting orderwire faults
Start
Check the phone setting
Is the phone No
Modify the phone setting
correctly set?
Yes
Is the phone line No

Reconnect the phone line
correctly connected?
Yes
2
Check the orderwire
configuration
Is the configuration No
Modify the configuration
correct?
Yes
3
Replace the possibly faulty No
Proceed with the next step Is the fault rectified?
board
Yes
End

Table 5-28 Description of the procedure for troubleshooting orderwire faults
Comment Description
No.

l Check whether the ring current switch "RING" on the phone set is set to
"ON".
l Check whether the dialing mode switch is set to "T", namely, the dual
tone multi-frequency mode.
l An orderwire phone set should be in on-hook state when it is not in
communication, and the upper-right red indicator in the front view of
the orderwire phone set should be off.
If the red indicator is on, it indicates that the phone set is in off-hook
state. Press the "TALK" button in the front of phone set to hook it up. In
certain occasions, the maintenance personnel press the "TALK" button
is pressed by mistake. As a result, the phone set stay in off-hook state all
the time and the orderwire call from the other NEs cannot get through.

l Whether all orderwire phone numbers on a subnet are of the same length
l Whether all orderwire phone numbers on a subnet are unique
l Whether the overhead bytes of all the NEs on a subnet are the same
l Whether the orderwire port is set correctly
3 Locate the fault by replacing the board in which the orderwire unit, line
unit, and system control unit reside.

To troubleshoot orderwire faults, you must check the orderwire phone periodically.
5.17 Typical Cases

This section describes typical microwave link troubleshooting cases.
5.17.1 Transient Link Unavailability Due to Multi-path Fading
Fault Symptoms
A 20 km long cross-ocean 1+1 hot standby (HSB) radio link was interrupted intermittently,
and alarms such as B1_SD, MW_LOF, and R_LOF, were reported and lasted several seconds
to dozens of seconds.
Cause Analysis and Handling Procedure

1. Checked the ODU receive power that was recorded during the alarm period.

The difference between the maximum receive power and the minimum receive power
was more than 40 dB, and the minimum receive power was close to or less than the
receiver sensitivity. Therefore, it was inferred that the fault was caused by spatial fading.
2. Checked the network planning design.
The ODU operated at the 8 GHz band, which was less prone to rain fading, and therefore
multipath fading caused intermittent link interruptions. In addition, 1+1 HSB protection
does not well protect radio links against multipath fading.
3. Replaced 1+1 HSB protection with 1+1 space diversity (SD) protection.
Conclusions and Suggestions

l Routinely check whether the receive power reaches the designed value. If not, it is
recommended that you check the configuration, adjust antennas, or replace ODUs so the
receive power reaches the designed value.
l Minimize the impact of multipath fading by using one of the following methods,
depending on the actual conditions:
– Use low capacity, low-order modulation schemes, and low bandwidths.
– Increase the height difference between antennas at both ends providing that line-of-
sight (LOS) is guaranteed.
– Add two antennas and configure an SD protection group.

5.17.2 Transoceanic Link Transient Unavailability Due to

Insufficient Height Difference between Diversity Antennas
Fault Symptoms
The received signal levels (RSLs) at both ends of a 1+1 SD cross-ocean radio link fluctuated
dramatically, leading to bit errors or even link interruptions.

1. Checked the alarms reported by NEs at both ends of the radio link.
The NEs did not report any hardware alarms but frequently reported radio link alarms
and service interruption alarms.
2. Checked the RSLs of the main and standby ODUs at each end.
The RSLs of the main and standby ODUs at each end fluctuated dramatically, with a
fluctuation range over 30 dB. Therefore, the fault was possibly caused by multipath
fading.
3. Checked the network plans and the mounting height difference between the main and
standby antennas at each end.
The mounting height difference between the main and standby antennas at each end was
only 4 meters, so space diversity performance was poor.
NOTE
To protect long-distance cross-ocean radio links against multipath fading, take the following measures
during network planning:
l Ensure that the fading margin is greater than or equal to 30 dB.
l Increase the mounting height difference between the main and standby antennas at both ends of a
1+1 SD radio link.
4. Adjusted the mounting heights of the main antennas to 24 meters and those of the
standby antennas to 10 meters.
The following figure shows the simulation result and illustrates satisfactory diversity
compensation.
NOTE
The value of K generally ranges from 0.67 to 1.33. In this case, the RSLs of the main and standby
antennas are not correlated with each other. When designing mounting heights for main and standby
antennas, keep appropriate antenna spacing for minimizing the impact of reflection on radio links.
When reflection causes high attenuation on the main path, the attenuation on the standby path is low.


When planning cross-ocean radio links, especially long-distance cross-ocean radio links, take
measures to minimize the impact of multipath fading. 1+1 SD protection is recommended for
these radio links. When mounting the main and standby antennas at one end, keep an
appropriate mounting height difference between them so attenuation has no impact on RSLs.
In addition, the main and standby antennas can be tilted slightly upwards providing that RSLs
be not affected.
5.17.3 Link Unavailability Due to Inter-building Reflection
Fault Symptoms
On a 900-meter 1+0 microwave hop, working with 18 GHz HP ODUs, at 28 MHz channel
bandwidth and in 256QAM modulation, with XPIC disabled. One end of the link
continuously reports MW_LOF alarms and the other end reports MW_RDI alarms.
On this microwave hop, ODUs are mounted onto 0.3-meter diameter dual-polarized antennas
in separate-mount manner. Both ends of the radio hop are located on roofs. Antennas are
installed at the middle of poles about 5 meters high standing on the roofs.

1. The total hop spans only 900 meters. The receive power is ideal but the MSE is poor.
The faulty microwave link end is surrounded by many buildings, most of which have
glass walls. Therefore, it is suspected that some signals are reflected for many times
between the buildings before reaching the receive end or that some microwave signals
are reflected twice when traveling through the glass walls before reaching the receive
end. See Figure 5-21.
Figure 5-21 Microwave link between buildings
Site A
Site B
Reflected signal
Main signal
2. To suppress signal reflection, do as follows:

– Change the pole position.

– Adjust the antenna elevation.
– Increase the antenna mount height.
– Use antennas with a larger diameter.
NOTE
Move poles near the building roof edges to decrease the inter-building reflection possibility or number
of reflection times. Generally, antennas can be adjusted upwards, downwards, leftwards, or rightwards.
During antenna adjustment, notice the MSE changes and ensure that the RSL is within its allowed
range.
The larger the antenna diameter, the denser the beams. The smaller the beam angle at the receive end,
the powerful the capabilities to suppress reflection.
3. By means of the preceding methods, you can adjust the MSE values at both ends to be
-30 dB to clear alarms.

The addressed problem is characterized by satisfactory receive power, poor MSE, and failure
in clearing alarms. To find out the cause, check whether the equipment hardware is faulty,
whether the equipment operates abnormally, and whether any exceptions occur on the path
from an antenna to an indoor unit (IDU). Then narrow down the cause on the space link, and
determine whether reflection and refraction are possible according to the topography.
5.17.4 Unidirectional Link Availability Due to Interference
Fault Symptoms
A 1+0 microwave link between NE A and NE B was configured with QPSK/28M modulation
and 8G/HP ODUs. The link is available only in one direction after the link is expanded from
mode 5 (QPSK/28M/16E1) to mode 7 (128QAM/28M/STM-1).

1. The ODU supports 128QAM modulation scheme according to query results of NE data
in mode 7 and query of ODU product manual.
2. The receive power is unlikely to fade because the RSL is stable and the link is only 1.27
Km long.
3. The MSE values on the NE A are -35.35 dB and -34.57 dB in the mode 5 and the mode 7
respectively. The MSE values on the NE B are -26.77 dB and -20.56 dB in the mode 5
and the mode 7 respectively. The MSE value on the NE B is greatly different from the
required modulation threshold from -24 dB to -35 dB in the mode 7. The modulation
threshold of the MSE value in the mode 7 is from -24 dB to -35 dB. When the link is
normal, the MSE value of NE B is also low. It is suspected that interference exists.
Because the anti-interference capability in QPSK modulation is more powerful than that
in 128QAM modulation, signal modulation is successful in QPSK modulation but fails
in 128QAM modulation.
4. Scan the frequency on the NE B to find out the interference source. Change the operating
frequency to eliminate interference.


For unidirectional link availability in case of modulation upshift, the possible causes are as
follows:
l The ODU cannot support the new IF mode of high modulation and of large capacity after
the link capacity is expanded.
l The link is interrupted because the receive power cannot meet the sensitivity requirement
in the new IF mode.
l The link is interrupted because the MSE value cannot reach the demodulation threshold
due to interference occurrence on the link.
Check the above items to prevent the link from being interrupted before the link capacity
expansion.
5.17.5 Bit Errors on Microwave Links
Fault Symptoms
Bit errors were detected in a microwave link hop (between NE A and NE B) during
acceptance checks. The distance between two ends of the link hop was 2.5 km. The link was
configured with 0.6 m antennas, 15G ODUs, and QPSK/28M modulation.

1. Checked the alarms and logs of the two NEs.
The NEs did not report any hardware alarm. NE A reported an MW_FEC_UNCOR
alarm, but NE B did not.
2. Checked the RSLs at the two NEs.
The RSL at NE A was -62 dBm and that at NE B was -70 dBm. These two values were
greater than the receiver sensitivity (-85 dBm) in mode 5.
3. Checked for interference signals by muting the ODU at NE B.
The RSL at NE A was -80 dBm. Therefore, interference signals existed.
4. Used one of the following methods for eliminating interference signals:
– Using frequencies that are not affected by interference signals (tests showed that the
sub-bands supported by the ODU were all interfered)
– Using antennas with a diameter greater than 0.6 meters (the workload is heavy and
interference signals are also amplified)
– Changing a polarization direction (cross-polarization discrimination of 30 dB can
be achieved)
5. Changed the polarization direction of the radio link.
The fault was rectified.

If the RSL of an ODU is normal or apparently greater than the receiver sensitivity, frequent
and intermittent radio link interruptions or bit errors are generally caused by interference
signals.

5.17.6 Poor Reliability Due to Network Planning Errors

Fault Symptoms
A radio link frequently but intermittently reported MW_RDI, R_LOC, and RPS_INDI alarms,
and HSB switchovers were triggered.
Table 5-29 Link information

Protection 1+1 HSB
IF mode IF mode 7 (128QAM/28M/STM-1)
ODU type SPA ODUs operating at the 8 GHz

frequency band
Receiver sensitivity -70.5 dBm
Transmit power 20 dBm
Receive power -39.5 dBm
Planned availability 99.994%
Predicted annual interruption time 1877 seconds

1. Queried historical receive power values of the radio link.
The receive power decreased to a value close to the receiver sensitivity when an alarm
was reported. Most alarms were reported during the night or in the early morning. When
the weather was favorable at noon, the receive power was normal. Therefore,
intermittent radio link interruptions were caused by multipath fading.
2. Checked annual interruption time predicted for the radio link.
The actual annual interruption time was longer than the predicted time of 1877 seconds.
Therefore, the fading margin was insufficient.
3. Checked the network planning methods.
The ITU-R-P.530-7/8 method was used. The area covered by the radio link was in the
Middle East, and therefore the ITU-R-P.530-9 method should be used.
4. Used the ITU-R-P.530-9 method to predict annual interruption time without changing
other conditions.
The obtained value was about 175833 seconds, which was longer than the value obtained
using the ITU-R-P.530-7/8 method.

Figure 5-22 Using the ITU-R-P.530-7/8 method
Figure 5-23 Using the ITU-R-P.530-9 method
5. Deleted 1+1 HSB protection settings and configured 1+1 SD protection. The link
availability met service requirements.

Network planning is crucial to radio link performance. For radio links that are frequently
interrupted due to fading, it is recommended that you first check their network planning
information.

Maintenance Guide 6 Part Replacement
6 Part Replacement
About This Chapter
Part replacement is a method frequently used to locate faults. The replacement operation
varies according to the specific part type.
Table 6-1 Part replacement description
Part Name Operation Tool
CQ1 6.4 Replacing the Channelized l ESD wrist strap

STM-1 Processing Board l Screwdriver
SL1D, SL1DA 6.3 Replacing the SDH Optical l U2000
Interface Board l Fiber extractor
EX1, EG4, 6.7 Replacing the Ethernet
EG4P, EM6T, Interface Board
EM6F, EMS6,
EM6TA,
EM6FA, and
EFP8
CF card 6.9 Replacing the CF Card
CSHN, 6.10 Replacing the System

CSHNA, and Control, Switching and Timing
CSHNU Board
AUX 6.11 Replacing the Auxiliary

Board
SP3D and 6.5 Replacing the PDH Interface l ESD wrist strap
SP3S Board l Screwdriver
l U2000

Part Name Operation Tool
ISM6, ISV3, 6.8 Replacing an IF Board

ISX2, ISU2,
IF1, IFU2, and
IFX2
PIU 6.13 Replacing the Power Board
ML1 and MD1 6.6 Replacing the Smart E1

Interface Board
FAN 6.12 Replacing the Fan Board l ESD wrist strap

l U2000
ODU 6.15 Replacing an ODU l Wrench (torque wrench)

l U2000
l Silicon
l Waterproof adhesive tape
IF cable 6.16 Replacing an IF Cable l Multimeter

l Wrench
l Electrician's knife
l File
l Connector installation fittings
and accessories
l IF cable
SFP 6.14 Replacing the SFP l ESD wrist strap

l Tweezer Fiber extractor
l U2000

6.1 Removing a Board

Removing a board is a basic operation for replacing a board.
Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD
wrist strap.
Figure 6-1 Wear the ESD wrist strap
Step 2 Optional: If cables are connected to the board, make labels for the cables and then remove
the cables.
NOTE
Use fiber removers to remove fibers or network cables.

Figure 6-2 Tweezer fiber remover
Step 3 Remove the board.

1. Loosen the screws on the panel of the board.
Figure 6-3 Removing a board (1)
2. Hold the left and right ejector levers with hands. Push them outwards to disengage the
board from the backplane.

NOTE
As shown in Figure 6-5, there is a latch on each ejector lever of the System control
Switch&Timing board. To remove the System control Switch&Timing board, you need to push the
latches when pulling the ejector levers outward.
Figure 6-5 Removing the System control Switch&Timing board
3. Pull out the board gently along the slot guide rail.

NOTICE
Remove the board slowly to prevent the components on the boards from colliding.
Step 4 Put the removed board into the antistatic box or bag.
----End
6.2 Inserting a Board

Inserting a board is a basic operation for replacing a board.
Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD
wrist strap.
Figure 6-7 Wear the ESD wrist strap
Step 2 Insert the board.

1. Hold the ejector levers on the panel with both hands. Push them outwards so that the
angle between the ejector lever and the panel is about 45 degrees.
2. Push the board gently along the slot guide rail until the board cannot slide further.

Figure 6-8 Inserting a board (1)
NOTICE
Insert the board slowly to prevent the components on the boards from colliding.
3. Press the two ejector levers inward with force.
4. Tighten screws on the panel.

Step 3 Optional: If cables are connected to the board, recover the original cable connections
according to the labels that are made previously.
----End
6.3 Replacing the SDH Optical Interface Board

When the SDH optical interface board is replaced, the unprotected services on the board are
interrupted.
Prerequisites
l You must know the impact of board replacement.
l You must know the specific position of the board to be replaced.
l You must know the service protection and protection channels of the board to be
replaced.
l The spare SDH optical interface board must be available, and the version and type of the
spare board must be the same as the version and type of the board to be replaced. You
can query the board manufacturing information to obtain the version of the board to
be replaced.

l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
Procedure
Step 1 Query the current alarms of the board.
Step 2 Optional: If the services on the board are configured with SNCP, ensure that the services are
already switched to the protection channel.

1. Query the SNCP protection group.

2. Perform the forced switching, if the port on the board functions as the current working
channel, the current protection channel is not on the board, and the state of the current
protection channel is normal or SD.
Step 3 Optional: If the services on the board are configured with linear MSP, ensure that the services
are already switched to the protection channel.
1. Query the linear MSP group.
Step 5 Check whether the version and SFP type of the spare board are the same as the version and
SFP type of the board to be replaced.
Step 7 After the board starts to work, check the STAT indicator on the board. The STAT indicator
should be on and green.
There should be no new alarms on the board.
Step 9 Optional: If the forced switching has been performed on the board, release the forced
switching.
Step 10 Optional: If the linear MSP switching has been performed for the services, release the forced
switching.
----End
6.4 Replacing the Channelized STM-1 Processing Board

When the channelized STM-1 processing board is replaced, the unprotected services on the
board are interrupted.
Prerequisites
replaced.
l The spare channelized STM-1 processing board must be available, and the version and
type of the spare board must be the same as the version and type of the board to be
replaced. You can query the board manufacturing information to obtain the version
of the board to be replaced.

l ESD wrist strap
l Screwdriver

l U2000
l Fiber remover
Procedure
Step 2 Optional: If the services on the board are configured with linear MSP, ensure that the services
1. Query the linear MSP group.
Step 4 Check whether the version and SFP type of the spare board are the same as the version and
SFP type of the board to be replaced.
Step 6 After the board starts to work, check the STAT indicator on the board. The STAT indicator
should be on and green.

switching.
----End
6.5 Replacing the PDH Interface Board

When the PDH interface board is replaced, the services on the board are interrupted.
Prerequisites
replaced.
l The spare board must be made available, and the version and type of the spare board
must be the same as those of the board to be replaced. You can query the board
manufacturing information to obtain the version of the board to be replaced.

l ESD wrist strap
l Screwdriver
l U2000

Procedure
Step 3 Check and ensure that the version and type of the spare board are the same as the version and
type of the board to be replaced.
Step 5 After the board starts to work, check the indicators on the board. The STAT indicator should
be on and green.

----End
6.6 Replacing the Smart E1 Interface Board

When the Smart E1 Interface board is replaced, the services on the board are interrupted.
Prerequisites
replaced.
l The spare board must be available, and the version and type of the spare board must be
the same as the version and type of the board to be replaced. You can query the board

l ESD wrist strap
l Screwdriver
l U2000
Procedure
Step 1 Query the current alarms of the board to be replaced.
Step 3 Verify that the spare board has the same board version and board type as the board to be
replaced.
Step 4 Insert the spare board.
Step 5 After the substitute board starts to work, check the indicators on the board. The STAT
indicator is on and green.

NOTE
Smart E1 boards are hot-swappable. After the spare board is installed, it enters initialization state and starts to
work 2 minutes later.
Step 6 Query the current alarms of the substitute board.

There is no new alarm on the board.
----End
6.7 Replacing the Ethernet Interface Board

When the Ethernet interface board is replaced, the unprotected services on the board are
interrupted.
Prerequisites
replaced.

l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
Procedure
Step 2 Optional: If the services are configured with MPLS APS, ensure that the services are already
switched to the protection tunnel.
1. Querying MPLS APS Status.
2. If the board functions as the current working board, perform the forced switching.
Step 3 Optional: If the services are configured with PW APS, ensure that the services are already
switched to the protection PW.
1. Querying PW APS Status.
Step 5 Check and ensure that the board version and the model of the SFP module on the spare board
are the same as the board version and the model of the SFP module on the board to be
replaced.


NOTE
Ethernet interface boards are hot-swappable. After the substitute board is installed, it enters initialization state
and starts working two minutes later.
If dynamic ARP is disabled on the NE at the opposite end of an MPLS tunnel, you need to change the static
ARP table entries of the opposite NE.
be on and green.
Step 9 Optional: If the forced switching has been performed for the services, release the forced
switching.
----End
6.8 Replacing an IF Board

When an IF board is replaced, unprotected services on the board are interrupted.
Prerequisites
replaced.
l The spare board must be available, and the version and type of the spare board must be
the same as the version and type of the board to be replaced. You can query the board

l ESD wrist strap
l Screwdriver
l U2000
Precautions
IF boards support hot swap. After a substitute board is installed, it enters the initialization
state and starts working two minutes later.
If an IF port carries an MPLS tunnel and dynamic ARP is disabled on the peer NE of the
MPLS tunnel, you need to change the static ARP table entries of the peer NE.
NOTICE
To replace a dual-channel IF board, turn off the soft power switch of the connected ODU
before removing an IF cable.

Procedure
Step 2 Optional: If the services on the board are configured with SNCP, ensure that the services are
already switched to the protection channel.
1. Query the SNCP protection group.
2. If the port on the board functions as the current working channel, the current protection
channel is not on the board, perform the forced switching.
Step 3 Optional: If the services on the radio link are configured with 1+1 protection, switch the
service to the protection IF board.
1. Query the IF 1+1 protection group.
Step 4 Optional: If the services on the radio link are configured with N+1 protection, ensure that the
services are already switched to the protection IF board.
1. Query the IF N+1 protection group.
Step 5 Optional: If the services are configured with MPLS APS, ensure that the services are already
switched to the protection tunnel.
1. Querying MPLS APS Status.
Step 6 Optional: If the services are configured with PW APS, ensure that the services are already
1. Querying PW APS Status.
Step 7 Optional: If the IF board is configured with the XPIC function, see 8.1.3 Muting/Unmuting
an ODU and mute the ODU at the opposite end.
Step 8 Perform the following steps according to the IF board types.
If... Then...
A single-channel IF board needs to be Turn off the ODU-PWR switch on the IF
replaced board.
NOTICE
To turn off the ODU-PWR switch, pull the switch
lever outwards slightly and set the switch to the "O"
position.
A dual-channel IF board needs to be Turn off the soft power switch of the ODU.
replaced
Step 10 Check and verify that the version and type of the spare board are the same as the version and
Step 11 Ensure that the ODU-PWR switch on the front panel of the spare IF board is turned off.

NOTE
Skip this step when replacing a dual-channel IF board (ISM6).
be on and green.
If... Then...
A single-channel IF board needs to be Turn on the ODU-PWR switch on the front
replaced panel of the IF board.
NOTICE
To turn on the ODU-PWR switch, pull the switch
lever outwards slightly and set the switch to the "I"
position.
A dual-channel IF board needs to be Turn on the soft power switch of the ODU.
replaced

Step 16 Optional: If the forced switching has been performed for the services, release the forced
switching.
Step 17 Optional: If the forced protection switching has been performed for the radio link, release the
forced switching.
Step 18 If the IF board is configured with the XPIC function, see 8.1.3 Muting/Unmuting an ODU
and unmute the ODU at the opposite end.
----End
6.9 Replacing the CF Card

If the NE is configured with only one System control Switch&Timing board, all the services
are interrupted during the replacement of the CF card.
Prerequisites
l You must be aware of the impact of CF card replacement.
l You must know the specific position of the CF card to be replaced.
l You must be a user with "NE maintainer" authority or higher.
l You must obtain a spare CF card that has the same capacity as the CF card to be
replaced.

l ESD wrist strap
l U2000

l Fiber remover
Procedure
Step 2 Optional: If the board is configured with 1+1 protection, ensure that the services are switched
from the current working board to the protection board.
1. See 8.11 Switching the System Control Unit and the Cross-Connect Unit, and ensure
that the current working board functions as the protection board.
2. If the board functions as the current working board, perform the manual switching.
Step 4 Remove the CF card according to the illustration in the following figure.
Step 5 Check the spare CF card.
Step 6 Install the spare CF card according to the illustration in the following figure.
Step 8 After the board starts to work, observe the indicators on the board. The STAT indicator should
be on and green.
There should be no new alarms.
Step 10 Optional: If the manual switching has been performed on the board, release the manual
switching.
----End

6.10 Replacing the System Control, Switching and Timing

Board
All the services are interrupted during the period of replacing the system control, switching,
and timing board, if the NE is configured with only one system control switch and timing
board. If a CSHN board is replaced, you can restore NE data by replacing the CF card. If a
CSHNA/CSHNU board is replaced, you can back up and restore NE data from a USB flash
drive. Perform the operations specific to the type of the board to be replaced.
Prerequisites
l You must be aware of the impact of board replacement.
replaced.
l If a CSHNA/CSHNU board is to be replaced, NE data has been obtained.
– The backup NE data has been imported to a laptop where the Web LCT is installed,
if there is a backup of the NE database on the NMS.
– The network plan document has been obtained if there is no backup of the NE
database on the NMS.
Impact on System
If no protection board is available, the replacement of the system control, switching, and
timing board results in service interruption.

l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
l A USB flash drive with the authorization file if a CSHNA/CSHNU board is to be
replaced
– The file folders related to the NE (\db, \pkg, \patch, \sysdata, \script, and \license)
should not exist in the USB flash drive.
– The RTN.CER file of the NE should be copied to the root directory of the USB
flash drive.
The RTN.CER file, which stores the account and password information at the
system administration level (the password is encrypted), is generated by the system
administrator of a network management center using dedicated tools.

Context
NOTE
After the NE database is restored successfully, a cold reset is automatically performed on the NE.
Procedure
Step 1 If a CSHN board is replaced, restore NE data by replacing the CF card.
1. Query the current alarms of the board. If the board reports the A.3.122 HARD_BAD
alarm, locate the fault according to alarm causes. If the system control, switching, and
timing board needs to be replaced, go to the next step.
2. Replace the system control, switching, and timing board.
If... Then...
One system 1. Notify the onsite maintenance personnel to switch off the power
control, supply and remove the board.
switching, and 2. Verify that the version and type of the spare board (including the
timing board patch version) are correct.
is configured
NOTE
If the spare board and the board to be replaced have different patch
versions, contact Huawei engineers for loading correct patches.
3. Remove the CF card from the original board and then install the
CF card to the spare board. For details about how to install the
CF card, see 6.9 Replacing the CF Card.
4. Insert the spare board into the chassis.
5. Switch on the power supply so that the board automatically
restores the NE databases, system parameters, software
packages, and NE logs from the CF card.
NOTE
n In the process of restoring the NE database, the PROG indicator on
the board blinks green for about 20 minutes.
n If the database restoration is successful, the NE resets automatically.
During the rest, the STAT indicator is off, and the PROG indicator is
blinking green. After the NE resets successfully, the STAT and
PROG indicators are on and green.
n If the database restoration fails, the NE does not reset, and the
PROG is red. In this case, contact Huawei technical support
engineers for rectifying the fault.
NOTE
After the NE starts up normally, the STAT and PROG indicators on the
board are green.

If... Then...
Two system 1. Before replacing a working system control, switching, and

control, timing board, switch services from the working board to the
switching, and protection board. For details, see 8.11 Switching the System
timing boards Control Unit and the Cross-Connect Unit.
are configured NOTICE
When the data of the working board is being synchronized to the
protection board or synchronization data is being delivered to the chip of
the protection board, removing the working board may interrupt
services. Before removing the working board, ensure that the board is in
standby status.
Wait until the protection switchover is completed, and then go to the
next step. A protection switchover is completed only after the data of the
working board has been synchronized to the protection board and
synchronization data has been delivered to the chip of the protection
board.
2. After completing the protection switchover, Remove the board
to be replaced.
3. Check whether the version and type of the spare board are the
same as the version and type of the board to be replaced.
4. Insert the spare board.
NOTE
During the replacement process, the ACT indicator is off. After the
replacement is complete, the ACT indicator is on and green.
5. Wait for about 10 minutes to complete the backup of the data on
the main and standby system control units.
NOTE
n After the NE starts up normally, the STAT and PROG indicators on
the board are green. If data backup fails, the PROG indicator is on
and red.
n After data is being synchronized between the active and standby
system control boards, the PROG indicator on the active system
control board blinks green at an interval of 1s. Do not insert or
remove the boards.
3. Query the current alarms of the board. There should be no new alarms.
Step 2 Perform the following steps for CSHNA/CSHNU boards.

If... Then...
One system 1. Query the current alarms of the board.

control, 2. Optional:
switching, and If the NE is running, back up the NE data to the USB flash drive.
timing board is
configured a. Insert the USB flash drive in the USB port on the OptiX RTN
980.
The indicator beside the USB port is blinking yellow during the
data backup, and is steady green after the data backup is
complete.
b. Remove the USB flash drive after the data backup is complete.
NOTE
If the NE is not running, data backup is not required.
3. Switch off the power supply.
4. Replace the CSHNA/CSHNU board.
a. Make labels for the cables and then remove the cables connected
to the board.
b. Remove the CSHNA/CSHNU board.
c. Verify that the spare board and the board to be replaced are of
the same version and use the same type of SFP modules.
d. Insert the spare CSHNA/CSHNUboard into the slot.
e. Recover the original cable connections according to the labels
that are made previously.
5. See the Commissioning Guide to power on the NE.
6. Restore NE configuration data.
– If the original NE is in the running state and NE database is
backed up by following Step 2.2, then insert the USB flash drive
into the USB port of the board
NOTE
The indicator beside the USB port is blinking yellow during data
restoration, and is steady green after the data is restored. It takes more
than 10 minutes to restore NE configuration data.
– If the original NE is not in the running state and NE database is
backed up to a USB flash drive, perform the following steps:
a. Set the ID and IP address of the NE to the predefined values
by referring to Changing the NE ID and Changing the NE IP
Address.
b. Restore NE configuration data by referring to 7.4 Restoring
the Database by NMS.
– If the original NE is not in the running state and NE database is
not backed up, re-configure all data on the NE according to the
network plan.
7. Query the current alarms of the board. There should be no new
alarms.

If... Then...
Two system 1. Query the current alarms of the board.

control, 2. Before replacing a working system control, switching, and timing
switching, and board, switch services from the working board to the protection
timing boards board. For details, see 8.11 Switching the System Control Unit
are configured and the Cross-Connect Unit.
NOTICE
When the data of the working board is being synchronized to the protection
board or synchronization data is being delivered to the chip of the protection
board, removing the working board may interrupt services. Before removing
the working board, ensure that the board is in standby status.
Wait until the protection switchover is completed, and then go to the next
step. A protection switchover is completed only after the data of the working
board has been synchronized to the protection board and synchronization
data has been delivered to the chip of the protection board.
3. After completing the protection switchover, Remove the board to
be replaced.
4. Check whether the version and type of the spare board are the same
as the version and type of the board to be replaced.
5. Insert the spare board.
NOTE
During the replacement process, the ACT indicator is off. After the
replacement is complete, the ACT indicator is on and green.
6. Wait for about 10 minutes to complete the backup of the data on the
main and standby system control units.
NOTE
– After the NE starts up normally, the STAT and PROG indicators on the
board are green. If data backup fails, the PROG indicator is on and red.
– After data is being synchronized between the active and standby system
control boards, the PROG indicator on the active system control board
blinks green at an interval of 1s. Do not insert or remove the boards.
7. Query the current alarms of the board. There should be no new
alarms.
----End
6.11 Replacing the Auxiliary Board

When the auxiliary board is replaced, the services on the auxiliary board are interrupted.
Prerequisites


l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
Procedure
Step 4 Insert the spare board.
be on and green.
There should be no new alarms on the auxiliary board.
----End
6.12 Replacing the Fan Board

The IDU cannot perform air cooling in the process of replacing the fan board. Therefore, you
need to replace the fan board quickly.
Prerequisites
manufacturing information to learn about the version of the board to be replaced.

l ESD wrist strap
l U2000
Precautions
CAUTION
Do not touch the blades until the fan has stopped rotating.

Procedure
Step 2 Move the cables away from the front panel of the fan board assembly.
Step 3 Loosen captive screws.
Step 4 Remove the fan board.
Step 6 Insert the standby fan board.

Step 7 Tighten captive screws.
Step 8 After the board starts to work, observe the indicators on the board. The FAN indicator should
be on and green.

There should be no new alarms.
----End
6.13 Replacing the Power Board

If another power board works normally during the replacement period, the services at the IDU
are not affected.
Prerequisites
manufacturing information to learn about the version of the board to be replaced.

l ESD wrist strap
l Screwdriver
l U2000

Precautions
CAUTION
Do not remove or insert the power plug when the power is on. Turn off the power switch
before removing the power cable from the PIU.
Procedure
Step 2 Turn off the output power switch for the IDU on the power supply equipment.
Step 3 Remove the cables connected to the board.
Step 4 Remove the power board gently and horizontally along the guide rail.
Step 5 Ensure that the version and type of the spare board are the same as the version and type of the
board to be replaced.
Step 6 Insert the spare board steadily along the guide rail.
Step 7 Reconnect the cables between the board and the power supply equipment.
Step 8 Turn on the output power switch for the IDU.
Step 9 After the board starts to work, observe the indicators on the board. The PWR indicator should
be on and green.
----End
6.14 Replacing the SFP

When the small form pluggable (SFP) is replaced, the unprotected services on the optical/
electrical port are interrupted.
Prerequisites
l You must know the impact of SFP replacement.
l You must know the specific position of the SFP to be replaced.
l You must know the service protection and protection channels of the SFP to be replaced.
l The spare SFP must be available, and the version and type of the spare SFP must be the
same as the version and type of the SFP to be replaced. You can query the board
manufacturing information to obtain the version of the SFP to be replaced.

l ESD wrist strap

l Tweezer fiber remover

l U2000
Procedure
Step 2 Optional: If SNCP is configured for services at the optical interface, ensure that the services
1. Query the status of the SNCP group.
2. If the port on the local board functions as the working channel, the protection channel
does not involve the local board, and the protection channel is in the normal or SD state,
perform forced switching.
Step 3 Optional: If linear MSP is configured for services at the optical interface, ensure that the
services are already switched to the protection channel.
1. Query the status of the linear MSP group.
2. If the port on the local board functions as the working channel, the protection channel
does not involve the local board, and the protection channel is in the normal or SD state,
perform forced switching.
Step 4 Record the cable connections of the SFP, and then disconnect cables.
Step 5 Check the types of the spare SFP and the SFP to be replaced, and remove the SFP module.
NOTE
l Hold the extraction lever to remove the optical module.
l Press the release button before removing the STM-1 electrical module.
1 Press the release button.
2 Remove the STM-1 electical module.
Step 6 Insert the standby SFP module and reconnect cables based on the record.


Step 8 Optional: If the forced switching has been performed on the board, release the forced
switching.
switching.
----End
6.15 Replacing an ODU

When an ODU is replaced, the unprotected services on the ODU are interrupted.
Prerequisites
l You must know the impact of ODU replacement.
l You must know the specific positions of the ODU to be replaced and the IF board
connected to the ODU.
l The spare ODU must be at hand, whose type must be the same as the type of the ODU to
be replaced.

l Ejector lever (torque wrench)
l U2000
l Silicon
Precautions
CAUTION
l Before replacing an ODU, power off the ODU.
l Considering live-line working and radiation risks, it is advised to power off ODUs on
adjacent channels before replacing an ODU installed on a hybrid coupler.
NOTICE
l Replacing an ODU installed on a hybrid coupler may temporarily affect services on other
channels. It is advised to mute the peer ODU to minimize the impact.
l Do not damage the coating when you replace an ODU. In the case of any coating damage,
repair the coating timely.

Procedure
Step 1 Query the current alarms on the ODU and then record the results.
If... Then...
The ODU to be replaced connects to a Turn off the ODU-PWR switch on the IF
single-channel IF board board.
NOTICE
position.
The ODU to be replaced connects to a Turn off the soft power switch of the ODU.
dual-channel IF board
Step 3 Remove the IF cable and the PGND cable from the ODU.
Step 4 Remove the ODU.
Option Description
If... Then...
You need to remove the RTN 600 ODU Loosen the four latches of the ODU and
with a waveguide interface disconnect the ODU from the antenna, the
hybrid coupler, or ODU adapter.
You need to remove the RTN 600 ODU Remove the ODU from the post.
with a coaxial interface
You need to remove the RTN XMC ODU Loosen the captive screws on the ODU and
disconnect the ODU from the antenna, the
hybrid coupler, or ODU adapter.
Step 5 Ensure the type of the spare ODU is the same as the type of the ODU to be replaced.
Step 6 Install the ODU.
Option Description
If... Then...
You need to install a new RTN 600 ODU with a See the RTN 600 ODU Quick
waveguide interface Installation Guide.
You need to install a new RTN 600 ODU with a See the RTN 600 ODU Quick
coaxial interface Installation Guide.
You need to install a new RTN XMC ODU See the RTN XMC ODU Installation
Guide.
Step 7 Connect the PGND cable and the IF cable to the ODU.
Step 8 Waterproof the IF interface on the ODU.

If... Then...
The ODU to be replaced connects to a Turn on the ODU-PWR switch on the front
single-channel IF board panel of the IF board.
NOTICE
position.
The ODU to be replaced connects to a Turn on the soft power switch of the ODU.
Step 10 After the ODU starts to work, check the LINK indicator and ODU indicator on the IF board.
The ODU indicator and LINK indicator should be on and green.
Step 11 Query the current alarms of the ODU. There should be no new alarms on the ODU.
----End
6.16 Replacing an IF Cable

When an IF cable is replaced, the unprotected services on the IF cable are interrupted.
Prerequisites
l You must know the impact of IF cable replacement.
l You must know the specific positions of the IF cable to be replaced and the IF board
connected to the IF jumper.
l In the case of the RG-8U IF cable or the 1/2-inch IF cable, an IF jumper is required to
connect the IF cable to the IDU and both ends of the IF cable should be terminated with
type-N connectors. In the case of the 5D IF cable, the IF cable is connected directly to
the IDU and the cable end connecting to the IDU should be terminated with the TNC
connector and the cable end connecting to the ODU should be terminated with the type-
N connector.

l Multimeter
l Ejector lever
l Electro-technical knife
l File
l Installation parts and accessories of the connector
l IF cable

Precautions
NOTICE
To replace a dual-channel IF board, turn off the soft power switch of the connected ODU
before removing an IF cable.
Procedure
Step 1 Query and record the current alarm of the IDU.
If... Then...
The ODU to be replaced connects to a Turn off the ODU-PWR switch on the IF
single-channel IF board board.
NOTICE
position.
The ODU to be replaced connects to a Turn off the soft power switch of the ODU.
Step 3 Disconnect the IF cable from the IF jumper and from the ODU.
Step 4 Use a multimeter to test the connectivity of the IF cable to determine whether you need to
make new connectors for the IF cable or replace the IF cable with a new one.
If... Then...
You need to make new connectors for the See the Installation Reference and make new
IF cable connectors for the IF cable.
You need to replace the IF cable with a Replace the IF cable with a new one.
new one
Step 5 Connect the IF cable to the IF jumper and to the ODU.
Step 6 Waterproof the connectors at the two ends of the IF cable with the waterproof adhesive tape.
If... Then...
The ODU to be replaced connects to a Turn on the ODU-PWR switch on the front
single-channel IF board panel of the IF board.
NOTICE
position.

If... Then...
The ODU to be replaced connects to a Turn on the soft power switch of the ODU.
Step 8 After the ODU starts to work, check the LINK and ODU indicators on the IF board.
The ODU indicator and LINK indicator should be on and green.
Step 9 Query the current alarms of the IDU.

There should be no new alarms on the IDU.
----End
6.17 Erasing Data in the Repair Parts

The storage media on the system control board stores NE configuration data. If necessary,
erase data on the board before repair.
6.17.1 Board Storage Media

The system control board has two types of storage media: CF card and flash memory.
Overview
OptiX RTN 980 has two types of storage media: CF card and flash memory. Both the CF card
and flash memory may contain configuration data. As shown in Table 6-2, the types of
storage media supported by the system control boards for the OptiX RTN 980 are listed.
Table 6-2 Types of storage media on the system control boards
Board Storage Media
CSHN/CSHNA l Flash memory (integrated on the system

control board)
l CF card (pluggable)
CSHNA Flash memory (integrated on the system

control board)
Positions of the Storage Media

DIP switches on the system control board are used for some special maintenance-related
operations, including formatting the flash memory.
For the positions of the CF card and the DIP switches for formatting the flash memory, see
"DIP Switches and CF Card" of the system control board in the IDU Hardware Description.
NOTE
CSHNA boards do not provide DIP switches.

6.17.2 Removing the CF Card

If necessary, remove the CF card from the repaired system control board to ensure data
security.

l ESD wrist strap or ESD glove
l ESD bag for storing the removed CF card
NOTICE
Slowly and carefully remove the CF card, to prevent damages to the CF card or its card slot.
Procedure
Step 1 Wear an ESD wrist strap or ESD gloves during operations.
1. Put your hand through the ESD wrist strap, as shown inFigure 6-11.
2. Fasten the wrist strap to ensure good contact between the ESD wrist strap and your skin.
3. Connect the ground end of the ESD wrist strap to the ESD jack in the cabinet or chassis.
Step 2 Remove the CF card.
Step 3 Place the removed CF card to an ESD bag.
----End
6.17.3 Formatting the Flash Memory

If necessary, erase data in the flash memory by setting the DIP switches.

l ESD wrist strap or ESD glove

Procedure
Step 1 Wear an ESD wrist strap or ESD gloves during operations.
1. Put your hand through the ESD wrist strap, as shown inFigure 6-12.
2. Fasten the wrist strap to ensure good contact between the ESD wrist strap and your skin.
3. Connect the ground end of the ESD wrist strap to the ESD jack in the cabinet or chassis.
Step 2 Format the flash memory.
1. Remove the system control board from the chassis.
2. Set the BIOS DIP switches to binary values "1111".
When the DIP switches are set to "1111", the software will erase all data (except for
board manufacturing information), including data in the file system and the system
parameter area.
NOTE
For the positions of the DIP switches of system control boards, see "DIP Switches and CF Card"
of the system control board in the IDU Hardware Description.
3. Insert the system control board to the backup chassis, and power on the board. Observe
the RUN indicator. If the RUN indicator on the system control board blinks every 1s, the
data on the flash memory has been cleared.
NOTE
If the system control board cannot be powered on or the software fails to start, the preceding
method of clearing data from the flash memory by changing DIP switch settings is inapplicable. In
this case, contact Huawei technical support engineers.
----End

Maintenance Guide 7 Database Backup and Restoration
7 Database Backup and Restoration
About This Chapter
The OptiX RTN 980 supports database backup and restoration through the NMS.
7.1 NE Database
An NE database stores communication data, security data, alarm data, performance data, and
configuration data of an NE in a certain structure, to facilitate data query and modification
and to ensure that the data can be restored after the NE is reset.
7.2 Backing Up the Database Manually
The NE configuration data is stored in the database of an NE. To prevent the database from
being damaged due to certain risky operations such as replacing a faulty system control,
cross-connect, and timing board or upgrading the software, you need to manually back up the
database on a regular basis and before performing any risk operation.
7.3 Setting the Database Backup Policy
You can set the policy of backing up a database to realize the function of periodically backing
up the database.
7.4 Restoring the Database by NMS
If the database is damaged, you can restore the NE database by using the database files that
are saved previously.
7.5 Recovering Databases from a USB Flash Drive
When NE data is lost or abnormal and DCN communication fails, you can recover NE
databases from a USB flash drive.
7.6 Restoring Databases for an NE from Its Peer NE
This section describes how to restore databases for an NE from its peer NE. After the
databases of an NE are damaged, configure a microwave link between the NE and its peer
NE, turn up the microwave link, and restore its databases from its peer NE.
7.7 Restoring Databases from Local NEs
When the database of an NE is damaged, restore the database using the data automatically
backed up by the system to the local NE.

7.1 NE Database
An NE database stores communication data, security data, alarm data, performance data, and
configuration data of an NE in a certain structure, to facilitate data query and modification
and to ensure that the data can be restored after the NE is reset.
Three types of NE databases are available:
l Memory database (MDB)
The data in the MDB varies according to the configuration and is lost when the system
control unit is reset or when the NE is powered off.
l Dynamic random database (DRDB)
The DRDB automatically stores the data that is checked successfully. The DRDB is
resident in the reserved memory. Hence, the data in the DRDB is not lost when a warm
reset is performed on the system control unit. The data, however, is lost when a cold
reset is performed on the system control unit or when the NE is powered off.
l Flash database (FDB)
The FDB includes FDB0 and FDB1. The FDB is resident in the flash memory on the
board. Hence, the data in the FDB is permanently stored.
NE Database Backup
NE configuration data, after being delivered to the system control unit, is stored in the MDB.
Upon successful verification of the configuration data, the system control unit copies the data
from the MDB to DRDB and delivers the data to boards.
Two modes are available to back up DRDB data to the FDB:
l An NE backs up DRDB data to the FDB within five minutes after NE configuration data
is modified.
l Perform two backups of DRDB data to different areas on the FDB every 24 hours.
l Back up DRDB data to the FDB every 7 days. A maximum of 4 pieces of latest backup
data can be stored on the FDB.
The following modes are available to back up FDB data:
l Upon a scheduled backup of DRDB data to the FDB, the NE backs up FDB data to a
dedicated partition of the flash memory (other than FDB0 and FDB1).
l On the NMS, FDB data can be backed up to an NMS server manually or at specified
intervals.
l Before backing up the NE database to a USB flash drive, it is advisable to delete all
folders and files except the RTN.CER file from the USB flash drive.
l For a CSHN board: A CF card stores NE databases, system parameters (including NE-
IPs, NE-IDs, subnet masks, and LSR IDs), software packages, and NE logs.

NOTE
The software packages on a CF card are synchronized with those on the system control, switching, and
timing board only during package diffusion. Automatic or manual backup is not needed for software
package synchronization.
Ensure that the software version of the system control, switching, and timing board is the same as that
in a CF card. If the software packages on the system control, switching, and timing board are
inconsistent with those in a CF card, the SWDL_CHGMNG_NOMATCH alarm is reported.
NOTE
When you use the NMS to back up FDB data, system parameters such as NE-IPs, NE-IDs, or subnet
masks are not backed up, but LSR IDs are backed up.
The NE automatically backs up its database locally, and also backs up its database and system
parameters such as NE ID and NE IP address to the peer NE at an interval of 72 hours.
NE Database Restoration
l When an NE is warm reset, the system control unit checks whether configuration data is
available in the DRDB. If configuration data is available in the DRDB, the system
control unit restores data from the DRDB. If the configuration data in the DRDB is
damaged, the system control unit restores data from FDB0 and FDB1.
l When the NE is cold reset, the system control unit restores data from FDB0 and FDB1.
l When the data in both FDB0 and FDB1 is damaged, data can be restored from the
dedicated partition of the flash memory.
l On the NMS, the FDB data in flash memory can be restored from an NMS server
without interruption of TDM services.
l For a CSHNA board: If a USB flash drive is inserted in the USB port and the FDB data
in the USB flash drive is newer than that in the flash memory, the NE backs up the FDB
data from the USB flash drive to the flash drive.
l For a CSHN board: After you hold down the CRV button on the system control,
switching, and timing board for 8s, the data stored on the CF card will be synchronized
to the board. To synchronize the NE databases, system parameters, and NE logs from the
system control, switching, and timing board to the CF card, enable the regular backup
function. The default backup interval is 24 hours.
7.2 Backing Up the Database Manually

The NE configuration data is stored in the database of an NE. To prevent the database from
being damaged due to certain risky operations such as replacing a faulty system control,
cross-connect, and timing board or upgrading the software, you need to manually back up the
database on a regular basis and before performing any risk operation.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l You must log in to the NE.

U2000

NOTE
Procedure
Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/
Restoration from the Main Menu.
Step 2 In NE View, click Find.
Step 3 In the Find NE dialog box, set the search conditions and search for the NE that requires
database backup.
Step 4 Click OK.
Step 5 Click Backup.

NOTE
Press and hold the Ctrl button on the keyboard, you can select multiple NEs to back up the data at one
time.
Step 6 Set the data backup path to NMS Server or NMS Client according to the requirements.

Step 7 Click Start to start backing up the NE data. In NE View, Operation Status indicates the
progress of backing up the data. After the data backup is successful, Operation Status
displays a message, indicating that the operation is successful.
----End
7.3 Setting the Database Backup Policy

You can set the policy of backing up a database to realize the function of periodically backing
up the database.
7.3.1 Setting the User-Defined Backup Policy

Through this task, you can set the backup policy for a specific NE.
Prerequisites

U2000
NOTE
Each NE has a default data backup policy.
l Database packages are backed up once at 2:00.

l The default backup policy is disabled by default.

l A maximum of five database packages can be backed up.

l Data changes do not trigger any backup operations.
Procedure
Step 1 Choose Administration > NE Software Management > NE Backup Policy Management
from the Main Menu.
Then, the NE Backup Policy Management dialog box is displayed.
Step 2 In Auto Backup Policy window, set NE type.

The version, name, and IP address of the selected NE are displayed.
Step 3 Click New Policy.
Step 4 Optional: Click to import the information of the NEs.
Step 5 Optional: Click to export the information of the NEs.

The information of the selected NEs is stored in the specified location.
Step 6 In NE Table, select one or more NEs.
Step 7 Click Next.

Then, the Setting Policy dialog box is displayed.
Step 8 Set Policy Name, Period Backup Policy, and Period Save Policy.

NOTE
l If The Added NE's Policy Status is set to Enable, the NMS performs the backup operation within
the specified period, day, and time.
l If The Added NE's Policy Status is set to Disable, the backup policy is still in the Disable state
although the policy period reaches the specified period, day, and time.
Step 9 Click Advanced Settings, and set Backup Type, Max Backup Num, and Configuration
Change Backup for a certain type of NEs.
Step 10 Click OK.
Step 11 Click OK.
----End
7.3.2 Enable the Backup Policy of the Device

Through this task, you can set the backup policy of a device to the running state.
Prerequisites
You must be an NM user with NE administrator authority or higher.

U2000
NOTE
Procedure
from the Main Menu.


Step 3 Right click the selected NE, Click Enable Backup Policy.
----End
7.3.3 Disable the Backup Policy of the Device

Through this task, you can set the backup policy of a device to the suspended state.
Prerequisites


U2000
NOTE
Procedure
from the Main Menu.
Then, the NE Backup Policy Management dialog box is displayed.

Step 3 Right click the selected NE, Click Disable Backup Policy.

----End
7.4 Restoring the Database by NMS

If the database is damaged, you can restore the NE database by using the database files that
are saved previously.
Prerequisites
l The data to be restored must be backed up.

U2000
NOTE
Precautions
A backup database can be used to restore configurations only for a system control board in the
same type as that on the original NE.
Before restoring the database of an NE, ensure that the KMC key for the NE is the same as
the key for the backup database. If they are different, database restoration fails. For details
about KMC key settings, see Configuring a KMC Key.
A V100R009C00 NE can restore its database from a backup database of an NE earlier than
V100R009C00. An NE earlier than V100R009C00 can restore its database only from a
backup database of an NE in the same version.
Context
If NE configurations have been modified after the database is backed up, using the backup
database to restore configurations may interrupt DCN communication or services. Therefore,
you must manually configure service parameters if NE configurations have been modified
after the database is backed up.

Procedure
Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/
Restoration from the Main Menu.
NOTE
The equivalent operations on the Web LCT are as follows:
In NE List, click .
In Login, click OK.
For the DC, the default user name is szhw and the default password is Changeme_123. For the license tool,
the default user name is lct and the default password is Changeme_123. If the user name or password has
been changed, use the latest one.
The NE Data Backup/Restoration window is displayed.
Step 2 In NE View, click Find.
Then, the Find NE dialog box is displayed.
Step 3 In the Find NE dialog box, set the search conditions to search for the NEs that need to restore
databases.
Step 4 Click OK.

Step 5 Select the NE whose data needs to be recovered, and click Recover.
NOTE
You can select multiple NEs to recover the data at one time.
Then, the Recover dialog box is displayed.
Step 6 Select Browse in File Name.

Then, the Select File dialog box is displayed.

Step 7 Select files from NMS Server or NMS Client, and then choose the files to be recovered.
Click OK.
Step 8 Set Activate Type to With Service Interruption and select Deliver To Board Activate.
NOTE
l If Activate Type is No Reboot, only database files are overwritten and the NE will not be warm
reset. The database does not take effect until the NE is reset.
l If Activate Type is With Service Interruption, database files will be overwritten, the NE will be
warm reset, and then the database will take effect.
l If Deliver To Board Activate is selected, the EFP8/EMS6 board will be instructed to perform a cold
reset during database activation.
l If Deliver To Board Activate is unselected, the EFP8/EMS6 board will not be cold reset.
NOTE
If the NE transmits data services, select Deliver to Board.

Services are interrupted during the activation of databases.
Step 9 In the Recover dialog box, click Start.
Step 10 Click Yes in the prompt dialog box.

The system starts recovering the selected data files on the specified NE.
In the NE list of NE View, Operation Status indicates the progress of recovering the data.
After the data is recovered, Operation Status displays a message, indicating that the
operation is successful.
Step 11 In NE View, right-click the NE and choose Active Database from the shortcut menu.
The Active Database dialog box is displayed.

Step 12 Click Start to start activating the database.
In NE View, Operation Status indicates the progress of activating the database. After the
database is activated, Operation Status indicates that the operation is successful.
----End

7.5 Recovering Databases from a USB Flash Drive

When NE data is lost or abnormal and DCN communication fails, you can recover NE
databases from a USB flash drive.
Prerequisites
l The NE database has been backed up.
l You have logged in to the NE on the NMS.

U2000
USB flash drive
Precautions
OptiX RTN 980 supports use of old-version backup files to restore the database.
Procedure
Step 1 Copy all NE database files backed up on the NMS server to the \db directory in the USB flash
drive.
NOTE
Other directories related to the NE (\pkg, \patch, \sysdata, \script, and \license) cannot exist.
Step 2 Copy the RTN.CER and RTNEXTRA.CER files of the NE to the root directory of the USB
flash drive.
NOTE
The RTN.CER and RTNEXTRA.CER files, which store the account and password information at the
system administration level (the password is encrypted), are generated by the system administrator of a
network management center using dedicated tools. For details about how to generate the file, refer to
instructions in Preparing the Certificate File for NE Access from a USB Flash Drive.
Step 3 Insert the USB flash drive in the USB port on the OptiX RTN 980.
NOTE
During the database recovering process, do not perform operations such as data configuration, NE resets, and
software loading.
Step 4 Check the data loading status based on the indicator on the USB flash drive.

Status of the USB Data Loading Status Operation

Indicator
The indicator blinks yellow The loading of Remove the USB flash
and then turns steady green. commissioning data is drive.
complete.
NOTE
l When the indicator is
blinking yellow, do not
remove the USB flash
drive. Otherwise, the data
loading may be
interrupted.
l After the data loading is
complete, the NE will
automatically reset, which
takes 2 minutes to 3
minutes. After the reset is
complete, the USB
indicator and the system
indicator (SRV) on the NE
are both steady green,
indicating that the data
loading is successful.
The indicator is off. The USB flash drive is l Copy the commissioning
faulty and fails to get online. data to another USB
NOTE flash drive.
Another possible cause is that l Repeat 1 to load the
the USB flash drive is not
commissioning data to
properly inserted.
the NE.
The indicator blinks red. The type of the USB flash l Copy the commissioning
drive is incorrect or an error data to another USB
occurs when the NE flash drive.
attempts to read/write the l Repeat 1 to load the
USB flash drive. commissioning data to
NOTE the NE.
Preparing Documents and
Tools provides the USB flash
drive types that the OptiX
RTN 980 supports.
The indicator is steady red. The loaded commissioning Reload the data:
data is abnormal. l Save the correct NE
software and
commissioning data
scripts in the correct
directories of the USB
flash drive.
l Repeat 1 to load the
commissioning data to
the NE.

----End
7.6 Restoring Databases for an NE from Its Peer NE

This section describes how to restore databases for an NE from its peer NE. After the
databases of an NE are damaged, configure a microwave link between the NE and its peer
NE, turn up the microwave link, and restore its databases from its peer NE.
Prerequisites
A microwave link between the NE and its peer NE has been configured, and the DCN channel
has been set up.

U2000
NOTE
Precautions
NE database backup or recovery is not supported over IF1 links.
If failed to restore database, please other methods (eg. download database).
A V100R009C00 NE can restore its database from a backup database of an NE earlier than
V100R009C00. An NE earlier than V100R009C00 can restore its database only from a
backup database of an NE in the same version.
Context
If NE configurations have been modified after the database is backed up, using the backup
database to restore configurations may interrupt DCN communication or services. Therefore,
you must manually configure service parameters if NE configurations have been modified
after the database is backed up.
Procedure
Step 1 Restore databases for the NE from its peer NE.

3
2
Step 2 Check the execution results.

Select the NE.
Execution results.
5
----End
7.7 Restoring Databases from Local NEs

When the database of an NE is damaged, restore the database using the data automatically
backed up by the system to the local NE.
Prerequisites

U2000
NOTE

Background
If the configuration of an NE is modified after the database is backed up, using the backup file
to restore the database may interrupt the DCN communication or services. To resolve this
issue, manually configure the corresponding service parameters.
The database can be restored only to the system control board of the original type.
Procedure
Step 1 Restore the database from the local NE.
NOTE
In the Database restoration from history window, File indicates the time when the system performs
automatic backup. Select the database to be restored to suit your situation.
Step 2 In the Risk window that appears, click Yes.
Step 3 Check the execution results.

----End

Maintenance Guide 8 Common Maintenance Operations
8 Common Maintenance Operations
About This Chapter
This section introduces common maintenance operations.
8.1 Microwave Link Troubleshooting

This section describes common maintenance operations related to microwave link
troubleshooting.
8.2 Ethernet Service Troubleshooting
This section describes common maintenance operations related to Ethernet service
troubleshooting.
8.3 TDM/CES Service Troubleshooting
This section describes common maintenance operations related to TDM/CES service
troubleshooting.
8.4 Software Loopback
Software loopback refers to the loopback operation that is implemented by using the NMS.
During software loopback, you need not visit the engineering site. Hence, software loopback
is used more widely than hardware loopback.
8.5 Hardware Loopback
Hardware loopback refers to the loopback operation performed by changing the physical
connection.
8.6 Reset
Reset is an important method of troubleshooting software faults. Reset is classified into cold
reset, warm reset.
8.7 Setting the Automatic Release Function
To protect the communication between the NMS and NE against improper operations, an NE
supports the automatic release of the ODU muting, software loopback, and other operations
that require you to exercise caution. The automatic release time is five minutes by default.
You can set whether to enable the automatic release function and the automatic release time
through the NMS.
8.8 Querying Power Consumption of Boards
This section describes how to query power consumption of the ODU and each board.

8.9 Querying Optical Power and Alarm Thresholds of SDH Ports

This section describes how to query the RX/TX optical power and alarm thresholds of SDH
ports.
8.10 Preventing Service Loops
You can enable the automatic service loopback detection function or the automatic broadcast
packet suppression function to prevent service loops.
8.11 Switching the System Control Unit and the Cross-Connect Unit
When the is configured with two system control, cross-connect, and timing boards, you can
manually switch the system control unit and the cross-connect unit as required.
8.12 Cleaning Fiber Connectors and Adapters
The optical connectors are easily contaminated in the maintenance process. The minute dust
particles that can be seen only in the microscope can also affect the quality of optical signals.
In this case, the system performance deteriorates. Hence, the fiber connectors or adapters that
are terminated need to be cleaned in time.

8.1 Microwave Link Troubleshooting

This section describes common maintenance operations related to microwave link
troubleshooting.
8.1.1 Monitoring Radio Link Indicators

This section describes how to collect high-density samples about the RSL and MSE indicators
of radio links for monitoring. The longest monitoring duration is 48 hours.
Prerequisites
l The time and time zone of an NE on which microwave link indicators are sampled must
be the same as those on the NMS.

U2000
NOTE
Procedure
Step 1 Navigate to the interface for monitoring the RSL and MSE indicators of radio links.
Step 2 Configure parameters for monitoring the RSL and MSE indicators of radio links.

Set the monitoring 3 6

duration. The
maximum value is Set the monitored
48 hours. object.
Step 3 Query the monitoring result.
Set the query type.

The query result of the MSE
is displayed in green and that
of the RSL is displayed in red.
Set the time range of
7 the query.
8
9
----End
8.1.2 Scanning Interfering Signals

You can learn whether intra-frequency or inter-frequency interference exists by scanning
frequency spectra in microwave channels.
Prerequisites
l Mute the ODU at the opposite end, before scanning the reference signal.

U2000
NOTE

When interfering signals are scanned, services and DCN communication are interrupted.
Both local frequency scanning and remote frequency scanning are supported. You can obtain
results of remote frequency scanning after DCN communication restores.
Procedure
Step 1 Scan interfering signals.
1
Select an ODU, and specify the scanning range, frequency
3 adjustment step, and bandwidth parameters.
4
5
Select Mute Peer Transmit Status to mute the peer

transmitter and specify the auto unmute time.
2
The NE will increment its transmit frequency based on the specified

frequency adjustment step and within the specified scanning range, and
detect and record receive frequency values accordingly.
For remote frequency scanning, you can query the

results after DCN communication restores.
----End
8.1.3 Muting/Unmuting an ODU

The transmission status of an ODU can be "mute" or "unmute". In the "unmute" state, an
ODU can receive and transmit microwave signals. In the "mute" state, an ODU can only
receive microwave signals because its transmitter does not work.
Prerequisites
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.

U2000
NOTE

Procedure
l Mute/Unmute an ODU.
2
4
Typically, Configure Transmission Status should be set

to unmute.
In the mute state, an ODU can only receive microwave
signals.
In the unmute state, an ODU can transmit and receive
microwave signals.
----End
8.1.4 Turning On/Off the Soft Power Switch of an ODU

This section describes how to turn on or off the soft power switch of an ODU connected to a
dual-channel IF board through software.
Prerequisites
l The mapping IF board and ODUs have been added on the NE Panel.

U2000
NOTE
Procedure
l Turn on/off the soft power switch of an ODU.

3
4
1
Select the
desired IF port. 5
----End
8.1.5 Performing a PRBS Test for the IF Board

If a special test tool is unavailable, you can perform the PRBS test by using the embedded test
system on the IF Board.
Prerequisites
Different service mode has different PRBS direction.

U2000
NOTE
Precautions
Two PRBS test types are available, PRBS frames are transmitted through the specified E1
timeslot or transmitted as Ethernet frames.
Figure 8-1 PRBS test of the IF Board
IF board ODU ODU IF board
PRBS
transmitter
1 1 1
PRBS
transmitter
NE at the local end NE at the opposite end

1 IF port outloop

NOTICE
l During the PRBS test, the services in the tested path are interrupted.
l The PRBS test can be performed only in one path and in one direction at one time.
l During the PRBS test, ensure that the PRBS function is enabled on both the local end and
peer end.
l The standby IF unit does not support the PRBS test. Before you perform the PRBS test for
the standby IF Board of a 1+1 HSB/FD/SD protection group, you must switch the standby
IF Board to the working state.
Procedure
Step 1 Configure an outloop on the peer IF board by referring to instructions in 8.4.7 Setting
Loopback for the IF Board and .
Step 2 Start a PRBS test on the IF board.
Select the desired IF board.
Configure the
test time. 5
1 4
Select the desired PRBS test type. 3

Three PRBS test types are available: Select an E1 path.
1. PRBS frames are sent to the air-interface This parameter is
direction as Ethernet frames. mandatory only for
2. PRBS frames are sent to the cross-connect E1 PRBS tests.
direction through a specified E1 timeslot.
3. PRBS frames are sent to the air-interface
direction through a specified E1 timeslot.
2 6
Step 3 View test results.

8
View test results.
Green indicates no
exception.
9 View the test

report.
No bit error is found,

indicating that the link
works properly.
10
----End
8.2 Ethernet Service Troubleshooting

This section describes common maintenance operations related to Ethernet service
troubleshooting.
8.2.1 Querying the Attributes of an Ethernet Port

Through the operation, you can learn about the attributes of an Ethernet port, such as rate.
Prerequisites

U2000

Procedure
Step 1 Optional: Query the attributes of the FE or GE port on the packet plane.
NOTE
1. In NE Explorer, select the required NE from the Object Tree.
2. Choose Configuration > Interface Management > Ethernet Interface from the
Function Tree.
3. Click the Advanced Attributes tab.
4. Check the parameters such as Port Physical Parameters, Transmitting Rate, and
Receiving Rate.
Step 2 Optional: Querying the attributes of the port.

NOTE

1. In NE Explorer, select the required NE from the Object Tree.
2. Choose Configuration > Interface Management > Microwave Interface from the
Function Tree.
4. Check the parameters such as Transmitting Rate and Receiving Rate.
Step 3 Optional: Query the attributes of the external port on the EFP8 board.
NOTE
1. In NE Explorer, select the EFP8 board from the Object Tree.
2. Choose Configuration > Ethernet Interface Management > Ethernet Interface from
the Function Tree.
3. Select External Port.
5. Check the parameters such as Transmitting Rate and Receiving Rate.
NOTE
By performing this operation, you can query the attributes of the external ports on the EFP8 board (PORT1 to
PORT8) and the attributes of the bridging port on the EFP8 board (PORT9).
----End
8.2.2 Searching for Service Paths Based on VLANs

For E-Line services, this operation can display the transmission path of the VLAN service
flow on one access port. For E-LAN services, this operation can display the broadcast domain
to which the VLAN belongs.
Prerequisites
End-to-end Ethernet services have been deployed.

Procedure
Step 1 Optional: Search for an E-Line service path.
Step 2 Optional: Search for an E-LAN service path.
----End

8.2.3 Searching for Service Paths Based on MAC Addresses

For E-LAN services, this operation allows the information of a MAC address learned by each
NE on a service path to be displayed, illustrating the entire service path through which
packets with the MAC address being the source address travel.
Prerequisites
Procedure
Step 1 Search for an E-LAN service path.
Step 2 Query the Learning of MAC Addresses.

----End
8.2.4 Checking the Layer 2 Protocols Used by Ethernet Services

This section describes how to check the Layer 2 protocols, including ERPS, MSTP, and STP,
used by E-LAN services based on service paths.
Prerequisites
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure

Step 2 Check the Layer 2 protocols used by the E-LAN services.
----End
8.2.5 Performing Intelligent Service Fault Diagnosis for Ethernet

Services
This section describes how to intelligently diagnose faults of Ethernet services based on
service paths.
Prerequisites

Procedure
Step 1 Search for services.
Step 2 Select a service to be diagnosed by specifying a service port.
Step 3 Diagnose the service and display the result.

----End
8.2.6 Performing E-LAN Service Loopback Detection

This section checks whether a loopback occurs on Ethernet services based on service paths.
Users can quickly rectify a data storm on a loop after finding out the loopback point.
Prerequisites
created.
Procedure

Step 2 Perform E-LAN service loopback detection.
NOTE
l If a service is looped back, can be seen from the icons.

l To remove a loopback, you must disable the E-LAN service. After the loopback is removed, you can
manually enable the E-LAN service.
----End
8.2.7 Monitoring Ethernet Service Performance and Traffic

Volume Based on Service Paths
This section describes how to monitor Ethernet service performance based on service paths.

Prerequisites
created.
Procedure
Step 1 Search for service paths.
Step 2 Query the real-time and historical performance data of each measured object on each service
path.
The following figure shows how to query the real-time performance data of priority queues on
a port. Querying the real-time and historical performance data of other measured objects is
similar.

----End
8.2.8 Querying Ethernet Service QoS Configurations Based on

Service Paths
This section describes how to query Ethernet service QoS configurations based on service
paths.
Prerequisites
End-to-End Ethernet services and associated fibers have been created.
Procedure
Step 1 Search out service paths.

Step 2 Select the service to be diagnosed by specifying service ports.
Step 3 Query QoS configurations.

----End
8.2.9 Using IP Ping Commands to Locate Ethernet Service Faults

The OptiX RTN 980 can respond to IP ping commands, facilitating Ethernet fault diagnosis.
Prerequisites

U2000
NOTE
Context
Two types of IP ping functions are supported:
l Near-end IP ping

The near-end IP ping function is typically used to check whether the link between a
customer edge (CE) device and a near-end transmission NE is faulty. Near-end IP ping
can be initiated from the CE device to a UNI on the near-end transmission NE, or from a
UNI on the transmission NE to the near-end CE device. For example, the RNC initiates
IP ping packets to the UNI port on NE1, as shown in Figure 8-2.
l Far-end IP ping
The far-end IP ping function is typically used to check whether the link between a CE
device and a far-end transmission NE is faulty. Far-end IP ping can be initiated from the
CE device to a UNI on the far-end transmission NE, or from a UNI on the transmission
NE to the far-end CE device. For example, the RNC initiates IP ping packets to the UNI
port on NE2, as shown in Figure 8-2.
Figure 8-2 Application of the IP ping functions

Far-end IP Ping
Near-end IP Ping
NodeB RNC
NE2 NE1
Near-end IP Ping
Far-end IP Ping
Precautions
l IP ping can be enabled only for UNI Ethernet ports.
l IP ping can be enabled only for a maximum of four ports on an NE.
l E-Aggr services do not support far-end IP ping.
l To support far-end IP ping, the protocol VLAN ID (if any) must be configured to the
same value as the VLAN ID carried by IP packets initiated by the local CE. This enables
NEs enabled with the IP ping function can select the correct PW for transmitting IP ping
packets based on the configured protocol VLAN ID.
l If IP ping packets initiated by the local CE do not carry any VLAN ID (for example,
when the port tag attribute is access), the protocol VLAN ID must be set to 0 or /. This
enables NEs enabled with the IP ping function to select the correct service for
transmitting IP ping packets based on the PVIDs of UNI ports.
l The CE device or transmission NE on which IP ping is initiated must support non-strict
ARP learning mode. That is, the CE must be able to learn MAC addresses based on ARP
request packets.
l The maximum length of the IP ping packet is 1494 bytes.

Sample IP Ping Connection

Figure 8-3 shows the test procedure, using the Ethernet service between PORT1 on NE1 and
PORT1 on NE2 as an example.
Figure 8-3 Networking diagram
137.0.0.2/
255.255.255.0 137.0.0.4/ 137.0.0.3/ 137.0.0.1/
255.255.255.0 255.255.255.0 255.255.255.0
PORT 1 PORT 1
VLAN ID=100 VLAN ID=100
NodeB NE 2 NE 1 RNC
The Ethernet service between NE1 and NE2 has the VLAN ID 100. The tag attributes of both
PORT1s on NE2 and NE1 are tag aware.
You can perform IP ping on a transmission NE by initiating the ping from the transmission
NE or from a CE device. The following describes the two methods of initiating IP ping.
Procedure
l Initiate IP ping from a transmission NE to locate Ethernet service faults.
a. Configure near-end IP ping on NE1. That is, ping the near-end RNC (137.0.0.1)
from Port1 (137.0.0.3) on NE1.
i. In the NE Explorer, select the desired NE and choose Configuration > IP
Ping Test.
ii. Enable IP ping for the port and configure related parameters.

NOTE
If NE1 and the RNC are on the same network segment, set Next Hop IP Address to
the IP address of the RNC. If NE1 and the RNC are on different network segments, set
Next Hop IP Address to the IP address of the router near NE1.
iii. Click Apply.
iv. Click IP PING TEST.
v. Click Add.
vi. Configure near-end IP ping parameters.
NOTE
A port supports multiple IP ping tests. A maximum of 16 IP ping tests can be initiated
on a network.
b. Configure far-end IP ping on NE1. That is, ping the near-end Node B (137.0.0.2)
from Port1 (137.0.0.3) on NE1.
i. Configure IP ping on NE1 by referring to a.
ii. Configure IP ping on NE2 by referring to a.
iii. Configure the far-end IP ping agent on NE2. The proxy IP address is the
address of Port1 (137.0.0.3) on NE1.
c. On NE1, initiate near-end IP ping to the RNC (that is, ping 137.0.0.1).
If... Then...
The operation times out A fault occurs between NE1 and the
RNC. Handle the fault.
Response packets are received from Go to the next step.

the RNC.
d. On NE1, initiate far-end IP ping to the NodeB (that is, ping 137.0.0.2). If response
packets are received from the NodeB, links are normal. Therefore, end fault
diagnosis. If no response packets are received from the NodeB, go to the next step.
If... Then...
The operation times out Go to the next step.

If... Then...
Response packets are received from Services are normal. Therefore, end
the NodeB. fault diagnosis.
e. On NE2, initiate near-end IP ping to the NodeB (that is, ping 137.0.0.2).
If... Then...
NodeB. Handle the fault.
Response packets are received from A transmission network fault occurs

the NodeB. between NE1 and NE2. Handle the
fault.
l Initiate IP ping from the CE device to locate Ethernet service faults.

a. On NE1, set IP ping parameters to perform near-end IP ping. That is, ping Port1
(137.0.0.3) on NE1 from the RNC (137.0.0.1).
i. In the NE Explorer, select the desired NE and choose Configuration > IP
Ping Test.
ii. Enable IP ping for the port and configure related parameters.
NOTE
If NE1 and the RNC are on the same network segment, set Next Hop IP Address to
the IP address of the RNC. If NE1 and the RNC are on different network segments, set
Next Hop IP Address to the IP address of the router near NE1.
iii. Click Apply.
b. On NE1, set the far-end IP ping agent to ping Port1 (137.0.0.4) on NE2 from the
RNC (137.0.0.1).
i. Configure IP ping on NE1 by referring to a.
ii. Configure IP ping on NE2 by referring to a.
NOTE
Next Hop IP Address is used only for near-end IP ping. Therefore, you are advised to set
Next Hop IP Address to the IP address of the NodeB so that NE2 can respond to near-end
IP ping.
iii. Configure the far-end IP ping agent on NE1. The proxy IP address is the
address of Port1 (137.0.0.4) on NE2.
iv. Click Apply.

c. On the RNC, initiate pass-through IP ping to the NodeB (that is, ping 137.0.0.2).
If... Then...
Response packets are received from Services are normal. Therefore, end
the NodeB. fault diagnosis.
The operation times out Go to the next step.
d. On the RNC, initiate near-end IP ping to NE1 (that is, ping 137.0.0.3).
If... Then...
Response packets are received from Go to the next step.

NE1.
RNC. Handle the fault.
e. On the RNC, initiate far-end IP ping to NE2 (that is, ping 137.0.0.4).
If... Then...
Response packets are received from A fault occurs between NE2 and the
NE2. NodeB. Handle the fault.
The operation times out A transmission network fault occurs

between NE1 and NE2. Handle the
fault.
----End
8.2.10 Monitoring Ethernet Packets Through Port Mirroring

To monitor and analyze the Ethernet packets at a port, you can enable the port mirroring
function so that the received or transmitted packets on the port are duplicated to another
Ethernet port to which the Ethernet tester is connected. Then, you can monitor and analyze the
packets.
Prerequisites

U2000
NOTE

Context
Figure 8-4 Schematic diagram of Ethernet port mirroring

NE under port mirroring
Forwarding
Mirroring Port
Ethernet equipment port
Duplication Ethernet equipment

Monitoring
port
Ethernet tester
The port mirroring can be performed in two directions.

For the physical ports:
l In the ingress direction
Also in the upstream direction. The equipment duplicates the packets received from the
mirroring port to the observing port, and then transmits the packets from the observing
port to the Ethernet tester.
l In the egress direction
Also in the downstream direction. The equipment duplicates the packets transmitted by
the mirroring port to the observing port, and then transmits the packets from the
observing port to the Ethernet tester.
For the VCTRUNK of EFP8/EMS6:
l In the upstream direction, the ports mirror the data transmitted from the VCTRUNK to
the TDM side.
l In the downstream direction, the ports mirror the data transmitted from the TDM side to
the VCTRUNK.
Precautions
EG4/EG4P boards of the OptiX RTN 980 do not support port mirroring in the egress
direction.
Procedure
Step 1 Configure the port mirroring function for Ethernet boards other than EMS6/EFP8.

Step 2 Configure the port mirroring function for EMS6/EFP8 boards.

----End
8.2.11 Monitoring Ethernet Packets by Using Port Traffic

Mirroring
If the Ethernet packets at a port need to be observed and analyzed, you can enable the port
traffic mirroring function. It duplicates packets received by a port to another Ethernet port that
is connected to an Ethernet tester, so that the Ethernet tester observes and analyzes the
packets.
Prerequisites

U2000
NOTE

Context
Figure 8-5 Traffic mirroring over Ethernet ports

NE with port traffic
mirroring enabled
Forwarding
Mirroring Port
Ethernet equipment port
Duplicating Ethernet equipment
Monitoring service traffic
port
Ethernet tester
Port traffic mirroring duplicates only service traffic matching the specified rule to the
listening port.
Precautions
NOTE
l One NE supports a maximum of four port traffic mirroring (only ingress) or port mirroring
configurations.
l One port supports only one port traffic mirroring configuration. If port traffic mirroring is
configured, ingress port mirroring cannot be configured.
l The port traffic mirroring setting on a slave port in a LAG must have traffic classification rules
consistent with those on the master port. Before deleting a slave port, delete traffic mirroring
configurations on the port.
l Traffic classification rules can be specified by C-VLAN ID, C-VLAN PRI, S-VLAN ID, S-VLAN
PRI, IP DSCP, or DMAC but L2 and L3 rules cannot coexist.
l Port traffic mirroring by VLAN-based traffic classification cannot be configured for the following
services: point-to-point transparently-transmitted E-Line services, VLAN-based E-Line services
(VLAN switching table configured), QinQ-based E-Line services, PW-carried E-Line services, or
IEEE 802.1ad-based E-LAN services.
l MPLS packets can be mirrored only by Ethernet frame header before the MPLS label.
l Only data boards support port traffic mirroring.
l After port traffic mirroring is configured, traffic mirroring rules must not be modified or deleted.
Procedure
Step 1 Configure the port traffic mirroring function.

Select the NE.
Configure the mirror name, direction of

mirror source function point, mirror
source function point, and mirror
observation point.
4
Configure the traffic

classification rules.
7
5
9
Configure the parameter of

traffic classification rules.
8
6
2
----End
8.2.12 Capturing Headers of Specified Ethernet Packets

You can capture headers of ingress/egress Ethernet packets at a port for further analysis. The
number and type of Ethernet packets to be captured can be specified.
Prerequisites
l Ethernet services have been created, and service packets are being forwarded.
l The port is not configured with complex traffic classification.

U2000
Context
Headers of Layer 2 and Layer 3 packets can be captured. The header length of smallest Layer
2 packets is 16 bytes, consisting of an SMAC (6 bytes), a DMAC (6 bytes), and a VLAN
header (4 bytes). The header length of largest Layer 3 packets is 74 bytes, consisting of a
longest frame header (34 bytes), an IPv4 header (20 bytes), and a TCP header (20 bytes).
NOTE
This operation is intended to detect transmission faults or errors as required, but may require the collection
and storage of some communication content (at most the first 74 bytes of transmitted packets collected and
stored). Huawei is forbidden to collect or storage communication content without your awareness. It is
recommended that you enable the related function in line with the objective and scope allowed by the local
laws and regulation. You should also take proper measures before performing this operation, to ensure
communication confidentiality.

Precautions
l In a link aggregation group (LAG), physical link aggregation (PLA) group, or enhanced
PLA (EPLA) group, the packet header capturing function can be enabled only for the
master port.
l On the OptiX RTN 980, packet headers cannot be captured from the slave port of an
inter-board LAG.
l One-off packet header capturing allows you to capture a maximum of 1000 packets. In
consecutive packet header capturing, the NMS stores the latest 5000 packets captured.
l The OptiX RTN 980 allows header capturing only from ingress packets.
l On the OptiX RTN 980, headers of Layer 2 packets cannot be captured by inner VLAN
or Ethernet type, and headers of Layer 3 packets cannot be captured by source IP
address, sink IP address, TOS, ICMP CODE, TCP source port, or UDP source port.
l On the OptiX RTN 980, the packet header capturing function cannot be enabled for
Layer 3 ports or mixed (Layer 2+Layer 3) ports.
l On the OptiX RTN 980, Ethernet ports of EM6T/EM6TA/EM6F/EM6FA/EG2D boards
and IF ports of IFU2/IFX2 boards supports rule-based packet header capturing, not
allowing port-based packet header capturing.
Procedure
l Capture headers of Layer 2 packets.
1
Select the
desired NE. 3
Set basic parameters.
Specify Layer 2 service

parameters.
4
View packet capture results and analyze 5

network status based on the results.
l Capture headers of Layer 3 packets.

Select the 3
desired NE.
Set basic parameters.
Specify Layer 3 service parameters.

4
View packet capture results and analyze 5

network status based on the results.
----End
8.2.13 Using the Ethernet Test Frames

By using the Ethernet test frames, you can check the connectivity of VCTRUNKs. Only the
EFP8 board supports this operation.
Prerequisites
l The service traffic is encapsulated or mapped by using the GFP method.

U2000
NOTE
The Ethernet board uses the specific GFP management frame or Ethernet frame as the test
frame. One frame is transmitted to the opposite Ethernet board per second. After receiving the
test frame, the Ethernet board returns the response frame. Upon receiving the response frame,
the Ethernet service processing board at the local end can judge the connectivity of the
VCTRUNK in between.

Figure 8-6 Ethernet test frames between Ethernet boards
Test frame
Local Remote
Ethernet Ethernet
board board
Response frame
Precautions
NOTICE
Do not use the test frames when the network traffic is heavy.
Procedure
Step 1 In NE Explorer, select the EFP8 board.
Step 2 Choose Configuration > Ethernet Maintenance > Ethernet Test from the Function Tree.
Then, the Ethernet Test dialog box is displayed.
Step 3 Select the test port and click Clear Counters. Select Clear All Counters.
Step 4 Set Send Mode and Frames to Send.

NOTE
It is recommended that you choose "Burst mode", and a maximum of 10 frames can be transmitted each
time.
Step 5 Click Apply.

The system starts transmitting and receiving test frames.
Step 6 After Status displays Finished Sending, click Query.
Step 7 Check Counter of Frames Sent and Counter of Received Response of Test Frame.
Test frames are used to check the network connectivity. If some of the test frames are lost but
no alarm is reported on the SDH side, you can infer that the network is normal. If all the test
frames are lost, you can infer that the network is faulty.
----End
Related Information
If you choose the continue mode, the local port transmits test frames continuously until the
test is disabled.

8.3 TDM/CES Service Troubleshooting

This section describes common maintenance operations related to TDM/CES service
troubleshooting.
8.3.1 Setting the On/Off State of the Laser

When performing operations such as testing a fiber cut, you can set the on/off state of the
laser rather than removing and re-inserting the optical fiber on site.
Prerequisites

U2000
NOTE
Precautions
Before setting the on/off state of the laser for a port, determine whether NE management is
performed using this port. If yes, do not set the on/off state of the laser for the port. If no, this
setting is allowed.
Procedure
Step 1 Select the desired SDH optical interface board or the channelized STM-1 processing board
from the Object Tree in the NE Explorer.
Operation object Operation Steps
SDH optical interface board 1. Choose Configuration > SDH

Interface from the Function Tree.
2. Choose By Function.
3. Select Laser Switchfrom the drop-down
list.
4. Select a port, and then set Laser Switch.
channelized STM-1 processing board 1. Choose Configuration > Interface

Management > SDH Interface from
the Function Tree.
2. Select Basic Attributes.
3. Select a port, and then set Laser
Interface Status.

Step 2 Click Apply.

A confirmation dialog box is displayed.
Step 3 Click OK.

A prompt is displayed.
Step 4 Click OK.
----End
8.3.2 Setting the ALS Function

The SDH optical interface board supports the automatic laser shutdown (ALS) function. This
function enables the board to turn off a laser when the board does not transmit services, the
optical fiber is faulty, or the received optical signals are lost.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select the desired SDH optical interface board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > Automatic Laser Shutdown from the Function Tree.
Step 3 Select a port, and then set Automatic Shutdown to Enabled.
Step 4 Click Apply to save the settings.
----End
8.3.3 Performing a PRBS Test for the Smart E1 Processing Board

system on the Smart E1 processing Board.
Prerequisites

U2000

NOTE
Context
The OptiX RTN 980 supports the PRBS test in the UNI direction and in the NNI direction.
The PRBS test in the UNI direction can be performed to check the cable connect to the Smart
E1 processing Board, as shown in Figure 8-7.
Figure 8-7 PRBS test in the tributary direction

Smart E1
processing unit
PRBS
Transmitter
PRBS
Recevicer
1 Loopback at the port
The PRBS test in the NNI direction can be performed to check the connection between the
Smart E1 processing Board and the remote NE, as shown in Figure 8-8.
Figure 8-8 PRBS test in the NNI direction

Smart E1 Cross-connect Smart E1
processing unit Unit processing unit
OUT
PRBS
transmitter
Inloop at an
E1 port
PRBS IN
receiver

Precautions
NOTICE
l A PRBS test can be performed for a CES service that is encapsulated in CESoPSN mode
and is carried by timeslots 1 to 31 on either UNI or NNI side.
l In a PRBS test in the NNI direction for an SATOP CES service, the LOOP_ALM alarm
will be reported on the E1 service where this service is deployed.
NOTE
Procedure
Step 1 Configure a loopback as required by referring to Figure 8-7 and Figure 8-8.
NOTICE
When a loopback is performed for a port or channel, services on the port or channel are
interrupted.
Step 2 Start a PRBS test for the smart E1 processing board

Specify the port type, frame

Select the desired format, test period, and test
smart E1 board in 3 duration (1 to 255)
the NE Explorer.

View test results, Green

indicates no exception.
The number of bit errors

and BER is 0, indicating
no exception.
----End
8.3.4 Performing a PRBS Test for the Tributary Board

system on the tributary Board.
Prerequisites

U2000
Context
The OptiX RTN 980 supports the PRBS test in the tributary direction and in the cross-connect
direction.
The PRBS test in the tributary direction can be performed to check the connection between
the tributary Board and the DDF, as shown in Figure 8-9.

Figure 8-9 PRBS test in the tributary direction

DDF frame PDH unit
PRBS
Transmitter
PRBS
Recevicer
1 Loopback at the DDF frame
The PRBS test in the cross-connect direction can be performed to check the connection
between the tributary Board and the remote NE, as shown in Figure 8-10.
Figure 8-10 PRBS test in the cross-connect direction

a) IF board working as the line board
PDH interface Cross-connect

board board IF board IF board
OUT
PRBS
transmitter
1 2 3
PRBS
IN
receiver
1 VC-4 inloop or 2 IF port inloop 3 IF port outloop

composite port inloop
b) Line board working as the SDH optical interface board

SDH optical
PDH interface board Cross-connect board interface board
OUT
PRBS
transmitter
1 2 3
PRBS
receiver IN
1 VC-4 inloop 2 Port inloop 3 Port outloop

Precautions
NOTICE
l If you perform a PRBS test in the tributary direction of a port on the SP3S/SP3D board,
the services carried on the other ports may be interrupted transiently.
NOTE
Procedure
Step 1 Configure a loopback as required by referring to Figure 8-9 and Figure 8-10.
NOTICE
When a loopback is performed on a port or channel, services on the port or channel are
interrupted.
Step 2 Start a PRBS test for the tributary board.

Configure the port type, test
period, and test duration (1
3 to 255).
Select an E1
interface board in the
NE Explorer.
1

View test results. Green

indicates no exception.
The number of bit errors

and the BER are 0,
indicating no exception.
----End
8.3.5 Querying the Impedance of an E1 Channel

The impedance of an E1 channel is 75 ohms or 120 ohms.
Prerequisites

U2000
NOTE
Procedure
Step 1 Select a PDH tributary board from the Object Tree in the NE Explorer.

Step 2 Choose Configuration > PDH Interface from the Function Tree.
Step 3 Select By Board/Port(Channel).
Step 4 Select Port in the list.
Step 5 Select a port, and check Port Impedance.
----End
8.4 Software Loopback

Software loopback refers to the loopback operation that is implemented by using the NMS.
During software loopback, you need not visit the engineering site. Hence, software loopback
is used more widely than hardware loopback.
NOTICE
l Before performing a loopback, ensure that the corresponding services are not E-LAN
services. A loopback is forbidden for E-LAN services. Loopbacks include software/
hardware loopback at an Ethernet port, loopback at an IF port, and loopback at an SDH
port or E1 port that carries EoPDH or EoSDH services.
l Loopback operations on E-LAN services may cause network storms and service
interruptions.
8.4.1 Setting Loopback for the SDH Optical Interface Board

The SDH optical interface board supports the optical/electrical interface inloop/outloop and
the VC-4 path inloop/outloop.
Prerequisites

U2000
NOTE
Context
The optical/electrical interface inloop is a process wherein the signals over an SDH port are
looped back at the overhead processing unit towards the backplane.

Figure 8-11 Optical/electrical interface inloop
SDH optical
Backplane interface board
SDH
The optical/electrical interface outloop is a process wherein the signals over an SDH port are
looped back at the overhead processing unit towards the remote equipment.
Figure 8-12 Optical/electrical interface outloop
SDH optical
Backplane interface board
SDH
The VC-4 path outloop is a process wherein the signals on a VC-4 path are looped back at the
logic processing unit towards the remote equipment.
Figure 8-13 VC-4 path outloop
SDH optical
Backplane
interface board
VC-4
The VC-4 path inloop is a process wherein the signals on a VC-4 path are looped back at the
logic processing unit towards the backplane.

Figure 8-14 VC-4 path inloop
SDH optical
Backplane
board
VC-4
Precautions
NOTICE
l The services may be interrupted at the port or on the path where the loopback is
performed.
l A software loopback may be released automatically after a certain period (five minutes, by
defaults). For details, see 8.7 Setting the Automatic Release Function.
Procedure
Step 1 Select the SDH optical interface board from the NE Explorer.
NOTE
The SDH optical interface boards described in this section include the physical SL1D and SL1DA board and
the logical SL4D board that the physical CSHN board maps.
Step 2 Choose Configuration > SDH Interface from the Function Tree.
Step 3 Select By Function, and select the loopback mode from the drop-down list.
To Perform... Choose...
Optical/electrical interface loopback Optical(Electrical) Interface Loopback
VC-4 path loopback VC4 Loopback
Step 4 Set the loopback status of the port or path based on the requirements.
Step 5 Click Apply.

Then, the Confirm dialog box is displayed.
Step 6 Click OK.
----End

8.4.2 Setting Loopback for the Channelized STM-1 Processing

Board
The channelized STM-1 processing board supports the optical/electrical interface inloop/
outloop.
Prerequisites

U2000
NOTE
Context
The optical/electrical interface inloop is a process wherein the signals over an STM-1 port are
looped back at the overhead processing unit towards the backplane.
Figure 8-15 Optical/electrical interface inloop
Channelized STM-1
Processing Board
backplane
VC-12
The optical/electrical interface outloop is a process wherein the signals over an STM-1 port
are looped back at the overhead processing unit towards the remote equipment.
Figure 8-16 Optical/electrical interface outloop
Channelized STM-1
backplane Processing Board
VC-12

Precautions
NOTICE
performed.
Procedure
Step 1 Select the channelized STM-1 processing board from the Object Tree.
Step 2 Choose Configuration > Interface Management > SDH Interface from the Function Tree.
Step 3 Select Advanced Attributes tab.
Step 4 Set the loopback status of the port or path based on the requirements.
Step 5 Click Apply.

Step 6 Click OK.
----End
8.4.3 Setting Loopback for the Tributary Board

The tributary board supports the tributary inloop and outloop.
Prerequisites

U2000
NOTE
Context
The tributary inloop is a process wherein the signals over a PDH port are looped back at the
coding/decoding unit towards the backplane.

Figure 8-17 Tributary inloop
Backplane PDH interface board
PDH
The tributary outloop is a process wherein the signals on a tributary path are looped back at
the PDH interface board of the local IDU towards the remote equipment.
Figure 8-18 Tributary outloop
Backplane PDH interface board
PDH
Precautions
NOTICE
The services may be interrupted on the port or on the path where the loopback is performed.
Procedure
Step 1 Select the PDH interface board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > PDH Interface from the Function Tree.
Step 3 Select By Function, and select Tributary Loopback from the drop-down list.
Step 4 Set the loopback status of the path based on the requirements.

Step 5 Click Apply.

Step 6 Click OK.
----End
8.4.4 Setting a Loopback for the Smart E1 Processing Board

A Smart E1 processing board supports inloops and outloops on E1 ports.
Prerequisites

U2000
NOTE
Context
The E1 inloop is a process wherein the signals over an E1 port are looped back from the
coding/decoding unit to the backplane.
Figure 8-19 E1 inloop
Smart E1
Backplane Processing Board
E1
The E1 outloop is a process wherein the signals over an E1 port are looped back from the
Smart E1 processing board of the local IDU to the remote equipment.
Figure 8-20 E1 outloop
Smart E1
Backplane Processing Boards
E1

Precautions
NOTICE
performed.
l A software loopback may be released automatically within a period (5 minutes, by
default). For details, see 8.7 Setting the Automatic Release Function.
Procedure
Step 1 Select the Smart E1 processing board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > Interface Management > PDH Interface from the Function Tree.
Smart E1
Backplane Processing Board
E1
Step 3 In the Advanced Attributes tab, select the required port.
Step 4 Set the loopback status of the port as required.
Step 5 Click Apply.

The system displays a prompt dialog box for confirmation.
Step 6 Click OK.
Step 7 Close the dialog box.
----End
8.4.5 Setting a Loopback for the Packet-plane Ethernet Interface

Board
The Packet-plane Ethernet interface board supports the Ethernet port inloop (at the MAC
layer and PHY layer).
Prerequisites


U2000
NOTE
Context
The Ethernet port MAC inloop is a process wherein the Ethernet physical signals are looped
back at the service processing module of the board at the MAC layer towards the backplane.
The Ethernet port PHY inloop is a process wherein the Ethernet frame signals are looped back
at the interface module of the board at the PHY layer towards the backplane.
Figure 8-21 Ethernet port inloop
Ethernet service
Backplane
processing board
MAC PHY
Precautions
NOTE
The tributary boards described in this section include the physical EM6TA, EM6FA, EM6T and EM6F boards
and the logical EG2D board that the physical CSHN board map.
PORT 10 on the EFP8 board can not be configured with loops.
PORT 8 on the EMS6 board can not be configured with loops.
NOTICE
l A loopback operation results in service interruption.
NOTICE
l When Port Mode of an Ethernet port is set to Layer 3, do not perform any loopback on
the port. In this case, LSP Traceroute is recommended for locating faults.
l If an NE is managed through the inband DCN using a port, do not perform any loopback
on the port. Otherwise, the NE becomes unavailable to the NMS.

Procedure
Step 1 Select an Ethernet processing board from the Object Tree in the NE Explorer.
Select the desired Ethernet 4

board.
1
2 6
Step 2 Choose Configuration > Interface Management > Ethernet Interface from the Function
Tree.
Step 3 Click the Advanced Attributes tab.
Step 4 Set the loopback status of the port based on the requirements.
Step 5 Click Apply.

Step 6 Click OK.
----End
8.4.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet

Interface Board
EPF8 board supports the inloop at Ethernet ports (at the MAC layer and PHY layer) and the
inloop in VC-12 paths. EMS6 board supports the inloop at Ethernet ports (at the MAC layer
and PHY layer) and the inloop in VC-3 paths.
Prerequisites

U2000
NOTE

Context
A MAC layer inloop is an inloop where the service processing module loops back the
Ethernet physical signals towards the backplane through the MAC layer. A PHY layer inloop
is an inloop where the interface module loops back the Ethernet frame signals towards the
backplane through the PHY layer.
NOTE
PORT 9 in the EFP8 board only supports inloop at the MAC layer.
PORT 7 in the EMS6 board only supports inloop at the MAC layer.
Figure 8-22 Ethernet port inloop
Ethernet service
Backplane
processing board
MAC PHY
An inloop in a VC-12 path is an inloop where the logic processing unit of a board loops back
the signals in a specific VC-12 path towards the backplane.
Backplane EFP8
EOPDH
An inloop in a VC-3 path is an inloop where the logic processing unit of a board loops back
the signals in a specific VC-3 path towards the backplane.
Backplane EMS6
EOS

Precautions
NOTICE
l A loopback operation may interrupt the services on the port where the loopback is
performed.
l A software loopback may be automatically released within a period (five minutes by
default). For details, see 8.7 Setting the Automatic Release Function.
NOTE
A VC-3 loopback can be performed only after the EMS6 is configured with services.
Procedure
Step 1 In NE Explorer, select the required board from the Object Tree.
Step 2 Select the corresponding function options from the Function Tree according to the loopback
type.
PHY loopback 1. Choose Configuration > Ethernet Interface Management >
Ethernet Interface from the Function Tree.
MAC loopback 1. Choose Configuration > Ethernet Interface Management >
Ethernet Interface from the Function Tree.
VC-12 path 1. Choose Configuration > SDH Interface from the Function Tree.
inloop 2. Select By Function.
3. Select the required VC-12 path.
VC-3 path inloop 1. Choose Configuration > SDH Interface from the Function Tree.
2. Select By Board/Port(Channel).
3. Select the required VC-3 path.
Step 3 Set the loopback status of the port as required.
Step 4 Click Apply.

The confirmation dialog box is displayed.
Step 5 Click OK.

The prompt dialog box is displayed.

Step 6 Click OK.

Step 7 Close the prompt dialog box.
----End
8.4.7 Setting Loopback for the IF Board

Loopbacks on the IF board are classified into IF port loopback, composite port loopback, and
port MAC loopback. The IF1 board supports the IF port inloop, IF port outloop, composite
port inloop, and composite port outloop. The IFU2/IFX2 board supports the IF port inloop, IF
port outloop, composite port inloop, composite port outloop, and port MAC inloop. The
ISU2/ISX2/ISV3 board supports the IF port inloop, IF port outloop, composite port inloop,
and composite port outloop.
Prerequisites

U2000
Context
The IF port inloop is a process wherein the IF signals are looped back at the modem unit
towards the backplane.
Figure 8-25 IF port inloop
Backplane IF board
IF signal
The IF port outloop is a process wherein the IF signals are looped back at the modem unit of
the board towards the remote equipment.
Figure 8-26 IF port outloop
Backplane IF board
IF signal

The composite port inloop is a process wherein the microwave baseband signal is looped back
at the MUX/DEMUX unit of the board towards the backplane.
Figure 8-27 Composite port inloop
Backplane IF board
Microwave
baseband signal
The composite outloop is a process wherein the microwave baseband signal is looped back at
the MUX/DEMUX unit of the board towards the remote equipment.
Figure 8-28 Composite port outloop
Backplane IF board
Microwave
baseband
signal
Precautions
NOTICE
performed.
l To perform the software loopback on the standby IF board of the 1+1 HSB/FD/SD
protection group, switch the standby IF board to the working state forcibly. Otherwise, the
operation may fail.
l Before performing the loopback operation for the IFU2/IFX2 board, disable the AM
function at both ends of the radio link.

NOTICE
When Port Mode of an port is set to Layer 3, do not perform any loopback on the port. In
this case, LSP Traceroute is recommended for locating faults.
NOTE
Steps for configuring a loopback for an IF board on the U2000 are the same as those on the Web LCT.
Procedure
Step 1 Select the corresponding IF board from the Object Tree in the NE explorer.
NOTE
Step 2 Select the desired navigation path based on the loopback type.
IF port loopback 1. Choose Configuration > IF Interface from the Function Tree.
2. Select IF Attributes tab.
3. Select the port where the loopback needs to be performed and set
IF Port Loopback.
Composite port 1. Choose Configuration > Interface Management > Microwave
loopback Interface from the Function Tree.
2. Select Loopback Attributes.
Composite port loopback.
MAC loopback 1. Choose Configuration > Interface Management > Microwave
Interface from the Function Tree.
2. Select Loopback Attributes.
MAC Loopback.
Step 3 Click Apply.

Step 4 Click OK to close the dialog box.

Then, a dialog box is displayed.
----End
8.4.8 Setting Software Loopback for the NE

This task sets the loopback for the object on an NE.

Prerequisites

U2000
NOTE
Precautions
NOTICE
performed.
Procedure
Step 1 Select the NE in the NE Explorer.
Step 2 Choose Diagnoses&Maintenance > NE Loopback from the Function Tree.
Step 3 Select the desired loopback status for the desired port in the table.
Step 4 Click Apply.
----End
8.4.9 Setting Software Loopback for the Microwave Link

This task sets the loopback for the object on a single-hop radio link.
Prerequisites


U2000
NOTE
Precautions
NOTICE
The services may be interrupted at the port or on the path where the loopback is performed.
Procedure
Step 1 Select the NE in the NE Explorer.
Step 2 ChooseDiagnoses&Maintenance > Radio Link Loopback from the Function Tree.
Step 3 Select the local IF board.
Step 4 Select the desired loopback status for the desired object.
Step 5 Click Apply.

Then, the dialog box is displayed.
Step 6 Click OK.
----End
8.4.10 Locating a Fault by Performing Loopback Operations

Loopback is a common method of locating the fault.
Prerequisites

U2000
Service Trail
Figure 8-29 shows how to locate a fault by performing a loopback operation.

Figure 8-29 Service trail

PDH SDH
Cross-connect IF ODU ODU
IF Cross-connect
tributary
tributary
board board board board
board board
NE1 NE2
PDH SDH
Cross-connect IF IF Cross-connect
tributary ODU ODU tributary
board board board board
board board
NE4 NE3
Optical cable
Precautions
The LSP Traceroute method, instead of sectional loopbacks, is recommended for locating the
faults of PWE3 services.
Procedure
Step 1 If the services are available on the radio links, perform the inter-station loopbacks to narrow
down the fault to a specific hop.
1. Set the outloops for the SDH optical interface boards on NE2 and NE3, and then
perform the inter-station loopbacks to locate the fault.
Step 2 After the fault is located on the specific radio link, perform the intra-station loopbacks to
narrow down the fault to a specific NE or board.
1. Set inloop for the IF board on the NEs at both ends of the radio link where the fault
occurs, to check whether the service receiver or the radio link is faulty.
2. If the fault is located in the service receiver, set outloop for the PDH tributary board
to check whether the interface board or switch unit is faulty.
3. If the radio link is faulty, replace the IF board and ODU to check whether the IF board or
ODU is faulty.
----End
8.5 Hardware Loopback

Hardware loopback refers to the loopback operation performed by changing the physical
connection.

Hardware loopback is classified into optical cable loopback, PDH cable loopback, and
Ethernet electrical port loopback.
l Optical cable loopback indicates that the receive and transmit optical fibers are
connected through a fiber jumper on the ODF. In certain occasions, an optical attenuator
is added based on the actual situation, to prevent the optical SFP from being damaged by
the excessive receive optical power.
l PDH cable loopback indicates that the receive and transmit PDH cables are connected
through a short-circuiting cable or connector on the DDF.
l Ethernet electrical port loopback indicates that the receive and transmit service signals
on one Ethernet port are looped back through a special loopback Ethernet cable.
NOTICE
l Before performing a loopback, ensure that the corresponding services are not E-LAN
services. A loopback is forbidden for E-LAN services. Loopbacks include software/
hardware loopback at an Ethernet port, loopback at an IF port, and loopback at an SDH
port or E1 port that carries EoPDH or EoSDH services.
l Loopback operations on E-LAN services may cause network storms and service
interruptions.
8.6 Reset
Reset is an important method of troubleshooting software faults. Reset is classified into cold
reset, warm reset.
8.6.1 Cold Reset

Cold reset is a process wherein the board software is reset and the board is re-initiated. During
the board initialization, the FPGA, if any, is re-loaded.
Prerequisites

U2000
NOTE

Precautions
NOTICE
l Cold reset causes service interruption because it is similar to the procedure of removing
and inserting a board.
l Do not configure a board that is being reset.
l Do not modify IF configurations when an ODU is being reset. Otherwise, the
configurations may be incorrect or do not take effect.
l Before resetting system control boards, ensure that data synchronization between the
active and standby system control boards is complete. If a reset is performed before the
data synchronization is complete, service configurations are lost.
Procedure
Step 1 In Running Status of the U2000, right-click the board where the cold reset needs to be
performed.
Step 2 Choose Cold Reset from the shortcut menu.

Step 3 Click OK.
----End
8.6.2 Warm Reset

Warm reset is a process wherein the board software is reset but the board is not re-initiated.
Prerequisites

U2000
NOTE
Precautions
During warm reset, the board software is reset but the services are not interrupted.

NOTICE
l When a board is reset, protocols running on the board may be interrupted.
l Do not configure a board that is being reset.
l Do not modify IF configurations when an ODU is being reset. Otherwise, the
configurations may be incorrect or do not take effect.
Procedure
Step 1 In Running Status of the U2000, right-click the board where the warm reset needs to be
performed.
Step 2 Choose Warm Reset from the shortcut menu.

Step 3 Click OK.
----End
8.7 Setting the Automatic Release Function

To protect the communication between the NMS and NE against improper operations, an NE
supports the automatic release of the ODU muting, software loopback, and other operations
that require you to exercise caution. The automatic release time is five minutes by default.
You can set whether to enable the automatic release function and the automatic release time
through the NMS.
Prerequisites

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function
from the Main Menu.

NOTE
The equivalent operations on the Web LCT are as follows:

In the NE Explorer, select the desired NE, and choose Configuration > Automatic Disabling of NE
Function from the Function Tree.
Step 2 Select the desired NE from the Object Tree. Click .

Step 3 In Automatic Disabling of NE Function, set Auto Disabling and Auto Disabling
Time(min).
Step 4 Click Apply to complete the settings for the automatic release function.
----End
8.8 Querying Power Consumption of Boards

This section describes how to query power consumption of the ODU and each board.
Prerequisites

U2000
NOTE
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Power Management from the Main
Menu.
Step 2 In the NE Power dialog box, select the Board Power tab.
Step 3 Select the required NE or board from the object tree, and then click .

Step 4 Click Query.

The Query progress bar is displayed.
Step 6 On the Board Power tab page, browse Nominal Power Consumption and Current Power
Consumption of the selected board.
----End
8.9 Querying Optical Power and Alarm Thresholds of

SDH Ports
This section describes how to query the RX/TX optical power and alarm thresholds of SDH
ports.
Prerequisites

U2000
NOTE
Procedure
Step 1 Query the optical power and alarm thresholds of SDH ports.
----End

8.10 Preventing Service Loops

You can enable the automatic service loopback detection function or the automatic broadcast
packet suppression function to prevent service loops.
8.10.1 Setting the Enabling Status of Automatic Service Loop

Detection for NEs
When the NE supports E-LAN service mounting and the port status changes from down to
up, service loop detection is automatically initiated and looped services are disabled.
Prerequisites

U2000
NOTE
Context
l Principle of E-LAN service loop detection: Special LD packets are sent (DA is a special
unicast packet, and SA indicates source MAC address. VLAN tags are encapsulated
based on the port that initiates the detection, and service information is encapsulated into
the payload of LD packets). The VLAN ID of LD packets is the same as that of service
packets, and the intermediate NE may forward LD packets as service packets. If the NE
receives the LD packets sent by itself from the same VPN (the SVL bridge is determined
according to the DA and SA, and the IVL bridge is determined according to the DA, SA,
and VLAN), the system considers that a loop exists.
l Automatic loop detection is enabled by default upon service creation and the port status
change.
l If automatic loop detection is enabled upon service creation: service loop detection will
be automatically initiated on the first and last VLANs in the VLAN list after a logical
port is added to the E-LAN. If a loop is detected on either of the two VLANs, the logical
port is disabled. If new VLANs are added on a logical port, service loop detection will be
automatically initiated on the first and last VLANs among the new VLANs. If a loop is
detected on either of the two VLANs, all the newly added VLANs are disabled.
l If automatic loop detection is enabled upon the port status change, service loop detection
will be automatically initiated on all logical ports on a physical port after the physical
port changes from down to up. If multiple VLANs are accessed to a logical port, service
loop detection will be initiated on any two VLANs. If a loop is detected, the logical port
is disabled and the SRV_SHUTDOWN_LD alarm is reported.

NOTE
Limitation and Impact

l After the function is enabled, loop detection will be initiated only when new services are created or
the physical port changes from down to up. If a loop occurs when neither of the preceding
conditions is met (such as a third-party network loop), it cannot be detected automatically or
disabled.
l If the LD packets sent by an NE are discarded during transmission (including but not limited to link
congestion, link bit error, transient link interruption, and board reset), the service loop cannot be
detected.
l If service loop detection is automatically initiated, after a loop is detected and the service is disabled,
the disabled service cannot be automatically enabled after the loop is eliminated. The disabled
service can only be enabled manually by the user. For details, see Operation Procedure.
l After automatic service loop detection is enabled, an LD packet is sent every second. If a loop is
detected within three consecutive detection periods (a period of five seconds), the system considers
that a loop exists and the service is disabled. If no loop is detected within three consecutive detection
periods (a period of five seconds), the system considers that no loop exists and the detection stops.
l Two VLANs on a logical port are randomly selected for automatic service loop detection. When
loops occur on some VLANs on the logical port: if no loop occurs on the selected VLANs but loops
occur on the other VLANs on the logical port, the loop cannot be detected and the service cannot be
disabled. If loops occur on the selected VLANs but no loop occurs on the other VLANs on the
logical port, the VLANs where no loop occurs are disabled.
l When services are disabled, the NNI of the S-Aware bridge disables all NNIs on the physical port
where the NNI of the S-Aware bridge is configured, and the E-LAN services of other types only
disable the logical port where a loop is detected.
l For VPLSs in IVL mode, when no UNI is configured, the NNI does not support automatic service
loop detection.
l When a loop occurs in a network but no broadcast storm occurs, automatic loop detection may cause
services to be disabled.
Precautions
When a loop occurs in a network but no broadcast storm occurs, automatic loop detection
may cause services to be disabled. If this occurs in a live network, disable the function of
automatic loop detection on the NE and re-enable the disabled service. After that, eliminate
the loop and enable the function again.
Procedure
Step 1 In the NE Explorer, select an NE from the object tree. Choose Diagnosis & Maintenance >
E-LAN LD Test Management from the function tree.
Step 2 Select Auto or Disabled.
Step 3 Click Apply.
----End

Procedure
1. Synchronize NE alarms, and check whether the SRV_SHUTDOWN_LD alarm occurs
on the NE. If the alarm occurs, find the service that is disabled according to alarm
details.
a. If the VUNI is disabled, the format of alarm location information is L2VPN(Service
ID)_VUNI(VUNI ID)_Port. As shown in Figure 8-30, the alarm location
information indicates that the VUNI on port 5 on board 3 in E-LAN 3956 on NEs
(55–66) is disabled.
Figure 8-30
b. If the VUNI is disabled, the format of alarm location information is L2VPN(Service

ID)_VUNI(VUNI ID)_PWID. As shown in Figure 8-31, the alarm location
information indicates that the PW 4874 of E-LAN 4842 on NEs (35-211) is
disabled.
Figure 8-31

2. In the NE Explorer located by the alarm information, select Configuration Ethernet

Service Management E-LAN Service from the function tree. Find and select the E-
LAN service according to the service ID reported by the SRV_SHUTDOWN_LD
alarm, and choose Manual Loop Detection.
3. Select UNI or NNI information, and click Service Status List. After the Service Status
List is displayed, check the service status. Enable indicates that the service is not
blocked, and Disable indicates that the service is blocked by loop detection. Select the
blocked service, and click Enable to re-enable the service.
NOTE
l Check the services before re-enabling the blocked services. If a loop exists, disrupt the loop before
re-enabling the blocked service.
l Service interruption persisting after the service is re-enabled indicates that a loop exists. Delete the
service and check the physical loop.

8.10.2 Enabling the Automatic Broadcast Packet Suppression

Function
After the automatic broadcast packet suppression function is enabled, an NE will
automatically start suppress broadcast packets over the corresponding ports upon detection of
MAC address flapping.
Prerequisites

U2000
NOTE
Context
Upon detection of MAC address flapping, an NE reports A.3.78 ELAN_SMAC_FLAPPING
alarms.
Precautions
NOTE
l EG2D boards support the suppression of broadcast, unknown multicast, and unknown unicast
packets.
l EX1 boards support the suppression of broadcast, unknown multicast, and unknown unicast packets.
l EG4/EG4P boards support the suppression of only broadcast packets.
l EM6T/EM6F/EM6TA/EM6FA boards support the suppression of only broadcast packets.
l IFU2/IFX2 boards support the suppression of broadcast, unknown multicast, and unknown unicast
packets.
l ISU2/ISX2 boards support the suppression of broadcast, unknown multicast, and unknown unicast
packets.
l ISV3 boards support the suppression of broadcast, unknown multicast, and unknown unicast
packets.
l ISM6 boards support the suppression of only broadcast packets.
l In a LAG group, PLA group consisting of IF boards, IF 1+1 protection group, or IF N+1 protection
group, the slave/standby port automatically synchronizes the broadcast packet suppression threshold
from the master/main port.
l In an EPLA group, the slave port automatically synchronizes the broadcast packet suppression
threshold from the master port and supports the suppression of broadcast, unknown multicast, and
unknown unicast packets.
l If MAC address flapping occurs on multiple ports, the automatic broadcast packet suppression
function can suppress packets at only two ports.
Procedure
Step 1 Enable the automatic broadcast packet suppression function.

1
3
Select the NE.
4
Enable automatic
broadcast packet
suppression
Step 2 Set a packet suppression threshold.
NOTICE
If the automatic broadcast packet suppression threshold is set to an excessively small value,
services may be lost, that is, packet loss may occur.
3
Select the NE.
4
Threshold for enabling
automatic broadcast
packet suppression
NOTE
If an automatic broadcast packet suppression threshold is specified and another broadcast packet
suppression threshold is set in the Ethernet port attributes, the smaller threshold will actually take effect.
----End

8.10.3 Enabling Loop Detection Upon MAC Address Flapping

After loop detection upon MAC address flapping is enabled for an NE, the NE automatically
initiates a loop detection upon detecting that MAC addresses learned by E-LAN services flap.
Prerequisites

U2000
NOTE
Procedure
Step 1 Enable loop detection upon MAC address flapping.
----End
8.11 Switching the System Control Unit and the Cross-

Connect Unit
When the is configured with two system control, cross-connect, and timing boards, you can
manually switch the system control unit and the cross-connect unit as required.
Prerequisites


U2000
NOTE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer.
NOTE
Step 2 Choose Configuration > Board 1+1 Protection from the Function Tree.
NOTE
Step 3 In 1+1 Protection List, select Cross-Connect Protection Pair.

NOTE
Step 4 Perform the 1+1 protection switching on the board.
If... Then...
Active Board is set to Working Board Click Working/Protection Switching.
Active Board is set to Protection Board Click Restore Working/Protection.
Step 5 In the prompt that is displayed, click OK.

NOTE
----End
8.12 Cleaning Fiber Connectors and Adapters

The optical connectors are easily contaminated in the maintenance process. The minute dust
particles that can be seen only in the microscope can also affect the quality of optical signals.
In this case, the system performance deteriorates. Hence, the fiber connectors or adapters that
are terminated need to be cleaned in time.
8.12.1 Cleaning Fiber Connectors by Using Cartridge Cleaners

When there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them for
cleaning the fiber connectors.
Prerequisites
l Disconnect both ends of the fiber. Ensure that there is no laser light on the fiber
connectors.

l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are
contaminated.

Cartridge cleaner
Procedure
Step 1 Press down and hold the lever. Then, the shutter slides back and exposes a new cleaning area.
Figure 8-32 Using the CLETOP cassette cleaner
Step 2 Position the fiber tip slightly against the cleaning area and drag the fiber tip slightly in the
downward direction.

Figure 8-33 Dragging the fiber tip slightly on one cleaning area
Step 3 Repeat the same in the other cleaning area in the same direction as Step 2.
Figure 8-34 Dragging the fiber tip slightly on the other cleaning area

Step 4 Release the lever to close the cleaning area.
----End
8.12.2 Cleaning Fiber Connectors by Using Lens Tissue

When there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.
Prerequisites
l Disconnect both ends of the fiber. ensure that there is no laser light on the fiber
connectors.
l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are
contaminated.

l Clean solvent
l Non-woven lens tissue
NOTE
l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.
Do not use alcohol or formalin.
l The fiber cleaning tissue or lint-free wipes can substitute the non-woven lens tissue.
l The special cleaning roll can substitute the special compressed gas.
Procedure
Step 1 Place a small amount of cleaning solvent on the lens tissue.
Step 2 Drag the fiber tip slightly on the lens tissue.
Figure 8-35 Cleaning the fiber with the lens tissue

Step 3 Repeat Step 2 several times on the areas of the lens tissue that have not been used.
Step 4 Use the compressed gas to blow the fiber tip.
When using compressed gas, note the following points:
l First spray it into the air because the initial spray of condensation may contain certain
sediment.
l Ensure that the injector nozzle is as close as possible to (but does not touch) the
connector surface.
----End
8.12.3 Cleaning Fiber Adapters by Using Optical Cleaning Sticks

The fiber adapters need to be cleaned with optical cleaning sticks. This section describes the
method of cleaning fiber adapters on the optical interface board. The same method can be
used to clean fiber adapters on the optical attenuators and flanges.
Prerequisites
l Before you clean the fiber adapter, remove the optical fiber and shut down the laser. For
details about how to shut down a laser, see 8.3.1 Setting the On/Off State of the Laser.
l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is
contaminated.

l Optical cleaning sticks
l Clean solvent
NOTE
l In the case of the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm. In
the case of the LC optical interface, use the cleaning stick with a diameter of 1.25 mm.
l The medical cotton or long fiber cotton can substitute the optical cleaning stick.
l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.
Do not use alcohol or formalin.
l The special cleaning roll can substitute the special compressed gas.
Procedure
Step 1 Apply a small amount of cleaning solvent on the optical cleaning stick.
Step 2 Touch the adapter gently with the optical cleaning stick and turn the stick clockwise four to
five times.
Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can
clean the adapter tip.
Step 3 Use the compressed gas to blow the fiber adapter.
When using compressed gas, note the following points:
l First spray the compressed gas into the air because the initial spray of condensation gas
may contain some sediment.

l Ensure that the injector nozzle is as close as possible to (but does not touch) the inner
surface of the connector.
----End

Maintenance Guide A Alarm Reference
A Alarm Reference
Alarms are important indicators when abnormalities occur on the equipment. This chapter
describes all the possible alarms on the OptiX RTN 980 and how to handle these alarms.
A.1 Alarm List (in Alphabetical Order)
The following table lists all the possible alarms generated by the OptiX RTN 980 in
alphabetical order.
A.2 Alarm List (Classified by Logical Boards)
This part lists the alarms that are reported by each board.
A.3 Alarms and Handling Procedures
This chapter describes all the alarms on the OptiX RTN 980 in alphabetical order and how to
handle these alarms.

A.1 Alarm List (in Alphabetical Order)

The following table lists all the possible alarms generated by the OptiX RTN 980 in
alphabetical order.
Table A-1 Alarm list

Alarm Name Description Alarm
Severity
A_LOC Loss of clock in the upstream bus Major
ACR_LOCK_FAIL 1588 ACR locking fails Major
AES_MAC_ERR AES verification failure Critical
ALM_E1RAI E1 link remote alarm indication Minor
ALM_GFP_dCSF Loss of GFP client signals Critical
ALM_GFP_dLFD Out of frame state of generic framing Major

procedure (GFP) frames
ALM_IMA_LIF Frame delimitation is out-of-frame at the Major

local end of the IMA link.
ALM_IMA_LODS Differential delay of the IMA link crosses Major

the threshold.
ALM_IMA_RE_RX_UNUS The IMA link on the opposite NE fails in Minor

ABLE the receive direction.
ALM_IMA_RE_TX_UNUS The IMA link on the opposite NE fails in Minor

ABLE the transmit direction.
ALM_IMA_RFI Frame delimitation is out-of-frame at the Major

remote end of the IMA link.
AM_DOWNSHIFT Downshift of AM modes Major
APS_FAIL Failure indication of MS protection Major

switching
APS_INDI Indication of the APS protection switching Major
APS_MANUAL_STOP MS protocol stopped manually Minor
ARP_FAIL An Ethernet port fails to learn the MAC Major

address of the remote end using the ARP.
ARP_MAC_MISMATCH The MAC address of the static ARP entry Major

is different from the actual MAC address.
ARP_SPOOF An ARP spoofing attack. Major


Severity
ATMPW_UNKNOWNCEL The number of unknown ATM cells Major

L_EXC exceeds the specified threshold in a time
unit.
AU_AIS AU alarm indication Major
AU_LOP Loss of AU pointers Major
B1_EXC Excessive regenerator section errors (B1) Minor
B1_SD Signal degradation due to excessive Minor

regenerator section errors (B1)
B2_EXC Excessive multiplex section errors (B2) Major
B2_SD Signal degradation due to excessive Minor

multiplex section errors (B2)
B3_EXC Excessive higher order path bit errors (B3) Major
B3_EXC_VC3 Excessive B3 bit errors in a VC-3 path Major
B3_SD Signal degradation due to excessive higher Minor

order path bit errors (B3)
B3_SD_VC3 Signal degradation due to excessive VC-3 Minor

path (B3) bit errors
BAT1TEMP_SENSOR_FAI The temperature sensor of battery group 1 Major

L fails.
BAT2TEMP_SENSOR_FAI The temperature sensor of battery group 2 Major

L fails.
BD_NOT_INSTALLED The logical board is not added on the Minor

NMS.
BD_STATUS The board is out-of-position. Major
BDTEMP_SENSOR_FAIL The board temperature sensor of the Major

cabinet fails.
BGPBACKTRANSITION A BGP session is interrupted. Major
BIOS_STATUS The board is in BIOS state. Major
BIP_EXC Excessive BIP errors Minor
BIP_SD Signal degradation due to excessive BIP Minor

errors
BOOTROM_BAD BOOTROM data check fails. Major
BRDCASTRATIO_OVER The ratio of broadcast traffic exceeds the Major

threshold.


Severity
BUS_ERR Bus errors Critical
CES_ACR_LOCK_ABN The locking function of CES ACR service Minor

clock is abnormal.
CES_APS_INDI Packet MSP protocol state indication Major
CES_APS_MANUAL_STOP The MSP protocol is disabled manually. Minor
CES_JTROVR_EXC The amount of jitter buffer overflow Major

crosses the specified threshold.
CES_JTRUDR_EXC The amount of jitter buffer underflow Major

crosses the specified threshold.
CES_K1_K2_M K1 and K2 mismatch Minor
CES_K2_M K2 mismatch Minor
CES_LOSPKT_EXC The number of lost packets crosses the Major

specified threshold in a time unit.
CES_MALPKT_EXC The number of deformed packets crosses Major

the specified threshold in a time unit.
CES_MISORDERPKT_EX The number of lost disordered packets Major

C crosses the specified threshold in a time
unit.
CES_RDI Remote defect indication Minor
CES_STRAYPKT_EXC The number of error packets crosses the Major

specified threshold in a time unit.
CESPW_OPPOSITE_ACFA The AC circuit on the opposite NE is Major

ULT faulty.
CESPW_OPPOSITE_RAI Remote alarm indication Major
CFCARD_FAILED The operation on the CF card fails. Major
CFCARD_FULL The CF card is full. Major
CFCARD_OFFLINE The CF card is offline. Major
CFCARD_W_R_DISABLE Writing/Reading the CF card is disabled. Major

D
CHCS Correctable cell errors Minor
CLK_LOCK_FAIL Clock locking fails Major
CLK_NO_TRACE_MODE The clock source is not in locked mode. Minor
COMMUN_FAIL Inter-board communication fails. Major


Severity
COM_EXTECC_FULL Excessive TCP connections between Major

automatically extended ECC NEs
CONFIG_NOSUPPORT Configuration is not supported. Major
CPU_BUSY The CPU usage is abnormally high. Major
DBMS_DELETE The databases are in the deletion state. Major
DBMS_ERROR Errors in the processing of system Critical

databases
DBMS_PROTECT_MODE System databases in protection mode Critical
DCNLINK_OVER There is an excessive number of DCN Major

links.
DCNSIZE_OVER Oversized DCN network Major
DDN_LFA The frame alignment signal of framed E1 Major

services is lost.
DOWN_E1_AIS Alarm indication of 2 Mbit/s downstream Minor

signals
DEVICE_AUTH_FAIL Anti-theft verification fails on a device. Major
DROPRATIO_OVER The number of lost packets due to port Minor

congestion crosses the threshold.
E1_LOC Loss of 2 Mbit/s clock in upstream signals Major
E1_LOS Loss of 2 Mbit/s line signals Minor
ELAN_SMAC_FLAPPING The source MAC address learned by an E- Major

LAN service flaps.
ENVHUM_SENSOR_FAIL The ambient humidity sensor of the Major

cabinet fails.
ENVTEMP_SENSOR_FAIL The ambient temperature sensor of the Major

cabinet fails.
ENVTEMP1_SENSOR_FAI The ambient temperature sensor 1 of the Major

L cabinet fails.
ENVTEMP2_SENSOR_FAI The ambient temperature sensor 2 of the Major

L cabinet fails.
ERPS_IN_PROTECTION Indicates that a node on the EPRS ring is Minor

faulty.
ETH_APS_LOST Loss of APS frames Minor


Severity
ETH_APS_PATH_MISMAT The working and protection paths of the Major

CH APS protection group differ between the
two ends.
ETH_APS_SWITCH_FAIL Protection switching failure Minor
ETH_APS_TYPE_MISMAT Protection scheme mismatch Major

CH
ETH_AUTO_LINK_DOWN Automatic link down of Ethernet port Minor
ETH_CFM_AIS A local MEP_AIS occurs. Major
ETH_CFM_LOC Loss of connectivity Major
ETH_CFM_MISMERGE Misconnection Major
ETH_CFM_RDI The maintenance association end point Minor

(MEP) fails to receive CCM packets.
ETH_CFM_UNEXPERI Error frames Minor
ETH_EFM_DF Discovery failure Major
ETH_EFM_EVENT Performance events at the opposite end Major
ETH_EFM_LOOPBACK A loopback occurs. Major
ETH_EFM_REMFAULT Faults occur at the opposite end. Critical
ETH_LINK_DOWN The connection on an Ethernet port is Critical

faulty.
ETH_LOS Loss of Ethernet port connection Critical
ETH_NO_FLOW No flow on the Ethernet port Major
ETH_PWR_SUPPLY_FAIL Power output failure of an Ethernet port Critical
ETHOAM_DISCOVER_FA Discovery failure is detected by point-to- Minor

IL point Ethernet OAM.
ETHOAM_RMT_CRIT_FA Severe faults are detected by point-to- Minor

ULT point Ethernet OAM at the remote end.
ETHOAM_RMT_LOOP A remote loopback is detected by point-to- Minor

point Ethernet OAM.
ETHOAM_RMT_SD Remote Ethernet performance degradation Minor

is detected by point-to-point Ethernet
OAM.
ETHOAM_SELF_LOOP An MAC port loopback is detected by Major

point-to-point Ethernet OAM.


Severity
ETHOAM_VCG_SELF_LO A VCTRUNK port loopback is detected Major

OP by point-to-point Ethernet OAM.
EX_ETHOAM_CC_LOS Loss of periodical continuity check Critical

packets
EX_ETHOAM_MPID_CNF Conflict of maintenance point IDs Major

LCT
EXT_SYNC_LOS Loss of external clock sources Critical
EXT_TIME_LOC Loss of external time sources Major
FAN_AGING Aged fans Minor
FAN_FAIL Failure of fan boards Major
FCS_ERR Frame check sequence (FCS) errors Critical
FDBSIZEALM_ELAN items listed in an E-LAN forwarding table Minor

are all used
FLOW_OVER excess data traffic received by Ethernet Minor

ports
FLOW_EXC_LCS The traffic exceeds the maximum capacity Minor

allowed by the license.
GSP_RSVP_NB_AUTH_ER An RSVP neighbor authentication error Major

R occurs.
GSP_RSVP_NB_DOWN An RSVP neighbor becomes unreachable. Major
GSP_TNNL_DOWN A tunnel is interrupted. Major
HARD_BAD Hardware faults Critical
HARD_ERR Minor hardware faults Minor
HARD_NONSUPPORT Board hardware does not support a certain Major

function.
HP_CROSSTR Threshold-crossing performance event of Minor

the higher order path
HP_LOM Loss of multiframes in the higher order Major

path
HP_RDI Higher order path remote defect indication Minor
HP_REI Higher order path remote error indication Warning
HP_SLM Higher order path signal label mismatch Minor
HP_TIM High order path trace identifier mismatch Minor


Severity
HP_UNEQ Unequipped higher order path Minor
HPAD_CROSSTR Adaptation performance threshold- Minor

crossing of the higher order path
IF_CABLE_OPEN IF cables are disconnected. Major
IF_INPWR_ABN The power supplied by an IF board to an Major

ODU is abnormal.
IF_MODE_UNSUPPORTE Preset IF working mode is not supported. Major

D
IMA_GROUP_LE_DOWN The IMA group at the local end fails. Major
IMA_GROUP_RE_DOWN The IMA group at the remote end fails. Major
IMA_TXCLK_MISMATCH The transmit clock modes at the two ends Minor

of the IMA group are different.
IN_PWR_ABN Abnormal input optical power Major
IN_PWR_HIGH Over high input optical power Critical
IN_PWR_LOW Over low input optical power Critical
INSUFFCNT_MEM_SPAC The memory file system space is Critical

E insufficient.
INSUFFCNT_FLSH_SPAC The flash file system space is insufficient. Critical

E
INTEMP_SENSOR_FAIL The air intake vent temperature sensor of Major

the cabinet fails.
ISIS_LSP_SEQ_EXCEED The number of LSP serial numbers Major

generated by the IS-IS exceeds the upper
threshold.
ISIS_SEQ_REACH_MAX The number of LSP serial numbers Critical

generated by the IS-IS reaches the
maximum.
ISISADJACENCYCHANG The status of an IS-IS neighbor changes. Major

E
J0_MM Trace identifier mismatch Minor
K1_K2_M K1 and K2 mismatch Minor
K2_M K2 mismatch Minor
KMC_KEY_SYNC_FAIL The KMC key synchronization fails. Critical
L3V_TRAP_THRE_EXCEE The number of private network route Major

D prefixes exceeds the threshold.


Severity
L3V_TRAP_VRF_DOWN All ports on a private network are down. Major
LAG_BWMM Bandwidth inconsistency in the LAG Major

group
LAG_DOWN The LAG is unavailable. Major
LAG_MEMBER_DOWN A member port of a link aggregation Minor

group (LAG) is unavailable.
LAG_PORT_FAIL A member port of a LAG fails. Minor
LAG_VC_PORT_FAIL A VCG port of an LAG fails. Minor
LAN_LOC Ethernet communication failure Major
LASER_CHECK_ERR An optical module check error occurs. Minor
LASER_CLOSED The laser is shut down. Major
LASER_MOD_ERR The type of the pluggable optical module Major

on the board does not match the type of
the optical interface.
LASER_MOD_ERR_EX The type of the pluggable optical module Major

on the board does not match the type of
LASER_MODULE_MISMA The type of the pluggable optical module Major

TCH on the board does not match the type of
LASER_SHUT The laser is shut down. Major
LCAS_FOPR LCAS protocol fails in the receive Major

direction.
LCAS_FOPT LCAS protocol fails in the transmit Major

direction.
LCAS_PLCR Loss of partial bandwidth in the LCAS Minor

receive direction
LCAS_PLCT Loss of partial bandwidth in the LCAS Minor

transmit direction
LCAS_TLCR Loss of total bandwidth in the LCAS Major

receive direction
LCAS_TLCT Loss of total bandwidth in the LCAS Major

transmit direction
LCD Loss of cell delimitation Major
LCS_DAYS_OF_GRACE The license file has expired but is still in Major

the grace period.


Severity
LCS_EXPIRED The license file has expired and its grace Critical
period has timed out.
LCS_FILE_NOT_EXIST An NE fails to detect the ESDP license Critical

file.
LCS_LIMITED The capacity of the configured services Major

exceeds the range permitted by the license
file.
LCS_TRIAL_PERIOD An NE is in the trial period. Major
LFA Out of frame state of E1 frames Major
LICENSE_LOST The NE fails to detect any license file. Major
LINK_ERR Faults occur in a data link. Critical
LMFA Out of frame state of E1 multiframes Major
LOCAL_FAULT A fault occurs at the alarmed Ethernet Minor

port.
LOOP_ALM A loopback occurs. Minor
LP_CROSSTR Performance threshold-crossing of the Minor

lower order path
LP_R_FIFO FIFO overflow on the receive side of the Minor

lower order path
LP_RDI Lower order path remote defect indication Minor
LP_RDI_VC12 VC-12 path remote defect indication Minor
LP_RDI_VC3 VC-3 path remote defect indication Minor
LP_REI Lower order path remote error indication Minor
LP_REI_VC12 VC-12 path remote error indication Minor
LP_REI_VC3 VC-3 path remote bit error indication Minor
LP_RFI Lower order path remote failure indication Minor
LP_SLM Lower order path signal label mismatch Minor
LP_SLM_VC12 VC-12 path signal label mismatch Minor
LP_SLM_VC3 VC-3 path signal label mismatch Minor
LP_T_FIFO FIFO overflow on the transmit side of the Minor

lower order path
LP_TIM Lower order path trace identifier mismatch Minor
LP_TIM_VC12 VC-12 path trace identifier mismatch Minor


Severity
LP_TIM_VC3 VC-3 path tracking identification Minor

mismatch
LP_UNEQ Unequipped lower order paths Minor
LP_UNEQ_VC12 Unequipped VC-12 paths Minor
LP_UNEQ_VC3 VC-3 path unequipped Minor
LPS_UNI_BI_M The switching mode is single-ended at one Minor

end and dual-ended at the other end.
LPT_CFG_CLOSEPORT The LPT closes the access port of the local Major
NE.
LPT_INEFFECT LPT function failed Major
LPT_RFI Link state pass-through function fails at Critical

the remote end.
LSR_BCM_ALM Laser bias current crossing the threshold Major
LSR_NO_FITED Laser not installed Critical
LSR_WILL_DIE Laser going to expire Critical
LTI Loss of clock synchronization source Major
MAC_EXT_EXC The number of bit errors at the MAC layer Major

crosses the threshold.
MAC_FCS_EXC The software detects that the number of bit Major

errors at the MAC layer crosses the
threshold.
MAC_FCS_SD Signal degrade bit errors at the MAC layer Major

cross the threshold.
MOD_COM_FAIL Module communication failure Critical
MOD_TYPE_MISMATCH Port module type mismatch Critical
MP_DELAY The group member delay Major
MP_DOWN MP group failure Major
MPLSLDPSESSIONDOWN Interruption of an LDP session Critical
MPLSLSP_TBL_LACK Deficiency of MPLS label resources Minor
MPLS_PW_AIS PW forward defect indication Major
MPLS_PW_BDI PW backward defect indication Minor
MPLS_PW_CSF MPLS PW Client Signal Fail Major


Severity
MPLS_PW_Excess Excessive trail termination source Warning

identifiers (TTSIs) are received on the
PW.
MPLS_PW_LCK The server layer (tunnel) of MPLS PW Major

locked indication
MPLS_PW_LOCK Administration locking of PW layer Major
MPLS_PW_LOCV Loss of PW connectivity Major
MPLS_PW_MISMATCH The trail termination source identifiers Major

(TTSIs) on the PW do not match with the
specified one.
MPLS_PW_MISMERGE The trail termination source identifiers Major

(TTSIs) are mismerged on the PW.
MPLS_PW_OAMFAIL OAM protocol negotiation failure Minor
MPLS_PW_RDI PW backward defect indication Minor
MPLS_PW_SD Signal degradation on the PW Major
MPLS_PW_SF Signal failure on the PW Major
MPLS_PW_UNEXPMEG The MEP receives a packet with correct Critical

MEG level but incorrect MEG ID.
MPLS_PW_UNEXPMEP The CCM information of a PW OAM Major

packet is incorrect.
MPLS_PW_UNEXPPER The PW does not receive a CCM packet in Major

the expected period.
MPLS_PW_UNKNOWN Unknown defects on the PW Major
MPLS_TUNNEL_AIS Tunnel forward defect indication Major
MPLS_TUNNEL_BDI Tunnel backward defect indication Minor
MPLS_TUNNEL_EXCESS Excessive trail termination source Warning

identifiers (TTSIs) are received on the
tunnel.
MPLS_TUNNEL_FDI Tunnel forward defect indication Minor
MPLS_TUNNEL_LOCK Administration locking of tunnel layer Minor
MPLS_TUNNEL_LOCV Loss of tunnel connectivity Major
MPLS_TUNNEL_MISMAT The trail termination source identifiers Major

CH (TTSIs) on the tunnel do not match with
the specified one.


Severity
MPLS_TUNNEL_MISMER The trail termination source identifiers Major

GE (TTSIs) are mismerged on the tunnel.
MPLS_TUNNEL_OAMFAI The OAM protocol negotiation between Minor

L the two ends of the tunnel fails.
MPLS_TUNNEL_RDI Tunnel backward defect indication Minor
MPLS_TUNNEL_SD Signal degradation on the tunnel Major
MPLS_TUNNEL_SF Signal failure on the tunnel Major
MPLS_TUNNEL_UNEXPM Unexpected MEG ID in the CCM packet Critical

EG
MPLS_TUNNEL_UNEXPM Unexpected MEP ID in the CCM packet Major

EP
MPLS_TUNNEL_UNEXPP Unexpected period of the CCM packet Major

ER
MPLS_TUNNEL_UNKNO Unknown defects on the tunnel Major

WN
MS_AIS Multiplex section alarm indication Major
MS_CROSSTR Multiplex section performance threshold- Minor

crossing
MS_RDI Multiplex section remote defect indication Minor
MS_REI Multiplex section remote error indication Warning
MSAD_CROSSTR Multiplex section adaptation performance Minor

threshold-crossing
MULTI_RPL_OWNER The ring network has multiple Minor

RPL_OWNER nodes.
MW_AM_TEST The IF port is in the AM testing state. Minor
MW_BER_EXC Excessive errors on radio links Minor
MW_BER_SD Signal degradation due to excessive errors Minor

on radio links
MW_CFG_MISMATCH Configuration mismatch on radio links Critical
MW_CONT_WAVE Continuous wave Minor
MW_E1_LOST Loss of E1 signals Major
MW_FEC_UNCOR Microwave frames have the errors that Minor

cannot be corrected by using the forward
error correction (FEC) technology.


Severity
MW_LIM Label mismatch on radio links Major
MW_LOF Loss of microwave frames Critical
MW_RDI Remote defect indication on radio links Minor
NEIP_CONFUSION IP address is conflict Major
NESF_LOST The NE software is lost. Critical
NESOFT_MM The software in the main area is different Major

from that in the standby area.
NO_BD_SOFT The board software is lost. Critical
NP1_MANUAL_STOP The N+1 protection protocol is stopped Minor

manually.
NP1_SW_FAIL The N+1 protection switching fails. Major
NP1_SW_INDI N+1 protection switching indication Major
NTP_SYNC_FAIL Synchronization with the NTP time fails. Minor
OCD Out of cell delimitation Major
ODC_BATTERY_CURREN Abnormal current of the storage battery Major

T_ABN
ODC_BATTERY_PWRDO The storage battery fails to supply power Major

WN for the equipment.
ODC_DOOR_OPEN The door of an outdoor cabinet is open. Critical
ODC_FAN_FAILED Fan failure Major
ODC_HUMI_ABN The relative humidity in the cabinet Minor

environment crosses the specified
threshold.
ODC_LOAD_PWRDOWN The secondary load is powered off. Major
ODC_MDL_ABN The power module is abnormal. Major
ODC_POWER_FAIL Exceptions occur in the AC input power Major

voltage.
ODC_SMOKE_OVER Smoke occurs in an outdoor cabinet. Critical
ODC_SURGE_PROTECTI The surge protection function of the Critical

ON_FAIL outdoor cabinet fails.
ODC_TEC_ALM The TEC air conditioning module in the Major

cabinet fails.


Severity
ODC_TEMP_ABN The ambient temperature of the cabinet or Minor

the temperature of the storage battery is
inappropriate.
ODC_WATER_ALM Water in the outdoor cabinet Critical
OSPFNBRSTATECHANGE The OSPF neighbor state changes. Major
OUT_PWR_ABN Abnormal output optical power Critical
OUT_PWR_HIGH Indicates that the output optical power is Major

excessively high.
OUT_PWR_LOW Indicates that the output optical power is Major

excessively low.
OUT1TEMP_SENSOR_FAI The air outlet temperature sensor of the Major

L cabinet fails.
OUT2TEMP_SENSOR_FAI The external recycling outlet temperature Major

L sensor of the cabinet fails.
PASSWORD_NEED_CHAN The default user password, WLAN Major

GE password, or AES MAC has not been
changed.
PATCH_BD_EXCLUDE Patch isolation Major
PATCH_BD_MATCH_FAIL Patch matching failure Major
PATCH_CHGSCC_NOTM Patch package mismatch due to system Major

ATCH control board replacement
PATCH_PKGERR Abnormal patch package Minor
PG_LINK_FAIL Links of the 1+1 protection group fail. Critical
PG_PRT_DEGRADED The working link or protection link of the Major

1+1 protection group is faulty.
PLA_CFG_MISMATCH Inconsistent PLA configurations Critical
PLA_DOWN PLA group is faulty Major
PLA_MEMBER_DOWN Member link of a PLA group is faulty Major
PLA_MEMBER_DOWN_E A member link of the PLA group is faulty. Minor

XT
PLA_PKT_ERR Packet reassembly fails in the receive Major

direction.
PORTMODE_MISMATCH The working mode of the remote FE port Minor

does not match that of the local FE port.


Severity
PORT_EXC_TRAFFIC The traffic is higher than the port Major

bandwidth threshold.
PORT_MODULE_OFFLIN The SFP module is offline. Major

E
POWER_ABNORMAL Power input alarm Major
POWER_ALM Power module alarm Major
PPP_LCP_FAIL LCP negotiation failure Major
PPP_NCP_FAIL NCP negotiation failure Major
PRO_PKT_FLOODING Flooding of protocol packets Major
PTP_SOURCE_SWITCH PTP time source switching Minor
PTP_TIMESTAMP_ABN PTP time stamp abnormality Major
PW_DROPPKT_EXC The number of lost packets in a PW Warning

crosses the threshold.
PW_NO_TRAFFIC The PW has no traffic. Critical
PWAPS_LOST Loss of APS frames Minor
PWAPS_PATH_MISMATC The working and protection paths of the Major

H APS protection group differ between the
two ends.
PWAPS_SWITCH_FAIL Protection switching failure Minor
PWAPS_TYPE_MISMATC Protection scheme mismatch Major

H
PW_APS_DEGRADED The PW APS protection group is Major

degraded.
PW_APS_OUTAGE The PW APS protection group is Major

unavailable.
PWD_ENCRYPT_RISK The user password encryption mode of an Major

NE has security risks.
PW_DOWN A PW is disconnected. Critical
R_LOC Loss of clock on the receive line side Critical
R_LOF Loss of frame on the receive line side Critical
R_LOS Loss of signal or loss of microwave frame Critical

on the receive line side
R_OOF The out-of-frame fault occurs on the Critical

receive line side.


Severity
RADIO_FADING_MARGI Radio fading margin is insufficient. Minor

N_INSUFF
RADIO_MUTE The radio transmitter is muted. Warning
RADIO_RSL_BEYONDTH Antennas are not aligned. Minor
RADIO_RSL_HIGH Over high radio receive signal level Critical
RADIO_RSL_LOW Over low radio receive signal level Critical
RADIO_TSL_HIGH Over high radio transmit signal level Critical
RADIO_TSL_LOW Over low radio transmit signal level Critical
RELAY_ALARM_CRITIC There are critical alarm inputs. Critical

AL
RELAY_ALARM_IGNORE There are warning inputs. Warning
RELAY_ALARM_MAJOR There are major alarm inputs. Major
RELAY_ALARM_MINOR There are minor alarm inputs. Minor
REMOTE_FAULT A fault occurs at a peer Ethernet port. Minor
RMFA Loss of multiframe alignment at the Minor

remote end
RPS_INDI Radio protection switching indication Major
RS_CROSSTR Regenerator section performance Minor

threshold-crossing
RT_TBL_LACK Routing table resources are insufficient. Minor
RTC_FAIL The real-time clock (RTC) of the system Major

control board fails.
S1_SYN_CHANGE Clock source switching in S1 mode Major
SYNC_FAIL Batch backup of SCC boards fails. Minor
SEC_RADIUS_FAIL RADIUS authentication fails. Major
SECU_ALM Security alarm Major
SLAVE_BAD A standby board is faulty. Warning
SOFTWARE_UNCOMMIT The board software is unauthorized. Major
SRV_SHUTDOWN_LD Ethernet services are interrupted. Major
SSL_CERT_DAMAGED A user-customized SSL certificate file is Critical

damaged.
SSL_CERT_NOENC Certificate file of SSL is not encrypted Major


Severity
SSL_CERT_TO_EXPIRE A customized SSL certificate file is about Critical

to expire.
STORAGE_FAIL A memory failure occurs. Critical
STORM_CUR_QUENUM_ The number of alarms on an NE is only Minor

OVER one less than the maximum length of the
alarm list.
SUBNET_RT_CONFLICT Subnetwork route conflict Minor
SWDL_ACTIVATED_TIME The commit operation is not performed Critical

OUT during software package loading.
SWDL_AUTOMATCH_IN The automatic match function is disabled. Minor

H
SWDL_CHGMNG_NOMAT The board software version and the Critical

CH version of the running software are
inconsistent.
SWDL_COMMIT_FAIL The submit operation fails. Minor
SWDL_INPROCESS The package diffusion is being performed Warning

on the NE.
SWDL_NEPKGCHECK Certain files in the package stored in flash Critical

memory are lost.
SWDL_PKG_NOBDSOFT The software package does not contain Minor

any board software.
SWDL_PKGVER_MM Software package version consistency Minor

check fails.
SWDL_ROLLBACK_FAIL The version rollback on an NE fails. Minor
SYN_BAD Synchronous source degradation Minor
SYNC_C_LOS Loss of synchronization clock sources Warning
SYNC_DISABLE Automatic synchronization on the system Minor

control board is disabled.
SYSLOG_COMM_FAIL The communication between the NE and Major

the syslog server fails.
T_ALOS Loss of analog signals at 2 Mbit/s Major

interfaces
T_LOC Loss of clock on the transmit line side Major
TEM_HA Too high laser temperature Major
TEM_LA Too low laser temperature Major


Severity
TEMP_ALARM Excessive board temperature Minor
TEMP_OVER Excessive board temperature Major
TF Laser transmission fails. Critical
THUNDERALM Surge protection fails. Minor
TIME_LOCK_FAIL Time locking fails. Major
TIME_NO_TRACE_MODE The high precision time of the NE is in the Minor

non-traced status.
TR_LOC Clock failure Major
TU_AIS TU alarm indication Major
TU_AIS_VC12 VC-12 path TU alarm indication Major
TU_AIS_VC3 TU of VC-3 level alarm indication Major
TU_LOP Loss of TU pointers Major
TU_LOP_VC12 Loss of TU pointers in VC-12 paths Major
TU_LOP_VC3 TU of VC-3 level loss of pointer Major
TUNNEL_APS_DEGRADE The tunnel protection group degrades. Major

D
TUNNEL_APS_OUTAGE The tunnel protection group is unavailable Major
UHCS Uncorrectable cell errors Minor
UP_E1_AIS Alarm indication of 2 Mbit/s upstream Minor

signals
USB_FILE_UNSEC The USB flash drive used by the NE is Major

insecure.
USB_PROCESS_FAIL Data restoration from a USB flash drive Minor

fails
V5_VCAIS Bits 5-7 in the V5 byte of a VC-12 path Major

are set to "1"s.
VC_AIS Alarm indication signal of the VC Critical

connection
VC_LOC Loss of VC continuity check Major
VC_RDI Remote defect indication of the VC Major

connection
VCAT_LOA Excessive virtual concatenation delay Critical


Severity
VCAT_LOM_VC12 Loss of multiframe of VC-12 path virtual Major

concatenation
VCAT_LOM_VC3 The virtually concatenated multiframes in Major

a VC-3 path are lost.
VCAT_SQM_VC12 SQ mismatch of VC-12 path virtual Major

concatenation
VCAT_SQM_VC3 SQ mismatch of VC-3 path virtual Major

concatenation
VOLT_LOS Loss of voltage Major
VP_AIS Alarm indication signal of the VP Critical

connection
VP_LOC Loss of VP continuity check Major
VP_RDI Remote defect indication of the VP Major

connection
W_R_FAIL Failure in reading and writing chip Major

registers
WRG_BD_TYPE Error board types Major
XPIC_LOS Loss of XPIC compensation signals Critical
A.2 Alarm List (Classified by Logical Boards)

This part lists the alarms that are reported by each board.
NOTE
The NE software consider a physical board as one or more logical boards when managing the physical board.
The NMS also considers a physical board as one or more logical boards when managing the physical board.
Table A-2 shows the logical boards corresponding to all physical boards
Table A-2 Mappings between the physical boards and logical boards
Physical Logical Board
Board
CSHN l CSHN in slot 15 + SL4D in slot 16 + EG2D in slot 17

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

l CSHNA in slot 20 + SL4D in slot 21 + EG4 in slot 22


Board
CSHNU l CSHNU in slot 15 + SL4D in slot 16 + EG4 in slot 17 + EX1 in slot

18
l CSHNU in slot 20 + SL4D in slot 21 + EG4 in slot 22 + EX1 in slot
23
AUX AUX in the same slot
IF1 IF1 in the same slot
IFU2 IFU2 in the same slot
IFX2 IFX2 in the same slot
ISU2 ISU2 in the same slot
ISX2 ISX2 in the same slot
ISV3 ISV3 in the same slot
ISM6 ISM6 in the same slot
SL1D SL1D in the same slot
SL1DA SL1DA in the same slot
EM6T EM6T in the same slot
EM6TA EM6TA in the same slot
EM6F EM6F in the same slot
EM6FA EM6FA in the same slot
EG4 EG4 in the same slot
EG4P EG4P in the same slot
EFP8 EFP8 in the same slot
EMS6 EMS6 in the same slot
EX1 EX1 in the same slot
SP3S SP3S in the same slot
SP3D SP3D in the same slot
ML1 ML1 in the same slot
MD1 MD1 in the same slot
CQ1 CQ1 in the same slot
PIU PIU in the same slot
FAN FAN in the same slot


Board
ODU ODU in the slot whose number is 50 plus the slot number for the IF
board that is connected to the ODU
A.2.1 AUX
l BD_STATUS
l HARD_BAD
l RELAY_ALARM_CRITICAL
l RELAY_ALARM_IGNORE
l RELAY_ALARM_MAJOR
l RELAY_ALARM_MINOR
l WRG_BD_TYPE
A.2.2 CQ1
l ALM_E1RAI l CES_RDI l LOOP_ALM l PPP_NCP_FAIL
l AU_AIS l CES_STRAYPKT_E l LP_RDI_VC12 l R_LOC
XC l LP_REI_VC12 l R_LOF
l AU_LOP
l CESPW_OPPOSITE_ l LP_RFI l R_LOS
l B1_EXC
ACFAULT
l B1_SD l LP_SLM_VC12 l R_OOF
l CESPW_OPPOSITE_
l B2_EXC RAI l LP_TIM_VC12 l TEM_HA
l HARD_BAD l LP_UNEQ_VC12 l TEM_LA

l B2_SD
l HP_RDI l LSR_BCM_ALM l TEMP_OVER
l B3_EXC
l HP_REI l LSR_NO_FITED l TF
l B3_SD
l HP_SLM l LSR_WILL_DIE l TR_LOC
l BD_STATUS
l HP_TIM l MP_DELAY l TU_AIS_VC12
l BIP_EXC
l HP_UNEQ l MP_DOWN l TU_LOP_VC12
l BIP_SD
l IN_PWR_ABN l MS_AIS l UP_E1_AIS
l BUS_ERR l MS_RDI l V5_VCAIS
l IN_PWR_HIGH
l CES_JTROVR_EXC l MS_REI l WRG_BD_TYPE
l IN_PWR_LOW
l CES_JTRUDR_EXC l OUT_PWR_ABN
l J0_MM
l CES_LOSPKT_EXC l PPP_LCP_FAIL
l LASER_MOD_ERR
l CES_MALPKT_EXC l LASER_SHUT
l CES_MISORDERPK l LFA
T_EXC
l LMFA

A.2.3 CSHN
l ACR_LOCK_FAIL l LCS_FILE_NOT_EX l MPLS_TUNNEL_UN l SECU_ALM
l APS_FAIL IST EXPMEP l SLAVE_BAD
l APS_INDI l LCS_LIMITED l MPLS_TUNNEL_UN l SOFTWARE_UNCO
l LCS_TRIAL_PERIO EXPPER MMIT
l APS_MANUAL_STO
P D l MPLS_TUNNEL_UN l SRV_SHUTDOWN_
l LICENSE_LOST KNOWN LD
l ARP_SPOOF
l LPS_UNI_BI_M l NEIP_CONFUSION l SSL_CERT_DAMAG
l BD_NOT_INSTALL
ED l NESF_LOST ED
l LPT_CFG_CLOSEP
l BD_STATUS ORT l NESOFT_MM l SSL_CERT_NOENC
l LTI l NP1_MANUAL_STO l STORM_CUR_QUE
l BIOS_STATUS
P NUM_OVER
l BOOTROM_BAD l MAC_EXT_EXC
l NP1_SW_FAIL l SUBNET_RT_CONF
l BRDCASTRATIO_O l MAC_FCS_EXC LICT
VER l NP1_SW_INDI
l MOD_COM_FAIL l SWDL_ACTIVATED
l BUS_ERR l NTP_SYNC_FAIL
l MPLS_PW_AIS _TIMEOUT
l CES_APS_INDI l PASSWORD_NEED_
l MPLS_PW_BDI l SWDL_AUTOMATC
CHANGE
l CES_APS_MANUAL l MPLS_PW_CSF H_INH
_STOP l PATCH_BD_EXCLU l SWDL_CHGMNG_N
l MPLS_PW_Excess DE
l CES_K1_K2_M OMATCH
l MPLS_PW_LCK l PATCH_BD_MATCH
l CES_K2_M l SWDL_COMMIT_F
l MPLS_PW_LOCK _FAIL AIL
l CFCARD_FAILED
l MPLS_PW_LOCV l PATCH_CHGSCC_N l SWDL_INPROCESS
l CFCARD_FULL OTMATCH
l MPLS_PW_MISMAT l SWDL_NEPKGCHE
l CFCARD_OFFLINE CH l PATCH_PKGERR CK
l CFCARD_W_R_DIS l MPLS_PW_MISMER l PG_LINK_FAIL l SWDL_PKG_NOBD
ABLED GE l PG_PRT_DEGRADE SOFT
l CLK_LOCK_FAIL D
l MPLS_PW_OAMFAI l SWDL_PKGVER_M
l CLK_NO_TRACE_ L l PLA_CFG_MISMAT M
MODE CH
l MPLS_PW_RDI l SWDL_ROLLBACK
l COM_EXTECC_FUL l PLA_DOWN _FAIL
l MPLS_PW_SD
L
l MPLS_PW_SF l PLA_MEMBER_DO l SYN_BAD
l COMMUN_FAIL WN
l MPLS_PW_UNEXP l SYNC_C_LOS
l DBMS_DELETE l PLA_PKT_ERR
MEG l SYNC_DISABLE
l DBMS_ERROR l PORT_EXC_TRAFFI l SYSLOG_COMM_F
l MPLS_PW_UNEXP
l DBMS_PROTECT_ MEP C AIL
MODE l POWER_ALM l TEMP_ALARM
l MPLS_PW_UNEXPP
l DCNLINK_OVER ER l PRO_PKT_FLOODI l TIME_LOCK_FAIL
l DCNSIZE_OVER l MPLS_PW_UNKNO NG l TIME_NO_TRACE_
l ELAN_SMAC_FLAP WN l PTP_SOURCE_SWI MODE
PING l MPLS_TUNNEL_AI TCH l TUNNEL_APS_DEG
l ETH_APS_LOST S l PTP_TIMESTAMP_ RADED
l ETH_APS_PATH_MI l MPLS_TUNNEL_BD ABN l TUNNEL_APS_OUT
SMATCH I l PW_DROPPKT_EXC AGE

l ETH_APS_SWITCH l MPLS_TUNNEL_Ex l PW_NO_TRAFFIC l IGSP_ENTRIES_EX

_FAIL cess l PWAPS_LOST C
l ETH_APS_TYPE_MI l MPLS_TUNNEL_FD l PWAPS_PATH_MIS l SSL_CERT_TO_EXP
SMATCH I MATCH IRE
l ETH_NO_FLOW l MPLS_TUNNEL_LO l PWAPS_SWITCH_F l ARP_MAC_MISMA
l EXT_SYNC_LOS CK AIL TCH
l EXT_TIME_LOC l MPLS_TUNNEL_LO l PWAPS_TYPE_MIS l INSUFFCNT_MEM_
CV MATCH SPACE
l FDBSIZEALM_ELA
N l MPLS_TUNNEL_MI l PW_APS_DEGRAD l INSUFFCNT_FLSH_
SMATCH ED SPACE
l FLOW_OVER
l MPLS_TUNNEL_MI l PW_APS_OUTAGE
l HARD_BAD SMERGE
l HARD_NONSUPPO l PWD_ENCRYPT_RI
l MPLS_TUNNEL_OA SK
RT MFAIL
l K1_K2_M l RPS_INDI
l MPLS_TUNNEL_RD
l K2_M I l RTC_FAIL
l KMC_KEY_SYNC_F l MPLS_TUNNEL_SD l S1_SYN_CHANGE
AIL l MPLS_TUNNEL_SF l SYNC_FAIL
l LAG_BWMM l MPLS_TUNNEL_UN l SEC_RADIUS_FAIL
l LAN_LOC EXPMEG
l LCS_DAYS_OF_GR
ACE
l LCS_EXPIRED

A.2.4 CSHNA
l ACR_LOCK_FAIL l LCS_DAYS_OF_GR l MPLS_TUNNEL_SD l RELAY_ALARM_MI
l APS_FAIL ACE l MPLS_TUNNEL_SF NOR
l APS_INDI l LCS_EXPIRED l MPLS_TUNNEL_UN l RPS_INDI
l APS_MANUAL_STO l LCS_FILE_NOT_EX EXPMEG l RTC_FAIL
P IST l MPLS_TUNNEL_UN l S1_SYN_CHANGE
l ARP_SPOOF l LCS_LIMITED EXPMEP l SYNC_FAIL
l BD_NOT_INSTALL l LCS_TRIAL_PERIO l MPLS_TUNNEL_UN l SEC_RADIUS_FAIL
ED D EXPPER
l SECU_ALM
l BD_STATUS l LICENSE_LOST l MPLS_TUNNEL_UN
l SLAVE_BAD
KNOWN
l BIOS_STATUS l LPS_UNI_BI_M l SOFTWARE_UNCO
l NEIP_CONFUSION
l BOOTROM_BAD l LPT_CFG_CLOSEP MMIT
l BRDCASTRATIO_O ORT l NESF_LOST l SRV_SHUTDOWN_
VER l LTI l NESOFT_MM LD
l BUS_ERR l MAC_EXT_EXC l NP1_MANUAL_STO l SSL_CERT_DAMAG
l CES_APS_INDI P ED
l MAC_FCS_EXC
l CES_APS_MANUAL l NP1_SW_FAIL l SSL_CERT_NOENC
l MOD_COM_FAIL
_STOP l NP1_SW_INDI l STORM_CUR_QUE
l MPLS_PW_AIS
l CES_K1_K2_M NUM_OVER
l NTP_SYNC_FAIL
l MPLS_PW_BDI l SUBNET_RT_CONF
l CES_K2_M l PASSWORD_NEED_
l MPLS_PW_CSF LICT
l CLK_LOCK_FAIL CHANGE
l MPLS_PW_Excess l SWDL_ACTIVATED
l CLK_NO_TRACE_ l PATCH_BD_EXCLU
_TIMEOUT
MODE l MPLS_PW_LCK DE
l SWDL_AUTOMATC
l COM_EXTECC_FUL l MPLS_PW_LOCK l PATCH_BD_MATCH
H_INH
L l MPLS_PW_LOCV _FAIL
l SWDL_CHGMNG_N
l COMMUN_FAIL l MPLS_PW_MISMAT l PATCH_CHGSCC_N OMATCH
l DBMS_DELETE CH OTMATCH
l SWDL_COMMIT_F
l DBMS_ERROR l MPLS_PW_MISMER l PATCH_PKGERR AIL
l DBMS_PROTECT_ GE l PG_LINK_FAIL l SWDL_INPROCESS
MODE l MPLS_PW_OAMFAI l PG_PRT_DEGRADE l SWDL_NEPKGCHE
l DCNLINK_OVER L D CK
l DCNSIZE_OVER l MPLS_PW_RDI l PLA_CFG_MISMAT l SWDL_PKG_NOBD
l MPLS_PW_SD CH SOFT
l DROPRATIO_OVER
l MPLS_PW_SF l PLA_DOWN l SWDL_PKGVER_M
l ELAN_SMAC_FLAP
PING l PLA_MEMBER_DO M
l MPLS_PW_UNEXP
MEG WN l SWDL_ROLLBACK
l ETH_APS_LOST
l PLA_PKT_ERR _FAIL
l ETH_APS_PATH_MI l MPLS_PW_UNEXP
SMATCH MEP l PORT_EXC_TRAFFI l SYN_BAD
l ETH_APS_SWITCH l MPLS_PW_UNEXPP C l SYNC_C_LOS
_FAIL ER l POWER_ALM l SYNC_DISABLE
l ETH_APS_TYPE_MI l MPLS_PW_UNKNO l PRO_PKT_FLOODI l SYSLOG_COMM_F
SMATCH WN NG AIL

l ETH_NO_FLOW l MPLS_TUNNEL_AI l PTP_SOURCE_SWI l TEMP_ALARM

l EXT_SYNC_LOS S TCH l TIME_LOCK_FAIL
l EXT_TIME_LOC l MPLS_TUNNEL_BD l PTP_TIMESTAMP_ l TIME_NO_TRACE_
I ABN MODE
l FDBSIZEALM_ELA
N l MPLS_TUNNEL_Ex l PW_APS_DEGRAD l TUNNEL_APS_DEG
cess ED RADED
l FLOW_OVER
l MPLS_TUNNEL_FD l PW_APS_OUTAGE l TUNNEL_APS_OUT
l HARD_BAD I l PW_DROPPKT_EXC AGE
l HARD_NONSUPPO l MPLS_TUNNEL_LO
RT l PW_NO_TRAFFIC l USB_FILE_UNSEC
CK
l K1_K2_M l PWAPS_LOST l USB_PROCESS_FAI
l MPLS_TUNNEL_LO L
l K2_M CV l PWAPS_PATH_MIS
MATCH l IGSP_ENTRIES_EX
l KMC_KEY_SYNC_F l MPLS_TUNNEL_MI C
AIL SMATCH l PWAPS_SWITCH_F
AIL l SSL_CERT_TO_EXP
l LAG_BWMM l MPLS_TUNNEL_MI IRE
SMERGE l PWAPS_TYPE_MIS
l LAN_LOC MATCH l ARP_MAC_MISMA
l MPLS_TUNNEL_OA TCH
MFAIL l PWD_ENCRYPT_RI
SK l DEVICE_AUTH_FAI
l MPLS_TUNNEL_RD L
I l RELAY_ALARM_C
RITICAL l INSUFFCNT_MEM_
l RELAY_ALARM_IG SPACE
NORE l INSUFFCNT_FLSH_
l RELAY_ALARM_M SPACE
AJOR l STORAGE_FAIL

A.2.5 CSHNU
l ACR_LOCK_FAIL l ISIS_LSP_SEQ_EXC l MPLS_TUNNEL_MI l PWAPS_SWITCH_F
l APS_FAIL EED SMATCH AIL
l APS_INDI l ISIS_SEQ_REACH_ l MPLS_TUNNEL_MI l PWAPS_TYPE_MIS
MAX SMERGE MATCH
l APS_MANUAL_STO
P l ISISADJACENCYC l MPLS_TUNNEL_OA l PWD_ENCRYPT_RI
HANGE MFAIL SK
l ARP_MAC_MISMA
TCH l K1_K2_M l MPLS_TUNNEL_RD l RELAY_ALARM_C
I RITICAL
l ARP_SPOOF l K2_M
l MPLS_TUNNEL_SD l RELAY_ALARM_IG
l BD_NOT_INSTALL l KMC_KEY_SYNC_F NORE
ED AIL l MPLS_TUNNEL_SF
l RELAY_ALARM_M
l BD_STATUS l L3V_TRAP_THRE_ l MPLS_TUNNEL_UN
AJOR
EXCEED EXPMEG
l BGPBACKTRANSIT l RELAY_ALARM_MI
ION l L3V_TRAP_VRF_D l MPLS_TUNNEL_UN
NOR
OWN EXPMEP
l BIOS_STATUS l RPS_INDI
l LAG_BWMM l MPLS_TUNNEL_UN
l BOOTROM_BAD l RT_TBL_LACK
EXPPER
l BRDCASTRATIO_O l LAN_LOC l RTC_FAIL
l MPLS_TUNNEL_UN
VER l LCS_DAYS_OF_GR l S1_SYN_CHANGE
KNOWN
l BUS_ERR ACE
l MPLSLDPSESSION l SEC_RADIUS_FAIL
l CES_APS_INDI l LCS_EXPIRED DOWN l SECU_ALM
l CES_APS_MANUAL l LCS_FILE_NOT_EX l MPLSLSP_TBL_LA l SLAVE_BAD
_STOP IST CK
l SOFTWARE_UNCO
l CES_K1_K2_M l LCS_LIMITED l NEIP_CONFUSION MMIT
l CES_K2_M l LCS_TRIAL_PERIO l NESF_LOST l SRV_SHUTDOWN_
l CLK_LOCK_FAIL D LD
l NESOFT_MM
l CLK_NO_TRACE_ l LICENSE_LOST l SSL_CERT_DAMAG
l NP1_MANUAL_STO
MODE l LPS_UNI_BI_M P ED
l COM_EXTECC_FUL l LPT_CFG_CLOSEP l NP1_SW_FAIL l SSL_CERT_NOENC
L ORT l SSL_CERT_TO_EXP
l NP1_SW_INDI
l COMMUN_FAIL l LTI IRE
l NTP_SYNC_FAIL
l DBMS_DELETE l STORAGE_FAIL
l MAC_EXT_EXC l OSPFNBRSTATECH
l DBMS_ERROR l STORM_CUR_QUE
l MAC_FCS_EXC ANGE
NUM_OVER
l DBMS_PROTECT_ l MPLS_PW_AIS l PASSWORD_NEED_
MODE l SUBNET_RT_CONF
CHANGE
l MPLS_PW_BDI LICT
l DCNLINK_OVER l PATCH_BD_EXCLU
l MPLS_PW_CSF l SWDL_ACTIVATED
l DCNSIZE_OVER DE
l MPLS_PW_Excess _TIMEOUT
l DEVICE_AUTH_FAI l PATCH_BD_MATCH
l SWDL_AUTOMATC
L l MPLS_PW_LCK _FAIL
H_INH
l DROPRATIO_OVER l MPLS_PW_LOCK l PATCH_CHGSCC_N l SWDL_CHGMNG_N
l ETH_APS_LOST l MPLS_PW_LOCV OTMATCH OMATCH
l ETH_APS_PATH_MI l MPLS_PW_MISMAT l PATCH_PKGERR l SWDL_COMMIT_F
SMATCH CH l PG_LINK_FAIL AIL

l ETH_APS_SWITCH l MPLS_PW_MISMER l PG_PRT_DEGRADE l SWDL_INPROCESS

_FAIL GE D l SWDL_NEPKGCHE
l ETH_APS_TYPE_MI l MPLS_PW_OAMFAI l PLA_CFG_MISMAT CK
SMATCH L CH
l SWDL_PKG_NOBD
l ETH_NO_FLOW l MPLS_PW_RDI l PLA_DOWN SOFT
l EXT_SYNC_LOS l MPLS_PW_SD l PLA_MEMBER_DO l SWDL_PKGVER_M
l EXT_TIME_LOC WN M
l MPLS_PW_SF
l FDBSIZEALM_ELA l PLA_MEMBER_DO l SWDL_ROLLBACK
l MPLS_PW_UNEXP WN_EXT
N _FAIL
MEG
l FLOW_OVER l PLA_PKT_ERR l SYN_BAD
l MPLS_PW_UNEXP
l GSP_RSVP_NB_AU l PORT_EXC_TRAFFI l SYNC_C_LOS
MEP
TH_ERR C
l MPLS_PW_UNEXPP l SYNC_DISABLE
l GSP_RSVP_NB_DO l POWER_ALM
ER l SYNC_FAIL
WN l PRO_PKT_FLOODI
l MPLS_PW_UNKNO NG l SYSLOG_COMM_F
l GSP_TNNL_DOWN WN AIL
l HARD_BAD l PTP_SOURCE_SWI
l MPLS_TUNNEL_AI TCH l TEMP_ALARM
l HARD_ERR S
l PTP_TIMESTAMP_ l TEMP_OVER
l HARD_NONSUPPO l MPLS_TUNNEL_BD ABN
RT l TIME_LOCK_FAIL
I
l PW_APS_DEGRAD l TIME_NO_TRACE_
l INSUFFCNT_FLSH_ l MPLS_TUNNEL_Ex ED
SPACE MODE
cess
l PW_APS_OUTAGE
l INSUFFCNT_MEM_ l TUNNEL_APS_DEG
l MPLS_TUNNEL_FD l PW_DOWN
SPACE RADED
I
l PW_DROPPKT_EXC l TUNNEL_APS_OUT
l MPLS_TUNNEL_LO
l PW_NO_TRAFFIC AGE
CK
l PWAPS_LOST l USB_FILE_UNSEC
l MPLS_TUNNEL_LO
CV l PWAPS_PATH_MIS l USB_PROCESS_FAI
MATCH L

A.2.6 EFP8
l ALM_GFP_dCSF l ETHOAM_DISCOV l LCAS_FOPR l LP_UNEQ_VC12
l ALM_GFP_dLFD ER_FAIL l LCAS_FOPT l LPT_RFI
l BD_STATUS l ETHOAM_RMT_CR l LCAS_PLCR l NO_BD_SOFT
IT_FAULT
l BIP_EXC l LCAS_PLCT l RMFA
l ETHOAM_RMT_LO
l BIP_SD OP l LCAS_TLCR l TEMP_ALARM
l COMMUN_FAIL l ETHOAM_RMT_SD l LCAS_TLCT l TU_AIS_VC12
l DOWN_E1_AIS l ETHOAM_SELF_LO l LFA l TU_LOP_VC12
l ETH_CFM_AIS OP l LMFA l VCAT_LOA
l ETH_CFM_LOC l ETHOAM_VCG_SE l LOOP_ALM l VCAT_LOM_VC12
l ETH_CFM_MISMER LF_LOOP l LP_RDI_VC12 l VCAT_SQM_VC12
GE l EX_ETHOAM_CC_L l LP_REI_VC12 l W_R_FAIL
l ETH_CFM_RDI OS
l LP_SLM_VC12 l WRG_BD_TYPE
l ETH_CFM_UNEXPE l EX_ETHOAM_MPI
D_CNFLCT l LP_TIM_VC12
RI
l ETH_LOS l FCS_ERR
l FLOW_OVER
l HARD_BAD
l LAG_PORT_FAIL
l LAG_VC_PORT_FAI
L

A.2.7 EG2D
l ARP_FAIL l ETH_EFM_DF l LAG_MEMBER_DO l OUT_PWR_ABN
l BD_STATUS l ETH_EFM_EVENT WN l PORT_EXC_TRAFFI
l BRDCASTRATIO_O l ETH_EFM_LOOPBA l LASER_MOD_ERR C
VER CK l LASER_SHUT l PORTMODE_MISM
l COMMUN_FAIL l ETH_EFM_REMFAU l LOOP_ALM ATCH
l DROPRATIO_OVER LT l LPT_CFG_CLOSEP l TEMP_ALARM
l ERPS_IN_PROTECT l ETH_LOS ORT l TF
ION l ETH_NO_FLOW l LSR_NO_FITED l WRG_BD_TYPE
l ETH_AUTO_LINK_ l ETHOAM_SELF_LO l LSR_WILL_DIE
DOWN OP l MAC_EXT_EXC
l ETH_CFM_AIS l FLOW_OVER l MAC_FCS_EXC
l ETH_CFM_LOC l HARD_BAD l MAC_FCS_SD
l ETH_CFM_MISMER l IN_PWR_ABN l MULTI_RPL_OWNE
GE l LAG_DOWN R
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI

A.2.8 EG4
l ARP_FAIL l ETH_EFM_REMFAU l LSR_BCM_ALM l TEM_HA (supported
l BD_STATUS LT l LSR_WILL_DIE only by logical EG4
l ETH_LOS boards)
l BRDCASTRATIO_O l MAC_EXT_EXC
VER l ETH_LINK_DOWN l TEM_LA (supported
l MAC_FCS_EXC only by logical EG4
l BUS_ERR l ETH_NO_FLOW l MAC_FCS_SD boards)
l DEVICE_AUTH_FAI l ETHOAM_SELF_LO l MULTI_RPL_OWNE l TEMP_ALARM
L OP R l TF
l DROPRATIO_OVER l FLOW_OVER l OUT_PWR_ABN l TR_LOC
l ERPS_IN_PROTECT l HARD_BAD l OUT_PWR_HIGH
ION l WRG_BD_TYPE
l HARD_ERR l OUT_PWR_LOW
l ETH_AUTO_LINK_ l IN_PWR_ABN
DOWN l PORT_EXC_TRAFFI
l IN_PWR_HIGH C
l ETH_CFM_AIS
l IN_PWR_LOW l PORT_MODULE_OF
l ETH_CFM_LOC FLINE
l LAG_DOWN
l ETH_CFM_MISMER l PORTMODE_MISM
GE l LAG_MEMBER_DO
WN ATCH
l ETH_CFM_RDI
l LASER_CHECK_ER
l ETH_CFM_UNEXPE R
RI
l LASER_MOD_ERR
l ETH_EFM_DF
l LASER_MODULE_
l ETH_EFM_EVENT MISMATCH
l ETH_EFM_LOOPBA l LASER_SHUT
CK
l LOOP_ALM
l LPT_CFG_CLOSEP
ORT
l LSR_NO_FITED

A.2.9 EG4P
l ARP_FAIL l ETH_EFM_DF l LAG_DOWN l MULTI_RPL_OWNE
l BD_STATUS l ETH_EFM_EVENT l LAG_MEMBER_DO R
l BRDCASTRATIO_O l ETH_EFM_LOOPBA WN l OUT_PWR_ABN
VER CK l LASER_MOD_ERR l PORT_EXC_TRAFFI
l BUS_ERR l ETH_EFM_REMFAU l LASER_SHUT C
l DEVICE_AUTH_FAI LT l LOOP_ALM l PORTMODE_MISM
L l ETH_LOS ATCH
l LPT_CFG_CLOSEP
l DROPRATIO_OVER l ETH_NO_FLOW ORT l TEMP_ALARM
l ERPS_IN_PROTECT l ETH_PWR_SUPPLY l LSR_NO_FITED l TF
ION _FAIL l LSR_WILL_DIE l TR_LOC
l ETH_AUTO_LINK_ l ETHOAM_SELF_LO l MAC_EXT_EXC l WRG_BD_TYPE
DOWN OP l HARD_ERR
l MAC_FCS_EXC
l ETH_CFM_AIS l FLOW_OVER
l MAC_FCS_SD
l ETH_CFM_LOC l HARD_BAD
l ETH_CFM_MISMER l IN_PWR_ABN
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
A.2.10 EM6T
l ARP_FAIL l ETH_CFM_MISMER l FLOW_OVER l PORT_EXC_TRAFFI
l BD_STATUS GE l HARD_BAD C
l ETH_CFM_RDI l PORTMODE_MISM
l BRDCASTRATIO_O l LAG_DOWN
l ETH_CFM_UNEXPE ATCH
VER l LAG_MEMBER_DO
RI l SLAVE_BAD
l BUS_ERR WN
l ETH_EFM_DF l TEMP_ALARM
l COMMUN_FAIL l LOOP_ALM
l ETH_EFM_EVENT l TR_LOC
l CPU_BUSY l LPT_CFG_CLOSEP
l ETH_EFM_LOOPBA ORT l WRG_BD_TYPE
l DROPRATIO_OVER CK
l ERPS_IN_PROTECT l MAC_EXT_EXC
l ETH_EFM_REMFAU
ION LT l MAC_FCS_EXC
l ETH_AUTO_LINK_ l ETH_LOS l MAC_FCS_SD
DOWN l MOD_COM_FAIL
l ETH_NO_FLOW
l ETH_CFM_AIS l ETHOAM_SELF_LO l MULTI_RPL_OWNE
l ETH_CFM_LOC OP R

A.2.11 EM6TA
l ARP_FAIL l ETH_CFM_MISMER l FLOW_OVER l PORT_EXC_TRAFFI
l BD_STATUS GE l HARD_BAD C
l ETH_CFM_RDI l PORTMODE_MISM
l BRDCASTRATIO_O l LAG_DOWN
l ETH_CFM_UNEXPE ATCH
VER l LAG_MEMBER_DO
RI l SLAVE_BAD
l BUS_ERR WN
l ETH_EFM_DF l TEMP_ALARM
l COMMUN_FAIL l LOOP_ALM
l ETH_EFM_EVENT l TR_LOC
l CPU_BUSY l LPT_CFG_CLOSEP
l ETH_EFM_LOOPBA ORT l WRG_BD_TYPE
l DROPRATIO_OVER CK
l ERPS_IN_PROTECT l MAC_EXT_EXC
l ETH_EFM_REMFAU
ION LT l MAC_FCS_EXC
l ETH_AUTO_LINK_ l ETH_LOS l MAC_FCS_SD
DOWN l MOD_COM_FAIL
l ETH_NO_FLOW
l ETH_CFM_AIS l ETHOAM_SELF_LO l MULTI_RPL_OWNE
l ETH_CFM_LOC OP R
A.2.12 EM6F
l ARP_FAIL l ETH_CFM_UNEXPE l LAG_MEMBER_DO l PORT_EXC_TRAFFI
l BD_STATUS RI WN C
l BRDCASTRATIO_O l ETH_EFM_DF l LASER_MOD_ERR l PORTMODE_MISM
VER ATCH
l ETH_EFM_EVENT l LASER_SHUT
l BUS_ERR l SLAVE_BAD
l ETH_EFM_LOOPBA l LOOP_ALM
l COMMUN_FAIL CK l TEM_LA
l LPT_CFG_CLOSEP
l CPU_BUSY l ETH_EFM_REMFAU ORT l TEM_HA
l DROPRATIO_OVER LT l LSR_NO_FITED l TEMP_ALARM
l ERPS_IN_PROTECT l ETH_LOS l TF
l LSR_WILL_DIE
ION l ETH_NO_FLOW l TR_LOC
l MAC_EXT_EXC
l ETH_AUTO_LINK_ l ETHOAM_SELF_LO l WRG_BD_TYPE
DOWN l MAC_FCS_EXC
OP
l ETH_CFM_AIS l MAC_FCS_SD
l FLOW_OVER
l ETH_CFM_LOC l MOD_COM_FAIL
l HARD_BAD
l ETH_CFM_MISMER l MULTI_RPL_OWNE
l IN_PWR_ABN R
GE
l LAG_DOWN l OUT_PWR_ABN
l ETH_CFM_RDI

A.2.13 EM6FA
l ARP_FAIL l ETH_CFM_UNEXPE l LAG_MEMBER_DO l PORT_EXC_TRAFFI
l BD_STATUS RI WN C
l BRDCASTRATIO_O l ETH_EFM_DF l LASER_MOD_ERR l PORTMODE_MISM
VER ATCH
l ETH_EFM_EVENT l LASER_SHUT
l BUS_ERR l SLAVE_BAD
l ETH_EFM_LOOPBA l LOOP_ALM
l COMMUN_FAIL CK l TEMP_ALARM
l LPT_CFG_CLOSEP
l CPU_BUSY l ETH_EFM_REMFAU ORT l TF
l DROPRATIO_OVER LT l LSR_NO_FITED l TR_LOC
l ERPS_IN_PROTECT l ETH_LOS l WRG_BD_TYPE
l LSR_WILL_DIE
ION l ETH_NO_FLOW l MAC_EXT_EXC
l ETH_AUTO_LINK_ l ETHOAM_SELF_LO
DOWN l MAC_FCS_EXC
OP
l ETH_CFM_AIS l MAC_FCS_SD
l FLOW_OVER
l ETH_CFM_LOC l MOD_COM_FAIL
l HARD_BAD
l ETH_CFM_MISMER l MULTI_RPL_OWNE
l IN_PWR_ABN R
GE
l LAG_DOWN l OUT_PWR_ABN
l ETH_CFM_RDI

A.2.14 EMS6
l ALM_GFP_dCSF l ETHOAM_RMT_LO l LCAS_TLCT l MULTI_RPL_OWNE
l ALM_GFP_dLFD OP l LINK_ERR R
l B3_EXC_VC3 l ETHOAM_RMT_SD l LOOP_ALM l NO_BD_SOFT
l B3_SD_VC3 l ETHOAM_SELF_LO l LP_RDI_VC12 l OUT_PWR_ABN
OP l PORT_MODULE_OF
l BD_STATUS l LP_RDI_VC3
l ETHOAM_VCG_SE FLINE
l BIP_EXC LF_LOOP l LP_REI_VC12
l TEMP_ALARM
l BIP_SD l EX_ETHOAM_CC_L l LP_REI_VC3
l TU_AIS_VC12
l BUS_ERR OS l LP_SLM_VC12
l TU_AIS_VC3
l COMMUN_FAIL l EX_ETHOAM_MPI l LP_SLM_VC3
D_CNFLCT l TU_LOP_VC12
l ETH_CFM_LOC l LP_TIM_VC12
l FCS_ERR l TU_LOP_VC3
l ETH_CFM_MISMER l LP_TIM_VC3
GE l FLOW_OVER l VCAT_LOA
l LP_UNEQ_VC12
l ETH_CFM_RDI l HARD_BAD l VCAT_LOM_VC12
l LP_UNEQ_VC3
l ETH_CFM_UNEXPE l IN_PWR_ABN l VCAT_LOM_VC3
l LPT_INEFFECT
RI l LAG_PORT_FAIL l VCAT_SQM_VC12
l LPT_RFI
l ETH_LOS l LAG_VC_PORT_FAI l VCAT_SQM_VC3
l MOD_TYPE_MISM
l ETHOAM_DISCOV L ATCH l WRG_BD_TYPE
ER_FAIL l LCAS_FOPR
l ETHOAM_RMT_CR l LCAS_FOPT
IT_FAULT
l LCAS_PLCR
l LCAS_PLCT
l LCAS_TLCR

A.2.15 EX1
l ARP_FAIL l ETH_EFM_EVENT l LAG_MEMBER_DO l MAC_FCS_SD
l BD_STATUS l ETH_EFM_LOOPBA WN l MULTI_RPL_OWNE
l BRDCASTRATIO_O CK l LASER_CHECK_ER R
VER l ETH_EFM_REMFAU R l OUT_PWR_ABN
l BUS_ERR LT l LASER_MOD_ERR l OUT_PWR_HIGH
l DROPRATIO_OVER l ETH_LINK_DOWN l LASER_MODULE_ l OUT_PWR_LOW
l ERPS_IN_PROTECT l ETH_LOS MISMATCH l PORT_EXC_TRAFFI
ION l ETH_NO_FLOW l LASER_SHUT C
l ETH_AUTO_LINK_ l ETHOAM_SELF_LO l LOCAL_FAULT l PORT_MODULE_OF
DOWN OP FLINE
l LOOP_ALM
l ETH_CFM_AIS l FLOW_OVER l REMOTE_FAULT
l LPT_CFG_CLOSEP
l ETH_CFM_LOC l HARD_BAD ORT l TEM_HA
l ETH_CFM_MISMER l IN_PWR_ABN l LSR_BCM_ALM l TEM_LA
GE l IN_PWR_HIGH l TEMP_ALARM
l LSR_NO_FITED
l ETH_CFM_RDI l IN_PWR_LOW l TF
l LSR_WILL_DIE
l ETH_CFM_UNEXPE l LAG_DOWN l WRG_BD_TYPE
RI l MAC_EXT_EXC
l ETH_EFM_DF l MAC_FCS_EXC
A.2.16 FAN
l BD_STATUS
l FAN_AGING
l FAN_FAIL
l POWER_ALM
l WRG_BD_TYPE

A.2.17 IF1
l AU_AIS l HP_LOM l MS_AIS l R_LOF
l AU_LOP l HP_RDI l MS_CROSSTR l R_LOS
l B1_EXC l HP_REI l MS_RDI l RS_CROSSTR
l B1_SD l HP_SLM l MS_REI l SLAVE_BAD
l B2_EXC l HP_TIM l MSAD_CROSSTR l T_LOC
l B2_SD l HP_UNEQ l MW_CONT_WAVE l TEMP_ALARM

l IF_CABLE_OPEN l VOLT_LOS
l B3_EXC l MW_FEC_UNCOR
l IF_MODE_UNSUPP l WRG_BD_TYPE
l B3_SD l MW_LIM
ORTED
l BD_STATUS l LCS_LIMITED l MW_LOF
l HARD_BAD l LICENSE_LOST l MW_RDI
l HP_CROSSTR l LOOP_ALM l R_LOC
A.2.18 IFU2
l AM_DOWNSHIFT l ETH_EFM_LOOPBA l LOOP_ALM l MW_LIM
l ARP_FAIL CK l LP_RDI l MW_LOF
l BD_STATUS l ETH_EFM_REMFAU l LP_REI l MW_RDI
LT
l BIP_EXC l LP_UNEQ l PORT_EXC_TRAFFI
l ETH_NO_FLOW C
l BIP_SD l MAC_EXT_EXC
l ETHOAM_SELF_LO l R_LOC
l BRDCASTRATIO_O OP l MAC_FCS_EXC
VER l MULTI_RPL_OWNE l R_LOF
l FLOW_OVER
l DROPRATIO_OVER R l SLAVE_BAD
l FLOW_EXC_LCS
l ERPS_IN_PROTECT l MW_BER_EXC l TEMP_ALARM
ION l HARD_BAD
l MW_BER_SD l TU_AIS
l ETH_CFM_AIS l IF_CABLE_OPEN
l MW_CFG_MISMAT l TU_LOP
l ETH_CFM_LOC l LAG_BWMM CH l VOLT_LOS
l ETH_CFM_MISMER l LAG_DOWN l MW_CONT_WAVE l WRG_BD_TYPE
GE l LAG_MEMBER_DO l MW_E1_LOST
WN l POWER_ALM
l ETH_CFM_RDI l MW_FEC_UNCOR
l ETH_CFM_UNEXPE l LCS_LIMITED
RI l LICENSE_LOST
l ETH_EFM_DF
l ETH_EFM_EVENT

A.2.19 IFX2
l AM_DOWNSHIFT l ETH_EFM_REMFAU l LP_REI l PORT_EXC_TRAFFI
l ARP_FAIL LT l LP_UNEQ C
l BD_STATUS l ETH_NO_FLOW l MAC_EXT_EXC l R_LOC
l BIP_EXC l ETHOAM_SELF_LO l MAC_FCS_EXC l R_LOF
OP l SLAVE_BAD
l BIP_SD l MULTI_RPL_OWNE
l FLOW_OVER R l TEMP_ALARM
l BRDCASTRATIO_O
VER l FLOW_EXC_LCS l MW_BER_EXC l TU_AIS
l DROPRATIO_OVER l HARD_BAD l MW_BER_SD l TU_LOP
l ERPS_IN_PROTECT l IF_CABLE_OPEN l MW_CFG_MISMAT l VOLT_LOS
ION l LAG_BWMM CH l WRG_BD_TYPE
l ETH_CFM_AIS l LAG_DOWN l MW_CONT_WAVE l XPIC_LOS
l ETH_CFM_LOC l LAG_MEMBER_DO l MW_E1_LOST l POWER_ALM
l ETH_CFM_MISMER WN l MW_FEC_UNCOR
GE l LCS_LIMITED l MW_LIM
l ETH_CFM_RDI l LICENSE_LOST l MW_LOF
l ETH_CFM_UNEXPE l LOOP_ALM l MW_RDI
RI l LP_RDI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK

A.2.20 ISM6
l BD_STATUS l ETH_CFM_UNEXPE l LAG_MEMBER_DO l MW_E1_LOST
l AM_DOWNSHIFT RI WN l MW_FEC_UNCOR
l ARP_FAIL l ETH_EFM_DF l LCS_LIMITED l MW_LIM
l AU_AIS l ETH_EFM_EVENT l LICENSE_LOST l MW_LOF
l AU_LOP l ETH_EFM_LOOPBA l LOOP_ALM l MW_RDI
CK
l B1_EXC l LP_RDI l PORT_EXC_TRAFFI
l ETH_EFM_REMFAU C
l B1_SD l LP_REI
LT
l B2_EXC l R_LOC
l ETH_NO_FLOW l LP_UNEQ
l B2_SD l R_LOF
l ETHOAM_SELF_LO l MAC_EXT_EXC
l B3_EXC l RS_CROSSTR
OP l MAC_FCS_EXC
l B3_SD l SLAVE_BAD
l FLOW_OVER l MS_AIS
l BIP_EXC l T_LOC
l HARD_BAD l MS_CROSSTR
l BIP_SD l TEMP_ALARM
l HARD_ERR l MS_RDI
l BRDCASTRATIO_O l TU_AIS
l HP_CROSSTR l MS_REI
VER l TU_LOP
l HP_LOM l MSAD_CROSSTR
l BUS_ERR l VOLT_LOS
l HP_RDI l MULTI_RPL_OWNE
l DROPRATIO_OVER l WRG_BD_TYPE
l HP_REI R
l ERPS_IN_PROTECT l XPIC_LOS
ION l HP_SLM l MW_AM_TEST
l DEVICE_AUTH_FAI
l ETH_CFM_AIS l HP_TIM l MW_BER_EXC L
l ETH_CFM_LOC l HP_UNEQ l MW_BER_SD l POWER_ALM
l ETH_CFM_MISMER l IF_CABLE_OPEN l MW_CFG_MISMAT
GE l LAG_BWMM CH
l ETH_CFM_RDI l LAG_DOWN l MW_CONT_WAVE

A.2.21 ISU2
l AM_DOWNSHIFT l ETH_CFM_UNEXPE l LAG_MEMBER_DO l MW_CFG_MISMAT
l ARP_FAIL RI WN CH
l AU_AIS l ETH_EFM_DF l LCS_LIMITED l MW_CONT_WAVE
l AU_LOP l ETH_EFM_EVENT l LICENSE_LOST l MW_E1_LOST
l B1_EXC l ETH_EFM_LOOPBA l LOOP_ALM l MW_FEC_UNCOR
CK l LP_RDI l MW_LIM
l B1_SD
l ETH_EFM_REMFAU l LP_REI l MW_LOF
l B2_EXC
LT
l B2_SD l LP_UNEQ l MW_RDI
l ETH_NO_FLOW
l B3_EXC l MAC_EXT_EXC l PORT_EXC_TRAFFI
l ETHOAM_SELF_LO C
l B3_SD l MAC_FCS_EXC
OP
l MS_AIS l R_LOC
l BD_STATUS l FLOW_OVER
l MS_CROSSTR l R_LOF
l BIP_EXC l FLOW_EXC_LCS
l MS_RDI l RS_CROSSTR
l BIP_SD l HARD_BAD
l MS_REI l SLAVE_BAD
l BRDCASTRATIO_O l HP_CROSSTR
VER l MSAD_CROSSTR l T_LOC
l HP_LOM
l BUS_ERR l MULTI_RPL_OWNE l TEMP_ALARM
l HP_RDI
l DROPRATIO_OVER R l TU_AIS
l HP_REI
l ERPS_IN_PROTECT l MW_AM_TEST l TU_LOP
ION l HP_SLM l MW_BER_EXC l VOLT_LOS
l ETH_CFM_AIS l HP_TIM l MW_BER_SD l WRG_BD_TYPE
l ETH_CFM_LOC l HP_UNEQ l POWER_ALM
l ETH_CFM_MISMER l IF_CABLE_OPEN
GE l LAG_BWMM
l ETH_CFM_RDI l LAG_DOWN

A.2.22 ISV3
l AM_DOWNSHIFT l ETH_EFM_EVENT l LP_REI l PORT_EXC_TRAFFI
l ARP_FAIL l ETH_EFM_LOOPBA l LP_UNEQ C
l AU_AIS CK l MAC_EXT_EXC l PASSWORD_NEED_
l ETH_EFM_REMFAU CHANGE
l AU_LOP l MAC_FCS_EXC
LT l R_LOC
l B1_EXC l MS_AIS
l ETH_NO_FLOW l R_LOF
l B1_SD l MS_CROSSTR
l ETHOAM_SELF_LO l RS_CROSSTR
l B2_EXC OP l MS_RDI
l SLAVE_BAD
l B2_SD l FLOW_OVER l MS_REI
l T_LOC
l B3_EXC l FLOW_EXC_LCS l MSAD_CROSSTR
l TEMP_ALARM
l B3_SD l HARD_BAD l MULTI_RPL_OWNE
R l TU_AIS
l BD_STATUS l HP_CROSSTR
l MW_AM_TEST l TU_LOP
l BIP_EXC l HP_LOM
l MW_BER_EXC l VOLT_LOS
l BIP_SD l HP_RDI
l MW_BER_SD l WRG_BD_TYPE
l BRDCASTRATIO_O l HP_REI
VER l MW_CFG_MISMAT l XPIC_LOS
l HP_SLM CH l AES_MAC_ERR
l BUS_ERR
l HP_TIM l MW_CONT_WAVE l DEVICE_AUTH_FAI
l DROPRATIO_OVER
l HP_UNEQ l MW_E1_LOST L
l ERPS_IN_PROTECT
ION l IF_CABLE_OPEN l MW_FEC_UNCOR l POWER_ALM
l ETH_CFM_AIS l LAG_BWMM l MW_LIM
l ETH_CFM_LOC l LAG_DOWN l MW_LOF
l ETH_CFM_MISMER l LAG_MEMBER_DO l MW_RDI
GE WN
l ETH_CFM_RDI l LCS_LIMITED
l ETH_CFM_UNEXPE l LICENSE_LOST
RI l LOOP_ALM
l ETH_EFM_DF l LP_RDI

A.2.23 ISX2
l AM_DOWNSHIFT l ETH_CFM_UNEXPE l LAG_MEMBER_DO l MW_CONT_WAVE
l ARP_FAIL RI WN l MW_E1_LOST
l AU_AIS l ETH_EFM_DF l LCS_LIMITED l MW_FEC_UNCOR
l AU_LOP l ETH_EFM_EVENT l LICENSE_LOST l MW_LIM
l B1_EXC l ETH_EFM_LOOPBA l LOOP_ALM l MW_LOF
CK
l B1_SD l LP_RDI l MW_RDI
l ETH_EFM_REMFAU
l B2_EXC l LP_REI l PORT_EXC_TRAFFI
LT
l B2_SD C
l ETH_NO_FLOW l LP_UNEQ
l B3_EXC l R_LOC
l ETHOAM_SELF_LO l MAC_EXT_EXC
l B3_SD l R_LOF
OP l MAC_FCS_EXC
l BD_STATUS l RS_CROSSTR
l FLOW_OVER l MS_AIS
l BIP_EXC l SLAVE_BAD
l FLOW_EXC_LCS l MS_CROSSTR
l BIP_SD l T_LOC
l HARD_BAD l MS_RDI
l BRDCASTRATIO_O l TEMP_ALARM
l HP_CROSSTR
VER l MS_REI l TU_AIS
l HP_LOM
l BUS_ERR l MSAD_CROSSTR l TU_LOP
l HP_RDI
l DROPRATIO_OVER l MULTI_RPL_OWNE l VOLT_LOS
l HP_REI R
l ERPS_IN_PROTECT l WRG_BD_TYPE
ION l HP_SLM l MW_AM_TEST
l XPIC_LOS
l ETH_CFM_AIS l HP_TIM l MW_BER_EXC l POWER_ALM
l ETH_CFM_LOC l HP_UNEQ l MW_BER_SD
l ETH_CFM_MISMER l IF_CABLE_OPEN
l MW_CFG_MISMAT
GE l LAG_BWMM CH
l ETH_CFM_RDI l LAG_DOWN

A.2.24 ML1/MD1
l ALM_E1RAI l CES_LOSPKT_EXC l LCD l TR_LOC
l ALM_IMA_LIF l CES_MALPKT_EXC l LFA l UHCS
l ALM_IMA_LODS l CES_MISORDERPK l LMFA l UP_E1_AIS
l ALM_IMA_RE_RX_ T_EXC l LOOP_ALM l VC_AIS
UNUSABLE l CES_RDI l MP_DELAY l VC_LOC
l ALM_IMA_RE_TX_ l CES_STRAYPKT_E l MP_DOWN l VC_RDI
UNUSABLE XC
l OCD l VP_AIS
l ALM_IMA_RFI l CESPW_OPPOSITE_
ACFAULT l POWER_ABNORM l VP_LOC
l ATMPW_UNKNOW AL
NCELL_EXC l CESPW_OPPOSITE_ l VP_RDI
RAI l PPP_LCP_FAIL l WRG_BD_TYPE
l BD_STATUS
l CHCS l PPP_NCP_FAIL
l BUS_ERR
l HARD_BAD l T_ALOS
l CES_ACR_LOCK_A
BN l IMA_GROUP_LE_D l TEMP_ALARM
l CES_JTROVR_EXC OWN
l CES_JTRUDR_EXC l IMA_GROUP_RE_D
OWN
l IMA_TXCLK_MISM
ATCH
A.2.25 ODU
l BD_STATUS l LOOP_ALM l RADIO_RSL_BEYO l RADIO_TSL_LOW
l CONFIG_NOSUPPO l POWER_ALM NDTH l TEMP_ALARM
RT l RADIO_FADING_M l RADIO_RSL_HIGH l WRG_BD_TYPE
l HARD_BAD ARGIN_INSUFF l RADIO_RSL_LOW l DEVICE_AUTH_FAI
l IF_INPWR_ABN l RADIO_MUTE l RADIO_TSL_HIGH L
A.2.26 PIU
l BD_STATUS
l HARD_BAD
l POWER_ABNORMAL
l TEMP_ALARM
l THUNDERALM
l WRG_BD_TYPE

A.2.27 PMU
l BAT1TEMP_SENSO l ENVTEMP2_SENSO l ODC_HUMI_ABN l ODC_SURGE_PROT
R_FAIL R_FAIL l ODC_LOAD_PWRD ECTION_FAIL
l BAT2TEMP_SENSO l HARD_BAD OWN l ODC_TEMP_ABN
R_FAIL l ODC_BATTERY_CU l ODC_MDL_ABN l ODC_WATER_ALM
l BD_STATUS RRENT_ABN l ODC_POWER_FAIL l WRG_BD_TYPE
l ENVHUM_SENSOR l ODC_BATTERY_PW l ODC_SMOKE_OVE
_FAIL RDOWN R
l ENVTEMP1_SENSO l ODC_DOOR_OPEN
R_FAIL
A.2.28 SL1D/SL1DA
l AU_AIS l HP_CROSSTR l LASER_CLOSE l MSAD_CROSS
l AU_LOP l HP_LOM D TR
l B1_EXC l HP_RDI l LASER_MOD_ l OUT_PWR_AB
ERR_EX N
l B1_SD l HP_REI
l LOOP_ALM l R_LOC
l B2_EXC l HP_SLM
l LSR_BCM_AL l R_LOF
l B2_SD l HP_TIM M l R_LOS
l B3_EXC l HP_UNEQ l LSR_NO_FITE l RS_CROSSTR
l B3_SD l IN_PWR_HIGH D
l T_LOC
l BD_STATUS l IN_PWR_LOW l LSR_WILL_DIE
l TF
l HARD_BAD l J0_MM l MS_AIS
l WRG_BD_TYP
l MS_CROSSTR E
l MS_RDI
l MS_REI

A.2.29 SL4D
l AU_AIS l HP_CROSSTR l LASER_CLOSE l MSAD_CROSS
l AU_LOP l HP_LOM D TR
l B1_EXC l HP_RDI l LASER_MOD_ l OUT_PWR_AB
ERR_EX N
l B1_SD l HP_REI
l LOOP_ALM l R_LOC
l B2_EXC l HP_SLM
l LSR_BCM_AL l R_LOF
l B2_SD l HP_TIM M l R_LOS
l B3_EXC l HP_UNEQ l LSR_NO_FITE l RS_CROSSTR
l B3_SD l IN_PWR_HIGH D
l T_LOC
l BD_STATUS l IN_PWR_LOW l LSR_WILL_DIE
l TEM_HA
l HARD_BAD l J0_MM l LASER_MODU
LE_MISMATCH l TEM_LA
l MS_AIS l TF
l MS_CROSSTR l WRG_BD_TYP
E
l MS_RDI
l MS_REI
A.2.30 SP3S/SP3D
l A_LOC l E1_LOS l LP_REI l TU_AIS
l BD_STATUS l HARD_BAD l LP_RFI l TU_LOP
l BIP_EXC l HPAD_CROSSTR l LP_SLM l UP_E1_AIS
l BIP_SD l LOOP_ALM l LP_T_FIFO l WRG_BD_TYPE
l DDN_LFA l LP_CROSSTR l LP_TIM
l DOWN_E1_AIS l LP_R_FIFO l LP_UNEQ
l E1_LOC l LP_RDI l T_ALOS
A.2.31 TCU
l BD_STATUS l INTEMP_SENSOR_ l ODC_SURGE_PROT l OUT1TEMP_SENSO
l BDTEMP_SENSOR_ FAIL ECTION_FAIL R_FAIL
FAIL l ODC_DOOR_OPEN l ODC_TEC_ALM l OUT2TEMP_SENSO
l ENVTEMP_SENSOR l ODC_FAN_FAILED l ODC_TEMP_ABN R_FAIL
_FAIL l ODC_SMOKE_OVE l ODC_WATER_ALM l WRG_BD_TYPE
l HARD_BAD R

A.3 Alarms and Handling Procedures

This chapter describes all the alarms on the OptiX RTN 980 in alphabetical order and how to
handle these alarms.
A.3.1 A_LOC
Description
The A_LOC is an alarm indicating that a clock signal is lost in the uplink bus.
Attribute
Alarm Severity Alarm Type

Major Equipment alarm
Parameters
None
Impact on the System

When the A_LOC alarm occurs, the services carried by the board are interrupted.
Possible Causes
Cause 1: A certain board is faulty.
Procedure
Step 1 Cause 1: A certain board is faulty.
1. Replace the board where the alarmed tributary unit is located.
----End
Related Information
None
A.3.2 ACR_LOCK_FAIL
Description
The ACR_LOCK_FAIL is an alarm indicating an IEEE 1588 ACR locking failure. This alarm
is reported when the NE works in 1588 ACR mode and the clock fails to be locked.

Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: indicates that the phase-locked loop (PLL) is in holdover or free-run
mode.
l 0x02: indicates that the Sync timestamp remains unchanged when the
Precision Time Protocol (PTP) clock is synchronized.
l 0x03: indicates that the PDV on the transport network exceeds the upper
threshold.
l 0x04: indicates that the ACR algorithm is in the quick lockout phase.

When this alarm occurs, the clock of the downstream NE is abnormal.
Possible Causes
l Cause 1: The frequency deviation of the clock source or the delay of the intermediate
network exceeds the upper threshold.
l Cause 2: The physical link where the traced clock source resides is faulty.
Procedure
Step 1 Handle the alarm according to the alarm parameters.
If... Then...
Parameter 1 = 0x01 Go to steps 3 and 4.
Parameter 1 = 0x02 Go to step 4.
Parameter 1 = 0x03 Go to step 3.
Parameter 1 = 0x04 No further action is required. Wait for a while (about 15 minutes).
Then, check whether the alarm is cleared.
Step 2 Check whether a hardware alarm such as HARD_BAD occurs on the SCC board or interface
board that accesses clocks. If yes, clear the alarm immediately.

Step 3 Query the PDV performance of the NE to determine whether the third-party network is
running properly. If not, ask the customer to optimize the PDV. For details about how to
query PDV performance of the local NE, see B.3.6 CURPOSITIVEPDV and
CURNEGATIVEPDV.
Step 4 Check the status of the master NE. If the master NE is abnormal, troubleshoot the abnormality
first.
----End
Related Information
None
A.3.3 AES_MAC_ERR
Description
The AES_MAC_ERR alarm indicates that the AES message authentication code (MAC) that
an NE receives from a service channel differs from the locally configured MAC (AES stands
for Advanced Encryption Standard).
Attribute
Critical Communication alarm
Parameters
None

If no protection scheme is configured, services on the channel are interrupted. If a protection
scheme is configured, this alarm triggers a switchover.
Possible Causes
l Cause 1: AES is enabled at only one end of the link or authentication codes are different
at the two ends of the link.
l Cause 2: Bit errors occur on the link.
Procedure
Step 1 Cause 1: AES is enabled at only one end of the link or authentication codes are different at the
two ends of the link.
1. Enable AES at both ends or configure the same authentication code at the two ends, refer
Setting AES-based Encryption at Air Interfaces.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 2.

Step 2 Cause 2: Bit errors occur on the link.

1. Clear the bit errors by following instructions in A.3.261 MW_BER_SD.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
A.3.4 ALM_E1RAI
Description
The ALM_E1RAI is an alarm indicating that the E1 link on the opposite NE reports alarms.
This alarm is reported on the local NE when the T_ALOS, UP_E1_AIS, DOWN_E1_AIS,
LFA, or LMFA alarm is reported on the opposite NE.
Attribute
Minor Communication alarm
Parameters
None

When this alarm occurs, the services on the local NE in the downstream direction are
interrupted.
Possible Causes
l Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA,
UP_E1_AIS, or DOWN_E1_AIS alarm.
Procedure
Step 1 Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA, UP_E1_AIS,
or DOWN_E1_AIS alarm.
Step 2 Handle these alarms first.
----End
Related Information
None

A.3.5 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that the generic framing procedure (GFP)
customer signal is lost. When the source end fails to receive the GFP customer signal, it sends
the management frame to the sink end. The ALM_GFP_dCSF alarm is reported when the sink
end receives the management frame.
Attribute
Parameters
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2, Parameter 3 Indicate the ID of the alarmed VCTRUNK. For example, 0x00
0x01 indicate that the alarm is reported in VCTRUNK 1.

When this alarm occurs, services are interrupted.
Possible Causes
l Cause 1: Timeslot binding is different at the source and sink VCTRUNKs.
l Cause 2: The radio link performance degrades.
l Cause 3: The alarmed board is faulty.
Procedure
Step 1 Cause 1: Timeslot binding is different at the source and sink VCTRUNKs.
1. Reconfigure the timeslot binding at the source and sink VCTRUNKs.
Step 2 Cause 2: The radio link performance degrades.

1. Troubleshoot the radio link.
Step 3 Cause 3: The alarmed board is faulty.

1. Replace the faulty board.
----End

Related Information
None
A.3.6 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the GFP frame is out of frame. This alarm
occurs when a board detects that the GFP frame is out of frame.
Attribute
Major Communication alarm
Parameters
Name Meaning
Parameter 1 Indicates the ID of the logical port, and the value is always 0x01.
Parameter 2, Indicate the ID of the alarmed VCTRUNK. For example, 0x00
Parameter 3 0x01 indicate that the alarm is reported in VCTRUNK 1.

Possible Causes
l Cause 1: Bit errors occur on certain links or certain links are faulty.
l Cause 2: When the LCAS is disabled, the source and the sink VCTRUNKs are
configured with different timeslots or different numbers of paths.
Procedure
Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.
1. Check whether the links where the service travels have errors or become faulty.
If... Then...
The links are faulty Rectify the fault.
The links are normal Replace the alarmed board.
Step 2 Cause 2: When the LCAS is disabled, the source and the sink VCTRUNKs are configured
with different timeslots or different numbers of paths.

1. Correct the configuration data. For details, see Configuring VCTRUNKs on an Ethernet
Board.
----End
Related Information
None
A.3.7 ALM_IMA_LIF
Description
The ALM_IMA_LIF is an alarm indicating that the IMA link is out of frame in the receive
direction. This alarm occurs when the frame alignment is lost on the IMA link in the receive
direction.
Attribute

Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the ATM Trunk ID.

l When this alarm occurs, the alarmed IMA link is unavailable. Therefore, the number of
available links in the IMA group decreases. If the bandwidth of the services configured
for the IMA group exceeds the total bandwidth of available IMA links, congestion
occurs on the IMA port, causing loss of cells.
l After this alarm is cleared, the affected IMA link becomes available.
Possible Causes
l Cause 1: The path that carries the IMA link reports the SDH alarms, such as R_LOS,
R_LOF, and MS_AIS.
l Cause 2: The IMA protocol negotiation fails between the two ends.
l Cause 3: The IMA link is faulty.

Procedure
Step 1 Cause 1: The path that carries the IMA link reports the SDH alarms, such as R_LOS,
R_LOF, and MS_AIS.
If... Then...
The path reports any SDH alarm Handle the relevant alarms first.
The path does not report any SDH alarm Go to Cause 2.
Step 2 Cause 2: The IMA protocol negotiation fails between the two ends.
1. Disable the IMA protocol at the two ends.
2. Check the IMA group configuration at the two ends and ensure that the configuration is
consistent.
3. Enable the IMA protocol at the two ends.
4. Then, check whether the alarm clears.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 3.
Step 3 Cause 3: The IMA link is faulty.

1. Replace the board. For details, see 6.6 Replacing the Smart E1 Interface Board.
----End
Related Information
Loss of frame alignment
A frame alignment word, provided at the physical layer, occupies the initial position of a
frame and defines the start of information field. An Out Of Frame (OOF) defect is declared
when the position of frame alignment word cannot be determined in the input bit stream.
A.3.8 ALM_IMA_LODS
Description
The ALM_IMA_LODS is an alarm indicating the differential delay on the IMA link crosses
the threshold. This alarm occurs when the maximum differential delay on the IMA link
exceeds the preset value.
Attribute
Parameters


Name Meaning

The IMA links are unavailable.
Possible Causes
l Cause 1: The maximum differential delay is configured incorrectly.
l Cause 2: Within one IMA group, the transmission distances of member links have too
large gaps.
Procedure
Step 1 Cause 1: The maximum differential delay is configured incorrectly.
1. Change the maximum differential delay to a greater value. For details, see Modifying
CES Service Parameters.
Step 2 Cause 2: Within one IMA group, the transmission distances of member links have too large
gaps.
1. Use the meter to measure the transmission time on E1 links. If the transmission time on
different links has a gap larger than 25 ms (default value), adjust the IMA links or delete
the member link with over long transmission time from the IMA group.
----End
Related Information
Differential delay
Differential delay refers to the service delay difference between E1 links.
A.3.9 ALM_IMA_RE_RX_UNUSABLE
Description
The ALM_IMA_RE_RX_UNUSABLE is an alarm indicating that the IMA link on the
opposite NE fails in the receive direction.
Attribute
Parameters


Name Meaning

Possible Causes
R_LOF, and MS_AIS.
Procedure
R_LOF, and MS_AIS.
If... Then...
consistent.
If... Then...

----End

Related Information
None
A.3.10 ALM_IMA_RE_TX_UNUSABLE
Description
The ALM_IMA_RE_TX_UNUSABLE is an alarm indicating that the IMA link on the
opposite NE fails in the transmit direction.
Attribute
Parameters
Name Meaning

Possible Causes
R_LOF, and MS_AIS.
Procedure
R_LOF, and MS_AIS.
If... Then...

If... Then...
consistent.
If... Then...

----End
Related Information
None
A.3.11 ALM_IMA_RFI
Description
The ALM_IMA_RFI is an alarm indicating that the IMA link on the opposite NE is out of
frame (OOF) in the receive direction. This alarm occurs when the frame alignment is lost on
the IMA link of the opposite NE and the opposite NE notifies the local NE of its OOF state.
Attribute

Parameters
Name Meaning


Possible Causes
R_LOF, and MS_AIS.
Procedure
R_LOF, and MS_AIS.
If... Then...
consistent.
If... Then...

----End
Related Information
Frame alignment loss
A frame alignment word, provided at the physical layer, occupies the initial position of a
frame and defines the start of information field. An Out Of Frame (OOF) defect is declared
when the position of frame alignment word cannot be determined in the input bit stream.

A.3.12 AM_DOWNSHIFT
Description
The AM_DOWNSHIFT alarm indicates the downshift of the AM scheme. This alarm occurs
after the AM mode is downshifted from the highest-order modulation scheme to the lower-
order modulation scheme. After the AM mode is upshifted from the lower-order modulation
scheme to the highest-order modulation scheme, this alarm is cleared.
Figure A-1 shows the process of reporting an AM_DOWNSHIFT alarm. To be specific, upon
detecting that the signal-to-noise ratio (SNR) deteriorates, the receive end transmits an AM
shift indication signal to the transmit end; upon receiving the signal, the transmit end
downshifts the AM mode and reports an AM_DOWNSHIFT alarm, and the receive end also
downshifts the AM mode but does not report any AM_DOWNSHIFT alarm.
NOTE
AM mode shifts in the two microwave directions are independent of each other.
Figure A-1 Process of reporting an AM_DOWNSHIFT alarm

NE reporting the
AM_DOWNSHIFT alarm
4 1
IF board IF board
3 2
Transmit end Receive end
③ Receives the AM shift instruction signals. ① Detects an SNR decrease.

④ Downshifts the modulation scheme and ② Transmits AM shift instruction signals
reports an AM_DOWNSHIFT alarm. to the peer NE.
Attribute
Parameters
None

When the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.
Possible Causes
l Cause 1: The external factors (for example, the climate) cause the degradation of the
working channels.

l Cause 2: There are interferences around the working channels.

l Cause 3: The ODU at the transmit end has abnormal transmit power.
l Cause 4: The ODU at the receive end has abnormal receive power.
Procedure
Step 1 Cause 1: The external factors (for example, the climate) cause the degradation of the working
channels.
1. When the external factors (for example, the climate) cause the degradation of the
working channels, the downshift of the AM scheme is normal. Hence, no measures
should be taken to handle the alarm.
Step 2 Cause 2: There are interferences around the working channels.

1. Eliminate the interferences around the working channels.
Step 3 Cause 3: The ODU at the transmit end has abnormal transmit power.
1. Use the NMS to check whether the transmit power of the ODU at the transmit end is
normal. For details on troubleshooting at the transmit end, see Troubleshooting
Microwave Links.
Step 4 Cause 4: The ODU at the receive end has abnormal receive power.
1. Use the NMS to check whether the receive power of the ODU at the receive end is
normal. For details on troubleshooting at the receive end, see Troubleshooting
Microwave Links.
----End
Related Information
None
A.3.13 APS_FAIL
Description
The APS_FAIL is an alarm indicating that the MS protection switching fails.
Attribute

Parameters

Name Meaning
Parameter 1 Indicates the type of the protection group.
l 0x01: linear MS protection

l 0x02: ring MS protection
Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates
that the alarm is reported by protection group 1.

When the APS_FAIL alarm occurs, the services cannot be switched. If the current paths are
unavailable, the services are interrupted.
Possible Causes
l Cause 1: The parameters of the MSP protocol are set incorrectly.
l Cause 2: The parameters of the MSP protocol are lost.
Procedure
Step 1 Cause 1: The parameters of the MSP protocol are set incorrectly.
1. Check whether the parameters of the MSP protocol are set correctly.
If... Then...
The parameters are set incorrectly Set the parameters correctly.
The parameters are set correctly Go to the next step.
Step 2 Cause 2: The parameters of the MSP protocol are lost.

1. Check whether the MSP protocol is normal on the network.
2. Check whether the MSP protocol is normal on the network. For details, see Enabling/
Disabling the linear MSP protocol or Enabling/Disabling the ring MSP protocol.
If... Then...
The alarm is cleared after the protocol is End the alarm handling.
restarted
The alarm persists after the protocol is Contact Huawei engineers to handle
restarted the alarm.
----End
Related Information
None

A.3.14 APS_INDI
Description
The APS_INDI alarm indicates that MS protection switching occurs.
Attribute
Parameters
Name Meaning
l 0x01: linear MS protection

l 0x02: ring MS protection

During the switching (≤ 50 ms), services are interrupted. After the switching is complete, the
services are restored to normal. In the case of 1:N MS protection, after the switching starts
and before the switching is complete, the extra services are interrupted.
Possible Causes
Cause 1: MS protection switching occurs.
Procedure
Step 1 Cause 1: MS protection switching occurs.
1. Query the linear MSP group or query the ring MSP group.
2. Check whether the MSP protocol is in the manual switching state, forced switching state,
or locked switching state. If yes, release the switching and check whether the alarm is
cleared.
3. Check whether the MSP protocol is in the automatic switching state. Do as follows:
a. Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that the
equipment reports. After the alarms are cleared, wait until the MSP protocol is
changed from the automatic switching state to the normal state. Then, check
whether the APS_INDI alarm is cleared.

b. Check whether the service board configured with the MSP protocol is faulty. If yes,
replace the faulty board and then check whether the APS_INDI alarm is cleared.
c. Check whether the currently working system control and cross-connect board is
faulty. If the currently working system control and cross-connect board is faulty and
a protection system control and cross-connect board is available, switch the service
to the protection system control and cross-connect board and replace the faulty
system control and cross-connect board. Then, check whether the APS_INDI
alarm is cleared.
----End
Related Information
This alarm is also reported upon a packet-based linear MSP switching. For querying the
packet-based Linear MSP group, refer toQuerying the Status of a Packet-based Linear MSP
Group.
A.3.15 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped
manually.
Attribute
Minor Processing alarm
Parameters
Name Meaning
l 0x01: linear MS protection.

l 0x02: ring MS protection.

When the APS_MANUAL_STOP alarm occurs, the MSP protocol may fail and therefore the
protection switching may fail.

Possible Causes
Cause 1: The MSP protocol is stopped manually.
Procedure
Step 1 Cause 1: The MSP protocol is stopped manually.
1. Enable/Disable the linear MSP protocol or Enable/Disable the ring MSP protocol.
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For enabling/disabling the
packet linear MSP protocol, refer toEnabling/Disabling the Linear MSP Protocol.
A.3.16 ARP_FAIL
Description
The ARP_FAIL alarm indicates that an Ethernet port fails to learn the MAC address of the
remote end using the ARP.
Attribute
Parameters
Name Meaning
Parameters 1 and 2 Indicate the VLAN ID of a VLAN subinterface. The parameters take
the fixed value of 0xfff for a non-VLAN sub-interface.
Parameters 3-6 Indicate the next-hop IP address.

When this alarm occurs, services on the interface are interrupted.
Possible Causes
l Cause 1: IP addresses of ports at both ends are not in the same network segment, or the
ports are not configured with IP addresses.
l Cause 2: A physical loop exists.

Procedure
Step 1 Cause 1: IP addresses of ports at both ends are not in the same network segment, or the ports
are not configured with IP addresses.
1. Check whether the interconnected ports at both ends are configured with IP addresses. If
no, configure IP addresses according to the network plan.
2. Check whether IP addresses of the ports at both ends are in the same network segment. If
no, reconfigure IP addresses according to the network plan.
Step 2 Cause 2: A physical loop exists.

1. Check the physical connections between NEs to release the physical loop.
----End
Related Information
None
A.3.17 ARP_MAC_MISMATCH
Description
The ARP_MAC_MISMATCH alarm indicates that the MAC address in a user-configured
static Address Resolution Protocol (ARP) entry is inconsistent with the MAC address of the
peer port.
Attribute
Parameters
None

Services may be unavailable.
Possible Causes
l Cause 1: The MAC address configuration is incorrect.
l Cause 2: The peer board has been replaced.
Procedure
Step 1 Change the MAC address in the static ARP entry to the MAC address of the peer port.
----End

Related Information
None
A.3.18 ARP_SPOOF
Description
The ARP_SPOOF is an alarm indicating an ARP spoofing attack. This alarm is reported when
the number of ARP spoofing attacks on an NE exceeds the alarm threshold within 1 minute
and is cleared when the NE does not suffer any ARP spoofing attack within 1 minute.
Attribute
Major Security alarm
Parameters
Name Meaning
Parameter 1, parameter 2 Indicates the slot number.
Parameter 3 Indicates the subboard number.
Parameter 4, parameter 5 Indicates the port number.

If an ARP_SPOOF alarm is generated, the system impact from the associated fault could
include:
l A large number of CPU resources are occupied. As a result, the system is unstable and
the protocol status jitters.
l Normal ARP protocol packets are lost. As a result, ARP protocol entries are refreshed
and packet loss may occur.
Possible Causes
The possible causes of the ARP_SPOOF alarm include:
The number of gratuitous ARP packets and the number of ARP reply packets received per
minute exceed the thresholds for the same IP address in the ARP protocol entries. The MAC
address of the ARP packet is different from that of the current ARP protocol entry.

Procedure
Step 1 Check the ARP_SPOOF alarm on the NMS. Query the attacker list.
Step 2 Find the host of the attacker based on the MAC address of the attacker. Disconnect the host
from the network to eliminate the attack source.
Step 3 Check whether the alarm is cleared. If it persists, contact Huawei engineers.
----End
Related Information
None
A.3.19 ATMPW_UNKNOWNCELL_EXC
Description
The ATMPW_UNKNOWNCELL_EXC is an alarm indicating that the number of unknown
cells exceeds the specified threshold in a time unit. This alarm occurs when the board detects
that, within a period (2.5s), the number of unknown cells crosses the specified threshold.
Attribute
Parameters
None

An unknown cell is discarded once it is detected. As a result, the packet loss rate increases
and services are affected.
Possible Causes
l Cause 1: PW control words mismatch.
l Cause 2: PW types mismatch.
l Cause 3: Fragments are received on the network side.
Procedure
Step 1 Check whether the configuration at the two ends of the PW is consistent. If not, modify the
configuration.
Step 2 Check whether connections are correct. If not, reconnect fibers or reconfigure connections.
----End

Related Information
None
A.3.20 AU_AIS
Description
The AU_AIS is an alarm indicating the administrative unit (AU). This alarm occurs when the
board detects the AU pointer of all 1s for three consecutive frames.
Attribute
Parameters
None

When the AU_AIS alarm occurs, the service in the alarmed AU-4 path is interrupted. If the
services are configured with protection, protection switching may be triggered.
Possible Causes
l Cause 1: The opposite NE inserts the AU_AIS alarm.
l Cause 2: The transmit unit of the opposite NE is faulty.
l Cause 3: The receive unit of the local NE is faulty.
Procedure
Step 1 Cause 1: The opposite NE inserts the AU_AIS alarm.
If... Then...
The alarm that triggers the AU_AIS insertion occurs Clear the alarm immediately.
No such alarms that trigger the AU_AIS insertion occur Go to Cause 2.
Step 2 Cause 2: The transmit unit of the opposite NE is faulty.

1. Replace the line board at the opposite end
If... Then...
The alarm is cleared after replacement The fault is rectified. End the alarm
handling.
The alarm persists after replacement Go to the next step.
2. Replace the system control, cross-connect, and timing board at the opposite end.

Step 3 Cause 3: The receive unit of the local NE is faulty.

1. Replace the alarmed board.
----End
Related Information
None
A.3.21 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm occurs when a
board detects the AU pointer of invalid values or with the NDF for eight consecutive frames.
Attribute
Parameters
None

When the AU_LOP alarm occurs, the service in the alarmed AU-4 path is interrupted. If the
services are configured with protection, protection switching may be triggered.
Possible Causes
l Cause 1: The transmit unit of the opposite NE is faulty.
Procedure
Step 1 Cause 1: The transmit unit of the opposite NE is faulty.
1. Replace the line board at the opposite end.
If... Then...
The alarm is cleared after replacement The fault is rectified. End the alarm
handling.
----End

Related Information
None
A.3.22 B1_EXC
Description
The B1_EXC is an alarm indicating that the B1 errors (in the regenerator section) exceed the
threshold. This alarm occurs when the board detects that the B1 errors exceed the preset
B1_EXC alarm threshold (10-3 by default).
An IF board that works in PDH mode may also report this alarm. This alarm is detected by
using the self-defined overhead byte B1 in PDH microwave frames.
Attribute
Minor Service alarm
Parameters
None

When the B1_EXC alarm occurs, the services on the port are interrupted.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
l Cause 3: The network clock quality degrades.
l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
l Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over low Replace the SFP on the
opposite NE.

If... Then...
The transmit power of the opposite NE is normal, but The fiber is faulty. Go to the
the receive power of the local NE is close to the value next step.
(for example, within ±3 dB) of the receiver sensitivity.
2. Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel.
If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step.
The errors do not vary with the change of Ensure that the board is normal.
the fiber.
3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out of the equipment room are pressed,
and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber
connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or
RPS_INDI alarm is reported. If yes, clear the alarm.
Step 3 Cause 3: The network clock quality degrades.
1. Check the network clock status of the alarmed NE.
If... Then...
The clock source of the local NE The clock may become asynchronous and B1
is different from the clock source errors may occur. Reconfigure the clock source,
of the opposite NE and ensure that the clock is synchronized on the
local NE and opposite NE.
The clock of the local NE and the This may cause errors and even service
clock of the opposite NE form a interruption. In this case, reconfigure the clock
timing loop source and release the timing loop.
Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
1. The board of the SDH line unit on the local NE is faulty. Loop back the optical interfaces
of the NE by using a fiber jumper to locate the fault.
If... Then...
The fault is not rectified after the Replace the board where the alarmed line
optical interfaces are looped back unit is located on the local NE.
The fault is rectified after the optical Replace the board where the alarmed line
interfaces are looped back unit is located on the opposite NE.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).
1. Perform an inloop for the multiplexing interface of the IF board on the local NE.

If... Then...
The fault is not rectified after the Replace the alarmed IF board on
multiplexing interface is looped back the local NE.
The fault is rectified after the multiplexing Replace the alarmed IF board on
interface is looped back the opposite NE.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
Handle the errors of TDM services.
A.3.23 B1_SD
Description
The B1_SD is an alarm indicating that the signal degrades due to the excessive B1 errors (in
the regenerator section). This alarm occurs when the board detects that the B1 errors exceed
the preset B1_SD alarm threshold (10-6 by default) but do not reach the preset B1_EXC alarm
threshold (10-3 by default).
An IF board that works in PDH mode may also report this alarm. This alarm is detected by
using the self-defined overhead byte B1 in PDH microwave frames.
Attribute

Minor Service alarm
Parameters
None

When the B1_SD alarm occurs, the service performance on the port degrades.
Possible Causes
interface board).

Procedure
board).
If... Then...
opposite NE.
(for example, within ±3 dB) of the receiver sensitivity
channel.
If... Then...
the fiber
connector.
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is
generated. If yes, clear the alarm.
If... Then...
The clock source of the local NE The clock may become asynchronous and errors
is different from the clock source may occur. Reconfigure the clock source, and
of the opposite NE ensure that the clock is synchronized on the local
NE and opposite NE.
1. The SDH optical line board of the local NE is faulty. Loop back the optical interfaces of
the NE by using a fiber jumper to locate the fault.

If... Then...
The fault is rectified after the optical Replace the board where the line unit is
interfaces are looped back located on the opposite NE.
If... Then...
----End
Related Information
A.3.24 B2_EXC
Description
The B2_EXC is an alarm indicating that the B2 errors (in the multiplex section) exceed the
threshold. This alarm occurs when the board detects that the number of B2 errors exceeds the
preset B2_EXC alarm threshold (10-3 by default).
Attribute
Major Service alarm
Parameters
None

The services on the port are interrupted.
Possible Causes
interface board).

Procedure
board).
If... Then...
opposite NE.
channel to locate the fault.
If... Then...
the fiber
connector.

If... Then...
NE and opposite NE.

If... Then...
If... Then...
----End
Related Information
A.3.25 B2_SD
Description
the multiplex section). This alarm occurs when the board detects that the number of B2 errors
is higher than the preset B2_SD alarm threshold (10-6 by default) and lower than the preset
Attribute
Minor Service alarm
Parameters
None

The service performance on the port degrades.

Possible Causes
interface board).
Procedure
board).
If... Then...
opposite NE.
(for example, within ± 3 dB) of the receiver sensitivity
If... Then...
the fiber
connector.

If... Then...
NE and opposite NE.

If... Then...
1. The SDH optical/electrical line board of the local NE is faulty. Loop back the optical
interfaces of the station by using a fiber jumper to locate the fault.
If... Then...
If... Then...
----End
Related Information
A.3.26 B3_EXC
Description
The B3_EXC is an alarm indicating that the B3 errors (in the higher order path) exceed the
threshold. This alarm occurs when the board detects that the number of B3 errors exceeds the
preset B3_EXC alarm threshold (10-3 by default).
Attribute
Major Service alarm
Parameters
None


When the B3_EXC alarm occurs, the service on the alarmed path is interrupted.
Possible Causes
interface board).
Procedure
board).
If... Then...
opposite NE.
If... Then...
the fiber
connector.


If... Then...
The clock source of the local NE In this case, the clock may become asynchronous
is different from the clock source and errors may occur. Reconfigure the clock
of the opposite NE source, and ensure that the clock is synchronized
on the local NE and opposite NE.
The clock of the local NE and This may cause errors and even service
the clock of the opposite NE interruption. In this case, reconfigure the clock
form a timing loop source and release the timing loop.
If... Then...
If... Then...
----End
Related Information
A.3.27 B3_EXC_VC3
Description
The B3_EXC_VC3 alarm indicates that the number of B3 bit errors in a VC-3 path crosses
the threshold. A board reports this alarm when detecting that the number of B3 bit errors
crosses the B3_EXC_VC3 alarm threshold (10-3, by default).
Attribute
Major Service alarm

Parameters
Name Meaning
Parameter 1 Has a fixed value of 0x01.
Parameter 2, Parameter Indicate the ID of the VC-3 path that reports the alarm. For
3 example, 0x00 0x01 indicate that the alarm is reported in VC-3
path 1.

The services in the alarmed path have a large number of bit errors.
Possible Causes
l Cause 1: Higher-level bit error alarms occur in the system.
l Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical
port).
l Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet
electrical port).
l Cause 4: A board is faulty.
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system.
1. Check whether the local or upstream site detects B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD alarms. If yes, clear the higher-level alarms.
2. Check whether the alarm is cleared.
If... Then...
The alarm persists Go to Cause 2 or Cause 3.
Step 2 Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical port).
1. Check whether the transmit power at the opposite site and the receive power at the local
site meet the specifications of the optical ports. For details, see Browsing Current
Performance Events.
If... Then...
The transmit power at the opposite site is too low Replace the optical module
at the opposite site.

If... Then...
The transmit power at the opposite site is normal, A fiber is faulty. Go to the
but the receive power at the local site is close to the next step.
receiver sensitivity (for example, a difference within
±3 dB)
2. Exchange the optical fibers in the receive and transmit directions of an optical path
segment.
If... Then...
The number of bit errors changes Go to the next step.
The number of bit errors does not change Go to Cause 4.
3. If a fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out from the equipment room are
pressed, and whether any fiber connector is dirty or damaged. If yes, clean or replace the
fiber connector, or replace the fiber jumper. Check whether the alarm is cleared.
If... Then...
Step 3 Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical
port).
1. Check whether the cable grounding, cable connectors, and cables are damaged. If yes,
replace the faulty cables.
If... Then...
Step 4 Cause 4: A board is faulty.

1. Perform an inloop at the Ethernet port that connects to the alarmed VC-3 path.
If... Then...
The fault is not rectified after the Replace the alarmed Ethernet
Ethernet port is looped back processing board at the local site.
The fault is rectified after the Ethernet Replace the Ethernet processing
port is looped back board at the opposite site.
----End
Related Information
None

A.3.28 B3_SD
Description
the higher order path). This alarm occurs when the board detects that the number of B3 errors
is higher than the preset B3_SD alarm threshold (10-6 by default) and lower than the preset
Attribute
Minor Service alarm
Parameters
None

The service performance on the port degrades.
Possible Causes
interface board).
Procedure
board).
If... Then...
opposite NE.

If... Then...
the fiber
connector.
If... Then...
The clock source of the local NE In this case, the clock may become asynchronous
is different from the clock source and errors may occur. Reconfigure the clock
of the opposite NE source, and ensure that the clock is synchronized
on the local NE and opposite NE.
The clock of the local NE and This may cause errors and even service
the clock of the opposite NE interruption. In this case, reconfigure the clock
form a timing loop source and release the timing loop.
1. The SDH optical/electrical line board of the local NE is faulty. Loop back the optical
interfaces of the station by using a fiber jumper to locate the fault.
If... Then...
If... Then...
----End
Related Information

A.3.29 B3_SD_VC3
Description
The B3_SD_VC3 alarm indicates a signal degrade (SD) condition caused by excessive B3 bit
errors in VC-3 paths. A board reports this alarm when detecting that the number of B3 bit
errors crosses the B3_SD_VC3 alarm threshold (10-6, by default).
Attribute

Minor Service alarm
Parameters
Name Meaning
Parameter 2, Parameter Indicate the ID of the path that reports the alarm. For example,
3 0x00 0x01 indicate that the alarm is reported in VC-3 path 1.

When the B3_SD_VC3 alarm occurs, the services in the alarmed path deteriorate.
Possible Causes
l Cause 1: Higher-level bit error alarms occur in the system.
port).
electrical port).
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system.
1. Check whether the local or upstream site detects B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD alarms. If yes, clear the higher-level alarms.

If... Then...
The alarm persists Go to Cause 2 or Cause 3.
Performance Events.
If... Then...
±3 dB)
2. Exchange the optical fibers in the receive and transmit directions of an optical path
segment.
If... Then...
The number of bit errors changes Go to the next step.
The number of bit errors does not change Go to Cause 4.
If... Then...
port).
If... Then...

1. Perform an inloop at the Ethernet port that connects to the alarmed VC-3 path.

If... Then...
The fault is not rectified after the Replace the alarmed Ethernet
Ethernet port is looped back processing board at the local site.
The fault is rectified after the Ethernet Replace the Ethernet processing
port is looped back board at the opposite site.
----End
Related Information
None
A.3.30 BAT1TEMP_SENSOR_FAIL
Description
The BAT1TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of
battery group 1 fails.
Attribute
Parameters
None

The temperature data of battery group 1 cannot be collected.
Possible Causes
l Cause 1: The temperature sensor of battery group 1 is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The temperature sensor is not installed.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 1 is faulty.
1. Replace the temperature sensor of battery group 1.
If... Then...
The alarm clears End the alarm handling.

If... Then...
Step 2 Cause 2: The control board of the cabinet is faulty.

1. Replace the cabinet.
If... Then...
Step 3 Cause 3: Cables are misconnected or damaged.

1. Replace damaged cables.
2. Connect cables correctly.
Step 4 Cause 4: The temperature sensor is not installed.
1. Install the temperature sensor.
----End
Related Information
None
A.3.31 BAT2TEMP_SENSOR_FAIL
Description
The BAT2TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of
battery group 2 fails.
Attribute
Parameters
None

The temperature data of battery group 2 cannot be collected.
Possible Causes
l Cause 1: The temperature sensor of battery group 2 is faulty.


l Cause 4: The temperature sensor is not installed.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 2 is faulty.
1. Replace the temperature sensor of battery group 2.
If... Then...

If... Then...

Step 4 Cause 4: The temperature sensor is not installed.

1. Install the board temperature sensor.
----End
Related Information
None
A.3.32 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED is an alarm indicating that the physical board is installed in a
certain slot, but the logical board is not added.
Attribute

Minor Equipment alarm

Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the slot.

When the BD_NOT_INSTALLED alarm occurs, the physical board in this slot cannot work.
Possible Causes
Cause 1: The logical board is not added in the corresponding logical slot.
Procedure
Step 1 Cause 1: The logical board is not added in the corresponding logical slot.
1. Configure the logical board.
----End
Related Information
None
A.3.33 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the board cannot be detected.
Attribute

Parameters
None

When the BD_STATUS alarm occurs, the alarmed board fails to work.

Possible Causes
If the alarm is reported by a board of the IDU, the possible causes are as follows:
l Cause 1 of the alarm reported by a board of the IDU: The board is installed in an
incorrect slot.
l Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are
not connected properly.
l Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
l Cause 4 of the alarm reported by a board of the IDU: A certain board is faulty.
If the alarm is reported by the ODU, the possible causes are as follows:
l Cause 1 of the alarm reported by the ODU: The other alarms are generated.
l Cause 2 of the alarm reported by the ODU: The ODU is faulty.
Procedure
Step 1 Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect
slot.
1. Check whether the logical slot and physical slot of the alarmed board are consistent. For
details, see 4.2 Checking the Board Status.
If... Then...
The alarmed board is installed in an Install the board in a correct slot.
incorrect slot
The alarmed board is installed in a Ensure that the board and the
correct slot backplane are connected properly.
Step 2 Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not
connected properly.
1. Remove and insert the alarmed board.
If... Then...
The alarm is cleared after the board is The fault is rectified. End the
removed and inserted alarm handling.
The alarm persists after the board is Ensure that the board is normal.
removed and inserted
Step 3 Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
1. Contact Huawei engineers to handle the fault of the slot.
NOTE
Generally, the slot becomes faulty due to the broken pin or bent pin. Remove the board, and use a
torch to observe whether there is any broken pin or bent pin.
2. If a vacant slot is available, insert the board in the vacant slot and add the board again.
Then, the board can work normally.
Step 4 Cause 4 of the alarm reported by a board of the IDU: A certain board is faulty.

If... Then...
The alarm is cleared after the board is The fault is rectified. End the alarm
replaced handling.
The alarm persists after the board is Ensure that the slot is normal.
replaced
Step 5 Cause 1 of the alarm reported by the ODU: The other alarms are generated.
1. Query whether the IF board reports the HARD_BAD, BD_STATUS,
IF_CABLE_OPEN, BD_NOT_INSTALLED or VOLT_LOS alarm.
If... Then...
The IF board reports any of the preceding alarms Clear the alarm immediately.
The IF board does not report any of the preceding Replace the alarmed ODU.
alarms
Step 6 Cause 2 of the alarm reported by the ODU: The ODU is faulty.
1. Replace the alarmed ODU.
----End
Related Information
None
A.3.34 BDTEMP_SENSOR_FAIL
Description
The BDTEMP_SENSOR_FAIL is an alarm indicating that the board temperature sensor of
the cabinet fails.
Attribute
Parameters
None

The board temperature data of the TCU cannot be collected.
Possible Causes
l Cause 1: The board temperature sensor is faulty.


l Cause 4: The board temperature sensor is not installed.
Procedure
Step 1 Cause 1: The board temperature sensor is faulty.
1. Replace the board temperature sensor.
If... Then...

If... Then...

Step 4 Cause 4: The board temperature sensor is not installed.

1. Install the board temperature sensor.
----End
Related Information
None
A.3.35 BGPBACKTRANSITION
Description
The BGPBACKTRANSITION alarm indicates that a Border Gateway Protocol (BGP)
connection is interrupted because the status of the BGP peer changes.
Attribute

Parameters
Name Meaning
Parameters 1-4 Indicate the IPv4 address of the BGP peer.
Parameters 5-7 Indicate the error code contained in the BGP notification returned
during the last BGP connection interruption.
Parameters 8-11 Indicate the status of the BGP peer.
Parameters 12-15 Indicate the instance ID.
Parameters 16-19 Indicate the address family.
Parameters 20-23 Indicate the sub-address family.
Parameters 24-27 Indicate the address type of the BGP peer.
Parameters 28-48 Indicate the IPv6 address of the BGP peer.
Parameters 49-52 Indicate the cause of the BGP connection interruption.
Parameters 53-56 Indicate the local interface index.
Parameters 57-120 Indicate the local interface name.

The BGP connection is interrupted, routes become unreachable, and services are interrupted.
Possible Causes
l Cause 1. The BGP configurations change.
l Cause 2: There is no reachable IP route to the BGP peer.
Procedure
Step 1 Cause 1. The BGP configurations change.
1. Ensure that the BGP configurations are consistent at the local end and the BGP peer.
Step 2 Cause 2: There is no reachable IP route to the BGP peer.
1. Ping the public IP address of the BGP peer to check whether there is a reachable IP route
to the BGP peer. If there is no reachable IP route to the BGP peer, go to the next step.

2. Check whether the link to the BGP peer is faulty, for example, whether an ETH_LOS
alarm is reported. If the link is faulty, rectify the fault.
3. Ensure that the IGP configurations between the local end and the BGP peer are correct.
----End
Related Information
None
A.3.36 BIOS_STATUS
Description
The BIOS_STATUS alarm indicates that the alarmed board is in the BIOS state.
Attribute

Major Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the slot ID of the board that is in the BIOS state.

The services on the alarmed board are interrupted.
Possible Causes
l Cause 1: The board software is lost.
l Cause 2: The board software becomes abnormal.
l Cause 3: The board is reset for three consecutive times in five minutes.
Procedure
Step 1 Perform a cold reset on the alarmed standby system control, switching, and timing board,
and check whether the alarm is cleared.
Step 2 If the alarm persists, remove the standby system control, switching, and timing board, and
reseat the board.
NOTE
If the equipment does not have a standby system control, switching, and timing board, skip this step.

NOTICE
Do not install or remove a board when the equipment is on. Before removing the standby
system control, switching, and timing board, power off the equipment.
Step 3 If the alarm persists, replace the board.
----End
Related Information
None
A.3.37 BIP_EXC
Description
The BIP_EXC is an alarm indicating that the BIP errors exceed the threshold. This alarm
occurs when the board detects that the number of BIP-2 errors (in byte V5) exceeds the preset
BIP_EXC alarm threshold (10-3 by default).
Attribute
Minor Service alarm
Parameters
None

When the BIP_EXC alarm occurs, the service on the alarmed path is interrupted.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service
board).
l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
1. Check whether the performance degradation alarm occurs on the STM-1 path or radio
link along which the E1 service signal travels. If yes, clear the alarm immediately.
The common line performance degradation alarms are as follows:

B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,

RPS_INDI, MW_BER_EXC, and MW_BER_SD.
If... Then...
There is any of the preceding alarms Clear the alarm immediately.
No such alarms occur Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
1. Check whether any alarm occurs on the tributary board or IF board that transmits the
service signal. If yes, clear the alarm immediately.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
1. Replace the board where the E1 service unit is located. Then, check whether the
alarm is cleared.
If... Then...
The alarm persists Replace the system control and cross-connect board.
Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
1. Replace the Hybrid IF board. Then, check whether the alarm is cleared.
If... Then...
----End
Related Information
The alarm parameters have the meanings listed in Table A-3 when EMS6 board report the
alarm.
Table A-3 Alarm Parameters of EMS6

Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path that reports the

alarm. For example, 0x00 0x01 indicate that
the alarm is reported in path 1.

A.3.38 BIP_SD
Description
The BIP_SD is an alarm indicating that the signal degrades due to the BIP errors. This alarm
occurs when the board detects that the number of BIP-2 errors (in byte V5) is higher than the
preset BIP_SD alarm threshold (10-6 by default) and lower than the preset BIP_EXC alarm
threshold (10-3 by default).
Attribute
Minor Service alarm
Parameters
None

When the BIP_SD alarm occurs, the service on the alarmed path degrades.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service
board).
l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
1. Check whether the performance degradation alarm occurs on the STM-1 path or radio
link along which the E1 service signal travels. If yes, clear the alarm immediately.
The common line performance degradation alarms are as follows:
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,

RPS_INDI, MW_BER_EXC, and MW_BER_SD.
If... Then...
There is any of the preceding alarms Clear the alarm immediately.
No such alarms occur Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
1. Check whether any alarm occurs on the tributary board or IF board that transmits the
service signal. If yes, clear the alarm immediately.

Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
1. Replace the board where the E1 service unit is located. Then, check whether the
alarm is cleared.
If... Then...
Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
1. Replace the Hybrid IF board. Then, check whether the alarm is cleared.
If... Then...
----End
Related Information
alarm.
Table A-4 Alarm Parameters of EMS6
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path that reports the

alarm. For example, 0x00 0x01 indicate that
the alarm is reported in path 1.
A.3.39 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data consistency check
fails. This alarm occurs when the BOOTROM data is damaged during a periodical check by
the system.
Attribute


Parameters
Name Meaning
Parameter 2, Parameter 3 Indicates the type of the BOOTROM damage.
l 0x00, 0x01: damage of the basic BIOS
l 0x00, 0x02: damage of the extended BIOS
Parameter 4, Parameter 5 The values are always 0xff 0xff.

When the BOOTROM_BAD alarm occurs, it indicates that errors occur in the system
database processing. The system configuration may be lost. As a result, the failure indication
is returned for certain query and setting commands, and certain system functions cannot work.
l When the NE is already started, the BOOTROM_BAD alarm does not affect the system
and services.
l If the BOOTROM_BAD alarm occurs and a hard reset is performed on a board, the
board fails to load the BIOS and cannot be started.
Possible Causes
l Cause 1: The basic BIOS is damaged.
l Cause 2: The extended BIOS is damaged.
l Cause 3: The BOOTROM database is damaged.
l Cause 4: The system control switch and timing boardis faulty.
Procedure
Step 1 Replace the alarmed board.
----End
Related Information
None
A.3.40 BRDCASTRATIO_OVER
Description
The BRDCASTRATIO_OVER alarm indicates that the ratio of broadcast traffic exceeds the
threshold. This alarm is reported when the ratio of broadcast and multicast packets to all
packets exceeds the specified threshold.

Attribute

Parameters
Name Meaning
Parameter 1 Indicates the service flow direction.
l 0x00: receive direction
l 0x01: transmit direction

When this alarm exists, a broadcast storm may occur.
Possible Causes
l Cause 1: A service loop is formed.
l Cause 2: The broadcast packet suppression threshold is improperly set in IPTV
scenarios.
l Cause 3: The PLA group configurations are deleted from the local NE, but not from the
other NEs in the same PLA group.
Procedure
Step 1 Cause 1: A service loop is formed.
1. Check for and release port self-loops or service loops on the service path.
Step 2 Cause 2: The broadcast packet suppression threshold is improperly set in IPTV scenarios.
1. Re-plan and modify the broadcast packet suppression threshold for IPTV services. For
detailed operations, see Setting the Advanced Attributes of Ethernet Ports.
Step 3 Cause 3: The PLA group configurations are deleted from the local NE, but not from the other
NEs in the same PLA group.
1. Delete PLA group configurations from other NEs in the same PLA group.
----End
Related Information
None

A.3.41 BUS_ERR
Description
The BUS_ERR alarm indicates a bus fault or a data service exception on an NE.
Attribute
Critical Equipment alarm

Parameters
Name Meaning
Parameter 1 For a service board or a switching and timing board, Parameter 1 indicates the
bus error type.
l 0x01: BUS_LOS
l 0x02: BUS_OOF
l 0x03: BUS_LOF
l 0x04: BUS_OOA
l 0x05: BUS_RX_DOWN
l 0x06: BUS_TX_DOWN
l 0x07: BUS_SPI_DOWN
l 0x08: BUS_SCI_ERR
l 0x09: BUS_OPP_CLK_LOC
l 0x0a: BUS_SERDS_ERR
l 0x0b: BUS_MII_ERR
l 0x0c: BUS_HW_ERR
l 0x0d: BUS_FE_ERR or anti-theft verification failure on a device
l 0x0e: BUS_EMIF_ERR
l 0x0f: BUS_IIC_ERR
l 0x10: BUS_GE_LINK_ERR
l 0x11: BUS_EMIF
For a system control board, Parameter 1 is set to 0x32 \0x30.
For an IF board, meanings of Parameter 1 are as follows:
l 0x00: Bus signals from the analog to digital converter (ADC) to the
modem are abnormal in the downlink direction.
l 0x01: Bus signals from the ADC to the modem are abnormal in the uplink
direction.
l 0x02: Bus signals from the modem to the ADC are abnormal in the
downlink direction.
l 0x03: IF signals from the backplane are abnormal.
l 0x04: The phase-locked loop (PLL) on a data service serial interface is out
of lock.
l 0x05: Decapsulation of data services is abnormal in the downlink
direction.
l 0x06: Communication between the master and slave boards in a PLA
group is abnormal.
l 0x07: The packet segment sequence numbers of the master and slave PLA
boards do not match.
l 0x08: Services on a PLA member are abnormal.
l 0x09: The Telecom bus detects B2 bit errors.

Name Meaning
Parameter Meanings of Parameter 2 are as follows:

2,
Parameter 3 For a service board, Parameter 2 and Parameter 3 indicate the ID of the faulty
bus.
For a system control board, When Parameter 1 is set to 0x30, the payload bus
between the system control board and extended board is faulty.When
Parameter 1 is set to 0x32, the TELECOM or LVDS bus between the system
control board and service board is faulty.
For an IF board, when Parameter 1 is 0x08, Parameter 2 and Parameter 3
indicate the ID of the PLA member port on which services are abnormal.
Parameter 3 is a user-defined parameter.

When the BUS_ERR alarm occurs, the services that travel along the faulty bus are interrupted
or have errors.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows:
l Cause 1: The board is not properly inserted.

l Cause 2: Service configurations or basic configurations (such as the number of E1
services) on an IF board are incorrect.
l Cause 3: A certain board is faulty.
l Cause 4: A board that has the anti-theft verification function enabled is inserted into an
NE that does not support this function.
Procedure
Step 1 Cause 1: The board is not properly inserted.
1. Remove and insert the board.
2. Check whether the BUS_ERR alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: Service configurations or basic configurations (such as the number of E1 services)
on an IF board are incorrect.
1. Check whether service configurations or basic configurations on IF boards are correct
(For example, check for the A.3.262 MW_CFG_MISMATCH alarm on IF boards). If
any alarms indicating incorrect service configurations or basic configurations are
reported, clear them.

1. Perform a cold reset on the alarmed board. Then, check whether the alarm is cleared.

If... Then...
The alarm is cleared The fault is rectified. End the alarm handling.
The alarm persists Replace the alarmed board.
Step 4 Cause 4: A board that has the anti-theft verification function enabled is inserted into an NE
that does not support this function.
1. Query the board for which the BUS_ERR alarm is reported on the NMS, and remove
the board from the NE.
2. Insert the board into an NE that supports the anti-theft verification function. For details,
see Part Replacement.
3. Disable the anti-theft verification function for the board.
4. Remove the board from the NE.
5. Insert the board that has the anti-theft verification function disabled into the original NE.
6. Check whether the BUS_ERR alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
Step 5 Check whether the BUS_ERR alarm is cleared. If the alarm persists, contact Huawei technical
----End
Related Information
alarm.
Table A-5 Alarm parameters of EMS6

Name Meaning
Parameter 1 Indicates the bus error type.

0x10: The Serdes bus of the GE bridge is
faulty.
A.3.42 CES_ACR_LOCK_ABN
Description
The CES_ACR_LOCK_ABN is an alarm indicating that the locking function of CES ACR
service clock is abnormal.
Attribute
Minor Service alarm

Parameters
Name Meaning
Parameter 1 to Indicate the index of PW that carries the services associated with
Parameter 4 the ACR clock source.
Parameter 5 Indicates clock mode.

l 0x01: tracing mode.
l 0x02: holdover mode.
l 0x03: free-run mode.
Parameter 6 Indicates whether the clock is locked.
l 0x00: unlocked.
l 0x01: locked.

Service quality is affected.
Possible Causes
l Cause 1: CES ACR services are unavailable or have alarms.
l Cause 2: The network is unstable.
l Cause 3: NEs on the service path are abnormal.
Procedure
Step 1 Cause 1: CES ACR services are unavailable or have alarms.
1. Query the CES services associated with the ACR clock source. For details, see
Configuring the Primary Clock for an ACR Clock Domain.
2. Check whether these services have alarms. For details, see 4.3.1 Browsing Current
Alarms.
Step 2 Cause 2: The network is unstable.
1. Check for jitters and delays on the network. Query service performance statistics. For
details, see 4.3.3 Browsing Current Performance Events.
2. Analyze service performance statistics. If the network is unstable, rectify the faults on
the network, or switch the affected services to a stable network.
Step 3 Cause 3: NEs on the service path are abnormal.
1. Query alarms reported by the NEs on the service path. For details, see 4.3.1 Browsing
Current Alarms.
2. Handle the alarms. For details, see A.3 Alarms and Handling Procedures.
----End
Related Information
None

A.3.43 CES_APS_INDI
Description
The CES_APS_INDI is an alarm indicating the status of the packet linear MSP. This alarm is
reported when the configured packet linear MSP is in the switching state.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the MSP protection group.

l When this alarm occurs, automatic protection switching or switching triggered by an
external command occurs. As a result, services are switched to the protection channel for
transmission.
l This alarm does not affect the services. If the protection channel fails at this time, the
services are interrupted.
Possible Causes
l Cause 1: An external command is issued to trigger switching (such as manual switching,
forced switching, exercise switching, and lockout of switching).
l Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD
alarm) or a cold reset that triggers automatic MSP switching.
l Cause 3: The attributes of the MSP protection group are incorrectly configured.
l Cause 4: The interface board is faulty.
Procedure
Step 1 Cause 1: An external command is issued to trigger switching (such as manual switching,
forced switching, exercise switching, and lockout of switching).
1. Check the switching status of the protection group.

If... Then...
The MSP is in the state of manual Clear the switching status. Check
switching, forced switching, or exercise whether the alarm is cleared. If the
switching alarm persists, go to Step 2.
The MSP is not in any of the preceding Go to Step 2.

switching state
Step 2 Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD
alarm) or a cold reset that triggers automatic MSP switching.
1. Check whether the protection group is in the automatic switching state.
If... Then...
The local NE reports the The MSP protection group changes to the switching
R_LOS, R_LOF, MS_AIS, state, and the CES_APS_INDI alarm is reported. Clear
or B2_EXC alarm the alarm immediately. Then check whether the
CES_APS_INDI alarm is cleared.
If the alarm persists, go to the next step.
The local NE reports the Clear the alarm immediately. Then check whether the
B2_SD alarm CES_APS_INDI alarm is cleared. If the alarm persists,
go to the next step.
The interface board is in the After the cold resetting ends, go to step 3 and identify
cold resetting state the cause of the cold resetting.
The MSP is not in any of the Go to the next step.

preceding switching state
2. Check the method for setting the revertive mode of the protection group.
If... Then...
Revertive Mode After the working channel recovers, the services are automatically
is set to switched from the protection channel to the working channel once
Revertive the preset wait to restore (WTR) time expires. The
CES_APS_INDI alarm will be cleared after the switching
succeeds.
Wait until the MSP protection group changes from the switching
status to the normal status. Then check whether the
CES_APS_INDI alarm is cleared. If the alarm persists, go to Step
3.

If... Then...
Revertive Mode The services are not switched from the protection channel to the
is set to Non- working channel after the working channel recovers, and the
Revertive CES_APS_INDI alarm persists.
To clear the CES_APS_INDI alarm, manually switch the services
from the protection channel to the working channel. Then go to the
next step.
3. After the manual switching succeeds, check whether the alarm is cleared. If the alarm
persists, go to Step 3.
Step 3 Cause 3: The attributes of the MSP protection group are incorrectly configured.
1. If the packet linear MSP is configured on a per-NE basis, check whether the MSP
parameters such as the protection type, switching mode, and mapping unit are configured
correctly. If any of the preceding parameter values are incorrect, change the values and
apply correct settings to the NE. For details, see Configuring Linear MSP.
Step 4 Cause 4: The interface board is faulty.
1. Check whether the interface board that is configured with the packet linear MSP is
functioning properly.
2. If a hardware alarm such as HARD_BAD occurs on the interface board, clear the alarm
immediately.
3. Replace the interface board. For details, see 6 Part Replacement.
----End
Related Information
None
A.3.44 CES_APS_MANUAL_STOP
Description
The CES_APS_MANUAL_STOP is an alarm indicating that the packet linear MSP protocol
is stopped manually. This alarm is reported when the packet linear MSP protocol is stopped
manually.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the ID of the MSP protection group.

When this alarm occurs, the packet linear MSP protocol is stopped and the MSP fails. As a
result, STM-1 services cannot be protected.
Possible Causes
Cause 1: The APS protocol for the corresponding protection group is manually stopped.
Procedure
Step 1 Cause 1: The APS protocol for the corresponding protection group is manually stopped.
1. Determine the ID of the MSP protection group whose APS protocol is stopped according
to alarm parameters.
2. Restart the MSP protocol for the protection group.
----End
Related Information
None
A.3.45 CES_JTROVR_EXC
Description
The CES_JTROVR_EXC is an alarm indicating that the number of jitter buffer overflows
crosses the specified threshold. This alarm occurs when the board detects that, the number of
jitter buffer overflows per second crosses the specified threshold.
Attribute
Parameters
None

The buffer area does not have sufficient space for the received frames. As a result, packets are
discarded.

Possible Causes
l Cause 1: The size of buffer area is set to a low value.
l Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
Procedure
Step 1 Cause 1: The size of buffer area is set to a low value.
1. Query the size of buffer area. For details, see Querying CES Service Information.
2. Determine whether the size can be increased according to network planning. If yes,
change the size to a greater value. For details, see Managing CES Services.
Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
1. Synchronize the PSN network clock by setting clock synchronization, reducing
transmission nodes, and optimizing transmission routes.
----End
Related Information
None
A.3.46 CES_JTRUDR_EXC
Description
The CES_JTRUDR_EXC is an alarm indicating that the number of jitter buffer underflows
crosses the specified threshold. This alarm occurs when the board detects that, within a period
(10s), the number of jitter buffer underflows per second crosses the specified threshold.
Attribute
Parameters
None

When this alarm occurs, no packets are available in the buffer area for transmission. As a
result, underflows occur in the buffer area.
Possible Causes
l Cause 1: Signals degrade on the link.
l Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.

l Cause 3: The link is looped.

l Cause 4: The link is congested.
l Cause 5: The size of buffer area is set to a low value.
Procedure
Step 1 Cause 1: Signals degrade on the link.
1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
1. Synchronize the PSN network clock by setting clock synchronization, reducing
transmission nodes, and optimizing transmission routes.
Step 3 Cause 3: The link is looped.
1. Release the loop.
Step 4 Cause 4: The link is congested.
1. Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth
or eliminate any source that transmits a large amount of invalid data.
Step 5 Cause 5: The size of buffer area is set to a low value.
1. Query the size of buffer area. For details, see Querying CES Service Information.
2. Determine whether the size can be increased according to network planning. If yes,
change the size to a greater value. For details, see Managing CES Services.
----End
Related Information
None
A.3.47 CES_K1_K2_M
Description
The CES_K1_K2_M is an alarm indicating that the K1 byte and K2 byte of the packet MSP
mismatch. This alarm is reported when the channel numbers indicated in the transmitted K1
byte and the received K2 byte are inconsistent and the inconsistency lasts for a period of time
(160 ms by default).
Attribute
Parameters
None


When this alarm occurs, MSP fails. If a fiber cut or another fault occurs at this time, services
may be interrupted.
Possible Causes
l Cause 1: MSP is incorrectly configured.
Procedure
Step 1 Cause 1: MSP is incorrectly configured.
1. Check whether the MSP configurations are consistent between the local and opposite
NEs. For example, ensure that the other end is configured as the working unit if one end
of a fiber is configured as the working unit; otherwise, the CES_K1_K2_M alarm is
reported.
2. Ensure that MSP is configured correctly. Then, check whether the alarm is cleared. If the
alarm persists, go to Step 2.

1. Check whether the interface boards on which MSP is configured are functioning
properly on the local and opposite NEs.
immediately.
3. If the alarm persists, replace the interface board. For details, see 6.10 Replacing the
System Control, Switching and Timing Board.
----End
Related Information
None
A.3.48 CES_K2_M
Description
The CES_K2_M is an alarm indicating that a mismatched K2 byte of the packet MSP is
detected. This alarm is reported when the protection mode used on the opposite NE, which is
indicated by bit 5 of the received K2 byte, is different from that used on the local NE for a
period of time (2s by default).
Attribute

Parameters
None

When this alarm occurs, MSP fails. If a fiber cut or another fault occurs at this time, services
may be interrupted.
Possible Causes
l Cause 1: Different protection modes are configured at both ends of a protection group.
Procedure
Step 1 Cause 1: Different protection modes are configured at both ends of a protection group.
1. Check whether the same protection mode is configured at both ends of a protection
group. If 1+1 protection is configured at one end and 1:N protection is configured at the
other end, the CES_K2_M alarm is reported. For details, see Creating a Packet-based
Linear MSP Group.

1. Check whether the interface boards on which MSP is configured are functioning
properly on the local and opposite NEs.
immediately.
3. If the alarm persists, replace the interface board. For details, see 6.10 Replacing the
System Control, Switching and Timing Board.
----End
Related Information
None
A.3.49 CES_LOSPKT_EXC
Description
The CES_LOSPKT_EXC is an alarm indicating that the number of lost packets of CES
services crosses the threshold in a time unit. This alarm occurs when the board detects that the
number of lost packets per second crosses the specified threshold.
Attribute


Parameters
None

When this alarm occurs, all 1s are inserted and services are interrupted.
Possible Causes
Procedure


----End
Related Information
Packets are lost when the sequence numbers of received packets are greater than expected.
A.3.50 CES_MALPKT_EXC
Description
The CES_MALPKT_EXC is an alarm indicating that, in a time unit, the number of deformed
frames in CES services crosses the threshold. This alarm occurs when the board detects that
the number of deformed frames in CES services crosses the specified threshold.
Attribute

Parameters
None


A deformed frame is discarded once it is detected. As a result, the packet loss rate increases
and services are affected.
Possible Causes
l Cause 1: The RTP head enabling status is different between the two ends of the PW.
l Cause 2: Bit errors occur on the link.
Procedure
Step 1 Cause 1: The RTP head enabling status is different between the two ends of the PW.
1. Set the RTP head enabling status to the same on the two ends of the PW. For details, see
Modifying CES Service Parameters.
Step 2 Cause 2: Bit errors occur on the link.

----End
Related Information
If a CESoPSN frame contains valid TDM data and does not contain any error indication, but
the size of the CESoPSN frame is not consistent with the specified size, a deformed
CESoPSN frame is generated.
A.3.51 CES_MISORDERPKT_EXC
Description
The CES_MISORDERPKT_EXC is an alarm indicating that, in a unit time, the number of
lost disordered packets crosses the specified threshold. This alarm occurs when the board
detects that the number of lost disordered packets per second crosses the specified threshold.
Attribute

Parameters
None

The packets are disordered. As a result, the packet loss rate increases and services are
affected.

Possible Causes
Procedure
1. See 5.3 Troubleshooting the Radio Link.


----End
Related Information
Packets are disordered when the sequence numbers of received packets are smaller than
expected.
A.3.52 CES_RDI
Description
The CES_RDI is an alarm of remote defect indication. When the CES_LOSPKT_EXC alarm
is reported at the remote end, the remote end sets the R bit in control word to 1. Upon
receiving a packet in which the R bit is 1, the local end reports the CES_RDI alarm.
Attribute
Parameters
None

The packet loss rate at the remote end crosses the specified threshold.
Possible Causes

Procedure
1. See 5.3 Troubleshooting the Radio Link.


----End
Related Information
None
A.3.53 CES_STRAYPKT_EXC
Description
The CES_STRAYPKT_EXC is an alarm indicating that, in a time unit, the number of error
packets in CES services crosses the threshold. This alarm occurs when the board detects that
the number of error packets in CES services per second crosses the specified threshold.
Attribute
Parameters
None

An error packet is discarded once it is detected. As a result, the packet loss rate increases and
services are affected.
Possible Causes
Cause 1: Links are misconnected.
Procedure
Step 1 Cause 1: Links are misconnected.

1. Check the link configuration and rectify the fault.
----End
Related Information
Incorrect packets are received when the tracing source field in the RTP head is different from
expected.
A.3.54 CESPW_OPPOSITE_ACFAULT
Description
The CESPW_OPPOSITE_ACFAULT is an alarm indicating that the AC circuit on the remote
NE is faulty. On detection of an AC circuit fault, the remote NE sets the L bit in the control
word to 1. When receiving a packet in which the L bit is 1, the local NE reports the
CESPW_OPPOSITE_ACFAULT alarm.
Attribute

Parameters
None

Possible Causes
Cause 1: The remote NE reports the T_ALOS, UP_E1_AIS, LFA, LMFA, R_LOS, R_LOF, or
MS_AIS alarm.
Procedure
Step 1 Check whether the remote NE reports the T_ALOS, UP_E1_AIS, LFA, LMFA, R_LOS,
R_LOF, or MS_AIS alarm.
1. If yes, handle these alarms.
----End
Related Information
None

A.3.55 CESPW_OPPOSITE_RAI
Description
The CESPW_OPPOSITE_RAI is a remote alarm indication. On detection of the RAI alarm,
the remote NE sets the L bit of the control word to 0 and the M field of the control word to
10. When receiving the packet in which the L bit is 0 and the M field is 10, the local NE
reports the CESPW_OPPOSITE_RAI alarm.
Attribute

Parameters
None

The services in the downstream direction of the remote NE are interrupted.
Possible Causes
Cause 1: The remote NE detects the RAI alarm.
Procedure
Step 1 Cause 1: The remote NE detects the RAI alarm.
1. Clear the ALM_E1RAI alarm on the remote NE.
----End
Related Information
None
A.3.56 CFCARD_FAILED
Description
The CFCARD_FAILED is an alarm indicating that the operation on the CF card fails.
Attribute


Parameters
None

When the CFCARD_FAILED alarm occurs, the database cannot be backed up to the CF card
or be restored from the CF card. This alarm may cause rollback of the package loading
upgrade.
Possible Causes
l Cause 1: The CF card fails to be initialized.
l Cause 2: The file system of the CF card does not match.
l Cause 3: The system control and communication board is faulty, and the file system of
the CF card fails to be created.
Procedure
Step 1 Cause 1: The CF card fails to be initialized.
Cause 2: The file system of the CF card does not match.
1. Replace the CF card and check whether the alarm is cleared.
If... Then...
Yes End the alarm handling.
No Go to Cause 3.
Step 2 Cause 3: The system control and communication board is faulty, and the file system of the CF
card fails to be created.
1. Check whether the HARD_BAD alarm occurs on the system control and communication
board.
2. If yes, perform a cold reset on the system control and communication board. Then,
check whether the alarm is cleared.
If... Then...
No Replace the system control and communication board.
----End
Related Information
None

A.3.57 CFCARD_FULL
Description
The CFCARD_FULL alarm indicates that the CF card will be used up. This alarm is reported
when the used capacity of the CF card exceeds the upper threshold.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot number of the board where the CFCARD_FULL
alarm is generated.
Parameter 2 Indicates the CF card number.
Parameter 3 Indicates the partition number of the CF card. If the bit is 1, it

indicates that this alarm is generated in this partition. If the bit is 0, it
indicates that this alarm is not generated in this partition.
l Bit (0) corresponds to SFS1.
NOTE
Bit (0) is the least significant bit.
Parameter 4, Reserved.
Parameter 5

In the case of the CFCARD_FULL alarm, services are not affected. The CFCARD_FULL
alarm is generated to indicate the CF card has no spare capacity.
Possible Causes
The possible cause of the CFCARD_FULL alarm is as follows:
Used capacity of partitions of the CF card crosses the threshold, which is 80% of the capacity.

Procedure
----End
Related Information
None.
A.3.58 CFCARD_OFFLINE
Description
The CFCARD_OFFLINE is an alarm indicating that the CF card is offline.
Attribute
Parameters
None

When the CFCARD_OFFLINE alarm occurs, the database cannot be backed up to the CF
card or be restored from the CF card. This alarm may cause rollback of the package loading
upgrade.
Possible Causes
l Cause 1: The CF card is not inserted.
l Cause 2: The CF card is in poor contact with the system control and communication
board.
l Cause 3: The CF card is faulty.
l Cause 4: The system control and communication board is faulty.
Procedure
Step 1 Cause 1: The CF card is not inserted.
1. Check whether the CF card is installed on the system control and communication board.
If... Then...
No Install the CF card.
Yes Go to Cause 2.
Step 2 Cause 2: The CF card is in poor contact with the system control and communication board.
1. Check whether the CF card is loosened. If yes, re-insert the CF card.

If... Then...
No Go to Cause 3.
Step 3 Cause 3: The CF card is faulty.

1. Replace the CF card.
If... Then...
No Go to Cause 4.
Step 4 Cause 4: The system control and communication board is faulty.

1. Check whether the HARD_BAD alarm occurs on the system control and communication
board.
2. If yes, perform a cold reset on the system control and communication board. Then,
3. If the alarm persists, replace the system control and communication board.
----End
Related Information
None
A.3.59 CFCARD_W_R_DISABLED
Description
The CFCARD_W_R_DISABLED is an alarm indicating that reading and writing the CF card
are disabled.
Attribute
Parameters
None.

When the CFCARD_R_R_DISABLED alarm occurs, the system is not affected. The alarm
only indicates that reading and writing the CF card are disabled.

Possible Causes
The possible cause of the CFCARD_W_R_DISABLED alarm is as follows:
Keep pressing the button on the CF card for more than five seconds.
Procedure
Step 1 Press the button on the CF card again.
----End
Related Information
None.
A.3.60 CHCS
Description
The CHCS is an alarm indicating the correctable cell error. When a correctable bit error is
detected in the cell header, the CHCS alarm occurs.
Attribute
Parameters
None

When the CHCS alarm occurs, the services are not affected. The alarm only indicates that
some cells with a bit error are detected during cell delimitation at the ATM port.
Possible Causes
l Cause 1: A few bit errors occur in the receive tunnel corresponding to the alarmed ATM
port.
l Cause 2: The ATM physical-layer processing chip of the board is faulty.
Procedure
Step 1 Cause 1: A few bit errors occur in the receive tunnel corresponding to the alarmed ATM port.
1. On the NMS, check whether the receive tunnel reports any alarms about excessive bit
errors, such as B1_SD, B2_SD, and B3_SD.
2. On the NMS, check whether the service is looped.

3. If yes, modify the service configuration to release the loop, and then check whether the
alarm is cleared.
Step 2 Cause 2: The ATM physical-layer processing chip of the board is faulty.
1. Perform a cold reset on the board that reports the CHCS alarm and check whether the
alarm is cleared. For details, see 8.6.1 Cold Reset.
2. Optional: If the CHCS alarm persists after the cold reset, replace the alarmed board and
check whether the alarm is cleared. For details, see 6.6 Replacing the Smart E1
Interface Board.
NOTE
Board replacement is not recommended because the alarm does not affect the services.
----End
Related Information
None
A.3.61 CLK_LOCK_FAIL
Description
The CLK_LOCK_FAIL is an alarm indicating a clock locking failure.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: indicates that the phase-locked loop (PLL) is in holdover or free-run
mode.
l 0x02: indicates that the timestamp in the Sync message remains the same in
Precision Time Protocol (PTP) synchronization mode.
l 0x03: indicates that the phase discrimination value within the given time
has crossed the upper threshold.

When this alarm occurs, the clock of the slave NE fails to trace that of the master NE, and bit
errors may occur.

Possible Causes
l Cause 1: Frequency deviation of the clock source has crossed the upper threshold in
physical synchronization mode.
l Cause 2: The physical link where the clock source resides is faulty in physical
synchronization mode.
l Cause 3: Frequency deviation of the clock source has crossed the upper threshold in
IEEE 1588v2 synchronization mode.
l Cause 4: The physical link where the clock source resides is faulty in IEEE 1588v2
Procedure
Step 1 Cause 1: Frequency deviation of the clock source has crossed the upper threshold in physical
1. Check whether high-level bit error alarms or performance events have been reported on
the NMS. If yes, handle them immediately.
2. If there is an external clock source, check whether its clock signals are normal. If no,
replace the external clock source. For details, see Configuring the Clock Sources.
3. Check whether clock configurations are correct. For example, if the input and output
modes of the external clock source do not match each other, modify the configurations.
For details, see Modifying the Parameters of the Clock Output.
Step 2 Cause 2: The physical link where the clock source resides is faulty in physical
1. If there is an external clock source, check whether the NE reports the SYNC_C_LOS
alarm. If yes, clear the alarm immediately.
2. If the CLK_LOCK_FAIL alarm persists, 6.10 Replacing the System Control,
Switching and Timing Board.
Step 3 Cause 3: Frequency deviation of the clock source has crossed the upper threshold in IEEE
1588v2 synchronization mode.
1. Check whether high-level bit error alarms or performance events have been reported on
the NMS. If yes, handle them immediately.
2. If there is an external clock source, check whether its clock signals are normal. If no,
replace the IEEE 1588v2 clock port. For details, see Replacing the IEEE 1588v2 Clock
Port.
Step 4 Cause 4: The physical link where the clock source resides is faulty in IEEE 1588v2
1. If the SYN_BAD alarm exists, clear the alarm immediately.
2. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None

A.3.62 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE alarm indicates that a clock source is not in locked mode.
This alarm is reported when the current clock does not trace any clock sources.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the clock mode.
l 0x01: holdover
l 0x02: free-run

When the clock source is not in the locked mode, the system clock is not of high quality.
Services may have bit errors when the clocks of the NEs are not synchronized. Pointer
justification may occur in TDM services. If a base station traces a clock that is carried by an
Ethernet service, an alarm indicating a large clock frequency deviation may occur.
Possible Causes
l Cause 1: The system clock source priority table is not configured.
l Cause 2: All the clock sources in the clock source priority table fail.
Procedure
Step 1 Cause 1: The system clock source priority table is not configured.
1. Configure the system clock source priority table. For details, see Configuring the Clock
Sources.
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
1. Troubleshoot the synchronization sources that are listed in the clock source priority table.

If... Then...
The synchronization source is an Handle the EXT_SYNC_LOS alarm.
external clock
The synchronization source is a line Handle the alarm that occurs on the line
clock board.
The synchronization source is an IF Handle the alarm that occurs on the IF board.
clock
The synchronization source is a Handle the alarm that occurs on the tributary
tributary clock board.
The synchronization source is an Handle the alarm that occurs on the Ethernet
Ethernet clock board.
----End
Related Information
None
A.3.63 COMMUN_FAIL
Description
The COMMUN_FAIL is an alarm indicating the inter-board communication failure. This
alarm is reported when the communication between a board and the SCC board is interrupted.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the ID of the port. The value is always 0x01.
Parameter 2, Indicates the ID of the path on which the alarm is generated.

Parameter 3 Parameter 2 is always 0x00. Parameter 3 has the following
meanings:
0x03: inter-board Ethernet communication

Name Meaning
Parameter 4,
Parameters 4 and 5 are reserved, and their values are always 0xFF.
Parameter 5

The NE configuration cannot be delivered to the board or the board cannot work.
Consequently, the services cannot be configured or the protection switching function is
unavailable.
Possible Causes
l Cause 1: A certain board is reset.
l Cause 2: A board and the backplane are connected improperly.
l Cause 4: A slot is faulty.
l Cause 5: When the active and standby system control boards switch over,
communication between them are interrupted transiently.
Procedure
Step 1 Cause 1: A certain board is reset.
1. After you reset the board, the alarm is cleared automatically.
Step 2 Cause 2: A board and the backplane are connected improperly.

1. Remove and insert the alarmed board. For details, see 6.1 Removing a Board and 6.2
Inserting a Board. Then, check whether the alarm is cleared.
If... Then...
The alarm is cleared after the The fault is rectified. End the alarm
board is removed and inserted handling.
The alarm persists after the board Clear the alarm according to the solution for
is replaced. the alarm that is generated when a board is
faulty.

1. Replace the alarmed board, and then check whether the alarm is cleared. For details, see
6 Part Replacement.
If... Then...
The alarm is cleared after the The fault is rectified. End the alarm handling.
board is replaced
The alarm persists after the Clear the alarm according to the solution for
board is replaced the alarm that is generated when a slot is
faulty.
Step 4 Cause 3: A slot is faulty.

1. Contact Huawei engineers to handle the faulty slot.

NOTE
The slot becomes faulty due to broken pins or bent pins. Remove the board, and use a torch to
check whether any pins are broken or bent.
2. If a vacant slot is available, insert the board in the vacant slot, and then update the data
on the NMS so that the board can work normally.
Step 5 Cause 5: When the active and standby system control boards switch over, communication
between them are interrupted transiently.
1. It is normal that this alarm is reported during the switchover, so this alarm does not need
to be handled.
----End
Related Information
None
A.3.64 COM_EXTECC_FULL
Description
The COM_EXTECC_FULL is an alarm indicating an excessive number of TCP connections
between automatically extended ECC NEs.
Attribute
Parameters
Name Meaning
Parameters 1 to 5 The value is always 0x00.

An excessive number of extended ECC NEs impacts NE performance.
Possible Causes
The number of TCP connections between automatically extended ECC NEs is larger than
four.

Procedure
Step 1 Set ECC Extended Mode to Specified mode by referring to Configuring Extended ECC
Communication.
----End
Related Information
None
A.3.65 CONFIG_NOSUPPORT
Description
The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported.
This alarm is reported if the ODU detects that the specified parameters do not meet the
requirements of the ODU.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates that the configuration data does not meet the requirements.
l 0x01: The frequency is set incorrectly.
l 0x02: The T/R spacing is set incorrectly.
l 0x03: The transmit power is set incorrectly.
l 0x04: The ATPC threshold is set incorrectly.
l 0x05: The bandwidth is set incorrectly.
l 0x06: The modulation mode is set incorrectly.

When the CONFIG_NOSUPPORT alarm occurs, the ODU fails to work normally. If the
equipment is configured with the 1+1 FD protection, the active ODU generates the
CONFIG_NOSUPPORT alarm. In this case, the IF 1+1 protection switching may be
triggered.

Possible Causes
l Cause 1: The type and configuration parameters of the ODU do not match the
requirements.
l Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only
when Parameter 1 is 0x03.)
NOTE
Perform the handling procedure of Cause 2 if the following conditions are met: The AM function is
enabled on the radio link; the transmit power configured for the ODU is lower than the maximum rated
power in AM guaranteed capacity mode.
Procedure
Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.
1. Determine the parameter that does not meet the requirement according to the alarm
parameter. Then, handle the fault accordingly.
If... Then...
The alarm parameter takes a value from 0x01 Perform the operation described in
to 0x03 Step 1.2.
The alarm parameter takes a value from 0x04 Perform the operation described in
to 0x06 Step 1.3.
2. Check whether the parameters of the ODU interface meet the requirements of network
planning. For details, see Configuring a Single-Hop Radio Link.
If... Then...
The parameters meet the requirements of Use the ODU of the proper model.
network planning
The parameters do not meet the requirements Modify the ODU interface
of network planning parameters.
3. Check whether the parameters of the IF interface meet the requirements of network
planning. For details, see Configuring a Single-Hop Radio Link.
If... Then...
The parameters meet the requirements Replace the IF board.
of network planning
The parameters do not meet the Modify the IF interface parameters. For
requirements of network planning details, see Configuring a Single-Hop
Radio Link.
Step 2 Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only when
Parameter 1 is 0x03.)
1. Verify that the alarm is caused by incorrect change of AM parameters.
Perform the handling procedure of Cause 2 if the following conditions are met:
– The AM function is enabled on the radio link.
– The transmit power configured for the ODU is lower than the maximum rated
power in AM guaranteed capacity mode

If... Then...
The conditions are met and the transmit Perform a cold reset for the alarmed
power needs to be changed ODU.
The conditions are met but the transmit Change the parameters of ODU
power does not need to be changed interfaces to recover the original value
of transmit power.
----End
Related Information
None
A.3.66 CPU_BUSY
Description
The CPU_BUSY alarm indicates that the CPU usage on a board is higher than the upper limit.
Attribute
Parameters
None

If the CPU is overloaded, some packets may not be processed timely and therefore discarded.
If this alarm persists for more than 30 minutes, the system control board warm resets and
services may be interrupted.
Possible Causes
l Cause 1: A great number of services are configured on the NE, and many alarm
monitoring and performance statistic tasks are enabled on the NE.
l Cause 2: An exception, such as a network storm, occurs on the network.
Procedure
Step 1 Cause 1: A great number of services are configured on the NE, and many alarm monitoring
and performance statistic tasks are enabled on the NE.
1. Disable some alarm monitoring and performance statistic tasks, or change the
performance statistic period from 15 minutes to 24 hours, to reduce CPU load. For
details, see Configuring the Performance Monitoring Status of NEs.

2. Check whether the CPU_BUSY alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: An exception, such as a network storm, occurs on the network.

1. Check for and release any loops on the network.
2. Check whether the CPU_BUSY alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None
A.3.67 DBMS_DELETE
Description
The DBMS_DELETE alarm indicates that a database is being deleted. This alarm is reported
when a user runs a command to delete the database and the NE is in Deleting Database state.
Attribute

Parameters
None

All data is lost if an NE is powered off or a system control board is cold reset within 48 hours.
Possible Causes
l Cause 1: A database is deleted.
Procedure
Step 1 Follow instructions in 7.4 Restoring the Database by NMS to restore the database.
----End
Related Information
None

A.3.68 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the processing of the system
database.
Attribute

Critical Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the error code.
l 0x00: The NE is running properly.
l 0x01: The database is being checked.
l 0x02: The database is undergoing a periodical backup.
l 0x04: The system is faulty.
l 0x08: Data on the active system control board and that on the standby
system control board are inconsistent.
l 0x10: Incremental data fails to be backed up.
l 0x20: Incremental data fails to be backed up to the NVRAM.
l 0x40: Incremental data fails to be backed up to the flash memory.
Parameter 2 Indicates the storage area of the database.

l 0x00: OFS1
l 0x01: OFS2
l 0x02: DRDB storage area
l 0x03: MDB storage area
l 0x04: TDRDB storage area
l 0x05: CF storage area
l 0x06: shared storage area
l 0x0C: NVRAM storage area
Parameter 3 Indicates the database ID.

l 0x00: all storage areas
l 0x01 to 0xff: database in which the error occurs
Parameter 4,
Reserved fields
Parameter 5


When the DBMS_ERROR alarm occurs, it indicates that errors occur in the system database
processing. The system configuration may be lost. As a result, the failure indication is
returned for certain query and setting commands, and certain system functions cannot work.
Possible Causes
Cause: The database processing fails or the database is damaged.
Procedure
Step 1 Obtain NE backup data (backed up periodically by the U2000 or backed up manually) or NE
service configuration information.
Step 2 Contact Huawei technical support engineers for handling the alarm.
Step 3 In case of emergency, 6.10 Replacing the System Control, Switching and Timing Board
and restore the database or reconfigure service data.
----End
Related Information
None
A.3.69 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the system database is in
protection mode.
Attribute
Parameters
None

When this alarm occurs, it indicates that errors occur in the system database processing and
the system configuration may be lost. As a result, the failure indication is returned for some
query and setting commands, and some system functions are unavailable.
Possible Causes
Cause 1: The database enters the protection mode due to frequent resets of the NE software.

Procedure
Step 1 Cause 1: The database enters the protection mode due to frequent resets of the NE software.
1. 6.10 Replacing the System Control, Switching and Timing Board.
----End
Related Information
None
A.3.70 DCNLINK_OVER
Description
The DCNLINK_OVER alarm indicates that the number of links on a DCN exceeds the
recommended value.
Attribute

Parameters
Name Meaning
Parameter 1 l 0x01: The total number of OSPF neighbors on the DCN exceeds the
recommended value.
l 0x02: The total number of OSPF neighbors to the same peer NE on the
DCN exceeds the recommended value.

System performance may be affected.
Possible Causes
l Cause 1: The total number of OSPF neighbors on the DCN exceeds the recommended
value.
l Cause 2: The total number of OSPF neighbors to the same peer NE on the DCN exceeds
the recommended value.

Procedure
Step 1 Disable unnecessary DCN channels on NEs to ensure that the total number of OSPF
neighbors on the DCN and the total number of OSPF neighbors to the same peer NE are
within the recommended ranges.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
A.3.71 DCNSIZE_OVER
Description
The DCNSIZE_OVER is an alarm indicating an over-sized DCN network.
Attribute

Parameters
Name Meaning
Parameter 1, Parameter If these parameters are 0xFF 0xFF, the NE works in L2DCN mode.
2 Otherwise, these parameters indicate the current size of the DCN
subnet.

l Some NEs become unreachable to the NMS because DCN packets cannot be forwarded
timely due to insufficient CPU resources.
l The DCN network is prone to route flapping and storms.
Possible Causes
Cause 1: The number of NEs on an L3 DCN subnet exceeds 400.

Procedure
Step 1 Replan the DCN network based on actual networking conditions.
----End
A.3.72 DDN_LFA
Description
The DDN_LFA is an alarm indicating loss of basic frame alignment for framed E1 services.
This alarm occurs when DDN (digital data network) side fails to receive the basic frame
alignment signal for framed E1 services.
Attribute

Parameters
None

E1 services on the alarmed board are unavailable.
Possible Causes
l Cause 1: The interconnected user equipment is faulty.
l Cause 2: The service frame format is configured incorrectly.
l Cause 3: The alarmed board has hardware faults.
Procedure
Step 1 Cause 1: The interconnected user equipment is faulty.
1. Troubleshoot the interconnected user equipment.
Step 2 Cause 2: The service frame format is configured incorrectly.

1. Set the E1 frame format of the local port to the same as that of the opposite port.
Step 3 Cause 3: The alarmed board has hardware faults.

1. Check whether the alarmed board also reports any hardware alarms, such as
HARD_BAD.
2. If yes, perform a cold reset on the alarmed board and check whether the DDN_LFA
alarm is cleared.

NOTICE
If the service on the alarmed board is not protected, a cold reset on the board causes
service interruptions.
3. If the alarm persists, replace the board.
----End
Related Information
Basic frame
As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence
(FAS) or an odd frame with non frame alignment sequence (NFAS).
A.3.73 DOWN_E1_AIS
Description
The DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when the
tributary board detects the 2 Mbit/s downlink signal of all 1s.
Attribute

Parameters
None

When the DOWN_E1_AIS alarm occurs, the E1 signal in the alarmed path is unavailable.
Possible Causes
l Cause 1: The opposite NE transmits the E1_AIS alarm.
l Cause 2: An upstream alarm triggers this alarm.
l Cause 3: On the local NE, the receive unit of the tributary board or the system control
and cross-connect board is faulty.
Procedure
Step 1 Cause 1: The opposite NE transmits the E1_AIS alarm.
1. Check whether the opposite NE reports the UP_E1_AIS or T_ALOS alarm.

If... Then...
The opposite NE reports the UP_E1_AIS or Clear the alarm immediately.
T_ALOS alarm
The opposite NE does not report the Ensure that the board on the local NE
UP_E1_AIS or T_ALOS alarm is normal.
Step 2 Cause 2: An upstream alarm triggers this alarm.

1. Clear the following upstream alarms immediately if there are any.
Upstream alarms that may cause a DOWN_E1_AIS alarm include R_LOS, R_LOF,
MS_AIS, AU_AIS, AU_LOP, MW_LOF, MW_LIM, R_LOF, MS_AIS, AU_AIS,
AU_LOP, MW_LOF, MW_LIM, and R_LOF.
Step 3 Cause 3: On the local NE, the receive unit of the tributary board or the system control and
cross-connect board is faulty.
1. Replace the board where the alarmed tributary unit is located. Then, check whether
the alarm is cleared.
If... Then...
The alarm persists Replace the system control and cross-connect board on the
local NE.
----End
Related Information
If EFP8 reports the alarm, the alarm parameters have the meanings listed in Table A-6.
Table A-6 Alarm Parameters of EFP8

Name Meaning
Parameter 1 0x01, indicates optical interface number.
Parameter 2, Parameter 3 Indicates the number of the path.
A.3.74 DEVICE_AUTH_FAIL
Description
The DEVICE_AUTH_FAIL alarm indicates that anti-theft verification fails on a device. This
alarm is reported if anti-theft verification is not performed or fails on the device after the anti-
theft function is enabled.

Attribute
Parameters
None

When this alarm occurs, services may be interrupted.
Possible Causes
The anti-theft function is enabled but anti-theft verification is not performed or fails on the
device.
Procedure
Step 1 Query the alarm on the NMS and check whether the anti-theft function is enabled for the
device.
1. If the anti-theft function is enabled, check whether the anti-theft information is matched.
If a match is found, use the NMS to verify this function. If a match is not found, go to
the next step.
2. If the anti-theft function is not enabled, go to the next step.
Step 2 Check whether the DEVICE_AUTH_FAIL alarm is cleared. If the alarm persists, contact
Huawei technical support engineers to handle the alarm.
----End
Related Information
None
A.3.75 DROPRATIO_OVER
Description
The DROPRATIO_OVER alarm indicates that the number of lost packets crosses the
threshold when queue congestion occurs at a port. This alarm is reported when the ratio of lost
packets on an object under performance monitoring is higher than the expected ratio.
Attribute
Minor Service alarm

Parameters
Name Meaning
Parameter 1 Indicates the direction in which traffic crosses the threshold.
l 0x00: The ratio of lost packets in the receive direction exceeds the
threshold.
l 0x01: The ratio of lost packets in the transmit direction exceeds the
threshold.

Service packet loss occurs.
Possible Causes
l Cause 1: Service configuration is incorrect.
l Cause 2: Actual traffic exceeds the configured port bandwidth or committed information
rate (CIR).
Procedure
Step 1 Cause 1: Service configuration is incorrect.
1. Check and reconfigure services according to the network plan.
Step 2 Cause 2: Actual traffic exceeds the configured port bandwidth or CIR.
1. 4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization. If traffic is
large, check whether a network storm has occurred, and eliminate the source that
illegally sends a large amount of data.
2. If the port bandwidth is too low, follow instructions in Modifying the Port Policy to
increase port bandwidth or expand the network.
----End
Related Information
If packet loss is indicated in the receive direction, check the method of handling red packets in
the traffic classification configuration. If the method of handling red packets is non-discard,
packets may not be actually lost in the receive direction.
A.3.76 E1_LOC
Description
The E1_LOC is an alarm indicating that the uplink 2M clock is lost. This alarm occurs when
the tributary board fails to extract the clock from the E1 signal.

Attribute
Parameters
None

When the E1_LOC occurs, the service is not affected.
Possible Causes
l Cause 1: The opposite NE is faulty.
l Cause 2: The wiring sequence of the cable is incorrect.
l Cause 3: The receive unit of the tributary board on the local NE is faulty.
l Cause 4: The input E1 signal has an abnormal waveform.
Procedure
Step 1 Cause 1: The opposite NE is faulty.
1. Rectify the fault on the opposite NE.
Step 2 Cause 2: The wiring sequence of the cable is incorrect.
1. Redo the cable.
Step 3 Cause 3: The receive unit of the tributary board on the local NE is faulty.
1. Replace the board where the line unit is located.
Step 4 Cause 4: The input E1 signal has an abnormal waveform.
1. Check whether any external interference causes the abnormal waveform of the E1 signal.
If... Then...
There is the external interference The fault is rectified. End the alarm handling.
There is no external interference Contact Huawei engineers.
----End
Related Information
None
A.3.77 E1_LOS
Description
The E1_LOS is an alarm indicating the loss of the E1 signal. This alarm occurs when the
tributary board detects the uplink E1 signal of all 0s.

Attribute

Parameters
None

When the E1_LOS alarm occurs, the E1 service is interrupted.
Possible Causes
l Cause 1: The cable is not connected or the cable is faulty.
l Cause 3: The tributary board on the local NE is faulty.
Procedure
Step 1 Cause 1: The cable is not connected or the cable is faulty.
1. Check whether the cable is connected properly.
If... Then...
The cable is not connected properly Connect the cable properly.
The cable is prepared incorrectly Redo the cable.

Step 3 Cause 3: The tributary board on the local NE is faulty.

1. Replace the board where the tributary unit is located.
----End
Related Information
None
A.3.78 ELAN_SMAC_FLAPPING
Description
The ELAN_SMAC_FLAPPING alarm indicates that the source MAC address learned by a
bridge-based or PW-carried E-LAN service flaps. This alarm is reported when two ports that
carry a bridge-based or PW-carried E-LAN service learn the same source MAC address.

Attribute
Major Service alarm
Parameters
Name Meaning
Parameters 1 to 6 Indicate the source MAC address that flaps.
Parameter 7, Parameter 8 Indicate the VLAN ID.
Parameter 9 Indicate the type of the port that learns the source MAC address
before the flapping occurs.
l 0x02: UNI
l 0x03: NNI

l When the ELAN_SMAC_FLAPPING alarm is generated, network storms may occur.
l When the ELAN_SMAC_FLAPPING alarm is generated, the SRV_SHUTDOWN_LD
alarm will be triggered if service shutdown upon MAC flapping is enabled on the NE.
Possible Causes
Cause: A loop exists on a UNI or NNI that carries the E-LAN service.
Procedure
Step 1 Determine the E-LAN service according to the service ID on the NMS.
Step 2 Check the E-LAN service path by referring to instructions in Detecting an E-LAN Service
Loop.
----End
Related Information
None

A.3.79 ENVHUM_SENSOR_FAIL
Description
The ENVHUM_SENSOR_FAIL is an alarm indicating that the ambient humidity sensor of
the cabinet fails.
Attribute
Parameters
None

The ambient humidity data of the PMU cannot be collected.
Possible Causes
l Cause 1: The ambient humidity sensor is faulty.
l Cause 4: The ambient humidity sensor is not installed.
Procedure
Step 1 Cause 1: The ambient humidity sensor is faulty.
1. Replace the ambient humidity sensor.
If... Then...

If... Then...


Step 4 Cause 4: The ambient humidity sensor is not installed.
1. Install the ambient humidity sensor.
----End
Related Information
None
A.3.80 ENVTEMP_SENSOR_FAIL
Description
The ENVTEMP_SENSOR_FAIL is an alarm indicating that the ambient temperature sensor
of the cabinet fails.
Attribute
Parameters
None

The ambient temperature data of the TCU cannot be collected.
Possible Causes
l Cause 1: The ambient temperature sensor is faulty.
l Cause 4: The ambient temperature sensor is not installed.
Procedure
Step 1 Cause 1: The ambient temperature sensor is faulty.
1. Replace the ambient temperature sensor.
If... Then...


If... Then...

Step 4 Cause 4: The ambient temperature sensor is not installed.

1. Install the ambient temperature sensor.
----End
Related Information
None
A.3.81 ENVTEMP1_SENSOR_FAIL
Description
The ENVTEMP1_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 1 of
the cabinet fails.
Attribute
Parameters
None

Ambient temperature data 1 of the PMU cannot be collected.
Possible Causes
l Cause 1: Ambient temperature sensor 1 is faulty.
l Cause 4: Ambient temperature sensor 1 is not installed.

Procedure
Step 1 Cause 1: Ambient temperature sensor 1 is faulty.
1. Replace ambient temperature sensor 1.
If... Then...

If... Then...

Step 4 Cause 4: Ambient temperature sensor 1 is not installed.

1. Install ambient temperature sensor 1.
----End
Related Information
None
A.3.82 ENVTEMP2_SENSOR_FAIL
Description
The ENVTEMP2_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 2 of
the cabinet fails.
Attribute

Parameters
None


Ambient temperature data 2 of the PMU cannot be collected.
Possible Causes
l Cause 1: Ambient temperature sensor 2 is faulty.
l Cause 4: Ambient temperature sensor 2 is not installed.
Procedure
Step 1 Cause 1: Ambient temperature sensor 2 is faulty.
1. Replace ambient temperature sensor 2.
If... Then...

If... Then...

Step 4 Cause 4: Ambient temperature sensor 2 is not installed.

1. Install ambient temperature sensor 2.
----End
Related Information
None
A.3.83 ERPS_IN_PROTECTION
Description
ERPS_IN_PROTECTION indicates that EPRS ring is in protection mode.

Attribute

Minor Equipment Alarm
Parameters
Name Meaning
Parameter 1 - Parameter 2 ERPS ID.
Parameter 3 DIR, indicating whether the faulty node is in the east or west
direction of the ERPS RPL-OWNER node.
l 0x01: east
l 0x00: west
Parameter 4 - Parameter 9 NODE ID, indicating the MAC address of the faulty node.

At least one node on the ring is unreachable. Services (if any) on this node may be
interrupted.
Possible Causes
Cause 1: This alarm is reported when EPRS switching is triggered by a fault on the ERPS
ring.
Procedure
Step 1 Cause 1: This alarm is reported when EPRS switching is triggered by a fault on the ERPS
ring.
1. Locate the faulty node on the ERPS ring based on the alarm parameters.
2. Locate the ERPS blocked port on the faulty node.
3. Rectify the fault.
----End
Related Information
This alarm is not reported on an ERPS V2 network where virtual channels are disabled.

A.3.84 ETH_APS_LOST
Description
The ETH_APS_LOST is an alarm indicating that the APS frame is lost. This alarm is reported
when an ingress/egress node of a bidirectional tunnel does not receive any APS frames from
the protection channel.
Attribute
Parameters
None

When this alarm occurs, the APS protection may fail.
Possible Causes
l Cause 1: The opposite NE is not configured with the APS protection.
l Cause 2: The APS protection group is deactivated.
l Cause 3: The settings of the APS protection group differ between the two ends.
l Cause 4: The service on the protection channel is interrupted.
Procedure
Step 1 Cause 1: The opposite NE is not configured with the APS protection.
1. On the NMS, check whether the opposite NE is configured with the APS protection. For
details, see Querying MPLS APS Status.
If... Then...
The opposite NE is not configured with the APS protection Go to the next step.
The opposite NE is configured with the APS protection Go to Cause 2.
2. Create a matching APS protection group on the opposite NE, and activate the APS
protocol. Check whether the alarm clears.
3. If the alarm persists, proceed to cause 4.
Step 2 Cause 2: The APS protection group is deactivated.

1. Check whether the APS protocol is activated at both ends.
If... Then...
The APS protocol is deactivated at one end Activate the APS protocol at the end.

If... Then...
The APS protocol is activated at both ends Go to Cause 3.
2. Check whether the alarm clears. If the alarm persists, go to Cause 3.
Step 3 Cause 3: The settings of the APS protection group differ between the two ends.
1. On the NMS, check whether the settings of the APS protection group are the same at the
two ends. If the settings differ between the two ends, change them to the same. Then,
deactivate and activate the APS protection group at the two ends.
2. Check whether the alarm clears. If the alarm persists, go to Cause 4.
Step 4 Cause 4: The service on the protection channel is interrupted.

1. Check whether the protection channel reports an alarm related to signal loss or signal
degrade, such as ETH_LOS. If yes, clear the alarm immediately.
----End
Related Information
None
A.3.85 ETH_APS_PATH_MISMATCH
Description
The ETH_APS_PATH_MISMATCH is an alarm indicating that the working and protection
paths of the APS protection group differ between the two ends. This alarm is reported when
the working and protection paths of one APS protection group at one end are different from
those at the other end.
Attribute
Parameters
None

When this alarm occurs, service protection fails.
Possible Causes
l Cause 1: The configured working and protection paths differ between the two ends.
l Cause 2: The physical link is connected incorrectly.

Procedure
Step 1 Cause 1: The configured working and protection paths differ between the two ends.
1. Check whether the APS settings at the two ends are the same. For details, see Querying
MPLS APS Status.
2. If the APS settings are different, change the settings to the same. Then, deactivate and
activate the APS protection group at the two ends. Then, check whether the alarm clears.
3. If the alarm persists, go to Cause 2.
Step 2 Cause 2: The physical link is connected incorrectly.

1. Check whether the fiber or cable is correctly connected between the two ends. If not,
connect the fiber or cable properly.
----End
Related Information
None
A.3.86 ETH_APS_SWITCH_FAIL
Description
The ETH_APS_SWITCH_FAIL is an alarm of a protection switching failure. This alarm is
reported when the request signal in the transmitted Automatic Protection Switching (APS)
frame is different from the bridge signal in the received APS frame and this symptom lasts for
50 ms.
Attribute
Parameters
None

When this alarm occurs, service protection fails.
Possible Causes
Cause 1: The settings of the APS protection group differ between the two ends.Cause 2: APS
fails due to other reasons.
Procedure
Step 1 Cause 1: The settings of the APS protection group differ between the two ends.

1. Change the settings to the same. For details, see Creating an MPLS APS Protection
Group. Then, deactivate and activate the APS protection group at the two ends.
Step 2 Cause 2: APS fails due to other reasons.
1. Reactivate APS protection at both ends.
----End
Related Information
None
A.3.87 ETH_APS_TYPE_MISMATCH
Description
The ETH_APS_TYPE_MISMATCH is an alarm of protection scheme mismatch. This alarm
is reported when the information in the received Automatic Protection Switching (APS) frame
is different from the APS settings at the local end.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the specific difference.
l 0x01: Indicates that the switching type is different.
l 0x02: Indicates that the switching direction is different.
l 0x03: Indicates that the revertive mode is different.

This alarm may cause the APS protection failure, and therefore the service protection fails.
Possible Causes
l Cause 1: The switching type is different.
l Cause 2: The switching direction is different.
l Cause 3: The revertive mode is different.

Procedure
Step 1 Determine the possible cause of the alarm according to the alarm parameters.
1. Change the settings of the APS protection group to the same at the two ends. For details,
see Querying MPLS APS Status. Then, deactivate and activate the APS protection group
at the two ends.
----End
Related Information
None
A.3.88 ETH_AUTO_LINK_DOWN
Description
The ETH_AUTO_LINK_DOWN alarm indicates that an Ethernet port is automatically
switched to the link down state upon a fault detected by link-state pass through (LPT).
Attribute
Parameters
None

The alarmed port cannot carry any services and a switchover may occur on external
equipment connected to the port.
Possible Causes
l Cause 1: The radio link connected to the alarmed port is faulty.
l Cause 2: The opposite service access port is faulty.
Procedure
Step 1 Cause 1: The radio link connected to the alarmed port is faulty.
1. Check for MW_LIM, MW_LOF, and MW_RDI alarms on the local and opposite
microwave ports, and clear them if any. Then, check whether the
ETH_AUTO_LINK_DOWN alarm is cleared.
Step 2 Cause 2: The opposite service access port is faulty.
1. Check for ETH_LOS alarm, and optical-module-related alarms on the opposite port, and
clear them if any.
----End

Related Information
None
A.3.89 ETH_CFM_AIS
Description
The ETH_CFM_AIS is an alarm indicating that an AIS packet is received by the local MEP.
This alarm is reported when the system receives an AIS packet, which indicates that the
Ethernet server layer is faulty.
Attribute

Parameters
Name Meaning
Parameters 1 to 4 Indicate the ID of the port that reports the alarm.
(port)
Parameters 5 and 6 Indicate the VLAN ID of the MEP.
(VLAN ID)
Parameter 7 Indicate the direction of the local MEP.
(direction) l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (level) Indicates the maintenance domain (MD) level of the local MEP.
l 0x00: operator MEP level (low)
l 0x01: operator MEP level (medium)
l 0x02: operator MEP level (high)
l 0x03: provider MEP level (low)
l 0x04: provider MEP level (high)
l 0x05: consumer MEP level (low)
l 0x06: consumer MEP level (medium)
l 0x07: consumer MEP level (high)
NOTE
Consumer indicates the customer, provider indicates the supplier, and operator
indicates the carrier.


l When this alarm occurs, the loopback (LB) and link trace (LT) detection functions are
disabled.
l In addition, the service between the relevant standard MEPs may be interrupted.
Possible Causes
Cause 1: The upstream NE detects a fault at the Ethernet server layer.
Procedure
Step 1 Check whether there is any defect in the Ethernet server layer between source and sink NE.
----End
Related Information
None
A.3.90 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs when
the system fails to receive the CCM packet from the remote MEP in 3.5 connectivity check
(CC) periods successively.
Attribute

Parameters
Name Meaning
Parameters 1 to 4 Indicates the ID of the alarmed port.
(port)
Parameters 5 and 6 Indicates the VLAN ID of the MEP.
(VLAN ID)

Name Meaning
Parameter 7 Indicates the direction of the local MEP.
(direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
Parameter 8 (level) Indicates the MD level of the local MEP.
NOTE
Consumer indicates the user, provider indicates the supplier, and operator
Parameter 9, Indicates the ID of the remote MEP.

Parameter 10
(RMEPID)

l When the ETH_CFM_LOC alarm occurs, the LB and LT detection functions of Ethernet
service OAM are unavailable.
l The service between the relevant standard MEPs may be interrupted.
Possible Causes
l Cause 1: The line between the local standard MEP and the remote standard MEP is
interrupted.
l Cause 2: The Ethernet service in the maintenance association (MA) to which the local
MEP belongs is faulty.
l Cause 3: Serious congestion occurs on the network.
Procedure
Step 1 Cause 1: The line between the local standard MEP and the remote standard MEP is
interrupted.
1. Check whether the physical links (such as network cables and fibers) between the
standard MEPs are connected properly.
If... Then...
The physical links are connected improperly Connect the physical links properly.
The physical links are connected properly Go to Cause 2.

Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP
belongs is faulty.
1. Check whether Ethernet service in the maintenance association (MA) to which the local
MEP belongs is configured correctly.
If... Then...
The service is configured Modify the configuration of the service to ensure
incorrectly consistency at two ends.
The service is configured Go to Cause 3.
correctly
Step 3 Cause 3: Serious congestion occurs on the network.

1. Check the utilization of bandwidth. If the bandwidth is exhausted, increase the
bandwidth or eliminate any source that transmits a large amount of invalid data.
----End
Related Information
The Table A-7 describes the meanings of the parameters in the ETH_CFM_LOC alarm
reported by the EoS/EoPDH plane.
Table A-7 Alarm Parameters

Name Meaning
Parameter 1 to Parameter 4 MD
Parameter 5 to Parameter 8 MA
Parameter 9, Parameter 10 MEP ID
Parameter 11 to Parameter 14 Indicates the ID of the alarmed port.

When these parameters indicate the
VCTRUNK ID, parameter values = (0x01 -
0x10) + 0x80.
Parameter 15, Parameter 16 Indicates the VLAN ID of the MEP.

l 0x00: The port is direction insensitive.

Name Meaning
Parameter 18 Indicates the MD level of the local MEP.

NOTE
Consumer indicates the user, provider indicates
the supplier, and operator indicates the carrier.
Parameter 19, Parameter 20 Indicates the ID of the remote MEP.

NOTE
If the alarmed port is a VCTRUNK, these
parameters are not supported.
A.3.91 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating an incorrect connection. This alarm
occurs when the system receives the CCM packet whose MA mismatches or whose priority is
lower.
Attribute
Parameters
Name Meaning
(port)
(VLAN ID)

Name Meaning
NOTE

When the ETH_CFM_MISMERGE alarm occurs, the service between the relevant standard
MEPs may be interrupted, and the data flow may be routed incorrectly.
Possible Causes
l Cause 1: The names of the maintenance domain and the maintenance alliance that the
standard MEPs correspond to are inconsistent.
l Cause 2: The levels of the maintenance domains that the standard MEPs correspond to
are different.
l Cause 3: The physical connection is incorrect.
Procedure
Step 1 Cause 1: The names of the maintenance domain and the maintenance alliance that the
standard MEPs correspond to are inconsistent.
1. Check whether the names of the maintenance domain and the maintenance alliance that
the standard MEPs correspond to are consistent.
If... Then...
The names are inconsistent Set the other names of maintenance domain and
maintenance alliance to ensure consistency at both ends.
The names are consistent Go to Cause 2.
Step 2 Cause 2: The levels of the maintenance domains that the standard MEPs correspond to are
different.

1. Check whether the MD levels of the standard MEPs are the same.
If... Then...
The levels are different Set the MD levels again to ensure consistency at both ends.
The levels are the same Go to Cause 3.
Step 3 Cause 3: The physical connection is incorrect.

1. Check the physical connection of the Ethernet service route and rectify the fault of the
physical connection if any.
----End
Related Information

Name Meaning

0x10) + 0x80.


Name Meaning

NOTE
A.3.92 ETH_CFM_RDI
Description
The ETH_CFM_RDI is an alarm indicating the CCM packet with RDI received from the
remote MEP. This alarm occurs when the system receives the CCM packet with RDI from the
remote maintenance end point (MEP).
Attribute
Parameters
Name Meaning
(port)
(VLAN ID)

Name Meaning
NOTE
Parameter 9, Indicates the ID of the remote MEP.

Parameter 10
(RMEPID)

l When the ETH_CFM_RDI alarm occurs, the loopback (LB) and link trace (LT) detection
functions of Ethernet service OAM are unavailable.
l The service between the relevant standard MEPs may be interrupted.
Possible Causes
l Cause 1: The remote MEP fails to receive the correct CCM packet.
Procedure
Step 1 Cause 1: The remote MEP fails to receive the correct CCM packet.
1. Determine the alarmed port according to the alarm parameter.
2. Check whether the remote MEP that is connected to the port reports the
ETH_CFM_MISMERGE, ETH_CFM_UNEXPERI, or ETH_CFM_LOC alarm.
----End
Related Information


Name Meaning

0x10) + 0x80.


NOTE
Parameter 19, Parameter 20 Indicates the ID of the remote MEP.

NOTE
If the alarmed port is a VCTRUNK, these
parameters are not supported.
A.3.93 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs
when the system receives invalid CCM packets.

Attribute
Parameters
Name Meaning
(port)
(VLAN ID)
NOTE

l When the ETH_CFM_UNEXPERI alarm occurs, the LB and LT detection functions of
Ethernet service OAM are unavailable.
l The service may become abnormal due to the loop.
Possible Causes
l Cause 1: No remote MEP is configured.
l Cause 2: The configuration of the MEPs at both ends is inconsistent. For example, the
connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.

l Cause 3: The service is looped back and the looped packet is received.
Procedure
Step 1 Cause 1: No remote MEP is configured.
1. Check whether the remote MEP is configured. If not, configure the remote MEP first.
Step 2 Cause 2: The configuration of the MEPs at both ends is inconsistent. For example, the
connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.
1. Check whether the CC periods set at the MEPs are the same.
If... Then...
The CC periods are different Change the CC periods to ensure consistency at both
ends.
The CC periods are the same Go to the next step.
2. Check whether the IDs of the MEPs in the maintenance domain are in conflict.
If... Then...
The IDs are in conflict Change the conflicting IDs.
The IDs are not in conflict Go to Cause 3.
Step 3 Cause 3: The service is looped back and the looped packet is received.
1. Check whether any loop exists at each IP port of the service trail. If yes, release the loop
and clear the alarm.
----End
Related Information
Name Meaning

0x10) + 0x80.

Name Meaning


NOTE
A.3.94 ETH_EFM_DF
Description
The ETH_EFM_DF is an alarm indicating negotiation failure. This alarm occurs when the
point-to-point OAM protocol negotiation fails at the Ethernet port.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the reason why the negotiation fails.
l 0x01: The local link is faulty.

l 0x02: The local end fails to receive any OAM packets in a specified period.
l 0x03: The OAM settings of the opposite end do not meet the requirements
of the local end.
l 0x04: The OAM settings of the local end do not meet the requirements of
the opposite end.

When the ETH_EFM_DF alarm occurs, the service at the alarmed port may be interrupted.
Possible Causes
l Cause 1: The physical port of the local end is faulty.
l Cause 2: The point to point OAM protocol is not enabled at the opposite end.
l Cause 3: The OAM configuration at both ends is inconsistent.
Procedure
Step 1 Cause 1: The physical port of the local end is faulty.
1. Check whether the physical port is faulty. If yes, replace the board where the Ethernet
port is located.
Step 2 Cause 2: The point to point OAM protocol is not enabled at the opposite end.
1. Enable the point to point OAM protocol at the opposite end.
Step 3 Cause 3: The OAM configuration at both ends is inconsistent.

1. Reconfigure the point to point OAM protocol and ensure the consistency at both ends.
----End
Related Information
None
A.3.95 ETH_EFM_EVENT
Description
The ETH_EFM_EVENT is an alarm indicating the performance event reported on the
opposite NE. This alarm occurs when the local end receives the link error indication packet
(OAMPDUM) from the opposite end.

Attribute

Parameters
Name Meaning
Parameter 1 Indicates the type of the link event.
l 0x01: errored symbol period.
l 0x02: errored frame.
l 0x03: errored frame period.
l 0x04: errored frame seconds summary.

When the ETH_EFM_EVENT alarm occurs, the service at the alarmed port may be
interrupted.
Possible Causes
l Cause 1: The physical port at the local end is faulty.
l Cause 2: The equipment at the opposite end is faulty.
port).
electrical port).
Procedure
Step 1 Cause 1: The physical port at the local end is faulty.
1. Check whether the physical port is faulty. If yes, replace the board where the Ethernet
port is located.
Step 2 Cause 2: The equipment at the opposite end is faulty.

1. Rectify the fault of the equipment at the opposite end.
Performance Events.

If... Then...
±3 dB)
If... Then...
The alarm persists Go to Cause 1 or 2.
port).
If... Then...
The alarm persists Go to Cause 1 or 2.
----End
Related Information
None
A.3.96 ETH_EFM_LOOPBACK
Description
The ETH_EFM_LOOPBACK is an alarm indicating the loopback. This alarm occurs when
the local end initiates a loopback or responds to a loopback request from the opposite end.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the state of the loopback.
l 0x01: The local end initiates a loopback.
l 0x02: The local end responds to a loop request from the opposite end.

When the ETH_EFM_LOOPBACK alarm occurs, the service at the alarmed port is looped
back.
Possible Causes
l Cause 1: The local end initiates a loopback.
l Cause 2: The opposite end initiates a loopback.
Procedure
Step 1 Cause 1: The local end initiates a loopback.
1. According to the alarm parameter, it is determined that the local end initiates a loopback.
Determine the causes of the loopback initiated at the local end and release the loopback
as soon as possible.
Step 2 Cause 2: The opposite end initiates a loopback.

1. According to the alarm parameter, it is determined that the opposite end initiates a
loopback. Determine the causes of the loopback initiated at the opposite port and release
the loopback as soon as possible.
----End
Related Information
None
A.3.97 ETH_EFM_REMFAULT
Description
The ETH_EFM_REMFAULT is an alarm indicating the fault on the opposite NE. This alarm
occurs when the local end receives the fault indication packet (OAMPDUM) from the
opposite end.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the fault type at the opposite end.
l 0x01: link fault.
l 0x02: dying gasp.
l 0x03: critical event.

When the ETH_EFM_REMFAULT alarm occurs, the service at the alarmed port may be
interrupted.
Possible Causes
l Cause 1: The opposite NE is reset.
Procedure
Step 1 Cause 1: The opposite NE is reset.
1. Check whether the opposite NE is reset frequently.
If... Then...
The opposite NE is reset frequently Reset the opposite NE, and the alarm is
cleared.
The opposite NE is not reset Rectify the fault on the opposite NE.
frequently

----End
Related Information
None
A.3.98 ETH_LINK_DOWN
Description
The ETH_LINK_DOWN alarm indicates that the link connected to an Ethernet port is
interrupted.

Attribute
Parameters
None

The services on the alarmed port are interrupted.
Possible Causes
l Cause 1: The alarmed port and its opposite port work in different modes.
l Cause 2: The network cable is not correctly connected to the alarmed port.
l Cause 4: The local NE is faulty.
Procedure
Step 1 Cause 1: The alarmed port and its opposite port work in different modes.
1. Check for the PORTMODE_MISMATCH alarm by referring to Browsing Current
Alarms.
If... Then...
The PORTMODE_MISMATCH alarm exists Clear it.
No PORTMODE_MISMATCH alarms exist Go to Cause 2.
Step 2 Cause 2: The network cable is not correctly connected to the alarmed port.
1. Check the network cable connected to the alarm port.
If... Then...
The network cable is loose or damaged Reconnect or replace the network
cable.
The network cable is intact and correctly Go to Cause 3.
connected to the alarm port
Step 3 Cause 3: The local NE is faulty.

1. Check whether the alarmed port is functional.
If... Then...
The port is faulty Replace the board where the port resides. For details, see the
Part Replacement.
The port is functional Go to Cause 4.


1. Check whether the opposite NE is faulty.
----End
Related Information
None
A.3.99 ETH_LOS
Description
The ETH_LOS alarm indicates the loss of Ethernet port connection.
Attribute

Parameters
None

When the ETH_LOS alarm occurs, the service at the alarmed port is interrupted.
Possible Causes
l Cause 1: The negotiation fails because the transmit port and receive port work in
different modes or the encapsulation modes of 10GE interfaces are different.
l Cause 2: The optical module types on the transmit end and receive end are different.
l Cause 3: The cable or fiber is faulty.
l Cause 4: The local receive end is faulty.
l Cause 5: The remote transmit end is faulty.
Procedure
Step 1 Cause 1: The negotiation fails because the transmit port and receive port work in different
modes or the encapsulation modes of 10GE interfaces are different.
1. Check whether the transmit port and receive port work in the same mode or whether the
encapsulation modes of 10GE interfaces are consistent.

If... Then...
The transmit port and receive Correctly set the working modes of the transmit
port work in different modes port and receive port.
Set the encapsulation modes of 10GE interfaces at
both ends to be consistent.
The transmit port and receive Go to Cause 2.

port work in the same mode
Step 2 Cause 2: The optical module types on the transmit end and receive end are different.
1. Query the board manufacturing information report, and check whether the types of
SFP optical modules on both ends are the same.
If... Then...
No Replace the optical modules with the same type of optical modules.
Yes Go to Cause 3.
Step 3 Cause 3: The cable or fiber is faulty.

1. Check the network cable or fiber jumper connected to the alarmed port.
If... Then...
The network cable is loose or damaged Connect the network cable properly or
replace the damaged network cable.
The connector of the fiber jumper is Clean the connector.
dirty
The connector or fiber is damaged Insert the connector properly or replace the
damaged fiber jumper.
The connection is normal Go to Cause 3.
Step 4 Cause 4: The local receive end is faulty.

1. Check whether any fault occurs on the alarmed port.
If... Then...
The equipment is faulty Replace the alarmed board on the local.
The equipment is normal Go to Cause 4.
Step 5 Cause 5: The remote transmit end is faulty.

1. Check whether any fault occurs on the equipment interconnected with the alarmed port.
----End
Related Information
None

A.3.100 ETH_NO_FLOW
Description
The ETH_NO_FLOW is an alarm indicating that the Ethernet port has no flow. This alarm is
reported when an enabled Ethernet port is in link up state but has no flow.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the MAC port number.
Parameter 2, Indicate the path ID.
Parameter 3
Parameter 2 indicates the most significant bits and the value is
always 0x00. Parameter 3 indicates the least significant bits and the
value is always 0x01.
Parameter 4 Indicates the direction in which the flow is unavailable.

l 0x00: Rx direction.
l 0x01: Tx direction.

When this alarm occurs, it indicates that the alarmed port has no flow.
Possible Causes
l Cause 1: The port is enabled and in link up state, but is configured with no service.
l Cause 2: The port is enabled and in link up state, but does not transmit any packet due to
the service fault at the local end.
l Cause 3: The port is enabled and in link up state, but does not receive any packet due to
the service fault at the remote end.
Procedure
Step 1 Determine the MAC port number, alarmed board, and cause according to the parameters.

Step 2 Cause 1: No services are configured.

1. Configure the Ethernet service.
Step 3 Cause 2: No services are available.
If... Then...
No services are available in the transmit Check whether the service is normal at the local
direction end.
No services are available in the receive Check whether the service is normal at the
direction remote end.
----End
Related Information
None
A.3.101 ETH_PWR_SUPPLY_FAIL
Description
The ETH_PWR_SUPPLY_FAIL alarm indicates a power outputting failure of an Ethernet
port. This alarm is reported when an Ethernet port is enabled with the PE function but outputs
no power.
Attribute
Parameters
None

When this alarm occurs, the NE that is connected to the Ethernet port outputs no power.
Possible Causes
l Cause: The board is faulty.
Procedure
Step 1 Cause: The board is faulty.
1. 6.7 Replacing the Ethernet Interface Board.
----End

Related Information
None
A.3.102 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL alarm indicates a discovery failure when the point-to-
point ETH-OAM function is enabled. This alarm occurs when the OAM function is enabled at
a port of a board and the negotiation between the port and the opposite equipment fails.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the alarmed port.
Parameter 2, The values are always 0x00 0x01.

Parameter 3
Parameter 4 Indicates the reason why the negotiation fails.

l 0x01: A fault occurs at the local receive link.
l 0x02: The local end fails to transmit OAM packets.
l 0x03: The OAM packets from the opposite end are not received.
l 0x04: The OAM configuration of the opposite end does not meet the
requirements of the local end.
l 0x05: The OAM configuration of the local end does not meet the
requirements of the opposite end.
l 0x06-0xff: other unknown reasons.

The OAM function based on IEEE 802.3ah is unavailable.

Possible Causes
l Cause 1: The physical port of the local end is faulty.
l Cause 2: The P2P OAM protocol is not enabled at the opposite end.
l Cause 3: The OAM configuration at both ends is inconsistent.
Procedure
Step 1 Cause 1: The physical port of the local end is faulty.
1. Check whether the physical port is faulty. If yes, replace the alarmed board.
Step 2 Cause 2: The P2P OAM protocol is not enabled at the opposite end.
1. Enable the P2P OAM protocol at the opposite end. For details, see Enabling the OAM
Auto-Discovery Function.
Step 3 Cause 3: The OAM configuration at both ends is inconsistent.

1. Reconfigure the P2P OAM protocol and ensure the consistency at both ends. For details,
see Enabling the OAM Auto-Discovery Function.
----End
Related Information
None
A.3.103 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that the point-to-point Ethernet
OAM detects a critical fault at the remote end. This alarm occurs when a port with the OAM
function enabled receives the OAM packets that contain critical fault information from the
opposite end.
Attribute
Parameters
Name Meaning

Name Meaning
Parameter 2, The values are always 0x00 0x01.

Parameter 3
Parameter 4 Indicates the type of the fault.

l 0x01: A link fault occurs at the port of the opposite end.
l 0x02: Irrecoverable problems such as the power failure occur at
the opposite end.
l 0x03-0xff: other faults.

When this alarm occurs, the services on the link may be interrupted.
Possible Causes
l Cause 1: A link fault occurs at the remote MEP.
l Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.
l Cause 3: Other faults occur at the remote MEP.
Procedure
Step 1 Determine the fault type according to Parameter 4.
If... Then...
The value of Parameter 4 is 0x01 Go to Cause 1.
Parameter 4 is a value from 0x03 to 0xff. Go to Cause 3.
Step 2 Cause 1: A link fault occurs at the remote MEP.

1. Handle the ETH_LOS alarm at the remote port.
Step 3 Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.
1. Handle the problems such as power failure at the remote MEP, and recover the power
supply to the remote MEP.
Step 4 Cause 3: Other faults occur at the remote MEP.

1. Contact Huawei technical support engineers.
----End
Related Information
None

A.3.104 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating that a remote loopback is initiated when
the point-to-point Ethernet OAM function is enabled. This alarm occurs when the local
equipment initiates a remote loopback or responds to the remote loopback initiated by the
opposite equipment.
Attribute
Parameters
Name Meaning
Parameter 2, Parameter 3 The values are always 0x00 0x01.
Parameter 4 l 0x01: The loopback is initiated.

l 0x02: The loopback is responded.

The services are looped back between the local equipment and the opposite equipment. The
services and other protocol packets are interrupted.
Possible Causes
l Cause 1: The local end issues a loopback command and the opposite end responds to the
command.
l Cause 2: The opposite end issues a loopback command and the local end responds to the
command.
Procedure
Step 1 Check the alarm on the NMS and determine the type of loopback according to the alarm
parameters.

If... Then...
Step 2 Cause 1: The local end issues a loopback command and the opposite end responds to the
command.
1. Determine the causes of the loopback at the local end and release the loopback.
Step 3 Cause 2: The opposite end issues a loopback command and the local end responds to the
command.
1. Determine the causes of the loopback at the opposite end and release the loopback.
----End
Related Information
None
A.3.105 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD alarm indicates that the point-to-point Ethernet-OAM detects the
degradation of remote Ethernet performance. This alarm occurs when a port with the OAM
function enabled receives link event notification packets from the opposite end.
Attribute
Parameters
Name Meaning

Name Meaning
Parameter 4 Indicates the type of the received link event.

l 0x01: errored frame event
l 0x02: errored frame period event
l 0x03: errored frame second event

When this alarm occurs, the performance of services degrades.
Possible Causes
l Cause 1: The link event notification function is enabled at the opposite end.
l Cause 2: The link performance thresholds of the opposite end are inappropriate.
l Cause 3: The link performance deteriorates.
Procedure
Step 1 Cause 1: The link event notification function is enabled at the opposite end.
1. Check whether the link event notification function is enabled at the opposite end.
If... Then...
If yes Disable the link event notification function at the opposite end.
If not Go to Cause 2.
Step 2 Cause 2: The link performance thresholds of the opposite end are inappropriate.
1. Check whether the link performance thresholds of the opposite end are appropriate.
If... Then...
If not Set the thresholds to appropriate values.
If yes Go to Cause 3.
Step 3 Cause 3: The link performance deteriorates.

1. Improve the link performance at the opposite end so that the opposite end does not send
any link event notification packet to the local end. Then, the alarm at the local end is
cleared automatically.
----End
Related Information
None

A.3.106 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs
the point-to-point OAM protocol. This alarm occurs when the MAC port of a board receives
the OAM protocol packet sent by the port itself or the board after the loop detection function
is enabled.
Attribute
Major Environmental alarms
Parameters
Name Meaning
Parameter 1 This parameter has a fixed value of 0x01.
Parameter 2, Parameter 3 Indicate the VCTRUNK ID.
Parameter 4 Indicates the loopback type.

l 0x01: The port is self-looped.
l 0x02: The board is self-looped.
l 0x03-0xff: unknown types.
l 0x04: The MAC address flaps.
Parameter 5 Indicates the ID of the virtual bridge whose MAC address flaps.

When the ETHOAM_SELF_LOOP alarm occurs, a network storm may occur due to the
loopback.
Possible Causes
l Cause 1: The cable connected to the port is self-looped, or the port is connected to a
LAN that has a loopback, or the PHY/MAC loopback is manually configured at the port.
l Cause 2: Two ports of the board are connected through cables or two ports of the board
are connected to the same LAN.

Procedure
Step 1 Determine the loopback type according to Parameter 1, and then handle the loopback
accordingly.
If... Then...
Step 2 Cause 1: The cable connected to the port is self-looped, or the port is connected to a LAN that
has a loopback, or the PHY/MAC loopback is manually configured at the port.
If... Then...
The PHY/MAC loopback is Manually release the PHY/MAC loopback (or wait five
manually configured at the port minutes for the automatic release by the NE if the
automatic loopback release function is enabled on the
NE). Then, the self-loop is released.
The cable connected to the port Connect the cable properly to release the self-loop.
is self-looped
The port is connected to a LAN Release the loopback on the LAN, or break the
that has a loopback connection between the port and the LAN, to release the
self-loop.
Step 3 Cause 2: Two ports of the board are connected through cables or two ports of the board are
connected to the same LAN.
1. Check whether two ports of the board are connected through cables or whether two ports
of the board are connected to the same LAN.
If... Then...
The two ports are connected Disconnect the cables to release the self-loop.
through cables
The two ports are connected to the Break the connection between a port and the
same network LAN to release the self-loop.
----End
Related Information
None
A.3.107 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP alarm indicates that a VCTRUNK port is looped back
when the point-to-point Ethernet OAM function is enabled. This alarm occurs when the
loopback detection function is enabled and the VCTRUNK port receives the OAM protocol
packets transmitted by the port itself or the board where the VCTRUNK port resides.

Attribute
Major Environment alarm
Parameters
Name Meaning
Parameter 1 This parameter has a fixed value of 0x01.
Parameter 2, Parameter 3 Indicate the VCTRUNK ID.
Parameter 4 Indicates the loopback type.

l 0x02: The board is self-looped.
l 0x03-0xff: unknown types.
l 0x04: The MAC address flaps.
Parameter 5 Indicates the ID of the virtual bridge whose MAC address flaps.

If the function of automatic shutdown in the case of a self-loop is enabled at the alarmed port,
the services at the alarmed port are interrupted. Otherwise, a network storm may occur.
Possible Causes
l Cause 1: A loopback occurs on the lines connected to one VCTRUNK.
l Cause 2: The lines connected to two VCTRUNKs on the same board are interconnected.
Procedure
Step 1 Check the alarm on the NMS and determine the type of loopback according to the alarm
parameters.
If... Then...
Step 2 Cause 1: The port is self-looped.

1. Release the loopback at the port.

2. Reconfigure the lines connected to the VCTRUNK port and ensure that the port is not
self-looped.
Step 3 Cause 2: The board is self-looped.
1. Reconfigure the lines connected to the VCTRUNK ports and ensure that the lines
connected to any two VCTRUNK ports on the same board are not interconnected.
----End
Related Information
None
A.3.108 EX_ETHOAM_CC_LOS
Description
The EX_ETHOAM_CC_LOS is an alarm indicating the loss of periodic connectivity check
(CC) packets. This alarm occurs when the sink MEP fails to receive CC packets from the
same source MEP in a period (3.5 transmission periods of CC packets at the source MEP).
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicates the ID of the remote MEP.
Parameter 5 to Parameter 8 Indicates the ID of the local MEP.
Parameter 9, Parameter 10 Indicates the ID of the alarmed port.

l PORT number, Parameter 9 is 0x00.
l VCTRUNK number, Parameter 9 is 0x80.
Parameter 14 to Parameter 17 Indicates the ID of the remote MEP.

Name Meaning
Parameter 18 - Parameter 21 Indicates the ID of the local MEP.

A unidirectional connectivity failure occurs in the Ethernet service between two MEPs.
Possible Causes
l Cause 1: The line between two MEPs is interrupted.
l Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.
l Cause 3: The services between two MEPs are congested or interrupted.
Procedure
Step 1 Cause 1: The line between two MEPs is interrupted.
1. Check whether the physical links (such as network cables or optical fibers) that carry
services between the two MEPs are correctly connected.
If... Then...
If not Re-connect the cables to rectify the faults on physical links.
Step 2 Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.
1. Check whether the Ethernet services in the MA to which the alarmed MEP belongs are
configured correctly.
If... Then...
If not Modify the configuration to ensure consistency at both ends.
Step 3 Cause 3: The services between two MEPs are congested or interrupted.
----End
Related Information
None
A.3.109 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the conflict of MPIDs. This
alarm occurs when two MEPs in one MD have the same maintenance point identity (MPID)
and one MEP receives the packets from the other MEP.

Attribute
Major Environment alarm
Parameters
Name Meaning
Parameter 5, Parameter 6 Indicates the ID of the alarmed port.

l PORT number, Parameter 9 is 0x00.
l VCTRUNK number, Parameter 9 is 0x80.

MPIDs must be unique on a network. When this alarm occurs, the LB and LT functions are
abnormal and OAM packets are received incorrectly.
Possible Causes
Cause 1: At least two MEPs in an MD have the same MPID.
Procedure
Step 1 Cause 1: At least two MEPs in an MD have the same MPID.
1. Check the alarm on the NMS and determine the associated MP ID according to the alarm
parameters.
2. Query the information about the MEP. Delete the incorrect MEPs and create MEPs with
unique MP IDs.
----End
Related Information
None

A.3.110 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm of the loss of the external clock source.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: the first external clock source
l 0x02: the second external clock source

l When the EXT_SYNC_LOS alarm occurs, if only the external clock source and internal
clock source are configured in the clock source priority list, the NE traces the internal
clock source after the external clock source is lost and enters the free-run state 24 hours
later. The system saves 24-hour holdover data. The system works in 24-hour holdover
mode instead of permanent holdover mode.
l If another valid clock source of higher priority and good quality is configured in the
clock source priority list, however, the clock protection switching occurs.
Possible Causes
Cause 1: The external clock source is configured in the clock source priority list, but the
external clock source cannot be detected or become invalid.
Procedure
Step 1 Cause 1: The external clock source is configured in the clock source priority list, but the
external clock source cannot be detected or become invalid.
1. Check whether the equipment that provides the external clock source is faulty.
If... Then...
The equipment is faulty Rectify the fault.
The equipment is normal Go to the next step.
2. Check whether the cable that connects the external clock source is normal.

If... Then...
The cable is abnormal Replace the cable.
The cable is normal Replace the alarmed board.
----End
Related Information
None
A.3.111 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm of the loss of the external time source.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: link failure on a port

l 0x02: unchanged second value in time of day (TOD) information, or
unavailable second pulse, or degraded second pulse
l 0x03: CRC errors in TOD information

The time of a local NE cannot be synchronized to the external time device to which the NE's
enabled external time port is connected.
Possible Causes
l Cause 1: The link at a port is faulty.
l Cause 2: The external time device is faulty.
Procedure
Step 1 Cause 1: The link at a port is faulty.

1. Check cable connections. If cables are incorrectly connected, connect the cables again.
Step 2 Cause 2: The external time device is faulty.

1. Check whether the external time device is faulty.
----End
Related Information
None
A.3.112 FAN_AGING
Description
The FAN_AGING is an alarm of the aged fan. This alarm occurs when the fan rotates at a
speed lower than eighty percent of the nominal speed.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the number of the alarmed fan.

When this alarm occurs, the temperature of the NE is too high and impacts the long-term
operation of the NE.
Possible Causes
Cause 1: The fan is aged.
Procedure
Step 1 Cause 1: The fan is aged.
1. Replace the fan.
----End

Related Information
None
A.3.113 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan is faulty.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the fan.

When the FAN_FAIL alarm occurs, the heat dissipation of the system is affected.
After an alarm is reported, clear it immediately. Otherwise, services may be interrupted or

equipment may be damaged.
When a fan is faulty, perform the following operations:
l Replace the faulty fan with one that works properly within a period of 96 hours if the
ambient temperature ranges from 0°C to 40°C.
l Replace the faulty fan with one that works properly within a period of 24 hours if the
ambient temperature is higher than 40°C.
When multiple fans are faulty, replace them immediately.
Possible Causes
l Cause 1: The board and the backplane are connected improperly.
l Cause 2: Fan failure occurs.
Procedure
Step 1 Cause 1: The board and the backplane are connected improperly.
1. Remove the fan board. Clean the dust on the fan and reinsert the fan board.

If... Then...
The alarm is cleared after the board is removed The fault is rectified. End the
and inserted alarm handling.
The alarm persists after the board is removed Go to Cause 2.
and inserted
Step 2 Cause 2: Fan failure occurs.

1. Replace the alarmed fan board.
----End
Related Information
None
A.3.114 FCS_ERR
Description
The FCS_ERR is an alarm indicating the errors of frame check sequence (FCS). This alarm
occurs when a board detects FCS errors in the received frames.
Attribute

Parameters
Name Meaning
Parameter 2, Parameter 3 Indicate the VCTRUNK number where the alarm occurs.

When the FCS_ERR alarm occurs, if the encapsulation protocols or encapsulation parameters
are inconsistent at both ends of Ethernet services, the services may have errors and even
become interrupted.

Possible Causes
l Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at
both ends of services.
l Cause 2: Service channels have errors.
Procedure
Step 1 Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both
ends of services.
1. Check whether the encapsulation protocols or encapsulation parameters are consistent at
both ends of services.
If... Then...
The protocols are inconsistent Correct the configuration data.
The protocols are consistent Go to the next step.
2. Check whether the encapsulation parameters are consistent at both ends of services.
If... Then...
The parameters are inconsistent Correct the configuration data.
The parameters are consistent Go to the next step.
Step 2 Cause 2: Service channels have errors.

1. Check whether any error alarm or performance event occurs on the board that carries the
services.
If... Then...
Yes Handle the alarm or performance event.
No Go to the next step.

----End
Related Information
None
A.3.115 FDBSIZEALM_ELAN
Description
The FDBSIZEALM_ELAN alarm indicates that items listed in an E-LAN forwarding table
are all used. This alarm is reported when the number of actual items in the MAC address table
for the E-LAN service is greater than Address Detection Upper Threshold. This alarm is
cleared automatically when the number of items in the MAC address table of the E-LAN
service is lower than Address Detection Upper Threshold.

Attribute
Minor Service alarm
Parameters
None

When this alarm occurs, the E-LAN service stops learning new MAC addresses. As a result,
unknown unicast packets in the traffic flow may increase, and broadcast packets may increase
accordingly. In this case, the line rate may be affected.
Possible Causes
The possible causes of the FDBSIZEALM_E-LAN alarm are as follows:
l Cause 1: The value of Address Detection Upper Threshold is too small.

l Cause 2: The E-LAN service is attacked.
Procedure
l Cause 1: The value of Address Detection Upper Threshold is too low.
a. Check whether the value of Address Detection Upper Threshold is too small. For
details, see Configuring the MAC Address Learning Parameters.
b. If yes, set the parameter to a larger value based on actual situations. Check whether
the alarm is cleared. If the alarm persists, go to Cause 2.
l Cause 2: The E-LAN service is attacked.
a. Modify the settings so that the E-LAN service discards unknown packets. For
details, see Setting the Mode for Processing an Unknown Frame of the E-LAN
Service.
----End
Related Information
None
A.3.116 FLOW_EXC_LCS
Description
The FLOW_EXC_LCS alarm indicates that the traffic exceeds the range allowed by the
license.

Attribute
Parameters
None

The service traffic volume is high, which may lead to packet loss.
Possible Causes
The actual transmitted service rate over an Ethernet port exceeds the maximum capacity
allowed by the license.
Procedure
Step 1 Check for any storm on the network. If there is a network storm, eliminate the source illegally
transmitting large volume of data. If there is no network storm, proceed to the next step.
Step 2 Load a proper license file.
----End
Related Information
None
A.3.117 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating the received or transmitted traffic over the
threshold for some performance object
Attribute
Minor Service alarm
Parameters

Name Meaning
Parameter 1 Indicates the receive or transmit direction in which traffic crosses the specified
threshold.
l 0x00: the receive direction
l 0x01: the transmit direction

When the FLOW_OVER alarm occurs, the extra data may be discarded.
Possible Causes
l Cause 1: The traffic threshold is very low.
l Cause 2: The opposite end transmits excessive data flow.
l Cause 3: The network exists data storm.
Procedure
Step 1 Cause 1: The traffic threshold is very low.
1. Increase the traffic threshold to a value that is lower than the rate of the local threshold.
Step 2 Cause 2: The opposite end transmits excessive data flow.

1. Configure the QoS policies at the opposite end to reduce the data flow that the opposite
end transmits.
Step 3 Cause 3: the network exists data storm.

1. Check whether the network exists data storm. Release the loops if exist.
----End
Related Information
None
A.3.118 GSP_RSVP_NB_AUTH_ERR
Description
The GSP_RSVP_NB_AUTH_ERR alarm indicates a Resource Reservation Protocol (RSVP)
neighbor authentication error.
Attribute


Parameters
Name Meaning
Parameters 1-4 Indicate the IP address of the local interface.
Parameters 5-8 Indicate the IP address of the RSVP neighbor's interface.

No TE tunnel can be established between the local NE and the RSVP neighbor.
Possible Causes
The RSVP authentication parameters are set inconsistently on the local NE and the RSVP
neighbor.
Procedure
Step 1 Check the RSVP authentication parameters of the local NE and the RSVP neighbor. If the
parameters are set inconsistently, modify them to make them consistent.
----End
Related Information
None
A.3.119 GSP_RSVP_NB_DOWN
Description
The GSP_RSVP_NB_DOWN alarm indicates an interruption between the local NE and the
RSVP neighbor. This alarm is reported if the local NE does not receive any RSVP response
messages from the RSVP neighbor within three consecutive intervals.
Attribute
Parameters

Name Meaning
Parameters 1-4 Indicate the IP address of the local interface.
Parameters 5-8 Indicate the IP address of the RSVP neighbor's interface.

The CR-LSP between the local NE and the RSVP neighbor is torn down.
Possible Causes
l Cause 1: RSVP is disabled on the RSVP neighbor.
l Cause 2: There is no reachable route to the RSVP neighbor.
l Cause 3: The link between the local NE and the RSVP neighbor is faulty.
l Cause 4: The RSVP neighbor is faulty.
Procedure
Step 1 Cause 1: RSVP is disabled on the RSVP neighbor.
1. Enable RSVP on the RSVP neighbor.
NOTE
RSVP is enabled on OptiX RTN 980 by default.
Step 2 Cause 2: There is no reachable route to the RSVP neighbor.

1. Check the IGP routing table and ensure that the table contains a route to the RSVP
neighbor.
2. Ensure that the IGP configurations between the local NE and the RSVP neighbor are
correct.
3. Ensure that the interface parameters are set consistently on the local NE and the RSVP
neighbor, and that the interface status of both ends is Up.
Step 3 Cause 3: The link between the local NE and the RSVP neighbor is faulty.
1. Check whether the link between the local NE and the RSVP neighbor is faulty, for
example, whether an ETH_LOS or MW_LOF alarm is reported.
2. If the link is faulty, rectify the fault by following instructions in Troubleshooting
Microwave Links or Troubleshooting Native Ethernet Services.
Step 4 Cause 4: The RSVP neighbor device is faulty.

1. Check whether the RSVP neighbor device is faulty. If the device is faulty, rectify the
fault.
----End
Related Information
None

A.3.120 GSP_TNNL_DOWN
Description
The GSP_TNNL_DOWN alarm indicates that an RSVP-TE tunnel is faulty.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the cause of the RSVP-TE tunnel fault. The values are as follows:
l 0x01: indicates a route calculation failure.
l 0x02: indicates a signaling response time-out.
l 0x03: indicates a bandwidth resource request error.
l 0x04: indicates that the resources (including interface and label
information) requested by RSVP are invalid.
l 0x05: indicates a label allocation failure.
l 0x06: indicates a cross-connection control failure.
l 0x07: indicates a tunnel cross-connection setup failure.
l 0x08: indicates an unavailable data link.
l 0x09: indicates a signaling negotiation failure.
l 0x0a: indicates an unknown cause.
l 0x0b: indicates a link fault.
l 0x0c: indicates an RSVP tunnel creation failure.
l 0x0d: indicates a restoration failure during an RSVP restart.
l 0x0e: indicates an RSVP summary refresh time-out.
l 0x0f: indicates an RSVP GR time-out.
l 0x10: indicates that a lower-priority RSVP tunnel goes Down because its
bandwidth resources are preempted by a higher-priority tunnel.
Parameters Indicate the IP address of the faulty NE on the RSVP-TE tunnel.
2-5

The RSVP-TE tunnel cannot carry any services.

Possible Causes
l Cause 1:
The system control board on the peer NE has a hardware fault or software fault.
This may be the cause for 0x01, 0x02, 0x06, 0x07, 0x09, 0x0c, 0x0d, 0x0e, or 0x0f.
l Cause 2:
The link to the peer NE is faulty.
This may be the cause for 0x01, 0x02, 0x06, 0x07, 0x08, 0x09, 0x0b, 0x0c, 0x0d, 0x0e,
or 0x0f.
l Cause 3:
There is no reachable route to the destination NE, or no route complies with the explicit
LSP.
This may be the cause for 0x01, 0x02, 0x09, 0x0c, 0x0d, 0x0e, or 0x0f.
l Cause 4:
The RSVP-TE tunnel configurations are incorrect.
This may be the cause for 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x09, 0x0a, 0x0c, 0x0f,
or 0x10.
l Cause 5:
The bandwidth of the NE is insufficient.
This may be the cause for 0x03, 0x04, or 0x10.
Procedure
Step 1 Cause 1: The system control board on the peer NE has a hardware or software fault.
1. Check whether the system control board on the peer NE has a hardware or software fault.
If the board has a fault, rectify it.
Step 2 Cause 2: The link to the peer NE is faulty.

1. Check whether the link to the peer NE is faulty. If the link is faulty and it is a microwave
link, rectify the fault by following instructions in Troubleshooting Microwave Links. If
the link is faulty and it is an Ethernet link, rectify the fault by following instructions in
Troubleshooting Native Ethernet Services.
Step 3 Cause 3: There is no reachable route to the destination NE, or no route complies with the
explicit LSP.
1. Ping the IP address of the destination NE and each NE along the explicit LSP. Ensure
that there is a reachable route to the destination NE or each NE along the explicit LSP.
2. Ensure that the IS-IS configurations on all the NEs between the local NE and destination
NE are correct.
Step 4 Cause 4: The RSVP-TE tunnel configurations are incorrect.

1. Ensure that the RSVP-TE tunnel configurations are correct. If IS-IS TE is enabled on an
interface, ensure that the RSVP authentication and RSVP-TE explicit path configurations
are correct.
Step 5 Cause 5: The bandwidth of the NE is insufficient.

1. Ensure that the bandwidth resources reserved for tunnels are configured correctly.

2. If a higher-priority tunnel preempts the bandwidth resources of a lower-priority tunnel,

check whether the tunnel priorities are configured properly. If the tunnel priorities are not
configured properly, configure them again.
3. If the reserved bandwidth resources are correctly configured and tunnel priorities are
configured properly but the link bandwidth cannot meet requirements, increase the
network bandwidth.
----End
Related Information
None
A.3.121 HARD_ERR
Description
The HARD_ERR alarm indicates an hardware error. This alarm is reported when there are
minor hardware errors.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates that a storage component is faulty. The value is fixed to 0x14.
Parameter 2 Indicates the sequence number of the faulty storage component.
Parameter 3 Reserved.

Generally, services are not affected.
Possible Causes
Cause: The board hardware is faulty.
Procedure
Step 1 Perform a warm reset or perform a cold reset on the board that reports the alarm on the
NMS.

Step 2 If the alarm persists, replace the board.
----End
Related Information
None
A.3.122 HARD_BAD
Description
The HARD_BAD alarm indicates that hardware is faulty.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2, Indicate the internal fault detected by the board. For details
Parameter 3 about the parameters, see the HARD_BAD alarm parameter
query tool.

The board that reports the HARD_BAD alarm fails to work. If the board is configured with
1+1 protection, protection switching is triggered.
Possible Causes
l Cause 1: The board that reports the HARD_BAD alarm and the backplane are not
connected properly.
l Cause 2: The board that reports the HARD_BAD alarm or system control, switching,
and timing board is faulty.
l Cause 3: The slot housing the board that reports the HARD_BAD alarm is faulty.
Procedure
Step 1 Cause 1: The board that reports the HARD_BAD alarm and the backplane are not connected
properly.
1. Reseat the board by following instructions in 6.1 Removing a Board and 6.2 Inserting
a Board.


Step 2 Cause 2: The board that reports the HARD_BAD alarm or system control, switching, and
timing board is faulty.
1. Replace the board that reports the HARD_BAD alarm by following instructions in 6
Part Replacement.
NOTE
To facilitate management, the NE software considers a physical board as one or more logical
boards. If a logical board is faulty, the corresponding physical board or the system control,
switching, and timing board must be replaced. The following table describes the mapping between
physical boards and logical boards.
Physical Board Logical Board
CSHN – CSHN in slot 15 + SL4D in slot 16 + EG2D in slot 17

– CSHN in slot 20 + SL4D in slot 21 + EG2D in slot 22
CSHNA – CSHNA in slot 15 + SL4D in slot 16 + EG4 in slot 17

– CSHNA in slot 20 + SL4D in slot 21 + EG4 in slot 22
CSHNU – CSHNU in slot 15 + SL4D in slot 16 + EG4 in slot 17 + EX1

in slot 18
– CSHNU in slot 20 + SL4D in slot 21 + EG4 in slot 22 + EX1
in slot 23
2. Check whether the alarm is cleared. If the alarm persists, replace the system control,
switching, and timing board by following instructions in 6 Part Replacement.
NOTE
An extended board may report a HARD_BAD alarm if the system control, switching, and timing
board is faulty.
Step 3 Cause 3: The slot housing the board that reports the HARD_BAD alarm is faulty.
1. If a vacant slot is available, insert the board that reports the HARD_BAD alarm in
the vacant slot, and add the board on the NMS so that the board can work normally.
NOTE
Generally, a slot becomes faulty due to broken or bent pins. Remove the board, and check whether
any pin is broken or bent with the help of a torch.
----End
Related Information
None

A.3.123 HARD_NONSUPPORT
Description
The HARD_NONSUPPORT alarm indicates that the hardware on the board does not support
a certain function or the total power consumption of the NE exceeds the upper limit.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: indicates that the board does not support the ETH PWE3 control
word function.
l 0x02: indicates that the board does not support the system control board's
bus rate of 2.5 Gbit/s.
l 0x03: indicates that the PW OAM does not support the control word mode.
l 0x04: indicates that the board does not support adjusting of the transmit
optical power or the transmit optical power configured by the user exceeds
the specified range.
l 0x05: indicates that the power consumption exceeds the upper limit.

When this alarm occurs, the corresponding function becomes unavailable. If the power
consumption exceeds the specified threshold, services may be affected.
Possible Causes
l Cause 1: The board is configured not to support the ETH PWE3 control word function.
l Cause 2: The board is configured not to support the bus rate of 2.5 Gbit/s.
l Cause 3: The system control board is configured to disable the generic associated
channel label (GAL) for the PW OAM.
l Cause 4: The transmit optical power of the board is modified, or the configured transmit
optical power exceeds the specified range.
l Cause 5: The power consumption power of the NE exceeds the upper limit.

Procedure
Step 1 Cause 1: The board is configured not to support the ETH PWE3 control word function.,
Cause 2: The board is configured not to support the bus rate of 2.5 Gbit/s., and Cause 3: The
system control board is configured to disable the generic associated channel label (GAL) for
the PW OAM.
1. Replace the board with another board that supports this function. For details, see Parts
Replacement.
Step 2 Cause 4: The transmit optical power of the board is modified, or the configured transmit
optical power exceeds the specified range.
1. Change the transmit optical power of the board back to the original value. Check
whether the alarm is cleared.
2. If this alarm is not cleared, change the transmit optical power to be within the normal
range. Check whether the alarm is cleared.
3. If the alarm is not cleared, replace the board.
Step 3 Cause 5: The power consumption power of the NE exceeds the upper limit.
1. Reduce the number of boards or ODUs.
2. Replace the boards or ODUs with those that have lower power consumption.
Step 4 Check whether the alarm is cleared. If the alarm is not cleared, contact Huawei technical
support engineers.
----End
Related Information
None
A.3.124 HP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating that the higher order path error crosses the
threshold. This alarm occurs when the board detects that the performance event that the higher
order path error crosses the preset threshold.
Attribute
Minor Service alarm

Parameters
Name Meaning
Parameter 1 Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm.
l 0x30: HPBBE
l 0x31: HPES
l 0x32: HPSES
l 0x33: HPFEBBE
l 0x34: HPFEES
l 0x35: HPFESES
l 0x36: HPUAS
l 0x4c: HPFEUAS

When the HP_CROSSTR alarm occurs, a large number of errors occur in the service, and the
service may be interrupted.
Possible Causes
Cause 1: The higher order path error crosses the preset threshold.
Procedure
Step 1 Cause 1: The higher order path error crosses the preset threshold.
1. Check the threshold crossing records to find out the performance event that the higher
order path error crosses the preset threshold. For details, see 4.3.5 Browsing the
Performance Event Threshold-Crossing Records.
2. Handle the threshold-crossing performance event.
----End
Related Information
None
A.3.125 HP_LOM
Description
The HP_LOM is an alarm indicating the loss of the higher order path multiframe. This alarm
occurs when the board detects that byte H4 is inconsistent with the expected multiframe
sequence.

Attribute
Parameters
None

When the HP_LOM alarm occurs, the service on the alarmed path is interrupted. If the
services are configured with protection, Protection switching may be triggered.
Possible Causes
l Cause 1: The service level is inconsistently configured at both ends.
l Cause 2: The transmit unit of the peer NE is faulty.
Procedure
Step 1 Cause 1: The service level is inconsistently configured at both ends.
1. Verify that cross-connection configurations (signal mapping) are consistent at both ends.
For example, if the VC-12 structure is configured at the local end and the VC-3 structure
is configured at the peer end, rectify the configurations.
Step 2 Cause 2: The transmit unit of the peer NE is faulty.
1. Replace the alarmed board on the local NE. Then, check whether the alarm is cleared.
If... Then...
The alarm persists Replace the system control, cross-connect, and timing board
on the peer NE.

----End
Related Information
None
A.3.126 HP_RDI
Description
The HP_RDI is an alarm indicating the higher order path remote receive failure. This alarm
occurs when the board detects that bit 5 of byte G1 is 1.

Attribute

Parameters
None

When the HP_RDI alarm occurs, the service on the local NE is not affected. The service
received by the opposite NE, however, is interrupted.
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the higher order path remote receive failure.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
1. Clear the alarms such as HP_LOM and B3_EXC that the AU-4 path reports on the
opposite NE.
----End
Related Information
None
A.3.127 HP_REI
Description
The HP_REI is an alarm indicating the higher order path remote error. This alarm occurs
when the board detects that bits 1-4 of G1 take a value from 1 to 8.
Attribute

Warning Service alarm
Parameters
None


The service on the local site is not affected. The service received by the opposite station,
however, has errors.
Possible Causes
the higher order path remote errors.
Procedure
1. Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.
----End
Related Information
None
A.3.128 HP_SLM
Description
The HP_SLM is an alarm indicating the lower order path label mismatch. This alarm occurs
when the board detects the C2 byte mismatch.
Attribute

Parameters
None

None
Possible Causes
l Cause 1: The C2 byte sent from the peer end is not 0 and differs from the C2 byte
configured to be received at the local end.
l Cause 2: Configuration data is incorrect.

Procedure
Step 1 Cause 1: The C2 byte sent from the peer end is not 0 and differs from the C2 byte configured
to be received at the local end.
1. Configure the same service type at the source and sink of the AU-4 path. For details, see
Configuring Overhead Bytes.
Step 2 Cause 2: Configuration data is incorrect.

1. If the alarmed port is the SDH port that is interconnected with the ATM/Ethernet
equipment, configure the service as VC-4 pass-through service. For details, see Creating
Cross-Connections of SNCP Services.
----End
Related Information
None
A.3.129 HP_TIM
Description
The HP_TIM is an alarm indicating the higher order path trace identifier mismatch. This
alarm occurs when the board detects the J1 byte mismatch.
Attribute

Parameters
None

If the service is configured with the protection that considers the HP_TIM alarm as a trigger
condition, the protection switching is triggered.
Possible Causes
l Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte
transmitted on the opposite NE.
Procedure
Step 1 Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted
on the opposite NE.

1. Disable the receivable J1 byte on the local NE or set the receivable J1 byte on the local
NE to the same as the transmitted J1 byte on the opposite NE. For details, see
Configuring VC-4 POHs.

1. If the alarmed port is the SDH port that is interconnected with the ATM/Ethernet
equipment, configure the service as VC-4 pass-through service. For details, see Creating
Cross-Connections of SNCP Services or Creating the Cross-Connections of Point-to-
Point Services.
If... Then...
The alarm is cleared after the configuration is The fault is rectified. End the alarm
changed handling.
The alarm persists after the configuration is Go to the next step.
changed
2. Check whether the cross-connections are configured correctly at the intermediate nodes
where the service travels. If not, reconfigure the cross-connections. For details, see
Creating Cross-Connections of SNCP Services or Creating the Cross-Connections of
Point-to-Point Services.
----End
Related Information
None
A.3.130 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the unequipped higher order path. This alarm occurs
when the board detects that the C2 byte is 0.
Attribute

Parameters
None

When the HP_UNEQ alarm occurs, the service in the alarmed AU-4 path is unavailable. If the
service is configured with the protection that considers the alarm as a trigger condition, the
protection switching is triggered.

Possible Causes
l Cause 1: The line port at the local NE is configured with services, but the corresponding
line port at the opposite NE is not configured with services.
l Cause 2: Byte C2 is set to 0 at the opposite NE.
Procedure
Step 1 Cause 1: The line port at the local NE is configured with services, but the corresponding line
port at the opposite NE is not configured with services.
1. Configure line services on the opposite NE. For details, see Creating Cross-Connections
of SNCP Services or Creating the Cross-Connections of Point-to-Point Services.
Step 2 Cause 2: Byte C2 is set to 0 at the opposite NE.

1. Change the setting of byte C2. For details, see Configuring VC-4 POHs.
----End
Related Information
None
A.3.131 HPAD_CROSSTR
Description
The HPAD_CROSSTR is an alarm indicating that the higher order path adaptation
performance crosses the threshold. This alarm occurs when a board detects that the
performance event of TU pointer justification crosses the preset threshold.
Attribute

Minor Service alarm
Parameters
Name Meaning
l 0x01: 15 minutes
l 0x02: 24 hours

Name Meaning
l 0xaa: TUPJCHIGH
l 0xab: TUPJCLOW
l 0xac: TUPJCNEW

When the HPAD_CROSSTR alarm occurs, bit errors may occur in the service.
Possible Causes
Cause 1: The performance event of TU pointer justification crosses the preset threshold.
Procedure
Step 1 Cause 1: The performance event of TU pointer justification crosses the preset threshold.
1. Check the threshold crossing records to find out the performance event of TU pointer
justification that crosses the preset threshold. For details, see 4.3.5 Browsing the
----End
Related Information
None
A.3.132 IF_CABLE_OPEN
Description
The IF_CABLE_OPEN is an alarm indicating that the IF cable is open.
Attribute
Parameters
None

When the IF_CABLE_OPEN alarm occurs, the service on the alarmed IF port is interrupted.

Possible Causes
l Cause 1: The IF cable is loose or faulty.
l Cause 2: The IF port on the IF board is damaged.
l Cause 3: The power module of the ODU is faulty.
NOTE
When rectifying the faults of the IF cable, IF port, and ODU, you must turn off the ODU before the
operation. You can turn on the ODU only after the operation is complete.
Procedure
Step 1 Cause 1: The IF cable is loose or faulty.
1. Check whether the connector of the IF cable is loose or whether the connector is made
properly.
The connectors to be checked include the connector between the IF fiber jumper and the
IF board, the connector between the IF fiber jumper and the IF cable, and the connector
between the IF cable and the ODU.
If... Then...
The connector is loose Connect the connector tightly.
The connector is made See the Installation Reference and make new
improperly connectors for the IF cable.
None of the above Go to the next step.
2. Check whether the surface of the IF fiber jumper and the IF cable is damaged.
If... Then...
The cable does not meet the requirement Replace the cable with a qualified one.
The cable meets the requirement Go to Cause 2 or Cause 3.
Step 2 Cause 2: The IF port on the IF board is damaged.

1. Replace the alarmed IF board.
Step 3 Cause 3: The power module of the ODU is faulty.
1. Replace the ODU connected to the alarmed IF port.
----End
Related Information
None.
A.3.133 IF_INPWR_ABN
Description
The IF_INPWR_ABN is an alarm indicating that the power supplied by an IF board to an
ODU is abnormal.

Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: Indicates that the input power of the ODU is too high.
l 0x02: Indicates that the input power of the ODU is too low.

When this alarm occurs, the services on the ODU are interrupted. If 1+1 protection is
configured, this alarm also triggers 1+1 HSB switching.
Possible Causes
l Cause 1: The IF board is faulty.
l Cause 2: The IF cable is faulty.
l Cause 3: The ODU is faulty.
l Cause 4: The IF fiber jumper and the IF board are connected incorrectly.
Procedure
Step 1 Cause 1: The IF board is faulty.
1. Replace the IF board connected to the alarmed ODU.
Step 2 Cause 2: The IF cable is faulty.

1. Check whether the connectors of the IF cable are loose or prepared incorrectly.
The connectors to be checked include the connector between the IF fiber jumper and the
IF board, the connector between the IF fiber jumper and the IF cable, and the connector
between the IF cable and the ODU.
If... Then...
Any of the connectors is loose Connect the connector tightly.
Any of the connectors is prepared See the Installation Reference and make
incorrectly new connectors for the IF cable.
All connectors are normal Go to the next step.

2. Check whether the surface of the IF fiber jumper and the IF cable is damaged or
deformed, and test the connectivity between the IF fiber jumper and the IF cable. For
details, see Testing the Connectivity of the IF Cable.
If... Then...
The IF cable is below standard Replace the IF cable.
The IF cable is up to standard The IF board or ODU may be faulty.
Step 3 Cause 3: The ODU is faulty.

1. Replace the alarmed ODU.
Step 4 Cause 4: The IF fiber jumper and the IF board are connected incorrectly.
1. Connect the IF fiber jumper and the IF board correctly.
----End
Related Information
For single-IF boards:
l The logical slot ID of an OptiX RTN 910A/950/950A ODU is the logical slot ID of the
IF board that is connected to the ODU plus 20.
l The logical slot ID of an OptiX RTN 980 ODU is the logical slot ID of the IF board that
is connected to the ODU plus 50.
For dual-IF boards:
l The logical slot ID of the OptiX RTN 910A/950/950A ODU connected to the first IF
port is the logical slot ID of the IF board plus 20. The logical slot ID of the OptiX RTN
980 ODU connected to the first IF port is the logical slot ID of the IF board plus 50.
l The logical slot ID of the OptiX RTN 910A, 950, 950A, or 980 ODU connected to the
second IF port is the logical slot ID of the ODU connected to the first IF port plus 20.
A.3.134 IF_MODE_UNSUPPORTED
Description
The IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working mode
is not supported. This alarm occurs if the board is not loaded with the FPGA file that supports
the configured IF working mode.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the ID of the FPGA file that is loaded to the board.
l 0x01 indicates that FPGA file 250 is loaded.
l 0x02 indicates that FPGA file 002 is loaded.

When the IF_MODE_UNSUPPORTED alarm occurs, the service on the alarmed IF port is
interrupted.
Possible Causes
Cause 1: The board is not loaded with the FPGA file that supports the configured IF working
mode, or the FPGA file that supports the configured IF working mode is damaged.
Procedure
l Cause 1: The board is not loaded with the FPGA file that supports the configured IF
working mode, or the FPGA file that supports the configured IF working mode is
damaged.
a. Contact Huawei engineers to upgrade the software and the FPGA file.
----End
Related Information
None
A.3.135 IGSP_ENTRIES_EXC
Description
The IGSP_ENTRIES_EXC alarm is reported when the number of IGMP Snooping multicast
table entries exceeds its upper threshold, and will be cleared when the number of IGMP
Snooping multicast table entries is smaller than its lower threshold.
Attribute
Minor Security alarm
Parameters


Name Meaning
Parameter 1 Indicates whether the number of IGMP Snooping multicast table entries
exceeds its upper threshold.
l 0x00: indicates that the number of IGMP Snooping multicast table entries
does not exceed its upper threshold.
l 0x01: indicates that the number of IGMP Snooping multicast table entries
Parameter 2 Indicates whether the number of IGMP Snooping multicast group members
l 0x00: indicates that the number of IGMP Snooping multicast group
members does not exceed its upper threshold.
l 0x01: indicates that the number of IGMP Snooping multicast group
members exceeds its upper threshold.

After the IGSP_ENTRIES_EXC alarm is reported, the IGMP Snooping multicast table has no
more space for learning new table entries. As a result, some IGMP service packets will be
discarded.
Possible Causes
l Cause 1: The configured upper threshold for the number of IGMP Snooping multicast
table entries is too small.
l Cause 2: IGMP Snooping protocol attack packets are generated on the network.
Procedure
Step 1 Cause 1: The configured upper threshold for the number of IGMP Snooping multicast table
entries is too small.
1. Check whether the configured upper threshold for the number of IGMP Snooping
multicast table entries is too small. If the upper threshold is too small, set another larger
value according to the network plan.
2. Check whether the alarm is cleared. If it persists, go to Cause 2.
Step 2 Cause 2: IGMP Snooping protocol attack packets are generated on the network.
1. Check whether IGMP Snooping protocol attack packets are generated on the network.
Upon detection of any IGMP Snooping attack packets, locate the attack source and
shield it.
----End

Related Information
None
A.3.136 IMA_GROUP_LE_DOWN
Description
The IMA_GROUP_LE_DOWN is an alarm indicating that the IMA group at the local end
fails. This alarm occurs when the IMA group is in non-Active state on the local NE or when
the activated links of the IMA group on the local NE are less than the minimum number.
Attribute
Parameters
None

When this alarm occurs, all links of the alarmed IMA group are unavailable.
Possible Causes
l Cause 1: The IMA links on the local NE are faulty.
l Cause 2: The activated links of the IMA group on the local NE are less than the
minimum number.
Procedure
Step 1 Cause 1: The IMA links on the local NE are faulty.
1. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm.
2. Check whether the IMA_GROUP_RE_DOWN alarm is cleared. If the alarm persists,
configure the related services at other ports or replace the related board.
Step 2 Cause 2: The activated links of the IMA group on the local NE are less than the minimum
number.
If... Then...
The ALM_IMA_LIF alarm Clear the ALM_IMA_LIF alarm immediately. Activate
occurs the links of the IMA group on the local NE.
No other alarm occurs Reconfigure the links of the IMA group on the local NE.
When the number of activated links of the IMA group reaches the minimum number, the
alarm clears automatically.
----End

Related Information
None
A.3.137 IMA_GROUP_RE_DOWN
Description
The IMA_GROUP_RE_DOWN is an alarm indicating that the IMA group at the remote end
fails. This alarm occurs when the IMA group is in non-Active state on the remote NE or when
the activated links of the IMA group on the remote NE are less than the minimum number.
Attribute
Parameters
None

When this alarm occurs, the ports of the IMA group are congested and services have bit
errors.
Possible Causes
l Cause 1: The IMA links on the remote NE are faulty.
l Cause 2: The activated links of the IMA group on the remote NE are less than the
minimum number.
Procedure
Step 1 Cause 1: The IMA links on the remote NE are faulty.
1. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm.
2. Check whether the IMA_GROUP_RE_DOWN alarm is cleared. If the alarm persists,
configure the related services at other ports or replace the related board.
Step 2 Cause 2: The activated links of the IMA group on the remote NE are less than the minimum
number.
If... Then...
The ALM_IMA_LIF alarm Clear the ALM_IMA_LIF alarm immediately. Activate
occurs the links of the IMA group on the opposite NE.
No other alarm occurs Reconfigure the links of the IMA group on the remote
NE.

When the number of activated links of the IMA group reaches the minimum number, the
alarm clears automatically.
----End
Related Information
None
A.3.138 IMA_TXCLK_MISMATCH
Description
The IMA_TXCLK_MISMATCH is an alarm indicating that the transmit clock modes of an
IMA group are inconsistent at the two ends.
Attribute
Parameters
None

The IMA_TXCLK_MISMATCH alarm may cause loss of ATM cells.
Possible Causes
Cause 1: The transmit clock modes of an IMA group are inconsistent at the two ends.
Procedure
Step 1 Cause 1: The transmit clock modes of an IMA group are inconsistent at the two ends.
1. Check the alarm information and determine the NE, board, and ATM trunk related to the
alarm.
2. Modify the Clock Mode parameter of the alarmed ATM trunk to the same value as that
of the opposite end. Then, check whether the alarm is cleared.
----End
Related Information
The Clock Mode parameter can be set to two modes.
l CTC mode: Common transmit clock mode. In CTC mode, all transmit clocks of the
links in an IMA group are from the same clock source.

l ITC mode: Independent transmit clock mode. In ITC mode, the transmit clocks of the
links in an IMA group are from different clock sources. When the IMA group is set to
the line clock mode, the ITC mode is recommended.
A.3.139 IN_PWR_ABN
Description
The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.
Attribute

Parameters
None

When the IN_PWR_ABN alarm occurs, the service at the alarmed optical interface has errors
and even becomes unavailable.
Possible Causes
l Cause 1: The transmit power of the opposite NE is over high or over low.
l Cause 2: The model of the selected optical module is incorrect.
l Cause 3: The optical module at the receive end is faulty.
l Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over high or over low.
1. Browse current performance events, and query the performance event of the transmit
optical power on the opposite NE.
If... Then...
The transmit optical power does not meet Replace the optical module.
the requirement
The transmit optical power is over high Add a proper attenuator to reduce the
receive optical power.
Step 2 Cause 2: The model of the selected optical module is incorrect.

1. Query the board manufacturing information report, and check whether the models of
the SFP optical modules used at both ends are correct.

If... Then...
The models are incorrect Replace the optical module.
The models are correct Go to Cause 3.
Step 3 Cause 3: The optical module at the receive end is faulty.

1. Use the optical power meter to test the receive optical power, and check whether the
receive optical power meets the requirement. If yes, contact Huawei engineers to replace
the optical module.
Step 4 Cause 4: The fiber performance degrades.
If... Then...
The connector of the fiber jumper is dirty Clean fiber connectors.
The connector or fiber is damaged Insert the connector properly or replace the
damaged fiber jumper.
----End
Related Information
The following table describes the meanings of the parameters in the IN_PWR_ABN alarm
reported by the EMS6.
Name Meaning
Parameter 1 Indicates the port number.
Parameter 2, Parameter 3 The value of Parameter 2 is always 0x00,

and the value of Parameter 3 is always
0x01. The two parameters indicate the path
ID.
Parameter 4, Parameter 5 Reserved. The values are always 0xFF.
A.3.140 IN_PWR_HIGH
Description
The IN_PWR_HIGH is an alarm indicating that the input optical power is over high.
Attribute
Parameters
None


When the IN_PWR_HIGH alarm occurs, the service at the alarmed optical interface has
errors.
Possible Causes
l Cause 1: The transmit power of the opposite NE is over high.
Procedure
Step 1 Cause 1: The transmit power of the opposite site is over high.
If... Then...
The transmit optical power does not Contact Huawei engineers to replace the
meet the requirement optical module.
The transmit optical power meets the Add a proper attenuator to reduce the
requirement receive optical power.

If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.

receive optical power meets the requirement. If yes, contact Huawei engineers to replace
the optical module.
----End
Related Information
The optical power threshold set for the IN_PWR_HIGH alarm is lower than the overload
point.
SDH Interface Performance.
A.3.141 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating that the input optical power is over low.

Attribute

Parameters
None

When the IN_PWR_LOW alarm occurs, the service at the alarmed optical interface has
errors.
Possible Causes
l Cause 1: The transmit power of the opposite NE is over low.
l Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over low.
If... Then...
The transmit optical power does not meet the Contact Huawei engineers to replace
requirement the optical module.
The transmit optical power meets the Go to Cause 2.
requirement

If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.

receive optical power meets the requirement.

If... Then...
The receive optical power meets the Contact Huawei engineers to replace
requirement the optical module.
The receive optical power does not meet the Go to Cause 4.
requirement
Step 4 Cause 4: The fiber performance degrades.

1. Clean fiber connectors and adapters.
If... Then...
The alarm is cleared after the connector is The fault is rectified. End the alarm
cleaned handling.
The alarm persists after the connector is cleaned Replace the fiber.
----End
Related Information
The optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity
point.
SDH Interface Performance.
A.3.142 INSUFFCNT_MEM_SPACE
Description
The INSUFFCNT_MEM_SPACE alarm indicates that the file system space in the memory is
insufficient. This alarm is reported when the memory space usage exceeds 90%.
Attribute
Critical Processing error alarm
Parameters
Name Meaning
Parameter 1 Indicates the resource type.
l 0x00: mfs
Parameter 2 Indicates that the current memory space utilization.

Name Meaning
Parameters 3 to 5 These parameters are reserved. Their values are always 0xff.

l Package loading fails.
l Database backup fails.
Possible Causes
Cause: The file system space in the memory is insufficient.
Procedure
Step 1 Check the alarm on the NMS for the specific alarmed memory space according to alarm
parameters.
Step 2 Query the files stored in the alarmed memory space and check for any oversized files or extra
files.
Step 3 Delete oversized and extra files, if any.
Step 4 Check whether the alarm clears. If the alarm persists, contact Huawei engineers to handle the
alarm.
----End
Related Information
None
A.3.143 INSUFFCNT_FLSH_SPACE
Description
The INSUFFCNT_FLSH_SPACE alarm indicates that the flash file space is insufficient. This
alarm is reported when the flash space usage exceeds 90%.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the resource type.
l 0x00: ofs1
l 0x01: ofs2
Parameter 2 Indicates that the current flash space utilization.
Parameters 3 to 5 These parameters are reserved. Their values are always 0xff.

File storage to the flash space fails.
Possible Causes
Cause: The file system space on the flash is insufficient.
Procedure
Step 1 Check the alarm on the NMS for the specific alarmed flash space according to the alarm
parameters.
Step 2 Query the files stored in the alarmed flash space and check for any oversized files or extra
files.
Step 3 Delete oversized and extra files, if any.
Step 4 Check whether the alarm clears. If the alarm persists, contact Huawei engineers to handle the
alarm.
----End
Related Information
None
A.3.144 INTEMP_SENSOR_FAIL
Description
The INTEMP_SENSOR_FAILL is an alarm indicating that the air inlet temperature sensor of
the cabinet fails.
Attribute


Parameters
None

The air inlet temperature data of the TCU cannot be collected.
Possible Causes
l Cause 1: The air inlet temperature sensor is faulty.
l Cause 4: The air inlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air inlet temperature sensor is faulty.
1. Replace the air inlet temperature sensor.
If... Then...

If... Then...

Step 4 Cause 4: The air inlet temperature sensor is not installed.

1. Install the air inlet temperature sensor.
----End
Related Information
None

A.3.145 ISIS_LSP_SEQ_EXCEED
Description
ISIS_LSP_SEQ_EXCEED indicates that the LSP serial number generated by the IS-IS
exceeds the upper threshold. This alarm is reported if the LSP serial number generated by the
IS-IS exceeds the upper threshold for three or more times.
Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicate the type of the IS-IS neighbor.
Parameters 5 to 28 Indicate the system ID of the IS-IS.
Parameters 29 to 32 Indicate the upper threshold of LSP serial numbers.

If the ISIS_LSP_SEQ_EXCEED alarm is reported, the instance system of IS-IS enters into
the dormant state.
Possible Causes
l Cause 1: The LSP serial number generated exceeds the upper threshold.
Procedure
Step 1 Cause 1: The LSP serial number generated exceeds the upper threshold.
1. On the NMS, continuously check the LSP serial number generated by the local router.
NOTE
The LSP updates the timer at an interval of 15 minutes by default. Each time the timer expires, the
LSP serial number is automatically incremented by 1.
If... Then...
The LSP serial number is incremented normally. The device runs properly, and no
action is required.

If... Then...
The LSP serial number is incremented by 1 at Go to the next step.
an interval of less than 15 minutes.
2. Check whether the system IDs of other routers in the domain are duplicate with the
system ID of the local router.
NOTE
According to the ISO 10589 protocol, the system IDs in the same IS-IS protocol domain cannot be
duplicate.
If... Then...
System IDs are duplicate. Change the system ID of the local router.
System IDs are not duplicate. Go to the next step.
3. Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
A.3.146 ISIS_SEQ_REACH_MAX
Description
ISIS_SEQ_REACH_MAX indicates that the LSP serial number generated by the IS-IS
exceeds the maximum value. This alarm is reported if the LSP serial number generated by the
IS-IS exceeds the maximum value for three or more times.
Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicate the type of the IS-IS neighbor.
Parameters 5 to 28 Indicate the system ID of the IS-IS.


If the ISIS_SEQ_REACH_MAX alarm is reported, the instance system of IS-IS enters into
the dormant state.
Possible Causes
l Cause 1: The LSP serial number exceeds the maximum value 0xFFFFFFFF.
Procedure
Step 1 Cause 1: The LSP serial number exceeds the maximum value 0xFFFFFFFF.
1. On the NMS, continuously check the LSP serial number generated by the local router.
NOTE
The LSP updates the timer at an interval of 15 minutes by default. Each time the timer expires, the
LSP serial number is automatically incremented by 1.
If... Then...
The LSP serial number is incremented normally. The device runs properly, and no
action is required.
The LSP serial number is incremented by 1 at Go to the next step.
an interval of less than 15 minutes.
2. Check whether the system IDs of other routers in the domain are duplicate with the
system ID of the local router.
NOTE
According to the ISO 10589 protocol, the system IDs in the same IS-IS protocol domain cannot be
duplicate.
If... Then...
System IDs are duplicate. Change the system ID of the local router.
System IDs are not duplicate. Go to the next step.
3. Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
A.3.147 ISISADJACENCYCHANGE
Description
The ISISADJACENCYCHANGE alarm indicates that the status of an IS-IS neighbor
changes.

Attribute
Parameters
Name Meaning
Parameters 1-4 Indicate the IS-IS process ID.
Parameters 5-8 Indicate the type of the IS-IS neighbor.
Parameters 9-12 Indicate the IS-IS interface index.
Parameters 13-16 Indicate the interface index.
Parameters 17-39 Indicate the system ID.
Parameters 40-43 Indicate the status of the IS-IS neighbor.
Parameters 44-47 Indicate the interface index.
Parameters 48-111 Indicate the interface name.
Parameters 112-115 Indicate the cause of the neighbor status change.

IS-IS may recalculate the route, resulting in route flapping.
The RSVP neighbor relationship and BGP peer relationship with IS-IS as the IGP route
protocol may be interrupted.
Possible Causes
l Cause 1: The IS-IS configurations are incorrect.
l Cause 2: The link between the local NE and the IS-IS neighbor is faulty.
l Cause 3: The IS-IS neighbor fails.
Procedure
Step 1 Cause 1: The IS-IS configurations are incorrect.

1. Ensure that the IS-IS configurations are consistent on the local NE and the IS-IS
neighbor.
Step 2 Cause 2: The link between the local NE and the IS-IS neighbor is faulty.
1. Check whether the link between the local NE and the IS-IS neighbor is faulty, for
example, whether an ETH_LOS alarm is reported.
2. If the link is faulty, rectify the fault.
Step 3 Cause 3: The IS-IS neighbor is faulty.

1. Check whether the IS-IS neighbor is faulty. If the IS-IS neighbor is faulty, rectify the
fault.
----End
Related Information
None
A.3.148 J0_MM
Description
The J0_MM is an alarm indicating the trace identifier mismatch. This alarm occurs when the
board detects the J0 byte mismatch.
Attribute
Parameters
None

None
Possible Causes
Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on the
opposite NE.
Procedure
Step 1 Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on the
opposite NE.
1. Disable the receivable J0 byte on the local NE. For details, see Configuring RSOHs.
----End

Related Information
None
A.3.149 K1_K2_M
Description
The K1_K2_M is an alarm indicating the K1/K2 byte mismatch. This alarm occurs when the
board detects inconsistent channel numbers that the transmitted K1 byte (bits 5-8) and the
received K2 byte (bits 1-4) indicate.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the protection group type.

When the K1_K2_M alarm occurs, the MSP protocol may fail and therefore the protection
switching may fail.
Possible Causes
l Cause 1: The switching modes configured at both ends are single-ended switching and
dual-ended switching separately.
l Cause 2: The fiber connection is incorrect.
Procedure
Step 1 Cause 1: The switching modes configured at both ends are single-ended switching and dual-
ended switching separately.
1. Check whether the switching modes at both ends are the same.

If... Then...
The switching modes are different Configure the switching modes as the same.
The switching modes are the same Go to Cause 2.
Step 2 Cause 2: The fiber connection is incorrect.

1. Check whether the fiber connection is correct. For example, the fiber at the receive or
transmit port may be incorrectly connected, or disconnected.
If... Then...
The fiber connection is incorrect Connect the fiber properly.
The connection is correct Go to Cause 3.

1. Replace the opposite line board. Then, check whether the alarm is cleared.
If... Then...
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For configuration details on
linear MSP, refer to Creating a Packet-based Linear MSP Group
A.3.150 K2_M
Description
The K2_M is an alarm indicating the K2 byte mismatch. This alarm occurs when the board
detects that the protection mode indicated by the received K2 (bit 5) is different from the
protection mode of the NE.
Attribute

Parameters

Name Meaning
Parameter 1 Indicates the protection group type.

When the K2_M alarm occurs, the MSP protocol may fail and therefore the protection
switching may fail.
Possible Causes
l Cause 1: Two NEs of the linear MSP group are configured with different protection
modes (1+1 or 1:N).
l Cause 2: The MSP protocol is stopped when the protection switching occurs.
l Cause 3: The fiber connection is incorrect.
Procedure
Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes
(1+1 or 1:N).
1. Query the status of the linear MSP, and check whether two NEs of the linear MSP group
are configured with different protection modes (1+1 or 1:N).
If... Then...
The protection modes are different Configure the protection modes as the same.
The protection modes are the same Go to Cause 2.
Step 2 Cause 2: The MSP protocol is stopped when the protection switching occurs.
1. Query the status of the linear MSP, and check whether the MSP protocol is stopped on
the opposite NE.
If... Then...
The protocol is stopped Restart the MSP protocol on the opposite NE. For details,
see Starting/Stopping the Linear MSP Protocol.
The protocol is running Go to Cause 3.
Step 3 Cause 3: The fiber connection is incorrect.

1. Check whether the fiber connection is correct. For example, the fiber at the receive or
transmit port may be incorrectly connected, or disconnected.
If... Then...
The connection is incorrect Connect the fiber properly

If... Then...

1. Replace the opposite line board. Then, check whether the alarm is cleared.
If... Then...
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For configuration details on
linear MSP, refer toCreating a Packet-based Linear MSP Group.
A.3.151 KMC_KEY_SYNC_FAIL
Description
The KMC_KEY_SYNC_FAIL alarm indicates a KMC key synchronization failure. (KMC is
short for key management center.)
Attribute
Parameters
None

The database cannot be backed up, KMC cannot be enabled or disabled, and KMC keys
cannot be configured.
Possible Causes
l Cause 1: The database on the alarmed NE is abnormal.
l Cause 2: The database backup fails on the alarmed NE.
Procedure
Step 1 Restore NE data from the latest backup database.
Step 2 If NE data restoration fails, contact Huawei engineers to handle the alarm.
----End

Related Information
None
A.3.152 L3V_TRAP_THRE_EXCEED
Description
The L3V_TRAP_THRE_EXCEED alarm indicates that the number of VPN route prefixes
exceeds the maximum number allowed.
Attribute
Parameters
Name Meaning
Parameters 1-31 Indicate the name of a VPN instance.
Parameters 32-35 Indicates the current number of route prefixes.
Parameters 36-39 Indicates the maximum number of route prefixes.

When the number of VPN route prefixes exceeds the maximum number allowed, excess VPN
route prefixes cannot be added into the VPN instance routing table. As a result, the excess
VPN routes are lost and some services are unavailable.
Possible Causes
l Cause 1: Data configuration is incorrect.
l Cause 2: The maximum number of route prefixes in a VPN instance routing table is set
to a small value.
l Cause 3: The network structure is not appropriate.
Procedure
Step 1 Cause 1: Data configuration is incorrect.
1. Check the data configuration, especially BGP route configuration, to ensure that the NE
receives only required routes.
Step 2 Cause 2: The maximum number of route prefixes in a VPN instance routing table is set to a
small value.

1. Increase the maximum number of route prefixes in a VPN instance routing table.
Step 3 Cause 3: The network structure is not appropriate.

1. Optimize the network structure.
----End
Related Information
None
A.3.153 L3V_TRAP_VRF_DOWN
Description
The L3V_TRAP_VRF_DOWN alarm indicates that a VPN instance is in the Down state. This
alarm is reported when all the interfaces bound to a VPN instance go Down or the binding
relationships between a VPN instance and interfaces in the Up state are deleted.
Attribute
Parameters
Name Meaning
Parameters 1-31 Indicate the name of a VPN instance.
Parameters 32-33 Indicate the slot ID.
Parameter 34 Indicates the sub-slot ID.
Parameters 35-36 Indicate the interface ID.
Parameters 37-40 Indicate the interface running status. The values are as follows:
l 0x01: active
l 0x02: notInService
Parameters 41-44 Indicate the VPN instance running status.
l 0x01: up
l 0x02: down

The VPN service is interrupted.
Possible Causes
l Cause 1: The VPN instance is not bound with any interfaces.

l Cause 2: All the interfaces bound to the VPN instance go Down.
Procedure
Step 1 Cause 1: The VPN instance is not bound with any interfaces.
1. Bind interfaces to the VPN instance according to the plan. Ensure that the status of these
interfaces is Up.
Step 2 Cause 2: All the interfaces bound to the VPN instance go Down.
1. Ensure that the interfaces are enabled and configured with IP addresses. For details, see
Setting Ethernet Interface Parameters. If the interfaces are still in the Down state, go to
the next step.
2. Check whether the links to the interfaces are faulty. If they are faulty, rectify the faults by
following instructions in Troubleshooting Native Ethernet Services.
----End
Related Information
None
A.3.154 LAG_BWMM
Description
LAG_BWMM is an alarm indicating the bandwidth inconsistency in the LAG group.
Attribute
Parameters
None

For a LAG group in load-sharing mode, data services may be lost.
Possible Causes
Cause 1: In the LAG group, the license capacities of the ports differ from each other.
Procedure
Step 1 Cause 1: In the LAG group, the license capacities of the ports differ from each other.
1. Query the license capacities of the LAG group by using the NMS.

2. If the license capacities of the ports differ from each other, reload a license file of an
appropriate capacity.
----End
Related Information
None
A.3.155 LAG_DOWN
Description
The LAG_DOWN is an alarm indicating that the link aggregation group (LAG) is
unavailable. This alarm occurs when the LAG does not have activated members.
Attribute

Parameters
None

When the LAG_DOWN alarm occurs, the service at the member port of the LAG is
interrupted.
Possible Causes
Cause 1: All the member ports of the aggregation group are invalid for the same causes as the
LAG_MEMBER_DOWN alarm.
Procedure
Step 1 Cause 1: All the member ports of the LAG are invalid for the same causes as the
LAG_MEMBER_DOWN alarm.
1. Determine the alarmed port according to the alarm parameter.
2. Rectify the fault at each member port according to the description of
LAG_MEMBER_DOWN.
----End
Related Information
None

A.3.156 LAG_MEMBER_DOWN
Description
The LAG_MEMBER_DOWN is an alarm indicating that a member port of a link aggregation
group (LAG) is unavailable. This alarm occurs when a member port of an LAG can neither be
activated nor function as a protection port.
Attribute

Parameters
Name Meaning
Parameter 1, Parameter Indicates the slot ID of the alarmed board.
2
Parameter 3 Indicates the ID of the alarmed subboard. The value is always 0xff.
Parameter 4, Parameter Indicates the ID of the alarmed port.
5
Parameter 6 Indicates the cause that makes the port unavailable.
l 0x01: The port link is faulty or disabled.
l 0x02: The port fails to receive the LACP packets.
l 0x03: The port works in half-duplex mode.

The port in the LAG cannot share the service load, and the port does not transmit or receive
any services.
Possible Causes
l Cause 1: The port link is faulty or disabled.
l Cause 2: The port receives no LACP packets.
l Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode.
l Cause 4: The port is self-looped.

Procedure
Step 1 Determine the alarmed port and the cause of the alarm according to the alarm parameters.
If... Then...
The value of Parameter 4 is 0x01 Perform the operations described in Step 2.
Step 2 Cause 1: The port link is faulty or disabled.

1. On the NMS, check whether the port in the LAG is enabled. For details, see Querying
the Protocol Information of the LAG.
If... Then...
The port is not enabled Enable the port in the LAG.
The port is enabled Go to the next step.
2. Check the link status of all ports and check whether the ETH_LOS alarm is reported.
If... Then...
The alarm is reported Clear the ETH_LOS alarm immediately and rectify the
fault of the port link.
The alarm is not reported Go to Cause 2.
Step 3 Cause 2: The port receives no LACP packets.

1. Check whether the local port and the remote port transmit the LACP packets. For details,
see Querying the Protocol Information of the LAG. If the LACP packets are not
transmitted, configure the ports at two ends to ensure that the packets can be normally
transmitted.
Step 4 Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode.
1. On the NMS, check whether the port in the LAG works in half-duplex mode. For details,
see Querying the Protocol Information of the LAG. If the port works in half-duplex
mode, change the working mode of the port into full-duplex.
2. On the NMS, change the working mode of the port into full-duplex and Auto-
Negotiation.
Step 5 Cause 4: The port is self-looped.

1. Check whether the port is self-looped. For details, see 8.2.1 Querying the Attributes of
an Ethernet Port. If the port is self-looped, release the selfloop. For details, see 8.4.5
Setting a Loopback for the Packet-plane Ethernet Interface Board.
----End
Related Information
None

A.3.157 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that a port in the LAG fails. When a port in the
LAG is unavailable, the LAG_PORT_FAIL alarm is reported.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the IP port.
Parameter 4 Indicates the cause of the protection failure.

l 0x01: The link of the port is faulty or fails.
l 0x02: The port is in half-duplex mode.
l 0x04: The port detects the selfloop.
l 0x05: Other unknown reasons.
Parameter 5 The value is always 0xff.

any services.
Possible Causes
l Cause 1: The port is disabled or the link is faulty.
l Cause 2: The port is in the half-duplex mode.
l Cause 3: The port fails to receive the LCAP packets.
l Cause 4: The port detects a selfloop.
l Cause 5: other unknown reasons

Procedure
Step 1 Determine the port where the alarm occurs and the alarm cause according to the alarm
parameter.
If... Then...
Step 2 Cause 1: The port is disabled or the link is faulty.

1. On the NMS, check whether the port in the LAG is enabled. For details, see Setting the
Basic Attributes of Ethernet Ports.
If... Then...
The port is not enabled Enable the port in the LAG group.
The port is enabled Check the link state of each port. If any link is faulty, rectify
the fault.
Step 3 Cause 2: The port is in the half-duplex mode.

1. On the NMS, check the working mode of the port in the LAG group. If the port is in
half-duplex mode, change the working mode of the port into full-duplex. For details, see
Setting the Basic Attributes of Ethernet Ports.
Step 4 Cause 3: The port fails to receive the LCAP packets.
1. On the NMS, check whether the LAG group is properly configured on the opposite end.
For details, see Querying the Protocol Information of the LAG.
If... Then...
The LAG group is not properly configured Reconfigure the LAG group.
The LAG group is properly configured Go to the next step.
2. Check whether the local port and the remote port transmit the LACP packets. If the
LACP packets are not transmitted, configure the ports at both ends to ensure that the
packets can be normally transmitted. For details, see Querying the Protocol Information
of the LAG.
Step 5 Cause 4: The port detects a selfloop.
1. Release the selfloop of the port with reference to Enabling Self-Loop Detection.
Step 6 Cause 5: other unknown reasons
1. Contact Huawei engineers.
----End
Related Information
None

A.3.158 LAG_VC_PORT_FAIL
Description
The LAG_VC_PORT_FAIL is an alarm indicating that a VCG port in the LAG fails. When
the VCTRUNK is unavailable, the alarm is reported.
Attribute
Parameters
Name Meaning
Parameter 2, Indicate the number of the faulty VCG port in the LAG. Parameter 2
Parameter 3 indicates the most significant bits and Parameter 3 indicates the least
significant bits.
Parameter 4 Indicates the cause of the protection failure.

l 0x01: The link of the port is faulty or fails.
l 0x04: The link of the port is configured into a loop.
l 0x05: other unknown reasons.

any services.
Possible Causes
l Cause 1: The link of the port is faulty or fails.
l Cause 2: The port fails to receive the LCAP packets.
l Cause 3: The port detects a selfloop.
l Cause 4: other unknown reasons

Procedure
Step 1 Determine the port where the alarm occurs and the alarm cause according to the alarm
parameter.
If... Then...
Step 2 Cause 1: The port is disabled or the link is faulty.

1. Check the link state of each VCG port. If any link is faulty, rectify the fault.
Step 3 Cause 2: The port fails to receive the LCAP packets.

1. On the NMS, check whether the LAG group is properly configured on the opposite end.
If... Then...
The LAG group is not properly configured Reconfigure the LAG group.
The LAG group is properly configured Go to the next step.
2. Check whether the local port and the remote port transmit the LACP packets. If the
LACP packets are not transmitted, configure the ports at both ends to ensure that the
packets can be normally transmitted.
Step 4 Cause 3: The port detects a selfloop.

1. Release the selfloop of the port.
Step 5 Cause 4: other unknown reasons

1. Contact Huawei engineers.
----End
Related Information
None
A.3.159 LAN_LOC
Description
The LAN_LOC is an alarm indicating the Ethernet communication failure.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the network port ID. For example, 0x01 indicates network
port 1 and 0x02 indicates network port 2.
Parameter 2, Indicates the number of the path on which the alarm is reported.
Parameter 3
Parameter 2 indicates the most significant bits and the value is always
0x00. Parameter 3 indicates the least significant bits and the value is
always 0x01.

When the alarm is reported, the communication of the network port is interrupted. As a result,
the NE is out of control. The existing services of the NE, however, are not affected.
Possible Causes
l Cause 1: The cable is not connected to the network port, or the cable is faulty.
l Cause 2: The network port is faulty.
l Cause 3: The system control, switching, and timing board is faulty.
Procedure
Step 1 View the alarm on the NMS. Determine the network port ID according to the alarm parameter
1.
Step 2 Cause 1: The cable is not connected to the network port, or the cable is faulty.
1. Check whether the cable of the network port is loose or no cable is connected. Properly
connect the NMS to the network port. The LINK indicator is in green.
Step 3 Cause 2: The network port is faulty.

1. Replace the faulty board. For details, see 6.10 Replacing the System Control,
Step 4 Cause 3: The system control, switching, and timing board is faulty.
1. Replace the system control, switching, and timing board. For details, see 6.10 Replacing
the System Control, Switching and Timing Board.
----End
Related Information
None

A.3.160 LASER_CHECK_ERR
Description
The LASER_CHECK_ERR alarm indicates that an optical module reading/writing error
occurs.
Attribute
Parameters
None

When the LASER_CHECK_ERR alarm is reported, the optical module rate, alarms,
performance, and manufacturing information cannot be reported to the system control board,
but port services are not affected.
Possible Causes
Possible causes of this alarm are as follows:
l Cause 1: The optical module is faulty.

l Cause 2: The optical module connector is faulty.
Procedure
Step 1 Cause 1: The optical module is faulty.
1. Replace the alarmed optical module.
Step 2 Cause 2: The optical module connector is faulty.

1. Replace the board. For details, see the Part Replacement.
----End
Related Information
None

A.3.161 LASER_CLOSED
Description
The LASER_CLOSED is an alarm indicating that the laser is shut down. This alarm occurs
when the laser is shut down by using the NMS.
Attribute

Parameters
None

When the LASER_CLOSED alarm occurs, the optical interface fails to carry services.
Possible Causes
Cause 1: The laser on the local NE is shut down by using the NMS.
Procedure
Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.
1. Find out the cause of shutting down the laser and start up the laser as soon as possible.
----End
Related Information
None
A.3.162 LASER_MOD_ERR
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module
on the board does not match the type of the optical interface.
Attribute


Parameters
None

When the LASER_MOD_ERR alarm occurs, the performance of the optical interface
degrades and serious degradation even causes service interruption.
Possible Causes
l Cause 1: The optical module installed at the optical interface does not match the rate of
l Cause 2: The small form-factor pluggable (SFP) module does not match the interface
type.
Procedure
Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
1. Check whether the optical module installed at the optical interface matches the rate of
the optical interface. For details, see 4.8.5 Querying the Board Manufacturing
Information Report.
If... Then...
The optical module does not match the Contact Huawei engineers to replace the
rate of the optical interface optical module with one that matches the
rate of the optical interface.
The optical module matches the rate of Go to Cause 2.
the optical interface
Step 2 Cause 2: The SFP module does not match the interface type.
1. Replace the existing SFP module with a proper SFP module.
1. Replace the faulty optical module.
If... Then...
The alarm is cleared after the optical module is replaced End the alarm handling.
The alarm persists after the optical module is replaced Go to Cause 3.

----End
Related Information
None

A.3.163 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module
on the board does not match the type of the optical interface.
Attribute
Parameters
None

When the LASER_MOD_ERR_EX alarm occurs, the performance of the optical interface
degrades and serious degradation even causes service interruption.
Possible Causes
l Cause 1: The optical module installed at the optical interface does not match the rate of
l Cause 2: The small form-factor pluggable (SFP) module does not match the interface
type.
Procedure
Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
1. Check whether the optical module installed at the optical interface matches the rate of
the optical interface. For details, see 4.8.5 Querying the Board Manufacturing
Information Report.
If... Then...
The optical module does not match the Contact Huawei engineers to replace the
rate of the optical interface optical module with one that matches the
rate of the optical interface.
The optical module matches the rate of Go to Cause 2.
the optical interface
Step 2 Cause 2: The SFP module does not match the interface type.
1. Replace the existing SFP module with a proper SFP module.

If.. Then...
The port type is incorrectly set See Configuring an SFP Port.to rectify the port type
setting
The SFP type is incorrect Replace it with an SFP module of the correct type.

1. Replace the faulty optical module.
If... Then...
The alarm is cleared after the optical module is replaced End the alarm handling.
The alarm persists after the optical module is replaced Go to Cause 3.

----End
Related Information
None
A.3.164 LASER_MODULE_MISMATCH
Description
LASER_MODULE_MISMATCH indicates that the optical module mismatches. This alarm is
reported if the type of the optical module inserted into an optical port of a board is not
supported by the optical port. For EX1 and EG4 boards integrated on the RTN 980 and RTN
980L, if a commercial-class optical module is used, this alarm is also reported.
Attribute
Parameters
None

When the LASER_MODULE_MISMATCH alarm is reported, services cannot be normally
received and transmitted, or even services are interrupted.
Possible Causes
l Cause 1: The type of the optical module inserted into an optical port mismatches the
optical module type supported by the physical board.

l Cause 2: For EX1 and EG4 boards integrated on the RTN 980 and RTN 980L, a
commercial-class optical module is used.
Procedure
l Cause 1: The type of the optical module inserted into an optical port mismatches the
optical module type supported by the physical board.
a. Check whether the type of the optical module inserted into an optical port is the
required optical module type.
If... Then...
The type of the optical module inserted into an Go to the next step.
optical port is the required optical module
type.
The type of the optical module inserted into an Replace the optical module
optical port is not the required optical module with a module of the
type. supported type.
l Cause 2: For EX1 and EG4 boards integrated on the RTN 980 and RTN 980L, a
commercial-class optical module is used.
a. Check whether the input optical port module is an industrial-class optical module.
If... Then...
Yes Go to the next step.
No Replace the optical module with an industrial-level optical module.
l Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
----End
Related Information
None
A.3.165 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser is shut down. This alarm occurs when
the laser is shut down by using the NMS.
Attribute
Parameters
None


When the laser_shut alarm occurs, the optical interface fails to carry services.
Possible Causes
Cause 1: The laser on the local NE is shut down by using the NMS.
Procedure
Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.
1. Find out the cause of shutting down the laser and start up the laser as soon as possible.
----End
Related Information
None
A.3.166 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating that the LCAS protocol in the receive direction fails.
This alarm occurs if the receive unit of the LCAS module of a board detects an abnormal state
in which the LCAS might fail to negotiate or cannot negotiate correctly.
Attribute
Parameters
Name Meaning

The Ethernet service is not normal.

Possible Causes
l Cause 1: Configuration data of the LCAS protocol is incorrect.
l Cause 2: The link is faulty.
Procedure
Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.
1. Check whether the LCAS enabling state and the LCAS parameters are the same at both
ends of the link.
If... Then...
The settings of the LCAS protocols are not Properly enable the LCAS
consistent protocols at both ends.
The settings of the LCAS protocols at both ends Go to Cause 2.
are consistent
2. Check whether configurations of the local and opposite NEs are correct. For example,
check whether a VCG on one NE is connected to multiple VCGs on the opposite NE.
If... Then...
The configurations of the local and opposite NEs Correct the configuration data.
are incorrect
The configurations of the local and opposite NEs Go to Cause 2.
are correct
Step 2 Cause 2: The link is faulty.

1. Check whether the link where the service travels has errors or becomes faulty.
If... Then...
The link is faulty Rectify the fault.
The link is normal Go to the next step.
2. Restart the LCAS protocols at both ends. Then, check whether the alarm clears.
If... Then...
----End
Related Information
None

A.3.167 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating that the LCAS protocol in the transmit direction
fails. This alarm occurs if the transmit unit of the LCAS module of a board detects an
abnormal state in which the LCAS might fail to negotiate or cannot negotiate correctly.
Attribute
Parameters
Name Meaning

The Ethernet service is not normal.
Possible Causes
l Cause 1: Configuration data of the LCAS protocol is incorrect.
l Cause 2: The link is faulty.
Procedure
Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.
1. Check whether the LCAS enabling state and the LCAS parameters are the same at both
ends of the link.
If... Then...
The settings of the LCAS protocols are not Properly enable the LCAS
consistent protocols at both ends.
The settings of the LCAS protocol at both ends Go to Cause 2.
are consistent

2. Check whether configurations of the local and opposite NEs are correct. For example,
check whether a VCG on one NE is connected to multiple VCGs on the opposite NE.
If... Then...
The configurations of the local and opposite NEs Correct the configuration data.
are incorrect
The configurations of the local and opposite NEs Go to Cause 2.
are correct
Step 2 Cause 2: The link is faulty.

1. Check whether the link where the service travels has errors or becomes faulty.
If... Then...
The link is faulty Rectify the fault.
The link is normal Go to the next step.
2. Restart the LCAS protocols at both ends. Then, check whether the alarm clears.
If... Then...
----End
Related Information
None
A.3.168 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating that a part of the LCAS bandwidth in the receive
direction is lost. This alarm occurs when a board detects that the number of paths that carry
the overloads in the receive direction of the VCTRUNK with the LCAS function enabled is
less than the preset number but is not zero.
Attribute
Minor Service alarm
Parameters

Name Meaning

The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the
remote site is different from that at the local site.
l Cause 2: Some paths in the transmit direction of the remote site are faulty.
l Cause 3: Some paths in the receive direction of the local site are faulty.
Procedure
Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the
1. Check whether the VCTRUNKs at the transmit and the receive directions at the local site
are configured with the same number of physical paths and timeslots.
If... Then...
The sink and source VCTRUNKs are Correct the configuration data. For
bound with different number of physical details, see Dynamically Increasing/
paths or bound with different timeslots Decreasing the VCTRUNK Bandwidth.
Step 2 Cause 2: Some paths in the transmit direction of the remote site are faulty.
1. Check whether any path alarm exists in the transmit direction of the remote site.
If... Then...
Any of the preceding alarms occurs Clear the alarm immediately.
No alarm occurs Go to Cause 3.
Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.
----End
Related Information
None

A.3.169 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating that part of the LCAS bandwidth in the transmit
direction is lost. This alarm occurs when a board detects that the number of paths that carry
the overloads in the transmit direction of the VCTRUNK with the LCAS function enabled is
less than the preset number but is not zero.
Attribute

Minor Service alarm
Parameters
Name Meaning
0x01 indicate that the alarm is reported in VCTRUN 1.

The available transmit bandwidth of Ethernet services is less than the preset bandwidth. When
the transmitted services are more than the available transmit bandwidth, packet loss occurs.
Possible Causes
l Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the
l Cause 2: Some paths in the receive direction of the remote site are faulty.
l Cause 3: Some paths in the transmit direction of the local site are faulty.
Procedure
Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the
1. Check whether the sink and source VCTRUNKs are bound with the same number of
physical paths or the same timeslots.

If... Then...
The sink and source VCTRUNKs are bound Correct the configuration data.
with different number of physical paths or For details, see Dynamically
different timeslots Increasing/Decreasing the
VCTRUNK Bandwidth.
The sink and source VCTRUNKs are bound Go to Cause 2.
with the same number of physical paths or the
same timeslots
Step 2 Cause 2: Some paths in the receive direction of the remote site are faulty.
1. Check whether any path alarm exists in the receive direction of the remote site.
If... Then...
No alarm occurs Go to the next step.
Step 3 Cause 3: Some paths in the transmit direction of the local site are faulty.
----End
Related Information
None
A.3.170 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating that all the LCAS bandwidth in the receive direction
is lost. This alarm occurs when no path in the receive direction of the VCTRUNK with LCAS
enabled carries the overload but paths are configured to carry the overload.
Attribute
Major Service alarm
Parameters
Name Meaning

Name Meaning
Parameter 2, Parameter 3 Indicates the ID of the alarmed VCTRUNK. For example, 0x00
0x01 indicate that the alarm is reported in VCTRUN 1.

There is no available bandwidth in the receive direction, and the Ethernet services are
interrupted.
Possible Causes
l Cause 1: No VCTRUNK is bound to the remote port.
l Cause 2: Paths in the transmit direction of the remote site are faulty.
l Cause 3: Paths in the receive direction of the local site are faulty.
Procedure
Step 1 Cause 1: No VCTRUNK is bound to the remote port.
1. Check whether VCTRUNKs have been added in the receive direction at the local end
and in the transmit direction at the remote end.
If... Then...
VCTRUNKs has been added, Correct the configuration data. For details, see
Configuring VCTRUNKs on an Ethernet Board.
No VCTRUNK has been added, Go to Cause 2.
Step 2 Cause 2: Paths in the transmit direction of the remote site are faulty.
1. Check whether any path alarm exists in the transmit direction of the remote site.
If... Then...
No alarm occurs Go to Cause 3.
Step 3 Cause 3: Paths in the receive direction of the local site are faulty.
----End
Related Information
None

A.3.171 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating that all the LCAS bandwidth in the transmit
direction is lost. This alarm occurs when no path in the transmit direction of the VCTRUNK
with LCAS enabled carries the overload but paths are configured to carry the overload.
Attribute
Major Service alarm
Parameters
Name Meaning

There is no available bandwidth in the transmit direction, and the Ethernet services are
interrupted.
Possible Causes
l Cause 1: No VCTRUNK is bound to the remote port.
l Cause 2: Paths in the receive direction of the remote site are faulty.
l Cause 3: Paths in the transmit direction of the local site are faulty.
Procedure
Step 1 Cause 1: No VCTRUNK is bound to the remote port.
1. Check whether VCTRUNKs have been added in the receive direction at the local end
and in the transmit direction at the remote end.
If... Then...
VCTRUNKs has been added, Correct the configuration data. For details, see
Configuring VCTRUNKs on an Ethernet Board.

If... Then...
No VCTRUNK has been added, Go to Cause 2.
Step 2 Cause 2: Paths in the receive direction of the remote site are faulty.
1. Check whether any path alarm exists in the receive direction of the remote site.
If... Then...
No alarm occurs Go to the next step.
Step 3 Cause 3: Paths in the transmit direction of the local site are faulty.
----End
Related Information
None
A.3.172 LCD
Description
The LCD is an alarm indicating loss of cell delimitation. This alarm occurs when the OCD
alarm continuously occurs within the transmission period of N cells. The letter "N" indicates
the LCD alarm threshold value. For different ports, the threshold value is different.
Attribute
Parameters
None

l When the LCD alarm occurs, all the services in the receive direction of the port are
interrupted and all the connections at the port insert segment or end AIS cells to the
downstream.
Possible Causes
l Cause 1: The path connected to the ATM port receives signals in an incorrect manner.
For example, the MS_AIS, AU_AIS or AU_LOP alarm occurs.
l Cause 2: A great number of bit errors occur in the receive path. The receive path reports
alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.

l Cause 3: The ATM processing chip of the board is faulty.
Procedure
Step 1 Cause 1: The path connected to the ATM port receives signals in an incorrect manner. For
example, the MS_AIS, AU_AIS or AU_LOP alarm occurs.
1. Check whether the MS_AIS, AU_AIS, or AU_LOP alarm occurs in the path connected
to the ATM port.
2. If yes, clear these alarms first, and then check whether the LCD alarm is cleared.
Step 2 Cause 2: A great number of bit errors occur in the receive path. The receive path reports
1. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path.
2. If yes, clear these alarms first, and then check whether the LCD alarm is cleared.
Step 3 Cause 3: The ATM processing chip of the board is faulty.

1. Perform a cold reset on the board that reports the LCD alarm. For details, see 8.6.1 Cold
Reset.
2. If the LCD alarm persists, replace the alarmed board. For details, see 6.6 Replacing the
Smart E1 Interface Board.
----End
Related Information
End and segment
The end point, used to monitor the entire virtual connection, is set at the end of the chain
network.
The segment point is used to monitor a segment of the entire link.
Thresholds of generating the LCD alarm at different ports
l For the external ATM port, the threshold of generating the LCD alarm is seven cells.
l For a VC-4 VCTRUNK port, the threshold of generating the LCD alarm is 360 cells.
l For a VC-12 VCTRUNK port, the threshold of generating the ALM_IMA_LINK_LCD
alarm in the bound E1 link is 104 cells. If only one E1 link is bound with the
VCTRUNK, the LCD alarm is reported when the ALM_IMA_LINK_LCD alarm occurs.
If the VCTRUNK is bound with multiple E1 links in the IMA group, and if the number
of E1 links in which the ALM_IMA_LINK_LCD alarm occurs is greater than the value
derived from the total number of bound E1 links subtracted by the minimum number of
activated links in the receive direction of the IMA group, the LCD alarm is reported at
the VCTRUNK port. Otherwise, the LCD alarm is not reported.
A.3.173 LCS_DAYS_OF_GRACE
Description
The LCS_DAYS_OF_GRACE alarm indicates that a license file has expired but is in the
grace period of 60 days.

Attribute

Parameters
Name Meaning
Parameters 1 and 2 Indicate the ID of a control item.
Parameters 3 and 4 Indicate the remaining grace period (days) of the license file.
Parameter 5 Indicates the cause for the license file to become invalid:
l 0x00: The license file is naturally invalid.
l 0x01: The license file is forcibly invalid.
l 0x02: The ESN does not match.
l 0x03: The V/R version does not match.
l 0x04: Both the ESN and V/R version do not match.

System functions are not affected within the grace period of 60 days after a license file
expires. The LCS_DAYS_OF_GRACE alarm is reported each day to remind users to update
the license.
Possible Causes
l Cause 1: The license file has expired, but is in the grace period of 60 days.
l Cause 2: The ESN of the license file or the V/R version does not match, and the license
file is in the grace period of 60 days.
l Cause 3: A certain control item expires but is in the grace period of 60 days.
Procedure
Step 1 Contact Huawei technical support engineers to reload the associated license file.
----End
Related Information
None

A.3.174 LCS_EXPIRED
Description
The LCS_EXPIRED alarm indicates that a license file has expired and the grace period of 60
days times out.
Attribute
Parameters
Name Meaning
Parameters 1 Indicate the days since the grace period of a license has expired or the ID
and 2 of the expired license.
Parameter 3 Indicates the cause for the license file to become invalid:
l 0x00: The license file is naturally invalid.
l 0x01: The license file is forcibly invalid.
l 0x02: The ESN does not match.
l 0x03: The V/R version does not match.
l 0x04: Both the ESN and V/R version do not match.
l 0xff: Parameters 1 and 2 indicate the ID of the expired license.

After the license file expires and the grace period of 60 days times out, the system provides
the minimum default functions.
Possible Causes
l Cause 1: The system has run for more than 60 days after the license file expired.
l Cause 2: The system has run for more than 60 days after the ESN or V/R version of the
license file does not match.
Procedure
Step 1 Contact Huawei technical support engineers to reload the associated license file.
----End

Related Information
None
A.3.175 LCS_FILE_NOT_EXIST
Description
The LCS_FILE_NOT_EXIST alarm indicates that an NE fails to detect the ESDP license file.
Attribute
Parameters
None

If the license is not loaded, the system provides the minimum default functions.
Possible Causes
The system fails to find the ESDP license file when being started.
Procedure
Step 1 Purchase and load the ESDP license file.
----End
Related Information
None
A.3.176 LCS_LIMITED
Description
The LCS_LIMITED alarm indicates that the configuration capacity of an NE exceeds the
capacity authorized by the license file.
Attribute

Parameters

Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The service capacity exceeds the capacity authorized by the license
file.
l 0x02: The AM license capacity exceeds the capacity authorized by the
license file.
l 0x03: For IF protection, the bandwidth at the standby port authorized by
the license file is lower than the bandwidth at the main port authorized by
the license file.
l 0x04: The 1588v2 capacity exceeds the capacity authorized by the license
file.
l 0x05: The ATM/IMA capacity exceeds the capacity authorized by the
license file.
l 0x06: The air port LAG capacity exceeds the capacity authorized by the
license file.
l 0x07: The E1PRIOR function is restricted.
l 0x08: The synchronous Ethernet capacity exceeds the capacity authorized
by the license file.
l 0x09: The air port compression capacity exceeds the capacity authorized by
the license file
l 0x0a: The MPLS service license capacity exceeds the capacity authorized
by the license file.
l 0x0b: The PLA license capacity exceeds the capacity authorized by the
license file.
l 0x0c: The total service bandwidth (TDM service bandwidth and data
service bandwidth) exceeds the bandwidth allowed by the Ethernet license
file for the working and protection links.
l 0x0d: The GE port capacity exceeds the capacity authorized by the license
file.
l 0x0e: No XPIC license is available.
l 0x0f: No ERPS license is available.
l 0x10: The number of configured VC-12 cross connections exceeds the
number authorized by the license file.
l 0x11: The number of ports configured with the 1024QAM modulation
scheme exceeds the number authorized by the license file.
l 0x12: No microwave 1+1 protection license is available.
l 0x13: No enhanced QoS license is available.
l 0x14: The capacity configured for the COMBO port exceeds the licensed
capacity.
l 0x15: No second-IF-port license is available.
l 0x16: No MPLS-TP OAM license is available.
l 0x17: No WRED license is available.
l 0x18: No AMAC license is available.

Name Meaning
l 0x19: L3 functions are restricted.
l 0x1a: No HQoS license is available.
l 0x1b: No L2DCN license is available.
l 0x1c: No ITU-T Y.1731 license is available.
l 0x1d: No LLDP license is available.
l 0x1e: No STM-1 license is available.
l 0x1f: No PoE license is available.
l 0x20: No IS3 mode license is available.
l 0x21: No IP FPM license is available.
l 0x22: The 62.5M or 125M sub-bandwidth function is restricted.
l 0x23: The 1.25 Gbit/s CPRI function is restricted.
l 0x24: The 2.5 Gbit/s CPRI function is restricted.
l 0x25: The 250M bandwidth extension function is restricted.
l 0x26: The 2048QAM function is restricted.
l 0x27: The enhanced N+1 function is restricted.
l 0x28: The total capacity over air interfaces on an NE exceeds the total
licensed capacity.
l 0x29: The number of configurable IF air interfaces exceeds the licensed
capacity.
l 0x2a: The 2048QAM function is restricted.
l 0x2b: The AES function is restricted.
l 0x2c: The 4096QAM function is restricted.
l 0x2d: The XPIC capacity on an ISM6 board exceeds the licensed capacity.
l 0x2E: The virtual master function is restricted.
l 0x2F: The virtual AP function is restricted.
l 0x30: The number of connected virtual APs exceeds the upper threshold.
l 0x32: The number of boards supporting Super Dual Band exceeds the limit
authorized by the license file.
l 0x34: The license for the bandwidth notification function is not loaded.
l 0x36: The number of boards with the anti-theft function enabled exceeds
the license threshold.
l 0x37: The licensed capacity for the 10GE port is exceeded.

When the LCS_LIMITED alarm occurs, the change of radio service capacity cannot take
effect on the NE.
Possible Causes
l Cause 1: The configured capacity exceeds the licensed capacity.

l Cause 2: The configured function is unlicensed.
Procedure
Step 1 Determine the alarm cause according to alarm data on the NMS.
Step 2 Query the capacity of the license on the NMS.
Step 3 Cause 1: The configured capacity exceeds the licensed capacity.

1. Check whether the capacity suggested in the alarm data is required.
2. If yes, purchase and load the license with the desired capacity.
3. If not, rectify the capacity configuration.
Step 4 Cause 2: The configured function is unlicensed.

1. Check whether the configured function is required.
2. If yes, purchase and load the desired license.
3. If not, do not enable the function.
----End
Related Information
For TDM services, radio service capacities of NEs are calculated based on the service cross-
connections on IF boards.
A.3.177 LCS_TRIAL_PERIOD
Description
The LCS_TRIAL_PERIOD alarm indicates that an NE is in the trial period. This alarm is
reported when an NE that is powered on and does not have a license is in the trial period of 90
days.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the remaining trial period (days).


Functions of the NE are not affected during the trial period. After the trial period times out,
the NE reports the LICENSE_LOST alarm.
Possible Causes
Cause: An NE that is not loaded with a license is in the trial period of 90 days.
Procedure
Step 1 Purchase and load the license file.
----End
Related Information
None
A.3.178 LFA
Description
The LFA is an alarm indicating that the E1 frame alignment at the local end of the inverse
multiplexing for ATM (IMA) link in the receive direction is lost.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicates the path ID.

l When this alarm occurs, the alarmed E1 link is unavailable, and the available links in the
IMA group are reduced.
l If the VCTRUNK link binds only one member, the service is interrupted when the LFA
alarm occurs.

l After this alarm clears, the E1 link in the IMA group will be recovered automatically.
Possible Causes
The possible causes of the LFA alarm are as follows:
l Cause 1: The demultiplexing module of the E1 frame cannot perform the frame
alignment function, and therefore the frame alignment loss alarms are reported. These
alarms include TU_LOP, TU_AIS, and alarm indicating that the cross-connection is not
configured.
Procedure
Step 1 Cause 1: Check for the TU_LOP and TU_AIS alarms on the NMS. If these alarms occur,
handle these alarms first.

1. Check whether the HARD_BAD alarm occurs on the board.
2. If the alarm occurs, perform a cold reset on the board that reports the hardware
failure alarm, and check whether the alarm clears.
NOTICE
If the service on the board is not protected, a cold reset on the board causes service
interruptions.
3. If the alarm persists, replace the board. For details, see 6.7 Replacing the Ethernet
Interface Board or 6.6 Replacing the Smart E1 Interface Board.
----End
Related Information
Basic frame
A.3.179 LICENSE_LOST
Description
The LICENSE_LOST is an alarm indicating that the NE fails to detect the license file.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the type of the license file.
l 0x02: Hybrid license
l 0x03: TDM license
l 0x06: NE license

When the LICENSE_LOST alarm occurs, the functions authorized by the license file cannot
take effect.
Possible Causes
The license file is lost or is not loaded.
Procedure
Step 1 Contact Huawei engineers to reload the license file to the NE.
----End
Related Information
None
A.3.180 LINK_ERR
Description
The LINK_ERR alarm indicates that a data link is faulty.
Attribute

Parameters

Name Meaning
Parameter 1 Indicates the ID of the optical port. For example, 0x01 indicates that
the alarm is reported by optical port 1.
Parameter 2, Indicate the ID of the path that reports the alarm. For example, 0x00
Parameter 3 0x01 indicate that the alarm is reported by path 1.

Services in the alarmed path are interrupted.
Possible Causes
l Cause 1: The optical fiber connected to the Ethernet optical port is faulty.
l Cause 2: The working modes of the ports at the local and opposite ends are different.
l Cause 3: The equipment at the local or opposite end is faulty.
Procedure
Step 1 Cause 1: The optical fiber connected to the Ethernet optical port is faulty.
1. Check whether the optical fiber connected to the Ethernet optical port is faulty.
If... Then...
The optical fiber is faulty Replace the fiber.
The optical fiber is not faulty Go to Cause 2.
Step 2 Cause 2: The working modes of the ports at the local and opposite ends are different.
1. Check whether the working modes of the ports at the local and opposite ends are
different.
If... Then...
The working modes of the ports at the local and Set the working modes of the
opposite ends are different ports to the same.
The working modes of the ports at the local and Go to the next step.
opposite ends are the same
Step 3 Cause 3: The equipment at the local or opposite end is faulty.

1. Use an optical fiber to perform a loopback at the the alarmed port. For details, see 8.5
Hardware Loopback.
If... Then...
The alarm is cleared Replace the Ethernet board at the opposite end.
The alarm persists Replace the Ethernet board at the local end.
----End

Related Information
None
A.3.181 LMFA
Description
The LMFA is an alarm indicating the E1 multiframe alignment is lost when the E1 frame is a
CRC-4 multiframe.
Attribute

Parameters
Name Meaning
0x01.
Parameter 2, Parameter 3 Indicates the path ID.

When this alarm occurs, the alarmed E1 links become unavailable. As a result, fewer links of
the IMA group are available. If the IMA group is comprised of only one link, services will be
interrupted.
Possible Causes
The possible cause of the LMFA alarm is as follows:

l Cause 2: The frame format is incorrect.
Procedure
1. Check whether the HARD_BAD alarm occurs on the board.
2. If the alarm occurs, perform a cold reset on the board that reports the hardware
failure alarm, and check whether the alarm clears.

NOTICE
If the service on the board is not protected, a cold reset on the board causes service
interruptions.
3. If the alarm persists, replace the board.

Step 2 Cause 2: The frame format is incorrect.
1. Check the frame format of the opposite port. For details, see Setting Advanced Attributes
of Smart E1 Ports.
2. Set the frame format to CRC-4 Multiframe if it is incorrect.
----End
Related Information
Basic frame
Multiframe
A multiframe is composed of sixteen PCM frames, and can implement cyclic redundancy
check (CRC).
A.3.182 LOCAL_FAULT
Description
The LOCAL_FAULT alarm indicates that a fault occurs at a local Ethernet port.
Attribute
Parameters
None

If a 10GE optical port reports a LOCAL_FAULT alarm, services in the receive direction may
be interrupted.
Possible Causes
Possible causes of the LOCAL_FAULT alarm are as follows:
l Cause 1: The peer NE is faulty.

l Cause 2: The optical fiber connector or the optical fiber connected to the alarmed port in
the receive direction is faulty.
Procedure
Step 1 Cause 1: The peer NE is faulty.
1. Check on the U2000 whether the transmit optical power of the peer NE is within the
normal range. If the transmit optical power is out the normal range, rectify the fault on
the peer NE. If the transmit optical power is within the normal range, go to Step 2.
Step 2 Cause 2: The optical fiber connector or the optical fiber connected to the alarmed port in the
receive direction is faulty.
1. Check whether the receive optical power of the alarmed Ethernet port is within the
normal range on the U2000. If the receive optical power is beyond the normal range, go
to the next substep. If the receive optical power is within the normal range, go to Step 3.
NOTE
For optical power specifications of a board, see the Hardware Description, or query board bar
code to obtain manufacturing information about optical modules on the board.
2. Check whether the optical fiber connector is properly connected to the alarmed port. If
the optical fiber connector is loose, connect it securely.
3. Check whether the optical fiber connector is clean. If the optical fiber connector is dirty,
clean it by following instructions in Cleaning Optical Fiber Connectors.
4. Verify that the attenuation value of the optical attenuator is proper according to the
specified transmit optical power of the peer board.
5. Verify that the flange plate is properly connected.
6. Check whether the optical fiber in the receive direction is properly connected and is not
deteriorating. If the optical fiber is not properly connected, reconnect it. If the optical
fiber is aged, replace it with a new one.

1. Replace the alarmed board by following instructions in Part Replacement.
2. Check whether the LOCAL_FAULT alarm is cleared. If the alarm persists, contact
----End
Related Information
None
A.3.183 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a loop occurs.

Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of loopback.
l 0x00: optical/electrical port inloop
l 0x01: optical/electrical port outloop
l 0x02: path inloop
l 0x03: path outloop
l 0x04: loopback on the user side
l 0x05: loopback on the multiplexing side
l 0x06: SPI inloop
l 0x07: SPI outloop
l 0x08: ATM layer inloop
l 0x09: ATM layer outloop
l 0x0A: PHY layer inloop
l 0x0B: PHY layer outloop
l 0x0C: MAC layer inloop
l 0x0D: MAC layer outloop
l 0x0E: VC-4 timeslot inloop
l 0x0F: VC-4 timeslot outloop
l 0x10: VC-3 timeslot inloop
l 0x11: VC-3 timeslot outloop
l 0x12: VC-12 timeslot inloop
l 0x13: VC-12 timeslot outloop
l 0x14: IF outloop
l 0x15: IF inloop
l 0x16: RF inloop
l 0xFF: any of the preceding loopback modes

When the LOOP_ALM alarm occurs, the looped port or path cannot carry services.

Possible Causes
Cause 1: A loop is performed on the local NE.
Procedure
Step 1 Cause 1: A loop is performed on the local NE.
1. Determine the type of loopback according to the alarm parameter.
2. Find out the cause of the loopback, and set the loopback status of the alarmed port to
Non-Loopback.
For details, see 8.4 Software Loopback.
----End
Related Information
This table provides parameters and their meanings for LOOP_ALM alarms reported by ports
1 to 7 on an EMS6 board.
Name Meaning
Parameter 1 Indicates the optical port ID. The parameter

takes a fixed value of 0x01.
Parameter 2, Parameter 3 Indicate the path ID (the value 1 indicates

that the optical port is looped back).

Name Meaning
Parameter 4 Indicates loopback types.

l 0x00: inloops at optical/electrical ports
l 0x01: outloops at optical/electrical ports
l 0x02: inloops at paths
l 0x03: outloops at paths
l 0x04: loopbacks on the client side
l 0x05: loopbacks on the combination
wave side
l 0x08: inloops at the ATM layer
l 0x09: outloops at the ATM layer
l 0x0A: inloops at the PHY layer
l 0x0B: outloops at the PHY layer
l 0x0C: inloops at the MAC layer
l 0x0D: outloops at the MAC layer
l 0x0E: inloops at VC-4 timeslots
l 0x0F: outloops at VC-4 timeslots
l 0x10: inloops at VC-3 timeslots
l 0x11: outloops at VC-3 timeslots
l 0x12: inloops at VC-12 timeslots
l 0x13: outloops at VC-12 timeslots
l 0x14: outloops at IF ports
l 0x15: inloops at IF ports
l 0x16: inloops at RF ports
l 0xFF: any of the preceding loopback
modes
This table provides parameters and their meanings for LOOP_ALM alarms reported by ports
VC-3 channels on an EMS6 board.
Name Meaning
Parameter 1 Indicates the optical port ID. The parameter

takes a fixed value of 0x01.
Parameter 2, Parameter 3 Indicates the VC-3 channel ID.

A.3.184 LP_CROSSTR
Description
The LP_CROSSTR is an alarm indicating that the lower order path error crosses the
threshold. This alarm occurs when the board detects that the performance event that the lower
Attribute
Minor Service alarm
Parameters
Name Meaning
l 0x01: 15 minutes
l 0x02: 24 hours
l 0x90: LPBBE
l 0x91: LPES
l 0x92: LPSES
l 0x93: LPFEBBE
l 0x94: LPFEES
l 0x95: LPFESES
l 0x96: LPUAS
l 0x8e: LPFEUAS

When the LP_CROSSTR alarm occurs, a large number of errors occur in the service, and the
service may even be interrupted.
Possible Causes
Cause 1: The lower order path error crosses the preset threshold.
Procedure
Step 1 Cause 1: The lower order path error crosses the preset threshold.
1. Check the threshold crossing records to find out the performance event that the lower

----End
Related Information
None
A.3.185 LP_R_FIFO
Description
The LP_R_FIFO is an alarm indicating that the FIFO overflows on the receive side of the
lower order path.
Attribute
Parameters
None

When the LP_R_FIFO alarm occurs, the service has errors.
Possible Causes
l Cause 1: The clock of the local NE is not synchronized with the clock of the opposite
NE.
Procedure
Step 1 Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.
1. Browse current performance events, and check whether the performance event of TU
pointer justification occurs on the local NE and the opposite NE.
If... Then...
The TU pointer justification Handle the performance event. For details, see
occurs B.3.37 TUPJCHIGH, TUPJCLOW, and
TUPJCNEW.
The TU pointer justification does Go to Cause 2.
not occur

----End

Related Information
None
A.3.186 LP_RDI
Description
The LP_RDI is an alarm indicating the lower order path remote receive failure. This alarm
occurs when the board detects that bit 8 of byte V5 is 1.
Attribute

Parameters
None

When the LP_RDI alarm occurs, the service on the local NE is not affected. The service
received by the opposite NE, however, is interrupted.
Possible Causes
the lower order path remote receive failure.
Procedure
the lower order path remote receive failure.
1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None
A.3.187 LP_RDI_VC12
Description
The LP_RDI_VC12 is an alarm indicating that data reception fails at the remote end of VC-12
lower order path. This alarm occurs when the board detects that bit 8 of byte V5 is 1.

Attribute

Parameters
Name Meaning
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.

When this alarm occurs, the service on the local NE is not affected. The service received by
the opposite NE, however, is interrupted.
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that
data reception fails at the remote end of a lower order path.
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that
data reception fails at the remote end of a lower order path.
1. Handle the alarm of the lower order path on the remote site.
----End
Related Information
None
A.3.188 LP_RDI_VC3
Description
The LP_RDI_VC3 alarm indicates that data reception at the remote end of a lower order
(VC-3) path fails. A board reports this alarm when detecting that bit 5 in byte G1 is 1.

Attribute

Parameters
Name Meaning
path 1.

When the LP_RDI_VC3 alarm occurs, the services at the local site are not affected, but the
opposite site cannot receive services.
Possible Causes
The local site receives a message from the opposite site, and the message says that data
reception fails at the remote end of a lower order (VC-3) path.
Procedure
Step 1 Cause: The local site receives a message from the opposite site, and the message says that
data reception fails at the remote end of a lower order (VC-3) path.
1. Handle the alarm in the lower order (VC-3) path at the opposite site.
----End
Related Information
None
A.3.189 LP_REI
Description
The LP_REI is an alarm indicating the lower order path remote error. This alarm occurs when
the board detects that bit 3 of V5 is 1.

Attribute
Minor Service alarm
Parameters
None

When the LP_REI alarm occurs, the service on the local NE is not affected. The service
received by the opposite NE, however, has errors.
Possible Causes
the lower order path remote errors.
Procedure
the lower order path remote errors.
1. Handle the LP_BBE performance event on the opposite NE.
----End
Related Information
None
A.3.190 LP_REI_VC12
Description
The LP_REI_VC12 is an alarm indicating that there are bit errors at the remote end of a
VC-12 lower order path. This alarm occurs when the board detects that bit 3 of byte V5 is 1.
Attribute
Minor Service alarm
Parameters

Name Meaning
0x01.

Bit errors exist in the service in the receive direction of the remote site.
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that
there are bit errors in the lower order path.
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that
there are bit errors in the lower order path.
1. Handle the LPBBE performance event of the remote site.
----End
Related Information
None
A.3.191 LP_REI_VC3
Description
The LP_REI_VC3 alarm indicates that there are bit errors at the remote end of a lower order
(VC-3) path. A board reports this alarm when detecting that any one of bits 1 to 4 in byte G1
is 1.
Attribute
Parameters
Name Meaning

Name Meaning
path 1.

Bit errors exist in received services at the opposite site.
Possible Causes
The local site receives a message from the opposite site, and the message says that there are
bit errors at the remote end of a lower order (VC-3) path.
Procedure
Step 1 Cause: The local site receives a message from the opposite site, and the message says that
there are bit errors at the remote end of a lower order (VC-3) path.
1. Handle the alarm in the lower order (VC-3) path at the opposite site.
----End
Related Information
None
A.3.192 LP_RFI
Description
The LP_RFI is an alarm indicating the lower order path remote failure. This alarm occurs
when the board detects that bit 4 of V5 is 1.
Attribute

Parameters
None

When the LP_RFI alarm occurs, the service on the local NE is not affected. The alarm only
indicates that the lower order paths on the opposite NE cannot carry services.

Possible Causes
the lower order path remote failure.
Procedure
the lower order path remote failure.
1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None
A.3.193 LP_SLM
Description
The LP_SLM is an alarm indicating that a mismatched signal label is detected in the lower
order path. This alarm is reported when the board detects a signal label mismatch between the
V5 bytes.
Attribute

Parameters
None

The services in the lower order path are unavailable.
Possible Causes
Cause 1: The signal label contained in the V5 byte that is received by the local site does not
match with the signal label contained in the V5 byte that is transmitted by the remote site.
Procedure
Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does not

1. Modify the signal label contained in the V5 byte that is to be received by the local site or
is to be transmitted by the remote site. Ensure that the signal labels at both ends match
with each other. For details, see Configuring VC-12 POHs.
----End
Related Information
None
A.3.194 LP_SLM_VC12
Description
The LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in the
lower order path. This alarm is reported when the board detects a signal label mismatch
between the V5 bytes.
Attribute
Parameters
Name Meaning
0x01.

The service in this lower order path is unavailable.
Possible Causes
Cause 1: The signal label contained in the V5 byte that is received by the local site does not
Procedure
Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does not

1. Modify the signal label contained in the V5 byte that is to be received by the local site or
is to be transmitted by the remote site. Ensure that the signal labels at both ends match
with each other. For details, see Configuring VC-12 POHs.
----End
Related Information
None
A.3.195 LP_SLM_VC3
Description
The LP_SLM_VC3 alarm indicates that a mismatched signal label is detected in a lower order
(VC-3) path. A board reports this alarm when detecting a mismatched signal label in byte C2.
Attribute
Parameters
Name Meaning
path 1.

The services in the lower order (VC-3) path are unavailable.
Possible Causes
The signal label in byte C2 that is received at the local site does not match with the signal
label in byte C2 that is transmitted at the opposite site.
Procedure
Step 1 Cause 1: The signal label in byte C2 that is received at the local site does not match with the
signal label in byte C2 that is transmitted at the opposite site.

1. Reset the signal label in byte C2 that is received at the local site or the signal label in
byte C2 that is transmitted at the local site. Ensure that the signal labels are the same at
both sites. For details, see Configuring VC-4 POHs.
----End
Related Information
None
A.3.196 LP_T_FIFO
Description
The LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmit side of the
lower order path.
Attribute
Parameters
None

Bit errors occur in the services.
Possible Causes
l Cause 1: The frequency offset of the input signal is very large.
Procedure
Step 1 Cause 1: The frequency offset of the input signal is very large.
1. Use an SDH analyzer to check whether the frequency offset of the input signal is within
50 ppm.
If... Then...
The frequency offset is very large Troubleshoot the remote site.
The frequency offset is within 50 ppm Go to Cause 2.

----End

Related Information
None
A.3.197 LP_TIM
Description
The LP_TIM is an alarm indicating a mismatched trace identifier is detected in the lower
order path. This alarm is reported when the board detects a mismatch between the J2 bytes at
both ends.
Attribute

Parameters
None

None
Possible Causes
l Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to
be transmitted by the remote site.
l Cause 2: The data configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to be
transmitted by the remote site.
1. Set the byte mode of the J2 byte to be received by the local site to the disable mode.
Alternatively, set the J2 byte to be received by the local site to match with the J2 byte to
be transmitted by the remote site. For details, see Configuring VC-12 POHs.
Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.

1. Check whether the cross-connections of the intermediate nodes where the service travels
are configured correctly. If not, reconfigure the cross-connections. For details, see
Querying TDM Services.
----End
Related Information
None

A.3.198 LP_TIM_VC12
Description
The LP_TIM_VC12 is an alarm indicating a mismatched trace identifier is detected in the
lower order path. This alarm is reported when the board detects a mismatch between the J2
bytes at both ends.
Attribute
Parameters
Name Meaning
0x01.

None
Possible Causes
l Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to
be transmitted by the remote site.
l Cause 2: The data configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to be
transmitted by the remote site.
1. Set the byte mode of the J2 byte to be received by the local site to the disable mode.
Alternatively, set the J2 byte to be received by the local site to match with the J2 byte to
be transmitted by the remote site. For details, see Configuring VC-12 POHs.
Step 2 Cause 2: The data configuration at the intermediate nodes is incorrect.
1. Check whether the cross-connections of the intermediate nodes where the service travels
are configured correctly. If not, reconfigure the cross-connections. For details, see
Querying TDM Services.
----End

Related Information
None
A.3.199 LP_TIM_VC3
Description
The LP_TIM_VC3 alarm indicates that a mismatched trace identifier is detected in a lower
order (VC-3) path. A board reports this alarm when detecting a mismatched trace identifier in
byte J1.
Attribute
Parameters
Name Meaning
path 1.

None
Possible Causes
l Cause 1: Byte J1 to be received at the local site does not match with byte J1 to be
transmitted at the opposite site.
l Cause 2: The data configuration at intermediate sites is incorrect.
Procedure
Step 1 Cause 1: Byte J1 to be received at the local site does not match with byte J1 to be transmitted
1. Set byte J1 to be received at the local site to the disable mode or the same as byte J1 to
be transmitted at the opposite site. For details, see Configuring VC-4 POHs.
Step 2 Cause 2: The data configuration at intermediate sites is incorrect.

1. Check whether the cross-connections of intermediate sites where the services travel are
configured correctly. If not, reconfigure the cross-connections. For details, see Querying
TDM Services.
----End
Related Information
None
A.3.200 LP_UNEQ
Description
The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm is
reported when the board detects that the V5 byte signal label is 0.
Attribute
Parameters
None

The services in the path are unavailable. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
The data configuration is incorrect.
l Cause 1: The tributary path at the local site is configured with services, but the tributary
path at the remote site is not configured with services.
l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path
at the remote site is not configured with services.
1. Check whether the tributary path at the remote site is configured with services. For
details, see Querying TDM Services.
If... Then...
The tributary path at the remote site is not Configure services for the tributary
configured with services path at the remote site.

If... Then...
The tributary path at the remote site is Go to Cause 2.
configured with services
Step 2 Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.

1. Check whether the cross-connection configuration at the intermediate nodes is correct. If
not, reconfigure the cross-connections. For details, see Querying TDM Services.
----End
Related Information
None
A.3.201 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that the VC-12 path is unequipped. This alarm
occurs when the board detects that the V5 byte signal label is 0.
Attribute
Parameters
Name Meaning
0x01.

If the alarm is generated due to incorrect service configurations, the services are interrupted.
Possible Causes
path at the remote site is not configured with services.

l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
at the remote site is not configured with services.
1. Check whether the tributary path at the remote site is configured with services. For
If... Then...
The tributary path at the remote site is not configured with Configure services.
services
The tributary path at the remote site is configured with Go to Cause 2.
services
Step 2 Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.

1. Check whether the cross-connection configuration at the intermediate nodes is correct. If
----End
Related Information
None
A.3.202 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 alarm indicates that a lower order (VC-3) path is unequipped. A board
reports this alarm when detecting that the C2 byte signal label is 0.
Attribute

Parameters
Name Meaning

Name Meaning
path 1.

The services in the path are unavailable. If the services are configured with protection,
protection switching is triggered.
Possible Causes
path at the opposite site is not.
l Cause 2: The cross-connection configuration at the intermediate sites is incorrect.
Procedure
at the opposite site is not.
1. Check whether the tributary path at the opposite site is configured with services. For
If... Then...
The tributary path at the opposite site is not configured with Configure services.
services
The tributary path at the opposite site is configured with Go to Cause 2.
services
Step 2 Cause 2: The cross-connection configuration at the intermediate sites is incorrect.

1. Check whether the cross-connection configuration at the intermediate sites is correct. If
----End
Related Information
None
A.3.203 LPS_UNI_BI_M
Description
The LPS_UNI_BI_M is an alarm indicating that switching modes (single-ended or dual-
ended) at both ends of the linear MSP do not match with each other.

Attribute

Parameters
Name Meaning
0x01: linear MS protection.

The system performs protection switching in single-ended mode.
Possible Causes
Cause 1: The linear MSP is configured incorrectly.
The LPS_UNI_BI_M alarm is generated only when the following conditions are met:
l The switching modes (single-ended or dual-ended) at the local and remote sites are
different.
l The last three bits of the K2 byte are set to the indicated mode.
l The type of the protocol is set to a restructure protocol.
Procedure
Step 1 Cause 1: The linear MSP is configured incorrectly.
1. Change the MSP switching modes at both ends, and ensure that they are the same. For
details, see Querying the Status of the Linear MSP.
----End
Related Information
None

A.3.204 LPT_CFG_CLOSEPORT
Description
The LPT_CFG_CLOSEPORT is an alarm indicating that the LPT closes the access port of the
local NE. Upon detecting that the convergence port of the local NE or the access port of the
remote NE is faulty, the LPT automatically closes the access port of the local NE. Then, the
LPT_CFG_CLOSEPORT alarm is reported.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the board ID.
Parameter 3 Indicates the ID of the sub-board.
Parameter 4, Parameter 5 Indicate the port ID.

When this alarm occurs, services are switched to the backup network and the LPT closes the
access port of the remote NE at the same time.
Possible Causes
l Cause 1: The convergence port of the local NE or the access port of the remote NE is
faulty.
Procedure
Step 1 Cause 1: The convergence port of the local NE or the access port of the remote NE is faulty.
1. Check whether the convergence port of the local NE, the access port and the
convergence port of the remote NE report the ETH_LOS alarm or other alarms related
to boards and optical modules.
2. If yes, clear these alarms. Then, check whether the LPT_CFG_CLOSEPORT alarm is
cleared.
----End

Related Information
None
A.3.205 LPT_INEFFECT
Description
The LPT_INEFFECT is an alarm indicating that the LPT function fails. If the user configures
the LPT function but the board does not support the LPT function, the LPT_INEFFECT alarm
is reported.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the IP port.
Parameter 2, Parameter 3 Indicate the port ID.

The values are always 0x00 0x01.
Parameter 4, Parameter 5 The values are always 0xff 0xff.

When the alarm is generated, the services are not affected. If the board hardware is of a very
early version, the board software automatically prevents the LPT protocol state machine from
running, but reserves the LPT configuration.
Possible Causes
Cause 1: The board hardware is of a very early version, and the user configures the LPT
function.
Procedure
Step 1 Cause 1: The board hardware is of a very early version, and the user configures the LPT
function.

1. Check whether the LPT function is required.
If... Then...
The LPT function is Replace the board with a board of the proper version. For
required details, see 6 Part Replacement.
The LPT function is not Delete the configuration of the LPT. For details, see LPT
required Configuration.
----End
Related Information
None
A.3.206 LPT_RFI
Description
The LPT_RFI is a remote failure indication of the link path through (LPT) function. This
alarm occurs when the LPT function detects the failure of the remote port or the LPT service
network.
Attribute
Critical Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the ID of the IP port.
Parameter 2, Parameter 3 Indicate the ID of the optical interface. The values are always
0x00 0x01.

During the data transmission, the links are unavailable and the services are interrupted when
the LPT function detects the failure of the remote port or the service network. At the same
time, the backup links are enabled. If the backup links are available, the services can be
restored on the backup links.

Possible Causes
l Cause 1: The remote port fails due to the alarms such as ETH_LOS and
LSR_NO_FITED, or the remote port is disabled.
l Cause 2: The LPT service network is faulty.
– The communication link is interrupted.
– There are the bit error threshold-crossing alarms BIP_EXC and B3_EXC.
– There are the alarms such as TU_LOP, TU_AIS, VCAT_LOA,
VCAT_LOM_VC12, and LP_UNEQ_VC12.
Procedure
Step 1 Check the alarms on the NMS, determine the board that reports the LPT_RFI alarm, and then
determine the ID of the alarmed port on the board according to Parameter 1.
Step 2 Cause 1: The remote port fails due to the alarms such as ETH_LOS and LSR_NO_FITED,
or the remote port is disabled.
1. Check whether the corresponding opposite port is enabled.
If... Then...
The opposite port is disabled Enable the opposite port.
The opposite port is enabled Go to the next step.
2. Check whether any link fault alarm occurs on the line board.
If... Then...
Any link fault alarm occurs Handle the link fault alarms. Focus on the R_LOS and
MW_LOF alarms and handle them first.
No link fault alarm occurs Go to Cause 2.
Step 3 Cause 2: The LPT service network is faulty.

1. Check whether the following alarms occur on the Ethernet boards of the MEPs at both
ends. Then, handle the alarms.
– ETH_LOS
– LSR_NO_FITED
– BIP_EXC and B3_EXC
– TU_LOP, TU_AIS, VCAT_LOA, VCAT_LOM_VC12, and LP_UNEQ_VC12
----End
Related Information
None
A.3.207 LSR_BCM_ALM
Description
The LSR_BCM_ALM is an alarm indicating a threshold-crossing of the bias current of a
laser. This alarm is reported when the bias current of a laser exceeds the threshold.

Attribute
Parameters
None

When this alarm occurs, the laser is functioning improperly. An over-high current burns out
the laser, and an over-low current causes insufficient gains. Both can interrupt services.
Possible Causes
l Cause 1: The laser is aged.
l Cause 2: The laser is faulty.
Procedure
Step 1 Browse alarms on the NMS and determine the board that reports the alarm.
Step 2 Replace the pluggable optical module. For details, see Replacing Pluggable Optical
Modules.
----End
Related Information
None
A.3.208 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the SFP optical module is not installed.
Attribute
Parameters
None

The optical interface fails to carry services.

Possible Causes
l Cause 1: The laser of the local site is not installed.
Procedure
Step 1 Cause 1: The SFP optical module of the local site is not installed.
1. Find out why the SFP optical module is not installed, and contact Huawei technical
support engineers for the installation. If SFP module is not needed, see Configuring an
SFP Port to delete this port.

1. 6.14 Replacing the SFP.
----End
Related Information
None
A.3.209 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the laser is to stop working.
Attribute
Parameters
None

When this alarm occurs, bit errors occur in the service. If the board is not replaced in a timely
manner, services are interrupted after the laser is damaged.
Possible Causes
l Cause 1: The laser is aged.
l Cause 2: The detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The laser is aged.

1. 6.14 Replacing the SFP.
Step 2 Cause 2: The detection circuit of the board is faulty.

1. Replacing the alarm Board.
----End
Related Information
None
A.3.210 LTI
Description
The LTI is an alarm indicating that the synchronization sources are lost. This alarm is reported
when all the synchronization sources for the NE are lost.
Attribute
Parameters
Name Meaning
Parameter 1 0x01: system priority list
0x02: external clock priority list

The clock enters the free-run mode and loses synchronization with other NE clocks.
Possible Causes
l Cause 1: The clock configuration is incorrect.
l Cause 2: All the clock sources in the clock source priority table fail.
l Cause 3: A fiber cut or a cable cut occurs.
l Cause 4: The synchronization source is set to the manual reversion mode.
l Cause 5: No input is available from the external clock source.
l Cause 6: The board is faulty.

Procedure
Step 1 Cause 1: The clock configuration is incorrect.
1. Check whether the data in the clock source priority table meets the network planning
requirement. For details, see Querying the Clock Synchronization Status.
If... Then...
The configuration is incorrect Correct the configuration.
The configuration is correct Go to Cause 2.
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
1. Troubleshoot the synchronization sources based on the clock source priority table.
If... Then...
external clock
clock board.
clock
The synchronization source is an Handle the alarm that occurs on the Ethernet
Ethernet clock board.
Step 3 Cause 3: A fiber cut or a cable cut occurs.

1. Connect the fiber or cable properly.
Step 4 Cause 4: The synchronization source is set to the manual reversion mode.
1. See Modifying the Recovery Parameter of the Clock Source, and set the clock source to
the automatic reversion mode.
Step 5 Cause 5: No input is available from the external clock source.
1. See Configuring Clock Sources for External Clock Output, and configure the clock
source that provides external clock signals.
Step 6 Cause 6: The board is faulty.
1. Replace the board.
----End
Related Information
None

A.3.211 MAC_EXT_EXC
Description
The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer crosses
the threshold.
Attribute
Parameters
Parameters
Name Meaning
Parameter 1 Indicates the threshold crossing type.
l 0x01: ETHDROP threshold crossing
l 0x02: ETHEXCCOL threshold crossing
l 0x03: RXBBAD threshold crossing

When the MAC_EXT_EXC alarm occurs, the performance of services degrades.
Possible Causes
l Cause 1: ETHDROP threshold crossing. The number of packet loss events crosses the
upper threshold.
l Cause 2: ETHEXCCOL threshold crossing. The number of frames unsuccessfully
transmitted after successive collisions crosses the upper threshold.
l Cause 3: RXBBAD threshold crossing. The number of bytes in received bad packets
crosses the upper threshold.
Procedure
Step 1 Check whether the working modes of the ports at the transmit and receive ends are the same.
1. On the NMS, query the working modes of the ports at the transmit and receive ends.

If... Then...
The ports at the transmit and Set the working modes of the ports at the
receive ends work in different transmit and receive ends to full-duplex or auto-
modes or in half-duplex mode negotiation. Ensure that the working modes of
the ports at the transmit and receive ends are the
same. For details, see Setting the Basic
Attributes of Ethernet Ports.
The ports at the transmit and Go to the next step.
receive ends work in the same
mode and neither port works in
half-duplex mode.
Step 2 Handle the problem that the opposite site transmits packets abnormally.
Step 3 Handle the quality problem with the transmission line.

Check whether the local end reports alarms such as ETH_LOS as the external line is
damaged or over attenuated. If yes, see the related handling method to clear the alarms.
Step 4 Replace the faulty board.
----End
Related Information
None
A.3.212 MAC_FCS_EXC
Description
The MAC_FCS_EXC alarm indicates that the software detects that the number of bit errors at
the MAC layer crosses the threshold. The software periodically detects the number of bytes
received by the MAC chip and the number of bytes that have bit errors. The MAC_FCS_EXC
alarm is reported when the number of bit errors crosses the threshold.
Attribute

Parameters

Name Meaning
Parameter 1 l 0x00: indicates that a performance threshold is crossed.
l 0x01: indicates bit-error-triggered switching.

When the MAC_FCS_EXC alarm occurs, the performance of services degrades.
Possible Causes
l Cause 1: The performance of the line signals degrades.
l Cause 2: The input optical power is abnormal.
l Cause 3: A fiber connector is dirty.
Procedure
Step 1 Cause 1: The performance of the line signals degrades.
1. On the NMS, check for a LOOP_ALM alarm. If there is any, clear it. For details, see 8.4
Software Loopback.
2. If the MAC_FCS_EXC alarm persists, check whether the NMS is under a denial-of-
service (DOS) attack. If yes, eliminate the source that transmits a large amount of invalid
data, and then check whether the MAC_FCS_EXC alarm is cleared.
3. If the MAC_FCS_EXC alarm persists, check whether a cable or fiber is faulty. Replace
the faulty cable or fiber, and then check whether the MAC_FCS_EXC alarm is cleared.
Step 2 Cause 2: The input optical power is abnormal.

1. Check whether the alarmed port reports an IN_PWR_ABN alarm as well.
2. If there is any, clear the IN_PWR_ABN alarm.
Step 3 Cause 3: A fiber connector is dirty.

1. Clean the fiber connector and the optical receive port. For details, see 8.12 Cleaning
Fiber Connectors and Adapters.
----End
Related Information
None
A.3.213 MAC_FCS_SD
Description
The MAC_FCS_SD alarm indicates that bit errors detected at the MAC layer exceed the
threshold. NE software periodically detects the number of bytes received by MAC chips and
the bytes that contain bit errors, and check the number of bit errors against the signal degrade
(SD) threshold. This alarm is reported if bit errors cross the threshold.

Attribute
Parameters
None

Service performance deteriorates.
Possible Causes
l Cause 1: Line signals degrade.
l Cause 2: Input optical power is abnormal.
l Cause 3: Fiber connectors are dirty.
Procedure
Step 1 Cause 1: Line signals degrade.
1. On the NMS, check whether a LOOP_ALM alarm is reported. If a LOOP_ALM alarm
is reported, clear it. For details, see 8.4 Software Loopback.
2. If the MAC_FCS_SD alarm persists, check whether any source unexpectedly sends a
large amount of data, such as DOS attacks. If yes, eliminate the data source.
3. If the alarm persists, check whether the cable or fiber is faulty. If the cable or fiber is
faulty, replace the faulty cable or fiber.
Step 2 Cause 2: Input optical power is abnormal.

1. Check whether the local port also reports an IN_PWR_ABN alarm.
2. If an IN_PWR_ABN alarm is also reported, clear it.
Step 3 Cause 3: Fiber connectors are dirty.

1. Clean the fiber connectors and the receive port of the processing board. For details, see
8.12 Cleaning Fiber Connectors and Adapters.
----End
Related Information
None
A.3.214 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that Module communicates abnormally.

Attribute
Parameters
Name Meaning
Parameter 1 0x11 indicates that the communication between the system control unit and
packet switching unit is failed.

The related operations cannot be performed by using the NMS and the performance
information of each module cannot be queried.
Possible Causes
l Cause 1: The software processing of the related modules of the board is faulty.
l Cause 2: The board hardware is faulty.
Procedure
Step 1 Cause 1: The software processing of the related modules of the board is faulty.
1. Perform a cold reset on the faulty board by using the NMS. For details, refer to 8.6.1
Cold Reset.
2. remove the faulty board and insert it again.
Step 2 Cause 2: The board hardware is faulty.
1. Replace the faulty board. For details, refer to 6.10 Replacing the System Control,
----End
Related Information
None
A.3.215 MOD_TYPE_MISMATCH
Description
The MOD_TYPE_MISMATCH alarm indicates that a mismatched port module is detected.

Attribute

Critical Maloperation
Parameters
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by port 1.

The services at the alarmed port are interrupted.
Possible Causes
Cause 1: The preset type of the SFP module is different from the actual type of the SFP
module.
Procedure
Step 1 Cause 1: The preset type of the SFP module is different from the actual type of the SFP
module.
1. Find out the port that reports the alarm according to the alarm parameters.
2. Check whether the preset type of the SFP module is the same as the actual type of the
SFP module.
If... Then...
The preset type of the SFP module is the Replace the optical/electrical SFP
same as the actual type of the SFP module module. Ensure that the new SFP
module is of the correct type.
The preset type of the SFP module is Reset the type of the SFP module.
different from the actual type of the SFP
module
----End
Related Information
None

A.3.216 MP_DELAY
Description
The MP_DELA is an alarm indicating a delay of the Multi-link Point-to-Point (ML-PPP)
group. This alarm is reported when the differential delay between MP group members
exceeds the threshold.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the board.
Parameter 2 Indicates the ID of the subborad.
Parameter 3, Parameter 4 Indicates the ID of the port.
Parameter 5 Indicates the ID of the timeslot or channel.

0xFF indicates that the parameter value is reserved.

When this alarm occurs, the service quality of the MP group deteriorates.
Possible Causes
l Cause 1: The signal quality of the MP group members deteriorates.
l Cause 2: The maximum differential delay is configured low.
Procedure
Step 1 Cause 1: The signal quality of the MP group members deteriorates.
1. Check whether the network is congested. If yes, expand the network and then check
2. If the alarm persists, replace the cable connecting to the port that reports the alarm. Then,

Step 2 Cause 2: The maximum differential delay is configured low.

1. Check whether the maximum differential delay is configured properly on the NMS. For
details, see Creating MP Groups.
2. If the maximum differential delay is configured low, increase the value based on the
actual situation or disable the fragment function.
----End
Related Information
None
A.3.217 MP_DOWN
Description
The MP_DOWN is an alarm indicating a failure of the Multi-link Point-to-Point (ML-PPP)
group. This alarm is reported when the number of the valid activated MP group members is
less than that of the specified minimum activated links. The minimum activated links is 1 by
default.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the cause of the failure.

l 0x00: unknown
l 0x01: indicates that the number of the MP group members is less than the
specified number.
l 0x02: indicates that the configurations at both ends of the MP group are
inconsistent.
l 0x03: indicates that the NCP protocol of the MP group is running
improperly.

l When this alarm occurs, all services that the MP group carries are interrupted.

l This alarm is cleared automatically when the number of the valid activated MP group
members is greater than the specified minimum activated links and the MP group is
configured with an IP address.
Possible Causes
l Cause 1: The number of the valid activated MP group members is less than that of the
minimum activated links.
l Cause 2: The configurations at both ends of the MP group are inconsistent.
l Cause 3: The NCP protocol on the member links of the MP group is running improperly.
l Cause 4: The physical link is interrupted.
l Cause 5: The MP group is not configured with an IP address or a subnet mask.
Procedure
Step 1 Cause 1: The number of the valid activated MP group members is less than that of the
minimum activated links.
1. On the NMS, check whether the number of the valid activated MP group members is less
than that of the minimum activated links. For details, see Querying the MP Group
Protocol Information.
2. If the number is less than that of the minimum activated links, change the minimum
activated links to a value less than the number of configured MP group members.
Step 2 Cause 2: The configurations at both ends of the MP group are inconsistent.
1. On the NMS, check whether the configurations at both ends of the MP group are
consistent. If not, modify the parameters. For details, see Creating MP Groups.
Step 3 Cause 3: The NCP protocol on the member links of the MP group is running improperly.
1. On the NMS, check whether the PPP_LCP_FAIL or PPP_NCP_FAIL alarm exists on
the member links of the MP group.
2. If yes, clear the PPP_LCP_FAIL or PPP_NCP_FAIL alarm immediately. Then, check
whether the MP_DOWN alarm is cleared.
Step 4 Cause 4: The physical link is interrupted.

1. On the NMS, check whether a signal alarm such as R_LOS or T_ALOS exists on the
member links of the MP group.
2. If yes, clear the R_LOS or T_ALOS alarm immediately.
Step 5 Cause 5: The MP group is not configured with an IP address or a subnet mask.
1. Configure an IP address and a subnet mask for the MP group. For details, see Creating
MP Groups.
----End
Related Information
None

A.3.218 MPLSLDPSESSIONDOWN
Description
The MPLSLDPSESSIONDOWN alarm indicates the interruption of an LDP session.
Attribute
Parameters
Name Meaning
Parameters 1-4 Indicate the peer LSR ID.
Parameters 5 and 6 Indicate the peer label space.
Parameters 7-10 Indicate the session status.
Parameters 11-14 Indicate the cause of the LDP session interruption.
Parameters 15-78 Indicate the name of a neighbor interface.

When this alarm occurs, related services are interrupted.
Possible Causes
l Cause 1: Parameters configured for the service interfaces are incorrect.
l Cause 2: The LDP configurations at both ends are inconsistent.
l Cause 3: The link between the local NE and its neighbor NE is faulty.
l Cause 4: The neighbor NE is faulty.
Procedure
Step 1 Cause 1: Parameters configured for the service interfaces are incorrect.
1. Check whether parameters configured for interfaces at both ends are correct, for
example, whether the interfaces are enabled and whether the interface IP addresses
match.
Step 2 Cause 2: The LDP configurations at both ends are inconsistent.
1. Check whether LDP parameters (such as LDP enable/disable status and LDP
authentication mode) are consistently configured at both ends. If no, modify the LDP
configurations according to the network plan.

Step 3 Cause 3: The link between the local NE and its neighbor NE is faulty.
1. Check whether the link between the local NE and its neighbor NE is faulty. For example,
check whether the ETH_LOS alarm is reported at the local end. If yes, clear the
ETH_LOS alarm first.
Step 4 Cause 4: The neighbor NE is faulty.

----End
Related Information
None
A.3.219 MPLSLSP_TBL_LACK
Description
The MPLSLSP_TBL_LACK alarm indicates that MPLS label resources are deficient. This
alarm is reported when MPLS label resources are deficient because the number of MPLS
LSPs exceeds equipment specifications.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the LSP type. This parameter takes the fixed value of 0x01
(LDP LSP).
Parameter 2 Indicates an ingress or egress label.

l 0x01: ingress label
l 0x02: egress label
Parameters 3-6 Indicate the label value.
Parameters 7-10 Indicate the VRF ID, which is used to identify an L3 VPN instance.
Parameters 11-14 Indicate the destination IP address.
Parameter 15 Indicates the mask length.


When this alarm occurs, the number of MPLS LSPs has reached the upper threshold. New
services are unavailable because new LSPs cannot be set up.
Possible Causes
Cause: The policy to set up LDP LSPs is incorrect, which causes the occupation of lots of
MPLS label resources.
Procedure
Step 1 Check whether the setup of LDP LSPs is triggered by host routes. If no, modify the
configuration.
Step 2 If the the LDP LSP setup policy is correct, re-plan services.
----End
Related Information
None
A.3.220 MPLS_PW_AIS
Description
The MPLS_PW_AIS is an alarm indicating a defect in the forward direction of a PW. This
alarm is reported when the Ethernet port receives an AIS packet, indicating that a fault occurs
on the tunnel at the server layer of the PW.
Attribute
Parameters
None

Possible Causes
Cause 1: The MPLS-TP OAM is incorrectly configured for tunnels between upstream NEs.
Cause 2: An upstream NE detects a fault on the tunnel at the PW server layer.

Procedure
Step 1 Cause 1: The MPLS-TP OAM is incorrectly configured for tunnels between upstream NEs.
1. Check whether the MPLS-TP OAM is configured correctly for tunnels between the local
NE and its upstream NEs. If not, modify the configuration. For details, see Configuring
MEP Parameters for MPLS-TP PW OAM.
Step 2 Cause 2: An upstream NE detects a fault on the tunnel at the PW server layer.
1. Check whether a tunnel fault occurs on the S-PE. If an alarm such as
MPLS_TUNNEL_LOCV exists, clear the alarm immediately.
----End
Related Information
None
A.3.221 MPLS_PW_CSF
Description
The MPLS_PW_CSF alarm indicates that client signals fail at the peer end of a PW. This
alarm is reported when one end of a PW receives Client Signal Fail (CSF) OAM packets from
the peer end.
Attribute
Parameters
None

Services may be interrupted.
Possible Causes
Cause 1: A link or hardware is faulty on the UNI side of the peer NE.
Procedure
Step 1 Cause 1: A link or hardware is faulty on the UNI side of the peer NE.
1. Check whether the peer NE reports any link- or hardware-related alarm on the UNI side.
If yes, clear the alarm.
Possible alarms include:

– Link-related alarm: ETH_LOS

– Hardware-related alarm: BD_STATUS, HARD_BAD
– Alarm related to the IEEE 802.3ah protocol: ETH_EFM_DF,
ETH_EFM_LOOPBACK
----End
Related Information
None
A.3.222 MPLS_PW_BDI
Description
The MPLS_PW_BDI is an alarm of PW backward defect indication. This alarm occurs when
the local NE receives the BDI packet, notifying that the remote NE detects that the PW is
faulty.
Attribute
Parameters
None

The services on the transmit side of the local NE are faulty.
Possible Causes
Cause 1: The remote NE detects that the PW is faulty.
Procedure
Step 1 Cause 1: The remote NE detects that the PW is faulty.
If... Then...
A board on the remote NE is reset or faulty Rectify the fault on the remote NE.
The physical link between the local NE and the Rectify the fault on the physical link.
remote NE is faulty
The bandwidth allocated to the PW is fully Increase the bandwidth of the PW.
occupied.
----End

Related Information
None
A.3.223 MPLS_PW_Excess
Description
The MPLS_PW_Excess is an alarm indicating that excessive trail termination source
identifiers (TTSIs) are received on the PW. This alarm occurs when five or more correct
CV/FFD packets are received within three consecutive CV/FFD periods.
Attribute
Warning Communication alarm
Parameters
None

Services may be interrupted if excessive redundant packets are received.
Possible Causes
l Cause 1: Multiple PWs are configured with the same label and PW ID.
l Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: Multiple PWs are configured with the same label and PW ID.
1. Check whether multiple PWs are configured with the same label and PW ID.
2. If yes, delete the redundant PWs or change the PW ID and label of each PW to unique
values.
If... Then...
Step 2 Cause 2: Physical links are misconnected.

1. Check whether any fiber or cable is misconnected.
2. If yes, rectify the fault.
----End

Related Information
None
A.3.224 MPLS_PW_LCK
Description
The MPLS_PW_LCK alarm indicates that a server layer tunnel is administratively locked.
This alarm is reported when the MEP receives a LCK message.
Attribute
Parameters
None

The server-layer tunnel is locked for diagnostic testing or other administrative purposes.
Possible Causes
Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
Procedure
Step 1 Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
1. Check whether tunnel locking is enabled on the nodes along the PW path. If yes, disable
the CLK after administrative locking (for diagnostic testing or other administrative
purpose) is no longer needed.
----End
Related Information
None
A.3.225 MPLS_PW_LOCK
Description
The MPLS_PW_LOCK alarm indicates that the locked signal function (LCK) is enabled for
the PW layer.

Attribute
Parameters
None

The PW is locked for diagnostic testing or other administrative purposes.
Possible Causes
Cause 1: Administrative locking is enabled for the PW layer.
Procedure
Step 1 Cause 1: Administrative locking is enabled for the PW layer.
1. Check whether the LCK is enabled for the PW layer. If yes, disable the CLK after
administrative locking (for diagnostic testing or other administrative purpose) is no
longer needed.
----End
Related Information
None
A.3.226 MPLS_PW_LOCV
Description
The MPLS_PW_LOCV is an alarm of PW connectivity loss. This alarm occurs when no
expected CV/FFD packets are received within three consecutive CV/FFD periods.
Attribute
Parameters
None


Possible Causes
l Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
l Cause 2: The OAM is different between the ends of the PW.
l Cause 3: The PW that carries services is faulty.
l Cause 4: The remote NE of the PW is faulty.
l Cause 5: The service interface is configured incorrectly.
l Cause 6: Serious congestion occurs on the network.
Procedure
Step 1 Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
1. Check whether the remote NE of the PW stops transmitting CV/FFD packets.
If... Then...
The remote NE of the PW stops transmitting Enable the CV/FFD detection and
CV/FFD packets then check whether the alarm clears.
The remote NE of the PW keeps transmitting Go to Cause 2.
CV/FFD packets
Step 2 Cause 2: The OAM is different between the ends of the PW.
1. Check whether the OAM is different between the ends of the PW. If no, Setting PW
OAM (Y.1711) Parameters according to the plan. If yes, go to cause 3.
Step 3 Cause 3: The PW that carries services is faulty.

1. Check whether the local NE and remote NE of the PW report any alarm related to
boards. If yes, clear the alarm. Then, check whether the MPLS_PW_LOCV alarm is
cleared.
2. Check whether any link-related alarm is reported. If yes, clear the alarm. Then, check
whether the MPLS_PW_LOCV alarm is cleared.
If... Then...
Step 4 Cause 4: The remote NE of the PW is faulty.

1. Check whether the interconnected board of the remote NE reports the COMMUN_FAIL
alarm. If yes, the board is being reset. Clear the COMMUN_FAIL alarm and then check
whether the MPLS_PW_LOCV alarm is cleared.
2. If the interconnected board of the remote NE reports other alarms, clear these alarms.
Then, check whether the MPLS_PW_LOCV alarm is cleared.

If... Then...
Step 5 Cause 5: The service interface is configured incorrectly.

1. Check whether the service interface is configured correctly according to service
planning.
2. If not, reconfigure the service interface. Then, check whether the MPLS_PW_LOCV
alarm is cleared.
If... Then...
Step 6 Cause 6: Serious congestion occurs on the network.

1. Check whether the bandwidth allocated to the faulty tunnel is fully occupied.
2. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large
amount of invalid data.
----End
Related Information
None
A.3.227 MPLS_PW_MISMATCH
Description
The MPLS_PW_MISMATCH is an alarm indicating that the trail termination source
identifiers (TTSIs) on the PW do not match with the specified one. This alarm occurs when
only the packets with wrong TTSIs are received within three consecutive CV/FFD periods.
Attribute
Parameters
None

Services are interrupted or the packets from other PWs are received.

Possible Causes
l Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.
Procedure
Step 1 Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.
1. Check whether the ingress node and egress node of the faulty PW are configured
correctly according to NE planning.
2. If the ingress node or egress node is configured incorrectly, correct the configuration and
then check whether the alarm clears.
----End
Related Information
None
A.3.228 MPLS_PW_MISMERGE
Description
The MPLS_PW_MISMERGE is an alarm indicating that the trail termination source
identifiers (TTSIs) are mismerged on the PW. This alarm is reported if the CV/FFD packets
with correct TTSIs and those with wrong TTSIs are received in three consecutive CV/FFD
periods.
Attribute
Parameters
None

Services are interrupted or the packets from other PWs are received.
Possible Causes
l Cause 1: The PW is configured incorrectly.

Procedure
Step 1 Cause 1: The PW is configured incorrectly.
1. Check whether the PW are configured correctly according to NE planning.
2. If the PW is configured incorrectly, correct the configuration and then check whether the
alarm clears.
----End
Related Information
None
A.3.229 MPLS_PW_OAMFAIL
Description
The MPLS_PW_OAMFAIL is an alarm indicating a failure of the OAM protocol negotiation.
This alarm is reported when the OAM protocol negotiation fails on NEs at both ends of the
PW.
Attribute
Parameters
None

When this alarm occurs, the PW APS protection switching is triggered, and services are
Possible Causes
Cause 1: The OAM function is enabled only on the NE at one end of the PW.
NOTE
Only the NE that is enabled with the OAM function reports the MPLS_PW_OAMFAIL alarm.
Cause 2: The PW has been interrupted when enabling the OAM function.
NOTE
When the PW is interrupted in the forward or reverse direction, the peer or local NE reports the
MPLS_PW_OAMFAIL alarm.

Procedure
Step 1 Cause 1: The OAM function is enabled only on the NE at one end of the PW.
1. On the NMS, query this alarm and check whether the OAM function is enabled on NEs
at both ends of the PW. If the OAM function is enabled only on one NE, set OAM
Status to Enabled on the other NE.
Step 2 Cause 2: The PW has been interrupted when enabling the OAM function.
1. On the NMS, check whether tunnel-related alarms such as A.3.245
MPLS_TUNNEL_OAMFAIL occur on NEs at both ends of the PW. If yes, clear them
immediately.
2. Check whether service-related alarms such as A.3.226 MPLS_PW_LOCV occur on
NEs at both ends of the PW. If yes, clear them immediately.
----End
Related Information
None
A.3.230 MPLS_PW_RDI
Description
The MPLS_PW_RDI is an alarm indicating a defect in the backward direction of a PW. The
local MEP sends an RDI packet to the remote MEP when detecting a PW fault. The
MPLS_PW_RDI alarm is reported when the remote MEP receives the RDI packet.
Attribute
Parameters
None

When this alarm occurs, services in the transmit direction on the remote MEP are affected.
Possible Causes
The local MEP NE detects a PW fault.
Procedure
Step 1 Handle the PW fault according to the MPLS-TP OAM-related alarm reported by the remote
MEP.

Step 2 If the alarm persists, check whether the physical link between faulty NEs is faulty. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty optical
fiber or cable.
Step 3 Check whether the bandwidth allocated to the PW is used up. If yes, increase the bandwidth
allocated to the PW.
----End
Related Information
None
A.3.231 MPLS_PW_SD
Description
The MPLS_PW_SD is an alarm of signal degrade on the PW. This alarm is reported when the
packet loss rate of the connectivity check (CC) crosses the SD threshold but is lower than the
SF threshold.
Attribute
Parameters
None

Services degrade and moderate packet loss occurs.
Possible Causes
l Cause 1: The bandwidth of the PW is fully occupied.
l Cause 2: The physical port has bit errors or packet loss.
l Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied.
1. Check whether the bandwidth allocated to the faulty PW is fully occupied.
amount of invalid data. Then, check whether the MPLS_PW_SD alarm is cleared.
Step 2 Cause 2: The physical port has bit errors or packet loss.
1. Check whether the fiber connector is loose. If yes, insert the fiber connector securely.

Step 3 Cause 3: The fiber connector or the optical module is dirty.

1. Clean the fiber connector or the optical module. For details, see Checking and cleaning
fiber connectors.
----End
Related Information
None
A.3.232 MPLS_PW_SF
Description
The MPLS_PW_SF is an alarm of signal failure on the PW. This alarm occurs when the
number of received connectivity check (CC) packets is less than the signal failure (SF)
threshold.
Attribute
Parameters
None

Services fail and severe packet loss occurs.
Possible Causes
l Cause 1: The bandwidth of the PW is fully occupied.
l Cause 2: The physical port has bit errors or packet loss.
l Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied.
1. Check whether the bandwidth allocated to the faulty PW is fully occupied.
amount of invalid data. Then, check whether the MPLS_PW_SF alarm is cleared.
Step 2 Cause 2: The physical port has bit errors or packet loss.
1. Check whether the fiber connector is loose. If yes, insert the fiber connector securely.
Step 3 Cause 3: The fiber connector or the optical module is dirty.

1. Clean the fiber connector or the optical module. For details, see Checking and cleaning
fiber connectors.
----End
Related Information
None
A.3.233 MPLS_PW_UNEXPMEG
Description
The MPLS_PW_UNEXPMEG is an alarm indicating that the MEP receives a packet with
correct MEG level but incorrect MEG ID.
Attribute
Parameters
None

When this alarm occurs, the MEP receives CCM packets of other PWs.
Possible Causes
l Cause 1: MEG IDs configured on NEs at both ends of the PW are different.
l Cause 2: The PW is configured incorrectly. Multiple PWs use the same label.
Procedure
Step 1 Cause 1: MEG IDs configured on NEs at both ends of the PW are different.
1. Check whether the PW configurations are consistent between NEs at both ends of the
PW. MEG IDs on NEs at both ends of a PW must be set to the same value. For details,
see Querying Information and Running Status of PWs.
Step 2 Cause 2: The PW is configured incorrectly. Multiple PWs use the same label.
1. Check whether the PW label is configured correctly. If multiple PWs use the same label,
reconfigure the PW label. For details, see Querying Information and Running Status of
PWs.
----End
Related Information
None

A.3.234 MPLS_PW_UNEXPMEP
Description
The MPLS_PW_UNEXPMEP is an alarm indicating an error in the PW OAM CCM
information. This alarm is reported when the sink NE of the PW receives a CCM packet with
an unexpected MEP ID.
Attribute
Parameters
None

When this alarm occurs, services are interrupted or the sink NE receives CCM packets of
other PWs.
Possible Causes
MEP IDs are inconsistent between NEs at both ends of a PW.
Procedure
Step 1 MEP IDs are inconsistent between NEs at both ends of a PW.
1. Check whether the remote MEP ID on the source NE is correctly configured with the
MEP ID of the sink NE. If not, reconfigure the remote MEP ID on the source NE.
----End
Related Information
None
A.3.235 MPLS_PW_UNEXPPER
Description
The MPLS_PW_UNEXPPER is an alarm indicating that the PW does not receive the CCM
packet in the expected period. This alarm is reported when the sink NE of the PW receives a
CCM packet with correct MEG level, MEG ID, and MEP ID but in an unexpected period. For
example, the transmit interval configured on the source and sink NEs is 10 ms, but the sink
NE receives the CCM packet from the source NE after 20 ms.

Attribute
Parameters
None

other PWs.
Possible Causes
CCM packet periods are inconsistent between the source and sink NEs at both ends of the
PW.
Procedure
Step 1 CCM packet periods are inconsistent between the source and sink NEs at both ends of the
PW.
1. Check whether PW configurations are consistent between the source and sink NEs. CCM
packet periods on NEs at both ends of a PW must be set to the same value. For details,
see Querying Information and Running Status of PWs.
----End
Related Information
None
A.3.236 MPLS_PW_UNKNOWN
Description
The MPLS_PW_UNKNOWN is an alarm of unknown defects on the PW. This alarm occurs
when the connectivity check (CC) packets of unexpected types, periods, and values are
received within three consecutive periods.
Attribute

Parameters
None

PW OAM fails.
Possible Causes
Cause 1: The PW OAM configuration at the two ends is different.
Procedure
Step 1 Cause 1: The PW OAM configuration at the two ends is different.
1. Change the PW OAM configuration to the same at the two ends.
----End
Related Information
None
A.3.237 MPLS_TUNNEL_AIS
Description
The MPLS_TUNNEL_AIS is an alarm indicating a defect in the forward direction of a tunnel.
This alarm is reported when the Ethernet port receives an AIS packet, indicating that a fault
occurs on the physical link at the server layer of the tunnel.
Attribute
Parameters
None

Possible Causes
An upstream NE detects a fault on the physical link at the server layer of the tunnel.

Procedure
Step 1 An upstream NE detects a fault on the physical link at the server layer of the tunnel.
1. Check whether the physical link is faulty between the local NE and the upstream NE.
Physical link faults may be caused by a fiber cut, a faulty optical module, or a faulty
board. If yes, rectify the faults.
----End
Related Information
None
A.3.238 MPLS_TUNNEL_BDI
Description
The MPLS_TUNNEL_BDI is an alarm of tunnel backward defect indication. This alarm
occurs when the port of the local NE receives the backward defect indication (BDI) packet,
notifying that the opposite NE detects that the tunnel is faulty.
Attribute
Parameters
None

When this alarm occurs, the services on the local NE is normal.
Possible Causes
Cause 1: The opposite NE detects MPLS alarms.
Procedure
Step 1 Cause 1: The opposite NE detects MPLS alarms.
1. Clear the MPLS alarms reported on the opposite NE.
----End
Related Information
None

A.3.239 MPLS_TUNNEL_EXCESS
Description
The MPLS_TUNNEL_EXCESS is an alarm indicating that excessive trail termination source
identifiers (TTSIs) are received in the tunnel. This alarm occurs when the Ethernet port of the
local NE receives five or more correct CV/FFD packets within three consecutive CV/FFD
periods.
Attribute
Parameters
None

Services may be interrupted if excessive redundant packets are received.
Possible Causes
Procedure
1. Check whether any fiber or cable is misconnected between the two ends. If yes,
reconnect the fiber or cable.
----End
Related Information
None
A.3.240 MPLS_TUNNEL_FDI
Description
The MPLS_TUNNEL_FDI alarm indicates a tunnel forward defect. This alarm is reported
when the local NE receives the forward defect indication (FDI) packet, notifying that the
upstream tunnel at the physical layer is faulty.

Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicate the IP address of the node where the fault occurs.
Parameters 5 and 6 Indicate the fault type.

l 0x00: NORMAL
l 0x01: SERVER
l 0x02: PEERME
l 0x03: LOCV
l 0x04: MISMATCH
l 0x05: MISMERGE
l 0x06: EXCESS
l 0x06: UNKNOWN

Possible Causes
Cause 1: The upstream NE detects that the physical link that carries the tunnel is faulty.
Procedure
Step 1 Cause 1: The upstream NE detects that the physical link that carries the tunnel is faulty.
If... Then...
The link-related alarms, such as MW_BER_EXC, MW_BER_SD, Clear these alarms
MW_FEC_UNCOR and MW_LOF, are reported first.
The transmit board of the local NE reports hardware-related Clear these alarms
alarms (alarms on the optical modules or boards), such as first.
HARD_BAD and LSR_NO_FITED
----End
Related Information
None

A.3.241 MPLS_TUNNEL_LOCV
Description
The MPLS_TUNNEL_LOCV is an alarm of tunnel connectivity loss. This alarm occurs when
the port of the local NE fails to receive expected CV/FFD packets within three CV/FFD
periods. (The expected CV/FFD packets must carry correct TTSIs and have the correct type,
period, and value.)
Attribute
Parameters
None

When this alarm occurs, the services that the faulty tunnel carries are interrupted.
Possible Causes
l Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection
packet type and detection packet period, differ at the two ends.
l Cause 2: Severe congestion occurs on the network.
l Cause 4: The physical link between the two ends is faulty.
Procedure
Step 1 Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection packet
type and detection packet period, differ at the two ends.
1. Check whether the MPLS OAM settings are the same at the two ends.
2. If the MPLS OAM settings are different at the two ends, change them to the same.
If... Then...
Step 2 Cause 2: Severe congestion occurs on the network.

1. If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is fully
used. If the bandwidth of the faulty tunnel is exhausted, increase the bandwidth or
eliminate the sources that transmit a large amount of invalid data.

If... Then...

1. Check whether the remote NE reports the COMMUN_FAIL alarm. If yes, you can infer
that the remote NE is being reset. Wait until the COMMUN_FAIL alarm clears.
If... Then...
The alarm persists Go to the next step.
2. Check whether the local NE and the remote NE report alarms related to optical modules
or boards, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms first.
3. Then, check whether the MPLS_TUNNEL_LOCV alarm clears.
If... Then...
Step 4 Cause 4: The physical link between the two ends is faulty.
1. Check whether any fiber or cable is damaged. If yes, replace the damaged fiber or cable.
----End
Related Information
None
A.3.242 MPLS_TUNNEL_LOCK
Description
The MPLS_TUNNEL_LOCK alarm the locked signal function (LCK) is enabled for a tunnel.
Attribute
Parameters
None

The tunnel is locked for diagnostic testing or other administrative purposes.

Possible Causes
Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.
Procedure
Step 1 Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.
1. Check whether the LCK is enabled for the tunnel layer. If yes, disable the CLK after
administrative locking (for diagnostic testing or other administrative purpose) is no
longer needed.
----End
Related Information
None
A.3.243 MPLS_TUNNEL_MISMATCH
Description
The MPLS_TUNNEL_MISMATCH is an alarm indicating that the trail termination source
identifiers (TTSIs) on the tunnel do not match with the specified one. This alarm is reported if
no CV/FFD packets with correct TTSIs are received in three consecutive CV/FFD periods.
Attribute
Parameters
None

When this alarm occurs, services are interrupted or packets from other tunnels are received.
Possible Causes
l Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ
at the two ends of the tunnel.
Procedure
Step 1 Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ at
the two ends of the tunnel.
1. Check whether the tunnel settings are the same at the two ends.

– If the source NE is an ingress node, Sink Node is the LSR ID of the sink NE. If the
sink NE is an egress node, Source Node is the LSR ID of the source NE.
– Tunnel IDs of the source NE and sink NE of a tunnel must be set to the same.
2. If the tunnel IDs are different, change them to the same.

1. Check whether any fiber or cable is misconnected between the two ends. If yes, connect
the fiber or cable properly.
----End
Related Information
None
A.3.244 MPLS_TUNNEL_MISMERGE
Description
The MPLS_TUNNEL_MISMERGE is an alarm indicating that the trail termination source
identifiers (TTSIs) are mismerged in the tunnel. This alarm is reported if the CV/FFD packets
with correct TTSIs and those with wrong TTSIs are received in three consecutive CV/FFD
periods.
Attribute
Parameters
None

When this alarm occurs, the packets from other tunnels are received.
Possible Causes
l Cause 1: Multiple tunnels are configured with the same label.
Procedure
Step 1 Cause 1: Multiple tunnels are configured with the same label.
1. Check whether multiple tunnels are configured with the same label.
2. If multiple tunnels are configured with the same label, delete the redundant labels or
change the label of each tunnel to a unique value.


1. Check whether any fiber or cable is misconnected between the two ends. If yes, connect
the fiber or cable properly.
----End
Related Information
On the NE, the label of each MPLS tunnel is unique.
A.3.245 MPLS_TUNNEL_OAMFAIL
Description
The MPLS_TUNNEL_OAMFAIL is an alarm indicating that the OAM protocol negotiation
between the two ends of the tunnel fails.
Attribute

Parameters
None

When this alarm occurs, services are switched to the backup network and the LPT closes the
access port of the remote NE at the same time.
Possible Causes
l Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one
end and is disabled on the other end.
l Cause 2: The tunnel is unavailable when the OAM function is enabled and the detection
mode is auto-sensing.
Procedure
Step 1 Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one end
and is disabled on the other end.
1. Enable the OAM function.
Step 2 Cause 2: The tunnel is unavailable when the OAM function is enabled and the detection mode
is auto-sensing.
1. Check whether the sink node of the alarmed tunnel reports the HARD_BAD,
ETH_LOS, or R_LOS alarm.

2. If yes, clear the alarm. After the OAM protocol negotiation succeeds, the
MPLS_TUNNEL_OAMFAIL alarm clears.
----End
Related Information
None
A.3.246 MPLS_TUNNEL_RDI
Description
The MPLS_TUNNEL_RDI is an alarm indicating a defect in the backward direction of a
tunnel. The local MEP sends an RDI packet to the remote MEP when detecting a tunnel fault.
The MPLS_TUNNEL_RDI alarm is reported when the remote MEP receives the RDI packet.
Attribute
Parameters
None

When this alarm occurs, services are affected in the transmit direction on the remote MEP.
Possible Causes
The local MEP NE detects a tunnel fault.
Procedure
Step 1 Handle the tunnel fault according to the MPLS-TP OAM-related alarm reported by the remote
MEP. Then, check whether the MPLS_TUNNEL_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the physical link is faulty between faulty NEs. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty optical
fiber or cable.
----End
Related Information
None

A.3.247 MPLS_TUNNEL_SD
Description
The MPLS_TUNNEL_SD is an alarm of signal degrade on the tunnel. This alarm is reported
when the packet loss rate of the CV/FFD crosses the SD threshold but is lower than the SF
threshold.
Attribute
Parameters
None

Services degrade and moderate packet loss occurs.
Possible Causes
l Cause 1: Excessive bit errors occur.
l Cause 2: The bandwidth of the tunnel is fully used.
Procedure
Step 1 Cause 1: Excessive bit errors occur.
1. Clear bit errors.
2. If the alarm persists, proceed to cause 2.
Step 2 Cause 2: The bandwidth of the tunnel is fully used.
1. Check whether the bandwidth allocated to the tunnel is fully used. If the bandwidth of
the faulty tunnel is exhausted, increase the bandwidth or eliminate the sources that
transmit a large amount of invalid data. Check whether the alarm clears.
----End
Related Information
None
A.3.248 MPLS_TUNNEL_SF
Description
The MPLS_TUNNEL_SF is an alarm indicating that the tunnel signal degrades severely. This
alarm is reported if the loss ratio of the CV/FFD packets is higher than the SF threshold and
CV/FFD packets are received in three consecutive periods.

Attribute
Parameters
None

When this alarm occurs, the quality of service degrades severely and a large number of
packets are lost.
Possible Causes
l Cause 1: Excessive bit errors occur.
l Cause 2: The bandwidth of the tunnel is fully used.
Procedure
Step 1 Cause 1: Excessive bit errors occur.
1. Clear bit errors.
2. If the MPLS_TUNNEL_SF persists, go to Cause 2.
Step 2 Cause 2: The bandwidth of the tunnel is fully used.
1. On the NMS, check whether the bandwidth of the tunnel is fully used. If the bandwidth
of the tunnel is fully used, increase the bandwidth allocated to the tunnel or eliminate any
source that transmits a large amount of invalid data. Check whether the alarm is cleared.
----End
Related Information
None
A.3.249 MPLS_TUNNEL_UNEXPMEG
Description
The MPLS_TUNNEL_UNEXPMEG is an alarm indicating an error in the tunnel OAM CCM
information. This alarm is reported when the sink NE receives a CCM packet with an
unexpected MEG ID.
Attribute

Parameters
None

When this alarm occurs, the sink NE receives CCM packets of other tunnels.
Possible Causes
l Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel.
l Cause 2: There are multiple tunnels with the same label between the source and sink
NEs.
Procedure
Step 1 Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel.
1. Check whether PW configurations are consistent between the source and sink NEs. MEG
IDs must be set to the same value on NEs at both ends of a tunnel. For details, see
Querying MPLS Tunnel Information.
Step 2 Cause 2: There are multiple tunnels with the same label between the source and sink NEs.
1. Check whether there are multiple tunnels with the same label on the source and sink
NEs. If yes, reconfigure labels for tunnels. For details, see Querying MPLS Tunnel
Information.
----End
Related Information
None
A.3.250 MPLS_TUNNEL_UNEXPMEP
Description
The MPLS_TUNNEL_UNEXPMEP is an alarm indicating an error in the tunnel OAM CCM
information. This alarm is reported when the sink NE receives a CCM packet with an
unexpected MEP ID.
Attribute
Parameters
None


other tunnels.
Possible Causes
MEP IDs are inconsistent between NEs at both ends of the tunnel.
Procedure
Step 1 MEP IDs are inconsistent between NEs at both ends of the tunnel.
1. Check whether the remote MEP ID on the source NE is correctly configured with the
MEP ID of the sink NE. If not, reconfigure the remote MEP ID on the source NE.
----End
Related Information
None
A.3.251 MPLS_TUNNEL_UNEXPPER
Description
The MPLS_TUNNEL_UNEXPPER is an alarm indicating that the tunnel does not receive the
CCM packet in the expected period. This alarm is reported when the sink NE of the PW
receives a CCM packet with correct MEG level, MEG ID, and MEP ID but in an unexpected
period.
For example, the transmit interval is set to 10 ms on the source and sink NEs, but the sink NE
receives the CCM packet from the source NE after 20 ms.
Attribute
Parameters
None

other tunnels.
Possible Causes
CCM packet periods are inconsistent between the source and sink NEs at both ends of the
tunnel.

Procedure
Step 1 CCM packet periods are inconsistent between the source and sink NEs at both ends of the
tunnel.
1. Check whether tunnel configurations are consistent between the source and sink NEs.
CCM packet periods on NEs at both ends of a PW must be set to the same value. For
details, see Querying MPLS Tunnel Information.
----End
Related Information
None
A.3.252 MPLS_TUNNEL_UNKNOWN
Description
The MPLS_TUNNEL_UNKNOWN is an alarm indicating that certain unknown defects exist
on the tunnel. This alarm is reported when the port receives the CV packets and the FFD
packets.
Attribute
Parameters
None

When this alarm occurs, the OAM function is affected.
Possible Causes
l Cause 1: The OAM settings differ at the two ends.
l Cause 2: The NE receives packets from an unknown source.
Procedure
Step 1 Cause 1: The OAM settings differ at the two ends.
1. If the MPLS_TUNNEL_UNKNOWN alarm is reported transiently, check whether
Tunnel OAM configuration is changed on the local NE and the opposite NE.
2. If the local NE and the opposite NE have different Tunnel OAM configuration, the
MPLS_TUNNEL_UNKNOWN alarm is reported transiently and then the
MPLS_TUNNEL_LOCV alarm is reported. Ensure that both ends have the same Tunnel
OAM configuration. Then, check whether the alarm is cleared.

Step 2 Cause 2: The NE receives packets from an unknown source.

1. Check whether there is any service configured between the NE and an unknown source,
or whether the NE is connected to an unknown source.
2. If yes, modify the incorrect configuration or reconnect the fibers.
----End
Related Information
None
A.3.253 MS_AIS
Description
The MS_AIS is an alarm indicating multiplex section alarms. This alarm is reported when the
board detects that bits 6-8 of the K2 byte in the three consecutive frames are 111.
Attribute

Parameters
None

The services on the line port are interrupted. If the services are configured with protection,
Possible Causes
l Cause 1: The transmit unit of the opposite station is faulty.
l Cause 2: The receive unit of the local site is faulty.
Procedure
Step 1 Cause 1: The transmit unit of the opposite station is faulty.
1. Replace the line board at the opposite site based on the type of the alarmed board.
If... Then...
The line board reports the alarm Replace the line board at the opposite end.
The IF board reports the alarm Replace the IF board at the opposite end.
2. Replace the board and then check whether the alarm is cleared.

If... Then...
The alarm is cleared after replacement End the fault handling.
If... Then...
The alarm is cleared after the board replacement End the fault handling.
The alarm persists after the board replacement Go to Cause 2.
Step 2 Cause 2: The receive unit of the local site is faulty.

----End
Related Information
None
A.3.254 MS_CROSSTR
Description
The MS_CROSSTR is an alarm indicating that a performance indicator of the multiplex
section crosses the threshold. This alarm is reported when the board detects that the MS BER
performance indicator crosses the preset threshold.
Attribute
Minor Service alarm
Parameters
Name Meaning
l 0x01: 15 minutes
l 0x02: 24 hours

Name Meaning
Parameter 2, Parameter 2 is always 0x00. Parameter 3 indicate the ID of a
Parameter 3 performance event that causes the alarm and has the following
meanings:
l 0x10: MSBBE
l 0x11: MSES
l 0x12: MSSES
l 0x13: MSFEBBE
l 0x14: MSFEES
l 0x15: MSFESES
l 0x16: MSUAS
l 0x21: MSFEUAS

A large number of bit errors occur in the services, and the services may be interrupted.
Possible Causes
l Cause 1: Services are interrupted for a long time.
l Cause 2: The MS BER performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
NOTE
Handle the alarm as follows if the value of parameter 3 is 0x16:
1. Check whether fibers are properly connected. If not, connect the fibers again according
to planning information.
2. Check whether cross-connections are configured for service ports. If not, configure
cross-connections again according to planning information.
Step 2 Cause 2: The MS BER performance indicator crosses the preset threshold.
1. Check the threshold crossing records of MS BER performance events to find out the
performance event that crosses the preset threshold. For details, see 4.3.5 Browsing the
2. Handle the performance event that crosses the threshold.
----End
Related Information
None

A.3.255 MS_RDI
Description
The MS_RDI is an alarm indicating that data reception at the remote end of the multiplex
section fails. This alarm is reported when the board detects that bits 6-8 of the K2 byte are
110.
Attribute

Parameters
None

The services on the local site are not affected. The services received by the opposite station,
however, are interrupted.
Possible Causes
Cause 1: The local site receives a message from the opposite station, and the message
indicates that data reception at the remote end of the multiplex section fails.
Procedure
Step 1 Cause 1: The local site receives a message from the opposite station, and the message
indicates that data reception at the remote end of the multiplex section fails.
1. Rectify the fault that occurs on the opposite station.
The possible alarms are as follows:
– MS_AIS
– R_LOS
– R_LOF
– B2_EXC
– B2_SD
----End
Related Information
None

A.3.256 MS_REI
Description
The MS_REI is an alarm indicating that bit errors occur on the remote end of the multiplex
section. This alarm is reported when the board detects that the M1 byte is non-zero.
Attribute

Parameters
None

The services on the local site are not affected. The services received by the opposite station,
however, has bit errors.
Possible Causes
Cause 1: The local site receives a message from the opposite station, and the message
indicates that bit errors occur on the remote end of the multiplex section.
Procedure
Step 1 Cause 1: The local site receives a message from the opposite station, and the message
indicates that bit errors occur on the remote end of the multiplex section.
1. Handle the MS_BBE performance event on the port of the opposite station.
----End
Related Information
None
A.3.257 MSAD_CROSSTR
Description
The MSAD_CROSSTR is an alarm indicating that the adaptation performance indicator of
the multiplex section crosses the threshold. This alarm is reported when the board detects that
an AU pointer adaptation performance indicator crosses the preset threshold.

Attribute

Minor Service alarm
Parameters
Name Meaning
l 0x01: 15 minutes
l 0x02: 24 hours
l 0x2a: AUPJCHIGH
l 0x2b: AUPJCLOW
l 0x2c: AUPJCNEW

Bit errors may occur in the services.
Possible Causes
Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.
1. Check the threshold crossing records of the AU pointer adaptation performance events to
find out the performance event that crosses the preset threshold. For details, see 4.3.5
Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None

A.3.258 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that the ring network contains several
RPL_OWNER nodes.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the ERPS instance.

The ERPS protection fails and the services configured on the Ethernet ring are interrupted.
Possible Causes
Cause 1: The related data is configured incorrectly.
Procedure
Step 1 Cause 1: The related data is configured incorrectly.
1. Reconfigure the ERPS protection. For details, see Creating Ethernet Ring Protection
Instances.
----End
Related Information
The following table describes the meanings of the parameters in the MULTI_RPL_OWNER
alarm reported by the EMS6.
Name Meaning
Parameter 1 to Parameter 4 Indicates the port ID.
Parameter 5, Parameter 6 Indicate the ID of the ERPS instance.

A.3.259 MW_AM_TEST
Description
The MW_AM_TEST is an alarm indicating that the IF port is in the AM testing state.
Attribute
Minor Other alarms
Parameters
None

The transmission capacity is reduced during the AM test, and services with low priorities may
be interrupted.
Possible Causes
l Cause: The AM testing is enabled.
Procedure
Step 1 Cause: The AM testing is enabled.
1. After the AM testing ends, disable the AM testing.
----End
Related Information
None
A.3.260 MW_BER_EXC
Description
The MW_BER_EXC is an alarm indicating that excessive bit errors occur on the radio link.
This alarm is reported when the bit errors on the radio link exceed the specified threshold
(10-3 by default).
Attribute
Minor Service alarm

Parameters
None

When the MW_BER_EXC alarm occurs, the service on the port is interrupted.
Possible Causes
l Cause 1: Signal attenuation on the radio link is very heavy.
l Cause 4: An interference event occurs.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is very heavy.
1. At the local end, check whether the receive power of the ODU is normal. If yes,
determine the abnormality and take proper measures. For details, see 4.4.1 Querying the
Historical Transmit Power and Receive Power
If... Then...
The RSL is lower than Follow the steps:

the receiver sensitivity
1. Check the installation of the antenna to ensure that the
azimuth of the antenna meets the requirement.
2. Check the antenna direction. Check whether the received
signal is from the main lobe.
If the antenna direction does not meet the requirement,
adjust the antenna in a wide range.
3. Check whether the setting of the polarization direction of
the antenna is correct. Adjust the incorrect polarization
direction.
4. Check whether the antenna gain at both the transmit and
receive ends meets the specifications. Replace the antennas
that do not meet the requirement.
5. Check whether any mountain or building obstacle exists in
the transmit direction.
If yes, contact the network planning department for proper
modification of the planning design, hence preventing the
block of the mountain or building obstacle.

If... Then...
The RSL is higher than Slow up fading occurs. Follow the steps:
the specified RSL of the
network. The offset value 1. Follow instructions in 8.1.2 Scanning Interfering Signals to
is tens of decibels. The scan the frequency spectrum around the radio link and check
duration is from tens of for co-frequency interference and bias-frequency
seconds to several hours. interference.
2. Use a spectrum analyzer to analyze the interference source.
3. Contact the spectrum management department to clear the
interference spectrum or change plans to minimize the
interference.
The RSL is lower than Slow down fading occurs. Generally, the radio link may be
the specified RSL of the faulty in both directions, because slow fading is imposed by the
network. The offset value transmission path. Contact the network planning department to
is tens of decibels. The make the following changes:
duration is from tens of
seconds to several hours. l Increase the installation height of the antenna.
l Reduce the transmission distance.
l Increase the antenna gain.
l Increase the transmit power.
If the RSL is lower than Fast fading occurs. Contact the network planning department to
or higher than the make the following changes:
specified RSL of the
network and if the l Adjust the position of the antenna to block the reflected
duration is from several wave or make the reflection point fall on the ground that has
milliseconds to tens of a small reflection coefficient, therefore reducing the
seconds. multipath fading.
l Adjust the RF configuration to make the links in the 1+1 SD
configuration.
l If the links are configured with the 1+1 SD protection,
adjust the height offset between two antennas to make the
receive power of one antenna stronger than the receive
power of the other antenna.
l Increase the fading margin.
Locate the fault by looping back the opposite station and excluding the position one by one.
Follow the steps:
1. Perform an inloop on the IF port at the opposite end. For details, see 8.4.7 Setting
Loopback for the IF Board. Check whether the fault at the opposite end is rectified
after the loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IF board.
The fault at the opposite end is rectified Go to the next step.

2. Check whether the cable connector is prepared according to the requirement. If any cable
connector does not meet the requirement, make a new connector.
3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the opposite
end.
The fault at the opposite end is rectified End the alarm handling.
Follow the steps:
1. Perform an inloop on the IF port at the local end. For details, see 8.4.7 Setting
Loopback for the IF Board. Check whether the fault at the local end is rectified after
the loopback.
If... Then...
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the local end.
Step 4 Cause 4: An interference event occurs.

1. Follow instructions in 8.1.2 Scanning Interfering Signals to scan the frequency
spectrum around the radio link and check for co-frequency interference and bias-
frequency interference.
3. Contact the spectrum management department to clear the interference spectrum or
change plans to minimize the interference.
----End
Related Information
None

A.3.261 MW_BER_SD
Description
The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarm
is reported when the bit errors on the radio link exceed the specified threshold (10-6 by
default) but does not reach the MW_BER_EXC alarm threshold (10-3 by default).
Attribute
Minor Service alarm
Parameters
None

The service performance on the port deteriorates. If the equipment is configured with 1+1
FD/SD protection, switching on the channel side may be triggered.
Possible Causes
Procedure
Historical Transmit Power and Receive Power

If... Then...

direction.
network. The offset value 1. Follow instructions in 8.1.2 Scanning Interfering Signals
is tens of decibels. The to scan the frequency spectrum around the radio link and
duration is from tens of check for co-frequency interference and bias-frequency
seconds to several hours. interference.
interference.

If... Then...
configuration.
Follow the steps:
after the loopback.
If... Then...
If... Then...
end.
Follow the steps:
the loopback.

If... Then...
If... Then...

1. Check whether any co-channel interference occurs.
a. Mute the ODU at the opposite end.
b. Check the RSL at the local end. For details, see Configuring a Single-Hop Radio
Link. If the RSL exceeds -90 dBm, it indicates that there is co-channel interference
that may affect the long-term availability and errored-second performance of the
system.
2. Follow instructions in 8.1.2 Scanning Interfering Signals to scan the frequency
spectrum around the radio link and check for co-frequency interference and bias-
frequency interference.
----End
Related Information
None
A.3.262 MW_CFG_MISMATCH
Description
The MW_CFG_MISMATCH is an alarm of configuration mismatch on radio links. This
alarm occurs when an NE detects configuration mismatch on both ends of a radio link. For
example, the number of E1 signals, the number of STM-1 signals, AM enabling, 1588
overhead enabling, modulation mode may be configured differently on both ends of a radio
link.

Attribute
Parameters
Name Meaning
Parameter Indicates the cause of the fault.
1
l 0x01: The number of E1 signals or the E1 timeslot priority at the local end
of a radio link is different from that at the other end.
l 0x02: The AM enabling is different.
l 0x03: The 1588 overhead enabling is different.
l 0x04: The modulation mode is different.
l 0x05: The service mode is different.
l 0x06: The number of STM-1 signals is different.
l 0x09: The IP header compression enabling is different.
l 0x0A: AES configurations at two ends of a link are inconsistent.
l 0x10: The IF board or its working mode does not match the type of the RF
unit.
l 0x12: Configurations of enhanced compression at both ends of a link are
inconsistent.

Name Meaning
Parameter When the value of Parameter 1 is 0x09:
2
l 0x01: The air interface compression at L2 is different.
l 0x02: The air interface compression at L3 is different.
When the value of Parameter 1 is 0x0A:
l 0x01: AES is enabled only at one end of a link.
l 0x02: AES message authentication codes (MACs) are inconsistent at both
ends of a link.
When the value of Parameter 1 is 0x12:
l 0x01: The enabling/disabling statuses of enhanced compression for CS7
queues are inconsistent at both ends of a link.
l 0x02: The enabling/disabling statuses of enhanced compression for CS6
l 0x03: The enabling/disabling statuses of enhanced compression for EF
l 0x04: The enabling/disabling statuses of enhanced compression for AF4
l 0x08: The enabling/disabling statuses of enhanced compression for BE
When Parameter 1 takes another value, Parameter 2 is reserved.

When this alarm occurs, the service configuration cannot take effect or services are
interrupted. After the NE is power cycled or reset, this alarm may still affect services.
NOTE
If the value of Parameter 1 is 0x01, 0x03, 0x12, 0x0A, or 0x09, the number of E1 signals configured
over a radio link, 1588 overhead enabling status, enhanced compression configuration, and IP header
compression may not take effect.
Possible Causes
l Cause 1: The number of E1 signals or the E1 timeslot priority at the local end of a radio
link is different from that at the other end.
l Cause 2: The AM enabling is different on both ends of a radio link.
l Cause 3: The 1588 overhead enabling is different on both ends of a radio link.

l Cause 4: The modulation mode is different on both ends of a radio link.

l Cause 5: The service mode is different on both ends of a radio link.
l Cause 6: The number of STM-1 signals is different on both ends of a radio link.
l Cause 7: The IP header compression is different on both ends of a radio link.
l Cause 8: The AES configuration is different on both ends of a radio link.
l Cause 9: The IF board or its working mode does not match the type of the RF unit.
l Cause 10: The enhanced compression status (enabled or disabled) is different at the two
ends of a radio link.
Procedure
Step 1 Determine the possible cause of the alarm according to the alarm parameters.
Step 2 Check the configuration on both ends of the radio link. Ensure that the configuration is the
same on both ends of the radio link. For details, see Managing Radio Links.
----End
Related Information
None
A.3.263 MW_CONT_WAVE
Description
The MW_CONT_WAVE is an alarm of continuous wave. This alarm occurs if the continuous
wave is output by the IF board.
Attribute
Parameters
None

If the continuous wave function is enabled, radio links cannot transmit services.
Possible Causes
l Cause 1: The continuous wave function is enabled.
l Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on
the IF port or composite port.
l Cause 3: The IF unit is faulty.

Procedure
Step 1 Cause 1: The continuous wave function is enabled.
1. Disable the continuous wave function. For details, see Setting IF Attributes.
Step 2 Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on the IF
port or composite port.
1. Release the loopback by referring to 8.4.7 Setting Loopback for the IF Board.
2. Clear the MW_LOF alarm.
Step 3 Cause 3: The IF unit is faulty.
1. 6.8 Replacing an IF Board.
----End
Related Information
The continuous wave function tests the frequency stability and frequency consistency and
should be disabled after a test is completed.
A.3.264 MW_E1_LOST
Description
The MW_E1_LOST is an alarm indicating that E1 services are lost. When the AM
modulation scheme is downshifted, this alarm is reported by the discarded E1 services.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the timeslots of E1 services.

Some E1 services are lost.
Possible Causes
Cause 1: The AM downshifts the modulation scheme.

Procedure
Step 1 Cause 1: The AM downshifts the modulation scheme.
1. Handle the alarm according to AM_DOWNSHIFT.
----End
Related Information
None
A.3.265 MW_FEC_UNCOR
Description
The MW_FEC_UNCOR is an alarm indicating that radio frames forward error correction
(FEC) encoding cannot be corrected.
Attribute

Parameters
None

Bit errors occur in the services. If the equipment is configured with 1+1 FD/SD protection,
HSM channel protection switching may be triggered.
Possible Causes
Procedure
Historical Transmit Power and Receive Power.

If... Then...

direction.
network. The offset value 1. Check whether intra-frequency or inter-frequency
is tens of decibels. The interference exists by scanning frequency spectra in
duration is from tens of microwave channels. For details, see 8.1.2 Scanning
seconds to several hours. Interfering Signals.
interference.

If... Then...
configuration.
Follow the steps:
after the loopback.
If... Then...
If... Then...
end.
Follow the steps:
the loopback.

If... Then...
3. Check whether the IF cable connector is prepared according to the requirement. If any
cable connector does not meet the requirement, make a new connector.
If... Then...

1. Check for co-channel interference. For details, see 8.1.2 Scanning Interfering Signals.
----End
Related Information
None
A.3.266 MW_LIM
Description
The MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. This
alarm is reported if an IF board detects that the link ID in the radio frame overheads is
inconsistent with the specified link ID.
Attribute
Parameters
None

After the IDU IF board reports the MW_LIM alarm, the IF board inserts the AIS alarm into
the received signal. Then, the services on the radio link are interrupted. If the services are
configured with SNCP, protection switching may be triggered.

Possible Causes
l Cause 1: The link ID of the local site does not match with the link ID of the opposite
station.
l Cause 2: The services on other radio links are received due to the incorrect configuration
of the radio link receive frequency at the local or opposite station.
l Cause 3: The antenna receives the radio signals from the other stations, because the
direction of the antenna is set incorrectly.
l Cause 4: The polarization direction of the XPIC is incorrect.
Procedure
Step 1 Cause 1: The link ID of the local site does not match with the link ID of the opposite station.
1. Check whether the link ID of the local site matches with the link ID of the opposite
station. For details, see Configuring a Single-Hop Radio Link. If not, set the link IDs of
the two stations to the same value according to the requirements of the networking
planning.
Step 2 Cause 2: The services on other radio links are received due to the incorrect configuration of
the radio link receive frequency at the local or opposite station.
1. Check whether the receive and transmit frequencies of the local site are consistent with
the receive and transmit frequencies of the opposite station. For details, see Configuring
a Single-Hop Radio Link. If not, set the receive and transmit frequencies of the two
stations again.
Step 3 Cause 3: The antenna receives radio signals from the other stations, because the direction of
the antenna is set incorrectly.
1. Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.
Step 4 Cause 4: The polarization direction of the XPIC is incorrect.
1. If XPIC protection groups are configured, check whether the XPIC configuration is
correct. For details, see Configuring a Single-Hop Radio Link.
a. Check whether the settings of XPIC IF board in polarization direction-V and
polarization direction-H meet the requirement of the planning.
If... Then...
The polarization direction does not Delete the working XPIC group that is
meet the requirement of the planning configured incorrectly and create the
other working XPIC group again.
The polarization direction meets the Go to the next step.

requirement of the planning
b. Check whether Link ID-V and Link ID-H meet the requirement of the planning.
If... Then...
The link ID does not meet the Reset the ID of the radio link of the
requirement of the planning XPIC IF board according to the
planning. For details, see Creating an
XPIC Working Group.

If... Then...
The link ID meets the requirement of Go to the next step.

the planning
2. Check and modify the mapping relationship among the XPIC IF board, ODU, OMT, and
antenna feed. Ensure that the XPIC IF board in the polarization direction V of the two
ends are interconnected with each other through the radio link in the polarization
direction V, and the XPIC IF board in the polarization direction H of the two ends are
interconnected with each other through the radio link in the polarization direction H.
----End
Related Information
The MW_LIM alarm is generated due to the inconsistency between the specified link ID and
the received link ID. When the MW_LOF alarm is generated on the link, the received link ID
is a random value. In this case, the link ID is invalid. The MW_LIM alarm is also suppressed
by the MW_LOF alarm.
A.3.267 MW_LOF
Description
The MW_LOF is an alarm indicating that the radio frame is lost.
Attribute
Parameters
None

The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
l Cause 1: The other alarms are generated.
l Cause 2: In the case of TDM radio services, the IF working modes at the local site and
the opposite station are different. In the case of services, the channel bandwidth and
modulation modes at the local site and the opposite station are different.
l Cause 3: The operating frequency of the ODU at the local site is inconsistent with the
operating frequency of the ODU at the opposite station.


l Cause 6: The receive power of the ODU is abnormal.
Procedure
Step 1 Cause 1: The other alarms are generated.
1. Check whether any alarms are generated in the equipment of the local site. If yes, take
priority to clear them.
The relevant alarms are as follows:
– HARD_BAD
– VOLT_LOS
– IF_CABLE_OPEN
– BD_STATUS
– RADIO_RSL_LOW
– CONFIG_NOSUPPORT
– TEMP_ALARM
Step 2 Cause 2: In the case of TDM radio services, the IF working modes at the local site and the
opposite station are different. In the case of services, the channel bandwidth and modulation
modes at the local site and the opposite station are different.
1. In the case of TDM radio services, check whether the working mode of the IF board at
the local site is consistent with the working mode of the IF board at the opposite station.
For details, see Configuring a Single-Hop Radio Link. If not, reset the working mode of
the IF board according to the network planning.
In the case of Hybrid radio services, check whether the channel bandwidth and
modulation modes are the same at both ends. If not, change the channel bandwidth and
modulation modes according to the network planning. For details, see Configuring a
Single-Hop Radio Link.
Step 3 Cause 3: The operating frequency of the ODU at the local site is inconsistent with the
operating frequency of the ODU at the opposite station.
1. Ensure that the type of the ODU at the local site is consistent with the type of the ODU
at the opposite station.
2. Reset the operating frequency of the ODU according to the network planning. For
details, see Setting ODU Transmit Frequency Attributes.
Set the transmit frequency of the local site to the same as the receive frequency of the
opposite station. Then, set the receive frequency of the local site to the same as the
transmit frequency of the opposite station.
1. Check whether any alarms are generated in the equipment of the local site. If yes, take
priority to clear them.
– HARD_BAD
– BD_STATUS
– VOLT_LOS

– IF_CABLE_OPEN
– RADIO_MUTE
– RADIO_TSL_HIGH
– RADIO_TSL_LOW
– TEMP_ALARM
2. Locate the fault by looping back the opposite station.
Follow the steps:
a. Perform an inloop on the IF port at the opposite end. For details, see 8.4.7 Setting
Loopback for the IF Board and . Check whether the fault at the opposite end is
rectified after the loopback.
If... Then...
b. Check whether the cable connector is prepared according to the requirement. If any
c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does
not meet the requirement.
d. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not Replace the ODU at the opposite
rectified end.

1. Locate the fault by looping back the opposite station.
Follow the steps:
a. Perform an inloop on the IF port at the local end. For details, see 8.4.7 Setting
Loopback for the IF Board and . Check whether the fault at the local end is
rectified after the loopback.
If... Then...
b. Check whether the cable connector is prepared according to the requirement. If any
c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does
not meet the requirement.
d. Check whether the fault at the local end is rectified.
Step 6 Cause 6: The receive power of the ODU is abnormal.

1. At the local site, check whether the receive power of the ODU is abnormal. For details,
see Browse historical performance events. If yes, determine the abnormality and take
proper measures.
If... Then...

direction.
network. The offset value 1. Check for co-channel interference. For details, see 8.1.2
is tens of decibels. The Scanning Interfering Signals.
duration is from tens of 2. Use a spectrum analyzer to analyze the interference source.
seconds to several hours. 3. Contact the spectrum management department to clear the
interference.

If... Then...
duration is from several wave or make the reflection point fall on the ground that
milliseconds to tens of has a small reflection coefficient, therefore reducing the
l Adjust the RF configuration to make the links in the 1+1
SD configuration.

Follow the steps:
1. Check for co-channel interference. For details, see 8.1.2 Scanning Interfering Signals.
----End
Related Information
NOTE
If the MW_LOF alarm is reported frequently, check whether Anti-jitter Time(s) is set to 0. You can
modify the configuration by following instructions in Modifying the Parameters of IF 1+1 Protection.
A.3.268 MW_RDI
Description
The MW_RDI is an alarm indicating that there are defects at the remote end of the radio link.
This alarm is reported when the IF board detects an RDI in the radio frame overheads. If RTN
905s are cascaded at the remote end of a PLA link and the slave RTN 905 detects a fault in
the cascading line, the NE connected to the slave RTN 905 reports the alarm.
Attribute
Parameters
None


If the local site is configured with the reverse switching function, the 1+1 switching is
triggered on the IF board when the working and protection IF boards receive the MW_RDI
alarm at the same time. This alarm also indicates that the services received by the opposite
station are interrupted.
If PLA is configured, a PLA switchover occurs when the microwave link receives an
MW_RDI alarm.
Possible Causes
Cause 1: After detecting a service alarm that is caused by the fault in a radio link, the receive
station returns a radio link fault indication to the transmit station.
Cause 2: RTN 905s are cascaded at the remote end of a PLA link and the slave RTN 905
detects a fault in the cascading line.
Procedure
Step 1 Clear the radio alarms that occur at the opposite station. The possible alarms are as follows:
l MW_LOF
l R_LOF
l R_LOC
l MW_FEC_UNCOR
l XPIC_LOS
l MW_BER_SD
l MW_BER_EXC
l If RTN 905s are cascaded at the remote end to implement the PLA function, the remote
NE may report an NB_UNREACHABLE alarm.
----End
Related Information
None
A.3.269 NEIP_CONFUSION
Description
The NEIP_CONFUSION alarm indicates an NE IP address conflict. (Several NEs use the
same IP address.)
Attribute

Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the IP address used by several NEs.

The NEs using the same IP address may be unreachable to the NMS or cannot be stably
managed.
Possible Causes
The possible cause of the NEIP_CONFUSION alarm is as follows:
l Cause 1: Several NEs use the same IP address.
l Cause 2: DCN is enabled on both ports of the NE that reports the alarm, and the two
ports are directly connected through a fiber or network cable.
Procedure
Step 1 Cause 1: Several NEs use the same IP address.
1. Change the IP address of the NE according to the network plan. For details, see
Changing the NE IP Address . Then check whether the alarm is cleared. If the alarm
persists, go to Step 2.
Step 2 Cause 2: DCN is enabled on both ports of the NE that reports the alarm, and the two ports are
directly connected through a fiber or network cable.
1. Determine whether the user wants to disconnect the fiber or network cable.
2. Determine the DCN type according to the network plan, and perform operations
accordingly.
Step 3 Contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
A.3.270 NESF_LOST
Description
The NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported
when the system control, cross-connect, and timing board detects that the NE software is lost.

Attribute
Parameters
Name Meaning
Parameter 2,
Indicate the ID of the routine inspection object.
Parameter 3
Parameter 4 Indicates the specific alarm cause when a different bit is 1.
l 0x01: If the first bit is 1, it indicates that the file does not exist.
l 0x02: If the second bit is 1, it indicates that verification of the file
fails.

If the NE software does not exist in the active and standby areas, an NE cannot be restarted
after it is powered off or reset.
Possible Causes
l Cause 1: No new NE software is loaded after the existing NE software is erased.
l Cause 2: Loading the NE software is unsuccessful.
Procedure
Step 1 Cause 1: No new NE software is loaded after the existing NE software is erased.
Cause 2: Loading the NE software is unsuccessful.
1. Check whether the alarm is caused by the loading operation.
If... Then...
The alarm is caused by the loading Contact the Huawei technical support
operation engineers to reload the software.
The alarm is not caused by the loading Go to the next step.
operation


1. For details, see 6.10 Replacing the System Control, Switching and Timing Board.
----End
Related Information
None
A.3.271 NESOFT_MM
Description
The NESOFT_MM alarm indicates that the software versions in the ofs1 and ofs2 areas are
inconsistent or the time for which the system waits after the software package is loaded
exceeds 24 hours.
l This alarm occurs when the first software system in the system control, switching, and
timing board is inconsistent with the second software system.
l This alarms occurs when the time for which the system waits after the software package
is loaded exceeds 24 hours.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the location of the file.
l 0x01: the files in the flash memory
l 0x02: the software that is currently running
l 0x03: the software in the CF card
Parameter 2, Indicate the IDs of the inconsistent files in the flash memory of the system
Parameter 3 control board if the value of Parameter 1 is 0x01,
Indicate the IDs of the inconsistent files in the currently running software if
the value of Parameter 1 is 0x02.
Parameter 4 Indicate the cause of the alarm.

l 0x04: The file versions in the master and slave areas of a single system
control board are inconsistent.
l 0x08: The file versions in the active and standby system control boards
are inconsistent.
l 0x0c: The file versions in the master and slave areas of a single system
control board are inconsistent and the file versions on the active and
standby system control boards are also inconsistent.


This alarm affects active/standby switching of system control boards if the active and standby
system control boards have different NE software versions.
If no NE software exists in the flash memory, the system is unable to restart after power-off or
reset.
Possible Causes
l Cause 1: The software running on the active and standby SCC boards has different
versions.
l Cause 2: The software stored in the ofs1 and ofs2 areas of the active SCC board has
different versions.
l Cause 3: The software stored in the mapping directories of active and standby SCC
boards has different versions.
l Cause 4: The time for which the system waits after the software package is loaded
exceeds 24 hours.
Procedure
Step 1 Cause 1: The software running on the active and standby SCC boards has different versions.
1. Upgrade the software on the active and standby SCC boards to the same latest version.
Step 2 Cause 2: The software stored in the ofs1 and ofs2 areas of the active SCC board has different
versions.
1. Upgrade the software in the ofs1 and ofs2 areas of the active SCC board to the same
latest version.
Step 3 Cause 3: The software stored in the mapping directories of active and standby SCC boards
has different versions.
1. The procedure is the same as Step 1.
Step 4 Cause 4: The time for which the system waits after the software package is loaded exceeds 24
hours.
1. Upgrade the software package, and then perform the activate and submit operations.
2. If the activate and submit operations are completed, the NESOFT_MM alarm is cleared
automatically. If the activate or submit operation fails, perform the rollback operation.
3. Reload the software.
Step 5 Check whether the NESOFT_MM alarm is cleared. If the alarm persists, contact Huawei
technical support engineers.
----End
Related Information
None

A.3.272 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the board software is lost.
Attribute
Parameters
Name Meaning
Parameter 2, Parameter 3 Indicates the number of the lost file.

l If the board software is lost, the board fails to work normally.
l If the FPGA is lost, the FPGA does not have a backup copy.
Possible Causes
Cause 1: The software fails to be loaded.
Procedure
Step 1 Cause 1: The software fails to be loaded.
1. Contact the Huawei technical support engineers to reload the software.
----End
Related Information
None
A.3.273 NP1_MANUAL_STOP
Description
The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is
disabled manually.

Attribute
Parameters
Name Meaning
Parameter 1, Parameter Indicates the ID of the alarmed protection group. For example,
2 0x01 indicates that the alarm is reported by protection group 1.

The N+1 protection may fail, or the protection switching may fail.
Possible Causes
Cause 1: The N+1 protection protocol is disabled manually.
Procedure
Step 1 Cause 1: The N+1 protection protocol is disabled manually.
1. Start the N+1 protection protocol.
----End
Related Information
None
A.3.274 NP1_SW_FAIL
Description
The NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.
Attribute
Parameters


Name Meaning
Parameter 1, Parameter Indicates the ID of the alarmed protection group. For example,

The services cannot be switched. If the current paths are unavailable, the services are
interrupted.
Possible Causes
l Cause 1: The parameters of the N+1 protection for the alarmed node are set incorrectly.
l Cause 2: The network-wide N+1 protection protocol runs abnormally.
Procedure
Step 1 Cause 1: The parameters of the N+1 protection for the alarmed node are set incorrectly.
1. Check whether the parameters of the N+1 protection are set correctly according to the
planning. For details, see Creating an N+1 Protection Group.
If... Then...
The parameters of the N+1 protection are set Set the parameters of the N+1
incorrectly protection correctly.
The parameters of the N+1 protection are set Go to Cause 2.
correctly
Step 2 Cause 2: The network-wide N+1 protection protocol runs abnormally.

1. Stop and restart the protocol manually. For details, see Starting/Stopping the N+1
Protection Protocol.
If... Then...
The alarm is cleared after the protocol is End the alarm handling.
restarted.
The alarm persists after the protocol is Contact the Huawei technical support
restarted engineers to handle the alarm.
----End
Related Information
None
A.3.275 NP1_SW_INDI
Description
The NP1_SW_INDI is an alarm indicating that the N+1 protection switching is detected.

Attribute
Parameters
Name Meaning
Parameter1, Parameter Indicates the ID of the alarmed protection group. For example,

During the N+1 protection switching, the services are interrupted. After the N+1 switching is
complete, the services are restored to normal. After the switching starts and before the
switching is complete, the extra services are interrupted.
Possible Causes
Cause 1: The N+1 protection switching is performed.
Procedure
Step 1 Cause 1: The N+1 protection switching is performed.
1. Find out the cause of switching, and take appropriate measures.
----End
Related Information
None
A.3.276 NTP_SYNC_FAIL
Description
The NTP_SYNC_FAIL is an alarm indicating that NTP time synchronization fails.
Attribute

Parameters
None

Time on the alarmed NE is different from time on the NTP server. The records on the NE,
such as performance events, alarms, and operations, cannot be kept with exact time.
Possible Causes
l Cause 1: The NTP server is not configured or is configured incorrectly.
l Cause 2: The NTP server cannot communicate with the NE.
l Cause 3: The NTP server fails.
Procedure
Step 1 Cause 1: The NTP server is not configured or is configured incorrectly.
1. Configure the NTP server correctly.
2. Re-configure the NTP parameters for the NE.
Step 2 Cause 2: The NTP server cannot communicate with the NE.
1. Check whether the cable connecting the gateway NE to the NTP server is normal. If not,
rectify the connection fault.
2. Check whether the DCN communication between the NTP server and the NE is normal.
If not, configure the DCN communication correctly.
Step 3 Cause 3: The NTP server fails.

1. Troubleshoot the NTP server.
----End
Related Information
None
A.3.277 OCD
Description
The OCD is an alarm indicating out-of-cell delimitation. This alarm occurs when the cell
delimitation state machine is in the HUNT or PRESYN state.
Attribute

Parameters
None

When the OCD alarm occurs, all the services in the receive direction of the alarmed ATM port
lose cells.
Possible Causes
l Cause 1: A great number of bit errors occur in the receive path. The receive path reports
the alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.
l Cause 2: The ATM processing chip of the board is faulty.
Procedure
Step 1 Cause 1: A great number of bit errors occur in the receive path. The receive path reports the
1. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path.
2. If yes, clear these alarms first, and then check whether the OCD alarm is cleared.
Step 2 Cause 2: The ATM processing chip of the board is faulty.
1. Perform a cold reset on the board that reports the OCD alarm. For details, see 8.6.1 Cold
Reset.
2. If the OCD alarm persists, replace the alarmed board. For details, see 6.6 Replacing the
----End
Related Information
None
A.3.278 ODC_BATTERY_CURRENT_ABN
Description
The ODC_BATTERY_CURRENT_ABN is an alarm indicating that the current of the storage
battery is abnormal.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the cause of the alarm.
l 0x01: The internal current loop of the storage battery is broken.
l 0x02: The recharge current of the storage battery is very high.
l 0x03: The storage battery is discharged unevenly.

The equipment may fail to work normally, or event the equipment is damaged.
Possible Causes
l Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.
l Cause 2: The positive and negative polarities of the storage battery are connected
inversely.
l Cause 3: The power module frame is faulty.
l Cause 4: The power monitoring module is faulty.
l Cause 5: The power module is faulty.
Procedure
Step 1 Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.
If... Then...
The circuit breaker of the storage battery is open Close the circuit breaker.
The fuse of the storage battery is broken Replace the fuse.
Step 2 Cause 2: The positive and negative polarities of the storage battery are connected inversely.
1. Connect the positive and negative polarities of the storage battery correctly.
Step 3 Cause 3: The power module frame is faulty.

1. Check whether the power module frame is damaged. If the power module frame is
damaged, replace the power module frame.
Step 4 Cause 4: The power monitoring module is faulty.

1. Replace the power monitoring module.
Step 5 Cause 5: The power module is faulty.

1. Check whether the ODC_MDL_ABN alarm is reported.
If... Then...
The ODC_MDL_ABN alarm is Rectify the fault by referring the solution to
reported the ODC_MDL_ABN alarm.

If... Then...
The ODC_MDL_ABN alarm is not Replace the power module.
reported
----End
Related Information
None
A.3.279 ODC_BATTERY_PWRDOWN
Description
The ODC_BATTERY_PWRDOWN is an alarm indicating that the storage battery fails to
provide power for the equipment.
Attribute
Parameters
Name Meaning
l 0x01: power-off due to low voltage
l 0x02: power-off due to NMS control
l 0x03: power-off due to human interference
l 0x04: power-off due to high temperature

The equipment does not have backup a power supply.
Possible Causes
l Cause 1 of power-off due to NMS control: The storage battery fails to provide power for
the equipment due to NMS control.
l Cause 1 of power-off due to local human interference: The BAT button on the front
panel of the PMU is set to OFF.

l Cause 1 of power-off due to low voltage: The AC input power is abnormal.

l Cause 2 of power-off due to low voltage: The power module is faulty.
l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
l Cause 1 of power-off due to high temperature: The temperature that results in power-off
of the storage battery due to high temperature is set to an inappropriate value.
l Cause 2 of power-off due to high temperature: The temperature of the storage battery is
very high.
l Cause 3 of power-off due to high temperature: The temperature sensor of the power
module is faulty.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Cause 1 of power-off due to NMS control: The storage battery fails to provide power for the
equipment due to NMS control.
1. Enable the battery to power on the equipment.
Step 3 Cause 1 of power-off due to local human interference: The BAT button on the front panel of
the PMU is set to OFF.
1. On the front panel of the PMU, hold the BAT ON button for 5-10 seconds to turn on the
storage battery.
Step 4 Cause 1 of power-off due to low voltage: The AC input power is abnormal.
1. Query the threshold that results in an alarm when the AC power voltage is abnormal.
Then, determine whether the threshold is appropriate according to the configuration and
planning information.
If... Then...
The threshold is inappropriate Set the threshold to an appropriate value.
The threshold is appropriate Go to the next step.
2. Check whether the AC circuit breaker is closed.
If... Then...
The AC circuit breaker is open Close the AC circuit breaker.
The AC circuit breaker is closed Go to the next step.
3. Check the connection of the AC power cable.
If... Then...
The connection of the AC power cable is incorrect. Connect the cable properly.
The AC power cable is deteriorated and damaged. Replace the cable.
Step 5 Cause 2 of power-off due to low voltage: The power module is faulty.
1. Rectify the fault of the power module by referring to the solution to the
ODC_MDL_ABN alarm.
Step 6 Cause 3 of power-off due to low voltage: The power monitoring module is faulty.

1. Rectify the fault of the power monitoring module.
Step 7 Cause 1 of power-off due to high temperature: The temperature that results in power-off of the
power module due to high temperature is set to an inappropriate value.
1. Query the threshold that results in an alarm due to high temperature. Then, determine
whether the threshold is appropriate according to the configuration and planning
information.
If... Then...
The threshold is Set the threshold to an appropriate value.
inappropriate
The threshold is Perform the operations required when the alarm is
appropriate generated by cause 2 of power-off due to high
temperature.
Step 8 Cause 2 of power-off due to high temperature: The temperature of the storage battery is very
high.
1. Replace the storage battery.
Step 9 Cause 3 of power-off due to high temperature: The temperature sensor of the power module is
faulty.
1. Replace the temperature sensor of the power module.
----End
Related Information
None
A.3.280 ODC_DOOR_OPEN
Description
The ODC_DOOR_OPEN is an alarm indicating that the door of an outdoor cabinet is open.
Attribute
Parameters
None

If the cabinet door is open, the temperature, ambient humidity, and dust-proof measures of the
equipment are affected by the external environment.
In addition, the equipment may be damaged or stolen.

Possible Causes
l Cause 1: The door access alarm is set incorrectly.
l Cause 2: The cabinet door is open.
l Cause 3: The cable between the door sensor and the monitor device is connected
incorrectly.
l Cause 4: The door sensor is faulty.
l Cause 5: The monitor device is faulty.
l Cause 6: No door sensor is installed.
Procedure
Step 1 Cause 1: The door access alarm is set incorrectly.
1. Check whether the door access alarm is set correctly according to the configuration and
If... Then...
The door access alarm is set correctly Go to Cause 2.
The door access alarm is set incorrectly Set the door access alarm correctly.
Step 2 Cause 2: The cabinet door is open.

1. Close the cabinet door.
Step 3 Cause 3: The cable between the door sensor and the monitor device is connected incorrectly.
1. Check the cable between the door sensor and the monitor device.
If... Then...
The cable is connected incorrectly or is loose Connect the cable properly.
The cable is deteriorated or damaged Replace the cable.
Step 4 Cause 4: The door sensor is faulty.

1. Rectify the fault of the door sensor.
If... Then...
Step 5 Cause 5: The monitor device is faulty.

1. Rectify the fault of the monitor device.
Step 6 Cause 6: No door sensor is installed.

1. Install a door sensor.
----End

Related Information
None
A.3.281 ODC_FAN_FAILED
Description
The ODC_FAN_FAILED is an alarm indicating that the fan is faulty.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the position of the fault.
l 0x01: The internal fan is faulty.
l 0x02: The external fan is faulty.

The cabinet cannot dissipate heat properly. As a result, the equipment may be damaged and
the services may be affected.
Possible Causes
l Cause 1: The fan cable is connected incorrectly.
l Cause 2: The fan is faulty.
l Cause 3: The fan is not installed.
Procedure
Step 1 Determine the faulty fan according to the alarm parameters displayed on the NMS.
Step 2 Cause 1: The fan cable is connected incorrectly.

1. Connect the cable properly to the fan according to the specified regulations or rules.
Step 3 Cause 2: The fan is faulty.

1. Replace the fan module.

Step 4 Cause 3: The fan is not installed.

1. Install the TEC module that contains a fan.
----End
Related Information
None
A.3.282 ODC_HUMI_ABN
Description
The ODC_HUMI_ABN is an alarm indicating that the relative humidity in the cabinet
environment exceeds the specified threshold.
Attribute

Minor Environment alarm
Parameters
Name Meaning
l 0x01: The relative humidity is very high.
l 0x02: The relative humidity is very low.

In the case of high relative humidity, the equipment may be damaged. In the case of low
relative humidity, the life of the equipment may be shortened.
Possible Causes
l Cause 1: The threshold that results in an alarm is set incorrectly.
l Cause 2: The cable between the humidity sensor and the monitoring equipment is
connected incorrectly.
l Cause 3: The humidity sensor is faulty.
l Cause 4: The associated monitoring equipment is faulty.

Procedure
Step 1 Cause 1: The threshold that results in an alarm is set incorrectly.
1. Check whether the humidity threshold is set correctly according to the configuration and
If... Then...
The humidity threshold is set Perform the operations required when the
correctly alarm is generated due to cause 2.
The humidity threshold is set Set the humidity threshold to an appropriate
incorrectly value.
Step 2 Cause 2: The cable between the humidity sensor and the monitoring equipment is connected
incorrectly.
If... Then...
The cable is connected incorrectly or is Connect the cable properly.
loose
The cable is deteriorated and damaged Handle the exceptions of the cable.
The cable is not deteriorated and Perform the operations required when the
damaged alarm is generated due to cause 3.
Step 3 Cause 3: The humidity sensor is faulty.

1. Rectify the fault of the sensor.
If... Then...
The alarm persists Perform the operations required when the alarm is
generated due to cause 4.
Step 4 Cause 4: The monitoring equipment is faulty.

1. Rectify the fault of the monitoring equipment.
----End
Related Information
None
A.3.283 ODC_LOAD_PWRDOWN
Description
The ODC_LOAD_PWRDOWN is an alarm indicating that the secondary load is powered off.

Attribute
Parameters
Name Meaning
l 0x01: power-off due to low voltage
l 0x02: power-off due to background control
l 0x03: power-off due to startup in the case of low temperature
l 0x04: power-off due to high temperature

The services on the secondary load are interrupted.
Possible Causes
l Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.
l Cause 1 of power-off due to low voltage: The AC input power is abnormal.
l Cause 2 of power-off due to low voltage: The power module is faulty.
l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
l Cause 1 of power-off due to low temperature: The cabinet temperature is very low.
l Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty.
l Cause 1 of power-off due to high temperature: The temperature that results in power-off
of the load due to high temperature is set to an inappropriate value.
l Cause 2 of power-off due to high temperature: The cabinet temperature is very high.
l Cause 3 of power-off due to high temperature: The ambient temperature sensor is faulty.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.
1. Turn on the storage battery for the equipment.
Step 3 Cause 1 of power-off due to low voltage: The AC input power is abnormal.
1. Query the threshold that results in an alarm when the AC power voltage is abnormal.
Then, determine whether the threshold is appropriate according to the configuration and

If... Then...
The threshold is inappropriate Set the threshold to an appropriate value.
The threshold is appropriate Go to the next step.
2. Check whether the AC circuit breaker is closed.
If... Then...
3. Check the connection of the AC power cable.
If... Then...
The connection of the AC power cable is Connect the cable properly.
incorrect.
The AC power cable is deteriorated and Handle the exceptions of the
damaged. cable.
Step 4 Cause 2 of power-off due to low voltage: The power module is faulty.
1. Rectify the fault of the power module by referring to the solution to the
ODC_MDL_ABN alarm.
Step 5 Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
1. Rectify the fault of the power monitoring module.
Step 6 Cause 1 of power-off due to low temperature: The cabinet temperature is very low.
1. Check whether the heat exchanger works properly.
If... Then...
The heat exchanger does not Rectify the fault of the heat exchange.
work properly
The heat exchanger works Perform the operations required when the alarm is
properly generated by cause 2 of power-off due to low
temperature.
Step 7 Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty.
1. Replace the temperature sensor of the power module.
Step 8 Cause 1 of power-off due to high temperature: The temperature that results in power-off of the
load due to high temperature is set to an inappropriate value.
1. Query the threshold that results in an alarm in the case of power-off due to high
temperature of the load. Then, determine whether the threshold is appropriate according
to the configuration and planning information.
If... Then...
The threshold is Set the threshold to an appropriate value.
inappropriate

If... Then...
The threshold is Perform the operations required when the alarm is
appropriate generated by cause 2 of power-off due to high
temperature.
Step 9 Cause 2 of power-off due to high temperature: The cabinet temperature is very high.
1. Check whether the ambient temperature is very high all the time.
2. Check whether the heat exchanger works properly.
If... Then...
The heat exchanger does not Rectify the fault of the heat exchange.
work properly
The heat exchanger works Perform the operations required when the alarm is
properly generated by cause 3 of power-off due to high
temperature.
Step 10 Cause 3 of power-off due to high temperature: The ambient temperature sensor is faulty.
1. Replace the ambient temperature sensor.
----End
Related Information
The secondary load refers to the load that the DC power outlet of the cabinet corresponds to.
A.3.284 ODC_MDL_ABN
Description
The ODC_MDL_ABN is an alarm indicating that the power module is abnormal.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the ID of the alarmed power module.

Name Meaning
Parameter 2, Indicates the cause of the alarm.
Parameter 3
l 0x01: The power module is switched off.
l 0x02: The power module is faulty.
l 0x03: The power module stops self-protection.
l 0x04: The power module fails to communicate with the power
monitoring module, or the power module is not in position.
l 0x05: The number of PSUs configured on the NMS is incorrect.
l 0x06: The power module status cannot be identified.

If the power module is faulty, the loading capability of the power system is affected. As a
result, the storage battery may discharge, or even the entire power system of the equipment is
powered off.
Possible Causes
l Cause 1: The number of PSUs configured on the NMS is incorrect.
l Cause 2: The power module is not in position.
l Cause 3: The power module is faulty.
l Cause 4: The power monitoring unit is abnormal.
Procedure
Step 1 Cause 1: The power module is not configured on the NMS.
1. Set the logical slot of the power module on the NMS.
Step 2 Cause 2: The power module is not in position, or the power module is not inserted properly.
If... Then...
The power module is not in position Install the power module.
The power module is not inserted securely Install the power module properly.
Step 3 Cause 3: The power module is faulty.

1. Replace the power module.
Step 4 Cause 4: The power monitoring unit is abnormal.

1. Rectify the fault of the power monitoring unit.
----End
Related Information
None

A.3.285 ODC_POWER_FAIL
Description
The ODC_POWER_FAIL is an alarm indicating that the AC input power voltage and DC
output power voltage of an outdoor cabinet are abnormal.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the type of the fault.
l 0x56: The AC input power is very high.
l 0x57: The AC input power is very low.
l 0x58: The DC output power is very high.
l 0x59: The DC output power is very low.
l 0x5b: No AC input power is available.
l 0x5c: The AC power voltage is abnormal.

l If the AC input power voltage is abnormal, the equipment is powered on by the storage
battery and cannot work for a long time.
l If the DC output power voltage is abnormal, the services on the equipment are
interrupted.
Possible Causes
l Cause 1: The AC input power voltage is abnormal.
l Cause 2: The DC output power voltage is abnormal.
Procedure
Step 1 Cause 1: The AC input power voltage is abnormal.
1. The threshold that results in an alarm due to the AC input power voltage is set
incorrectly.

If... Then...
The threshold is set incorrectly Set the threshold to an appropriate value.
The threshold is set correctly Go to the next step.
2. The AC circuit breaker is open.
If... Then...
3. The AC power cable is connected incorrectly.
If... Then...
The cable is connected incorrectly or is loose Connect the cable properly.
The cable is connected correctly Go to the next step.
4. The AC power grid distributes the power abnormally.
If... Then...
The AC power grid distributes the power Rectify the fault of the power module
abnormally at the base station.
The AC power grid distributes the power Go to the next step.
normally
5. The monitoring equipment is faulty.
If... Then...
The monitoring equipment is Rectify the fault of the monitoring equipment.
faulty
The monitoring equipment is not Perform the operations required when the
faulty alarm is generated due to cause 2.
Step 2 Cause 2: The DC output power voltage is abnormal.

1. The threshold that results in an alarm is set incorrectly.
If... Then...
The threshold is set incorrectly Set the threshold to an appropriate value.
The threshold is set correctly Go to the next step.
2. The PSU module is faulty.
If... Then...
The PSU module is faulty Rectify the fault of the PSU module.
The PSU module is not faulty Go to the next step.
3. The power of the storage battery is insufficient.

If... Then...
The power of the storage battery is Recharge the storage battery.
insufficient
The power of the storage battery is sufficient Rectify the fault of the monitoring
equipment.
----End
Related Information
None
A.3.286 ODC_SMOKE_OVER
Description
The ODC_SMOKE_OVER is an alarm indicating that smoke occurs in an outdoor cabinet.
Attribute

Critical Environment alarm
Parameters
None

The equipment may be burned.
Possible Causes
l Cause 1: The smoke alarm is set incorrectly.
l Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.
l Cause 3: The cable between the smoke sensor and the monitoring equipment is
l Cause 4: The smoke sensor is faulty.
Procedure
Step 1 Cause 1: The smoke alarm is set incorrectly.
1. Check whether the smoke alarm is set correctly according to the configuration and

If... Then...
The smoke alarm is set correctly Perform the operations required when the
alarm is generated due to cause 2.
The smoke alarm is set incorrectly Set the smoke alarm correctly.
Step 2 Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.
1. Extinguish the fire in the cabinet.
Step 3 Cause 3: The cable between the smoke sensor and the monitoring equipment is connected
incorrectly.
1. Check whether the cable between the sensor and the monitoring equipment is connected
correctly.
If... Then...
loose
The cable is deteriorated and damaged Replace the cable.
The cable is not deteriorated and Perform the operations required when
damaged the alarm is generated due to cause 4.
Step 4 Cause 4: The smoke sensor is faulty.

If... Then...
Step 5 Cause 5: The associated monitoring equipment is faulty.

----End
Related Information
None
A.3.287 ODC_SURGE_PROTECTION_FAIL
Description
The ODC_SURGE_PROTECTION_FAIL is an alarm indicating that the surge protection
function of the outdoor cabinet is abnormal.

Attribute

Parameters
Name Meaning
Parameter 1 Indicates the type of the alarm.
l 0x01: AC surge protection alarm
l 0x02: DC surge protection alarm

The AC surge protection function of the cabinet is disabled.
Possible Causes
l Cause 1: The alarm is set incorrectly.
l Cause 2: The cable between the lightning sensor and the monitoring equipment is
l Cause 3: The lightning sensor is faulty.
l Cause 3: The lightning arrestor is faulty.
Procedure
Step 1 Cause 1: The alarm is set incorrectly.
1. Check whether the alarm is set correctly according to the configuration and planning
information.
If... Then...
The alarm is set correctly Perform the operations required when the alarm is
The alarm is set incorrectly Set the surge protection alarm correctly.
Step 2 Cause 2: The cable between the lightning sensor and the monitoring equipment is connected
incorrectly.
1. Check the cable connection between the sensor and the monitoring equipment.

If... Then...
loose
The cable is deteriorated and damaged Replace the cable.
Step 3 Cause 3: The lightning sensor is faulty.

If... Then...
Step 4 Cause 3: The lightning arrestor is faulty.

1. Check whether the alarm output end of the lightning arrestor works properly.
If... Then...
The alarm output end of the lightning Perform the operations required
arrestor works properly when the alarm is generated due to
cause 5.
The alarm output end of the lightning Replace the lightning arrestor.
arrestor does not work properly
Step 5 Cause 5: The associated monitoring equipment is faulty.

----End
Related Information
None
A.3.288 ODC_TEC_ALM
Description
The ODC_TEC_ALM is an alarm indicating that the TEC air conditioning module in the
cabinet does not work properly.
Attribute

Parameters
None

If the TEC air conditioning module does not work properly, the storage battery may operate at
very high or low temperature and therefore the safety performance of the storage battery
degrades.
Possible Causes
l Cause 1: The TEC cable is connected incorrectly.
l Cause 2: The TEC module is faulty.
l Cause 3: The monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The TEC cable is connected incorrectly.
1. Connect the TEC cable correctly.
Step 2 Cause 2: The TEC module is faulty.
1. Replace the TEC module.
----End
Related Information
None
A.3.289 ODC_TEMP_ABN
Description
The ODC_TEMP_ABN is an alarm indicating that the ambient temperature of the cabinet or
the temperature of the storage battery is abnormal.
Attribute
Parameters

Name Meaning
l 0x01: The ambient temperature is higher than the upper threshold.
l 0x01: The ambient temperature is lower than the lower threshold.
Parameter 2 Indicates the temperature type.
l 0x01: The temperature at the air outlet is very high or low.
l 0x0b: Ambient temperature 1 is very high or low.
l 0x0c: Ambient temperature 2 is very high or low.
l 0x0d: The temperature of the battery group is very high or low.

If the temperature is abnormal, the equipment performance degrades and the life of the
equipment decreases.
Possible Causes
l Cause 1: The temperature threshold that results in an alarm is set incorrectly.
l Cause 2: The cable between the temperature sensor and the monitoring equipment is
l Cause 3: The temperature sensor is faulty.
Procedure
Step 1 Cause 1: The temperature threshold that results in an alarm is set incorrectly.
1. Check whether the temperature alarm is set correctly according to the configuration and
If... Then...
The temperature alarm is set Perform the operations required when the
correctly alarm is generated due to cause 2.
The temperature alarm is set Set the temperature alarm correctly.
incorrectly
Step 2 Cause 2: The cable between the temperature sensor and the monitoring equipment is
correctly.
If... Then...
loose

If... Then...
Step 3 Cause 3: The temperature sensor is faulty.

If... Then...

----End
Related Information
None
A.3.290 ODC_WATER_ALM
Description
The ODC_WATER_ALM is an alarm indicating that certain water enters the cabinet.
Attribute
Critical Environment alarm
Parameters
None

The moisture in the cabinet increases, and the equipment in the cabinet may be damaged.
Possible Causes
l Cause 1: The water alarm is set incorrectly.
l Cause 2: Certain water enters the cabinet.
l Cause 3: The cable between the water sensor and the monitoring equipment is connected
incorrectly.
l Cause 4: The water sensor is faulty.

Procedure
Step 1 Cause 1: The water alarm is set incorrectly.
1. Check whether the water alarm is set correctly according to the configuration and
If... Then...
The water alarm is set correctly Perform the operations required when the
alarm is generated due to cause 2.
The water alarm is set incorrectly Set the water alarm correctly.
Step 2 Cause 2: Certain water enters the cabinet.

1. Dry the cabinet and take waterproof measures for the cabinet.
Step 3 Cause 3: The cable between the sensor and the monitoring equipment is connected
incorrectly.
correctly.
If... Then...
loose
Step 4 Cause 4: The sensor is faulty.


----End
Related Information
None
A.3.291 OSPFNBRSTATECHANGE
Description
The OSPFNBRSTATECHANGE alarm indicates that the OSPF neighbor state changes.

Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the router ID.
Parameter 5 to Parameter 8 Indicate the IP address of the OSPF neighbor.
Parameter 9 to Parameter 12 Indicate the index number of the interface on the OSPF
neighbor.
Parameter 13 to Parameter 16 Indicate the router ID of the OSPF neighbor.
Parameter 17 to Parameter 20 Indicate the OSPF neighbor state.
l 0x01: Down
l 0x02: Attempt
l 0x03: Init
l 0x04: 2-Way
l 0x05: ExStart
l 0x06: Exchange
l 0x07: Loading
l 0x08: Full
Parameter 21 to Parameter 24 Indicate the OSPF process ID.
Parameter 25 to Parameter 28 Indicate the OSPF area ID.
Parameter 29 to Parameter 32 Indicate the index number of the local interface.
Parameter 33 to Parameter 36 Indicate the IP address of the local interface.
Parameter 37 to Parameter 100 Indicate the name of the local interface.
Parameter 101 to Parameter 131 Indicate the name of the VPN instance.
Parameter 132 to Parameter 135 Indicate the alarm cause.

If the neighbor state transitions from Down to Full, no handling is required. If the neighbor
state transitions from Full to Down, services may be interrupted.
NOTE
State changes from Down to Full: Down > Init > 2-way > Exstart > Exchange > Loading >Full

Possible Causes
l Cause 1: OSPF configurations are changed at the peer end.
l Cause 2: The peer port is faulty.
l Cause 3: The physical link is faulty.
Procedure
Step 1 Cause 1: OSPF configurations are changed at the peer end.
1. Check whether OSPF configurations are correct at the peer end. If the OSPF
configurations are incorrect (such as incorrect interface IP address configurations,
inconsistent authentication mode configurations, and inconsistent OSPF area
configurations), rectify the configurations to ensure configuration consistency at both
ends.
Step 2 Cause 2: The peer port is faulty.

1. Check whether the peer port is faulty, such as the port disabling state and abnormal
optical power. If the peer port is faulty, rectify the fault.
Step 3 Cause 3: The physical link is faulty.

1. Check whether any fiber or cable is broken, damaged, or pressed. If any of the preceding
problems exist, replace the faulty fiber or cable.

1. If the peer NE is faulty, rectify the fault.
----End
Related Information
None
A.3.292 OUT_PWR_ABN
Description
The OUT_PWR_ABN alarm indicates that the output optical power is abnormal.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the port ID.
Parameter 2, Parameter 3 Indicate the path ID. The parameters have a fixed value of 0x00
0x01.
Parameter 4, Parameter 5 Are reserved. The value is always 0xFF.

The OUT_PWR_ABN alarm affects the transmission performance of services, and may even
result in service interruption.
Possible Causes
l Cause 1: The output optical power is too high or low.
Procedure
Step 1 Cause 1: The output optical power is too high or low.
1. Browse optical power performance events.
If... Then...
The output optical power does not meet the Replace the optical module.
requirement
The output optical power is too high Add a proper attenuator to reduce the
input optical power.

----End
Related Information
None
A.3.293 OUT_PWR_HIGH
Description
The OUT_PWR_HIGH alarm indicates that the output optical power is excessively high. This
alarm is reported when a board detects that the output optical power is greater than the upper
threshold of the output power reference value.

Attribute
Parameters
None

After the OUT_PWR_HIGH alarm is reported, bit errors will occur on services. In addition,
the excessively high output optical power will damage the peer laser or meter.
Possible Causes
l Cause 1: The input optical power is excessively high.
l Cause 2: The optical module or board is faulty.
Procedure
Step 1 Cause 1: The input optical power is excessively high.
1. On the NMS, check whether the IN_PWR_HIGH alarm is present on the equipment. If
the alarm exists, clear it.
2. Check whether the OUT_PWR_HIGH alarm is cleared. If the alarm persists, proceed to
Cause 2.
Step 2 Cause 2: The optical module or board is faulty.

1. Check the pluggable optical module on the board that reports the alarm.
If... Then...
The optical module is not in good Remove and re-insert the optical module.
contact with the optical port,
The optical module is faulty, Replace the optical module. For the
method, see 6.14 Replacing the SFP.
2. Reset the board that reports the alarm. If the alarm persists, proceed to the next step.
3. Replace the board that reports the alarm. For details, see the Part Replacement.
----End
Related Information
None

A.3.294 OUT_PWR_LOW
Description
The OUT_PWR_LOW alarm indicates that the output optical power is excessively low. This
alarm is reported when a board detects that the output optical power is less than the lower
threshold of the output power reference value.
Attribute
Parameters
None

If the OUT_PWR_LOW alarm is reported, service transmission will be affected.
Possible Causes
l Cause 1: The input optical power is excessively low.
l Cause 2: The laser ages or board hardware is faulty.
Procedure
Step 1 Cause 1: The input optical power is excessively low.
1. On the NMS, check whether the IN_PWR_LOW alarm is present on the equipment. If
the alarm exists, clear it.
2. Check whether the OUT_PWR_LOW alarm is cleared. If the alarm persists, proceed to
Cause 2.
Step 2 Cause 2: The laser ages or board hardware is faulty.
1. Check the pluggable optical module on the board that reports the alarm.
If... Then...
The optical module is not in good Remove and re-insert the optical module.
contact with the optical port,
The optical module is faulty, Replace the optical module. For the
method, see 6.14 Replacing the SFP.
2. Reset the board that reports the alarm. If the alarm persists, proceed to the next step.
3. Replace the board that reports the alarm. For details, see the Part Replacement.
----End

Related Information
None
A.3.295 OUT1TEMP_SENSOR_FAIL
Description
The OUT1TEMP_SENSOR_FAIL is an alarm indicating that the air outlet temperature sensor
of the cabinet fails.
Attribute
Parameters
None

The air outlet temperature data of the TCU cannot be collected.
Possible Causes
l Cause 1: The air outlet temperature sensor is faulty.
l Cause 4: The air outlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air outlet temperature sensor is faulty.
1. Replace the air outlet temperature sensor.
If... Then...

If... Then...

If... Then...

Step 4 Cause 4: The air outlet temperature sensor is not installed.
1. Install the air outlet temperature sensor.
----End
Related Information
None
A.3.296 OUT2TEMP_SENSOR_FAIL
Description
The OUT2TEMP_SENSOR_FAIL is an alarm indicating that the external cycling air outlet
temperature sensor of the cabinet fails.
Attribute
Parameters
None

The external cycling air outlet temperature data of the TCU cannot be collected.
Possible Causes
l Cause 1: The external cycling air outlet temperature sensor is faulty.
l Cause 4: The external cycling air outlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The external cycling air outlet temperature sensor is faulty.
1. Replace the external cycling air outlet temperature sensor.

If... Then...

If... Then...

Step 4 Cause 4: The external cycling air outlet temperature sensor is not installed.
1. Install the external cycling air outlet temperature sensor.
----End
Related Information
None
A.3.297 PASSWORD_NEED_CHANGE
Description
The PASSWORD_NEED_CHANGE alarm indicates that the default user password, WLAN
password, or AES authentication code has not been changed and must been changed timely to
prevent security risks.
Attribute

Major Service alarm
Parameters
None

None

Possible Causes
l Cause 1: The default user password has not been changed.
l Cause 2: The default WLAN password has not been changed.
l Cause 3: The default AES authentication code has not been changed.
Procedure
Step 1 Change the default user password, WLAN password, or AES authentication code. After the
related password is changed, the PASSWORD_NEED_CHANGE alarm is automatically
cleared.
----End
Related Information
None
A.3.298 PATCH_BD_EXCLUDE
Description
The PATCH_BD_EXCLUDE alarm indicates that an error occurs when a patch package is
being loaded to a board. The board is automatically isolated from patch package loading.
Attribute
Parameters
None

The board is isolated from patch package matching and patch package loading.
Possible Causes
Cause: An error occurs when a patch package is being loaded to the board.
Procedure
Step 1 Re-load the patch package.
----End
Related Information
None

A.3.299 PATCH_BD_MATCH_FAIL
Description
The PATCH_BD_MATCH_FAIL alarm indicates that the patch package does not match the
board to which the patch package is loaded.
Attribute
Parameters
None

Patch package loading fails.
Possible Causes
Cause: The patch package does not match the board to which the patch package is loaded.
Procedure
Step 1 Reload a correct patch package to the board.
----End
Related Information
None
A.3.300 PATCH_CHGSCC_NOTMATCH
Description
The PATCH_CHGSCC_NOTMATCH alarm indicates a mismatch between the patch package
and the system control board after the system control board is replaced.
Attribute
Parameters
None


Patch package loading fails.
Possible Causes
Cause: The system control board is replaced.
Procedure
Step 1 Re-load the patch package.
----End
Related Information
None
A.3.301 PATCH_PKGERR
Description
The PATCH_PKGERR alarm indicates that a patch package is incorrect or has been damaged
or deleted.
Attribute

Minor alarm Equipment alarm
Parameters
None

If a patch package is incorrect or has been damaged or deleted, the patch package cannot be
successfully loaded, activated, or run.
NOTE
When this alarm is reported, services are not interrupted.
Possible Causes
l Cause 1: A patch package is incorrect.
l Cause 2: A patch package has been damaged.
l Cause 3: A patch package has been deleted.

Procedure
Step 1 Load a correct patch package.
----End
Related Information
None
A.3.302 PG_LINK_FAIL
Description
The PG_LINK_FAIL is an alarm indicating that the links in a 1+1 protection group fail.
Attribute

Parameters
None

The services on the radio links are interrupted.
Possible Causes
Cause: Service alarms occur on the main and standby boards.
Procedure
Step 1 Set the Alarm Report Mode to Protection group and board alarms. For details, see
Querying the IF 1+1 Protection Status.
NOTE
When alarms with different priorities occur on a board at the same time, the board reports only the
alarms with the highest priority. Alarms can be arranged in descending order by priority: hardware
alarms > configuration alarms > service alarms.
Step 2 Handle the queried alarms.
----End
Related Information
None

A.3.303 PG_PRT_DEGRADED
Description
The PG_PRT_DEGRADED alarm indicates that a 1+1 protection group is degraded. This
alarm is reported when a fault occurs on the active or standby link in a 1+1 protection group.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the slot ID of the board.
Parameter 2 Indicates the slot ID of the subboard.
Parameter 3 Indicates the port ID.
Parameter 4 Indicates the fault type.
l 0x01: indicates that another service alarm exists.

l 0x02: indicates that the protection group is in the lockout state.
l 0x03: indicates that the protection group is in the forced switching state.

The services at the NE are not affected, but radio link protection fails.
Possible Causes
l Cause 1: A service or hardware alarm exists on the board that has reported the alarm.
l Cause 2: The 1+1 protection group is locked out, or forced switching is performed
manually.
Procedure
Step 1 Query the PG_PRT_DEGRADE alarm on the NMS and identify the faulty board based on
alarm parameters.
Step 2 Cause 1: A service or hardware alarm exists on the board that has reported the alarm.
1. Check for R_LOF, MW_LOF, and HARD_BAD alarms on the faulty board or
corresponding ODU and clear them by following instructions in A.3.330 R_LOF, A.
3.267 MW_LOF, and A.3.122 HARD_BAD if any.

Step 3 Cause 2: The 1+1 protection group is locked out, or forced switching is performed manually.
1. Identify the cause of manual switching and clear the switching by following instructions
in Testing IF 1+1 Protection Switching.
Step 4 Check whether the alarm PG_PRT_DEGRADE is cleared. If the alarm persists, contact
----End
Related Information
None
A.3.304 PLA_CFG_MISMATCH
Description
The PLA_CFG_MISMATCH alarm indicates that physical link aggregation (PLA)
configurations are inconsistent at two ends of a microwave link.
Attribute
Parameters
Name Meaning
Parameter 1, Indicate the ID of the PLA group.

Parameter 2

Name Meaning
Parameter 3, Indicate the error type.

Parameter 4
Parameter 3 has a fixed value of 0x00. Parameter 4 takes one of the
following values:
l 0x00: The PLA group is not configured on the IF board of the peer NE.
l 0x01: Layer 2 header compression is enabled for only one NE.
l 0x02: Layer 3 header compression is enabled for only one NE.
l 0x03: The number of member links in the PLA group is different at
both ends.
l 0x04: Local member ports and peer member ports do not belong to the
same PLA group.
l 0x06: Configurations of enhanced compression for CS7 queues in PLA
groups at both ends of a microwave link are inconsistent.
l 0x07: Configurations of enhanced compression for CS6 queues in PLA
l 0x08: Configurations of enhanced compression for EF queues in PLA
l 0x09: Configurations of enhanced compression for AF4 queues in PLA
l 0x0A: Configurations of enhanced compression for AF3 queues in PLA
l 0x0B: Configurations of enhanced compression for AF2 queues in PLA
l 0x0C: Configurations of enhanced compression for AF1 queues in PLA
l 0x0D: Configurations of enhanced compression for BE queues in PLA
l 0x0E: The PLA capacities are inconsistent at the two ends of a
microwave link.
l 0x0F: The PLA scheduling types are inconsistent at the two ends of a
microwave link.
l 0x10: The PLA priority thresholds are inconsistent at the two ends of a
microwave link.
l 0x11: The priorities of PLA members are inconsistent at the two ends
of a microwave link.
l 0x12: The local-end PLA member port and the remote-end PLA
member port have different port rates.
l 0x13: The channel configurations of PLA members are inconsistent at
the two ends of a link.
l 0x14: The channel configurations of the master and slave devices in a
PLA group are inconsistent.


The services carried by the radio link are unavailable.
NOTE
If the value of Parameter 4 is 0x06-0x0D, 0x01 or 0x02, the enhanced compression configurations for
each queue, Layer 2 header compression configuration and Layer 3 header compression configuration in
the PLA protection group may not take effect.
Possible Causes
l Cause 1: The PLA group is configured on the local NE, but not configured on the peer
NE.
l Cause 2: Frame header compression is enabled for only one NE.
l Cause 3: The number of member links in the PLA group is different at both ends.
l Cause 4: Local member ports and peer member ports do not belong to the same PLA
group.
l Cause 5: Enhanced compression is enabled for only one NE.
l Cause 6: The Super EPLA configurations are inconsistent at the two ends of the
microwave link.
Procedure
Step 1 Cause 1: The PLA group is configured on the local NE, but not configured on the peer NE.
1. Configure the PLA group on the peer NE by referring to Creating a PLA/EPLA/EPLA+/
Super EPLA Group.
Step 2 Cause 2: Frame header compression is enabled for only one NE.
1. Determine the port that needs to be re-configured. For details, see Querying the Status of
a PLA/EPLA/EPLA+/Super EPLA Group and the network plan.
2. Enable or disable frame header compression on the port to ensure configuration
consistency at both ends. For details, see Configuring Ethernet Frame Header
Compression over Air Interfaces.
Step 3 Cause 3: The number of member links in the PLA group is different at both ends.
1. Set the number of member links consistently at both ends by referring to Creating a
PLA/EPLA/EPLA+/Super EPLA Group.
Step 4 Cause 4: Local member ports and peer member ports do not belong to the same PLA group.
1. Check whether PLA configurations of the interconnected IF boards comply with the
network plan. For details, see Creating a PLA/EPLA/EPLA+/Super EPLA Group.
Option Description
If... Then...
The configurations do not comply Re-configure the PLA group according to the
with the network plan network plan.
The configurations comply with Verify the IF cable connections between the IF
the network plan boards and ODUs to make sure the radio links
are correctly established.

Step 5 Cause 5: Enhanced compression is enabled for only one NE.

1. Ensure that the enhanced compression status is consistent on both NEs. For details, see
Managing Radio Links.
Step 6 Cause 6: The Super EPLA configurations are inconsistent at the two ends of the microwave
link.
1. If the NE reports the parameters 0x0E to 0x14, the Super EPLA configurations are
inconsistent at the two ends. Modify the Super EPLA configurations to ensure consistent
configurations at the two ends. For details, see Creating a Super EPLA Group.
----End
Related Information
None
A.3.305 PLA_DOWN
Description
The PLA_DOWN alarm indicates that a PLA group is faulty. This alarm is reported when the
number of active member links in a PLA group is 0 or smaller than the preset minimum
number of active member links.
NOTE
The PLA in this section refers to EPLA.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the PLA group.

The services carried by the PLA group are interrupted.
Possible Causes
The number of active member links in the PLA group is 0 or smaller than the preset minimum
number of active member links.

Procedure
Step 1 Check whether the specified minimum number of active links is consistent with the network
plan. If not, re-configure the minimum number of active links. For details, see querying PLA
group status.
Step 2 Clear the PLA_MEMBER_DOWN alarm.
----End
Related Information
None
A.3.306 PLA_MEMBER_DOWN
Description
The PLA_MEMBER_DOWN alarm indicates that a member link of a PLA group is faulty.
Attribute
Minor Service alarm
Parameters
Name Meaning
Parameter 1, Indicate the ID of the PLA group. For example, 0x00 0x01 indicates
Parameter 2 that the PLA group ID is 1. For details, see Parameter Examples.
Parameter 3 Indicates the slot ID of the inactive member. For example, 0x03
indicates that the slot ID is 3.
Parameter 4 Indicates the subboard ID of the inactive member. The parameter
takes a fixed value of 0xff.
Parameters 5 and 6 Indicate the port ID of the inactive member. For example, 0x00
0x01 indicates port 1.

If the PLA_DOWN alarm is also reported, services are interrupted. If the PLA_DOWN alarm
is not reported, only the services carried by the faulty member link are interrupted and
available bandwidth of the PLA group decreases.
Possible Causes
l Cause 1: A member link of the PLA group is faulty at the local end.

l Cause 2: The IF board configured with the PLA group or related ODU hardware is faulty
at the local end.
Procedure
Step 1 Cause 1: A member link of the PLA group is faulty at the local end.
1. Determine the associated IF board and radio links based on the ID of the PLA group. For
details, see querying PLA group status.
2. Check whether the MW_LOF, MW_LIM, MW_RDI, R_LOC, and R_LOF alarms are
reported the radio links. If yes, clear these alarms.
Step 2 Cause 2: The IF board configured with the PLA group or related ODU hardware is faulty at
the local end.
1. Determine the associated IF board and ODU based on the ID of the PLA group. For
details, see querying PLA group status.
2. Check whether the IF board and ODU report hardware-related alarms, such as
HARD_BAD, BD_STATUS, VOLT_LOS, WRG_BD_TYPE, and RADIO_MUTE. If
yes, clear these alarms.
----End
Related Information
Figure A-2 Parameter Examples
l Parameters 1 and 2 (0x00 0x01) indicate that the PLA group ID is 1.

l Parameter 3 (0x03) indicates that the slot ID is 3.
l Parameter 4 takes a fixed value of 0xff.
l Parameters 5 and 6 (0x00 0x01) indicate that the port ID is 1.
A.3.307 PLA_MEMBER_DOWN_EXT
Description
The PLA_MEMBER_DOWN_EXT alarm is reported when a member link of a Super EPLA
group is faulty.

Attribute
Minor QoS alarm
Parameters
Name Meaning
Parameter 1 and Indicate the ID of the Super EPLA group. For example, 0x00 0x08
Parameter 2 indicates that the protection group ID is 8. For details, see
Parameter Examples.
Parameter 3 to Indicate the NE ID. For example, 0x00 0x09 0xac 0x02 indicates
Parameter 6 that the NE ID is 9-44034. That is, parameters 3 and 4 indicate the
extended ID, and parameters 5 and 6 indicate the basic ID.
Parameter 7 and Indicate the slot ID of the board. For example, 0x00 0x01 indicates
Parameter 8 that the slot ID is 1.
Parameter 9 Indicates the slot ID of the subboard. The parameter takes a fixed
value of 0xff.
Parameter 10 and
Indicate the port ID. For example, 0x00 0x05 indicates port 5.
Parameter 11

Available bandwidth of the Super EPLA group decreases. If a PLA_DOWN alarm is also
reported, services are interrupted.
Possible Causes
l Cause 1: The general-band microwave link in the super EPLA group at the local end is
faulty.
l Cause 2: An IF board in the super EPLA group at the local end is faulty.
l Cause 3: The E-band microwave link in the super EPLA group at the local end is faulty.
l Cause 4: The E-band device in the super EPLA group at the local end is faulty.
l Cause 5: The cascaded NE is faulty.
l Cause 6: The cascade port is faulty.
l Cause 7: Loss of connectivity occurs on a member link of the Super EPLA group.
l Cause 8: Remote defect indication exists on a member link of the Super EPLA group.
Procedure
Step 1 Cause 1: The general-band microwave link in the super EPLA group at the local end is faulty.
1. Determine the faulty IF board and microwave link based on the ID of the Super EPLA
group. For details, see querying the status of a Super EPLA group.

2. Check whether a member link of the Super EPLA group reports MW_LOF, MW_LIM,
MW_RDI, R_LOC, or R_LOF alarms. If any of the preceding alarms is reported, clear
it.
Step 2 Cause 2: An IF board in the super EPLA group at the local end is faulty.
1. Determine the faulty IF board based on the ID of the Super EPLA group. For details, see
querying the status of a Super EPLA group.
2. Check whether any IF board in the Super EPLA group reports HARD_BAD,
BD_STATUS, VOLT_LOS, WRG_BD_TYPE, or RADIO_MUTE alarms. If any of
the preceding hardware-related alarms is reported, clear it.
Step 3 Cause 3: The E-band microwave link in the super EPLA group at the local end is faulty.
1. If the NMS can access the RTN 380, troubleshoot the E-band link fault by following
instructions in "Troubleshooting Microwave Link Faults of the OptiX RTN 380
Maintenance and Fault Management.
2. If the NMS cannot access the RTN 380, troubleshoot the fault by referring to the
troubleshooting steps for Cause 4.
Step 4 Cause 4: The E-band device in the super EPLA group at the local end is faulty.
1. Check whether an ETH_LOS alarm is reported at the local end. If yes, clear the alarm
immediately. If the RTN 380 is faulty, rectify the fault by following instructions in the
OptiX RTN 380 Maintenance and Fault Management.
Step 5 Cause 5: The cascaded NE is faulty.
1. Replace the cascaded NE and re-configure the Super EPLA group. Ensure that Super
EPLA group configurations are consistent at both ends.
Step 6 Cause 6: The cascade port is faulty.
1. If the cascade port is faulty, for example, the port is disabled, rectify the fault.
Step 7 Cause 7: Loss of connectivity occurs on a member link of the Super EPLA group.
1. Check for and clear the MW_LOF alarm on the local NE.
Step 8 Cause 8: Remote defect indication exists on a member link of the Super EPLA group.
1. Check for and clear the MW_RDI alarm on the local NE.
----End
Related Information
Figure A-3 Parameter Example 1
l Parameters 1 and 2 (0x00 0x08) indicate that the protection group ID is 8.

l Parameters 3 to 6 (0x00 0x09 0xac 0x02) indicate that the NE ID is 9-44034. That is,
parameters 3 and 4 indicate the extended ID, and parameters 5 and 6 indicate the basic
ID.

l Parameters 7 and 8 (0x00 0x01) indicate that the slot ID is 1.

l Parameters 12 and 13 (0x00 0x01) indicate that the path ID is 1.
l Parameter 14 (0x00) indicates that the fault cause is loss of connectivity.
Figure A-4 Parameter Example 2
l Parameters 1 and 2 (0x00 0x01) indicate that the protection group ID is 1.

l Parameters 3 to 6 (0x00 0x09 0xac 0xe2) indicate that the NE ID is 9-44258. That is,
parameters 3 and 4 indicate the extended ID, and parameters 5 and 6 indicate the basic
ID.
l Parameters 7 and 8 (0x00 0x04) indicate that the slot ID is 4.
A.3.308 PLA_PKT_ERR
Description
The PLA_PKT_ERR alarm indicates that packet reassembly fails in the receive direction.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameters 1 and 2 Indicate the ID of the PLA group.


Services in the PLA group are unavailable.
Possible Causes
Cause 1: The clock tracing relationship is incorrectly configured for the active and standby
NEs.
Cause 2: A member link in the PLA group is faulty.
Cause 3: The local or cascaded NE has a hardware fault.
Procedure
Step 1 Check whether the clock tracing relationship is correctly configured for the active and standby
NEs. If the clock tracing relationship is incorrect, configure the clock sources again. If the
clock tracing relationship is correct, go to the next step.
Step 2 Check for MW_LOF, MW_LIM, MW_RDI, and R_LOF alarms on links in the PLA group
and clear them if any. If no such alarm is reported, go to the next step.
Step 3 Check for the HARD_BAD alarm on the local and cascaded NEs. If the local or cascaded NE
reports the HARD_BAD alarm, replace the alarmed board by following instructions in 6.10
Replacing the System Control, Switching and Timing Board.
----End
Related Information
None
A.3.309 PORTMODE_MISMATCH
Description
The PORTMODE_MISMATCH is an alarm indicating that the working mode of the remote
FE port does not match with that of the local FE port. This alarm is reported when the local
FE port works in auto-negotiation mode and the opposite FE port works in non-auto-
negotiation mode.
NOTE
Both GE and FE ports support the PORTMODE_MISMATCH alarm.
Attribute
Minor Service alarm
Parameters


Name Meaning
Parameter 1, Parameter 2 Indicate the working mode of the FE port.

When the PORTMODE_MISMATCH alarm occurs, the service on the local NE is not
affected.
Possible Causes
l Cause 1: The local port works in auto-negotiation mode and the opposite port works in
non-auto-negotiation mode.
Procedure
Step 1 Cause 1: The local port works in auto-negotiation mode and the opposite port works in non-
auto-negotiation mode.
1. Disable the opposite port. For details, refer to Setting the Basic Attributes of Ethernet
Ports.
2. Enable the opposite port and set work mode of the port to auto-negotiation. For details,
refer to Setting the Basic Attributes of Ethernet Ports.
----End
Related Information
None
A.3.310 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC alarm indicates that the traffic over a port exceeds its threshold.
Attribute
Major Service alarm
Parameters

Name Meaning
Parameter 1 Indicates the traffic in the receive or transmit direction exceeds its threshold.
l 0x00: indicates the receive direction.

l 0x01: indicates the transmit direction.

Services are congested.
Possible Causes
l Cause 1: The configured bandwidth limit is too low.
l Cause 2: The port traffic is too high.
Procedure
Step 1 Cause 1: The configured bandwidth limit is too low.
1. Follow instructions in Configuring Traffic Shaping for Egress Queues to check the
configured bandwidth limit.
2. If the configured bandwidth limit is too low, follow instructions in Configuring Traffic
Shaping for Egress Queues to increase the bandwidth limit value or perform network
expansion.
Step 2 Cause 2: The configured port traffic is too high.

1. Follow instruction in 4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth
Utilization to query the bandwidth utilization over a port.
2. If the port bandwidth utilization is higher than its threshold, check whether a network
storm occurs. If a network storm occurs, eliminate the source that transmits a large
amount of invalid data.
----End
Related Information
None
A.3.311 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE alarm indicates that a SFP module is offline.
Attribute


Parameters
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm.
Parameter 2, Parameter 3 Have a fixed value of 0x00 0x01.
Parameter 4, Parameter 5 Are reserved and have a fixed value of 0xff.

The services over the alarmed port are interrupted.
Possible Causes
The alarmed port is enabled but house no SFP module.
Procedure
Step 1 Cause: The alarmed port is enabled but house no SFP module.
1. Check whether the alarmed port needs to receive/transmit a service.
If... Then...
The alarmed port needs to receive/ Go to the next step.
transmit a service
The alarm port does not need to Follow instructions in Setting the Basic
receive/transmit a service Attributes of Ethernet Ports to disable the
alarmed port.
2. Check whether the alarmed port houses an SFP module.
If... Then...
The alarmed port houses no SFP Follow instructions in Installing an SFP
module Module to add an SFP module.
The alarmed port houses an SFP Go to the next step.
module
3. Re-install the SFP module.
If... Then...
The alarm clears No further action is required.
The alarm persists Follow instructions in Replacing an SFP Module to replace the
SFP module.
----End
Related Information
None

A.3.312 POWER_ABNORMAL
Description
The POWER_ABNORMAL is an alarm indicating that the input power supply is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the voltage channel.
l 0x01: the first channel of voltage
l 0x02: the second channel of voltage
Parameter 2 Indicates the type of the alarm.
l 0x00: voltage loss
l 0x01: undervoltage
l 0x02: overvoltage

When the POWER_ABNORMAL alarm occurs, the power supply is abnormal, and therefore
the board may fail to work normally.
Possible Causes
l Cause 1: The power cable is cut, damaged, or incorrectly connected.
l Cause 2: The input power is abnormal.
Procedure
Step 1 Cause 1: The power cable is cut, damaged, or incorrectly connected.
1. Check whether the power cable is cut, damaged, or incorrectly connected. If the power
cable is cut or damaged, replace it with a proper power cable. If the power cable is
incorrectly connected, reconnect the power cable.
Step 2 Cause 2: The input power is abnormal.

1. Contact the engineers for power supply to rectify the fault.
----End
Related Information
None
A.3.313 POWER_ALM
Description
The POWER_ALM is an alarm indicating that the power module is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1 If the POWER_ALM alarm is reported on a board on the IDU, this parameter
indicates the ID of the alarmed power module. For example, 0x01 indicates
that the alarm is reported by power module 1 of the board.
If the POWER_ALM is reported on the ODU, this parameter indicates the type
of the power fault.
l 0x01: The -5 V power supply is faulty.
l 0x02: The power supply for the power amplifier is faulty.
Parameter 2 Indicates the alarm types.

l 0x01: under-voltage
l 0x02: over-voltage

The power modules are configured with protection. If only one power module reports the
POWER_ALM alarm, the system is not affected.
Possible Causes
If the alarm is reported by a board of the IDU, the possible causes are as follows:

l Cause 1: The input power or the PIU is abnormal.

l Cause 2: The power module is abnormal.
If the alarm is reported on the ODU, the cause is as follows:
l Cause 1: The power module of the ODU is faulty.
Procedure
Step 1 (POWER_ALM reported by a board of the IDU) Cause 1: The input power or the PIU is
abnormal.
1. Check whether alarms are reported on the PIU, If yes, clear these alarms immediately.
Step 2 (POWER_ALM reported by a board of the IDU) Cause 2: The power module is abnormal.
1. Replace the alarmed board. For details, see 6 Part Replacement.
Step 3 (POWER_ALM reported on the ODU) Cause 1: The power module of the ODU is faulty.
1. Replace the ODU. For details, see 6.15 Replacing an ODU.
----End
Related Information
None
A.3.314 PRO_PKT_FLOODING
Description
The PRO_PKT_FLOODING alarm indicates that an NE has detected a protocol packet flood
attack. This alarm is reported when the rate of a type of protocol packets is greater than the
upper threshold for consecutive 30s.
Attribute
Parameters
Name Meaning
Parameters 1 to 2 Indicate the slot ID.

Name Meaning
Parameters 3 to 4 Indicate the packet type.
l 0x00: LAG
l 0x01: IP Ping
l 0x02: ERPS
l 0x03: MSTP
l 0x04: IGMP
l 0x05: LPT
l 0x06: ARP
l 0x07: DCN
l 0x08: FIBERFIND
l 0x16: LLDP
l 0x1b: TPLB
l 0x1c: PWPING
l 0x1d: LSPTRACE
l 0x1e: LSPPING
l 0x1f: ETHOAM
l 0x20: MLPPP
Parameters 5 to 6 Indicate the upper threshold of the packet rate.

The system becomes unstable due to high CPU resource utilization. Normal protocol packets
may be lost.
Possible Causes
Cause: The rate of a type of protocol packets is greater than the upper threshold for 30
consecutive seconds.
Procedure
Step 1 Check for and handle packet attacks on the network.
----End
Related Information
None

A.3.315 PPP_LCP_FAIL
Description
The PPP_LCP_FAIL is an alarm indicating an LCP negotiation failure. This alarm is reported
when the port uses the PPP encapsulation type and fails to negotiate with the opposite port.
Attribute
Parameters
None

When this alarm occurs, the LCP negotiation fails and services are interrupted.
Possible Causes
l Cause 1: Parameter configurations on the opposite port are inconsistent with those on the
local port.
l Cause 2: The network is congested or its quality is poor, which causes improper running
of the LCP protocol.
l Cause 3: The physical link is interrupted.
Procedure
Step 1 Cause 1: Parameter configurations on the opposite port are inconsistent with those on the
local port.
1. On the NMS, check whether parameter configurations on the peer port are consistent
with those on the local port.
2. If the parameter configurations are inconsistent, modify the parameters. Then, check
3. For an optical interface, shut down and then start the laser. Then, check whether the
alarm is cleared.
Step 2 Cause 2: The network is congested or its quality is poor, which causes improper running of
the LCP protocol.
1. On the NMS, check whether the bandwidth for the tunnel connected to the ports is
configured low. For details, see Querying MPLS Tunnel Information.
2. If yes, configure the tunnel with a higher bandwidth. Then, check whether the alarm is
cleared.
Step 3 Cause 3: The physical link is interrupted.
1. Check whether the physical link is connected properly.

2. If not, restore the faulty physical link. Then, check whether the alarm is cleared.
----End
Related Information
None
A.3.316 PPP_NCP_FAIL
Description
The PPP_NCP_FAIL is an alarm indicating an NCP negotiation failure. This alarm is reported
when the NCP configuration attributes are inconsistent between the local and opposite NEs.
Attribute
Parameters
None

When this alarm occurs, the NCP negotiation fails and services are interrupted.
Possible Causes
l The NCP configurations are inconsistent between the local and opposite NEs.
Procedure
Step 1 The NCP configurations are inconsistent between the local and opposite NEs.
1. Reconfigure the NCP attributes on the local and opposite NEs and ensure they are
consistent.
----End
Related Information
None
A.3.317 PTP_SOURCE_SWITCH
Description
The PTP_SOURCE_SWITCH is an alarm indicating a switchover between PTP time sources.

Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the slot ID of the board before the switching.
Parameter 3 Indicates the ID of the subboard before the switching. 0xFF
indicates that there is no subboard.
Parameter 4, Parameter 5 Indicates the ID of the port before the switching.
Parameters 6 to 9 Indicates the ID 1 of the grandmaster clock before the
switching.
Parameters 10 to 13 Indicates the ID 2 of the grandmaster clock before the
switching.
Parameter 14, Parameter 15 Indicates the slot ID of the board after the switching.
Parameter 16 Indicates the ID of the subboard after the switching. 0xFF
indicates that there is no subboard.
Parameter 17, Parameter 18 Indicates the ID of the port after the switching.
Parameters 19 to 22 Indicates the ID 1 of the grandmaster clock after the switching.
Parameters 23 to 26 Indicates the ID 2 of the grandmaster clock after the switching.

When this alarm occurs, a switchover occurs on the IEEE 1588v2 clock source traced by the
NE, which will cause clock switchover in the entire clock domain.
Possible Causes
l Cause 1: The physical link between the local NE and the clock source is faulty.
l Cause 2: Information about the grandmaster clock such as the priority 1, quality level,
and priority 2 has changed.
l Cause 3: The network topology has changed.
Procedure
Step 1 Cause 1: The physical link between the local NE and the clock source is faulty.
1. Check the physical link between the NE and the clock source for troubleshooting.

Step 2 Cause 2: Information about the grandmaster clock such as the priority 1, quality level, and
priority 2 has changed.
1. If NE configurations are correct, no further action is required.
Step 3 Cause 3: The network topology has changed.

1. Replan the network and modify clock tracing relationships.
----End
Related Information
None
A.3.318 PTP_TIMESTAMP_ABN
Description
The PTP_TIMESTAMP_ABN is an alarm indicating an exception of the PTP timestamp. This
alarm is reported when the PTP (IEEE 1588V2) timestamp is abnormal.
Attribute

Parameters
Name Meaning
Parameter 1 l 0x02: indicates that timestamp t1 remains unchanged in three consecutive
seconds.
l 0x03: indicates that timestamp t2 remains unchanged in three consecutive
seconds.
l 0x04: indicates that timestamps t1 and t2 remain unchanged in three
Parameter 2 l 0x02: indicates that timestamp t3 remains unchanged in 17 consecutive
seconds.
l 0x03: indicates that timestamp t4 remains unchanged in 17 consecutive
seconds.
l 0x04: indicates that timestamps t3 and t4 remain unchanged in 17


When this alarm occurs, the slave NE fails to trace the time of the master NE. Bit errors may
occur in the service.
Possible Causes
l Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs.
l Cause 2: The transmit NE is faulty.
l Cause 3: The receive NE is faulty.
Procedure
Step 1 Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs.
1. Reconfigure the P/E attribute. For details, see Setting the PTP NE Attributes.
Step 2 Cause 2: The transmit NE is faulty.

1. Check the transmit NE for troubleshooting, or replace the clock source.
Step 3 Cause 3: The receive NE is faulty.

----End
Related Information
None
A.3.319 PW_APS_DEGRADED
Description
The PW_APS_DEGRADED alarm indicates that a PW automatic protection switching (APS)
protection group is degraded. This alarm is reported when a PW in the protection group is
faulty and availability of the protection group declines. This alarm is cleared when both the
working and protection PWs are functional or faulty.
Attribute
Major Service alarm
Parameters
None

Availability of the protection group declines.

Possible Causes
Cause: A PW in the protection group is faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the PWs are
incorrectly configured, rectify the configurations.
Step 2 Check whether a PWAPS_PATH_MISMATCH alarm is reported. If the alarm is reported,

handle the alarm.
----End
Related Information
None
A.3.320 PW_APS_OUTAGE
Description
The PW_APS_OUTAGE alarm indicates that a PW automatic protection switching (APS)
protection group is unavailable. This alarm is reported when both the working and protection
PWs in the protection group are faulty and the protection group is unavailable. This alarm is
cleared when a PW becomes available.
Attribute
Major Service alarm
Parameters
None

The protection group is unavailable and the services carried by the protection group are
interrupted.
Possible Causes
Cause: The working and protection PWs in the protection group are faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the PWs are
incorrectly configured, rectify the configurations.

Step 2 Check whether a PWAPS_PATH_MISMATCH alarm is reported. If the alarm is reported,

handle the alarm.
----End
Related Information
None
A.3.321 PW_DOWN
Description
The PW_DOWN alarm indicates that a PW is disconnected.
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the index number of the faulty service.
Parameter 5 to Parameter 8 Indicate the running status at the local end.
Parameter 9 to Parameter 12 Indicate the running status at the peer end.

Services are interrupted.
Possible Causes
l Cause 1: Configurations are changed at the peer end.
l Cause 2: Severe network congestion occurs.
l Cause 3: The physical link is faulty.
Procedure
Step 1 Cause 1: Configurations are changed at the peer end.
1. Check whether PW configurations are consistent at both ends. If the configurations are
inconsistent, rectify the configurations.

Step 2 Cause 2: Severe network congestion occurs.

1. Check the bandwidth utilization of the tunnel. If the bandwidth is exhausted, allocate
more bandwidth resources to the tunnel or eliminate any source that unexpectedly
transmits a large amount of data.
Step 3 Cause 3: The physical link is faulty.

1. Check whether any fiber or cable is broken, damaged, or pressed. If any of the preceding
problems exist, replace the faulty fiber or cable.

1. If the peer NE is faulty, rectify the fault.
----End
Related Information
None
A.3.322 PW_DROPPKT_EXC
Description
The PW_DROPPKT_EXC alarm indicates that the packet loss ratio on a PW exceeds its
threshold.
Attribute
Warning Processing alarm
Parameters
Parameters
Name Meaning
Parameter 1 Has a fixed value of 0x00, indicating that the traffic in the ingress or egress
direction crosses its threshold.

A small number of packets are lost, affecting service real-time performance.

Possible Causes
Cause: A small number of packets are lost on the alarmed PW.
Procedure
Step 1 Cause: A small number of packets are lost on the alarmed PW.
1. Follow instructions in Querying Information and Running Status of PWs to check the
bandwidth utilization of the alarmed PW. If the PW bandwidth is exhausted, increase the
bandwidth or eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None
A.3.323 PW_NO_TRAFFIC
Description
The PW_NO_TRAFFIC is an alarm indicating that a PW has no traffic. This alarm is reported
when the PW that carries services has no traffic.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the direction in which traffic is unavailable.

l 0x00: RX direction
l 0x01: TX direction

When this alarm occurs, the PW has no traffic and PW services are interrupted.
Possible Causes
l Cause 1: No service is configured.

l Cause 2: The local services are abnormal and therefore no packet is transmitted to the
peer end.
l Cause 3: The peer services are abnormal and therefore no packet is transmitted to the
local end.
l Cause 4: The port that corresponds to the faulty PW works improperly.
Procedure
Step 1 Determine the alarmed board, and direction in which traffic is unavailable according to the
alarm information on the NMS.
If... Then...
The PW_NO_TRAFFIC alarm is reported in both the receive and Go to Step 2.

transmit directions
0x00 Go to Step 4.
0x01 Go to Step 3.
Step 2 Cause 1: No service is configured.

1. Check whether the port is configured with any services. If not, configure services
correctly.
Step 3 Cause 2: The local services are abnormal and therefore no packet is transmitted to the peer
end.
1. Check whether the local PW services are correctly configured. For details, see Querying
Information and Running Status of PWs.
Step 4 Cause 3: The peer services are abnormal and therefore no packet is transmitted to the local
end.
1. Check whether the opposite PW services are correctly configured.
Step 5 Cause 4: The port that corresponds to the faulty PW works improperly.
1. Replace the board that reports the alarm on the local NE. For details, see 6 Part
Replacement.
2. Check whether the alarm is cleared. If the alarm persists, replace the corresponding
board of the opposite NE.
----End
Related Information
None
A.3.324 PWAPS_LOST
Description
The PWAPS_LOST is an alarm indicating that the APS frame is lost. This alarm occurs when
no APS frame is received from the protection channel.

Attribute
Parameters
None

When this alarm occurs, the service protection fails.
Possible Causes
l Cause 1: The remote NE of the PW is not configured with any protection group.
l Cause 2: The service on the protection channel is interrupted.
Procedure
Step 1 Cause 1: The remote NE of the PW is not configured with any protection group.
1. Check whether the remote NE of the PW is configured with a protection group. If yes,
ensure that the configuration is the same at the two ends.
Step 2 Cause 2: The service on the protection channel is interrupted.

1. Check whether the protection channel is faulty. If yes, rectify the fault.
----End
Related Information
None
A.3.325 PWAPS_PATH_MISMATCH
Description
The PWAPS_PATH_MISMATCH is an alarm indicating that the working and protection paths
of the APS protection group differ between the two ends. This alarm is reported when the
working and protection paths of one APS protection group at one end are different from those
at the other end.
Attribute

Parameters
None

Possible Causes
l Cause 2: Certain physical links are incorrectly connected.
Procedure
1. Check whether the APS settings at the two ends are the same.
2. If the APS settings are different, change the settings to the same.
Step 2 Cause 2: Certain physical links are incorrectly connected.

1. Connect the fibers or cables properly.
----End
Related Information
None
A.3.326 PWAPS_SWITCH_FAIL
Description
The PWAPS_SWITCH_FAIL is an alarm indicating a switching failure of the PW APS
protection group. This alarm is reported when the request signal in the transmitted Automatic
Protection Switching (APS) frame is different from the bridge signal in the received APS
frame and this symptom lasts for 50 ms.
Attribute
Parameters
None


Possible Causes
l Cause 2: Certain physical links are incorrectly connected.
Procedure
1. Check whether the APS settings at the two ends are the same.
2. If the APS settings are different, change the settings to the same.
Step 2 Cause 2: Certain physical links are incorrectly connected.
1. Connect the fibers or cables properly.
----End
Related Information
None
A.3.327 PWAPS_TYPE_MISMATCH
Description
The PWAPS_TYPE_MISMATCH is an alarm indicating that the local NE and the opposite
NE are configured with different PW protection types. This alarm occurs when the
information in the received APS frames is inconsistent with the APS protection scheme
configured at the local end.
Attribute
Parameters
None

Possible Causes
l Cause 1: The configured protection modes (1+1 protection or 1:1 protection) differ at the
two ends of the PW.
l Cause 2: The configured switching modes (single-ended or dual-ended) differ at the two
ends of the PW.
l Cause 3: The configured revertive modes (revertive or non-revertive) differ at the two
ends of the PW.

Procedure
Step 1 Check whether the APS protection settings, such as protection mode, switching mode, and
revertive mode, are the same at the local and remote ends. For details, see Querying PW APS
Status.
Step 2 If the APS protection settings are different, change the settings to the same.
----End
Related Information
None
A.3.328 PWD_ENCRYPT_RISK
Description
The PWD_ENCRYPT_RISK alarm indicates that the user password encryption mode of an
NE has security risks.
Attribute
Parameters
None

The user password may be cracked, and the system has security risks.
Possible Causes
Cause: The user password encryption mode of the NE is MD5 or SHA256.
Procedure
Step 1 In the NE Explorer, click the NE and choose Security > NE User Password Encryption
Management. Change Encryption Type to PBKDF2.
----End
Related Information
None

A.3.329 R_LOC
Description
The R_LOC is an alarm indicating that the clock is lost on the receive line side. This alarm is
reported when the line board fails to extract clock signal from the line signal or the IF board
fails to extract clock signal from the IF signal.
Attribute
Parameters
None

The services on the line port or the IF port are interrupted. If the system is configured with
protection, protection switching may be triggered.
Possible Causes
Procedure
1. At the local end, perform an inloop on the port of the alarmed board. For details, see 8.4
Software Loopback.
If... Then...
The alarm persists after the loopback Replace the alarmed opposite board.
The alarm is cleared after the loopback Go to Cause 2.

1. Replace alarmed opposite board.
If... Then...
The alarm is cleared after the board The fault is rectified. End the alarm handling.
is replaced
The alarm persists after the board is Replace the system control, switch&timing
replaced board at the opposite end.
----End

Related Information
None
A.3.330 R_LOF
Description
The R_LOF is an alarm indicating that frames are lost on the receive side. This alarm is
reported when the OOF state lasts for three milliseconds.
Attribute

Parameters
None

The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
l Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).
interface board).
Procedure
Step 1 Cause 1: Certain high-level alarms are generated (if the alarm is reported by an IF board).
1. If the alarm is reported by the IF board, check whether the MW_BER_EXC,
MW_BER_SD, MW_FEC_UNCOR alarm is generated.
If... Then...
The alarm is generated Take priority to clear the

MW_BER_EXC, MW_BER_SD,
MW_FEC_UNCOR alarm.
The alarm is not generated Go to the next step.
2. Set the inloop on the alarmed IF port.

If... Then...
The alarm persists after the inloop is Go to Cause 4.

performed
The alarm is cleared after the inloop is Go to Cause 3.

performed
board).
1. If the alarm is reported by an optical interface board, exchange the transmit and receive
fiber jumpers at both ends.
If... Then...
The alarm persists after the exchange Go to Cause 3 or 4
The line port of the opposite station Troubleshoot the optical fibers.
reports the R_LOF alarm

1. Replace the opposite board where the line unit is or the opposite IF board.
If... Then...
The alarm is cleared after the board The fault is rectified, and the alarm
replacement handling is complete.
The alarm persists after the board Go to the next step.

replacement
2. Replace the system control and cross-connect board at the opposite end.
If... Then...
The alarm is cleared after the board The fault is rectified, and the alarm
replacement handling is complete.
The alarm persists after the board Go to Cause 4.

replacement

----End
Related Information

A.3.331 R_LOS
Description
For IF boards, the R_LOS alarm indicates that microwave frames are lost on the receive line
side. For SDH line boards, the R_LOS alarm indicates that signals are lost on the receive line
side. For TDM cascading interface boards, the R_LOS alarm indicates that cascading signals
are lost on the receive line side.
Attribute
Parameters
None

If no protection scheme is configured, services on the board that reports the alarm are
interrupted. If a protection scheme is configured, a protection switchover is triggered.
Possible Causes
l Cause 1: Other alarms trigger the R_LOS alarm (if the R_LOS alarm is reported by an IF
board).
l Cause 2: The line performance deteriorates (if the R_LOS alarm is reported by an SDH
line board).
l Cause 3: The TDM cascade cable connection is abnormal (if the R_LOS alarm is
reported by a TDM cascading interface board).
l Cause 4: The transmit unit of the peer NE is faulty.
l Cause 6: No fiber jumper is connected to the optical port on the board that reports the
R_LOS alarm.
l Cause 7: The laser on the peer NE is closed.
l Cause 8: A fiber cut occurs on the transmission line.
l Cause 9. The optical loss is beyond the normal range.
Procedure
Step 1 Cause 1: Other alarms trigger the R_LOS alarm (if the R_LOS alarm is reported by an IF
board).
1. If the R_LOS alarm is reported by an IF board, check for and clear any
MW_BER_EXC, MW_BER_SD, and MW_FEC_UNCOR alarms on the IF board. If
no such alarm exists, go to the next step.
2. Set an inloop on the IF port that reports the R_LOS alarm.

3. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 2 Cause 2: The line performance deteriorates (if the R_LOS alarm is reported by an SDH line
board).
1. If the R_LOS alarm is reported by an SDH line board, exchange the transmit and receive
fiber jumpers at both ends.
2. If the peer line port reports an R_LOF alarm after fiber jumpers are exchanged, go to
Cause 8.
Step 3 Cause 3: The TDM cascade cable connection is abnormal (if the R_LOS alarm is reported by
a TDM cascading interface board).
1. If the R_LOS alarm is reported by a TDM cascading interface board, check whether the
TDM cascade cable is properly connected and functional. If the cable is not properly
connected, connect it properly. If the cable is faulty, replace it.
Step 4 Cause 4: The transmit unit of the peer NE is faulty.
1. Replace the board where the peer line unit is located or the peer IF board.
2. Replace the system control, switching, and timing board on the peer NE.
1. Replace the board that reports the R_LOS alarm.
Step 6 Cause 6: No fiber jumper is connected to the optical port on the board that reports the R_LOS
alarm.
1. Check fiber connections and ensure that fiber jumpers are properly connected.
Step 7 Cause 7: The laser on the peer NE is closed.
1. Turn on the laser on the peer NE.
Step 8 Cause 8: A fiber cut occurs on the transmission line.
1. Test the transmission line connectivity, identify the cause of fiber cuts, and re-connect or
replace related optical fibers.
Step 9 Cause 9. The optical loss is beyond the normal range.
1. Check whether there are any blocks in the microwave transmission path or in the near
field of the antenna. If there are any blocks in the microwave transmission path or in the

near field of the antenna, adjust the mounting height of the antenna to ensure good line
of sight (LOS) or re-plan the microwave link route.
2. Verify that the optical power of the optical module at the transmit end matches that of the
optical module at the receive end.
3. Check whether loss increases because the antenna, hybrid coupler, or flexible waveguide
is damaged or wet. If loss increases because any of the preceding components are
damaged or wet, replace the faulty components.
4. If the R_LOS alarm persists, contact Huawei technical support engineers to handle the
alarm.
----End
Related Information
The handling procedure also applies when the R_LOS alarm is reported by an STM-1e port.
A.3.332 R_OOF
Description
The R_OOF is an alarm indicating an out-of-frame event on the receive side of the line.
Attribute
Parameters
None

l When this alarm occurs, services are interrupted, and the AIS signal is inserted on the
downstream NE.
l When this alarm occurs, the system automatically returns the MS_RDI message to the
upstream NE. Then, the upstream NE reports the MS_RDI alarm.
Possible Causes
l Cause 1: The transmit cable is faulty, and the fiber connector is loose or contaminated.
l Cause 2: The receive board on the local NE is faulty.
l Cause 3: The transmit board on the opposite NE is faulty.
Procedure
Step 1 Cause 1: The transmit cable is faulty, and the fiber connector is loose or contaminated.
1. Check whether the transmit optical power of the board connected to the board that
reports the alarm is within the normal range.

If... Then...
The transmit optical power of the opposite board is abnormal Go to Step 3.
The transmit optical power of the opposite board is normal Go to the next step.
2. On the NMS, check whether the receive optical power of the local board is within the
normal range.
If... Then...
The receive optical power of the local board is too low Go to the next step.
The receive optical power of the local board is too high Go to Step 2.
3. Check whether the bend radius of the fiber jumper is within the normal range. If the bend
radius is less than 6 cm, re-roll the tail fiber. Check whether the alarm is cleared.
4. If the alarm persists, check whether the optical interface on the board is firmly connected
to the fiber jumper. Ensure that the fiber connector is firmly connected. Then, check
whether the R_LOS alarm is cleared.
5. If the alarm persists, check whether the fiber connector is contaminated. If yes, clean the
fiber and fiber connector. For details, see 8.12 Cleaning Fiber Connectors and
Adapters.
6. Check whether the optical cable is aged out, damaged, or pressed. If yes, replace the
optical cable.
Step 2 Cause 2: The receive board on the local NE is faulty.

1. Perform a hardware inloop for the transmit and receive interfaces of the port that reports
the alarm on the local NE. For details, see 8.5 Hardware Loopback.
NOTICE
A loopback causes service interruption. To prevent optical power overload during
hardware inloop, you can add an optical attenuator to the optical interface according to
the optical power specifications of the board.
If... Then...
The alarm persists The local board is faulty. Go to the next step.
The alarm is cleared Go to Step 3.
2. Replace the board that reports the R_OOF alarm on the local NE. If the board supports
the pluggable optical module, replace the pluggable optical module. For details, see 6.14
Replacing the SFP. Otherwise, replace the faulty board. For details, see 6.4 Replacing
the Channelized STM-1 Processing Board.
Step 3 Cause 3: The transmit board on the opposite NE is faulty.

1. Rectify the fault on the opposite board.
----End
Related Information
None
A.3.333 RADIO_FADING_MARGIN_INSUFF
Description
The RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean receive
power of the ODU is lower than the threshold of the receive power (the threshold value is
about the receiver sensitivity + 14 dB).
When the receive power of the ODU in consecutive six hours is lower than the threshold, the
system reports the alarm. When the mean receive power of the ODU becomes normal and
lasts for three minutes after the alarm is reported, the alarm is cleared.
Attribute

Parameters
None

If the MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is not
generated, the service is not affected.
Possible Causes
l Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.
l Cause 2: The direction of the antenna is deflected.
l Cause 3: The transmission environment changes.
l Cause 4: The fade margin in the case of rain and fog in the network planning is
insufficient.
Procedure
Step 1 Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.
1. Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.

If... Then...
The ODU at the transmit end reports the Handle the RADIO_TSL_LOW
RADIO_TSL_LOW alarm alarm.
The ODU at the transmit end does not report the Go to Cause 2.
RADIO_TSL_LOW alarm
Step 2 Cause 2: The direction of the antenna is deflected.

1. Check whether the direction of the antenna is deflected.
If... Then...
The direction of the antenna is deflected Adjust the direction of the antenna.
The direction of the antenna is not deflected Go to Cause 3.
Step 3 Cause 3: The transmission environment changes.

1. Check whether the transmission environment changes. For example, check whether any
building blocks the transmission and increases the link fading significantly.
If... Then...
The transmission environment Contact the network planning department for re-
changes planning the transmission trail.
The transmission environment does Go to Cause 4.
not change
Step 4 Cause 4: The fade margin in the case of rain and fog in the network planning is insufficient.
1. If the alarm is reported frequently, contact the network planning department to increase
the fade margin by re-planning the transmission trail.
----End
Related Information
None
A.3.334 RADIO_MUTE
Description
The RADIO_MUTE is an alarm indicating that radio transmitter is muted.
Attribute
Warning Equipment alarm
Parameters
None


The transmitter does not transmit services.
Possible Causes
l Cause 1: The other alarms are generated.
l Cause 2: The transmitter of the local site is muted manually.
l Cause 3: The IF board is faulty, causing abnormal IF output.
l Cause 4: The data output is abnormal because the ODU is faulty.
Procedure
Step 1 Cause 1: The other alarms are generated.
1. Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated.
If yes, take priority to clear the alarm.
Step 2 Cause 2: The transmitter of the local site is muted manually.

1. Check whether the transmitter of the ODU is muted. For details, see Configuring a
Single-Hop Radio Link. If yes, cancel the muting operation. Then, set the transmitting
status of the ODU to unmute.
Step 3 Cause 3: The IF board is faulty, causing abnormal IF output.

1. Replace the IF board.
Step 4 Cause 4: The data output is abnormal because the ODU is faulty.
1. Replace the ODU.
----End
Related Information
None
A.3.335 RADIO_RSL_BEYONDTH
Description
The RADIO_RSL_BEYONDTH is an alarm indicating that the antennas are not aligned.
When the receive power is set on the NE, the NE enables the antenna alignment indication
function. If the actual receive power of the ODU is lower than the power to be received 3 dB,
the RADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are aligned for
continuous 30 minutes, the antenna alignment indication function is disabled automatically.
Afterwards, the RADIO_RSL_BEYONDTH alarm is reported only when the
RADIO_FADING_MARGIN_INSUFF alarm is reported.
Attribute

Parameters
None

If the MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is not
generated, the service is not affected.
Possible Causes
l Cause 1: Antennas are not aligned during the equipment commissioning.
l Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is
running.
Procedure
Step 1 Cause 1: Antennas are not aligned during the equipment commissioning.
1. Align the antennas, and ensure that the actual receive power is within the range of preset
receive power +/-3 dB.
Step 2 Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.

1. Handle the RADIO_FADING_MARGIN_INSUFF alarm. When the
RADIO_FADING_MARGIN_INSUFF alarm is cleared, the
RADIO_RSL_BEYONDTH alarm is cleared.
----End
Related Information
None
A.3.336 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is very high.
This alarm is reported if the detected receive power is equal to or higher than the upper
threshold of the ODU (-20 dBm).
Attribute

Parameters
None


The service transmission is affected. If the system is configured with 1+1 protection,
Possible Causes
l Cause 1: The local ODU is faulty.
l Cause 2: There is a strong interference source nearby.
l Cause 3: The transmit power of the opposite ODU is very high.
Procedure
Step 1 Cause 1: The local ODU is faulty.
1. 6.15 Replacing an ODU.
Step 2 Cause 2: There is a strong interference source nearby.

1. Check whether any nearby signal source transmits signals whose frequency is close to
the specified range. If yes, check whether the signal source can be shut down or
removed. If not, contact the network planning department for replanning the frequency.
Step 3 Cause 3: The transmit power of the opposite ODU is very high
1. Reset the transmit power of the ODU at the opposite end. For details, see Configuring a
Single-Hop Radio Link.
----End
Related Information
None
A.3.337 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW is an alarm indicating that the radio receive power is very low. This
alarm is reported if the detected receive power is equal to or lower than the upper threshold of
the ODU (The upper threshold is –80 dBm for the 112 MHz channel bandwidth and –90
dBm for the other channel bandwidths).
Attribute

Parameters
None


If no MW_BER_EXC, MW_BER_SD, MW_LOF or MW_FEC_UNCOR alarm is
generated, the services are not affected.
Possible Causes
l Cause 1: Other alarms occur at the opposite station.
l Cause 2: The transmit power of the opposite station is very low.
l Cause 3: The local ODU is faulty.
Procedure
Step 1 Cause 1: Other alarms occur at the opposite station.
Check whether any of the following alarms is generated in the equipment of the opposite
station. If yes, take priority to clear the alarm.
l RADIO_MUTE
l CONFIG_NOSUPPORT
l RADIO_TSL_LOW
l BD_STATUS
Step 2 Cause 2: The transmit power of the opposite station is very low.
1. See Configuring a Single-Hop Radio Link. Check whether the transmit power of the
opposite station is normal. If not, replace the ODU of the opposite station.
1. Replace the ODU at the local end.
1. Browse history alarms and check whether the alarm is generated continuously.
If the alarm is generated occasionally, contact the network planning department to
change the design to increase the anti-fading performance.
2. Check whether the antennas at both ends are adjusted properly.
If not, align the antennas again.
3. Check whether any mountain or building obstacle exists in the transmit direction.
If yes, contact the network planning department for proper modification of the planning
design, hence preventing the block of the mountain or building obstacle.
4. Check whether the polarization direction of the antenna, ODU, and hybrid coupler is set
correctly.
If not, correct the polarization direction.
5. Check whether the outdoor units such as antennas, hybrid coupler, ODU, and flexible
waveguide are wet, damp, or damaged.
If yes, replace the unit that is wet, damp, or damaged. For the operations, see 6 Part
Replacement
6. Check whether the antenna gain at both the transmit and receive ends meets the
requirement.

If not, replace the antenna.
----End
Related Information
None
A.3.338 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. This
alarm is reported when the detected transmit power is higher than the upper power threshold
of the ODU.
Attribute

Parameters
None

Possible Causes
Cause 1: The local ODU is faulty.
Procedure
1. Replace the ODU.
----End
Related Information
None

A.3.339 RADIO_TSL_LOW
Description
The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is very low. This
alarm is reported when the detected transmit power is less than the lower power threshold of
the ODU.
Attribute
Parameters
None

Possible Causes
Cause 1: The local ODU is faulty.
Procedure
1. Replace the ODU.
----End
Related Information
None
A.3.340 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is an alarm indicating the critical alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to critical and there is such
an alarm input.
Attribute

Parameters
None

When the RELAY_ALARM_CRITICAL alarm occurs, it does not affect the operation of the
board or the services on the NE.
Possible Causes
Cause 1: There is a critical alarm input.
Procedure
Step 1 Cause 1: There is a critical alarm input.
1. Clear the alarms of the external equipment according to the defined meanings of the
alarms. Then, the RELAY_ALARM_CRITICAL alarm is cleared.
----End
Related Information
None
A.3.341 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is an alarm indicating the warning alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to warning and there is such
an alarm input.
Attribute
Parameters
None

When the RELAY_ALARM_IGNORE alarm occurs, it does not affect the operation of the
board or the services on the NE.
Possible Causes
Cause 1: There is a warning alarm input.

Procedure
Step 1 Cause 1: There is a warning alarm input.
alarms. Then, the RELAY_ALARM_IGNORE alarm is cleared.
----End
Related Information
None
A.3.342 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is an alarm indicating the major alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to major and there is such an
alarm input.
Attribute
Parameters
None

When the RELAY_ALARM_MAJOR alarm occurs, it does not affect the operation of the
board or or the services on the NE.
Possible Causes
Cause 1: There is a major alarm input.
Procedure
Step 1 Cause 1: There is a major alarm input.
alarms. Then, the RELAY_ALARM_MAJOR alarm is cleared.
----End
Related Information
None

A.3.343 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is an alarm indicating the minor alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to minor and there is such
an alarm input.
Attribute
Parameters
None

When the RELAY_ALARM_MINOR alarm occurs, it does not affect the operation of the
board or or the services on the NE.
Possible Causes
Cause 1: There is a minor alarm input.
Procedure
Step 1 Cause 1: There is a minor alarm input.
alarms. Then, the RELAY_ALARM_MINOR alarm is cleared.
----End
Related Information
None
A.3.344 REMOTE_FAULT
Description
The REMOTE_FAULT alarm indicates that a fault occurs at a remote Ethernet port.
Attribute

Parameters
None

If a 10GE optical port reports a REMOTE_FAULT alarm, services in the receive direction
may be interrupted.
Possible Causes
Possible causes of the REMOTE_FAULT alarm are as follows:
l Cause 1: The peer NE reports a LOCAL_FAULT alarm.
l Cause 2: The peer board is faulty.
Procedure
Step 1 Cause 1: The peer NE reports a LOCAL_FAULT alarm.
1. Check whether the peer NE reports a LOCAL_FAULT alarm on the U2000. If the peer
NE reports a LOCAL_FAULT alarm, clear the LOCAL_FAULT alarm by following
instructions in A.3.182 LOCAL_FAULT. If the peer NE does not report a
LOCAL_FAULT alarm, go to Step 2.
Step 2 Cause 2: The peer board is faulty.
1. Replace the peer board by following instructions in the Part Replacement.
2. Check whether the REMOTE_FAULT alarm is cleared. If the alarm persists, contact
----End
Related Information
None
A.3.345 RMFA
Description
The RMFA is an alarm indicating the loss of multiframe alignment at the remote end. This
alarm occurs when the local end detects all 1s of the remote indication bits in Z consecutive
CAS multiframes (Z = 1-5) of the framed E1/T1 input.
Attribute
Parameters


Name Meaning
0x01.
Parameter 2, Parameter 3 Indicate the path ID.

When this alarm occurs, the services at the local site are not affected. The alarm indicates that
the LMFA alarm occurs at the opposite end.
Possible Causes
The LMFA alarm occurs at the opposite end.
Procedure
Step 1 Check whether the opposite end of the alarmed path reports the LMFA alarm. If yes, clear the
LMFA alarm. Then, the RMFA alarm at the local end clears.
----End
Related Information
None
A.3.346 RPS_INDI
Description
The RPS_INDI is an alarm indicating that the radio protection switching is detected.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the protection group.

Name Meaning
Parameter 2 Indicates the type of protection switching.
0x01: HSB protection switching

During the protection switching, services are interrupted. After the switching is complete, the
services are restored to normal.
Possible Causes
l The possible causes of the HSB protection switching are as follows:
– Cause 1: An external switching event occurs
– Cause 2: An automatic switching event occurs.
– Cause 3: A reverse switching event occurs.
Procedure
Step 1 Determine the type of the protection switching based on the alarm parameters.
Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, the NMS issues a
command to trigger the switching.
1. Check whether the switching is the forced switching or manual switching. For details,
see Querying the IF 1+1 Protection Status.
If... Then...
The switching is the forced switching or Find the cause and release the switching
manual switching immediately.
The switching is not the forced switching Go to Cause 2 of HSB switching.
or manual switching
Step 3 Cause 2 of HSB switching: An automatic switching event occurs. That is, the equipment is
faulty, or the service is defective.
1. Check whether the following faults or alarms occur. If yes, rectify the faults or clear the
alarms.
– The hardware of the IF board or the ODU is faulty.
– VOLT_LOS
– RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH
– IF_INPWR_ABN or CONFIG_NOSUPPORT
– R_LOC, R_LOF, R_LOS, or MW_LOF
– BUS_ERR

NOTE
– If the switching is non-revertive, the services are not automatically switched to the working
path when the working path is restored to normal, and the RPS_INDI alarm persists. In this
case, you need to manually switch the services from the protection path to the working path.
The RPS_INDI alarm is cleared only when the switching is successful.
– If the switching is revertive, the services are automatically switched to the working path only
when the specified wait-to-restore (WTR) time expires after the working path is restored to
normal. The RPS_INDI alarm is cleared only when the switching is successful.
Step 4 Cause 3 of HSB switching: A reverse switching event occurs.

1. Query whether the active and standby IF boards report the MW_RDI alarm. If yes, take
priority to clear the MW_RDI alarm.
----End
Related Information
None
A.3.347 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that a regenerator section performance indicator
crosses the threshold. This alarm is reported if a board detects that a regenerator section bit
error performance event crosses the preset threshold.
Attribute
Minor Service alarm
Parameters
Name Meaning
l 0x01: 15 minutes
l 0x02: 24 hours

Name Meaning
Parameter 2, Parameter 2 is always 0x00. Parameter 3 indicate the ID of a
Parameter 3 performance event that causes the alarm and has the following
meanings:
l 0x01: RSBBE
l 0x02: RSES
l 0x03: RSSES
l 0x04: RSOOF
l 0x05: RSOFS
l 0x06: RSUAS

A large number of bit errors occur in the services, and the services may be interrupted.
Possible Causes
l Cause 1: Services are interrupted for a long time.
l Cause 2: The regenerator section bit error performance indicator crosses the preset
threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
NOTE
Handle the alarm as follows if the value of parameter 3 is 0x06:
1. Check whether fibers are properly connected. If not, connect the fibers again according
to planning information.
2. Check whether cross-connections are configured for service ports. If not, configure
cross-connections again according to planning information.
Step 2 Cause 2: The regenerator section bit error performance indicator crosses the preset threshold.
1. Find out the performance event that crosses the preset threshold. For details, see 4.3.5
Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None
A.3.348 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the real-time clock (RTC) on the system control
board fails.

Attribute
Parameters
None

The service is not affected.
Possible Causes
l Cause 1: The RTC on the system control board is abnormal.
l Cause 2: The board temperature is too high.
Procedure
Step 1 Cause 1: The RTC on the system control board is abnormal.
Step 2 Cause 2: The board temperature is too high.
1. 4.3.1 Browsing Current Alarms, and if theboard reports the TEMP_ALARM alarm,
clear this alarm first.
----End
Related Information
None
A.3.349 RT_TBL_LACK
Description
The RT_TBL_LACK alarm indicates that routing table resources are insufficient.
Attribute
Parameters


Name Meaning
Parameters 1-4 Indicate the IP address.
Parameters 5-8 Indicate the mask of the IP address.

Routes fail to be added into the routing table, and the associated services are unavailable.
Possible Causes
The number of routes or next hops in the routing table exceeds the maximum number
allowed.
Procedure
Step 1 Reduce service routes by re-planning services.
----End
Related Information
None
A.3.350 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 byte
mode.
Attribute

Parameters

Name Meaning
Parameter 1 0x01: system priority list
0x02: external clock priority list

If the new clock source has a lower quality, pointer justifications and bit errors are generated
after the switching of clock source. As a result, the quality of services is affected.
Possible Causes
When the SSM protocol or extended SSM protocol is enabled.
l Cause 1: The original clock source is lost.
l Cause 2: The fiber is cut off.
l Cause 3: The external BITS is interrupted.
l Cause 4: The S1_SYN_CHANGE alarm occurs at the upstream station.
Procedure
Step 1 Cause 1: The original clock source is lost.
1. Handle the SYNC_C_LOS alarm that is related to the original clock source.
Step 2 Cause 2: The fiber is cut off.
1. Replace the faulty fiber.
Step 3 Cause 3: The external BITS is interrupted.
1. Check whether the cable connect NE to BITS is normal. If not, replace the faulty cable.
Step 4 Cause 4: The S1_SYN_CHANGE alarm reported at the upstream station.
1. Handle the S1_SYN_CHANGE alarm reported at the upstream station.
----End
Related Information
None
A.3.351 SYNC_FAIL
Description
The SYNC_FAIL alarm indicates that the batch backup on SCC boards fails.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the cause of the failure.
l 0x1F: The database backup fails.

l 0x20: Software version verification fails on the main and standby SCC
boards.
l 0x21: Communication between the main and standby SCC boards fails.
l 0x22: The main and standby SCC boards have different data after an
upgrade.
l 0x23: Forced switching occurs between the main and standby SCC boards
before database backup is completed.
Parameter 2 Always 0xff
Parameter 3 Always 0xff

Data synchronization between the main and standby SCC boards fails, and the switching
between the two boards is unavailable.
Possible Causes
l Cause 1: The main and standby SCC boards have different versions of software.
l Cause 2: Databases on the main and standby SCC boards are damaged.
l Cause 3: The main and standby SCC boards have different data after an upgrade.
l Cause 4: Communication between the main and standby SCC boards fails.
l Cause 5: Forced switching occurs between the main and standby SCC boards before
database backup is completed.
Procedure
Step 1 Cause 1: The main and standby SCC boards have different versions of software.
1. Query and record the software versions of the main and standby SCC boards according
to 4.8.4 Querying the Board Information Report.
2. If the software versions are different, determine the correct version based on the version
mapping table and replace the SCC board with an incorrect version. For details, see 6.10
Replacing the System Control, Switching and Timing Board.
Step 2 Cause 2: Databases on the main and standby SCC boards are damaged.
1. Check whether the system reports the DBMS_ERROR alarm. For details, see 4.3.1
Browsing Current Alarms.

2. If yes, clear the DBMS_ERROR alarm. Then, check whether the SYNC_FAIL alarm is
cleared.
Step 3 Cause 3: The main and standby SCC boards have different data after an upgrade.
1. Re-install the standby SCC board.
Step 4 Cause 4: Communication between the main and standby SCC boards fails.
1. Check whether the system reports the COMMUN_FAIL alarm.
2. If yes, clear the COMMUN_FAIL alarm. The system will start batch backup
automatically.
Step 5 Cause 5: Forced switching occurs between the main and standby SCC boards before database
backup is completed.
1. Warm reset the alarmed board by following instructions in 8.6.2 Warm Reset.
----End
Related Information
None
A.3.352 SEC_RADIUS_FAIL
Description
The SEC_RADIUS_FAIL is an alarm indicating that RADIUS authentication fails over many
times. This alarm is reported when the RADIUS authentication fails for five consecutive
times.
Attribute

Parameters
Name Meaning
Parameter 1 to Parameter 16 Indicates the username.

A user cannot log in to an NE.

Possible Causes
l Cause 1: The active period of the account expires.
l Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and
access policies.
l Cause 3: There are unauthenticated login attempts.
l Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.
Procedure
Step 1 Cause 1: The active period of the account expires.
1. Use an active account.
Step 2 Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and access
policies.
1. Enter the correct password.
2. Set correct access policies.
Step 3 Cause 3: There are unauthenticated login attempts.

1. Eliminate the source that initiates the unauthenticated login attempts.
Step 4 Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.
1. Set the shared key correctly.
----End
Related Information
None
A.3.353 SECU_ALM
Description
The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.
Attribute
Parameters

Name Meaning
Parameter 1 Indicates the terminal type used in the login attempt.
Parameters 2 and 3 Indicate the errors that occur in the login attempt.
Parameters 4 and 5 Indicate the first two characters of the user name.

The SECU_ALM alarm is ended soon after it is reported, and the alarm does not affect the
system and services.
Possible Causes
An illegal user tries to log in to the NE.
Procedure
Step 1 An illegal user tries to log in to the NE.
1. Query the NE log to check the user name that is used for the login.
----End
Related Information
After a user fails to log in to an NE for five consecutive times (if the interval between two
logins is less than 3 minutes, the two logins are consecutive logins), the SECU_ALM alarm is
reported upon each subsequent login failure and meanwhile the user is locked for 900
seconds. During the 900 seconds, the user cannot log in to the NE.
A.3.354 SLAVE_BAD
Description
The SLAVE_BAD alarm indicates that the connection between the alarmed board and the
standby system control and timing board fails.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the fault type on the standby system control and timing board.
l 0x00: The cross-connect bus is faulty.
l 0x01: The standby clock unit is faulty.
l 0x02: The standby system control unit is faulty.
l 0x03: The service bus is faulty
Parameters 2
Indicates the slot ID of the standby system control and timing board.
and 3
Parameter 4 This parameter is valid only when the value of parameter 1 is 0x01. This
parameter indicates the cause of the fault.
l 0x01: The slave 38M system clock is lost.
l 0x02: The slave TOP 38M clock is lost.
l 0x03: The slave clock 8 is abnormal.
l 0x04: The slave 1588v2 header is lost.
If the value of parameter 1 is 0x03, the service bus of the standby system
control and clock board is faulty.
l 0x01: The SMB bus is faulty.
l 0x02: The Telecom bus is faulty.
l 0x03: The overhead is abnormal.
l 0x04: The service board status read by the active system control board is
online, and the service board status read by the standby system control
board is offline.
l 0x05: The IIC bus is faulty.
l 0x06: The telecom/lvds bus between the active system control board and
service boards is faulty, or the serdes bus between the active and standby
integrated SL4D boards is faulty.

When this alarm occurs, the active system control and timing board works in unprotected
mode.
Possible Causes
l Cause 1: The standby system control and timing board is faulty.
l Cause 3: The chassis is faulty.
Procedure
Step 1 Cause 1: The standby system control and timing board is faulty.

1. Replace the standby system control and timing board according to Replacing a System
Control, Switching, and Timing Board.
1. Replace the board that reports the alarm according to Replacing an IF Board.
Step 3 Cause 3: The chassis is faulty.
1. Power off the IDU.
2. Record positions of boards in the chassis. Disconnect cables from the boards and remove
the boards by following instructions in Removing a Board.
3. Replace the chassis. Install boards in proper slots according to the record by following
instructions in Installing a Board and connect cables to the boards.
4. Power on the IDU.
----End
Related Information
None
A.3.355 SOFTWARE_UNCOMMIT
Description
The SOFTWARE_UNCOMMIT alarm indicates that the board software is unauthorized. This
alarm is reported when the software version of a board is later than that of the system control
board and is unauthorized.
Attribute
Parameters
None

The board runs improperly.
Possible Causes
Cause 1: The board software is unauthorized.
Procedure
Step 1 Load the software license to the board.
----End

Related Information
None
A.3.356 SRV_SHUTDOWN_LD
Description
The SRV_SHUTDOWN_LD alarm indicates that an Ethernet service is deactivated. This
alarm is reported when an Ethernet service is deactivated due to a service loop. This alarm is
cleared after the Ethernet service is reactivated.
Attribute
Major Service alarm
Parameters
None

The loop of the alarmed Ethernet service is released, and the Ethernet service is restored.
Possible Causes
Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is
deactivated.
Procedure
Step 1 Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is
deactivated.
1. Check whether a service is looped back on the path of the alarmed Ethernet service.
2. Re-configure the preceding service based on the network plan.
----End
Related Information
None
A.3.357 SSL_CERT_DAMAGED
Description
The SSL_CERT_DAMAGED is an alarm indicating that a user-customized SSL certificate
file is damaged. This alarm is reported to notify the user to rectify the SSL certificate file and
is cleared after the file is rectified.

Attribute
Critical Security alarm
Parameters
None

When this alarm occurs and the SSL certificate file is not rectified in time, the NE will be
unreachable to the NMS in SSL mode after the system control board of the NE is reset.
Possible Causes
Cause: The user-customized SSL certificate file is damaged.
Procedure
Step 1 Cause: The user-customized SSL certificate file is damaged.
1. Log in to the U2000, and load and activate the customized SSL certificate file again. For
details, see the section about loading board-level software in the iManager U2000
Product Documentation.
----End
Related Information
None
A.3.358 SSL_CERT_NOENC
Description
SSL_CERT_NOEN indicates the certificate file of SSL is not encrypted.
Attribute
Major Equipment Alarm
Parameters
None

Unencrypted certificate file is stored on device, private key of the file maybe be get illegally.

Possible Causes
Cause: Certificate file of SSL is not encrypted.
Procedure
Step 1 Cause: Certificate file of SSL is not encrypted.
1. Download and verify the encrypted SSL certificate by NMS.
----End
Related Information
None
A.3.359 SSL_CERT_TO_EXPIRE
Description
The SSL_CERT_TO_EXPIRE alarm indicates that a customized SSL certificate file is about
to expire. This alarm is reported when a customized SSL certificate file will expire after two
months to prompt users to reload and activate the SSL certificate file. This alarm is
automatically cleared after the SSL certificate file is reloaded and activated.
Attribute
Critical Security alarm
Parameters
Name Meaning
Parameter 1 Indicates the certificate type.

If the customized SSL certificate file is not reloaded or activated in time, the NE cannot
communicate with the NMS through SSL after a reset.
Possible Causes
Cause: A customized SSL certificate file is about to expire.

Procedure
Step 1 Cause: A customized SSL certificate file is about to expire.
1. Log in to the U2000, and load and activate the customized SSL certificate file again. For
details, see the section about loading board-level software in the iManager U2000
Product Documentation.
----End
Related Information
None
A.3.360 STORAGE_FAIL
Description
The STORAGE_FAIL alarm indicates a memory fault. This alarm is reported when a fault is
detected from the memory of an NE.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the memory fault type.

l 0x01: DDR fault
l 0x02: CPU cache fault (reserved)
l 0x04: NOR flash memory fault
l 0x08: NAND flash memory fault
l 0x10: SATA/CF fault

Name Meaning
Parameter 2 Indicates the fault cause. The meanings of Parameter 2 vary with the
value of Parameter 1.
l 0x01: ECC single-bit error
l 0x04: BootROM fault
l 0x08: overall failure
l 0x04: bad block rate of over 20%
l 0x02: not OK displayed in S.M.A.R.T. information
l 0x04: insufficient remaining backup blocks
l 0x08: memory card not detected
Parameter 3, These parameters are reserved. Their values are always 0xff.
Parameter 4,
Parameter 5

l A read or write error will occur in the file system.
l The memory lifespan is about to end.
Possible Causes
l Cause: A fault has occurred in the memory.
Procedure
Step 1 Check the alarm on the NMS and view parameters 1 and 2 to determine the memory fault type
and cause.
Step 2 Replace the device. For details, see the Part Replacement.
----End
Related Information
None

A.3.361 STORM_CUR_QUENUM_OVER
Description
The STORM_CUR_QUENUM_OVER alarm is reported when the number of alarms on an
NE is only one less than the maximum length of the alarm list.
Attribute
Parameters
None

When the number of current alarms reported by an NE reaches the maximum number of
alarms allowed by the alarm list, a new alarm forces out the earliest reported alarm among all
lowest-severity alarms from the alarm list. The forced-out alarm is then deleted from current
alarms on the NMS, and is reported again after the STORM_CUR_QUENUM_OVER alarm
clears.
This alarm does not affect services.
Possible Causes
The current alarm list is full.
Procedure
Step 1 Browse current alarms and clear alarms that are frequently reported.
Step 2 This alarm automatically clears when the number of alarms in the alarm list drops to a certain
value.
----End
Related Information
None
A.3.362 SUBNET_RT_CONFLICT
Description
The SUBNET_RT_CONFLICT is an alarm indicating a subnetwork route conflict. This alarm
occurs when the subnet route of an NMS port, that is, the IP subnet route of an NE, covers the
learned route of an OSPF subnet whose mask is longer than that of the IP subnet.

Attribute
Parameters
Name Meaning
Parameter 1 to Indicate the IP address of the subnet whose route is covered by the NE
Parameter 4 IP subnet route and whose mask is longer than that of the NE IP
subnet. When the routes of multiple subnets are covered by the IP
subnet route, this parameter is the IP address of the subnet with the
longest mask.
Parameter 5 Indicates the mask length.

The NMS cannot manage the NEs through the NMS port of the NE that report the
SUBNET_RT_CONFLICT alarm.
Possible Causes
The subnet route of an NMS port (the IP subnet route of an NE) covers the learned route of an
OSPF subnet whose mask is longer than that of the IP subnet.
Procedure
Step 1 Collect the information about all NEs that report this alarm and check the DCN networking
based on the planned network topology.
Step 2 Obtain the information about the conflicting subnets and their masks based on the alarm
parameters.
Step 3 Determine the rectification plan based on the network topology and subnet information to
ensure that the subnet masks of non-gateway NEs are consistent with the mask of the gateway
NE. When subnet masks of multiple NEs need to be changed, change their subnet masks from
the farthest NE to the nearest one.
CAUTION
If the mask of a gateway NE needs to be changed, ensure that the DCN route after the change
is correct. If the DCN route is incorrect, NEs may be unreachable to the NMS.

Step 4 Change the subnet masks of NEs according to the plan.
----End
Related Information
The SUBNET_RT_CONFLICT alarm is generally caused by incorrect configurations of
subnet masks on NEs. For example, NE1 and NE2 are connected using air interfaces and the
OSPF protocol is enabled. The communication parameters and routing information of the two
NEs are listed in the following table.
If the NMS whose IP address is 129.9.0.254 is connected to the NMS port of NE1, the route
of packets transmitted from NE1 to the NMS is "129.9.0.0/255.255.255.0/129.9.0.2/OSPF/air
interface" according to the longest match principle. That is, the packets are transmitted from
the air interface of NE1 to the air interface of NE2 and finally to the NMS port of NE2.
Therefore, the NMS cannot manage NE1 properly.
NE Parameter
NE1 IP address 129.9.0.1
Subnet mask 255.255.0.0
Main IP routes l 129.9.0.0/255.255.0.0/129.9.0.1/direct/Ethernet

(destination IP address/ l 129.9.0.0/255.255.255.0/129.9.0.2/OSPF/IF
subnet mask/gateway/ l 129.9.0.1/255.255.255.255/127.0.0.1/direct/loop
protocol/interface)
l 129.9.0.2/255.255.255.0/129.9.0.2/direct/IF
NE2 IP address 129.9.0.2
Subnet mask 255.255.255.0
Main IP routes l 129.9.0.0/255.255.255.0/129.9.0.1/direct/Ethernet

(destination IP address/ l 129.9.0.0/255.255.0.0/129.9.0.2/OSPF/air interface
subnet mask/gateway/ l 129.9.0.2/255.255.255.255/127.0.0.1/direct/loop
protocol/interface)
l 129.9.0.1/255.255.255.0/129.9.0.2/direct/IF
A.3.363 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating the activation timeout of the
software package. During the package loading, the system reports the alarm if no data is
submitted within 30 minutes after activation of the NE software or board software.
Attribute

Parameters
None

The NE does not perform the submit operation. As a result, the software in the two areas of
the double-area boards on the NE is inconsistent.
Possible Causes
l Cause 1: The package loading or diffusion task is suspended during package activation.
l Cause 2: The radio link is faulty. As a result, the NE involved in the package loading
fails to receive the submit command.
Procedure
Step 1 Cause 1: The package loading or diffusion task is suspended during package activation.
1. Restart the package loading or diffusion task.
Step 2 Cause 2: The radio link is faulty. As a result, the NE involved in the package loading fails to
receive the submit command.
1. Check whether the radio link is faulty.
If... Then...
The radio link is faulty Troubleshoot the radio link to ensure that the link
between the nodes to be loaded is normal.
The radio link is normal Perform the package loading to the NE again.
----End
Related Information
None
A.3.364 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function is
disabled. When the automatic match function of the board is disabled, the system reports the
alarm if the board cannot match the software from the system control board.
Attribute


Parameters
None

When a board whose version is not consistent with the software version of the NE is installed,
the software versions of the whole NE are not consistent if the board cannot automatically
match the software from the system control board. As a result, certain functions of the NE
cannot run normally.
Possible Causes
Cause 1: The automatic match function is disabled.
Procedure
Step 1 Cause 1: The automatic match function is disabled.
1. Contact the Huawei technical support engineers for troubleshooting.
----End
Related Information
None
A.3.365 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm of software inconsistency. After an NE is
power recycled and the boards on the NE get online, if the system detects that the system
control board and any other boards are inconsistent in software packages, the system reports
the SWDL_CHGMNG_NOMATCH alarm.
Attribute

Parameters
None

When the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE may
be affected.

Possible Causes
Cause 1: After a system control board is replaced, the software package in the new system
control board is inconsistent with that in other boards.
Procedure
Step 1 Cause 1: After a system control board is replaced, the software package in the new system
control board is inconsistent with that in other boards.
1. Re-load the software packages on the NE where the SWDL_CHGMNG_NOMATCH
alarm is reported.
----End
Related Information
None
A.3.366 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating that the commission operation on the NE
fails. This alarm is reported when the commission operation fails in the package diffusion.
Attribute
Parameters
None

When the SWDL_COMMIT_FAIL alarm occurs, the software versions in the two areas of the
double-area board are inconsistent.
Possible Causes
Cause 1: File backup fails.
Procedure
Step 1 Cause 1: File backup fails.
1. Check whether the loaded package is correct.
2. Perform the package diffusion again on the NE where the alarm is reported.
----End

Related Information
None
A.3.367 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the NE is loading the software package.
Attribute

Warning Processing alarm
Parameters
None

The NE is loading the software package. The operations including modifying configurations,
uploading/downloading files, and backing up the database are prohibited.
Possible Causes
The NE is loading the software package.
Procedure
Step 1 The SWDL_INPROCESS alarm is cleared automatically after the loading or rollback is
complete. Hence, this alarm can be neglected.
----End
Related Information
None
A.3.368 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that a file in the loaded software package
is lost or cannot be recovered after a file check failure. This alarm is reported when the NE
software initiates a package file check, detects the loss of a file, and fails to recover the file
from any complete package in other areas.

Attribute

Parameters
None

l If this alarm occurs during package loading, package loading fails.
l If this alarm occurs in other conditions, automatic file matching fails.
Possible Causes
Cause 1: Certain files of the package are missing and cannot be recovered.
Procedure
Step 1 Cause 1: Certain files of the package are missing and cannot be recovered.
1. Ensure that the loaded software package is correct. Perform the package loading again on
the NE where the SWDL_NEPKGCHECK alarm is reported.
----End
Related Information
None
A.3.369 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missing
from the software package. This alarm is reported when the required software is missing from
the software package during the automatic match of the board.
Attribute

Parameters
None


The board cannot perform automatic match, because the board software is missing from the
software package. Therefore, the board software version is inconsistent with the NE software
version, and certain functions of the NE may be affected.
Possible Causes
Cause 1: Certain board software is uninstalled during the software package loading.
Procedure
Step 1 Cause 1: Certain board software is uninstalled during the software package loading.
1. Add the required board software to the software package. Alternatively, perform the
software package loading again.
----End
Related Information
None
A.3.370 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the consistency check on the software
package version fails. This alarm is reported when the consistency check on the software
package version fails.
Attribute

Parameters
None

The software version of the software package is inconsistent with the software version
described in the software package. As a result, certain functions of the NE may be affected.
Possible Causes
Cause 1: The software version information in the description file of the software package is
inconsistent with the actual software version information.

Procedure
Step 1 Cause 1: The software version information in the description file of the software package is
inconsistent with the actual software version information.
1. Ensure that the loaded software package is correct. Perform the package diffusion again
on the NE where the alarm is reported.
----End
Related Information
None
A.3.371 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that the rollback on the NE fails. This
alarm is reported when the rollback fails for any board on the NE.
Attribute
Parameters
None

The board software version and the NE software version may mismatch, and certain functions
of the NE may be affected.
Possible Causes
Cause 1: Certain board software is uninstalled during the software package loading.
Procedure
Step 1 Cause 1: Certain board software is uninstalled during the software package loading.
1. Add the required board software to the software package. Alternatively, perform the
software package loading again.
----End
Related Information
None

A.3.372 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the quality of the synchronization source declines.
Attribute
Parameters
None

The NE clock fails to be locked.
Possible Causes
l Cause 1: The quality of the synchronization source declines.
Procedure
Step 1 Cause 1: The quality of the synchronization source declines.
1. Take different measures based on the traced synchronization source.
If... Then...
The traced synchronization source is Perform Steps Step 1.2 to Step 1.4.
an external clock
The traced synchronization source is Replace the system control,
a line clock switching&timing board of the upstream
NE.
2. Check whether the configuration of the external clock is correct.
If... Then...
The configuration is incorrect Change the configuration data.
The configuration is correct Go to the next step.
3. Check whether the opposite equipment that provides the clock source is faulty.
If... Then...
The equipment functions normally Go to the next step.

4. Check whether the cable that is connected to the external clock source is in normal
status.
If... Then...
The cable is not in normal status Replace the cable.
The cable is in normal status Go to Cause 2.

----End
Related Information
None
A.3.373 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the synchronization source is lost.
Attribute
Parameters
None

The NE clock degrades or enters the free-run mode.
Possible Causes
Cause 1: The clock source is lost.
Procedure
Step 1 Cause 1: The clock source is lost.
1. See Querying the Clock Synchronization Status, troubleshoot the synchronization
sources of the lost clock source based on the clock source priority table.
If... Then...
external clock

If... Then...
clock
clock board.
----End
Related Information
None
A.3.374 SYNC_DISABLE
Description
The SYNC_DISABLE is an alarm indicating that the automatic synchronization function of
the system control board is disabled. When the automatic synchronization function of the
system control board is disabled, the SYNC_DISABLE alarm occurs.
Attribute
Parameters
None.

When the SYNC_DISABLE alarm occurs, the batch backup cannot be initiated. Therefore,
the data of the working and protection boards is inconsistent.
Possible Causes
Cause 1: The automatic synchronization function of the system control board is disabled.
Procedure
Step 1 Cause 1: The automatic synchronization function of the system control board is disabled.
1. Issue an order to set the automatic synchronization state of the system control board to
enabled, and then check whether the alarm is cleared.
2. If the SYNC_DISABLE alarm persists, replace the alarmed board. For details, refer to
6.10 Replacing the System Control, Switching and Timing Board.
----End

Related Information
None.
A.3.375 SYSLOG_COMM_FAIL
Description
The SYSLOG_COMM_FAIL is an alarm indicating that the communication between the NE
and the syslog server fails.
Attribute

Parameters
None

The syslog information of the NE cannot be sent to the syslog server.
Possible Causes
Cause 1: In the TCP mode, the connection between the NE and syslog server is interrupted, or
the session between the NE and server is abnormal.
Procedure
Step 1 Rectify the fault of the link between the NE and syslog server, or rectify the fault of the
protocol.
----End
Related Information
None
A.3.376 T_ALOS
Description
The T_ALOS is an alarm indicating that the 2Mbit/s analog signal is lost at the specific port.

Attribute
Parameters
None

The 2Mbit/s services are interrupted.
Possible Causes
l Cause 1: No 2Mbit/s services are received on the port.
l Cause 3: The E1 cable is faulty.
Procedure
Step 1 Cause 1: No 2Mbit/s services are received on the port.
1. Check whether the alarmed port receives the 2 Mbit/s service.
If... Then...
The services are not received Transmit the services to the port or delete the
unnecessary service configuration.
The services are received Go to Cause 2.
Step 2 Cause 2: The equipment at the opposite end is faulty.

1. Check whether the equipment at the opposite end is faulty.
If... Then...
The equipment is normal Go to Cause 3.
Step 3 Cause 3: The E1 cable is faulty.

1. Check whether the E1 cable is faulty.
If... Then...
The E1 cable is faulty Rectify the fault.
The E1 cable is not faulty Go to Cause 4.

----End

Related Information
None
A.3.377 T_LOC
Description
The T_LOC is an alarm indicating that the clock is lost on the transmit line side.
Attribute

Parameters
None

The services in the alarmed AU-4 path are interrupted.
Possible Causes
l Cause 1: The cross-connect and timing board is faulty.
l Cause 2: The line board is faulty.
Procedure
Step 1 Cause 1: The cross-connect and timing board is faulty.
1. Replace the system control, cross-connect, and timing board at the local end.
If... Then...
replaced handling.
The alarm persists after the board is Go to Cause 2.
replaced
Step 2 Cause 2: The line board is faulty.

----End
Related Information
None

A.3.378 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is too high.
Attribute
Parameters
None

When this alarm occurs, the laser is functioning improperly. As a result, services are
interrupted.
Possible Causes
l Cause 1: The ambient temperature of the board is too high.
Procedure
Step 1 Check whether the temperature of the equipment room is too high. If yes, decrease the
temperature to an appropriate temperature. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, the optical module may be faulty. Replace the faulty board. For details,
see 6.14 Replacing the SFP or Replacing the Alarming Board.
----End
Related Information
None
A.3.379 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is too low.

Attribute
Parameters
None

When this alarm occurs, the laser is functioning improperly. As a result, services are
interrupted.
Possible Causes
l Cause 1: The ambient temperature of the board is too low.
Procedure
Step 1 Check whether the temperature of the equipment room is too low. If yes, increase the
temperature to an appropriate temperature. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, the optical module may be faulty. Replace the faulty board. For details,
see 6.14 Replacing the SFP or Replacing the Alarming Board.
----End
Related Information
None
A.3.380 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the board temperature crosses the threshold.
Attribute
Minor Environmental alarm
Parameters

Name Meaning
Parameter 1 l 0x01: The temperature crosses the upper threshold.
l 0x02: The temperature crosses the lower threshold.

The board fails to work normally.
Possible Causes
l Cause 1: The board temperature crosses the threshold.
l Cause 2: The temperature detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The board temperature crosses the threshold.
1. If the alarm is reported by the ODU, take appropriate measures (for example, installing a
sunshade) to control the temperature.
2. If the alarm is reported by the board on the IDU, check whether the temperature control
devices, such as air-conditioners, work normally.
If... Then...
The temperature control devices work Adjust the temperature control devices.
abnormally
The temperature control devices work Go to the next step.
normally
3. Check whether the heat dissipation hole on the IDU is covered or blocked.
If... Then...
The heat dissipation hole is covered or Clear or remove the covering
blocked materials or obstacles.
The heat dissipation hole is not covered or Go to Cause 2.
blocked
Step 2 Cause 2: The temperature detection circuit of the board is faulty.

1. If the ambient temperature is normal and no other heat dissipation problems exist,
replace the alarmed board.
----End
Related Information
None

A.3.381 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature of the board crosses
the threshold.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01: The temperature crosses the upper threshold.
l 0x02: The temperature crosses the lower threshold.

When this alarm occurs, the board cannot work properly.
Possible Causes
l Cause 1: The board temperature crosses the threshold.
l Cause 2: The temperature detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The board temperature crosses the threshold.
1. Check whether temperature control devices, such as air-conditioners, work properly.
If... Then...
The temperature control devices Adjust the temperature control devices.
malfunction
The temperature control devices work Go to the next step.
properly
2. Check whether the heat dissipation hole on the IDU is covered or blocked.

If... Then...
The heat dissipation hole is covered or Clear or remove the covering
blocked materials or obstacles.
The heat dissipation hole is not covered or Go to the next step.
blocked
Step 2 Cause 2: The temperature detection circuit of the board is faulty.

1. If the ambient temperature is normal and no other heat dissipation problems exist,
replace the board that reports the alarm. For details see Replacing the Alarming Board.
----End
Related Information
None
A.3.382 TF
Description
The TF is an alarm indicating that the laser transmission fails. This alarm is reported when a
board detects that the output optical power of the laser exceeds the preset failure alarm
threshold.
Attribute
Parameters
None

When this alarm occurs, the laser transmission fails. As a result, services are interrupted.
Possible Causes
l Cause 1: The laser module is damaged.
l Cause 2: The laser is aged out.
Procedure
Step 1 6.14 Replacing the SFP.
----End

Related Information
None
A.3.383 THUNDERALM
Description
The THUNDERALM is an alarm indicating the surge protection failure. If the system detects
the surge protection circuit fails, the THUNDERALM occurs.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the PIU that reports the alarm.
l 0x01: PIU1
l 0x02: PIU2

When the THUNDERALM occurs, the system operation and services are not affected, but the
surge protection function fails.
Possible Causes
The possible causes of the THUNDERALM alarm are as follows:
l Cause 1: The fuse tube of the surge protection circuit is interrupted.
Procedure
Step 1 Cause 1: The fuse tube of the surge protection circuit is interrupted.
1. Replace the fuse tube, and then check whether the alarm is cleared.
1. Replace the board that reports the THUNDERALM alarm.
----End

Related Information
None
A.3.384 TIME_LOCK_FAIL
Description
The TIME_LOCK_FAIL is an alarm indicating a time locking failure.
Attribute

Parameters
Name Meaning
Parameter 1 l 0x01: indicates that the time synchronization is disabled or the 1588v2 port
is not traced.
l 0x02: indicates that the clock is unlocked because phase discrimination
value within the given time exceeds the upper threshold.
l 0x03: indicates that the forward delay is abnormal.
l 0x04: indicates that the backward delay is abnormal.
l 0x05: indicates that the accumulated offset value within the given time
exceeds 240 ns.
l 0x06: indicates that the accumulated offset value within the given time is
greater than 100 ns but less than 240 ns.

When this alarm occurs, the time of the slave NE fails to trace that of the master NE. Bit
errors may occur in the service.
Possible Causes
The timestamp change on the NE is too large.
Procedure
Step 1 Check whether there are CLK_LOCK_FAIL or TIME_NO_TRACE_MODE alarms on the
NE. If yes, clear them before you proceed.
Step 2 Adjust the time on the upstream NE.
----End

Related Information
None
A.3.385 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the high precision time of the
boards is in the non-traced status. This alarm is reported when the high precision time
function of an NE is enabled and the current tracing source is the internal time source.
Attribute
Parameters
Name Meaning
Parameter 1 Indicate the cause of the alarm.

0x01: indicates that the IEEE 1588v2 function is enabled on a port.
0x02: indicates that an external clock interface is set to the input status.

When this alarm occurs, time between the NE and the upstream NEs cannot be synchronized.
Possible Causes
l Cause 1: The clock source priority table is not configured when an external clock
interface is used to trace the upstream NE clock.
l Cause 2: The link between the traced upstream time source and the NE is faulty.
l Cause 3: The announce attribute of the local NE is inconsistent with that of the upstream
NE. As a result, the time source cannot be traced.
Procedure
Step 1 Cause 1: The clock source priority table is not configured when an external clock interface is
used to trace the upstream NE clock.
1. Set the clock source priority. For details, see Configuring the Clock Sources.

Step 2 Cause 2: The link between the traced upstream time source and the NE is faulty.
1. Check the link fault.
Step 3 Cause 3: The announce attribute of the local NE is inconsistent with that of the upstream NE.
As a result, the time source cannot be traced.
1. Check clock tracing relationships on the entire network based on the network plan.
----End
Related Information
None
A.3.386 TR_LOC
Description
The TR_LOC is an alarm indicating that the clock is faulty. This alarm is reported when a
board detects that the clock signal transmitted from the clock unit to the board is lost.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot ID of the board that loses the clock.
l 0x01: board with a smaller slot ID.
l 0x02: board with a larger slot ID.
l 0x03: two boards.

l If the protection cross-connect board is faulty, the services are not affected.
l If the working cross-connect board is faulty, the services are switched, therefore causing
transient service interruption.
Possible Causes
l Cause 1: If one board reports this alarm, the board hardware is faulty.
l Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board
is faulty.

Procedure
Step 1 Locate the alarmed board according to the alarm parameter.
Step 2 Cause 1: If one board reports this alarm, the board hardware is faulty.
1. Perform a warm reset on the alarmed board, and then check whether the alarm is cleared.
If the alarm persists, perform a cold reset on the alarmed board. For details, see
Resetting a Boards.
2. If the alarm persists, remove the alarmed board and check whether certain pins on the
backplane are bent. Insert the board again, and then check whether the alarm is cleared.
3. If the alarm persists, replace the alarmed board. For details, see Replacing a Board.
Step 3 Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board is
faulty.
1. If the working cross-connect board is faulty, perform 1+1 protection switching on the
cross-connect board. For details, see Performing 1+1 Protection Switching.
2. Perform a cold reset on the protection cross-connect board, and then check whether the
alarm is cleared.
3. If the alarm persists, remove and insert the protection cross-connect board, and then
4. If the alarm persists, replace the protection cross-connect board.
----End
Related Information
None
A.3.387 TU_AIS
Description
The AU_AIS is an alarm indicating that the TU has errors. This alarm is reported if a board
detects that the signal in the TU path is all 1s.
Attribute

Parameters
None

The service in the alarmed TU path is interrupted. If the services are configured with
protection, protection switching is also triggered.

Possible Causes
l Cause 2: The line is faulty.
l Cause 3: The board at the opposite end is faulty.
l Cause 4: The board at the local end is faulty.
Procedure
1. See Creating the Cross-Connections of Point-to-Point Services to check whether the
service data is incorrect.
If... Then...
The service data is incorrect Change the configuration data.
The service data is correct Go to Cause 2.
Step 2 Cause 2: The line is faulty.

1. Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
For details about the line alarms that cause AIS insertion, see D.2.6 AIS Insertion.
If... Then...
The line alarm is reported Clear the line alarms that cause AIS insertion.
No line alarms are reported Go to the next step.
2. See 8.4 Software Loopback to locate whether the board at the local end or at the
opposite end is faulty.
If... Then...
The board at the opposite end is faulty Go to Cause 3.
The board at the local end is faulty Go to Cause 4.
Step 3 Cause 3: The board at the opposite end is faulty.

1. Replace the faulty board at the opposite end.
Step 4 Cause 4: The board at the local end is faulty.

1. Replace the board where the local line unit resides.
If... Then...
replaced handling.
The alarm persists after the board is Go to the next step.
replaced

If... Then...
replaced handling.
replaced
----End
Related Information
None
A.3.388 TU_AIS_VC12
Description
The TU_AIS_VC12 is an indication of TU alarms at VC-12 level. This alarm occurs when a
board detects TU pointers of all 1s.
Attribute
Parameters
Name Meaning
0x01.

When this alarm occurs, the services in the alarmed VC-12 path are interrupted. If the services
are configured with protection, protection switching is also triggered.
Possible Causes
l Cause 2: The line is faulty.
l Cause 3: The board at the opposite site is faulty.

l Cause 4: The board at the local site is faulty.
Procedure
1. Check whether the SDH service data is correct. For details, see Creating the Cross-
Connections of Point-to-Point Services.
If... Then...
The SDH service data is incorrect Change the configuration data.
The SDH service data is correct Go to Cause 2.
Step 2 Cause 2: The line is faulty.

1. Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
For details about the line alarms that cause AIS insertion, see D.2.6 AIS Insertion.
If... Then...
The line alarm is reported Change the configuration data.
No line alarms are reported Go to Step 3.
Step 3 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.4.6
Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.
If... Then...
The board at the opposite site is faulty Go to Cause 3.
The board at the local site is faulty Go to Cause 4.
Step 4 Cause 3: The board at the opposite site is faulty.

1. Replace the faulty board at the opposite site.
Step 5 Cause 4: The board at the local site is faulty.

1. Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical
Interface Board.
If... Then...
The alarm clears after the board is The fault is rectified. End the alarm
replaced handling.
replaced
2. Replace the alarmed board at the local site
----End
Related Information
None

A.3.389 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU-3 alarm indication. The alarm is reported when a board detects TU
pointers of all "1"s.
Attribute
Parameters
Name Meaning
path 1.

The services in the alarmed TU-3 paths are interrupted. If the services are configured with
protection, protection switching is triggered.
Possible Causes
l Cause 1: SDH service configuration data is incorrect.
l Cause 2: The service path is faulty.
Procedure
Step 1 Cause 1: SDH service configuration data is incorrect.
1. Follow instructions in Creating the Cross-Connections of Point-to-Point Services to
check whether the SDH service configuration data is incorrect.
If... Then...
The SDH service configuration data is Rectify the SDH service configuration
incorrect data.

If... Then...
The SDH service configuration data is Go to cause 2.
correct
Step 2 Cause 2: The service path is faulty.

1. Check whether a line alarm that will cause AIS insertion is reported on the service path.
NOTE
For the line alarms that will cause AIS insertion, see D.2.6 AIS Insertion.
If... Then...
A line alarm that will cause AIS insertion is Rectify the SDH service configuration
reported data.
No line alarm is reported Go to step 3.
Step 3 Follow instructions in 8.4.5 Setting a Loopback for the Packet-plane Ethernet Interface
Board to identify whether the board at the local end or at the opposite end is faulty.
If... Then...
The board at the opposite end is faulty Go to cause 3.
The board at the local end is faulty Go to cause 4.


1. Follow instructions in 6.3 Replacing the SDH Optical Interface Board to replace the
line board at the local end.
If... Then...
2. Follow instructions in 6.10 Replacing the System Control, Switching and Timing
Board to replace the system control, switching, and timing board.
If... Then...
The alarm persists Follow instructions in Replacing an Alarmed Board to replace
the board that reports the alarm.
----End
Related Information
None

A.3.390 TU_LOP
Description
The TU_LOP is an alarm indicating that the TU pointer is lost. This alarm is reported if a
board detects that the TU-PTR value is an invalid pointer or NDF reversion in eight
consecutive frames.
Attribute

Parameters
None

The service in the alarmed TU path is interrupted. If the services are configured with
protection, protection switching is also triggered.
Possible Causes
l Cause 1: The system control, cross-connect, and timing board is faulty.
l Cause 2: The tributary board is faulty.
Procedure
Step 1 Cause 1: The system control, cross-connect, and timing board is faulty.
If... Then...
replaced handling.
The alarm persists after the board is Go to Cause 2.
replaced
Step 2 Cause 2: The tributary board is faulty.

1. Replace the board where the tributary unit resides.
----End
Related Information
None

A.3.391 TU_LOP_VC12
Description
The TU_LOP_VC12 is an alarm indicating that the VC-12 TU pointer is lost. This alarm is
reported when a board receives invalid pointers or new data flags (NDFs) in eight consecutive
VC-12 frames.
Attribute
Parameters
Name Meaning
0x01.

Services in the alarmed TU path are interrupted. If the services are configured with protection,
protection switching is also triggered.
Possible Causes
l Cause 2: The board at the opposite site is faulty.
l Cause 3: The board at the local site is faulty.
Procedure
1. Check whether the SDH service data is correct. For details, see Creating the Cross-
Connections of Point-to-Point Services.
If... Then...
The SDH service data is incorrect Change the configuration data.
The SDH service data is correct Go to Step 2.
Step 2 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.4.6
Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.

If... Then...
The board at the opposite site is faulty Go to Cause 2.
The board at the local site is faulty Go to Cause 3.
Step 3 Cause 2: The board at the opposite site is faulty.

1. In this case, replace the faulty board at the opposite site.
Step 4 Cause 3: The board at the local site is faulty.

1. Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical
Interface Board.
If... Then...
The alarm clears after the board is The fault is rectified. End the alarm
replaced handling.
replaced
2. Replace the alarmed board at the local site.
----End
Related Information
None
A.3.392 TU_LOP_VC3
Description
The TU_LOP_VC3 alarm indicates that a TU-3 pointer is lost. This alarm is reported if a
board detects that eight consecutive VC-3 TU-PTR values are invalid or the NDF field in
eight consecutive VC-3 TU-PTR values are reversed.
Attribute

Parameters
Name Meaning

Name Meaning
path 1.

The services in the alarmed TU-3 path are interrupted. If the services are configured with
protection, protection switching is triggered.
Possible Causes
l Cause 1: SDH service configuration data is incorrect.
Procedure
Step 1 Cause 1: SDH service configuration data is incorrect.
1. Follow instructions in Creating the Cross-Connections of Point-to-Point Services to
check whether the SDH service configuration data is incorrect.
If... Then...
The SDH service configuration data is Rectify the SDH service configuration
incorrect data.
The SDH service configuration data is Go to step 2.
correct
Step 2 Follow instructions in 8.4.5 Setting a Loopback for the Packet-plane Ethernet Interface
Board to identify whether the board at the local end or at the opposite end is faulty.
If... Then...
The board at the opposite end is faulty Go to cause 2.
The board at the local end is faulty Go to cause 3.

1. Follow instructions in 6.3 Replacing the SDH Optical Interface Board to replace the
line board at the local end.
If... Then...
2. Follow instructions in 6.10 Replacing the System Control, Switching and Timing
Board to replace the system control, switching, and timing board.

If... Then...
3. Follow instructions in Replacing an Alarmed Board to replace the board that reports
the alarm.
----End
Related Information
None
A.3.393 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED is an alarm indicating that a tunnel protection group
degrades.
Attribute
Major Service alarm
Parameters
None

The protection tunnel is faulty and the protection group fails. The working tunnel is
unprotected.
Possible Causes
Cause: The protection tunnel in the tunnel protection group is faulty.
Procedure
Step 1 Check the status of the tunnel protection group, locate the failed tunnel in the protection
group.
Step 2 Querying MPLS tunnel information, locate the board and port used by the failed tunnel.
Step 3 If the port is a Ethernet port, refer to Setting the Basic Attributes of Ethernet Ports, check
whether the port is disabled.
Enable the port if it was disabled.
Step 4 Refer to 4.3.1 Browsing Current Alarms, check whether any relevant Ethernet services
alarms are generated in the port or board. If yes, take priority to clear them.


l Hardware alarms: Such as HARD_BAD, POWER_ALM, BD_STATUS,
COMMUN_FAILand LASER_MOD_ERR.
l Link alarms: Such as ETH_LOS, ETH_AUTO_LINK_DOWN,
ETH_EFM_LOOPBACK, LOOP_ALM, PORTMODE_MISMATCH, and
LAG_DOWN.
l Radio link alarms: Such as MW_LOF, MW_LIM.
Step 5 Refer to 4.3.1 Browsing Current Alarms, check whether any alarms are generated in the
failed tunnel. If yes, take priority to clear them.

l MPLS_TUNNEL_BDI
l MPLS_TUNNEL_Excess
l MPLS_TUNNEL_FDI
l MPLS_TUNNEL_LOCV
l MPLS_TUNNEL_MISMATCH
l MPLS_TUNNEL_MISMERGE
l MPLS_TUNNEL_OAMFAIL
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_UNKNOWN
l MPLS_TUNNEL_AIS
l MPLS_TUNNEL_RDI
l MPLS_TUNNEL_UNEXPMEG
l MPLS_TUNNEL_UNEXPMEP
l MPLS_TUNNEL_UNEXPPER
----End
Related Information
None
A.3.394 TUNNEL_APS_OUTAGE
Description
The TUNNEL_APS_OUTAGE alarm indicates that a tunnel APS protection group is
unavailable. This alarm is reported when both the working and protection tunnels of the
protection group fail.
Attribute
Major Service alarm

Parameters
None

The services carried by the protection group are interrupted.
Possible Causes
Cause 1: The working and protection tunnels of the tunnel APS protection group fail.
Procedure
Step 1 Cause 1: The working and protection tunnels of the tunnel APS protection group fail.
1. Determine the boards and port IDs associated with the faulty tunnels. For details, see
Querying MPLS APS Status.
2. Handle tunnel faults by referring to 5.10 Troubleshooting MPLS Tunnels.
----End
Related Information
None
A.3.395 UHCS
Description
The UHCS is an alarm of uncorrected header check sequence. This alarm occurs when
multiple uncorrectable bit errors exist in the cell headers.
Attribute
Parameters
None

When the UHCS alarm occurs, some cells with multiple bit errors are detected during cell
delimitation at the ATM port. Consequently, the user cells are lost.
Possible Causes
l Cause 1: A few bit errors occur in the receive path related to the ATM port which reports
the UHCS alarm.

l Cause 2: The ATM physical-layer processing chip of the board is faulty.
Procedure
Step 1 Cause 1: A few bit errors occur in the receive path connected to the ATM port which reports
the UHCS alarm.
1. On the NMS, check whether the related receive path reports any alarms indicating
excessive bit errors, such as B1_SD, B2_SD, and B3_SD.
2. On the NMS, check whether the service is looped.
3. If yes, modify the service configuration to release the loop, and then check whether the
alarm is cleared.
Step 2 Cause 2: The ATM physical-layer processing chip of the board is faulty.
1. Perform a cold reset on the board that reports the UHCS alarm and check whether the
alarm is cleared. For details, see 8.6.1 Cold Reset.
2. Optional: If the UHCS alarm persists after the cold reset, replace the alarmed board and
check whether the alarm is cleared. For details, see 6.6 Replacing the Smart E1
Interface Board.
----End
Related Information
None
A.3.396 UP_E1_AIS
Description
The UP_E1_AIS is an alarm indication of the 2 Mbit/s uplink signal. This alarm is reported
when the tributary board detects that the 2 Mbit/s uplink signal is all 1s.
Attribute
Parameters
None

E1 signals are unavailable.
Possible Causes
l Cause 1: The opposite equipment transmits the AIS signal.
l Cause 2: The receive unit of the tributary board on the local equipment is faulty.

Procedure
Step 1 Cause 1: The opposite equipment transmits the AIS signal.
1. Check whether the opposite equipment transmits the AIS signal.
If... Then...
The opposite equipment transmits the AIS Rectify the fault on the opposite
signal equipment.
The opposite equipment does not transmit Go to Cause 2.
the AIS signal
Step 2 Cause 2: The receive unit of the tributary board on the local equipment is faulty.
----End
Related Information
None
A.3.397 USB_FILE_UNSEC
Description
The USB_FILE_UNSEC alarm indicates that the USB flash drive used by the NE is insecure.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The file is not encrypted.
l 0x02: Decryption fails.
l 0x03: The integrity check fails.

If the file is not encrypted, security risks exist, but functions of the USB flash drive are
available.

If the integrity check or decryption fails, data backup or restoration on the USB flash drive
will fail.
Possible Causes
l Cause 1: The file is not encrypted.
l Cause 2: Decryption fails.
l Cause 3: The integrity check fails.
Procedure
Step 1 Determine the alarm cause based on alarm parameters.
Step 2 If the file is not encrypted, encrypt the file using an NMS tool.
Step 3 If the integrity check or decryption fails, re-copy the database backup file.
----End
Related Information
None
A.3.398 USB_PROCESS_FAIL
Description
The USB_PROCESS_FAIL is an alarm indicating that data recovery from or data backup to a
USB disk fails.
Attribute
Parameters
Name Meaning
Parameter 1 l 0x01 indicates data recovery.
l 0x02 indicates data backup.

Name Meaning
Parameter 2 Indicates the file type.
l 0x01: indicates the software package.

l 0x02: indicates the patch package.
l 0x03: indicates the system parameter area.
l 0x04: indicates the script.
l 0x05: indicates the database.
l 0x06: indicates the license file.
l 0x08: indicates the configuration file related to the anti-theft function of the
equipment.

When this alarm occurs, the database fails to be backed up or recovered. The system status
remains unchanged.
Possible Causes
l Cause 1: Recovering data from a USB disk fails.
l Cause 2: Backing up data to a USB disk fails.
Procedure
Step 1 Cause 1: Recovering data from a USB disk fails.
1. Verify that the USB flash drive can be identified by the NE.
2. Check whether the data in the USB flash drive is correct. If the data is incorrect, upload
the USB flash drive with correct data.
3. Verify that the operations for recovering data from the USB flash drive are correct.
Step 2 Cause 2: Backing up data to a USB disk fails.
1. Verify that the USB flash drive has enough capacity for data backup.
2. Check whether the USB flash drive is properly inserted. If the USB flash drive is not
properly inserted, re-insert the USB flash drive.
3. Replace the USB flash drive and re-back up data.
----End
Related Information
None
A.3.399 V5_VCAIS
Description
The V5_VCAIS is an alarm indicating that bits 5-7 in the V5 byte of a VC-12 path are set to
"1"s.

Attribute
Parameters
None

When this alarm occurs, services are interrupted in the TU path of the board.
Possible Causes
l Cause 1: Hardware fault alarms occur on boards of an upstream NE.
Procedure
Step 1 Check whether any hardware fault alarms occur on boards of an upstream NE. If yes, clear
them. Then, check whether the V5_VCAIS alarm is cleared.
Step 2 If the alarm persists, the alarmed board is faulty. Cold Reset the board and check whether
the alarm is cleared.
Step 3 If the alarm persists, Replace the alarming board.
----End
Related Information
None
A.3.400 VC_AIS
Description
The VC_AIS is an alarm indication of the virtual channel (VC) connection. This alarm occurs
when the VC connection that is set with the segment end point attribute receives the AIS
cells, indicating that the upstream ATM services are abnormal.
Attribute
Parameters


Name Meaning
Parameter 1 Indicates the direction of ATM connection.

l 0x01: forward
l 0x02: backward
Parameter 2 Indicates the segment and end attribute of ATM connection.

l 0x01: segment
l 0x02: end

l If the continuity check (CC) sink is enabled on an upstream NE but the upstream NE
does not receive any CC cells, the local NE reports the VP_AIS. Then, the connection,
though not interrupted, is not loaded with any user service.
l In other cases, when the local NE detects that the VC connection is interrupted, the AIS
cells are inserted in the downstream direction and the RDI cells are returned to the
upstream NE.
Possible Causes
l Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted to the
downstream.
l Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is
abnormal in the receive direction and therefore inserts AIS cells to the downstream.
l Cause 3: The board on the local NE is faulty.
Procedure
Step 1 Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted to the
downstream.
1. On the NMS, check whether the VC_LOC occurs and the ATM connections that report
the VC_LOC have the same ID.
2. If the VC_LOC occurs, clear the VC_LOC and then the AIS insertion stops.
Step 2 Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is
1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,
TU_AIS or TU_LOP occurs in the upstream SDH path.
2. If yes, clear these alarms and then the AIS insertion stops.
Step 3 Cause 3: The board on the local NE is faulty.
1. Perform a cold reset on the alarmed board.
2. If the alarm persists, replace the alarmed board.
----End

Related Information
Unidirectional Connection
A complete bidirectional connection consists of two unidirectional connections: a forward
connection and a backward connection. The direction of the forward and backward
connections is based on the same node.
End and Segment
The end point refers to the termination point in the chain network, and it is used to monitor
the whole virtual connection.
The segment point is, generally, used to monitor a segment of the whole link.
Segment End Point
This is one of the segment end attributes. The segment end attributes include: segment point,
end point, segment and end point, non segment and end point.
l If an NE is set with the segment end point attribute, it can retrieve the alarms that are
generated at the segment and end.
l If an NE is set with the segment point attribute, it can retrieve the alarms that are
generated at a segment.
l If an NE is set with the end point attribute, it can retrieve the alarms that are generated at
an end.
l If an NE is set with the non segment end point attribute, it fails to retrieve the alarms that
are generated at the segment and end.
A.3.401 VC_LOC
Description
The VC_LOC is an alarm indicating loss of connectivity on the virtual channel (VC). This
alarm is reported when the CC is enabled but no cell is received within 3.5s (±0.5s).
Attribute
Parameters

Name Meaning

l 0x01: forward
l 0x02: backward

l 0x01: segment
l 0x02: end

l If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,
the service connection, though not interrupted, is not loaded with any user service.
l In other cases, the service is interrupted when the alarm occurs.
l When this alarm occurs, the system automatically inserts AIS cells to the downstream.
Possible Causes
l Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the
upstream NE.
l Cause 2: No bandwidth is available on the local NE.
abnormal in the receive direction.
Procedure
Step 1 Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the
upstream NE.
1. Check whether the CC function on the local NE is activated.
2. If yes, Deactivate the CC function on the local NE. Then, check whether the alarm is
cleared.
Step 2 Cause 2: No bandwidth is available on the local NE.

1. On the NMS, check whether the bandwidth allocated to the tunnel is fully used.
2. If yes, increase the bandwidth or eliminate the sources that transmit a large amount of
invalid data.
1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,
TU_AIS or TU_LOP, occurs in an upstream SDH path.
2. If yes, clear these alarms and check whether the VC_LOC is cleared.


----End
Related Information
None
A.3.402 VC_RDI
Description
The VC_RDI is an alarm indicating that defects occur at the remote end of the virtual channel
(VC) connection. This alarm occurs when a forward or backward VC connection that is set
with the segment end point attribute receives the RDI cells, indicating that the downstream
services are abnormal.
Attribute
Parameters
Name Meaning

l 0x01: forward
l 0x02: backward

l 0x01: segment
l 0x02: end

l When this alarm occurs, it indicates that a segment end point at the remote end of the VC
connection receives AIS cells and returns RDI cells to the local end, but the services at
the local end are not affected.
Possible Causes
l Cause 1: The VC_AIS occurs in the receive direction of the downstream VC connection.

Procedure
Step 1 Cause 1: The VC_AIS occurs in the receive direction of the downstream VC connection.
1. Check whether the VC_AIS occurs in the receive direction of the downstream VC
connection.
2. If yes, clear the VC_AIS and then check whether the VC_RDI is cleared.

----End
Related Information

End and Segment
Segment End Point
an end.
A.3.403 VCAT_LOA
Description
The VCAT_LOA is an alarm indicating alignment loss of virtual concatenations. This alarm is
reported if a board detects that the time delays between the timeslots bound to a VCTRUNK
exceed the permissible limit.

Attribute

Parameters
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the VCTRUNK path.

The virtually concatenated services are interrupted.
Possible Causes
Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so the
delays between the virtually concatenated links are long.
Procedure
Step 1 Cause 1: The timeslots bound to a VCTRUNK travel through different physical links, so the
delays between the virtually concatenated links are long.
1. Determine the ID of the alarmed VCTRUNK path based on the alarm parameters.
2. Check whether the transmission routes of the paths bound to a VCTRUNK are the same.
If not, adjust their routes to the same.
----End
Related Information
None
A.3.404 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 is an alarm indicating the loss of virtual concatenation multiframes
in the VC-12 path. This alarm is reported if the board detects that the K4 byte of the VC-12
path does not match the expected multiframe sequence.

Attribute

Parameters
Name Meaning
0x01.

The alarmed path is unavailable. If the LCAS function is disabled, the services in the path are
interrupted.
Possible Causes
l Cause 1: Bit errors occur on the line.
l Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
l Cause 3: The delays between virtual concatenations are over long.
Procedure
Step 1 Cause 1: Bit errors occur on the line.
1. Check whether any bit error alarm such as BIP_EXC and BIP_SD occurs.
If... Then...
A bit error alarm occurs Handle the alarm immediately.
No bit error alarm occurs Go to Cause 2.
Step 2 Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
1. Replace the board at the opposite site. For details, see 6.7 Replacing the Ethernet
Interface Board.
2. Replace the board and then check whether the alarm clears.
If... Then...

Step 3 Cause 3: The delays between virtual concatenations are over long.
1. Check whether the VCAT_LOA alarm is reported in this path.
If... Then...
The VCAT_LOA alarm is reported Handle the VCAT_LOA alarm
immediately.
The VCAT_LOA alarm is not reported Go to Cause 2.
2. Check whether the VCAT_LOM_VC12 alarm clears after handling the VCAT_LOA
alarm.
If... Then...
The alarm persists Replace the alarmed board at the local site. For details, see
Replace the alarmed board.
----End
Related Information
None
A.3.405 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 alarm indicates the loss of virtually concatenated multiframes in a
VC-3 path. A board reports this alarm when detecting that byte H4 in the VC-3 path does not
match the expected multiframe sequence.
Attribute
Parameters
Name Meaning
path 1.


The path that reports the alarm is unavailable. If the LCAS function is disabled, services are
interrupted.
Possible Causes
l Cause 1: Bit errors occur in the line.
l Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect.
l Cause 3: The delays between virtual concatenations are too long.
Procedure
Step 1 Cause 1: Bit errors occur in the line.
1. Check for the bit error alarms such as BIP_EXC or BIP_SD.
If... Then...
The bit error alarms exist Handle the alarms immediately.
The bit error alarms do not exist Go to Cause 2.
Step 2 Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect.
1. Follow instructions in 6.7 Replacing the Ethernet Interface Board to replace the board
2. Replace the alarmed board and then check whether the alarm clears.
If... Then...
Step 3 Cause 3: The delays between virtual concatenations are too long.
1. Check whether a VCAT_LOA alarm is reported in this path.
If... Then...
A VCAT_LOA alarm is reported in this path Handle the VCAT_LOA alarm
immediately.
No VCAT_LOA alarm is reported in this Go to Cause 2.
path
2. Check whether the VCAT_LOM_VC3 alarm clears after handling the VCAT_LOA
alarm.
If... Then...
The VCAT_LOM_VC3 alarm End the alarm handling.
clears
The VCAT_LOM_VC3 alarm Follow instructions in 6.7 Replacing the
persists Ethernet Interface Board to replace the alarmed
board at the local site.
----End

Related Information
None
A.3.406 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 is an alarm indicating the SQ number mismatch of a virtual
concatenation in the VC-12 path. This alarm is reported if the board detects that the SQ of a
virtual concatenation does not match the expected value.
Attribute
Parameters
Name Meaning
0x01.

The alarmed path is unavailable. If the LCAS function is disabled, services are interrupted.
Possible Causes
l Cause 1: Bit errors occur on certain links or certain links are faulty.
l Cause 2: The SQ number sent from the opposite site is incorrect.
Procedure
Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.
1. Check whether bit errors or line alarms occur. Focus on the bit error alarm BIP_EXC or
BIP_SD.
If... Then...
Bit errors or line alarms occur Clear these alarms.
No bit errors or line alarms occur Go to the next step.

Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.
1. Replace the corresponding board at the opposite site.
If... Then...
The alarm clears after the board is End the alarm handling.
replaced
The alarm persists after the board is Contact Huawei technical support
replaced engineers for handling the alarm.
----End
Related Information
None
A.3.407 VCAT_SQM_VC3
Description
The VCAT_SQM_VC3 alarm indicates that the sequence (SQ) number mismatch of a virtual
concatenation in a VC-3 path. A board reports this alarm when detecting that the SQ of a
virtual concatenation does not match the expected value.
Attribute
Parameters
Name Meaning
path 1.

The path that reports the alarm is unavailable. If the LCAS function is disabled, services are
interrupted.

Possible Causes
l Cause 1: Bit errors occur on a link or a link is faulty.
l Cause 2: The SQ number sent from the opposite site is incorrect.
Procedure
Step 1 Cause 1: Bit errors occur on a link or a link is faulty.
1. Check for bit error alarms or line alarms, especially BIP_EXC and BIP_SD.
If... Then...
Bit error alarms or line alarms occur Clear these alarms.
No bit error alarms or line alarms occur Go to Cause 2.
Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.
1. Replace the related board at the opposite site.
If... Then...
The VCAT_SQM_VC3 alarm clears after the board End the alarm handling.
is replaced
The VCAT_SQM_VC3 alarm persists after the Contact Huawei technical
board is replaced support engineers.
----End
Related Information
None
A.3.408 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power voltage is unavailable.
Attribute
Parameters

Name Meaning

The ODU that is connected to the IF board that reports this alarm fails to work.
Possible Causes
l Cause 1: The output power is abnormal.
l Cause 2: The input power is abnormal.
Procedure
Step 1 Cause 1: The output power is abnormal.
1. Check whether the soft power switch of an ODU connected to the dual-channel IF board
or the power switch of the ODU connected to the single-channel IF board is turned on.
If... Then...
The soft power switch of an ODU Turn on the soft power switch of the
connected to the dual-channel IF board is ODU.
not turned on
The soft power switch of the ODU Turn on the soft power switch.
connected to the single-channel IF board
is not turned on
The soft power switch or power switch is Go to the next step.

turned on
2. Use the multimeter to check the IF fiber jumper, IF cable, or ODU section by section for
a short circuit.
NOTICE
If the alarm is reported due to a short circuit, replace the short-circuited cable or ODU,
and then replace the IF board. Otherwise, the new IF board may be damaged again.
If... Then...
A short circuit exists Replace the short-circuited component,

and then replace the alarmed IF board.
No short circuits exist replace the alarmed IF board.
Step 2 Cause 2: The input power is abnormal.

1. Replace the alarmed IF board.
----End
Related Information
None
A.3.409 VP_AIS
Description
The VP_AIS is an alarm indication of the virtual path (VP) connection. When a forward or
backward VP connection that is set with the segment end point attribute receives the AIS
cells, the alarm is reported, indicating that the upstream services are abnormal.
Attribute
Parameters
Name Meaning

l 0x01: forward
l 0x02: backward

l 0x01: segment
l 0x02: end

l If the continuity check (CC) sink is enabled on an upstream NE but the upstream NE
does not receive any CC cells, the local NE reports the alarm. In this case, the
connection, though not interrupted, is not loaded with any user service.
l In other cases, when the local NE detects that the VP connection is interrupted, the AIS
cells are inserted to the downstream and the RDI cells are returned to the upstream NE.
Possible Causes
l Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to the
downstream.

abnormal in the receive direction and inserts AIS cells to the downstream.
Procedure
Step 1 Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to the
downstream.
1. On the NMS, check whether the VP_LOC occurs and the ATM connections that report
the VP_LOC have the same ID.
2. If the VP_LOC occurs, clear the VP_LOC and then the AIS insertion stops.
1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, TU_AIS, TU_LOP,
AU_AIS or AU_LOP, occurs in an upstream SDH path.
2. If yes, clear these alarms and then the AIS insertion stops.

----End
Related Information

End and Segment
Segment End Point
an end.

A.3.410 VP_LOC
Description
The VP_LOC is an alarm indicating loss of connectivity on the virtual path (VP). This alarm
is reported when the CC is enabled but no cell is received within 3.5s (±0.5s). When any cell
is received, the alarm is cleared automatically.
Attribute
Parameters
Name Meaning

l 0x01: forward
l 0x02: backward

l 0x01: segment
l 0x02: end

l If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,
the service connection, though not interrupted, is not loaded with any user service.
l In other cases, the service is interrupted when the alarm occurs.
l When this alarm occurs, the system automatically inserts AIS cells to the downstream.
l The VP_LOC is suppressed when the VP_AIS occurs.
Possible Causes
l Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the
upstream NE.
l Cause 2: No bandwidth is available on the local NE.

Procedure
Step 1 Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the
upstream NE.
1. Deactivate the CC function on the local NE.
Step 2 Cause 2: No bandwidth is available on the local NE.

1. On the NMS, check whether the bandwidth allocated to the tunnel is fully used.
2. If yes, increase the bandwidth or eliminate the sources that transmit a large amount of
invalid data.
1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, TU_AIS, TU_LOP,
AU_AIS or AU_LOP, occurs in an upstream SDH path.
2. If yes, clear these alarms.

2. Check whether the alarm is cleared. If not, replace the alarmed board.
----End
Related Information
None
A.3.411 VP_RDI
Description
The VP_RDI is an alarm indicating that defects occur at the remote end of the virtual path
(VP) connection. This alarm occurs when a forward or backward VP connection that is set
with the segment end point attribute receives the RDI cells, indicating that the downstream
services are abnormal.
Attribute

Parameters

Name Meaning

l 0x01: forward
l 0x02: backward

l 0x01: segment
l 0x02: end

l When this alarm occurs, the services are not affected. This alarm just indicates that the
services in the receive direction of the downstream VP connection are abnormal. The
AIS cells are received in a segment point of the connection, and the RDI cells are
returned to the upstream VP connection.
Possible Causes
l Cause 1: The VP_AIS occurs in the receive direction of the downstream VP connection.
Procedure
l Cause 1: The VP_AIS occurs in the receive direction of the downstream VP connection.
a. Check whether the VP_AIS occurs in the receive direction of the downstream VP
connection.
b. If yes, clear the VP_AIS and then check whether the VP_RDI is cleared.
a. Perform a cold reset on the alarmed board. For details, see 8.6.1 Cold Reset.
b. If the alarm persists, replace the alarmed board. For details, see 6.6 Replacing the
----End
Related Information
End and Segment
Segment End Point

an end.
A.3.412 W_R_FAIL
Description
The W_R_FAIL is an alarm indicating a failure of reading or writing chip register.
Attribute

Parameters
Name Meaning
Parameter 1 Indicates the ID of the chip.

Services in the alarmed path are interrupted.
Possible Causes
Cause 1: The chip register is faulty or the read/write timing is incorrect.
Procedure
Step 1 Cause 1: The chip register is faulty or the read/write timing is incorrect.
----End

Related Information
None
A.3.413 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating that the type of the board is incorrect.
Attribute

Parameters
None

The board fails to work.
Possible Causes
l Cause 2: The board of an incorrect type is installed.
Procedure
1. See Configuring the Logical Board to check whether the board type complies with the
planning requirement.
If... Then...
The board type does not meet the planning Change the configuration data.
requirement
The board type meets the planning requirement Go to Cause 2.
Step 2 Cause 2: The board of an incorrect type is installed.

1. Replace the board of an incorrect type.
----End
Related Information
None

A.3.414 XPIC_LOS
Description
The XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.
Attribute
Parameters
None

Bit errors may occur in the service at the port, and the service may even be interrupted.
Possible Causes
l Cause 1: The radio link is faulty.
l Cause 2: The XPIC cable is faulty.
NOTE
For ISM6 boards, ignore this cause.
l Cause 3: The IF board or ODU is faulty.
Procedure
Step 1 Cause 1: The radio link is faulty.
1. Check whether the paired board that is connected to the XPIC IF board through the
XPIC cable reports the MW_LOF alarm. If yes, first clear the MW_LOF alarm.
Step 2 Cause 2: The XPIC cable is faulty.

1. Check the connection of the XPIC cable.
If... Then...
The cable is improperly connected Connect the XPIC cable properly.
The cable is properly connected Go to the next step.
2. Test the make and break of the XPIC cable by using the multimeter. If the XPIC cable is
damaged, replace it.
Step 3 Cause 3: The IF board or ODU is faulty.
Locate the fault by replacing the IF board or ODU.
1. Replace the paired board of the XPIC IF board.

The paired board of the XPIC IF board refers to the other XPIC IF board connected to
the alarmed XPIC IF board through the XPIC cable.
If... Then...
The alarm is cleared after the board is End the alarm handling.
replaced

replaced
2. Replace the ODU that is connected to the paired XPIC IF board.

If... Then...
The alarm is cleared after the ODU is End the alarm handling.
replaced
The alarm persists after the ODU is Replace the alarmed XPIC IF board.
replaced
----End
Related Information
None

Maintenance Guide B Performance Event Reference
B Performance Event Reference
Performance events are important indicators when the equipment performance changes. This
chapter describes all the possible performance events on the and how to handle these
performance events.
B.1 Performance Events (by Event Type)

The list is categorized based on the performance event type, and includes all the events of the
OptiX RTN 980.
B.2 Performance Events (by Logical Board)
This part lists all the performance events that are reported by each board.
B.3 Performance Events and Handling Procedures
Based on the type of a performance event, this chapter describes all the performance events
on the and how to handle these performance events.

B.1 Performance Events (by Event Type)

The list is categorized based on the performance event type, and includes all the events of the
OptiX RTN 980.
B.1.1 SDH/PDH Performance Event List

SDH/PDH performance events are classified into six categories: pointer justification,
regenerator section error, multiplex section error, higher order path error, lower order path
error, E1 Error Performance Events and E1 line side code violation.
Table B-1 Pointer Justification Performance Events
Event Name Description
AUPJCHIGH Indicates the count of positive AU pointer

justifications.
AUPJCLOW Indicates the count of negative AU pointer

justifications.
AUPJCNEW Indicates the count of new AU pointer

justifications.
TUPJCHIGH Indicates the count of positive TU pointer

justifications.
TUPJCLOW Indicates the count of negative TU pointer

justifications.
TUPJCNEW Indicates the count of new TU pointer

justifications.
Table B-2 Regenerator Section Error Performance Events
RSBBE Indicates the regenerator section

background block error.
RSES Indicates the regenerator section errored

second.
RSSES Indicates the regenerator section severely

errored second.
RSUAS Indicates the regenerator section unavailable

second.
RSCSES Indicates the regenerator section

consecutive severely errored second.

RSOFS Indicates the regenerator section out-of-

frame second.
RSOOF Indicates the count of regenerator section

out-of-frame events.
NOTE
In the case of PDH radio, regenerator section bit error performance events also exist and they are detected
according to the overheads used for detecting frame alignment and bit errors in the PDH microwave frames.
Table B-3 Multiplex Section Error Performance Events

MSBBE Indicates the multiplex section background

block error.
MSES Indicates the multiplex section errored

second.
MSSES Indicates the multiplex section severely

errored second.
MSCSES Indicates the multiplex section consecutive

severely errored second.
MSUAS Indicates the multiplex section unavailable

second.
MSFEBBE Indicates the multiplex section far end

MSFEES Indicates the multiplex section far end

errored second.
MSFESES Indicates the multiplex section far end

MSFECSES Indicates the multiplex section far end

MSFEUAS Indicates the multiplex section far end

unavailable second.
Table B-4 Higher Order Path Error Performance Events

HPBBE Indicates the higher order path background

block error.

HPES Indicates the higher order path errored

second.
HPSES Indicates the higher order path severely

errored second.
HPCSES Indicates the higher order path consecutive

HPUAS Indicates the higher order path unavailable

second.
HPFEBBE Indicates the higher order path far end

HPFEES Indicates the higher order path far end

errored second.
HPFESES Indicates the higher order path far end

HPFECSES Indicates the higher order path far end

HPFEUAS Indicates the higher order path far end

unavailable second.
Table B-5 Lower Order Path Error Performance Events

LPBBE Indicates the lower order path background

block error.
LPES Indicates the lower order path errored

second.
LPSES Indicates the lower order path severely

errored second.
LPCSES Indicates the lower order path consecutive

LPUAS Indicates the lower order path unavailable

second.
LPFEBBE Indicates the lower order path far end

LPFEES Indicates the lower order path far end

errored second.

LPFESES Indicates the lower order path far end

LPFECSES Indicates the lower order path far end

LPFEUAS Indicates the lower order far end

unavailable second.
Table B-6 E1 Line Side Code Violation Performance Events

E1_LCV_SDH Indicates the count of E1 line side code

violations.
E1_LLOSS_SDH Indicates the E1 line side loss-of-signal

second.
E1_LES_SDH Indicates the E1 line side code violation

errored second.
E1_LSES_SDH Indicates the E1 line side code violation

Table B-7 E1 Error Performance Events

E1_BBE Indicates the E1 background block error.
E1_ES Indicates the E1 errored second.
E1_SES Indicates the E1 severely errored second.
E1_CSES Indicates the E1 consecutive severely

errored second.
E1_UAS Indicates the E1 unavailable second.
B.1.2 Radio Performance Events

The radio performance events are performance events of the radio link bit errors, ATPC, AM,
and power.

Table B-8 Radio power performance events
TSL_MAX Maximum value of radio transmit signal

level
TSL_MIN Minimum value of radio transmit signal

level
TSL_CUR Current value of radio transmit signal level
TSL_AVG Average value of radio transmit signal level
RSL_MAX Maximum value of radio receive signal

level
RSL_MIN Minimum value of radio receive signal level
RSL_CUR Current value of radio receive signal level
RSL_AVG Average value of radio receive signal level
TLHTT The duration when the ODU at the local end

has a transit power higher than the upper
threshold
TLLTT The duration when the ODU at the local end

has a transit power higher than the lower
threshold
RLHTT The duration when the ODU at the local end

has a receive power lower than the upper
threshold
RLLTT The duration when the ODU at the local end

has a receive power lower than the lower
threshold
Table B-9 FEC performance events
FEC_BEF_COR_ER FEC bit error rate before correction
FEC_UNCOR_BLOCK_CNT FEC uncorrected block count
Table B-10 Radio link error performance events
IF_BBE Radio link background block errors
IF_ES Radio link errored seconds

IF_SES Radio link severely errored seconds
IF_UAS Radio link unavailable second
IF_CSES Radio link consecutive severely errored

seconds
IF_BER Radio link bit error rate
Table B-11 ATPC performance events

ATPC_P_ADJUST Positive ATPC adjustment
ATPC_N_ADJUST Negative ATPC adjustment
Table B-12 AM performance events

QPSKWS Working time of the QPSK mode
QAMWS16 Working time of the 16QAM mode
QPSK_S_WS Working time of the QPSKSTRONG mode
QAM_S_WS16 Working time of the 16QAMSTRONG

mode
QAM_L_WS512 Working time of the 512QAMLIGHT mode
QAM_L_WS1024 Working time of the 1024QAMLIGHT

mode
AMDOWNCNT Count of the downshift of the AM scheme

AMUPCNT Count of the upshift of the AM scheme
Table B-13 XPIC performance events

XPD_MAX Maximum XPD value
XPD_MIN Minimum XPD value
XPIC_XPD_VALUE XPIC XPD value
Table B-14 IF 1+1 protection group error performance events

PG_IF_BBE IF 1+1 protection group background block

errors
PG_IF_ES IF 1+1 protection group errored seconds
PG_IF_SES IF 1+1 protection group severely errored

seconds
PG_IF_UAS IF 1+1 protection group unavailable second
PG_IF_CSES IF 1+1 protection group consecutive

severely errored seconds
Table B-15 IF port error performance events

IF_SNR_MAX Maximum signal to noise ratio
IF_SNR_MIN Minimum signal to noise ratio
IF_SNR_AVG Average signal to noise ratio
IF_MSE_MAX Maximum MSE
IF_MSE_MIN Minimum MSE
IF_MSE_AVG Average MSE
IF_MSE_CUR Current MSE

B.1.3 MPLS PW Performance Events

This section lists MPLS PW performance events.
Table B-16 MPLS tunnel/PW performance events
MPLS_PW_LS PW packet loss seconds
MPLS_PW_SLS PW severe packet loss seconds
MPLS_PW_CSLS PW consecutive severe packet loss seconds
MPLS_PW_UAS PW unavailable seconds
MPLS_PW_LS_N PW packet loss seconds at the near end
MPLS_PW_SLS_N PW severe packet loss seconds at the near

end
MPLS_PW_CSLS_N PW consecutive severe packet loss seconds

at the near end
MPLS_PW_UAS_N PW unavailable seconds at the near end
B.1.4 Other Performance Events

In addition to the SDH/PDH and radio performance events, the OptiX RTN 980 supports
performance events of the optical power, the temperature, laser and clock.
Table B-17 Optical power performance events
TPLMAX Maximum value of transmit optical power
TPLMIN Minimum value of transmit optical power
TPLCUR Current value of transmit optical power
RPLMAX Maximum value of receive optical power
RPLMIN Minimum value of receive optical power
RPLCUR Current value of receive optical power
Table B-18 Board temperature performance events
BDTEMPMAX Maximum value of board temperature

BDTEMPMIN Minimum value of board temperature
BDTEMPCUR Current value of board temperature
Table B-19 Laser temperature performance events

OSPITMPMAX Maximum temperature of a laser core
OSPITMPMIN Minimum temperature of a laser core
OSPITMPCUR Current temperature of a laser core
Table B-20 Transmitted bias current performance events

Performance Event Name Description
TLBMAX Maximum transmitted bias current of the

laser
TLBMIN Minimum transmitted bias current of the

laser
TLBCUR Current transmitted bias current of the laser
Table B-21 Clock performance events

MAXFREQDEV Maximum frequency deviation
MINFREQDEV Minimum frequency deviation
AVGFREQDEV Average frequency deviation
CURPOSITIVEPDV Current positive PDV
MAXPOSITIVEDELAY Maximum positive delay
MINPOSITIVEDELAY Minimum positive delay
AVGPOSITIVEDELAY Average positive delay
MAXPHASEOFFSET Maximum phase offset
MINPHASEOFFSET Minimum phase offset
AVGPHASEOFFSET Average phase offset

MAXMEANPATHDELAY Maximum path delay
MINMEANPATHDELAY Minimum path delay
AVGMEANPATHDELAY Average path delay
Table B-22 Memory usage performance events
MEMUSAGEAVG Average memory usage
MEMUSAGECUR Current memory usage
MEMUSAGEMAX Maximum memory usage
MEMUSAGEMIN Minimum memory usage
B.2 Performance Events (by Logical Board)

This part lists all the performance events that are reported by each board.
NOTE
The NE software consider a physical board as one or more logical boards when managing the physical board.
The NMS also considers a physical board as one or more logical boards when managing the physical board.
Table A-2 shows the logical boards corresponding to all physical boards
Table B-23 Mappings between the physical boards and logical boards

Board
CSHN l CSHN in slot 15 + SL4D in slot 16 + EG2D in slot 17

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

l CSHNA in slot 20 + SL4D in slot 21 + EG4 in slot 22
CSHNU l CSHNU in slot 15 + SL4D in slot 16 + EG4 in slot 17 + EX1 in slot

18
l CSHNU in slot 20 + SL4D in slot 21 + EG4 in slot 22 + EX1 in slot
23
AUX AUX in the same slot
IF1 IF1 in the same slot
IFU2 IFU2 in the same slot


Board
IFX2 IFX2 in the same slot
ISU2 ISU2 in the same slot
ISX2 ISX2 in the same slot
ISV3 ISV3 in the same slot
ISM6 ISM6 in the same slot
SL1D SL1D in the same slot
SL1DA SL1DA in the same slot
EM6T EM6T in the same slot
EM6TA EM6TA in the same slot
EM6F EM6F in the same slot
EM6FA EM6FA in the same slot
EG4 EG4 in the same slot
EG4P EG4P in the same slot
EFP8 EFP8 in the same slot
EMS6 EMS6 in the same slot
EX1 EX1 in the same slot
SP3S SP3S in the same slot
SP3D SP3D in the same slot
ML1 ML1 in the same slot
MD1 MD1 in the same slot
CQ1 CQ1 in the same slot
PIU PIU in the same slot
FAN FAN in the same slot
ODU ODU in the slot whose number is 50 plus the slot number for the IF
board that is connected to the ODU
B.2.1 CQ1
The CQ1 board reports the board temperature performance events, SDH performance events
and Laser Performance Events.

Board temperature performance events

SDH Performance Events


justifications.

justifications.

justifications.
TUPJCHIGH Indicates the count of positive TU pointer

justifications.
TUPJCLOW Indicates the count of negative TU pointer

justifications.



second.

errored second.

second.


Table B-27 Multiplex section error performance events

MSBBE Multiplex section block of background error
MSES Multiplex section errored second
MSSES Multiplex section severely errored second
MSCSES Multiplex section consecutive severely

errored second
MSUAS Multiplex section unavailable second
MSFEBBE Multiplex section far end block of

background error
MSFEES Multiplex section far end errored second
MSFESES Multiplex section far end severely errored

second
MSFECSES Multiplex section far end consecutive

severely errored second
MSFEUAS Multiplex section far end unavailable

second
Table B-28 Higher order path error performance events

HPBBE Higher order path background errored block
HPES Higher order path errored second
HPSES Higher order path severely errored second
HPCSES Higher order path consecutive severely

errored second
HPUAS Higher order path unavailable second
HPFEBBE Higher order path far end background

errored block
HPFEES Higher order path far end errored second
HPFESES Higher order path far end severely errored

second
HPFECSES Higher order path far end consecutive

HPFEUAS Higher order path far end unavailable

second

Table B-29 Lower order path error performance events
LPBBE Lower order path block of background error
LPES Lower order path errored second
LPSES Lower order path severely errored second
LPCSES Lower order path continuous severe bit

error second
LPUAS Lower order path unavailable second
LPFEBBE Lower order path far end block of

background error
LPFEES Lower order path far end errored second
LPFESES Lower order path far end severely errored

second
LPFECSES Lower order path far end consecutive

LPFEUAS Lower order far end unavailable second
Laser Performance Events
Table B-30 Transmitted bias current performance events
Performance Event Name Description
TLBMAX Maximum transmitted bias current of the

laser
TLBMIN Minimum transmitted bias current of the

laser
TLBCUR Current transmitted bias current of the laser


B.2.2 CSHN
The CSHN board reports four types of performance events: board temperature performance
events, IF 1+1 protection group error performance events, clock performance events, and PW
performance events.

BDTEMPMAX Indicates the maximum board

temperature.
BDTEMPMIN Indicates the minimum board

temperature.
BDTEMPCUR Indicates the current board temperature.


errors

seconds



Table B-36 PW performance events


end

at the near end

B.2.3 CSHNA
The CSHNA board reports four types of performance events: board temperature performance
events, IF 1+1 protection group error performance events, clock performance events, and PW
performance events.


temperature.

temperature.


errors

seconds



Table B-40 PW performance events


end

at the near end

B.2.4 CSHNU
The CSHNU board reports the following types of performance events: board temperature
performance events, bit error performance events of IF 1+1 protection groups, clock

performance events, PW service performance events, CPU usage performance events, and
memory usage performance events.

BDTEMPMAX Maximum board temperature
BDTEMPMIN Minimum board temperature
BDTEMPCUR Current board temperature
Table B-43 Bit error performance events of IF 1+1 protection groups

PG_IF_BBE Background block error of a protection

group
PG_IF_CSES Consecutive severely errored second of a

protection group
PG_IF_ES Errored second of a protection group
PG_IF_SES Severely errored second of a protection

group
PG_IF_UAS Unavailable second of a protection group


Table B-45 PW service performance events

MPLS_PW_CSLS PW consecutive severe packet loss second
MPLS_PW_LS PW packet loss second
MPLS_PW_SLS PW severe packet loss second
MPLS_PW_UAS PW unavailable second
MPLS_PW_CSLS_N PW consecutive severe packet loss second

at the near end
MPLS_PW_LS_N PW packet loss second at the near end
MPLS_PW_SLS_N PW severe packet loss second at the near

end
MPLS_PW_UAS_N PW unavailable second at the near end
Table B-46 Tunnel performance events

MPLS_TUNNEL_CSLS Tunnel consecutive severe packet loss

second
MPLS_TUNNEL_LS Tunnel packet loss second
MPLS_TUNNEL_SLS Tunnel severe packet loss second
MPLS_TUNNEL_UAS Tunnel unavailable second
MPLS_TUNNEL_CSLS_N Tunnel consecutive severe packet loss

second at the near end
MPLS_TUNNEL_LS_N Tunnel packet loss second at the near end
MPLS_TUNNEL_SLS_N Tunnel severe packet loss second at the near

end
MPLS_TUNNEL_UAS_N Tunnel unavailable second at the near end

Table B-47 CPU usage performance events

CPUUSAGEAVG Average CPU usage
CPUUSAGECUR Current CPU usage
CPUUSAGEMAX Maximum CPU usage
CPUUSAGEMIN Minimum CPU usage

B.2.5 EG2D
The EG2D board reports only the optical power performance events.

B.2.6 EG4P
The EG4P board reports optical power performance events and board temperature
performance events.



B.2.7 EG4
The EG4 board reports optical power performance events, laser performance events, and
board temperature performance events.

Table B-53 Board temperature performance events (supported only by physical EG4 boards)

Table B-54 Laser performance events (supported only by integrated EG4 boards)
LSBIASCUR Current laser bias current
LSBIASMAX Maximum laser bias current
LSBIASMIN Minimum laser bias current
LSIOPCUR Current input optical power of the laser
LSIOPMAX Maximum input optical power of the

laser
LSIOPMIN Minimum input optical power of the

laser
LSOOPCUR Current output optical power of the laser
LSOOPMAX Maximum output optical power of the

laser
LSOOPMIN Minimum output optical power of the

laser
LSTMPCUR Current laser temperature
LSTMPMAX Maximum laser temperature
LSTMPMIN Minimum laser temperature
B.2.8 EM6T
The EM6T board reports only the board temperature performance events.

B.2.9 EM6TA
The EM6TA board reports only the board temperature performance events.
B.2.10 EM6F
The EM6F board reports optical power performance events and board temperature
performance events.
B.2.11 EM6FA
The EM6FA board reports optical power performance events and board temperature
performance events.



B.2.12 EFP8
The EFP8 board reports the temperature and PDH performance events.



error second


background error

second

B.2.13 EMS6
The EMS6 board reports the SDH performance events, board temperature performance
events, laser temperature performance events, and optical power performance events.


error second

background error

second




errored second

errored block

second





B.2.14 EX1
The EX1 board reports optical power performance events and board temperature performance
events.
Table B-69 Board temperature performance events (supported only by physical EX1 boards)
Table B-70 Laser performance events (supported only by integrated EX1 boards)
LSBIASCUR Current laser bias current
LSBIASMAX Maximum laser bias current
LSBIASMIN Minimum laser bias current
LSIOPCUR Current input optical power of the laser

LSIOPMAX Maximum input optical power of the

laser
LSIOPMIN Minimum input optical power of the

laser
LSOOPCUR Current output optical power of the laser
LSOOPMAX Maximum output optical power of the

laser
LSOOPMIN Minimum output optical power of the

laser
LSTMPCUR Current laser temperature
LSTMPMAX Maximum laser temperature
LSTMPMIN Minimum laser temperature
B.2.15 IF1
The IF1 board reports three types of performance events: SDH/PDH performance events,
microwave performance events, and temperature performance events.
SDH/PDH Performance Events
Table B-71 Pointer justification performance events
AUPJCHIGH Count of positive AU pointer justification
AUPJCLOW Count of negative AU pointer justification
AUPJCNEW Count of new AU pointer justifications
Table B-72 Regenerator section error performance events
RSBBE Regenerator section block of background

error
RSES Regenerator section errored second
RSSES Regenerator section severely errored second
RSUAS Regenerator section unavailable second

RSCSES Regenerator section consecutive severely

errored second
RSOFS Regenerator section out-of-frame second
RSOOF Regenerator section out of frame
NOTE
The regenerator section error performance events also occur in the case of the PDH radio. The PDH
radio frame is detected through the overheads that are used for frame location and bit error detection.


errored second

background error

second


second

HPBBE Higher order path background block error


errored second
HPFEBBE Higher order path far end background block

error

second


second
Radio Performance Events

FEC_COR_BYTE_CNT Frame count incorrect by FEC

IF_MSE_MAX Maximum MSE value
IF_MSE_MIN Minimum MSE value
IF_MSE_CUR Current MSE value
IF_MSE_AVG Average MSE value

Other Performance Events
B.2.16 IFU2/ISU2
The IFU2/ISU2 board reports three types of performance events: SDH performance events,
PDH performance events, radio performance events, and board temperature performance
events.
SDH Performance Events (Only reported by ISU2)

error

errored second



errored second

background error

second


second


errored second

errored block

second


second

PDH Performance Events


error second

background error

second





seconds




B.2.17 IFX2/ISX2
The IFX2/ISX2 board reports three types of performance events: SDH/PDH performance
events, radio performance events, and board temperature performance events.
SDH Performance Events (Only Reported by ISX2)



error

errored second



errored second

background error

second


second


errored second

errored block

second


second



error second

background error

second





seconds


B.2.18 ISV3
The ISV3 board reports four types of performance events: SDH performance events, PDH
performance events, microwave performance events, and board temperature performance
events.


error

errored second



errored second

background error

second


second


justifications.

justifications.

justifications.


errored second


errored block

second


second


error second

background error

second



seconds
QPSK_S_WS Working time of the QPSK strong mode
QAM_S_WS16 Working time of the 16QAM strong mode
QAM_L_WS512 Working time of the 512QAM light mode





B.2.19 ISM6
The ISM6 board reports four types of performance events: SDH performance events, PDH
performance events, microwave performance events, and board temperature performance
events.


error

errored second


errored second

background error

second



second


justifications.

justifications.

justifications.


errored second

errored block

second


second



error second

background error

second





seconds

QPSK_S_WS Working time of the QPSK strong mode
QAM_S_WS16 Working time of the 16QAM strong mode




B.2.20 ML1/MD1
The ML1/MD1 board reports E1 performance events and board temperature performance
events.
Table B-121 E1 Performance Event List

E1_LCV_SDH Indicates the count of E1 line side code

violations.
E1_LLOSS_SDH Indicates the E1 line side loss-of-signal

second.
E1_LES_SDH Indicates the E1 line side code violation

errored second.

E1_LSES_SDH Indicates the E1 line side code violation

Table B-122 Board Temperature Performance Events


temperature.

temperature.
B.2.21 ODU
The ODU reports radio performance events and board temperature performance events.
Table B-123 Radio power performance events

TSL_MAX Maximum value of radio transmit signal

level
TSL_MIN Minimum value of radio transmit signal

level
TSL_CUR Current value of radio transmit signal level
TSL_AVG Average value of radio transmit signal level
RSL_MAX Maximum value of radio receive signal

level
RSL_MIN Minimum value of radio receive signal level
RSL_CUR Current value of radio receive signal level
RSL_AVG Average value of radio receive signal level
TLHTT The duration when the ODU at the local end

has a transit power higher than the upper
threshold
TLLTT The duration when the ODU at the local end

has a transit power higher than the lower
threshold

RLHTT The duration when the ODU at the local end

has a receive power lower than the upper
threshold
RLLTT The duration when the ODU at the local end

has a receive power lower than the lower
threshold
ODU_SSV_TH The duration when the ODU at the local end

has a receive power lower than the receiver
sensitivity
Table B-124 ATPC performance events
ATPC_P_ADJUST Positive ATPC adjustment
ATPC_N_ADJUST Negative ATPC adjustment

temperature.

temperature.
B.2.22 SL1D/SL1DA
The SL1D/SL1DA board reports two types of performance events: SDH performance events,
and optical power performance events.



error

errored second


errored second

background error

second


second



errored second

errored block

second


second

B.2.23 SL4D
The SL4D board reports SDH performance events and optical power performance events.


justifications.

justifications.

justifications.


second.

errored second.

second.

RSOFS Indicates the regenerator section out-of-

frame second.
RSOOF Indicates the count of regenerator section

out-of-frame events.
Table B-133 Multiplex Section Error Performance Events
MSBBE Indicates the multiplex section background

block error.
MSES Indicates the multiplex section errored

second.
MSSES Indicates the multiplex section severely

errored second.

MSCSES Indicates the multiplex section consecutive

MSUAS Indicates the multiplex section unavailable

second.
MSFEBBE Indicates the multiplex section far end

MSFEES Indicates the multiplex section far end

errored second.
MSFESES Indicates the multiplex section far end

MSFECSES Indicates the multiplex section far end

MSFEUAS Indicates the multiplex section far end

unavailable second.
Table B-134 Higher Order Path Error Performance Events

HPBBE Indicates the higher order path background

block error.
HPES Indicates the higher order path errored

second.
HPSES Indicates the higher order path severely

errored second.
HPCSES Indicates the higher order path consecutive

HPUAS Indicates the higher order path unavailable

second.
HPFEBBE Indicates the higher order path far end

HPFEES Indicates the higher order path far end

errored second.
HPFESES Indicates the higher order path far end

HPFECSES Indicates the higher order path far end


HPFEUAS Indicates the higher order path far end

unavailable second.
Table B-135 Optical Power Performance Events
TPLMAX Indicates the maximum transmit optical

power at an optical interface.
TPLMIN Indicates the minimum transmit optical

TPLCUR Indicates the current transmit power at an

optical interface.
RPLMAX Indicates the maximum receive optical

RPLMIN Indicates the minimum receive optical

RPLCUR Indicates the current receive power at an

optical interface.
B.2.24 SP3S/SP3D
The SP3S/SP3D board reports only the PDH performance events.
TUPJCHIGH Count of positive TU pointer justifications
TUPJCLOW Count of negative TU pointer justifications
TUPJCNEW Count of new TU pointer justifications


error second

background error

second

Table B-138 E1 error performance events

E1_BBE Indicates the E1 background block error.
E1_ES Indicates the E1 errored second.
E1_SES Indicates the E1 severely errored second.
E1_CSES Indicates the E1 consecutive severely

errored second.
E1_UAS Indicates the E1 unavailable second.
B.3 Performance Events and Handling Procedures

Based on the type of a performance event, this chapter describes all the performance events
on the and how to handle these performance events.
B.3.1 ATPC_P_ADJUST and ATPC_N_ADJUST

Description
l ATPC_P_ADJUST indicates the positive ATPC adjustment event.
This performance event indicates that the quality of a communication link declines.
Therefore, you must increase the transmit power of the ODU to maintain the
communication quality.

l ATPC_N_ADJUST indicates the negative ATPC adjustment event.

This performance event indicates that the quality of a communication link becomes well
or the transmit power of the ODU is very large. Therefore, you can decrease the transmit
power of the ODU.
Attribute
Attribute Description
Performance event cell ATPCPADJUST (ATPC_P_ADJUST) and

ATPCNADJUST (ATPC_N_ADJUST)
Unit times

The ATPC adjustment indicates only the stability of a communication link and it does not
affect services. When the value of the performance event is larger, more adjustments are
made.
When the factors that affect a communication link, such as sudden change of the weather, do
not exist, and when the ATPC adjustment count is very large, the communication link may be
faulty. You must check the communication link to prevent it from failure.
Related Alarms
None
B.3.2 AMDOWNCNT and AMUPCNT
Description
l AMDOWNCNT indicates the count of the AM downshifts on a board in the current
performance statistics period.
l AMUPCNT indicates the count of the AM upshifts on a board in the current
performance statistics period.
Attribute
Performance event cell ACMDCNT(AMDOWNCNT) and

ACMUCNT(AMUPCNT)
Unit times
Impact on System
l When the value of the performance event is larger, more AM scheme are made.

l When the factors that affect a communication link, such as sudden change of the
weather, do not exist, and when the AM scheme count is very large, the communication
link may be faulty. You must check the communication link to prevent it from failure.
Related Alarms
AM_DOWNSHIFT
Possible Causes
When the AM function is enabled, the transmission modulation scheme that the IF port on the
IF board uses varies according to the quality of the link. Accordingly, the system counts the
performance events of the modulation scheme shift. When the low-efficiency modulation
scheme is shifted to the high-efficiency modulation scheme, an upshift is recorded and one
AMUPCNT event is counted. Similarly, when the high-efficiency modulation scheme is
shifted to the low-efficiency modulation scheme, a downshift is recorded and one
AMDOWNCNT event is counted.
B.3.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW

Description
l AUPJCHIGH indicates the count of positive AU pointer justifications.
l AUPJCLOW indicates the count of negative AU pointer justifications.
l AUPJCNEW indicates the count of new AU pointer justifications.
Attribute
Performance event cell PPJE (AUPJCHIGH)

NPJE (AUPJCLOW)
NDF (AUPJCNEW)
Unit Block
Impact on System
Less than six AUPJCHIGH and AUPJCLOW events do not affect the system. If the pointer is
justified for many times, or the AUPJCNEW event occurs, bit errors may occur in the service.
Related Alarms
When the AUPJCHIGH, AUPJCLOW, or AUPJCNEW performance event crosses the preset
threshold, the MSAD_CROSSTR alarm is reported.
Performance Event Default 15-Minute Default 24-Hour

Threshold Threshold
AUPJCHIGH 1500 30000


Threshold Threshold
AUPJCLOW 1500 30000
AUPJCNEW 1500 30000
Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.
----End
B.3.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR

Description
l BDTEMPMAX indicates the maximum temperature of a board.
l BDTEMPMIN indicates the minimum temperature of a board.
l BDTEMPCUR indicates the current temperature of a board.
Attribute
Performance event cell XCS_TEMP
Unit 0.1°C
Impact on System
If the temperature of a board is very high or very low, the performance of the board declines,
and bit errors or other faults occur.
Related Alarms
If the temperature of a board crosses the specific threshold, the TEMP_ALARM alarm is
reported.

B.3.5 CPUUSAGEMAX, CPUUSAGEMIN, CPUUSAGECUR, and

CPUUSAGEAVG
Description
l CPUUSAGEMAX indicates the maximum CPU usage.
l CPUUSAGEMIN indicates the minimum CPU usage.
l CPUUSAGECUR indicates the current CPU usage.
l CPUUSAGEAVG indicates the average CPU usage.
Attribute
Performance event cell SYS_CPU_CONDITION
Unit Percentage

None
Relevant Alarms
None
B.3.6 CURPOSITIVEPDV and CURNEGATIVEPDV
Description
l CURPOSITIVEPDV indicates the current positive packet delay variation (PDV).
l CURNEGATIVEPDV indicates the current negative PDV.
Attribute
Performance event cell PTP_N_PDV_15M (15-minute negative

PDV)
PTP_N_PDV_24H (24-hour negative PDV)
Unit ns
Impact on System
The less the PDV, the better the clock performance.

Related Alarms
When the PDV exceeds the acceptable range, the clock is unlocked and the
ACR_LOCK_FAIL alarm is reported.
B.3.7 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and

E1_LSES_SDH
Description
l The E1_LCV_SDH is a performance event indicating the E1 line side code violation
count.
l The E1_LLOSS_SDH is a performance event indicating the E1 line side loss-of-signal
seconds.
l The E1_LES_SDH is a performance event indicating the E1 line side code violation
errored second.
ES refers to a second in which one or more errored blocks are detected.
l The E1_LSES_SDH is a performance event indicating the E1 line side code violation
An SES refers to a certain second in which 30% or more errored blocks are detected or at
least one serious disturbance period (SDP) exists. The SDP refers to a period of at least
four consecutive blocks or 1 ms (taking the longer one) in which the BER of all the
consecutive blocks is equal to or higher than 10-2 or the signal is lost.
Attribute
Performance event cell LCV_BPVCNT
Unit Second (E1_LCV_SDH, E1_LLOSS_SDH,

E1_LES_SDH, and E1_LSES_SDH)

If bit errors occur in the services, you need to find out the causes and troubleshoot the
problem in a timely manner. Otherwise, the signal transmission quality will be affected.
Related Alarms
None
Possible Causes
l External causes:
– The fiber performance is degraded, and the fiber has extremely high attenuation.
– The fiber connector is dirty or incorrect.
– The equipment is improperly grounded.

– A strong interference source is present near the equipment.

– The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
l Equipment problems:
– The service code types are incorrect.
– The board becomes faulty, or the performance of the board is degraded.
Procedure
Step 1 First eliminate external causes, such as poor grounding, too high operating temperature, too
low or too high the receiving optical power of the line board.
Step 2 Check whether the correct E1 service code is selected. If not, modify the code of the services
received by a board by setting the code type of the board.
----End
B.3.8 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS
Description
l E1_BBE indicates the E1 background block error.
Background block error (BBE) refers to the errored blocks excluding the errored blocks
in the unavailable and severely errored seconds. This performance event can be detected
only when the E1 frame format is CRC-4.
l E1_ES indicates the E1 errored second.
Errored second (ES) refers to a second in which one or more errored blocks are detected.
l E1_SES indicates the E1 severely errored second.
Severely errored second (SES) refers to a second in which 30% or more than 30%
errored blocks exist or at least one severely disturbed period (SDP) exists. SDP is the
period in which the BER of all the consecutive blocks in a period of less than four
consecutive blocks or 1 ms (the longer period is applied) is equal to or higher than 10-2
or the signal is lost.
l E1_CSES indicates the E1 consecutive severely errored second.
Consecutive severely errored second (CSES) refers to a second in which the SES occurs
continuously for less than 10 seconds.
l E1_UAS indicates the E1 unavailable second.
The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs
included. When SESs disappear for 10 consecutive seconds, the available time begins
from the eleventh second, with the previous 10 seconds included.
Attribute
Performance event cell E1CRC_ERR_CNT

Unit Block (E1_BBE)

Second (E1_ES, E1_SES, E1_CSES, and
E1_UAS)
Impact on System
Excessive bit errors interrupt the service (the BER should be less than -3 for the voice service,
and 10-6 for the data service).
Related Alarms
None

Threshold Threshold
E1_BBE 1500 15000
E1_ES 50 100
E1_SES 20 50
E1_UAS 20 50
E1_CSES 4 (number of consecutive SESs)
Possible Causes
The system detects the E1 bit errors.
Procedure
Step 1 Check whether the frame format of the local E1 port is the same as that of the opposite port.
Step 2 Check whether the E1 cable is intact. If it is damaged, replace it.
Step 3 Use another E1 port.
Step 4 Troubleshoot the interconnected equipment.
----End
B.3.9 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and

FEC_UNCOR_BLOCK_CNT
Description
l FEC_BEF_COR_ER indicates the BER before the FEC is performed.
This event indicates the impact of the external environment on the transmission.

l FEC_COR_BYTE_CNT indicates the number of bytes corrected through the FEC.

This event indicates the impact of the FEC.
l FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be corrected
through the FEC.
This event indicates the number of blocks that cannot be corrected through the FEC.
Attribute
Performance event cell FECBEFCORER (FEC_BEF_COR_ER)

FECCORBYTECNT(FEC_COR_BYTE_C
NT)
FECUNCORBLOCKCNT
(FEC_UNCOR_BLOCK_CNT)
Unit None (FEC_BEF_COR_ER)

None (FEC_COR_BYTE_CNT)
Block (FEC_UNCOR_BLOCK_CNT)
Impact on System
If the value of FEC_BEF_COR_ER is very high, residual bit errors exist in the service after
the FEC is performed.
If the value of FEC_UNCOR_BLOCK_CNT is not zero, it can be inferred that bit errors that
cannot be corrected exist on a radio link. Bit errors exist in the service accordingly.
Related Alarms
If a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.
B.3.10 HPBBE, HPES, HPSES, HPCSES, and HPUAS

Description
l HPBBE indicates the higher order path background block error.
BBE refers to the errored blocks excluding the errored blocks in the unavailable and
severely errored seconds.
l HPES indicates the higher order path errored second.
l HPSES indicates the higher order path severely errored second.
SES refers to a second in which 30% or more than 30% errored blocks exist or at least
one SDP exists. SDP is the period in which the BER of all the consecutive blocks in a
period of less than four consecutive blocks or 1 ms (the longer period is applied) is equal
to or higher than 10-2 or the signal is lost.
l HPCSES indicates the higher order path consecutive severely errored second.
CSES refers to a second in which the SES occurs continuously for less than 10 seconds.

l HPUAS indicates the higher order path unavailable second.

Attribute
Performance event cell B3CNT
Unit Block (HPBBE)

Second (HPES, HPSES, HPCSES, and
HPUAS)
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Related Alarms
When the HPBBE, HPES, HPSES, or HPUAS performance event crosses the preset
threshold, the HP_CROSSTR alarm is reported.

Threshold Threshold
HPBBE 1500 15000
HPES 50 100
HPSES 20 50
HPUAS 20 50
Possible Causes
The system detects higher order path bit errors through the B3 byte.
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling.
----End

B.3.11 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS
Description
l HPFEBBE indicates the higher order path far end background block error.
Far end background block error (FEBBE) indicates that the BBE occurs at the opposite
end.
l HPFEES indicates the higher order path far end errored second.
FEES indicates that the ES occurs at the opposite end.
l HPFESES indicates the higher order path far end severely errored second.
FESES indicates that the SES occurs at the opposite end.
l HPFECSES indicates the higher order path far end consecutive severely errored second.
FECSES indicates that the CSES occurs at the opposite end.
l HPFEUAS indicates the higher order path far end unavailable second.
FEUAS indicates that the UAS occurs at the opposite end.
Attribute
Performance event cell PFEBE
Unit Block (HPFEBBE)

Second (HPFEES, HPFESES, HPFECSES,
and HPFEUAS)
Impact on System
Related Alarms
The HP_REI alarm is reported at the local end.
Possible Causes
The system detects the higher order path far end bit errors through bits 1 to 4 in the G1 byte.
Procedure
Step 1 Clear the corresponding performance event at the opposite end.
----End

B.3.12 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS
Description
l IF_BBE indicates the radio link background block error.
l IF_ES indicates the radio link errored second.
l IF_SES indicates the radio link severely errored second.
l IF_CSES indicates the radio link consecutively severely errored second.
l IF_UAS indicates the radio link unavailable second.
l IF_BER indicates the radio link bit error rate.
The BER is the number of bit errors divided by the total number of bits transferred on a
microwave link within a specified interval.
Attribute
Performance event cell IF_BIP8

IF_BER_15M(IF_BER)
IF_BER_24H(IF_BER)
Unit Block (IF_BBE)

Second (IF_ES, IF_SES, IF_CSES,
IF_UAS)
None (IF_BER)
Impact on System
Related Alarms
The MW_BER_SD or MW_BER_EXC alarm is reported when the BER crosses the specific
threshold.

Possible Causes
The system detects bit errors on the radio link through the bit error detection overheads in a
radio frame.
Procedure
----End
B.3.13 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG
Description
l IF_SNR_MAX indicates the maximum signal to noise ratio.
l IF_SNR_MIN indicates the minimum signal to noise ratio.
l IF_SNR_AVG indicates the average signal to noise ratio.
Attribute
Performance event cell IF_SNR(IF_SNR_MAX, IF_SNR_MIN)

IF_SNR_AVG_15M, and
IF_SNR_AVG_24H(IF_SNR_AVG)
Unit dB
Impact on System
A greater SNR value indicates a steady radio link; a smaller SNR value indicates a worse
radio link, errors and even interruptions occur on the radio link.
Related Alarms
None
B.3.14 IF_MSE_MAX, IF_MSE_MIN, IF_MSE_AVG, and

IF_MSE_CUR
Description
l IF_MSE_MAX indicates the maximum MSE.
l IF_MSE_MIN indicates the minimum MSE.
l IF_MSE_AVG indicates the average MSE.
l IF_MSE_CUR indicates the current MSE.

Attribute
Attribute Meaning
Performance event cell IF_MSE (IF_MSE_MAX, IF_MSE_MIN,

and IF_MSE_CUR)
IF_MSE_AVG_15M and
IF_MSE_AVG_24H (IF_MSE_AVG)
Unit dB

A larger absolute value of MSE indicates a higher link stability. If the absolute value of MSE
for a link is small, bit errors may occur or services may even be interrupted on the link.
Related Alarms
None
B.3.15 LPBBE, LPES, LPSES, LPCSES, and LPUAS
Description
l LPBBE indicates the lower order path background block error.
l LPES indicates the lower order path errored second.
l LPSES indicates the lower order path severely errored second.
l LPCSES indicates the lower order path consecutive severely errored second.
l LPUAS indicates the lower order path unavailable second.
Attribute
Performance event cell LPBIP2CNT

Unit Block (LPBBE)

Second (LPES, LPSES, LPCSES, and
LPUAS)
Impact on System
Related Alarms
When the LPBBE, LPES, LPSES, or LPUAS performance event crosses the preset threshold,
the LP_CROSSTR alarm is reported.

Threshold Threshold
LPBBE 1500 15000
LPES 50 100
LPSES 20 50
LPUAS 20 50
Possible Causes
The system detects lower order path bit errors through the BIP2 in the V5 byte (E1 interface
board or Hybrid IF board).
Procedure
----End
B.3.16 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS

Description
l LPFEBBE indicates the lower order path far end background block error.
FEBBE indicates that the BBE occurs at the opposite end.
l LPFEES indicates the lower order path far end errored second.
FEES indicates that the ES occurs at the opposite end.
l LPFESES indicates the lower order path far end severely errored second.
FESES indicates that the SES occurs at the opposite end.

l LPFECSES indicates the lower order path far end consecutive severely errored second.
FECSES indicates that the CSES occurs at the opposite end.
l LPFEUAS indicates the lower order path far end unavailable second.
FEUAS indicates that the UAS occurs at the opposite end.
Attribute
Performance event cell LPFEBE
Unit Block (LPFEBBE)

Second (LPFEES, LPFESES, LPFECSES,
and LPFEUAS)
Impact on System
Related Alarms
The LP_REI alarm is reported at the local end.
Possible Causes
The system detects the lower order path far end bit errors through bit 3 in the V5 byte.
Procedure
----End
B.3.17 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV

Description
l MAXFREQDEV indicates the maximum frequency offset.
l MINFREQDEV indicates the minimum frequency offset.
l AVGFREQDEV indicates the average frequency offset.
Attribute
Performance event cell PTP_DA
Unit ns

Impact on System
If the frequency offset exceeds the acceptable range, clock signals deteriorate.
Related Alarms
If the frequency offset exceeds the acceptable range, the SYN_BAD alarm is reported.
B.3.18 MAXMEANPATHDELAY, MINMEANPATHDELAY, and

AVGMEANPATHDELAY
Description
l MAXMEANPATHDELAY indicates the maximum path delay between the master and
slave clocks.
l MINMEANPATHDELAY indicates the minimum path delay between the master and
slave clocks.
l AVGMEANPATHDELAY indicates the average path delay between the master and slave
clocks.
Attribute
Performance event cell MAXMEANPATHDELAY

(MAXMEANPATHDELAY)
MINMEANPATHDELAY
(MINMEANPATHDELAY)
AVGMEANPATHDELAY
(AVGMEANPATHDELAY)
Unit ns
Impact on System
The deviation between the maximum and minimum path delays indicates the delay and jitter.
If the deviation exceeds the acceptable range, clock performance will be affected.
Related Alarms
None
B.3.19 MAXPHASEOFFSET, MINPHASEOFFSET, and

AVGPHASEOFFSET
Description
l MAXPHASEOFFSET indicates the maximum time deviation between the master and
slave clocks.

l MINPHASEOFFSET indicates the minimum time deviation between the master and
slave clocks.
l AVGPHASEOFFSET indicates the average time deviation between the master and slave
clocks.
Attribute
Performance event cell MAXPHASEOFFSET

(MAXPHASEOFFSET),
MINPHASEOFFSET
(MINPHASEOFFSET),
AVGPHASEOFFSET
(AVGPHASEOFFSET)
Unit ns
Impact on System
This performance indicates the time deviation between the local and upstream NEs. If the
time deviation exceeds the acceptable range (greater than 100 ns), the time of the upstream
NE cannot be locked, and NE time synchronization fails.
Related Alarms
When the time deviation between the master and slave clocks is greater than 100 ns, the
TIME_LOCK_FAIL alarm is reported.
B.3.20 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and

AVGPOSITIVEDELAY
Description
l MAXPOSITIVEDELAY indicates the maximum positive delay between the master and
slave clocks.
l MINPOSITIVEDELAY indicates the minimum positive delay between the master and
slave clocks.
l AVGPOSITIVEDELAY indicates the average positive delay between the master and
slave clocks.
Attribute
Performance event cell PTP_PTD
Unit ns

Impact on System
The deviation between the maximum and minimum positive delays indicates the delay and
jitter. If the deviation exceeds the acceptable range, clock performance will be affected.
Related Alarms
None
B.3.21 MEMUSAGEAVG, MEMUSAGECUR, MEMUSAGEMAX,

and MEMUSAGEMIN
Description
l MEMUSAGEMAX indicates the maximum memory usage.
l MEMUSAGEMIN indicates the minimum memory usage.
l MEMUSAGECUR indicates the current memory usage.
l MEMUSAGEAVG indicates the average memory usage.
Attribute
Performance event cell SYS_MEM_CONDITION
Unit Percentage (%)
Impact on System
The events have no impact on the system.
Related Alarms
None
B.3.22 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and

MPLS_PW_UAS
Description
l MPLS_PW_LS indicates the packet loss seconds of the PW service.
l MPLS_PW_SLS indicates the severe packet loss seconds of the PW service.
l MPLS_PW_CSLS indicates the consecutive severe packet loss seconds of the PW
service.
l MPLS_PW_UAS indicates the unavailable seconds of the PW service.

Attribute
Performance event cell MPLS_PW_FL
Unit s
Impact on System
The greater of the seconds of packets that are lost in one measurement period (for example, 15
minutes or 24 hours), the more packets are lost. Then, the QoS will be affected.
Procedure
Check the bandwidth utilization. If the bandwidth utilization equals to or exceeds the
specified bandwidth threshold, expand the network.
B.3.23 MPLS_PW_LS_N, MPLS_PW_SLS_N, MPLS_PW_CSLS_N,

and MPLS_PW_UAS_N
Description
l MPLS_PW_LS_N indicates packet loss seconds of PW services at the local end.
l MPLS_PW_SLS_N indicates severe packet loss seconds of PW services at the local end.
l MPLS_PW_CSLS_N indicates consecutive severe packet loss seconds of PW services at
the local end.
l MPLS_PW_UAS_N indicates unavailable seconds of PW services at the local end.
Attribute
Attribute Meaning
Performance event cell MPLS_PW_FLR_N
Unit Second

The larger the number of packet loss seconds in one measurement period (for example, 15
minutes or 24 hours), the more packets are lost, which seriously affects the quality of service.
Procedure
Check the bandwidth utilization. If the set bandwidth has been reached or exceeded, capacity
expansion is required.

B.3.24 MSBBE, MSES, MSSES, MSCSES, and MSUAS
Description
l MSBBE indicates the multiplex section background block error.
l MSES indicates the multiplex section errored second.
l MSSES indicates the multiplex section severely errored second.
l MSCSES indicates the multiplex section consecutive severely errored second.
l MSUAS indicates the multiplex section unavailable second.
Attribute
Unit Block (MSBBE)

Second (MSES, MSSES, MSCSES, and
MSUAS)
Impact on System
Related Alarms
When the MSBBE, MSES, MSSES, or MSUAS performance event crosses the preset
threshold, the MS_CROSSTR alarm is reported.

Threshold Threshold
MSBBE 1500 15000
MSES 50 100


Threshold Threshold
MSSES 20 50
MSUAS 20 50
Possible Causes
The system detects multiplex section bit errors through the B2 byte.
Procedure
Step 2 When an MSUAS performance event is reported, check whether cross-connections are
configured and whether fibers are properly connected at service ports. If cross-connections are
not configured, configure cross-connections again according to planning information; if fibers
are incorrectly connected, connect the fibers again according to planning information.
----End
B.3.25 MSFEBBE, MSFEES, MSFESES, MSFECSES, and

MSFEUAS
Description
l MSFEBBE indicates the multiplex section far end background block error.
Far end background block error (FEBBE) indicates that the BBE occurs at the opposite
end.
l MSFEES indicates the multiplex section far end errored second.
Far end errored second (FEES) indicates that the ES occurs at the opposite end.
l MSFESES indicates the multiplex section far end severely errored second.
Far end severely errored second (FESES) indicates that the SES occurs at the opposite
end.
l MSFECSES indicates the multiplex section far end consecutive severely errored second.
Far end consecutive severely errored second (FECSES) indicates that the CSES occurs at
the opposite end.
l MSFEUAS indicates the multiplex section far end unavailable second.
Far end unavailable second (FEUAS) indicates that the UAS occurs at the opposite end.
Attribute
Performance event cell LFEBE

Unit Block (MSFEBBE)

Second (MSFEES, MSFESES,
MSFECSES, and MSFEUAS)

Related Alarms
The MS_REI alarm is reported at the local end.
Possible Causes
The system detects multiplex section far end bit errors through the M1 byte.
Procedure
----End
B.3.26 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

Description
l OSPITMPMAX indicates the maximum temperature of a laser core.
l OSPITMPMIN indicates the minimum temperature of a laser core.
l OSPITMPCUR indicates the current temperature of a laser core.
Attribute
Performance event cell TMP
Unit °C
Impact on System
If the temperature of a laser core is very high or very low, the performance of the laser
degrades, and bit errors or other faults occur.
Relevant Alarms
None

B.3.27 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and

PG_IF_UAS
Description
l PG_IF_BBE indicates the protection group background block error.
in the unavailable and severely errored seconds.
l PG_IF_ES indicates the protection group errored second.
l PG_IF_SES indicates the protection group severely errored second.
l PG_IF_CSES indicates the protection group consecutive severely errored second.
l PG_IF_UAS indicates the protection group unavailable second.
Attribute
Performance event cell IF_BIP8
Unit Block (PG_IF_BBE)

Second (PG_IF_ES, PG_IF_SES,
PG_IF_CSES, and PG_IF_UAS)
Impact on System
Excessive bit errors interrupt the service (the BER should be less than -3 for the voice service,
and 10-6 for the data service).
Related Alarms
PG_LINK_FAIL, PG_PRT_DEGRADED

Threshold Threshold
PG_IF_BBE 1500 15000


Threshold Threshold
PG_IF_ES 50 100
PG_IF_SES 20 50
PG_IF_UAS 20 50
PG_IF_CSES 4 (number of consecutive SESs)
Possible Causes
The system detects the protection group bit errors.
Procedure
Step 1 See PG_LINK_FAIL, PG_PRT_DEGRADED.
----End
B.3.28 RPLMAX, RPLMIN, and RPLCUR

Description
l RPLMAX indicates the maximum receive optical power at an optical interface.
l RPLMIN indicates the minimum receive optical power at an optical interface.
l RPLCUR indicates the current receive optical power at an optical interface.
Attribute
Performance event cell IPM
Unit 0.1dBm
Impact on System
In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,
and 5 dB lower than the overload power.
If the receive optical power is very low or very high, bit errors occur and even services are
interrupted.
Related Alarms
l If the transmit optical power is lower than the receiver sensitivity, the IN_PWR_LOW
alarm is reported.
l If the receive optical power is higher than the overload power, the IN_PWR_HIGH
alarm is reported.

B.3.29 RSBBE, RSES, RSSES, RSCSES, and RSUAS
Description
l RSBBE indicates the regenerator section background block error.
in the unavailable and severely errored seconds.
l RSES indicates the regenerator section errored second.
l RSSES indicates the regenerator section severely errored second.
l RSCSES indicates the regenerator section consecutive severely errored second.
l RSUAS indicates the regenerator section unavailable second.
NOTE
When the IF board works in PDH mode, these performance events may also be reported. These events
are detected through the self-defined overhead byte B1 in the PDH radio frame.
Attribute
Unit Block (RSBBE)

Second (RSES, RSSES, RSCSES, and
RSUAS)
Impact on System
Related Alarms
When the RSBBE, RSES, RSSES, or RSUAS performance event crosses the preset threshold,
the RS_CROSSTR alarm is reported.


Threshold Threshold
RSBBE 1500 15000
RSES 50 100
RSSES 20 50
RSUAS 20 50
Possible Causes
The system detects the regenerator section bit errors through the B1 byte.
Procedure
Step 2 When an RSUAS performance event is reported, check whether cross-connections are
configured and whether fibers are properly connected at service ports. If cross-connections are
not configured, configure cross-connections again according to planning information; if fibers
are incorrectly connected, connect the fibers again according to planning information.
----End
B.3.30 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG
Description
l RSL_MAX indicates the maximum radio received signal level.
l RSL_MIN indicates the minimum radio received signal level.
l RSL_CUR indicates the current radio received signal level.
l RSL_AVG indicates the average radio received signal level.
Attribute
Performance event cell RSL
Unit 0.1dBm
Impact on System
When the radio received signal level is very low or very high, bit errors occur and even

Related Alarms
If the radio received signal level crosses the specific threshold, the RADIO_RSL_HIGH or
RADIO_RSL_LOW alarm is reported.
B.3.31 RSOOF and RSOFS
Description
l RSOOF indicates the regenerator section out of frame.
The out-of-frame (OOF) block refers to a data block in which incorrect A1 and A2 bytes
are detected.
l RSOFS indicates the regenerator section out-of-frame second.
The out-of-frame second (OFS) refers to a second in which one or more OOF blocks are
detected.
Attribute
Performance event cell OOF
Unit Block (RSOOF)

Second (RSOFS)
Impact on System
The system discards OOF data blocks. Therefore, an RSOOF event is equivalent to a big error
(if one RSOOF exists in a second, the BER is not less than 1.25 x 10-5).
Related Alarms
If RSOOF is received in five consecutive frames, the equipment changes to the OOF state. If
the OOF state lasts for 3 ms, the R_LOF alarm is reported and all the services are interrupted.
Possible Causes
The system detects incorrect A1 and A2 bytes.
Procedure
Step 1 If the R_LOF alarm, as well as the performance event, is reported, eliminate the errors
according to the alarm. Otherwise, see 5.4 Troubleshooting Bit Errors in TDM Services for
handling.
----End

B.3.32 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16,

QAMWS32, QAMWS64, QAMWS128, QAMWS256, QAMWS512,
QAM_L_WS512, QAMWS1024, QAM_L_WS1024, QAMWS2048,
QAMWS4096
Description
l QPSKWS indicates the working duration of the QPSK mode.
l QPSK_S_WS indicates the working duration of the QPSKWS Strong mode.
l QAMWS16 indicates the working duration of the 16QAM mode.
l QAM_S_WS16 indicates the working duration of the 16QAM Strong mode.
l QAM_L_WS512 indicates the working duration of the 512QAM Light mode.
l QAM_L_WS1024 indicates the working duration of the 1024QAM Light mode.
Attribute
Performance event cell QPSKWSSECOND (QPSK)

QPSK_S_WSSECOND (QPSK Strong)
QAMWS16SECOND (16QAM)
QAM_S_WS16SECOND (16QAM Strong)
QAM_L_WS512SECOND (512QAM
Light)
QAM_L_WS1024SECOND (1024QAM
Light)

Unit Second
Impact on System
When the AM function is disabled, the performance event does not affect the system.
When the AM function is enabled, in normal cases, the seconds of the modulation scheme for
maximum capacity should account for a larger percentage. In the duration set for good
weather, if the seconds of the low-efficiency modulation scheme account for a larger
percentage, the performance of the radio link is abnormal.
Related Alarms
None
B.3.33 TLBMAX, TLBMIN, and TLBCUR
Description
l TLBMAX indicates the maximum transmit bias current of the laser.
l TLBMIN indicates the minimum transmit bias current of the laser.
l TLBCUR indicates the current transmit bias current of the laser.
Attribute
Performance event cell LSBCM
Unit 0.1 mA
Impact on System
If the bias current of the laser is over-high or over-low, the laser is damaged.
Related Alarms
If the receive optical power on the opposite NE is abnormal, the IN_PWR_ABN alarm is
reported.
B.3.34 RLHTT, RLLTT, TLHTT, TLLTT
Description
l The RLHTT indicates the duration when the ODU at the local end has a receive power
lower than the upper threshold.

l The RLLTT indicates the duration when the ODU at the local end has a receive power
lower than the lower threshold.
l The TLHTT indicates the duration when the ODU at the local end has a transit power
higher than the upper threshold.
l The TLLTT indicates the duration when the ODU at the local end has a transit power
higher than the lower threshold.
Attribute
Performance event cell RLHTS(RLHTT), RLLTS(RLLTT),

TLHTS(TLHTT), and TLLTS(TLLTT)
Unit Second
Impact on System
When the receive power of an ODU is lower than the receiver sensitivity, bit errors occur and
services may even be interrupted.
Related Alarms
None
B.3.35 TPLMAX, TPLMIN, and TPLCUR

Description
l TPLMAX indicates the maximum transmit optical power at an optical interface.
l TPLMIN indicates the minimum transmit optical power at an optical interface.
l TPLCUR indicates the current transmit optical power at an optical interface.
Attribute
Performance event cell OPM
Unit 0.1dBm
Impact on System
In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,
and 5 dB lower than the overload power.
If the transmit optical power is very low or very high, the receive optical power at the
opposite site is accordingly very low or very high. As a result, bit errors occur and even

Related Alarms
l If the transmit optical power at the opposite site is lower than the receiver sensitivity, the
IN_PWR_LOW alarm is reported.
l If the receive optical power at the opposite site is higher than the overload power, the
IN_PWR_HIGH alarm is reported.
B.3.36 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Description
l TSL_MAX indicates the maximum radio transmitted signal level.
l TSL_MIN indicates the minimum radio transmitted signal level.
l TSL_CUR indicates the current radio transmitted signal level.
l TSL_AVG indicates the average radio transmitted signal level.
Attribute
Performance event cell TSL
Unit 0.1dBm
Impact on System
When the radio transmitted signal level is very low or very high, the radio received signal
level at the opposite site is very low or very high. As a result, bit errors occur and even
Related Alarms
If the radio transmitted signal level is not within the range supported by the ODU, the
RADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.
B.3.37 TUPJCHIGH, TUPJCLOW, and TUPJCNEW

Description
l TUPJCHIGH indicates the count of positive TU pointer justifications.
l TUPJCLOW indicates the count of negative TU pointer justifications.
l TUPJCNEW indicates the count of new TU pointer justifications.

Attribute
Performance event cell TUPPJE (TUPJCHIGH)

TUNPJE (TUPJCLOW)
TUNDF (TUPJCNEW)
Unit Block
Impact on System
Less than six TUPJCHIGH and TUPJCLOW events on each port do not affect the system. If
the pointer is justified for many times, or the TUPJCNEW event occurs, bit errors may occur
in the service.
Related Alarms
When the TUPJCHIGH, TUPJCLOW, or TUPJCNEW performance event crosses the preset
threshold, the HPAD_CROSSTR alarm is reported.

Threshold Threshold
TUPJCHIGH 1500 30000
TUPJCLOW 1500 30000
TUPJCNEW 1500 30000
Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.
----End
B.3.38 XPD_MAX, XPD_MIN and XPIC_XPD_VALUE
Description
XPD_MAX indicates the maximum XPD value within 15 minutes or 24 hours.
XPD_MIN indicates the minimum XPD value within 15 minutes or 24 hours.
XPIC_XPD_VALUE indicates the XPD value after the XPIC function is enabled.

Attribute
Performance event cell XPD
Unit dB
Impact on System
l XPD_MAX and XPD_MIN: The events have no impact on the system.
l XPIC_XPD_VALUE: When the XPIC function is disabled, the performance event does
not affect the system.
l XPIC_XPD_VALUE: When the XPIC function is enabled, a greater XPD value indicates
less interference between H and V polarization directions and better signaling
environment; a smaller XPD value indicates more interference and worse signaling
environment. If the XPD value is smaller than a specific value, errors and even
interruptions occur on the radio link.
Related Alarms
None

Maintenance Guide C RMON Event Reference
C RMON Event Reference
RMON events reflect the running of the Ethernet services. This chapter describes the possible
RMON events on the OptiX RTN 980 and how to handle these events.
C.1 List of RMON Alarm Entries

The RMON alarm entries refer to the table entries in the RMON alarm group.
C.2 RMON Performance Entries List on the Packet-Plane
This section lists RMON performance entries on the packet plane by logical board.
C.3 RMON Performance Entries List on the EoS/EoPDH-Plane
This section lists RMON performance entries on the EoS/EoPDH plane by board type.
C.4 RMON Events and Handling Procedures
This chapter describes the RMON events that indicate Ethernet service abnormalities and how
to handle these events.

C.1 List of RMON Alarm Entries

The RMON alarm entries refer to the table entries in the RMON alarm group.
Table C-1 List of RMON alarm entries

Alarm Description Remarks Source
Name
ETHDR The number of packet ETHDROP indicates the ISU2, ISX2, IFU2,
OP loss events number of packet loss IFX2, ISV3, ISM6,
events caused by EG2D, EM6FA,
insufficient Ethernet EM6TA, EM6, EG4,
chip resources. The EG4P, EM6T, EM6F
count is not the number
of discarded packets but
the number of times
packet loss is detected.
ETHEX The number of frames Indicates the number of EG2D, EM6T, EM6F,
CCOL that fail to be frames that fail to be EM6FA, EM6TA, EM6,
transmitted after transmitted due to EG4, EG4P
continuous collisions consecutive collisions.
ETHLAT The number of Indicates the number of

ECOL collisions that are collisions that are
detected after a timeslot detected after a timeslot
period elapses period elapses. The late
collisions indicate that
the diameter of a LAN
is too large.
TXDEFF The number of frames Indicates the number of

RM whose transmission is frames whose first
delayed transmission is delayed
because transmission
media are busy,
excluding the number of
frames whose
transmission is delayed
due to collisions.
ETHUN The number of received Undersized packets are EG2D, EM6T, EM6F,
DER undersized packets the packets shorter than EM6FA, EM6TA, EM6,
64 bytes (including FCS EG4, EG4P
bytes but not framing
bits).


Name
ETHOV The number of received Indicates the number of

ER oversized packets received packets that are
longer than MTU bytes
(including FCS bytes
but not framing bits)
and do not contain any
other errors.
ETHFRG The number of received ETHFRG indicates the

fragmented packets number of received
packets that are shorter
than 64 bytes (including
FCS bytes but not
framing bits) and
contain FCS errors or
alignment errors.
ETHJAB The number of received Indicates the total

errored oversized number of received
packets packets that are longer
than MTU bytes
and contain FCS errors
or alignment errors.
RXBBA The number of bytes in FCS bytes are included ISU2, ISX2, IFU2,
D received bad packets but framing bits are IFX2, ISV3, ISM6,
excluded. EG2D, EM6FA,
EM6TA, EM6, EG4,
ETHFCS The number of frames FCS error frames EG4P, EM6T, EM6F
that have FCS check exclude oversized
errors frames and undersized
frames.
PORT_R Indicates the bandwidth Bandwidth utilization

X_BW_ utilization at a port in ratio = (Number of
UTILIZ the receive direction. received bytes x 8/
ATION Monitoring period)/
Configured or actual
bandwidth
PORT_T Indicates the bandwidth Bandwidth utilization

X_BW_ utilization at a port in ratio = (Number of
UTILIZ the transmit direction. transmitted bytes x 8/
ATION Monitoring period)/
bandwidth


Name
PORT_R Indicates the average Average bandwidth IFU2, IFX2, ISU2,

X_BW_ bandwidth utilization on utilization on a specified ISX2, ISV3, ISM6,
UTILIZ a port in the receive port in the receive EM6F, EM6T, EM6FA,
ATION_ direction. direction = (Number of EM6TA, EG2D, EM6,
AVG received bytes x 8/ EG4, EG4P, EX1
Monitoring period)/
bandwidth
PORT_R Indicates the maximum Maximum bandwidth

X_BW_ bandwidth utilization on utilization on a specified
UTILIZ a port in the receive port in the receive
ATION_ direction. direction = (Number of
MAX received bytes x 8/
Monitoring period)/
bandwidth
PORT_R Indicates the minimum Minimum bandwidth

UTILIZ a port in the receive port in the receive
MIN received bytes x 8/
Monitoring period)/
bandwidth
PORT_T Indicates the average Average bandwidth

UTILIZ a port in the transmit port in the transmit
AVG transmitted bytes x 8/
Monitoring period)/
bandwidth
PORT_T Indicates the maximum Maximum bandwidth

MAX transmitted bytes x 8/
Monitoring period)/
bandwidth


Name
PORT_T Indicates the minimum Minimum bandwidth

MIN transmitted bytes x 8/
Monitoring period)/
bandwidth
Table C-2 List of EMS6\EFP8 RMON alarm entries

Name
ETHDR The number of packet ETHDROP indicates the EMS6, EFP8

OP loss events number of packet loss
events caused by
insufficient Ethernet
chip resources. The
count is not the number
of discarded packets but
the number of times
packet loss is detected.
RXBBA The number of bytes in FCS bytes are included

D received bad packets but framing bits are
excluded.
ETHUN The number of received Undersized packets are

DER undersized packets the packets shorter than
64 bytes (including FCS
bytes but not framing
bits).
ETHOV The number of received Indicates the number of

ER oversized packets received packets that are
longer than MTU bytes
and do not contain any
other errors.


Name
ETHFRG The number of received ETHFRG indicates the

fragmented packets number of received
packets that are shorter
than 64 bytes (including
FCS bytes but not
framing bits) and
contain FCS errors or
alignment errors.
ETHJAB The number of received Indicates the total

errored oversized number of received
packets packets that are longer
than MTU bytes
and contain FCS errors
or alignment errors.
ETHFCS The number of frames FCS error frames

that have FCS check exclude oversized
errors frames and undersized
frames.
ETHALI The number of An alignment error

alignment error frames means that the frame
contains a fractional
number of bytes and
fails to pass the FCS
check.
C.2 RMON Performance Entries List on the Packet-Plane

This section lists RMON performance entries on the packet plane by logical board.
C.2.1 EM6F/EM6T/EM6FA/EM6TA
The RMON performance that the EM6F/EM6T/EM6FA/EM6TA board supports includes
basic performance, extended performance, port traffic classification performance, port priority
performance, and Port DS domain performance.

NOTE
The current performance statistics of an RMON performance item are the count of performance events
within the current sampling period (which is usually a few seconds). The historical performance
statistics of an RMON performance item are calculated using the corresponding method based on counts
in sampling periods within a specific statistical period. The following table lists calculation methods for
historical performance statistics.
Performance Counting Calculation Method

Method
Accumulated value Accumulates the counts in all sampling periods within a statistical
period and takes the accumulated value as the historical
performance count.
Maximum value obtained Takes the maximum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Minimum value obtained Takes the minimum value among counts in all sampling periods
Value obtained in the last Takes the count of the last sampling period within a statistical
sampling period period as the historical performance count.
Average value of counts in all Takes the average value of counts in all sampling periods within a
sampling periods statistical period as the historical performance count.
Table C-3 Basic performance entry list (EM6F/EM6T/EM6FA/EM6TA)

Brief Full Perform Perform Remarks
Name of Name of ance ance
a a Count Countin
Perform Perform Unit g
ance ance Method
Entry Entry
Indicates Packets Accumul

the ated
packets value Bad packets, broadcast packets, and multicast packets are
RXPKTS received. included.
ETHDRO Indicates Times Accumul ETHDROP indicates the number of packet loss events
P the ated caused by insufficient Ethernet chip resources. The count is
packet value not the number of discarded packets but the number of times
loss packet loss is detected.
events.
RXOCTE Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
TS the bytes ated packets (including bad packets), including framing bits but
received. value not FCS bytes.
NOTE
If the packets received by an EM6T/EM6F board are larger than
MTU, byte count is calculated based on the MTU.
If the packets received by an EM6FA/EM6TA board are larger than
the MTU, byte count is calculated based on actual packet size.


a a Count Countin
ance ance Method
Entry Entry
RXMUL Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
multicast value broadcast packets.
packets
received.
RXBRD Indicates Packets Accumul RXMULCAST indicates the total number of received good
broadcast value broadcast packets.
packets
received.
ETHOVE Indicates Packets Accumul Indicates the number of received packets that are longer than
R the ated MTU bytes (including FCS bytes but not framing bits) and
oversized value do not contain any other errors.
packets
received.
ETHJAB Indicates Packets Accumul Indicates the total number of received packets that are longer
the ated than MTU bytes (including FCS bytes but not framing bits)
oversized value and contain FCS errors or alignment errors.
error
packets
received.
ETHUN Indicates Packets Accumul Undersized packets are the packets shorter than 64 bytes
DER the ated (including FCS bytes but not framing bits).
undersize value
d packets
received.
ETHFRG Indicates Packets Accumul ETHFRG indicates the number of received packets that are
the ated shorter than 64 bytes (including FCS bytes but not framing
fragments value bits) and contain FCS errors or alignment errors. Increase of
received. the count is normal because noise collisions exist.
ETHCOL Indicates Times Accumul -

the ated
collisions value
.


a a Count Countin
ance ance Method
Entry Entry
PORT_R Indicates 0.0001 Average Bandwidth utilization = (Number of received bytes x 8/

X_BW_U the value of Monitoring period)/Configured or actual bandwidth
TILIZATI bandwidt counts in
ON h all
utilization sampling
on a port periods
in the
receive
direction.
PORT_T Indicates 0.0001 Average Bandwidth utilization = (Number of transmitted bytes x 8/

ON h all
on a port periods
in the
transmit
direction.
Table C-4 Extended performance entry list (EM6F/EM6T/EM6FA/EM6TA)

a a Count Countin
ance ance Method
Entry Entry
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
transmitte
d.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted packets
TS the bytes ated (including bad packets), including framing bits but not FCS
transmitte value bytes.
d
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an integral
the FCS ated number of octets in length but do not pass the FCS check.
errored value NOTE
frames. This count does not include undersized frames and oversized
frames.


a a Count Countin
ance ance Method
Entry Entry
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
received
good
packets.
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
transmitte
d good
packets.
RXBBA Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the bytes ated
in value
received
bad
packets.
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmitte
d.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast packets.
AST the ated
unicast value
packets
received.
TXMUL Indicates Packets Accumul The multicast packets that are discarded or fail to be
CAST the ated transmitted are included.
multicast value
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
broadcast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
EED frame sampling
bytes period
transmitte
d.
RXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
received.
TXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
RXPAUS Indicates Frames Accumul RXPAUSE indicates the number of MAC flow control
E the pause ated frames with the PAUSE opcode.
frames value
received.
TXPAUS Indicates Frames Accumul TXPAUSE indicates the number of MAC flow control
frames value
transmitte
d.
ETHLAT Indicates Times Accumul Indicates the number of collisions that are detected after a
ECOL the late ated timeslot period elapses. The late collisions indicate that the
collisions value diameter of a LAN is too large.
.


a a Count Countin
ance ance Method
Entry Entry
ETHEXC Indicates Frames Accumul -

COL the ated
frames value
unsuccess
fully
transmitte
d after
consecuti
ve
collisions
.
TXDEFF Indicates Frames Accumul Indicates the number of frames whose first transmission is
RM the ated delayed because transmission media are busy, excluding the
frames value number of frames whose transmission is delayed due to
that are collisions.
deferred
in
transmissi
on.
RX_DRO Packet 0.0001 Average The discarded packets ratio in the ingress direction, that is,
P_RATIO loss rate value of number of actually drop packets/received packets.
in the counts in
ingress all
direction sampling
periods
TX_DRO Packet 0.0001 Average The discarded packets ratio in the ingress direction, that is,
P_RATIO loss rate value of number of actually drop packets/transmitted packets.
in the counts in
egress all
direction sampling
periods
ETH_RX Indicates kbit/s Maximu Maximum throughput = Number of received bytes

_THROU the m value (including inter-frame gaps and preambles)/Monitoring
GHPUT_ maximum obtained period
MAX throughp among all
ut on a sampling
port in periods
the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
ETH_RX Indicates kbit/s Minimum Minimum throughput = Number of received bytes (including
_THROU the value inter-frame gaps and preambles)/Monitoring period
GHPUT_ minimum obtained
MIN throughp among all
ut on a sampling
port in periods
the
receive
direction.
ETH_RX Indicates kbit/s Average Average throughput = Number of received bytes (including
_THROU the value of inter-frame gaps and preambles)/Monitoring period
GHPUT_ average counts in
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.
Indicates kbit/s Maximu

the m value
maximum obtained
ETH_TX transmit among all
_THROU throughp sampling Throughput at the transmit direction = Total number of
GHPUT_ ut of a periods received bytes (including the preamble and frame gap)/
MAX port. Measurement period
Indicates kbit/s Minimum

the value
minimum obtained
MIN port. Measurement period
Indicates kbit/s Average

the value of
average counts in
ETH_TX transmit all
AVG port. Measurement period


a a Count Countin
ance ance Method
Entry Entry

the ated
packet value
loss count
in the
TX_DRO transmit
P_PKTS direction. -

the ated
packet value
loss count
in the
RX_DRO receive
P_PKTS direction. -
RXBPS Indicates Bits/s Value Bit rate in the receive direction = Number of received bytes
the bit obtained x 8/Monitoring period
rate in the in the last
receive sampling
direction period
of an
Ethernet
port.
TXBPS Indicates Bits/s Value Bit rate in the transmit direction = Number of transmitted
the bit obtained bytes x 8/Monitoring period
transmit sampling
direction period
of an
Ethernet
port.
RXPPS Indicates Packets/s Value Packet rate in the receive direction = Number of received
the obtained packets/Monitoring period
packet in the last
rate in the sampling
receive period
direction
of an
Ethernet
port.


a a Count Countin
ance ance Method
Entry Entry
TXPPS Indicates Packets/s Value Packet rate in the transmit direction = Number of transmitted
packet in the last
transmit period
direction
of an
Ethernet
port.
RXBRD Broadcast 0.0001 Average Ratio of broadcast and multicast packets to all packets in the
CAST_R traffic value of receive direction
ATIO ratio in counts in
the all
receive sampling
direction periods
TXBRDC Broadcast 0.0001 Average Ratio of broadcast and multicast packets to all packets in the
AST_RA traffic value of transmit direction
TIO ratio in counts in
the all
transmit sampling
direction periods
PORT_R Indicates 0.0001 Average Average bandwidth utilization on a specified port in the
X_BW_U the value of receive direction = (Number of received bytes x 8/
TILIZATI average counts in Monitoring period)/Configured or actual bandwidth
ON_AVG bandwidt sampling
h periods
utilization
on a port
in the
receive
direction.
Indicates 0.0001 Maximu Maximum bandwidth utilization on a specified port in the

the m value receive direction = (Number of received bytes x 8/
maximum of counts Monitoring period)/Configured or actual bandwidth
bandwidt in
h sampling
PORT_R utilization periods
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.


a a Count Countin
ance ance Method
Entry Entry
Indicates 0.0001 Minimum Minimum bandwidth utilization on a specified port in the

the value of receive direction = (Number of received bytes x 8/
minimum counts in Monitoring period)/Configured or actual bandwidth
bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.
Indicates 0.0001 Average Average bandwidth utilization on a specified port in the

the value of transmit direction = (Number of transmitted bytes x 8/
average counts in Monitoring period)/Configured or actual bandwidth
bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.

the m value transmit direction = (Number of transmitted bytes x 8/
bandwidt in
h sampling
PORT_T utilization periods
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.

Table C-5 Port traffic classification performance entry list (EM6F/EM6T/EM6FA/EM6TA)

a a Count Countin
ance ance Method
Entry Entry
QOS_PO Indicates Packets Accumul -

RTCAR_ the ated
MarkedR number value
edPKTS of red
packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
MarkedY number value
ellowPK of yellow
TS packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
MarkedG number value
reenPKT of green
S packets
after
traffic
monitorin
g is
enabled.

RTSTRM the ated
_RCVM number value
ATCHPK of
TS packets
received
in the
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_SNDM number value
ATCHPK of
TS packets
transmitte
d in the
matched
flow.
PORTST Indicates Packets Accumul -

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarded
due to
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
PORTST Indicates 0.0001 Value Packet loss rate in the egress direction = Number of
RM_SHA the ratio obtained discarded packets in the egress direction/Number of packets
PING_D of packet in the last matching the traffic classification rule in the egress direction
ROPRAT loss due sampling
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.


a a Count Countin
ance ance Method
Entry Entry
QOS_PO Indicates 0.0001 Value Proportion of packets marked in red in the ingress direction
RTCAR_ the obtained = Number of packets marked in red in the ingress direction/
MarkedR proportio in the last Number of packets matching the traffic classification rule in
edRATIO n of sampling the ingress direction
packets period
marked in
red when
the traffic
policing
function
is
enabled.
QOS_PO Indicates Packets/s Value Packet rate in the receive direction = Number of received
RTSTRM the obtained packets/Monitoring period
_RX_PPS packet in the last
receive period
direction
of a
matched
flow.
QOS_PO Indicates Packets/s Value Packet rate in the transmit direction = Number of transmitted
_TX_PPS packet in the last
transmit period
direction
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry
QOS_PO Indicates Bytes Accumul -

RTSTRM the ated
_RCVM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
received
packets
of a
matched
flow.

RTSTRM the ated
_SNDM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
transmitte
d packets
of a
matched
flow.
QOS_PO Indicates Bits/s Value Bit rate in the receive direction = Number of received bytes
RTSTRM the bit obtained (including inter-frame gaps and preambles) x 8/Monitoring
_RX_BP rate in the in the last period
S receive sampling
direction period
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry
QOS_PO Indicates Bits/s Value Bit rate in the transmit direction = Number of transmitted
RTSTRM the bit obtained bytes (including inter-frame gaps and preambles) x 8/
_TX_BP rate in the in the last Monitoring period
S transmit sampling
direction period
of a
matched
flow.
Table C-6 Port priority performance entry list (EM6F/EM6T/EM6FA/EM6TA)

a a Count Countin
ance ance Method
Entry Entry
QOS_PO Indicates 0.0001 Average Packet loss rate in an egress queue = Number of discarded
RTQUEU the ratio value of packets with a priority in the egress queue/Number of
E_DROP of packet counts in packets with the priority in the egress queue
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.
QOS_PRI Indicates Packets Accumul -

_DROPP the ated
KTS number value
of
packets
discarded
in the
services
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry
QOS_PRI Indicates Bytes Accumul -

_DROPB the ated
YTES number value
of bytes
discarded
in the
services
with
different
priorities.
PORT_P Indicates Packets Accumul -

RI_SNDP the ated
KTS number value
of
packets
transmitte
d in
egress
queues
with
different
priorities.
PORT_P Indicates Bytes Accumul -

RI_SND the ated
BYTES number value
of bytes
in the
packets
transmitte
d in
egress
queues
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry
PORT_P Indicates Bits/s Value Bit rate = Number of transmitted bytes x 8/Monitoring
RI_TX_B the bit obtained period
PS rates of in the last
egress sampling
queues period
with
different
priorities
in the
transmit
direction.
PORT_P Indicates Packets/s Value Packet rate = Number of transmitted packets/Monitoring

RI_TX_P the obtained period
PS packet in the last
rate of sampling
egress period
queues
with
different
priorities
in the
transmit
direction.

Table C-7 Port DS domain performance entry list (EM6F/EM6T/EM6FA/EM6TA)

a a Count Countin
ance ance Method
Entry Entry
DS_CVL Indicates Packets Accumul -

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the DS
domain
DS_CVL Indicates Bytes Accumul -

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the DS
domain.
DS_SVL Indicates Packets Accumul -

ANPRI_P the ated
KTS number value
of
packets
with
matched
S-VLAN
priorities
in the DS
domain.


a a Count Countin
ance ance Method
Entry Entry
DS_SVL Indicates Bytes Accumul -

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the DS
domain.
DS_DSC Indicates Packets Accumul -

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the DS
domain.
DS_DSC Indicates Bytes Accumul -

P_BYTE the ated
S number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the DS
domain.
NOTE
Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic classifications or
port DS domains.

Table C-8 LAG performance entry list (EM6F/EM6T/EM6FA/EM6TA)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.
NOTE
If the packets received by an /EG2D/EX1 board are larger than the
MTU, byte count is calculated based on actual packet size.
packets
received.
packets
received.
packets
received.
error
packets
received.


a a Count Countin
ance ance Method
Entry Entry
undersize value
d packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
the ated included.
packets value
transmitte
d.
d
errored value NOTE
frames.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
frames value
received.
frames value
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
C.2.2 EG2D
The RMON performance that the EG2D board supports includes basic performance, extended
performance, port traffic classification performance, port priority performance, and Port DS
domain performance.

NOTE

Method
performance count.
Table C-9 Basic performance entry list (EG2D)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.
NOTE


a a Count Countin
ance ance Method
Entry Entry
packets
received.
packets
received.
packets
received.
error
packets
received.
undersize value
d packets
received.

the ated
collisions value
.


a a Count Countin
ance ance Method
Entry Entry

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
Table C-10 Extended performance entry list (EG2D)

a a Count Countin
ance ance Method
Entry Entry
the ated included.
packets value
transmitte
d.
d
errored value NOTE
frames.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
frames value
received.
frames value
transmitte
d.
.


a a Count Countin
ance ance Method
Entry Entry

COL the ated
frames value
unsuccess
fully
transmitte
d after
consecuti
ve
collisions
.
deferred
in
transmissi
on.
P_RATIO loss rate value of number of actually drop packets/ received packets.
in the counts in
ingress all
direction sampling
periods
P_RATIO loss rate value of number of actually drop packets/ transmitted packets.
in the counts in
egress all
direction sampling
periods

ut on a sampling
port in periods
the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
ut on a sampling
port in periods
the
receive
direction.
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.

the m value
maximum obtained

the value
minimum obtained

the value of
average counts in
ETH_TX transmit all


a a Count Countin
ance ance Method
Entry Entry

the ated
packet value
loss count
in the
TX_DRO transmit
P_PKTS direction. -

the ated
packet value
loss count
in the
RX_DRO receive
P_PKTS direction. -
receive sampling
direction period
of an
Ethernet
port.
transmit sampling
direction period
of an
Ethernet
port.
packet in the last
receive period
direction
of an
Ethernet
port.


a a Count Countin
ance ance Method
Entry Entry
packet in the last
transmit period
direction
of an
Ethernet
port.
the all
receive sampling
direction periods
the all
transmit sampling
direction periods
h periods
utilization
on a port
in the
receive
direction.
PORT_R Indicates 0.0001 Maximu Maximum bandwidth utilization on a specified port in the
X_BW_U the m value receive direction = (Number of received bytes x 8/
TILIZATI maximum of counts Monitoring period)/Configured or actual bandwidth
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
PORT_R Indicates 0.0001 Minimum Minimum bandwidth utilization on a specified port in the
TILIZATI minimum counts in Monitoring period)/Configured or actual bandwidth
ON_MIN bandwidt sampling
h periods
utilization
on a port
in the
receive
direction.
PORT_T Indicates 0.0001 Average Average bandwidth utilization on a specified port in the
X_BW_U the value of transmit direction = (Number of transmitted bytes x 8/
h periods
utilization
on a port
in the
transmit
direction.
PORT_T Indicates 0.0001 Maximu Maximum bandwidth utilization on a specified port in the
X_BW_U the m value transmit direction = (Number of transmitted bytes x 8/
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
transmit
direction.
PORT_T Indicates 0.0001 Minimum Minimum bandwidth utilization on a specified port in the
h periods
utilization
on a port
in the
transmit
direction.

Table C-11 Port traffic classification performance entry list (EG2D)

a a Count Countin
ance ance Method
Entry Entry

RTCAR_ the ated
edPKTS of red
packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
ellowPK of yellow
TS packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
reenPKT of green
S packets
after
traffic
monitorin
g is
enabled.

RTSTRM the ated
_RCVM number value
ATCHPK of
TS packets
received
in the
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_SNDM number value
ATCHPK of
TS packets
transmitte
d in the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarded
due to
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.


a a Count Countin
ance ance Method
Entry Entry
packets period
marked in
red when
the traffic
policing
function
is
enabled.
receive period
direction
of a
matched
flow.
transmit period
direction
of a
matched
flow.

Table C-12 Port priority performance entry list (EG2D)

a a Count Countin
ance ance Method
Entry Entry
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.

_DROPP the ated
KTS number value
of
packets
discarded
in the
services
with
different
priorities.

_DROPB the ated
YTES number value
of bytes
discarded
in the
services
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmitte
d in
egress
queues
with
different
priorities.

RI_SND the ated
BYTES number value
of bytes
in the
packets
transmitte
d in
egress
queues
with
different
priorities.
egress sampling
queues period
with
different
priorities
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry

rate of sampling
egress period
queues
with
different
priorities
in the
transmit
direction.
Table C-13 Port DS domain performance entry list (EG2D)

a a Count Countin
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the DS
domain


a a Count Countin
ance ance Method
Entry Entry

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the DS
domain.

ANPRI_P the ated
KTS number value
of
packets
with
matched
S-VLAN
priorities
in the DS
domain.

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the DS
domain.


a a Count Countin
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the DS
domain.

P_BYTE the ated
S number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the DS
domain.
Table C-14 LAG performance entry list (EG2D)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.


a a Count Countin
ance ance Method
Entry Entry
NOTE
packets
received.
packets
received.
packets
received.
error
packets
received.
undersize value
d packets
received.


a a Count Countin
ance ance Method
Entry Entry

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
the ated included.
packets value
transmitte
d.
d
errored value NOTE
frames.
OD the bytes ated
in value
received
good
packets.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
frames value
received.
frames value
transmitte
d.
h periods
utilization
on a port
in the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
receive
direction.
h periods
utilization
on a port
in the
receive
direction.
h periods
utilization
on a port
in the
transmit
direction.
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
transmit
direction.
NOTE
port DS domains.
C.2.3 EX1
The RMON performance that the EX1 board supports includes basic performance, extended
performance, port traffic classification performance, port priority performance, and Port DS
domain performance.
NOTE

Method
performance count.

Table C-15 Basic performance entry list (EX1)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.
NOTE
packets
received.
packets
received.
packets
received.
error
packets
received.


a a Count Countin
ance ance Method
Entry Entry
undersize value
d packets
received.

the ated
collisions value
.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
4 received ated
(64 bytes value
in length)
5 received ated
(65-127 value
bytes in
length)


a a Count Countin
ance ance Method
Entry Entry
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)
12 received ated
(512-102 value
3 bytes in
length)
RXPKT1 Packets Packets Accumul Indicates the total number of received packets (including
024 received ated corrupted packets) with a length of 1024 to MTU bytes
(1024-15 value (including FCS bytes but not framing bits).
18 bytes
in length)
Table C-16 Extended performance entry list (EX1)

a a Count Countin
ance ance Method
Entry Entry
the ated included.
packets value
transmitte
d.
d


a a Count Countin
ance ance Method
Entry Entry
errored value NOTE
frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
frames value
received.
frames value
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
.

COL the ated
frames value
unsuccess
fully
transmitte
d after
consecuti
ve
collisions
.
deferred
in
transmissi
on.
in the counts in
ingress all
direction sampling
periods
in the counts in
egress all
direction sampling
periods


a a Count Countin
ance ance Method
Entry Entry

ut on a sampling
port in periods
the
receive
direction.
ut on a sampling
port in periods
the
receive
direction.
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.

the m value
maximum obtained

the value
minimum obtained


a a Count Countin
ance ance Method
Entry Entry

the value of
average counts in
ETH_TX transmit all

the ated
packet value
loss count
in the
TX_DRO transmit
P_PKTS direction. -

the ated
packet value
loss count
in the
RX_DRO receive
P_PKTS direction. -
receive sampling
direction period
of an
Ethernet
port.
transmit sampling
direction period
of an
Ethernet
port.


a a Count Countin
ance ance Method
Entry Entry
packet in the last
receive period
direction
of an
Ethernet
port.
packet in the last
transmit period
direction
of an
Ethernet
port.
the all
receive sampling
direction periods
the all
transmit sampling
direction periods
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
RXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
h periods
utilization
on a port
in the
receive
direction.
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
receive
direction.
h periods
utilization
on a port
in the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
transmit
direction.
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
transmit
direction.
h periods
utilization
on a port
in the
transmit
direction.

Table C-17 Port traffic classification performance entry list (EX1)

a a Count Countin
ance ance Method
Entry Entry

RTCAR_ the ated
edPKTS of red
packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
ellowPK of yellow
TS packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
reenPKT of green
S packets
after
traffic
monitorin
g is
enabled.

RTSTRM the ated
_RCVM number value
ATCHPK of
TS packets
received
in the
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_SNDM number value
ATCHPK of
TS packets
transmitte
d in the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarded
due to
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.


a a Count Countin
ance ance Method
Entry Entry
packets period
marked in
red when
the traffic
policing
function
is
enabled.
receive period
direction
of a
matched
flow.
transmit period
direction
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_RCVM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
received
packets
of a
matched
flow.

RTSTRM the ated
_SNDM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
transmitte
d packets
of a
matched
flow.
S receive sampling
direction period
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry
S transmit sampling
direction period
of a
matched
flow.
Table C-18 Port priority performance entry list (EX1)

a a Count Countin
ance ance Method
Entry Entry
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.

_DROPP the ated
KTS number value
of
packets
discarded
in the
services
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry

_DROPB the ated
YTES number value
of bytes
discarded
in the
services
with
different
priorities.

RI_SNDP the ated
KTS number value
of
packets
transmitte
d in
egress
queues
with
different
priorities.

RI_SND the ated
BYTES number value
of bytes
in the
packets
transmitte
d in
egress
queues
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry
egress sampling
queues period
with
different
priorities
in the
transmit
direction.

rate of sampling
egress period
queues
with
different
priorities
in the
transmit
direction.

Table C-19 Port DS domain performance entry list (EX1)

a a Count Countin
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the DS
domain

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the DS
domain.

ANPRI_P the ated
KTS number value
of
packets
with
matched
S-VLAN
priorities
in the DS
domain.


a a Count Countin
ance ance Method
Entry Entry

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the DS
domain.

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the DS
domain.

P_BYTE the ated
S number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the DS
domain.

Table C-20 LAG performance entry list (EX1)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.
NOTE
packets
received.
packets
received.
packets
received.
error
packets
received.


a a Count Countin
ance ance Method
Entry Entry
undersize value
d packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
the ated included.
packets value
transmitte
d.
d
errored value NOTE
frames.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
frames value
received.
frames value
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
receive
direction.
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
receive
direction.
h periods
utilization
on a port
in the
receive
direction.
h periods
utilization
on a port
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
transmit
direction.
h periods
utilization
on a port
in the
transmit
direction.
NOTE
port DS domains.
C.2.4 EG4/EG4P
The RMON performance that the EG4/EG4P board supports includes basic performance,
extended performance, port traffic classification performance, port priority performance, and
Port DS domain performance.

NOTE

Method
performance count.
Table C-21 Basic performance entry list (EG4/EG4P)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.
NOTE
If the packets received by an EG4/EG4P board are larger than the


a a Count Countin
ance ance Method
Entry Entry
packets
received.
packets
received.
ETHOVE Indicates Packets Accumul Oversized packets are the packets larger than MTU
R the ated (including FCS bytes but not framing bits).
oversized value NOTE
packets For EG4/EG4P boards, an oversized packet is larger than 1518
received. bytes.
ETHJAB Indicates Packets Accumul ETHJAB indicates the number of received packets that are
the ated larger than MTU (including FCS bytes but not framing bits)
error NOTE
packets For EG4/EG4P boards, an oversized error packet is larger than 1518
received. bytes.
undersize value
d packets
received.

the ated
collisions value
.


a a Count Countin
ance ance Method
Entry Entry

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
4 received ated
(64 bytes value
in length)
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)


a a Count Countin
ance ance Method
Entry Entry
12 received ated
(512-102 value
3 bytes in
length)
024 received ated corrupted packets) with a length of 1024 to 1518 bytes
18 bytes
in length)
Table C-22 Extended performance entry list (EG4/EG4P)

a a Count Countin
ance ance Method
Entry Entry
the ated included.
packets value
transmitte
d.
d
errored value NOTE
frames. For EG4/EG4P boards, this count includes undersized frames and
oversized frames.
OD the bytes ated
in value
received
good
packets.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
frames value
received.
frames value
transmitte
d.
.


a a Count Countin
ance ance Method
Entry Entry

COL the ated
frames value
unsuccess
fully
transmitte
d after
consecuti
ve
collisions
.
deferred
in
transmissi
on.
in the counts in
ingress all
direction sampling
periods
in the counts in
egress all
direction sampling
periods

ut on a sampling
port in periods
the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
ut on a sampling
port in periods
the
receive
direction.
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.

the m value
maximum obtained

the value
minimum obtained

the value of
average counts in
ETH_TX transmit all


a a Count Countin
ance ance Method
Entry Entry

the ated
packet value
loss count
in the
TX_DRO transmit
P_PKTS direction. -

the ated
packet value
loss count
in the
RX_DRO receive
P_PKTS direction. -
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
receive sampling
direction period
of an
Ethernet
port.
transmit sampling
direction period
of an
Ethernet
port.
packet in the last
receive period
direction
of an
Ethernet
port.
packet in the last
transmit period
direction
of an
Ethernet
port.
the all
receive sampling
direction periods


a a Count Countin
ance ance Method
Entry Entry
the all
transmit sampling
direction periods
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.

Table C-23 Port traffic classification performance entry list (EG4/EG4P)

a a Count Countin
ance ance Method
Entry Entry

RTCAR_ the ated
edPKTS of red
packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
ellowPK of yellow
TS packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
reenPKT of green
S packets
after
traffic
monitorin
g is
enabled.

RTSTRM the ated
_RCVM number value
ATCHPK of
TS packets
received
in the
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_SNDM number value
ATCHPK of
TS packets
transmitte
d in the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarded
due to
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.


a a Count Countin
ance ance Method
Entry Entry
packets period
marked in
red when
the traffic
policing
function
is
enabled.
receive period
direction
of a
matched
flow.
transmit period
direction
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_RCVM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
received
packets
of a
matched
flow.

RTSTRM the ated
_SNDM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
transmitte
d packets
of a
matched
flow.
S receive sampling
direction period
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry
S transmit sampling
direction period
of a
matched
flow.
Table C-24 Port priority performance entry list (EG4/EG4P)

a a Count Countin
ance ance Method
Entry Entry
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.

_DROPP the ated
KTS number value
of
packets
discarded
in the
services
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry

_DROPB the ated
YTES number value
of bytes
discarded
in the
services
with
different
priorities.

RI_SNDP the ated
KTS number value
of
packets
transmitte
d in
egress
queues
with
different
priorities.

RI_SND the ated
BYTES number value
of bytes
in the
packets
transmitte
d in
egress
queues
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry
egress sampling
queues period
with
different
priorities
in the
transmit
direction.

rate of sampling
egress period
queues
with
different
priorities
in the
transmit
direction.

Table C-25 Port DS domain performance entry list (EG4/EG4P)

a a Count Countin
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the DS
domain

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the DS
domain.

ANPRI_P the ated
KTS number value
of
packets
with
matched
S-VLAN
priorities
in the DS
domain.


a a Count Countin
ance ance Method
Entry Entry

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the DS
domain.

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the DS
domain.

P_BYTE the ated
S number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the DS
domain.

Table C-26 LAG performance entry list (EG4/EG4P)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.
NOTE
packets
received.
packets
received.
packets
received.
error
packets
received.


a a Count Countin
ance ance Method
Entry Entry
undersize value
d packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
the ated included.
packets value
transmitte
d.
d
errored value NOTE
frames.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
frames value
received.
frames value
transmitte
d.
4 received ated
(64 bytes value
in length)


a a Count Countin
ance ance Method
Entry Entry
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
h periods
utilization
on a port
in the
receive
direction.
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
receive
direction.
h periods
utilization
on a port
in the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
transmit
direction.
ON_MA bandwidt in
X h sampling
utilization periods
on a port
in the
transmit
direction.
h periods
utilization
on a port
in the
transmit
direction.
NOTE
port DS domains.
C.2.5 IFU2/IFX2
The RMON performance that the IFU2/IFX2 board supports includes basic performance,
extended performance, port traffic classification performance, port priority performance, and
Port DS domain performance.

NOTE

Method
performance count.
Table C-27 Basic performance entry list (IFU2/IFX2)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.
NOTE
If the packets received by an IFU2/IFX2 board are larger than the
MTU, byte count is calculated based on MTU.


a a Count Countin
ance ance Method
Entry Entry
packets
received.
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.

Table C-28 Extended performance entry list (IFU2/IFX2)

a a Count Countin
ance ance Method
Entry Entry
the ated included.
packets value
transmitte
d.
d
errored value NOTE
frames. For the IFU2/IFX2 board, this count does not include undersized
frames and oversized frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
in the counts in
ingress all
direction sampling
periods
in the counts in
egress all
direction sampling
periods

ut on a sampling
port in periods
the
receive
direction.
ut on a sampling
port in periods
the
receive
direction.
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
receive sampling
direction period
of an
Ethernet
port.
transmit sampling
direction period
of an
Ethernet
port.
packet in the last
receive period
direction
of an
Ethernet
port.
packet in the last
transmit period
direction
of an
Ethernet
port.

the m value
maximum obtained


a a Count Countin
ance ance Method
Entry Entry

the value
minimum obtained

the value of
average counts in
ETH_TX transmit all

the ated
packet value
loss count
in the
TX_DRO transmit
P_PKTS direction. -

the ated
packet value
loss count
in the
RX_DRO receive
P_PKTS direction. -
the all
receive sampling
direction periods
the all
transmit sampling
direction periods


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
Table C-29 Port traffic classification performance entry list (IFU2/IFX2)

a a Count Countin
ance ance Method
Entry Entry

RTCAR_ the ated
edPKTS of red
packets
after
traffic
monitorin
g is
enabled.


a a Count Countin
ance ance Method
Entry Entry

RTCAR_ the ated
ellowPK of yellow
TS packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
reenPKT of green
S packets
after
traffic
monitorin
g is
enabled.

RTSTRM the ated
_RCVM number value
ATCHPK of
TS packets
received
in the
matched
flow.

RTSTRM the ated
_SNDM number value
ATCHPK of
TS packets
transmitte
d in the
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarded
due to
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
packets period
marked in
red when
the traffic
policing
function
is
enabled.


a a Count Countin
ance ance Method
Entry Entry
receive period
direction
of a
matched
flow.
transmit period
direction
of a
matched
flow.

RTSTRM the ated
_RCVM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
received
packets
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_SNDM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
transmitte
d packets
of a
matched
flow.
S receive sampling
direction period
of a
matched
flow.
S transmit sampling
direction period
of a
matched
flow.

Table C-30 Port priority performance entry list (IFU2/IFX2)

a a Count Countin
ance ance Method
Entry Entry
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.

_DROPP the ated
KTS number value
of
packets
discarded
in the
services
with
different
priorities.

_DROPB the ated
YTES number value
of bytes
discarded
in the
services
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmitte
d in
egress
queues
with
different
priorities.

RI_SND the ated
BYTES number value
of bytes
in the
packets
transmitte
d in
egress
queues
with
different
priorities.
egress sampling
queues period
with
different
priorities
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry

rate of sampling
egress period
queues
with
different
priorities
in the
transmit
direction.
Table C-31 Port DS domain performance entry list (IFU2/IFX2)

a a Count Countin
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the DS
domain


a a Count Countin
ance ance Method
Entry Entry

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the DS
domain.

ANPRI_P the ated
KTS number value
of
packets
with
matched
S-VLAN
priorities
in the DS
domain.

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the DS
domain.


a a Count Countin
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the DS
domain.

P_BYTE the ated
S number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the DS
domain.
Table C-32 LAG performance entry list (IFU2/IFX2)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.


a a Count Countin
ance ance Method
Entry Entry
NOTE
packets
received.
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
the ated included.
packets value
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
d
errored value NOTE
frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.


a a Count Countin
ance ance Method
Entry Entry
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
NOTE
l Integrated IP microwave ports support this parameter.

l Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic
classifications or port DS domains.
C.2.6 ISU2/ISX2/ISV3/ISM6
The RMON performance that the ISU2/ISX2/ISV3/ISM6 board supports includes basic
performance, extended performance, port traffic classification performance, port priority
performance, and Port DS domain performance.

NOTE

Method
performance count.
Table C-33 Basic performance entry list (ISU2/ISX2/ISV3/ISM6)

a a Count Countin
ance ance Method
Entry Entry
RXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
received.
events. NOTE
For the ISV3 board, ETHDROP counts packet loss events caused by
congestion.
For the ISU2 and ISX2 boards, ETHDROP counts packet loss
events caused by exceptions or congestion.
For other boards, ETHDROP counts packet loss events caused by
insufficient Ethernet chip resources, but does not count packet loss
events caused by link congestion and other reasons.


a a Count Countin
ance ance Method
Entry Entry
NOTE
If the packets received by an ISU2/ISX2/ISV3/ISM6 board are
larger than the MTU, byte count is calculated based on MTU.
packets
received.
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
4 received ated
(64 bytes value
in length)


a a Count Countin
ance ance Method
Entry Entry
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
Table C-34 Extended performance entry list (ISU2/ISX2/ISV3/ISM6)

a a Count Countin
ance ance Method
Entry Entry
the ated included.
packets value
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
d
errored value NOTE
frames. For the ISU2/ISX2/ISV3/ISM6 board, this count does not include
undersized frames and oversized frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.


a a Count Countin
ance ance Method
Entry Entry
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
P_RATIO loss rate value of number of actually drop packets/received packets.
in the counts in
ingress all
direction sampling
periods
P_RATIO loss rate value of number of actually drop packets/transmitted packets.
in the counts in
egress all
direction sampling
periods
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry

ut on a sampling
port in periods
the
receive
direction.
ut on a sampling
port in periods
the
receive
direction.
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.
receive sampling
direction period
of an
Ethernet
port.
transmit sampling
direction period
of an
Ethernet
port.


a a Count Countin
ance ance Method
Entry Entry
packet in the last
receive period
direction
of an
Ethernet
port.
packet in the last
transmit period
direction
of an
Ethernet
port.

the m value
maximum obtained

the value
minimum obtained

the value of
average counts in
ETH_TX transmit all


a a Count Countin
ance ance Method
Entry Entry

the ated
packet value
loss count
in the
TX_DRO transmit
P_PKTS direction. -

the ated
packet value
loss count
in the
RX_DRO receive
P_PKTS direction. -
the all
receive sampling
direction periods
the all
transmit sampling
direction periods
h periods
utilization
on a port
in the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
Table C-35 Port traffic classification performance entry list (ISU2/ISX2/ISV3/ISM6)

a a Count Countin
ance ance Method
Entry Entry

RTCAR_ the ated
edPKTS of red
packets
after
traffic
monitorin
g is
enabled.

RTCAR_ the ated
ellowPK of yellow
TS packets
after
traffic
monitorin
g is
enabled.


a a Count Countin
ance ance Method
Entry Entry

RTCAR_ the ated
reenPKT of green
S packets
after
traffic
monitorin
g is
enabled.

RTSTRM the ated
_RCVM number value
ATCHPK of
TS packets
received
in the
matched
flow.

RTSTRM the ated
_SNDM number value
ATCHPK of
TS packets
transmitte
d in the
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarded
due to
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
packets period
marked in
red when
the traffic
policing
function
is
enabled.


a a Count Countin
ance ance Method
Entry Entry
receive period
direction
of a
matched
flow.
transmit period
direction
of a
matched
flow.

RTSTRM the ated
_RCVM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
received
packets
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_SNDM number value
ATCHBY of bytes
TES (excludin
g inter-
frame
gaps and
preamble
s) in the
transmitte
d packets
of a
matched
flow.
S receive sampling
direction period
of a
matched
flow.
S transmit sampling
direction period
of a
matched
flow.

Table C-36 Port priority performance entry list (ISU2/ISX2/ISV3/ISM6)

a a Count Countin
ance ance Method
Entry Entry
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.

_DROPP the ated
KTS number value
of
packets
discarded
in the
services
with
different
priorities.

_DROPB the ated
YTES number value
of bytes
discarded
in the
services
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmitte
d in
egress
queues
with
different
priorities.

RI_SND the ated
BYTES number value
of bytes
in the
packets
transmitte
d in
egress
queues
with
different
priorities.
egress sampling
queues period
with
different
priorities
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry

rate of sampling
egress period
queues
with
different
priorities
in the
transmit
direction.
ECMPRS Indicates 0.0001 Value Compression ratio of Ethernet packets after traversing the
_RATIO the obtained enhanced compression module = Number of bytes after
compressi in the last compression/Number of bytes before compression
on ratio sampling NOTE
of the period Only ISV3 boards support this performance entry.
enhanced
compressi
on
module.
Table C-37 Port DS domain performance entry list (ISU2/ISX2/ISV3/ISM6)

a a Count Countin
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the DS
domain


a a Count Countin
ance ance Method
Entry Entry

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the DS
domain.

ANPRI_P the ated
KTS number value
of
packets
with
matched
S-VLAN
priorities
in the DS
domain.

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the DS
domain.


a a Count Countin
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the DS
domain.

P_BYTE the ated
S number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the DS
domain.
Table C-38 LAG performance entry list (ISU2/ISX2/ISV3/ISM6)

a a Count Countin
ance ance Method
Entry Entry

the ated
events.


a a Count Countin
ance ance Method
Entry Entry
NOTE
packets
received.
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
the ated included.
packets value
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
d
errored value NOTE
frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.


a a Count Countin
ance ance Method
Entry Entry
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
4 received ated
(64 bytes value
in length)
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)


a a Count Countin
ance ance Method
Entry Entry
56 received ated
(256-511 value
bytes in
length)
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.

NOTE
l Integrated IP microwave ports support this parameter.

l Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic
classifications or port DS domains.
C.2.7 ML1/MD1
The RMON performance that the ML1/MD1 board supports includes ATM PWE3
performance, ATM/IMA performance events on the access side, CES performance, PW
performance, PPP performance, and MLPPP performance.
NOTE

Method
performance count.
Table C-39 ATM PWE3 performance entry list (ML1/MD1)

a a Count Countin
ance ance Method
Entry Entry
Indicates Cells Accumul

the count ated
ATMPW of value
_SNDCE transmitte
LLS d cells. -


a a Count Countin
ance ance Method
Entry Entry
ATMPW Indicates Cells Accumul -

_RCVCE the count ated
LLS of value
received
cells.
ATMPW Indicates Cells Accumul -

_UNKN the count ated
OWNCE of value
LLS unknown
cells.
Table C-40 ATM/IMA performance entry list on the access side (ML1/MD1)

a a Count Countin
ance ance Method
Entry Entry
ATM_CO Indicates Cells Accumul ATM_CORRECTED_HCSERR is used to evaluate the

RRECTE the ated service quality.
D_HCSE number value
RR of
correctabl
e HCS
error cells
received.
ATM_UN Indicates Cells Accumul ATM_UNCORRECTED_HCSERR is used to determine

CORREC the ated whether cell loss occurs on a port.
TED_HC number value
SERR of
uncorrect
able HCS
error cells
received.
ATM_RC Indicates Cells Accumul ATM_RCVCELLS is used to determine whether ATM

VCELLS the total ated connections are normal.
number value
of
received
cells.


a a Count Countin
ance ance Method
Entry Entry
ATM_RC Indicates Cells Accumul ATM_RCVIDLECELLS is used to determine whether cells

VIDLEC the total ated are properly processed at the ATM physical layer.
ELLS number value
of
received
idle cells.
ATM_SN Indicates Cells Accumul ATM_SNDCELLS is used to determine whether a port

DCELLS the total ated transmits services normally.
number value
of
transmitte
d cells.
ATM_IF_ Indicates Cells/s Maximu -

INRATE_ the m value
MAX maximum obtained
rate of among all
normal sampling
cells periods
received
on the
port.
ATM_IF_ Indicates Cells/s Minimum -

INRATE_ the value
MIN minimum obtained
rate of among all
normal sampling
cells periods
received
on the
port.
ATM_IF_ Indicates Cells/s Average -

INRATE_ the value of
AVG average counts in
rate of all
normal sampling
cells periods
received
on the
port.


a a Count Countin
ance ance Method
Entry Entry
ATM_IF_ Indicates Cells/s Maximu -

OUTRAT the m value
E_MAX maximum obtained
rate of among all
normal sampling
cells periods
transmitte
d on the
port.
ATM_IF_ Indicates Cells/s Minimum -

OUTRAT the value
E_MIN minimum obtained
rate of among all
normal sampling
cells periods
transmitte
d on the
port.
ATM_IF_ Indicates Cells/s Average -

OUTRAT the value of
E_AVG average counts in
rate of all
normal sampling
cells periods
transmitte
d on the
port.
ATM_CE Indicates 0.0001 Value Percentage of valid cells = (Total number of cells - Number
LL_AVAI the obtained of HEC-detected error cells)/Total number of cells
LABILIT percentag in the last
Y e of valid sampling
cells. period

ON h all
rate of the periods
port in
the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry

ON h all
rate of the periods
port in
the
transmit
direction.
ATM_UN Indicates Cells/s Maximu ATM_UNI1_INRATE_MAX is based on VPIs/VCIs.

I1_INRA the m value
TE_MAX maximum obtained
rate of among all
receiving sampling
correct periods
cells on
the UNI1
side of
ATM
connectio
ns.
ATM_UN Indicates Cells/s Minimum ATM_UNI1_INRATE_MIN is based on VPIs/VCIs.

I1_INRA the value
TE_MIN minimum obtained
rate of among all
receiving sampling
correct periods
cells on
the UNI1
side of
ATM
connectio
ns.


a a Count Countin
ance ance Method
Entry Entry
ATM_UN Indicates Cells/s Average ATM_UNI1_INRATE_AVG is based on VPIs/VCIs.

I1_INRA the value of
TE_AVG average counts in
rate of all
receiving sampling
correct periods
cells on
the UNI1
side of
ATM
connectio
ns.
ATM_UN Indicates Cells/s Maximu ATM_UNI1_OUTRATE_MAX is based on VPIs/VCIs.

I1_OUTR the m value
ATE_MA maximum obtained
X rate of among all
transmitti sampling
ng correct periods
cells on
the UNI1
side of
ATM
connectio
ns.
ATM_UN Indicates Cells/s Minimum ATM_UNI1_OUTRATE_MIN is based on VPIs/VCIs.

I1_OUTR the value
ATE_MI minimum obtained
N rate of among all
transmitti sampling
ng correct periods
cells on
the UNI1
side of
ATM
connectio
ns.


a a Count Countin
ance ance Method
Entry Entry
ATM_UN Indicates Cells/s Average ATM_UNI1_OUTRATE_AVG is based on VPIs/VCIs.

I1_OUTR the value of
ATE_AV average counts in
G rate of all
transmitti sampling
ng correct periods
cells on
the UNI1
side of
ATM
connectio
ns.
ATM_UN Indicates Cells/s Maximu ATM_UNI2_INRATE_MAX is based on VPIs/VCIs.

I2_INRA the m value
TE_MAX maximum obtained
rate of among all
receiving sampling
correct periods
cells on
the UNI2
side of
ATM
connectio
ns.
ATM_UN Indicates Cells/s Minimum ATM_UNI2_INRATE_MIN is based on VPIs/VCIs.

I2_INRA the value
TE_MIN minimum obtained
rate of among all
receiving sampling
correct periods
cells on
the UNI2
side of
ATM
connectio
ns.


a a Count Countin
ance ance Method
Entry Entry
ATM_UN Indicates Cells/s Average ATM_UNI2_INRATE_AVG is based on VPIs/VCIs.

I2_INRA the value of
TE_AVG average counts in
rate of all
receiving sampling
correct periods
cells on
the UNI2
side of
ATM
connectio
ns.
ATM_UN Indicates Cells/s Maximu ATM_UNI2_OUTRATE_MAX is based on VPIs/VCIs.

I2_OUTR the m value
ATE_MA maximum obtained
X rate of among all
transmitti sampling
ng correct periods
cells on
the UNI2
side of
ATM
connectio
ns.
ATM_UN Indicates Cells/s Minimum ATM_UNI2_OUTRATE_MIN is based on VPIs/VCIs.

I2_OUTR the value
ATE_MI minimum obtained
N rate of among all
transmitti sampling
ng correct periods
cells on
the UNI2
side of
ATM
connectio
ns.


a a Count Countin
ance ance Method
Entry Entry
ATM_UN Indicates Cells/s Average ATM_UNI2_OUTRATE_AVG is based on VPIs/VCIs.

I2_OUTR the value of
ATE_AV average counts in
G rate of all
transmitti sampling
ng correct periods
cells on
the UNI2
side of
ATM
connectio
ns.
ATM_UN Indicates Cells Accumul ATM_UNI1_INCELLS is used to determine whether ATM

I1_INCE the total ated connections are normal.
LLS number value
of
receiving
correct
cells on
the UNI1
side of
ATM
connectio
ns.
ATM_UN Indicates Cells Accumul ATM_UNI1_OUTCELLS is used to determine whether

I1_OUTC the total ated ATM connections are normal.
ELLS number value
of
transmitti
ng correct
cells on
the UNI1
side of
ATM
connectio
ns.


a a Count Countin
ance ance Method
Entry Entry
ATM_UN Indicates Cells Accumul ATM_UNI2_INCELLS is used to determine whether ATM

I2_INCE the total ated connections are normal.
LLS number value
of
receiving
correct
cells on
the UNI2
side of
ATM
connectio
ns.
ATM_UN Indicates Cells Accumul ATM_UNI2_OUTCELLS is used to determine whether

I2_OUTC the total ated ATM connections are normal.
ELLS number value
of
transmitti
ng correct
cells on
the UNI2
side of
ATM
connectio
ns.
Table C-41 CES performance entry list (ML1/MD1)

a a Count Countin
ance ance Method
Entry Entry
CES_MI Indicates Packets Accumul -

SORDER the ated
PKTS number value
of lost
disordere
d packets.


a a Count Countin
ance ance Method
Entry Entry
CES_ST Indicates Packets Accumul -

RAYPKT the ated
S number value
of mis-
connected
packets.
CES_MA Indicates Packets Accumul -

LPKTS the ated
number value
of
deformed
frames.
CES_JTR Indicates Times Accumul -

UDR the ated
number value
of jitter
buffer
underflo
ws.

OVR the ated
number value
of jitter
buffer
overflows
.
CES_LO Indicates Packets Accumul -

SPKTS the ated
number value
of lost
packets.
CES_RX Indicates Packets Accumul -

_PKTS the ated
number value
of
received
packets.


a a Count Countin
ance ance Method
Entry Entry
CES_TX Indicates Packets Accumul -

_PKTS the ated
number value
of
transmitte
d packets.
Table C-42 PW performance entry list (ML1/MD1)

a a Count Countin
ance ance Method
Entry Entry
PW_RCV Indicates Packets Accumul -

PKTS the ated
number value
of
packets
received
from
PWs.
PW_RCV Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
received
from
PWs.
MPLS_P Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
W_FLR the obtained source - Number of packets received by the sink)/Number of
packet in the last packets transmitted by the source
loss rate sampling
on the period
PW.


a a Count Countin
ance ance Method
Entry Entry
MPLS_P Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
W_FL the ated the source - Number of packets received by the sink (Both
packet value numbers are detected by the performance monitoring scheme
loss of OAM.)
number
on the
PW.
MPLS_P Indicates µs Value Frame delay = Time when the source sends a request packet
W_FD the frame obtained - Time when the source receives the response packet
delay on in the last
the PW. sampling
period
MPLS_P Indicates µs Value Frame delay variation is the difference between two frame
W_FDV the frame obtained delay test results.
delay in the last
variation sampling
on the period
PW.
Table C-43 PPP performance entry list (ML1/MD1)

a a Count Countin
ance ance Method
Entry Entry
PPP_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmitte
d PPP
packets.


a a Count Countin
ance ance Method
Entry Entry
PPP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmitte
d PPP
packets.
PPP_RX_ Indicates Packets Accumul -

PKTS the ated
number value
of
received
PPP
packets.
PPP_RX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
received
PPP
packets.

FCSPKT the ated
S number value
of PPP
packets
that
received
FCS
faults.

LOSPKT the ated
S number value
of PPP
packets
dropped
in the
transmitti
ng
process.


a a Count Countin
ance ance Method
Entry Entry

LOSPKT the ated
S number value
of
relieved
abnormal
PPP
packets.
PPP_RX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of received bytes x 8/
BW_UTI the PPP obtained Monitoring period)/Configured or actual bandwidth
LIZATIO bandwidt in the last
N h usage in sampling
the period
receive
direction.
PPP_TX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of transmitted bytes x 8/
the period
transmit
direction.
Table C-44 MLPPP performance entry list (ML1/MD1)

a a Count Countin
ance ance Method
Entry Entry
MP_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmitte
d MP
packets.


a a Count Countin
ance ance Method
Entry Entry
MP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmitte
d MP
packets.
MP_RX_ Indicates Packets Accumul -

PKTS the ated
number value
of
received
MP
packets.
MP_RX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
received
MP
packets.

ERRPKT the ated
S number value
of
received
MP
packets.
MP_TX_ Indicates Packets Accumul The transmitted MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
transmitte
d MP
packets.


a a Count Countin
ance ance Method
Entry Entry
MP_RX_ Indicates Packets Accumul The received MP packets include service and protocol
KTS number value
of
received
MP
packets.
MP_RX_ Indicates 0.0001 Value MP bandwidth usage = (Number of received bytes x 8/

BW_UTI the MP obtained Monitoring period)/Configured or actual bandwidth
the period
receive
direction.
MP_TX_ Indicates 0.0001 Value MP bandwidth usage = (Number of transmitted bytes x 8/

the period
transmit
direction.
C.2.8 CQ1
The RMON performance that the MP1 board supports includes CES performance, PW
performance, PPP performance, and MLPPP performance.

NOTE

Method
performance count.
Table C-45 CES performance entry list (MP1)

a a Count Countin
ance ance Method
Entry Entry

the ated
number value
CES_MI of lost
SORDER disordere
PKTS d packets. -
CES_ST Indicates Packets Accumul -

RAYPKT the ated
S number value
of mis-
connected
packets.
CES_MA Indicates Packets Accumul -

LPKTS the ated
number value
of
deformed
frames.


a a Count Countin
ance ance Method
Entry Entry

UDR the ated
number value
of jitter
buffer
underflo
ws.

OVR the ated
number value
of jitter
buffer
overflows
.
CES_LO Indicates Packets Accumul -

SPKTS the ated
number value
of lost
packets.
CES_RX Indicates Packets Accumul -

_PKTS the ated
number value
of
received
packets.
CES_TX Indicates Packets Accumul -

_PKTS the ated
number value
of
transmitte
d packets.

Table C-46 PW performance entry list (MP1)

a a Count Countin
ance ance Method
Entry Entry

PKTS the ated
number value
of
packets
received
from
PWs.
Table C-47 PPP performance entry list (MP1)

a a Count Countin
ance ance Method
Entry Entry

PKTS the ated
number value
of
transmitte
d PPP
packets.
PPP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmitte
d PPP
packets.

PKTS the ated
number value
of
received
PPP
packets.


a a Count Countin
ance ance Method
Entry Entry
PPP_RX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
received
PPP
packets.

FCSPKT the ated
S number value
of PPP
packets
that
received
FCS
faults.

LOSPKT the ated
S number value
of PPP
packets
dropped
in the
transmitti
ng
process.

LOSPKT the ated
S number value
of
relieved
abnormal
PPP
packets.
PPP_RX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of received bytes x 8/
the period
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
PPP_TX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of transmitted bytes x 8/
the period
transmit
direction.
Table C-48 MLPPP performance entry list (MP1)

a a Count Countin
ance ance Method
Entry Entry
MP_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmitte
d MP
packets.
MP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmitte
d MP
packets.

PKTS the ated
number value
of
received
MP
packets.


a a Count Countin
ance ance Method
Entry Entry
MP_RX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
received
MP
packets.

ERRPKT the ated
S number value
of
received
MP
packets.
MP_TX_ Indicates Packets Accumul The transmitted MP packets include service and protocol
KTS number value
of
transmitte
d MP
packets.
MP_RX_ Indicates Packets Accumul The received MP packets include service and protocol
KTS number value
of
received
MP
packets.
MP_RX_ Indicates 0.0001 Value MP bandwidth usage = (Number of received bytes x 8/

the period
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
MP_TX_ Indicates 0.0001 Value MP bandwidth usage = (Number of transmitted bytes x 8/

the period
transmit
direction.
C.2.9 CSHN
The RMON performance that the CSHN board supported include L2VPN performance,
Tunnel performance, PW performance of L2VPN, ETH OAM 802.1ag performance, and
MPLS-TP OAM performance.
NOTE

Method
performance count.

Table C-49 L2VPNa performance entry list (CSHN)

a a Count Countin
ance ance Method
Entry Entry

the ated
number value
of
packets
received
at the V-
VLAN_R UNI
CVPKTS VLAN. -
VLAN_R Indicates Bytes Accumul -

CVBYTE the ated
S number value
of bytes
in the
packets
received
at the V-
UNI
VLAN.
VUNI_R Indicates Packets Accumul Indicates the number of packets received on a V-UNI of a
CVPKTS the ated service.
number value
of
packets
received
on the V-
UNI.
VUNI_R Indicates Bytes Accumul Indicates the number of bytes received on a V-UNI of a
CVBYTE the ated service.
S number value
of bytes
received
on the V-
UNI.


a a Count Countin
ance ance Method
Entry Entry
VLAN_R Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
X_BPS the bit obtained
receive sampling
direction period
of a
VLAN to
which a
V-UNI
belongs.
VLAN_R Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
X_PPS the obtained
packet in the last
receive period
direction
of a
VLAN to
which a
V-UNI
belongs.
Table C-50 Tunnel performance entry list (CSHN)

a a Count Countin
ance ance Method
Entry Entry
TUNNEL Indicates Packets Accumul Indicates the number of packets received in the reverse
_REVER the ated tunnel of a bidirectional transit tunnel.
SE_RCV number value
PKTS of
packets
received
in the
reverse
tunnel.


a a Count Countin
ance ance Method
Entry Entry
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in the reverse tunnel
_REVER the ated of a bidirectional transit tunnel.
SE_RCV number value
BYTES of bytes
received
in the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets received in a tunnel.
_RCVPK the ated
TS number value
of
packets
received
in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in a tunnel.
_RCVBY the ated
TES number value
of bytes
received
in the
tunnel.
TUNNEL Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
_REVER the bit obtained
SE_RX_ rate in the in the last
BPS receive sampling
direction period
of a
reverse
tunnel.
TUNNEL Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
_REVER the obtained
SE_RX_ packet in the last
PPS rate in the sampling
receive period
direction
of a
reverse
tunnel.


a a Count Countin
ance ance Method
Entry Entry
_RX_BP the bit obtained
S rate in the in the last
receive sampling
direction period
of a
monitore
d object.
_RX_PPS the obtained
packet in the last
receive period
direction
of a
monitore
d object.
Table C-51 L2VPN PW performance entry list (CSHN)

a a Count Countin
ance ance Method
Entry Entry

PKTS the ated
number value
of
packets
received
on the
PW.

BYTES the ated
number value
of bytes
received
on the
PW.


a a Count Countin
ance ance Method
Entry Entry
PW_DR Indicates Packets Accumul -

OPPKTS the ated
number value
of
packets
discarded
on the
PW.
PW_RX_ Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
BPS the bit obtained
receive sampling
direction period
of a
monitore
d object.
PW_RX_ Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
PPS the obtained
packet in the last
receive period
direction
of a
monitore
d object.
Table C-52 ETH OAM performance entry list (CSHN)

a a Count Countin
ance ance Method
Entry Entry
ETH_CF Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
M_FLR the obtained source MEP - Number of packets received by the sink
Ethernet in the last MEP)/Number of packets transmitted by the source MEP
service sampling
packet period
loss rate.


a a Count Countin
ance ance Method
Entry Entry
ETH_CF Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
M_FL the ated the source - Number of packets received by the sink (Both
number value numbers are detected by the performance monitoring scheme
of of OAM.)
discarded
Ethernet
service
packets.
ETH_CF Indicates µs Value Frame delay = Time when the source MEP sends a request
M_FD the obtained packet - Time when the source MEP receives the response
Ethernet in the last packet
service sampling
delay. period
ETH_CF Indicates µs Value Frame delay variation is the difference between two frame
M_FDV the obtained delay test results.
Ethernet in the last
service sampling
delay period
variation.
M_FLR_ the obtained source MEP - Number of packets received by the sink
PRIn packet in the last MEP)/Number of packets transmitted by the source MEP
NOTE loss rate sampling
0≤n≤7 of the period
Ethernet
service
with a
priority
of n.
M_FL_P the ated the source - Number of packets received by the sink (Both
RIn number value numbers are detected by the performance monitoring scheme
NOTE of lost of OAM.)
0≤n≤7 packets in
the
Ethernet
service
with a
priority
of n.


a a Count Countin
ance ance Method
Entry Entry
ETH_CF Indicates µs Value Bidirectional frame delay = Time when the source sends a
M_FD_P the delay obtained request packet - Time when the source receives the response
RIn of the in the last packet
NOTE Ethernet sampling
0≤n≤7 service period
with a
priority
of n.
ETH_CF Indicates µs Value Frame delay variation is the difference between two frame
M_FDV_ the delay obtained delay test results.
PRIn variation in the last
NOTE of the sampling
0≤n≤7 Ethernet period
service
with a
priority
of n.
Table C-53 MPLS-TP OAM performance entry list (CSHN)

a a Count Countin
ance ance Method
Entry Entry
loss rate sampling
on the period
PW.
W_FLR_ the obtained source - Number of packets received by the sink)/Number of
N packet in the last packets transmitted by the source
loss rate sampling
on the period
PW at the
near end.


a a Count Countin
ance ance Method
Entry Entry
loss of OAM.)
number
on the
PW.
W_FL_N the ated the source - Number of packets received by the sink (Both
of lost of OAM.)
packets
on the
PW at the
near end.
MPLS_P Indicates µs Value Frame delay = Time when the source sends a request packet
the PW. sampling
period
MPLS_P Indicates µs Value Frame delay variation is the difference between two frame
delay in the last
variation sampling
on the period
PW.
MPLS_T Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
UNNEL_ the obtained source - Number of packets received by the sink)/Number of
FLR packet in the last packets transmitted by the source
loss rate sampling
in the period
tunnel.
FLR_N packet in the last packets transmitted by the source
loss rate sampling
on the period
tunnel at
the near
end.


a a Count Countin
ance ance Method
Entry Entry
MPLS_T Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
UNNEL_ the ated the source - Number of packets received by the sink (Both
FL packet value numbers are detected by the performance monitoring scheme
loss of OAM.)
number
in the
tunnel.
FL_N number value numbers are detected by the performance monitoring scheme
of lost of OAM.)
packets
on the
tunnel at
the near
end.
MPLS_T Indicates µs Value Frame delay = Time when the source sends a request packet
UNNEL_ the frame obtained - Time when the source receives the response packet
FD delay in in the last
the sampling
tunnel. period
MPLS_T Indicates µs Value Frame delay variation is the difference between two frame
UNNEL_ the frame obtained delay test results.
FDV delay in the last
variation sampling
in the period
tunnel.
Table C-54 1+1/XPIC performance entry list (CSHN)

a a Count Countin
ance ance Method
Entry Entry
RXPKTS Indicates Packets Accumul

the ated
received. included.


a a Count Countin
ance ance Method
Entry Entry
events.
Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
RXOCTE the bytes ated packets (including bad packets), including framing bits but
TS received. value not FCS bytes.
packets
received.
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
4 received ated
(64 bytes value
in length)
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)


a a Count Countin
ance ance Method
Entry Entry
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
the ated included.
packets value
transmitte
d.
d
errored value
frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.


a a Count Countin
ance ance Method
Entry Entry
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.


a a Count Countin
ance ance Method
Entry Entry
BGOOD the good ated
full-frame value
bytes
transmitte
d.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
Table C-55 PLA/1+1/XPIC performance entry list (CSHN)

a a Count Countin
ance ance Method
Entry Entry

the ated
received. included.


a a Count Countin
ance ance Method
Entry Entry
events.
packets
received.
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
4 received ated
(64 bytes value
in length)
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)


a a Count Countin
ance ance Method
Entry Entry
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
the ated included.
packets value
transmitte
d.
d
errored value
frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.


a a Count Countin
ance ance Method
Entry Entry
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.


a a Count Countin
ance ance Method
Entry Entry
BGOOD the good ated
full-frame value
bytes
transmitte
d.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
the all
receive sampling
direction periods
the all
transmit sampling
direction periods
NOTE
a:
l VUNI represents virtual UNI, represents the sink or source of services on the UNI side.
l The E-LAN services transmitted by the OptiX RTN 980 do not support the VLAN-based and VUNI-
based RMON performance statistics.

C.2.10 CSHNA
The RMON performance that the CSHNA board supports includes L2VPN performance,
NOTE

Method
performance count.
Table C-56 Basic performance entry list of an Ethernet port (CSHNA)

a a Count Countin
ance ance Method
Entry Entry
4 received ated
(64 bytes value
in length)
5 received ated
(65-127 value
bytes in
length)


a a Count Countin
ance ance Method
Entry Entry
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
ETHUN Indicates Packets Accumul An undersized packet has less than 64 bytes (including FCS
DER the ated bytes but excluding framing bits).
number value
of
received
packets
that are
undersize
d but
error-free.
h periods
utilization
on a port
in the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
Table C-57 Extended performance entry list of an Ethernet port (CSHNA)

a a Count Countin
ance ance Method
Entry Entry
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry

ut on a sampling
port in periods
the
receive
direction.
ut on a sampling
port in periods
the
receive
direction.
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.

the m value
maximum obtained

the value
minimum obtained


a a Count Countin
ance ance Method
Entry Entry

the value of
average counts in
ETH_TX transmit all

the ated
packet value
loss count
in the
TX_DRO transmit
P_PKTS direction. -

the ated
packet value
loss count
in the
RX_DRO receive
P_PKTS direction. -
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.

Table C-58 L2VPNa performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

the ated
number value
of
packets
received
at the V-
VLAN_R UNI
CVPKTS VLAN. -
VLAN_R Indicates Bytes Accumul -

CVBYTE the ated
S number value
of bytes
in the
packets
received
at the V-
UNI
VLAN.
VUNI_R Indicates Packets Accumul Indicates the number of packets received on a V-UNI of a
CVPKTS the ated service.
number value
of
packets
received
on the V-
UNI.
VUNI_R Indicates Bytes Accumul Indicates the number of bytes received on a V-UNI of a
CVBYTE the ated service.
S number value
of bytes
received
on the V-
UNI.


a a Count Countin
ance ance Method
Entry Entry
VLAN_R Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
X_BPS the bit obtained
receive sampling
direction period
of a
VLAN to
which a
V-UNI
belongs.
VLAN_R Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
X_PPS the obtained
packet in the last
receive period
direction
of a
VLAN to
which a
V-UNI
belongs.
Table C-59 Tunnel performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry
SE_RCV number value
PKTS of
packets
received
in the
reverse
tunnel.


a a Count Countin
ance ance Method
Entry Entry
SE_RCV number value
BYTES of bytes
received
in the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets received in a tunnel.
_RCVPK the ated
TS number value
of
packets
received
in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in a tunnel.
_RCVBY the ated
TES number value
of bytes
received
in the
tunnel.
_REVER the bit obtained
SE_RX_ rate in the in the last
direction period
of a
reverse
tunnel.
_REVER the obtained
SE_RX_ packet in the last
receive period
direction
of a
reverse
tunnel.


a a Count Countin
ance ance Method
Entry Entry
_RX_BP the bit obtained
S rate in the in the last
receive sampling
direction period
of a
monitore
d object.
_RX_PPS the obtained
packet in the last
receive period
direction
of a
monitore
d object.
Table C-60 L2VPN PW performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

PKTS the ated
number value
of
packets
received
on the
PW.

BYTES the ated
number value
of bytes
received
on the
PW.


a a Count Countin
ance ance Method
Entry Entry

OPPKTS the ated
number value
of
packets
discarded
on the
PW.
PW_RX_ Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
BPS the bit obtained
receive sampling
direction period
of a
monitore
d object.
PW_RX_ Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
PPS the obtained
packet in the last
receive period
direction
of a
monitore
d object.
Table C-61 ETH OAM performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry
M_FLR the obtained source MEP - Number of packets received by the sink
Ethernet in the last MEP)/Number of packets transmitted by the source MEP
service sampling
packet period
loss rate.


a a Count Countin
ance ance Method
Entry Entry
of of OAM.)
discarded
Ethernet
service
packets.
ETH_CF Indicates μs Value Frame delay = Time when the source MEP sends a request
M_FD the obtained packet - Time when the source MEP receives the response
Ethernet in the last packet
service sampling
delay. period
ETH_CF Indicates μs Value Frame delay variation is the difference between two frame
M_FDV the obtained delay test results.
Ethernet in the last
service sampling
delay period
variation.
M_FLR_ the obtained source MEP - Number of packets received by the sink
PRIn packet in the last MEP)/Number of packets transmitted by the source MEP
NOTE loss rate sampling
0≤n≤7 of the period
Ethernet
service
with a
priority
of n.
M_FL_P the ated the source - Number of packets received by the sink (Both
RIn number value numbers are detected by the performance monitoring scheme
NOTE of lost of OAM.)
the
Ethernet
service
with a
priority
of n.


a a Count Countin
ance ance Method
Entry Entry
ETH_CF Indicates μs Value Bidirectional frame delay = Time when the source sends a
M_FD_P the delay obtained request packet - Time when the source receives the response
RIn of the in the last packet
0≤n≤7 service period
with a
priority
of n.
ETH_CF Indicates μs Value Frame delay variation is the difference between two frame
M_FDV_ the delay obtained delay test results.
PRIn variation in the last
0≤n≤7 Ethernet period
service
with a
priority
of n.
Table C-62 MPLS-TP OAM performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry
loss rate sampling
on the period
PW.
W_FLR_ the obtained source - Number of packets received by the sink)/Number of
N packet in the last packets transmitted by the source
loss rate sampling
on the period
PW at the
near end.


a a Count Countin
ance ance Method
Entry Entry
loss of OAM.)
number
on the
PW.
of lost of OAM.)
packets
on the
PW at the
near end.
MPLS_P Indicates μs Value Frame delay = Time when the source sends a request packet
the PW. sampling
period
MPLS_P Indicates μs Value Frame delay variation is the difference between two frame
delay in the last
variation sampling
on the period
PW.
FLR packet in the last packets transmitted by the source
loss rate sampling
on the period
tunnel.
FLR_N packet in the last packets transmitted by the source
loss rate sampling
on the period
tunnel at
the near
end.


a a Count Countin
ance ance Method
Entry Entry
FL packet value numbers are detected by the performance monitoring scheme
loss of OAM.)
number
in the
tunnel.
FL_N number value numbers are detected by the performance monitoring scheme
of lost of OAM.)
packets
on the
tunnel at
the near
end.
MPLS_T Indicates μs Value Frame delay = Time when the source sends a request packet
UNNEL_ the frame obtained - Time when the source receives the response packet
FD delay in in the last
the sampling
tunnel. period
MPLS_T Indicates μs Value Frame delay variation is the difference between two frame
UNNEL_ the frame obtained delay test results.
FDV delay in the last
variation sampling
in the period
tunnel.
Table C-63 1+1/XPIC performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

the ated
received. included.


a a Count Countin
ance ance Method
Entry Entry
events.
packets
received.
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
4 received ated
(64 bytes value
in length)


a a Count Countin
ance ance Method
Entry Entry
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
the ated included.
packets value
transmitte
d.
d
errored value
frames.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
Table C-64 N+1 performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

the ated
received. included.
events.
packets
received.


a a Count Countin
ance ance Method
Entry Entry
packets
received.

ON h all
on a port periods
in the
receive
direction.

ON h all
on a port periods
in the
transmit
direction.
the ated included.
packets value
transmitte
d.
d
errored value
frames.


a a Count Countin
ance ance Method
Entry Entry
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
Table C-65 NMS port performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

the ated
number value
of
received Corrupted packets, broadcast packets, and multicast packets
packets. are included.


a a Count Countin
ance ance Method
Entry Entry
Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
the ated
number value
of bytes
in
received
packets
(includin
g
RXOCTE corrupted
TS packets).
RXMUL Indicates Packets Accumul Broadcast packets are excluded.

CAST the ated
number value
of error-
free
multicast
packets
received.
RXBRD Indicates Packets Accumul Multicast packets are excluded.

CAST the ated
number value
of error-
free
broadcast
packets
received.
PORT_R Indicates 0.0001 Average Bandwidth utilization on a port in the receive direction =
X_BW_U the value of (Number of received bytes x 8/Monitoring period)/
TILIZATI bandwidt counts in Configured or actual bandwidth
ON h all
on a port periods
in the
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
PORT_T Indicates 0.0001 Average Bandwidth utilization on a port in the transmit direction =
X_BW_U the value of (Number of received bytes x 8/Monitoring period)/
ON h all
on a port periods
in the
transmit
direction.
RXPKT6 Indicates Packets Accumul Corrupted packets are included.

4 the ated
number value
of
received
packets
with a
length of
64 bytes
(includin
g FCS
bytes but
excluding
framing
bits).

5 the ated
number value
of
received
packets
with a
length of
65 to 127
bytes
(includin
g FCS
bytes but
excluding
framing
bits).


a a Count Countin
ance ance Method
Entry Entry

28 the ated
number value
of
received
packets
with a
length of
128 to
255 bytes
(includin
g FCS
bytes but
excluding
framing
bits).

56 the ated
number value
of
received
packets
with a
length of
256 to
511 bytes
(includin
g FCS
bytes but
excluding
framing
bits).


a a Count Countin
ance ance Method
Entry Entry

12 the ated
number value
of
received
packets
with a
length of
512 to
1023
bytes
(includin
g FCS
bytes but
excluding
framing
bits).
RXPKT1 Indicates Packets Accumul Indicates the total number of received packets (including
024 the ated corrupted packets) with a length of 1024 to MTU bytes
number value (including FCS bytes but not framing bits).
of
received
packets
with a
length of
1024 to
1518
(MTU)
bytes
(includin
g FCS
bytes but
excluding
framing
bits).
TXPKTS Indicates Packets Accumul Corrupted packets, broadcast packets, and multicast packets
the ated are included.
number value
of
transmitte
d packets.


a a Count Countin
ance ance Method
Entry Entry
TXOCTE Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
TS the ated
number value
of bytes
in
transmitte
d packets
(includin
g
corrupted
packets).
OD the ated
number value
of bytes
in error-
free
packets
transmitte
d.
OD the ated
number value
of bytes
in error-
free
packets
received.
TXUNIC Indicates Packets Accumul The packets that are dropped and fail to be transmitted are
AST the ated included.
number value
of unicast
packets
transmitte
d.
RXUNIC Indicates Packets Accumul Only error-free packets are included.

AST the ated
number value
of error-
free
unicast
packets
received.


a a Count Countin
ance ance Method
Entry Entry
TXMUL Indicates Packets Accumul The packets that are dropped and fail to be transmitted are
CAST the ated included.
number value
of
multicast
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The packets that are dropped and fail to be transmitted are
AST the ated included.
number value
of
broadcast
packets
transmitte
d.
RXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
RAMESP receiving in the last
EED error-free sampling
full-frame period
bits.
TXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
RAMESP transmitti in the last
EED ng error- sampling
free full- period
frame
bits.
RXFULL Indicates Bytes Accumul FCS bytes and framing bits are included.
BGOOD the ated
number value
of error-
free full-
frame
bytes
received.


a a Count Countin
ance ance Method
Entry Entry
TXFULL Indicates Bytes Accumul FCS bytes and framing bits are included.
BGOOD the ated
number value
of error-
free full-
frame
bytes
transmitte
d.
TXPKT6 Indicates Packets Accumul Corrupted packets are included.

4 the ated
number value
of
transmitte
d packets
with a
length of
64 bytes
(includin
g FCS
bytes but
excluding
framing
bits).

5 the ated
number value
of
transmitte
d packets
with a
length of
65 to 127
bytes
(includin
g FCS
bytes but
excluding
framing
bits).


a a Count Countin
ance ance Method
Entry Entry

28 the ated
number value
of
transmitte
d packets
with a
length of
128 to
255 bytes
(includin
g FCS
bytes but
excluding
framing
bits).

56 the ated
number value
of
transmitte
d packets
with a
length of
256 to
511 bytes
(includin
g FCS
bytes but
excluding
framing
bits).


a a Count Countin
ance ance Method
Entry Entry

12 the ated
number value
of
transmitte
d packets
with a
length of
512 to
1023
bytes
(includin
g FCS
bytes but
excluding
framing
bits).

024 the ated
number value
of
transmitte
d packets
with a
length of
1024 to
1518
bytes
(includin
g FCS
bytes but
excluding
framing
bits).


a a Count Countin
ance ance Method
Entry Entry

519 the ated
number value
of
transmitte
d packets
with a
length of
1519
bytes to
the MTU
(includin
g FCS
bytes but
excluding
framing
bits).

519 the ated
number value
of
received
packets
with a
length of
1519
bytes to
the MTU
(includin
g FCS
bytes but
excluding
framing
bits).
RX_DRO Indicates 0.0001 Average Packet loss rate in the receive direction = Number of
P_RATIO the value of discarded packets/Total number of received packets
packet counts in
loss rate all
in the sampling
receive periods
direction.


a a Count Countin
ance ance Method
Entry Entry
TX_DRO Indicates 0.0001 Average Packet loss rate in the transmit direction = Number of
P_RATIO the value of discarded packets/Total number of transmitted packets
packet counts in
loss rate all
in the sampling
transmit periods
direction.
Table C-66 Port traffic classification performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

RTSTRM the ated
_SNDM number value
ATCHPK of
TS packets
transmitte
d in the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarded
due to
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.


a a Count Countin
ance ance Method
Entry Entry
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
packets period
marked in
red when
the traffic
policing
function
is
enabled.
receive period
direction
of a
matched
flow.


a a Count Countin
ance ance Method
Entry Entry
transmit period
direction
of a
matched
flow.
Table C-67 Port priority performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.

RI_SNDP the ated
KTS number value
of
packets
transmitte
d in
egress
queues
with
different
priorities.


a a Count Countin
ance ance Method
Entry Entry

RI_SND the ated
BYTES number value
of bytes
in the
packets
transmitte
d in
egress
queues
with
different
priorities.
egress sampling
queues period
with
different
priorities
in the
transmit
direction.

rate of sampling
egress period
queues
with
different
priorities
in the
transmit
direction.

Table C-68 Port DS domain performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the DS
domain

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the DS
domain.

ANPRI_P the ated
KTS number value
of
packets
with
matched
S-VLAN
priorities
in the DS
domain.


a a Count Countin
ance ance Method
Entry Entry

ANPRI_ the ated
BYTES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the DS
domain.

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the DS
domain.

P_BYTE the ated
S number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the DS
domain.

Table C-69 PLA/EPLA performance entry list (CSHNA)

a a Count Countin
ance ance Method
Entry Entry

the ated
received. included.
events.
packets
received.
packets
received.

TILIZATI bandwidt counts in NOTE
ON h all The maximum bandwidth of an enhanced physical link aggregation
utilization sampling (EPLA) group is 2.5 Gbit/s. If the physical bandwidth configured for
on a port periods an EPLA group exceeds 2.5 Gbit/s, bandwidth utilization is still
calculated based on 2.5 Gbit/s.
in the
receive
direction.

TILIZATI bandwidt counts in NOTE
ON h all The maximum bandwidth of an enhanced physical link aggregation
utilization sampling (EPLA) group is 2.5 Gbit/s. If the physical bandwidth configured for
on a port periods an EPLA group exceeds 2.5 Gbit/s, bandwidth utilization is still
calculated based on 2.5 Gbit/s.
in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
4 received ated
(64 bytes value
in length)
5 received ated
(65-127 value
bytes in
length)
28 received ated
(128-255 value
bytes in
length)
56 received ated
(256-511 value
bytes in
length)


a a Count Countin
ance ance Method
Entry Entry
12 received ated
(512-102 value
3 bytes in
length)
18 bytes
in length)
the ated included.
packets value
transmitte
d.
P_RATIO the value of packets lost in the transmit direction/Total number of
packet counts in transmitted packets
loss rate all
in the sampling
transmit periods
direction.
TXBPS Indicates Bit/s Value Bit rate in the transmit direction = Number of transmitted
transmit sampling
direction. period
TXPPS Indicates Packets/ Value Packet rate in the transmit direction = Number of transmitted
the second obtained packets/Monitoring period
packet in the last
transmit period
direction.
TX_DRO Indicates Packets Accumul -

P_PKTS the ated
number value
of
packets
lost in the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry
d
errored value
frames.
OD the bytes ated
in value
received
good
packets.
OD the bytes ated
in value
transmitte
d good
packets.
D the bytes ated
in value
received
bad
packets.
unicast value
packets
transmitte
d.
AST the ated
unicast value
packets
received.


a a Count Countin
ance ance Method
Entry Entry
multicast value
packets
transmitte
d.
broadcast value
packets
transmitte
d.
EED frame sampling
bytes period
received.
EED frame sampling
bytes period
transmitte
d.
BGOOD the good ated
full-frame value
bytes
received.
BGOOD the good ated
full-frame value
bytes
transmitte
d.


a a Count Countin
ance ance Method
Entry Entry
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)


a a Count Countin
ance ance Method
Entry Entry
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
the all
receive sampling
direction periods
the all
transmit sampling
direction periods
NOTE
a:
l VUNI represents virtual UNI, represents the sink or source of services on the UNI side.
l The E-LAN services transmitted by the OptiX RTN 980 do not support the VLAN-based and VUNI-
based RMON performance statistics.

C.2.11 CSHNU
The RMON performance that the CSHNU board supports includes L2VPN performance,
NOTE

Method
performance count.
Table C-70 Basic performance entry list of an Ethernet port (CSHNU)

a a Count Countin
ance ance Method
Entry Entry
ETHDRO Indicates Times Accumul ETHDROP indicates the number of events in which packet
P that ated loss occurs due to resource deficiency. This count is not the
packets value number of discarded packets but the number of times that
are lost. packets are discarded.
R that ated MTU bytes (including FCS bytes but not framing bits) and
oversize value do not contain any other errors.
packets
are
received.


a a Count Countin
ance ance Method
Entry Entry
ETHUN Indicates Packets Accumul Indicates the number of received packets that contain fewer
DER that ated than 64 bytes (including FCS bytes but not framing bits) and
undersize value do not contain any other errors.
packets
are
received.
PORT_R Indicates 0.0001 Average Bandwidth utilization on a specified port in the receive
X_BW_U the value of direction = (Number of received bytes x 8/Monitoring
TILIZATI bandwidt counts in period)/Configured or actual bandwidth
ON h sampling
utilization periods
on a port
in the
receive
direction.
h periods
utilization
on a port
in the
receive
direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA receive
X direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilization
PORT_R on a port
X_BW_U in the
TILIZATI receive
ON_MIN direction.
PORT_T Indicates 0.0001 Average Bandwidth utilization on a port in the transmit direction =
X_BW_U the value of (Number of transmitted bytes x 8/Monitoring period)/
ON h sampling
utilization periods
on a port
in the
transmit
direction.

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_AVG direction.

bandwidt in
h sampling
X_BW_U on a port
TILIZATI in the
ON_MA transmit
X direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilization
PORT_T on a port
X_BW_U in the
TILIZATI transmit
ON_MIN direction.
Indicates Bytes Accumul Indicates the total number of bytes (including FCS bytes but
RXOCTE bytes ated not framing bits) in received packets (including corrupted
TS received. value packets).
RXMUL Indicates Packets Accumul Indicates the total number of received good packets
CAST multicast ated (excluding broadcast packets) whose destination address is a
packets value multicast address.
received.
RXBRD Indicates Packets Accumul Indicates the total number of received good packets
CAST broadcast ated (excluding multicast packets) whose destination address is a
packets value broadcast address.
received.

packets ated Indicates the total number of received packets, including
received. value corrupted packets, broadcast packets, and multicast packets.
4 packets ated corrupted packets) with a length of 64 bytes (including FCS
received value bytes but not framing bits).
(64 bytes
in
length).
5 packets ated corrupted packets) with a length of 65 to 127 bytes
received value (including FCS bytes but not framing bits).
(65–127
bytes in
length).


a a Count Countin
ance ance Method
Entry Entry
(128–
255 bytes
in
length).
(256–
511 bytes
in
length).
(512–
1023
bytes in
length).
024 packets ated corrupted packets) with a length of 1024 to MTU bytes
(1024–
1518
bytes in
length).
Table C-71 Extended performance entry list of an Ethernet port (CSHNU)

a a Count Countin
ance ance Method
Entry Entry
ETHFCS Indicates Frames Accumul Indicates the number of received frames that contain an
FCS ated integer number of bytes and FCS check errors.
errored value
frames.


a a Count Countin
ance ance Method
Entry Entry
h periods
utilizatio
n on a
port in
the
receive
direction.

maximu of counts Monitoring period)/Configured or actual bandwidth
m in
bandwidt sampling
h periods
utilizatio
PORT_R n on a
X_BW_U port in
TILIZATI the
ON_MA receive
X direction.

bandwidt sampling
h periods
utilizatio
n on a
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MIN direction.


a a Count Countin
ance ance Method
Entry Entry

bandwidt sampling
h periods
utilizatio
n on a
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_AVG direction.

maximu of counts Monitoring period)/Configured or actual bandwidth
m in
bandwidt sampling
h periods
utilizatio
PORT_T n on a
X_BW_U port in
TILIZATI the
ON_MA transmit
X direction.

bandwidt sampling
h periods
utilizatio
n on a
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MIN direction.
RX_DRO Indicates 0.0001 Average Packet loss rate in the receive direction = Number of
P_RATIO the value of discarded packets/Total number of received packets
packet counts in
loss rate sampling
in the periods
receive
direction.


a a Count Countin
ance ance Method
Entry Entry
P_RATIO the value of discarded packets/Total number of transmitted packets
packet counts in
loss rate sampling
in the periods
transmit
direction.
TXBGO Indicates Bytes Accumul Indicates the total number of bytes (including FCS bytes but
OD the ated not framing bits) in transmitted good packets.
number value
of bytes
in the
transmitt
ed good
packets.
RXBGO Indicates Bytes Accumul Indicates the total number of bytes (including FCS bytes but
OD the ated not framing bits) in received good packets.
number value
of bytes
in
received
good
packets.
RXBRD Indicates 0.0001 Average Indicates the ratio of broadcast and multicast packets to all
CAST_R the value of packets in the receive direction.
ATIO broadcast counts in
traffic sampling
ratio in periods
the
receive
direction.
TXBRDC Indicates 0.0001 Average Indicates the ratio of broadcast and multicast packets to all
AST_RA the value of packets in the transmit direction.
TIO broadcast counts in
traffic sampling
ratio in periods
the
transmit
direction.


a a Count Countin
ance ance Method
Entry Entry
TXUNIC Indicates Packets Accumul Indicates the total number of transmitted unicast packets,
AST unicast ated including discarded packets and packets that fail to be
packets value transmitted.
transmitt
ed.
RXUNIC Indicates Packets Accumul Indicates the total number of good unicast packets that are
AST unicast ated received.
packets value
received.
TXMUL Indicates Packets Accumul Indicates the total number of transmitted multicast packets,
CAST multicast ated including discarded packets and packets that fail to be
transmitt
ed.
TXBRDC Indicates Packets Accumul Indicates the total number of transmitted broadcast packets,
AST broadcast ated including discarded packets and packets that fail to be
transmitt
ed.
RXGOO Indicates Kbit/s Current Indicates the rate of received good packets, including
DFULLF the bit value of framing bits (20 bytes) and FCS bytes.
RAMESP rate of counts in
EED good full- sampling
frame periods
packets
received.
TXGOO Indicates Kbit/s Current Indicates the rate of transmitted good packets, including
DFULLF the bit value of framing bits (20 bytes) and FCS bytes.
RAMESP rate of counts in
EED good full- sampling
frame periods
packets
transmitt
ed.
RXFULL Indicates Bytes Accumul Indicates the total number of bytes in received good packets,
BGOOD good full- ated including framing bits (20 bytes) and FCS bytes.
frame value
bytes
received.


a a Count Countin
ance ance Method
Entry Entry
TXFULL Indicates Bytes Accumul Indicates the total number of bytes in transmitted good
BGOOD good full- ated packets, including framing bits (20 bytes) and FCS bytes.
frame value
bytes
transmitt
ed.
TX_HS_ Indicates 0.0001 Current Ratio of high-priority service traffic to bandwidth for high-
TRAFF_ the ratio value of priority services in the transmit direction = Number of
BW_RAT of high- counts in transmitted bytes x 8/Monitoring period/Bandwidth for high-
IO priority sampling priority services)
service periods NOTE
traffic to This performance entry is supported only by Super EPLA.
bandwidt
h for
high-
priority
services
in the
transmit
direction.
TXPKTS Indicates Packets Accumul Indicates the total number of transmitted packets, including
packets ated corrupted packets, broadcast packets, and multicast packets.
transmitt value
ed.
TXBPS Indicates Bit/s Current Bit rate in the transmit direction = Number of transmitted
the bit value of bytes x 8/Monitoring period
rate in counts in
the sampling
transmit periods
direction.
TXPPS Indicates Packets/ Current Packet rate in the transmit direction = Number of transmitted
the second value of packets/Monitoring period
packet counts in
rate in sampling
the periods
transmit
direction.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes (including FCS bytes but
TS bytes ated not framing bits) in transmitted packets (including corrupted
transmitt value packets).
ed.


a a Count Countin
ance ance Method
Entry Entry
RXBBA Indicates Bytes Accumul Indicates the total number of bytes (including FCS bytes but
D bytes in ated not framing bits) in received corrupted packets.
received value
corrupted
packets.
of
received
packets
(includin
g
corrupted
packets)
with a
length
greater
than 1518
bytes.
TXPKT6 Indicates Packets Accumul Indicates the total number of transmitted packets (including
4 the ated corrupted packets) with a length of 64 bytes (including FCS
number value bytes but not framing bits).
of
transmitt
ed
packets
(includin
g
corrupted
packets)
with a
length of
64 bytes.


a a Count Countin
ance ance Method
Entry Entry
5 the ated corrupted packets) with a length of 65 to 127 bytes
of
transmitt
ed
packets
(includin
g
corrupted
packets)
with a
length of
65 to 127
bytes.
of
transmitt
ed
packets
(includin
g
corrupted
packets)
with a
length of
128 to
255
bytes.


a a Count Countin
ance ance Method
Entry Entry
of
transmitt
ed
packets
(includin
g
corrupted
packets)
with a
length of
256 to
511
bytes.
of
transmitt
ed
packets
(includin
g
corrupted
packets)
with a
length of
512 to
1023
bytes.


a a Count Countin
ance ance Method
Entry Entry
of
transmitt
ed
packets
(includin
g
corrupted
packets)
with a
length of
1024 to
1518
bytes.
of
transmitt
ed
packets
with a
length
greater
than 1518
bytes.

the ated
number value
of
packets
lost in the
TX_DRO transmit
P_PKTS direction. -

Table C-72 L2VPNa performance entry list (CSHNU)

Brief Full Perform Perfor Remarks
Name of Name of ance mance
a a Count Counti
Perform Perform Unit ng
ance ance Metho
Entry Entry d
Indicates Packets Accumu

the lated
number value
of
packets
received
at the V-
VLAN_R UNI
CVPKTS VLAN. -
VLAN_R Indicates Bytes Accumu -

CVBYTE the lated
S number value
of bytes
in the
packets
received
at the V-
UNI
VLAN.
VLAN_S Indicates Packets Accumu -

NDPKTS the lated
number value
of
packets
transmitte
d at the
V-UNI
VLAN.
VLAN_S Indicates Bytes Accumu -

NDBYTE the lated
S number value
of bytes
in the
packets
transmitte
d at the
V-UNI
VLAN.


a a Count Counti
ance ance Metho
Entry Entry d
VUNI_R Indicates Packets Accumu Indicates the number of packets received on the specified V-
CVPKTS the lated UNI of the specified service.
number value
of
packets
received
on the V-
UNI.
VUNI_R Indicates Bytes Accumu Indicates the number of bytes received on the specified V-
CVBYTE the lated UNI of the specified service.
S number value
of bytes
received
on the V-
UNI.
VUNI_S Indicates Packets Accumu Indicates the number of packets transmitted on the specified
NDPKTS the lated V-UNI of the specified service.
number value
of
packets
transmitte
d on the
V-UNI.
VUNI_S Indicates Bytes Accumu Indicates the number of bytes in the packets transmitted on
NDBYTE the lated the specified V-UNI of the specified service.
S number value
of bytes
transmitte
d on the
V-UNI.
VLAN_R Indicates Bit/s Current Bit rate in the receive direction of the specified V-UNI VLAN
X_BPS the bit value of = Number of received bytes x 8/Monitoring period
rate in the counts
receive in
direction samplin
of the V- g
UNI periods
VLAN.


a a Count Counti
ance ance Metho
Entry Entry d
VLAN_R Indicates Packets/ Current Packet rate in the receive direction of the specified V-UNI
X_PPS the second value of VLAN = Number of received packets/Monitoring period
packet counts
rate in the in
receive samplin
direction g
of the V- periods
UNI
VLAN.
VLAN_T Indicates Bit/s Current Bit rate in the transmit direction of the specified V-UNI
X_BPS the bit value of VLAN = Number of transmitted bytes x 8/Monitoring period
rate in the counts
transmit in
direction samplin
of the V- g
UNI periods
VLAN.
VLAN_T Indicates Packets/ Current Packet rate in the transmit direction of the specified V-UNI
X_PPS the second value of VLAN = Number of transmitted bytes x 8/Monitoring period
packet counts
rate in the in
transmit samplin
direction g
of the V- periods
UNI
VLAN.

Table C-73 Tunnel performance entry list (CSHNU)

a a Count Countin
ance ance Method
Entry Entry
SE_RCV number value
PKTS of
packets
received
in the
reverse
tunnel.
SE_RCV number value
BYTES of bytes
received
in the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets received in the specified
_RCVPK the ated tunnel.
TS number value
of
packets
received
in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes in the packets received in the
_RCVBY the ated specified tunnel.
TES number value
of bytes
received
in the
tunnel.
TUNNEL Indicates Bit/s Current Bit rate in the receive direction of the reverse tunnel =
_REVER the bit value of Number of received bytes x 8/Monitoring period
SE_RX_ rate in the counts in
direction periods
of the
reverse
tunnel.


a a Count Countin
ance ance Method
Entry Entry
TUNNEL Indicates Packets/ Current Packet rate in the receive direction of the reverse tunnel =
_REVER the second value of Number of received packets/Monitoring period
SE_RX_ packet counts in
receive periods
direction
of the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets transmitted in the specified
_REVER the ated tunnel.
SE_SND number value
PKTS of
packets
transmitte
d in the
reverse
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes in the packets transmitted in
_REVER the ated the specified tunnel.
SE_SND number value
BYTES of bytes
transmitte
d in the
reverse
tunnel.
TUNNEL Indicates Bit/s Current Bit rate in the transmit direction of the reverse tunnel =
_REVER the bit value of Number of transmitted bytes x 8/Monitoring period
SE_TX_ rate in the counts in
BPS transmit sampling
direction periods
of the
reverse
tunnel.
TUNNEL Indicates Packets/ Current Packet rate in the transmit direction of the reverse tunnel =
_REVER the second value of Number of transmitted packets/Monitoring period
SE_TX_P packet counts in
PS rate in the sampling
transmit periods
direction
of the
reverse
tunnel.


a a Count Countin
ance ance Method
Entry Entry
TUNNEL Indicates Bit/s Current Bit rate in the receive direction of a specified monitored
_RX_BP the bit value of object = Number of received bytes x 8/Monitoring period
S rate in the counts in
receive sampling
direction. periods
TUNNEL Indicates Packets/ Current Packet rate in the receive direction of a specified monitored
_RX_PPS the second value of object = Number of received packets/Monitoring period
packet counts in
receive periods
direction.
TUNNEL Indicates Packets Accumul Indicates the number of packets transmitted in the specified
_SNDPK the ated tunnel.
TS number value
of
packets
transmitte
d in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes in the packets transmitted in
_SNDBY the ated the specified tunnel.
TES number value
of bytes
transmitte
d in the
tunnel.
TUNNEL Indicates Bit/s Current Bit rate in the transmit direction of the specified tunnel =
_TX_BP the bit value of Number of transmitted bytes x 8/Monitoring period
S rate in the counts in
transmit sampling
direction periods
of the
tunnel.
TUNNEL Indicates Packets/ Current Packet rate in the transmit direction of the specified tunnel =
_TX_PPS the second value of Number of transmitted packets/Monitoring period
packet counts in
transmit periods
direction
of the
tunnel.

Table C-74 L2VPN PW performance entry list (CSHNU)

a a Count Countin
ance ance Method
Entry Entry

PKTS the ated
number value
of
packets
received
on the
PW.

BYTES the ated
number value
of bytes
received
on the
PW.

OPPKTS the ated
number value
of
packets
discarded
on the
PW.
PW_RX_ Indicates Bit/s Current Bit rate in the receive direction of a specified monitored
BPS the bit value of object = Number of received bytes x 8/Monitoring period
rate in the counts in
receive sampling
direction. periods
PW_RX_ Indicates Packets/ Current Packet rate in the receive direction of a specified monitored
PPS the second value of object = Number of received packets/Monitoring period
packet counts in
receive periods
direction.


a a Count Countin
ance ance Method
Entry Entry
PW_SND Indicates Packets Accumul Indicates the number of packets transmitted on the specified
PKTS the ated PW.
number value
of
packets
transmitte
d on the
PW.
PW_SND Indicates Bytes Accumul Indicates the number of bytes transmitted on the specified
BYTES the ated PW.
number value
of bytes
transmitte
d on the
PW.
PW_TX_ Indicates Bit/s Current Bit rate in the transmit direction of the specified PW =
BPS the bit value of Number of transmitted bytes x 8/Monitoring period
rate in the counts in
transmit sampling
direction periods
of the
PW.
PW_TX_ Indicates Packets/ Current Packet rate in the transmit direction of the specified PW =
PPS the second value of Number of transmitted packets/Monitoring period
packet counts in
transmit periods
direction
of the
PW.

Table C-75 ETH OAM performance entry list (CSHNU)

a a Count Countin
ance ance Method
Entry Entry
ETH_CF Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by the
M_FLR the value of source MEP - Number of packets received by the sink
packet counts in MEP)/Number of packets transmitted by the source MEP
loss rate sampling
of the periods
Ethernet
service.
number value numbers are detected by the performance monitoring
of lost mechanism of OAM.)
packets
of the
Ethernet
service.
ETH_CF Indicates μs Current E-Line service delay = Time when the source MEP sends a
M_FD the value of request packet - Time when the source MEP receives the
Ethernet counts in response packet
service sampling
delay. periods
ETH_CF Indicates μs Current The frame delay variation is the difference between two
M_FDV the value of frame delay test results.
Ethernet counts in
service sampling
delay periods
variation.
ETH_CF Indicates 0.0001 Current Packet loss rate = (Number of packets with priority n
M_FLR_ the value of transmitted by the source MEP - Number of packets with
PRIn packet counts in priority n received by the sink MEP)/Number of packets
NOTE loss rate sampling with priority n transmitted by the source MEP
0≤n≤7 of the periods
Ethernet
service
with a
priority
of n (0 ≤
n ≤ 7).


a a Count Countin
ance ance Method
Entry Entry
ETH_CF Indicates Packets Accumul Number of lost packets = Number of packets with priority n
M_FL_P the ated transmitted by the source - Number of packets with priority
RIn number value n received by the sink (Both numbers are detected by the
NOTE of lost performance monitoring mechanism of OAM.)
the
Ethernet
service
with
priority n.
ETH_CF Indicates μs Current Bidirectional frame delay = Time when the source sends a
M_FD_P the delay value of request packet with priority n - Time when the source
RIn of the counts in receives the response packet with priority n
0≤n≤7 service periods
with
priority n.
ETH_CF Indicates μs Current The frame delay variation is the difference between two
M_FDV_ the delay value of frame delay test results.
PRIn variation counts in
0≤n≤7 Ethernet periods
service
with
priority n.
Table C-76 MPLS-TP OAM performance entry list (CSHNU)

a a Count Countin
ance ance Method
Entry Entry
MPLS_P Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by the
W_FLR the value of source - Number of packets received by the sink)/Number of
packet counts in packets transmitted by the source
loss rate sampling
of the periods
PW.


a a Count Countin
ance ance Method
Entry Entry
MPLS_P Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by the
W_FLR_ the value of source - Number of packets received by the sink)/Number of
N packet counts in packets transmitted by the source
loss rate sampling
on the periods
PW at the
near end.
packets in
the PW.
packets
on the
PW at the
near end.
MPLS_P Indicates μs Current Frame delay = Time when the source sends a request packet
W_FD the frame value of - Time when the source receives the response packet
delay on counts in
the PW. sampling
periods
MPLS_P Indicates μs Current The frame delay variation is the difference between two
W_FDV the frame value of frame delay test results.
delay counts in
variation sampling
on the periods
PW.
MPLS_T Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by the
UNNEL_ the value of source - Number of packets received by the sink)/Number of
FLR packet counts in packets transmitted by the source
loss rate sampling
of the periods
tunnel.


a a Count Countin
ance ance Method
Entry Entry
MPLS_T Indicates 0.01% Current Packet loss rate = (Number of packets transmitted by the
UNNEL_ the value of source - Number of packets received by the sink)/Number of
FLR_N packet counts in packets transmitted by the source
loss rate sampling
in the periods
tunnel at
the near
end.
FL number value numbers are detected by the performance monitoring
packets in
the
tunnel.
FL_N number value numbers are detected by the performance monitoring
packets in
the tunnel
at the
near end.
MPLS_T Indicates μs Current Frame delay = Time when the source sends a request packet
UNNEL_ the frame value of - Time when the source receives the response packet
FD delay in counts in
the sampling
tunnel. periods
MPLS_T Indicates μs Current The frame delay variation is the difference between two
UNNEL_ the frame value of frame delay test results.
FDV delay counts in
variation sampling
in the periods
tunnel.
NOTE
a:
l VUNI indicates a virtual UNI, corresponding to the UNI-side source or end of a service.
l The E-LAN service of the OptiX RTN 980 does not support RMON performance statistics based on
VUNI and VLAN.

C.2.12 EFP8/EMS6
The RMON performance that the EFP8/EMS6 supports includes basic performance and
extended performance.
The bridging port (PORT10) of an EFP8 board is on the packet plane.
The bridging port (PORT8) of an EMS6 board is on the packet plane.
NOTE

Method
performance count.
Table C-77 Basic performance entry list (EFP8/EMS6)

a a Count Countin
ance ance Method
Entry Entry
Bytes in Bytes Accumul

good ated
RXBGO packets value
OD received FCS bytes are included but framing bits are excluded.
Bytes in Bytes Accumul

good ated
packets value
TXBGO transmitte
OD d FCS bytes are included but framing bits are excluded.


a a Count Countin
ance ance Method
Entry Entry
Bytes Accumul
RXOCTE Bytes ated
TS received value FCS bytes are included but framing bits are excluded.
Packets Accumul
Packets ated Corrupted packets, broadcast packets, and multicast packets
RXPKTS received value are included.
Broadcast Packets Accumul

RXBRD packets ated
CAST received value Multicast packets are excluded.
Multicast Packets Accumul

RXMUL packets ated
CAST received value Broadcast packets are excluded.
Table C-78 Extended performance entry list (EFP8/EMS6)

a a Count Countin
ance ance Method
Entry Entry
RXGOO Bit rate of kbit/s Value FCS bytes and framing bits (20 bits) are included.
DFULLF good obtained
RAMESP frames in the last
EED received sampling
period
TXGOO Bit rate of kbit/s Value FCS bytes and framing bits (20 bits) are included.
DFULLF good obtained
RAMESP frames in the last
EED transmitte sampling
d period
RXFULL Number Bytes Accumul FCS bytes and framing bits (20 bits) are included.
BGOOD of bytes ated
in good value
frames
received


a a Count Countin
ance ance Method
Entry Entry
TXFULL umber of Bytes Accumul FCS bytes and framing bits (20 bits) are included.
BGOOD bytes in ated
good value
frames
transmitte
d
TXMUL Multicast Packets Accumul The packets that are dropped and fail to be transmitted are
CAST packets ated included.
transmitte value
d
RXUNIC Unicast Packets Accumul Only error-free unicast packets are included.
AST packets ated
received value
TXUNIC Unicast Packets Accumul The packets that are dropped and fail to be transmitted are
AST packets ated included.
transmitte value
d
TXBRDC Broadcast Packets Accumul The packets that are dropped and fail to be transmitted are
AST packets ated included.
transmitte value
d
RXPAUS Pause Frames Accumul RXPAUSE indicates the number of received MAC flow
E frames ated control frames whose operation code is PAUSE.
received value
TXPAUS Pause Frames Accumul TXPAUSE indicates the number of transmitted MAC flow
E frames ated control frames whose operation code is PAUSE.
transmitte value
d
ETHDRO Packet Times Accumul ETHDROP indicates the number of events in which packet
P loss event ated loss occurs due to resource deficiency.
value
ETHOVE Oversized Packets Accumul Indicates the number of received packets that are longer than
R packets ated MTU bytes (including FCS bytes but not framing bits) and
received value do not contain any other errors.
ETHJAB Oversized Packets Accumul Indicates the total number of received packets that are longer
error ated than MTU bytes (including FCS bytes but not framing bits)
packets value and contain FCS errors or alignment errors.
received


a a Count Countin
ance ance Method
Entry Entry
ETHFCS Frames Frames Accumul Frames that contain an integer number of bytes and FCS
with FCS ated errors. Ultra-long or ultra-short frames are excluded.
errors value
(MAC_F
CS)
RXBBA Number Bytes Accumul FCS bytes are included but framing bits are excluded.
D of bytes ated
in the value
corrupt
packets
received
ETH_RX Maximu kbit/s Maximu ETH_RX_THROUGHPUT_MAX indicates the maximum

_THROU m receive m value throughput at the receive direction of an interface and equals
GHPUT_ throughp obtained to total number of received bytes (including the preamble
MAX ut of an among all and frame gap) divided by the measurement period.
interface sampling
periods
ETH_RX Minimum kbit/s Minimum ETH_RX_THROUGHPUT_MIN indicates the minimum

_THROU receive value throughput at the receive direction of an interface and equals
GHPUT_ throughp obtained to total number of received bytes (including the preamble
MIN ut of an among all and frame gap) divided by the measurement period.
interface sampling
periods
ETH_RX Average kbit/s Average ETH_RX_THROUGHPUT_AVG indicates the average

_THROU receive value of throughput at the receive direction of an interface and equals
GHPUT_ throughp counts in to total number of received bytes (including the preamble
AVG ut of an all and frame gap) divided by the measurement period.
interface sampling
periods
C.3 RMON Performance Entries List on the EoS/EoPDH-

Plane
This section lists RMON performance entries on the EoS/EoPDH plane by board type.
C.3.1 EFP8
The RMON performance that the EFP8 Board supports include basic performance, extended
performance, and VCG performance.

The EFP8 board's Ethernet ports PORT1 to PORT8, bridging port PORT9, and internal ports
VCTRUNK1 to VCTRUNK16 are on the EoPDH plane.
NOTE

Method
performance count.
Table C-79 Basic performance entry list (EFP8)

Brief Name Full Perfor Performa RemarksSource Port Source Port
of a Name of mance nce
Performanc a Count Countin
e Entry Performa Unit g
nce Method
Entry
RXOCTETS Bytes Bytes Accumula RXOCTETS indicates the total PORT1 to

received ted value number of bytes in received packets PORT9
(including bad packets), including
framing bits but not FCS bytes.
RXPKTS Packets Packets Accumula Bad packets, broadcast packets, and

received ted value multicast packets are included.
RXBRDCAS Broadcast Packets Accumula RXBRDCAST indicates the total

T packets ted value number of received good packets with
received broadcast destination addresses,
excluding multicast packets.
RXMULCA Broadcast Packets Accumula RXMULCAST indicates the total

ST packets ted value number of received good packets with
received multicast destination addresses,
excluding broadcast packets.


nce Method
Entry
RXPKT64 Packets Packets Accumula FCS bytes are included but framing
received ted value bits are excluded.
(64 bytes
in length)
(65-127
bytes in
length)
(128-255
bytes in
length)
(256-511
bytes in
length)
(512-1023
bytes in
length)
RXPKT1024 Packets Packets Accumula Indicates the total number of received

received ted value packets (including corrupted packets)
(1024-151 with a length of 1024 to 1518 bytes
8 bytes in (including FCS bytes but not framing
length) bits).
ETHOVER Indicates Packets Accumula Indicates the number of received

the ted value packets that are longer than MTU
oversized bytes (including FCS bytes but not
packets framing bits) and do not contain any
received. other errors.
ETHJAB Indicates Packets Accumula Indicates the total number of received

error framing bits) and contain FCS errors
packets or alignment errors.
received.


nce Method
Entry
ETHUNDER Undersize Packets Accumula Indicates the number of received PORT1 to

d packets ted value packets that are shorter than 64 bytes PORT8
received (including FCS bytes but not framing
bits) and do not contain any other
errors except for FCS errors.
ETHFRG Fragments Packets Accumula Indicates the total number of received

received ted value packets that have FCS or alignment
errors (FCS bytes are included but
framing bits are excluded). The count
increases because of noise collisions.
Table C-80 Extended performance entry list (EFP8)

Brief Name Full Perfor Performa Remarks Source Port
nce Method
Entry
RXGOODF Indicates kbit/s Value Framing bits (20 bytes) and FCS PORT1 to
ULLFRAME the rate of obtained bytes are included. PORT9
SPEED good full- in the last
frame bits sampling
received. period
TXGOODFU Indicates kbit/s Value Framing bits (20 bytes) and FCS
LLFRAMES the rate of obtained bytes are included.
PEED good full- in the last
frame bits sampling
transmitte period
d.
RXFULLBG Indicates Bytes Accumula Framing bits (20 bytes) and FCS
OOD the good ted value bytes are included.
full-frame
bytes
received.


nce Method
Entry
TXFULLBG Indicates Bytes Accumula Framing bits (20 bytes) and FCS
full-frame
bytes
transmitte
d.
TXMULCAS Indicates Packets Accumula The multicast packets that are

T the ted value discarded or fail to be transmitted are
multicast included.
packets
transmitte
d.
RXCTLPKT Control Frames Accumula -

S frames ted value
received
TXOCTETS Bytes Bytes Accumula Indicates the total number of bytes

transmitte ted value (including those in bad packets)
d transmitted (including FCS bytes but
not framing bits).
TXPKTS Packets Packets Accumula Bad packets, broadcast packets, and

transmitte ted value multicast packets are included.
d
TXCTLPKT Control Frames Accumula -

S frames ted value
transmitte
d
TXPKT64 Packets Packets Accumula FCS bytes are included but framing
transmitte ted value bits are excluded.
d (64
bytes in
length)
d (65-127
bytes in
length)


nce Method
Entry
d
(128-255
bytes in
length)
d
(256-511
bytes in
length)
d
(512-1023
bytes in
length)
d
(1024-151
8 bytes in
length)
RXUNICAS Unicast Packets Accumula RXUNICAST indicates the number

T packets ted value of good unicast packets.
received
TXUNICAS Unicast Packets Accumula The unicast packets that are discarded
T packets ted value or fail to be transmitted are included.
transmitte
d
TXBRDCAS Broadcast Packets Accumula The broadcast packets that are

T packets ted value discarded or fail to be transmitted are
transmitte included.
d
RXPAUSE Pause Frames Accumula RXPAUSE indicates the number of

frames ted value MAC flow control frames with the
received. PAUSE opcode.


nce Method
Entry
TXPAUSE Pause Frames Accumula TXPAUSE indicates the number of

frames ted value MAC flow control frames with the
transmitte PAUSE opcode.
d
PKT64 Packets Packets Accumula FCS bytes are included but framing
and
transmitte
d (64
bytes in
length)
and
transmitte
d (65-127
bytes in
length)
and
transmitte
d
(128-255
bytes in
length)
and
transmitte
d
(256-511
bytes in
length)
and
transmitte
d
(512-1023
bytes in
length)


nce Method
Entry
and
transmitte
d
(1024-151
8 bytes in
length)
ETHFCS Frames Frames Accumula Frames that contain an integer

with FCS ted value number of bytes and FCS errors.
errors Ultra-long or ultra-short frames are
(MAC_F excluded.
CS)
ETHALI Alignment Frames Accumula An alignment error frame contains a

error ted value fractional number of bytes and fails to
frames pass the FCS check.
ETH_RX_T Maximum kbit/s Maximum ETH_RX_THROUGHPUT_MAX

HROUGHP receive value indicates the maximum throughput at
UT_MAX throughpu obtained the receive direction of an interface
t of an among all and equals to total number of
interface sampling received bytes (including the
periods preamble and frame gap) divided by
the measurement period.
ETH_RX_T Minimum kbit/s Minimum ETH_RX_THROUGHPUT_MIN

HROUGHP receive value indicates the minimum throughput at
UT_MIN throughpu obtained the receive direction of an interface
t of an among all and equals to total number of
ETH_RX_T Average kbit/s Average ETH_RX_THROUGHPUT_AVG

HROUGHP receive value of indicates the average throughput at
UT_AVG throughpu counts in the receive direction of an interface
t of an all and equals to total number of

Table C-81 VCGperformance entry list (EFP8)

nce Method
Entry
VCG_TXGO Good Packets Accumula - VCTRUNK1 to

ODPACKET packets ted value VCTRUNK16
S transmitte
d
VCG_TXPA Packets Packets Accumula Bad packets, broadcast packets, and

CKETS transmitte ted value multicast packets are included.
d
VCG_TXOC Bytes Bytes Accumula Bad packets are included (FCS bytes
TETS transmitte ted value are included but framing bits are
d excluded).
VCG_RXGO Good Packets Accumula -

ODPACKET packets ted value
S received
VCG_RXPA Packets Packets Accumula Bad packets, broadcast packets, and

CKETS received ted value multicast packets are included.
VCG_RXOC Bytes Bytes Accumula Bad packets are included (FCS bytes
TETS received ted value are included but framing bits are
excluded).
VCG_TXSP Speed of kbit/s Value Bad packets are included (FCS bytes
EED bytes obtained are included but framing bits are
transmitte in the last excluded).
d sampling
period
VCG_RXSP Speed of kbit/s Value Bad packets are included (FCS bytes
received in the last excluded).
sampling
period
C.3.2 EMS6
The RMON performance that the EMS6 Board supported include basic performance,
extended performance, and VCG performance.
The EMS6 board's Ethernet ports PORT1 to PORT6, bridging port PORT7, and internal ports
VCTRUNK1 to VCTRUNK8 are on the EoS plane.

NOTE

Method
performance count.
Table C-82 Basic performance entry list (EMS6)

nce Method
Entry
RXOCTETS Indicates Bytes Accumula RXOCTETS indicates the total PORT1 to

the bytes ted value number of bytes in received packets PORT7
received. (including bad packets), including
framing bits but not FCS bytes.
RXBRDCAS Indicates Packets Accumula RXBRDCAST indicates the total

T the ted value number of received good packets with
broadcast broadcast destination addresses,
packets excluding multicast packets.
received.
RXMULCA Indicates Packets Accumula RXMULCAST indicates the total

ST the ted value number of received good packets with
broadcast multicast destination addresses,
packets excluding broadcast packets.
received.


nce Method
Entry
ETHOVER Indicates Packets Accumula Indicates the number of received

packets framing bits) and do not contain any
received. other errors.
RXPKTS Indicates Packets Accumula Bad packets, broadcast packets, and

the ted value multicast packets are included.
packets
received.
ETHJAB Indicates Packets Accumula Indicates the total number of received

error framing bits) and contain FCS errors
packets or alignment errors.
received.
ETHFCS The Frames Accumula -

number of ted value
frames
that have
FCS
check
errors-
ETHUNDER Undersize Packets Accumula Indicates the number of received

d packets ted value packets that are shorter than 64 bytes
received (including FCS bytes but not framing
bits) and do not contain any other
errors except for FCS errors.
ETHFRG Fragments Packets Accumula Indicates the total number of received

received ted value packets that have FCS or alignment
errors (FCS bytes are included but
framing bits are excluded). The count
increases because of noise collisions.
(64 bytes
in length)
(65-127
bytes in
length)


nce Method
Entry
(128-255
bytes in
length)
(256-511
bytes in
length)
(512-1023
bytes in
length)
RXPKT1024 Packets Packets Accumula Indicates the total number of received

received ted value packets (including corrupted packets)
(1024-151 with a length of 1024 to 1518 bytes
8 bytes in (including FCS bytes but not framing
length) bits).
ETHALI The Frames Accumula An alignment error frame contains a PORT3 to

number of ted value fractional number of bytes and fails to PORT6
alignment pass the FCS check.
error
frames
Table C-83 Extended performance entry list (EMS6)

nce Method
Entry
RXCTLPKT Control Frames Accumula - PORT1 to

S frames ted value PORT7
received


nce Method
Entry
TXOCTETS Bytes Bytes Accumula Indicates the total number of bytes

transmitte ted value (including those in bad packets)
d transmitted (including FCS bytes but
not framing bits).
TXPKTS Packets Packets Accumula Bad packets, broadcast packets, and

transmitte ted value multicast packets are included.
d
TXCTLPKT Control Frames Accumula -

S frames ted value
transmitte
d
d (64
bytes in
length)
d (65-127
bytes in
length)
d
(128-255
bytes in
length)
d
(256-511
bytes in
length)
d
(512-1023
bytes in
length)


nce Method
Entry
d
(1024-151
8 bytes in
length)
and
transmitte
d (64
bytes in
length)
and
transmitte
d (65-127
bytes in
length)
and
transmitte
d
(128-255
bytes in
length)
and
transmitte
d
(256-511
bytes in
length)


nce Method
Entry
and
transmitte
d
(512-1023
bytes in
length)
and
transmitte
d
(1024-151
8 bytes in
length)
RXGOODF Indicates kbit/s Value Framing bits (20 bytes) and FCS
ULLFRAME the rate of obtained bytes are included.
SPEED good full- in the last
frame bits sampling
received. period
TXGOODFU Indicates kbit/s Value Framing bits (20 bytes) and FCS
LLFRAMES the rate of obtained bytes are included.
PEED good full- in the last
frame bits sampling
transmitte period
d.
RXFULLBG Indicates Bytes Accumula Framing bits (20 bytes) and FCS
full-frame
bytes
received.
TXFULLBG Indicates Bytes Accumula Framing bits (20 bytes) and FCS
full-frame
bytes
transmitte
d.


nce Method
Entry
TXMULCAS Indicates Packets Accumula The multicast packets that are

multicast included.
packets
transmitte
d.
RXUNICAS Indicates Packets Accumula RXUNICAST indicates the number

T the ted value of good unicast packets.
unicast
packets
received.
TXUNICAS Indicates Packets Accumula The unicast packets that are discarded
T the ted value or fail to be transmitted are included.
unicast
packets
transmitte
d.
TXBRDCAS Indicates Packets Accumula The broadcast packets that are

broadcast included.
packets
transmitte
d.
RXPAUSE Indicates Frames Accumula RXPAUSE indicates the number of

the pause ted value MAC flow control frames with the
frames PAUSE opcode.
received.
TXPAUSE Indicates Frames Accumula TXPAUSE indicates the number of

the pause ted value MAC flow control frames with the
frames PAUSE opcode.
transmitte
d.

Table C-84 VCGperformance entry list (EMS6)

nce Method
Entry
VCG_TXGO Good Packets Accumula - VCTRUNK1 to

ODPACKET packets ted value VCTRUNK8
S transmitte
d
VCG_TXPA Packets Packets Accumula Bad packets, broadcast packets, and

CKETS transmitte ted value multicast packets are included.
d
VCG_TXOC Bytes Bytes Accumula Bad packets are included (FCS bytes
TETS transmitte ted value are included but framing bits are
d excluded).
VCG_RXGO Good Packets Accumula -

ODPACKET packets ted value
S received
VCG_RXPA Packets Packets Accumula Bad packets, broadcast packets, and

CKETS received ted value multicast packets are included.
VCG_RXOC Bytes Bytes Accumula Bad packets are included (FCS bytes
TETS received ted value are included but framing bits are
excluded).
VCG_TXSP Speed of kbit/s Value Bad packets are included (FCS bytes
transmitte in the last excluded).
d sampling
period
VCG_RXSP Speed of kbit/s Value Bad packets are included (FCS bytes
received in the last excluded).
sampling
period
C.4 RMON Events and Handling Procedures

This chapter describes the RMON events that indicate Ethernet service abnormalities and how
to handle these events.

C.4.1 ETHDROP
Description
ETHDROP indicates the number of events in which packet loss occurs due to resource
deficiency of Ethernet chips. An RMON threshold-crossing event is reported when the
number of packet loss events is higher than the upper threshold or lower than the lower
threshold.
NOTE
For the ISV3 board, ETHDROP counts packet loss events caused by congestion.
For the ISU2 and ISX2 boards, ETHDROP counts packet loss events caused by exceptions or
congestion.
For other boards, ETHDROP counts packet loss events caused by insufficient Ethernet chip resources,
but does not count packet loss events caused by link congestion and other reasons.
Impact on System
When packet loss occurs frequently, services are affected and the system is affected seriously.
Hence, you must rectify the fault immediately.
Possible Causes
This performance event indicates packet loss due to the full MAC buffer, FIFO overflow, or
backward pressure.
l The lower threshold is not set to a non-zero value.

l The hardware at the local end is faulty.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower Change the lower threshold to 0.
threshold
The number is higher than the Manually decrease the traffic transmitted from the
upper threshold opposite end. If the problem persists, go to the next
step.
Step 2 Replace the involved part.
----End
Reference
None

C.4.2 ETHEXCCOL
Description
ETHEXCCOL indicates the number of frames that fail to be transmitted due to continuous
port collisions. An RMON threshold-crossing event is reported when the number of frames
that fail to be transmitted is higher than the upper threshold or lower than the lower threshold.
Generally, the value indicates that 16 port collisions occur continuously when the same frame
is transmitted.
Impact on System
The opposite equipment fails to normally receive services.
Possible Causes
Generally, this event is caused when the local port is connected to a device that work in half-
duplex mode.
Procedure
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
The number is higher than the upper threshold Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.
If... Then...
The ports on the equipment at both ends work Set the working modes of the ports on
in inconsistent modes, or any port works in the equipment at both ends to full-duplex
half-duplex mode or auto-negotiation, so that these ports
work in consistent modes.
The ports on the equipment at both ends work Go to the next step.
in consistent modes and no ports work in half-
duplex mode
----End
Reference
None

C.4.3 ETHLATECOL
Description
ETHLATECOL indicates the number of collisions detected within a timeslot period after a
packet is transmitted. An RMON threshold-crossing event is reported when the number of
collisions is higher than the upper threshold or lower than the lower threshold.
Impact on System
Possible Causes
Generally, this performance event is caused by a large network diameter.
Procedure
If... Then...
If... Then...
duplex mode
Step 3 Check whether the network diameter of the LAN is very large according to the networking
If... Then...
The network diameter is Divide the network and deploy equipment to different buses or
very large physically shared devices (such as hubs).
NOTE
In the case of the 10 Mbit/s port rate, the maximum Ethernet diameter is
2000 m. In the case of the 100 Mbit/s port rate, the maximum Ethernet
diameter is 200 m.
The network diameter is Go to the next step.

appropriate
----End

Reference
None
C.4.4 RXBBAD
Description
RXBBAD indicates the total number of bytes in received bad packets, excluding the framing
bit but including the FCS byte. An RMON threshold-crossing event is reported when the total
number of bytes in received bad packets is higher than the upper threshold or lower than the
lower threshold.
Impact on System
A port discards bad packets. This may even interrupt system services.
Possible Causes
1. Errors occur when the opposite end transmits packets.
2. The transmission line is of the poor quality and bit errors exist.
3. The hardware at the local end is faulty.
Procedure
If... Then...
Step 2 Correct the errors that occur when the opposite end transmits packets.
Step 3 Handle the problem of poor quality of the transmission line.
Check whether the ETH_LOS alarm is reported at the local end because the external line is
damaged or over attenuated. If yes, see the related handling method to clear the alarm.
----End
Reference
None
C.4.5 TXDEFFRM
Description
TXDEFFRM indicates the number of frames the first transmission of which is delayed due to
the congestion on the transmission media, excluding the number of frames the first
transmission of which is delayed due to collisions. An RMON threshold-crossing event is

reported when the number of frames that fail to be transmitted is higher than the upper
threshold and lower than the lower threshold.
Impact on System
The rate of frame transmission decreases, and therefore packets are congested at a port and
the throughput of the port decreases.
Possible Causes
Generally, this event is caused when the external port at the local end is connected to a device
that work in half-duplex mode.
Procedure
If... Then...
If... Then...
duplex mode
----End
Reference
None
C.4.6 ETHUNDER
Description
ETHUNDER indicates that an RMON threshold-crossing event is reported when the number
of packets that are shorter than 64 bytes and are received on the line side crosses the preset
threshold.
Impact on System
The data frames whose length is not within the specific range are discarded. As a result, the
system services are affected.

Possible Causes
1. The length of a data frame that is received at a port is shorter than 64 bytes.
Procedure
Step 1 Check whether the opposite equipment transmits the packet that is shorter than 64 bytes.
If... Then...
The opposite equipment transmits the packet that is Rectify the fault on the opposite
shorter than 64 bytes equipment.
The opposite end does not transmit the packet that is Go to the next step.
shorter than 64 bytes
----End
Reference
None
C.4.7 ETHOVER
Description
ETHOVER indicates that an RMON threshold-crossing event is reported when the number of
packets that are longer than MTU and are received at a port crosses the preset threshold.
Impact on System
If the length of the data frame received at a port is more than the preset maximum frame
length, the data frame is discarded and therefore the system services are affected.
Possible Causes
1. The preset maximum frame length is less than the length of the frame that is received at
a port.
Procedure
Step 1 Check whether the opposite equipment transmits the packet that is longer than the maximum
frame length set for the local equipment.
If... Then...
The opposite equipment transmits the packet that is Notify the opposite equipment
longer than the maximum frame length set for the that the length of transmitted
local equipment frames should be changed.

If... Then...
The opposite equipment does not transmit the packet Go to the next step.
that is longer than the maximum frame length set for
the local equipment
----End
Reference
None
C.4.8 ETHFRG
Description
ETHFRG indicates that an RMON threshold-crossing event is reported when the number of
received packets that are shorter than 64 bytes and have FCS or alignment errors exceeds the
preset upper threshold.
Impact on System
Data transmission is delayed or packet loss occurs.
Possible Causes
l The working modes of the ports on the equipment at both ends are not consistent.
l The ports on the equipment at both ends work in half-duplex mode, and the data traffic is
very heavy.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.
If... Then...
The working modes are Go to the next step.
consistent
The working modes are not Change the working mode of the local port so that the
consistent ports on the equipment at both ends work in consistent
modes.
Step 2 Check whether the working modes of the ports on the equipment at both ends are set to the
half-duplex mode.
If... Then...
The working modes are not set to the Go to the next step.
half-duplex mode

If... Then...
The working modes are set to the half- Change the working modes of the ports on the
duplex mode equipment at both ends to the full-duplex mode
or adaptive mode.
----End
C.4.9 ETHJAB
Description
ETHJAB indicates that an RMON threshold-crossing alarm is reported when the number of
received packets that are longer than MTU and have FCS or alignment errors is higher than
the upper threshold.

Data transmission is delayed or packet loss occurs.
Possible Causes
l The working modes of the ports on the equipment at both ends are not consistent.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.
If... Then...
The working modes are Go to the next step.
consistent
The working modes are not Change the working mode of the local port so that the
consistent ports on the equipment at both ends work in consistent
modes.
----End
C.4.10 ETHCOL
Description
ETHCOL indicates the number of detected packet collisions. An RMON threshold-crossing
event is reported when the number of collisions is higher than the upper threshold or lower
than the lower threshold.
Impact on System

Possible Causes
Generally, this event is caused when the local port is connected to a large number of devices
that work in half-duplex mode.
Procedure
If... Then...
If... Then...
duplex mode
----End
Reference
None
C.4.11 ETHFCS
Description
ETHFCS indicates the number of received Ethernet data frames with FCS check errors at the
local end (excluding the oversized and undersized frames). An RMON threshold-crossing
event is reported when the number is higher than the upper threshold or lower than the lower
threshold.
Impact on System
Most ports discard the packets with FCS check errors. The system services are interrupted in
the worst case.
Possible Causes
1. The local port and opposite port work in inconsistent modes. For example, one port
works in full-duplex mode, and the opposite port works in half-duplex mode.
2. The transmission line is of the poor quality and bit errors exist.

Procedure
Step 1 Therefore, handle the alarm according to the specific performance event.
If... Then...
If... Then...
The ports on the equipment at both ends Change the working modes of the ports on
work in inconsistent modes the equipment at both ends so that they can
work in consistent modes
The ports on the equipment at both ends Go to the next step.
work in consistent modes
----End
Reference
None
C.4.12 ATMPW_LOSPKTS
Description
The ATMPW_LOSPKTS is a performance event indicating the number of lost ATM PW
packets.

None
Possible Causes
1. Signals on the radio link deteriorate.
2. A strong interference source is present near the equipment.
3. A board at the transmit or receive end is faulty.
4. The operating temperature of the equipment is very high.
Procedure
Step 1 Handle the fault on the radio link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Remove the interference source near the equipment and then check whether the performance
event is cleared.

Step 4 Replace the faulty board and then check whether the performance event is cleared.
Step 5 Rectify the fault in the fan so that the fan lowers the operating temperature of the equipment.
----End
Related Information
None
C.4.13 ATMPW_MISORDERPKTS
Description
The ATMPW_MISORDERPKTS is a performance event indicating the number of disordered
ATM PW packets.

None
Possible Causes
Procedure
event is cleared.
----End
Related Information
None

C.4.14 ATMPW_UNKNOWNCELLS
Description
The ATMPW_UNKNOWNCELLS a performance event indicating the number of unknown
cells in an ATM PW service.

None
Possible Causes
Procedure
event is cleared.
----End
Related Information
None
C.4.15 ATM_CORRECTED_HCSERR
Description
The ATM_CORRECTED_HCSERR is a performance event indicating the number of cells
that are received by an ATM port and contain correctable header check sequence (HCS)
errors.

None
Possible Causes


Procedure
event is cleared.
----End
Related Information
None
C.4.16 ATM_UNCORRECTED_HCSERR
Description
The ATM_UNCORRECTED_HCSERR is a performance event indicating the number of cells
that are received by an ATM port and contain uncorrectable header check sequence (HCS)
errors.

None
Possible Causes
Procedure
Step 1 Refer to 5.3 Troubleshooting the Radio Link and handle the fault on the radio link.
event is cleared.
----End

Related Information
None
C.4.17 CES_MISORDERPKTS
Description
The CES_MISORDERPKTS is a performance event indicating the count of lost disordered
CES PW packets.

The packets are disordered. As a result, the packet loss rate increases and services are
affected.
Possible Causes
1. Signals degrade on the link.
2. The link is looped.
3. The link is congested.
Related Alarms
CES_MISORDERPKT_EXC
Procedure
Step 1 See 5.3 Troubleshooting the Radio Link.
Step 2 Release the loop.
Step 3 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or
eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None
C.4.18 CES_STRAYPKTS
Description
The CES_STRAYPKTS is a performance event indicating the number of misconnected
packets in a period.

The packets are discarded. As a result, the packet loss rate increases and services are affected.

Possible Causes
1. Links are misconnected.
Related Alarms
CES_STRAYPKT_EXC
Procedure
Step 1 Check the link configuration and rectify the fault.
----End
Related Information
None
C.4.19 CES_MALPKTS
Description
The CES_MALPKTS is a performance event indicating the number of deformed CES packets
in a period.

The packets are discarded. As a result, the packet loss rate increases and services are affected.
Possible Causes
1. The RTP head enabling status is different between the two ends of the PW.
2. Bit errors occur on the link.
Related Alarms
CES_MALPKT_EXC
Procedure
Step 1 Set the RTP head enabling status to the same on the two ends of the PW. For details, see
Modifying CES Service Parameters.
----End
Related Information
None

C.4.20 CES_JTRUDR
Description
The CES_JTRUDR is a performance event indicating the number of jitter buffer underflows.

When no packets are transmitted from the jitter buffer, the buffer underflows.
Possible Causes
1. Signals degrade on the link.
2. The PSN network clocks used for the transmission of CES services are not synchronized.
3. The link is looped.
4. The link is congested.
5. The size of buffer area is set to a low value.
Related Alarms
CES_JTRUDR_EXC
Procedure
Step 1 Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Synchronize the PSN network clock by setting clock synchronization, reducing transmission
nodes, and optimizing transmission routes.
Step 5 Query the size of buffer area. For details, see Querying CES Service Information.
Step 6 Determine whether the size can be increased according to network planning. If yes, change
the size to a greater value. For details, see Managing CES Services.
----End
Related Information
None
C.4.21 CES_JTROVR
Description
The CES_JTROVR is a performance event indicating the number of jitter buffer overflows.

The jitter buffer is insufficient. As a result, the buffer overflows.

Possible Causes
1. The jitter buffer area is too small.
2. The clocks are not synchronous.
3. Link quality deteriorates, causing more jitters.
4. There are too many hops of radio link on the network side, causing a large number of
jitters.
Related Alarms
CES_JTROVR_EXC
Procedure
Step 1 Allocate a larger jitter buffer area.
Step 2 Check whether the LTI and other clock-related alarms are reported.
Step 4 Determine whether the hops can be reduced according to network planning. If yes, reduce the
hops of radio link on the network side.
----End
Related Information
None
C.4.22 CES_LOSPKTS
Description
The CES_LOSPKTS is a performance event indicating the number of CES packets lost in a
period.

When this alarm occurs, all 1s are inserted and services are interrupted.
Possible Causes
1. The link transmission quality is poor.
2. The link is configured as a loop.
3. Link congestion occurs.
Related Alarms
CES_LOSPKT_EXC
Procedure

----End
Related Information
None

Maintenance Guide D Alarm Management
D Alarm Management
The alarm management on the OptiX RTN 980 is classified into the NE alarm management
and board alarm management.
D.1 NE Alarm Management

The NE alarm management function set by user is applicable to all the boards on the NE.
D.2 Board Alarm Management
The board alarm management function is only applicable to the board on which users have
configured this function.

D.1 NE Alarm Management

The NE alarm management function set by user is applicable to all the boards on the NE.
The equipment supports the following NE alarm management functions:
l Settings of the alarm storage mode
l Setting of the alarm delay
l Setting of the alarm reversion mode
For details about these functions, see the manuals or online Help of the NMS.
D.2 Board Alarm Management

The board alarm management function is only applicable to the board on which users have
configured this function.
D.2.1 Setting the Alarm Severity

Alarms are classified into four levels: critical, major, minor, and warning, according to their
severities. The maintenance personnel can change the alarm severity by using the NMS.
This function is supported by all the boards.
l Critical alarm: A critical alarm indicates a critical problem with the network. A critical
problem can be the failure, overload, or system restart of mission-critical boards. It must
be cleared immediately. Otherwise, system breakdown may occur.
l Major alarm: A major alarm indicates failure of certain boards or links, such as
communication links. Urgent action is required to rectify the fault as this type of alarms
affects the QoS of the system.
l Minor alarm: A minor alarm indicates a non-service affecting problem that needs to be
solved, for example, fan speed exceeds threshold alarm. This type of alarms does not
affect the QoS of the system, but you need to locate and remove these faults in time.
l Warning alarm: A warning alarm indicates a potential error that may affect the QoS of
the system, for example, License file expiring precaution alarm. This type of alarms
needs to be handled based on actual conditions.
Critical alarms and major alarms need to be handled immediately to avoid system failures and
service interruptions.
D.2.2 Alarm Suppression

The maintenance personnel can change the alarm monitoring attribute by setting the alarm
suppression function. A board detects only the alarms that are not suppressed. The alarm
suppression function helps users to ignore their unconcerned alarms.
D.2.3 Alarm Auto-Report

If Alarm Auto-Report is set to Reported, all the detected alarms are reported to the NMS in
a timely manner. If Alarm Auto-Report is set to Not Report, the alarms are reported only

when alarm query is performed on the NMS. The maintenance personnel can change the
setting on the NMS.
D.2.4 Alarm Reversion

In the case of a port that is not configured with services, certain alarms may be reported. To
filter the alarms that users are not concerned, set these alarms to be reversed. In this manner,
the alarm status at this port is the opposite to the actual case. That is, the status is displayed as
normal when an alarm is actually reported.
The alarm reversion function is available in three modes, namely, non-reversion, automatic
reversion, and manual reversion.
l Non-revertive (Disable)
In this mode, the alarms are monitored by default and alarm reversion cannot be enabled
for a port.
l Auto restore
In this mode, alarm reversion can be enabled for a port where alarms are reported. After
alarm reversion is enabled at a port, alarms are not reported. When the current alarm is
cleared, the alarm reversion automatically changes to the disabled status. That is, it
changes to the non-reversion mode. Then, the alarm reporting status at the port is the
same as the actual status.
l Manual restore
In this mode, alarm reversion can be enabled for a port regardless of whether any alarms
are reported at the port. After alarm reversion is enabled, the alarm reporting status at the
port is opposite to the actual status. After alarm reversion is manually disabled, the alarm
reversion status changes to the non-reversion mode. Then, the alarm reporting status at
the port is the same as the actual status.
Pay attention to the following points when you set the alarm reversion function:
l For OptiX RTN 980, only R_LOS, T_ALOS, MW_LOF, ETH_LOS, and LAN_LOC
alarms support alarm reversion.
l Alarm reversion is set based on ports. Configurations are required at both the NE level
and the port level.
l Alarm reversion does not change the actual status of alarms on the board, as well as the
indication status of the alarm indicators.
l Alarm reversion is realized on the NE software. The alarm data is the same on the NE
and the NMS, which indicates the status after the alarm reversion. If you directly query
the alarm data of a board, however, the actual alarm status is returned.
D.2.5 Setting Alarm Thresholds

This section lists the alarms whose thresholds can be configured and hyperlinks to the detailed
configuration operations.
NOTE
The functions of the upper and lower thresholds are as follows: When the detected value is greater than
the upper threshold, a threshold-crossing alarm is reported; when the detected value is lower than the
lower threshold, the threshold-crossing alarm clears.

Table D-1 Bit error alarm thresholds

Alarm Descriptio Performan Threshold Default Reference
Name n ce Item Range Threshold
HP_CROSS Performance HPBBE 0-65535 (15 1500 (15 Setting

TR threshold- minutes) minutes) Performanc
crossing of 0-1048575 15000 (24 e
the higher (24 hours) hours) Thresholds
order path
HPES 0-900s (15 50s (15
minutes) minutes)
0-65535s 100s (24
(24 hours) hours)
HPSES 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)
HPUAS 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)
HPFEBBE 0-65535 (15 1500 (15

minutes) minutes)
0-1048575 15000 (24
(24 hours) hours)
HPFEES 0-900s (15 50s (15

minutes) minutes)
0-65535s 100s (24
(24 hours) hours)
HPFESES 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)
HPFEUAS 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)
HPAD_CRO Performance TUPJCHIG 0-16777215 1500 (15

SSTR threshold- H L (15 minutes)
crossing of minutes) 30000 (24
higher order 0-67108863 hours)
path L (24 hours)
adaptation


TUPJCLOW 0-16777215 1500 (15

L (15 minutes)
minutes) 30000 (24
0-67108863 hours)
L (24 hours)
TUPJCNEW 0-16777215 1500 (15

L (15 minutes)
minutes) 30000 (24
0-67108863 hours)
L (24 hours)
LP_CROSS Performance LPBBE 0-65535 (15 1500 (15

TR threshold- minutes) minutes)
crossing of 0-1048575 15000 (24
the lower (24 hours) hours)
order path
LPES 0-900s (15 50s (15
minutes) minutes)
0-65535s 100s (24
(24 hours) hours)
LPSES 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)
LPUAS 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)
LPFEBBE 0-65535 (15 1500 (15

minutes) minutes)
0-1048575 15000 (24
(24 hours) hours)
LPFEES 0-900s (15 50s (15

minutes) minutes)
0-65535s 100s (24
(24 hours) hours)
LPFESES 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)


LPFEUAS 0-900s (15 20s (15

minutes) minutes)
0-65535s 50s (24
(24 hours) hours)
MSAD_CR Performance AUPJCHIG 0-65535 (15 1500 (15

OSSTR threshold- H minutes) minutes)
crossing of 0-1048575 30000 (24
multiplex (24 hours) hours)
section
adaptation AUPJCLO 0-65535 (15 1500 (15
W minutes) minutes)
0-1048575 30000 (24
(24 hours) hours)
AUPJCNE 0-65535 (15 1500 (15

W minutes) minutes)
0-1048575 30000 (24
(24 hours) hours)
MW_BER_ Excessive - 10-8-10-3 10-3 Setting Bit

EXC bit errors on Error
microwave Thresholds
links for Service
Ports
MW_BER_ Signal - 10-9-10-4 10-6
SD degrade
(SD) due to
excessive bit
errors on
microwave
links
B1_SD Regenerator - 10-9-10-4 10-6

section (B1)
SD
B1_EXC Excessive - 10-8-10-3 10-3

bit errors in
the
regenerator
section (B1)
B2_SD Multiplex - 10-9-10-4 10-6

section (B2)
SD


B2_EXC Excessive - 10-8-10-3 10-3

bit errors in
the
multiplex
section (B2)
B3_SD Higher order - 10-9-10-4 10-6

path (B3)
SD
B3_EXC Excessive - 10-8-10-3 10-3

bit errors in
the higher
order path
(B3)
B3_EXC_V Excessive - 10-8-10-3 10-3

C3 bit errors in
VC-3 paths
(B3)
B3_SD_VC VC-3 path - 10-9-10-4 10-6

3 (B3) SD
BIP_SD Signal - 10-8-10-4 10-6

degrade due
to excessive
BIP errors
BIP_EXC Excessive - 10-7-10-3 10-3

BIP errors
Table D-2 Physical condition alarm thresholds

Alarm Description Threshold Default Reference
Name Range Threshold
ODC_TEMP Outdoor cabinet Upper threshold Upper threshold: Setting the

_ABN temperature range: 20-80 65°C Temperature and
(°C) Lower Humidity Alarm
Lower threshold threshold: -20°C Thresholds for
range: -40-10 the PMU
(°C)
RADIO_FA Insufficient 100 dB-350 dB 140 dB Setting the

DING_MAR microwave fade Alarm
GIN_INSUF margin Threshold for
F Insufficient
Fade Margin

Alarm Description Threshold Default Reference

Name Range Threshold
TEMP_OVE Board operating - - In the NE

R temperature Explorer, select
the desired
board and
choose
Configuration
> Environment
Monitor
Configuration
> Environment
Monitor
Interface from
the Function
Tree. Then
specify the
upper and lower
thresholds.
TEMP_ALA Board operating - - In the NE

RM temperature Explorer, select
the desired
board and
choose
Configuration
> Environment
Monitor
Configuration
> Environment
Monitor
Interface from
the Function
Tree. Then
specify the
upper and lower
thresholds.
NOTE
The board operating temperature thresholds vary with products and board types. You are not advised to
modify the default thresholds.
Table D-3 RMON alarm thresholds

MAC_FCS_ Bit errors ETHFCS 10GE: Upper Configuring

EXC detected at 0-65535 threshold: 90 Ethernet
the MAC (frames) Lower Performanc
layer exceed threshold: 0 e


the upper GE: 0-15000 Upper Threshold-

threshold. (frames) threshold: 9 Crossing
Lower Parameters
threshold: 0
100M: Upper
0-65535 threshold: 1
(frames) Lower
threshold: 0
10M: Upper
(frames) Lower
threshold: 0
MAC_FCS_ SD detected - 10-6-10-5 0

SD at the MAC
layer
exceeds the
upper
threshold.
PORT_EXC The PORT_RX_ 0-100 (%) Upper

_TRAFFIC bandwidth BW_UTILI threshold:
utilization of ZATION 100%
a port Lower
exceeds the threshold:
upper 75%
threshold.
PORT_TX_ 0-100 (%) Upper
BW_UTILI threshold:
ZATION 100%
Lower
threshold:
75%
MAC_EXT_ Bit errors at ETHDROP 10GE: Upper

EXC the MAC 0-150000 threshold: 90
layer exceed (times) Lower
the upper threshold: 0
threshold.
GE: 0-15000 Upper
(times) threshold: 9
Lower
threshold: 0


100M: Upper
(times) Lower
threshold: 0
10M: Upper
(times) Lower
threshold: 0
4G: 0-15000 Upper

(times) threshold: 36
Lower
threshold: 0
2.5G: Upper
(times) Lower
threshold: 0
400M: Upper
(times) Lower
threshold: 0
ETHEXCC 10GE: Upper

OL 0-65535 threshold: 10
(frames) Lower
threshold: 0
GE: 0-15000 Upper

(frames) threshold: 10
Lower
threshold: 0
100M: Upper
(frames) Lower
threshold: 0
10M: Upper
(frames) Lower
threshold: 0


RXBBAD 10GE: 0-248 Upper

(bytes) threshold:
75900 bytes
Lower
threshold: 0
byte
GE: 0-248 Upper

(bytes) threshold:
7590 bytes
Lower
threshold: 0
byte
100M: 0-248 Upper

(bytes) threshold:
759 bytes
Lower
threshold: 0
byte
10M: 0-248 Upper

(bytes) threshold:
759 bytes
Lower
threshold: 0
byte
2.5G: 0-248 Upper

(bytes) threshold:
7590 bytes
Lower
threshold: 0
byte
MPLS_TUN SD on a - 1-100 0
NEL_SD tunnel
MPLS_TUN Signal - 1-100 0

NEL_SF failure (SF)
on a tunnel
MPLS_PW_ SD on a PW - 1-100 0
SD
MPLS_PW_ SF on a PW - 1-100 0
SF


CES_LOSP The number - 0-1000 Upper

KT_EXC of CES threshold:
packets lost 100
within a Lower
certain threshold: 5
period
exceeds the
upper
threshold.
CES_MISO The number - 0-1000 Upper

RDERPKT_ of CES threshold:
EXC packets lost 100
due to Lower
disorder threshold: 5
within a
certain
period
exceeds the
upper
threshold.
CES_STRA The number - 0-1000 Upper

YPKT_EXC of errored threshold:
CES packets 100
within a Lower
period
exceeds the
upper
threshold.
CES_MALP The number - 0-1000 Upper

KT_EXC of deformed threshold:
CES packets 100
within a Lower
period
exceeds the
upper
threshold.
CES_JTRU The number - 0-1000 Upper

DR_EXC of jitter threshold:
buffer 100
underflows Lower
exceeds the threshold: 5
upper
threshold.


CES_JTRO The number - 0-1000 Upper

VR_EXC of jitter threshold:
buffer 100
overflows Lower
upper
threshold.
DROPRATI The number QOS_PORT 0-100 (%) Upper

O_OVER of packets QUEUE_D threshold:
lost due to ROPRATIO 0.1%
congestion Lower
upper
threshold. QOS_PORT 0-100 (%) Upper
CAR_Marke threshold:
dRedRATIO 0.1%
Lower
threshold: 0
PORTSTRM 0-100 (%) Upper

_SHAPING threshold:
_DROPRAT 0.1%
IO Lower
threshold: 0
TX_DROP_ 0-100 (%) Upper

RATIO threshold:
30%
Lower
threshold:
25%
FLOW_OV The traffic PORT_PRI_ 10GE: 0-259 Upper

ER exceeds the SNDBYTES (bytes) threshold:
upper 1187500000
threshold. (bytes)
Lower
threshold:
937500000
(bytes)


2.5G: 0-259 Upper

(bytes) threshold:
296875000
(bytes)
Lower
threshold:
234375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
118750000
(bytes)
Lower
threshold:
93750000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11875000
(bytes)
Lower
threshold:
9375000
(bytes)
DS_CVLAN 10GE: 0-259 Upper

PRI_BYTES (bytes) threshold:
1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)


GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)
DS_SVLAN 10GE: 0-259 Upper

PRI_BYTES (bytes) threshold:
1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)


FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)
DS_DSCP_ 10GE: 0-259 Upper

BYTES (bytes) threshold:
1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)


VUNI_RCV 10GE: 0-259 Upper

1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
4G: 0-259 Upper

(bytes) threshold:
468920000
(bytes)
Lower
threshold:
370200000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)


VUNI_SND 10GE: 0-259 Upper

1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
4G: 0-259 Upper

(bytes) threshold:
468920000
(bytes)
Lower
threshold:
370200000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)


VLAN_RC 10GE: 0-259 Upper

VBYTES (bytes) threshold:
1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
4G: 0-259 Upper

(bytes) threshold:
468920000
(bytes)
Lower
threshold:
370200000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)


VLAN_SN 10GE: 0-259 Upper

DBYTES (bytes) threshold:
1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
4G: 0-259 Upper

(bytes) threshold:
468920000
(bytes)
Lower
threshold:
370200000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)


PW_RCVB 10GE: 0-259 Upper

YTES (bytes) threshold:
1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
4G: 0-259 Upper

(bytes) threshold:
468920000
(bytes)
Lower
threshold:
370200000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)


PW_SNDB 10GE: 0-259 Upper

YTES (bytes) threshold:
1172300000
(bytes)
Lower
threshold:
925500000
(bytes)
4G: 0-259 Upper

(bytes) threshold:
468920000
(bytes)
Lower
threshold:
370200000
(bytes)
2.5G: 0-259 Upper

(bytes) threshold:
293075000
(bytes)
Lower
threshold:
231375000
(bytes)
GE: 0-259 Upper

(bytes) threshold:
117230000
(bytes)
Lower
threshold:
92550000
(bytes)
FE: 0-259 Upper

(bytes) threshold:
11723000
(bytes)
Lower
threshold:
9255000
(bytes)


RXGOODF 10GE: Upper

ULLFRAM 0-15000000 threshold:
ESPEED 00 (kbit/s) 9500000
(kbit/s)
Lower
threshold:
7500000
(kbit/s)
GE: Upper
0-15000000 threshold:
0 (kbit/s) 950000
(kbit/s)
Lower
threshold:
750000
(kbit/s)
100M: Upper
(kbit/s) 95000
(kbit/s)
Lower
threshold:
75000
(kbit/s)
10M: Upper
(kbit/s) 9500 (kbit/s)
Lower
threshold:
7500 (kbit/s)
4G: Upper
0 (kbit/s) 3800000
(kbit/s)
Lower
threshold:
3000000
(kbit/s)


2.5G: Upper
0 (kbit/s) 2375000
(kbit/s)
Lower
threshold:
1875000
(kbit/s)
400M: Upper
(kbit/s) 380000
(kbit/s)
Lower
threshold:
300000
(kbit/s)
TXGOODF 10GE: Upper

ULLFRAM 0-15000000 threshold:
ESPEED 00 (kbit/s) 9500000
(kbit/s)
Lower
threshold:
7500000
(kbit/s)
GE: Upper
0 (kbit/s) 950000
(kbit/s)
Lower
threshold:
750000
(kbit/s)
100M: Upper
(kbit/s) 95000
(kbit/s)
Lower
threshold:
75000
(kbit/s)


10M: Upper
(kbit/s) 9500 (kbit/s)
Lower
threshold:
7500 (kbit/s)
4G: Upper
0 (kbit/s) 3800000
(kbit/s)
Lower
threshold:
3000000
(kbit/s)
2.5G: Upper
0 (kbit/s) 2375000
(kbit/s)
Lower
threshold:
1875000
(kbit/s)
400M: Upper
(kbit/s) 380000
(kbit/s)
Lower
threshold:
300000
(kbit/s)
RXOCTETS 10GE: Upper

00 (bytes) 1000000000
(bytes)
Lower
threshold:
750000000
(bytes)


GE: Upper
0 (bytes) 100000000
(bytes)
Lower
threshold:
75000000
(bytes)
100M: Upper
(bytes) 10000000
(bytes)
Lower
threshold:
7500000
(bytes)
10M: Upper
(bytes) 1000000
(bytes)
Lower
threshold:
750000
(bytes)
TXOCTETS 10GE: Upper

00 (bytes) 1000000000
(bytes)
Lower
threshold:
750000000
(bytes)
GE: Upper
0 (bytes) 100000000
(bytes)
Lower
threshold:
75000000
(bytes)


100M: Upper
(bytes) 10000000
(bytes)
Lower
threshold:
7500000
(bytes)
10M: Upper
(bytes) 1000000
(bytes)
Lower
threshold:
750000
(bytes)
Table D-4 Other alarm thresholds

Alarm Name Description Threshold Default Reference
Range Threshold
L3V_TRAP_T The number of 1-100 The allowed -

HRE_EXCEED private network maximum
prefixes number of route
exceeds the prefixes is not
upper threshold. limited for the
VPN instance
IPv4 address
family.

Alarm Name Description Threshold Default Reference

Range Threshold
FDBSIZEALM E-LAN Upper threshold Upper In the NE

_ELAN forwarding range: 80-100 threshold: 95% Explorer, select
table entries are (%) Lower the desired NE
exhausted. Lower threshold: 90% and choose
threshold range: Configuration
60-100 (%) > Ethernet
Service
Management >
E-LAN Service
from the
Function Tree.
Select a service,
click the MAC
Address
Learning
Parameters
tab, and
configure the
upper and lower
thresholds.
ARP_SPOOF ARP spoofing 0-1024 20 In the NE

Explorer, select
the desired NE
and choose
Diagnosis &
Maintenance >
ARP Anti-
spoofing from
the Function
Tree. Then
configure the
alarm
thresholds.
IGSP_ENTRIE The number of Upper threshold Upper Configuring the

S_EXC IGMP snooping range: 80-100 threshold: IGMP
entries exceeds (%) 100% Snooping
the upper Lower Lower Protocol
threshold. threshold range: threshold: 80%
60-100 (%)
D.2.6 AIS Insertion

AIS insertion can be set for certain alarms reported on a board. When the board detects the
alarms, it inserts all 1s into the lower level service to indicate the remote end that the service
is unavailable.

Table D-5 Setting of the AIS insertion

Trigger Condition Default Value Applicable Board
B1_EXC Enabled ISV3, ISM6, ISX2, ISU2,

IF1, SL1D, SL1DA, SL4D
B2_SD Disabled
B2_EXC Disabled
HP_LOM Enabled
HP_TIM Disabled
HP_SLM Disabled
HP_UNEQ Disabled
B3_EXC Enabled
B3_SD Disabled
B1_SD Disabled
LP_TIM Disabled SP3S, SP3D
LP_UNEQ Disabled
LP_SLM Disabled
BIP_EXC Disabled
MW_BER_EXC Enabled IFX2, IFU2, ISU2, ISX2,

ISV3, ISM6
MW_BER_SD Disabled
R_LOS Enabled CQ1
NOTE
l When the SL1D/SL4D/SL1DA/ISU2/ISX2/ISV3 board detects the R_LOS, R_LOF, MS_AIS,

AU_AIS, or AU_LOP alarm, it forcibly inserts the AIS.
l When the IF1/ISU2/ISX2/ISV3 board detects the MW_LOF, MW_LIM, R_LOF, MS_AIS,
AU_AIS, or AU_LOP alarm, it forcibly inserts the AIS.
l When the IFX2 and IFU2 board detect the MW_LOF, MW_LIM, or R_LOF alarm, it forcibly
inserts the AIS.
D.2.7 UNEQ Insertion

When a board detects that the service path is not in use or that the LOS alarm exists, it inserts
all 0s into the service signal to notify the remote end that this signal is unavailable.
Table D-6 Setting of the UNEQ insertion

T_ALOS Disabled SP3S and SP3D

Service path being not in Disabled

use

Maintenance Guide E Performance Event Management
E Performance Event Management
The performance event management is classified into the NE performance event management
and board performance event management.
E.1 NE Performance Event Management

The NE performance event management function set by user is applicable to all the boards on
the NE.
E.2 Board Performance Event Management
The performance event management function is only applicable to the board on which users
have configured this function.

Maintenance Guide E Performance Event Management
E.1 NE Performance Event Management

The NE performance event management function set by user is applicable to all the boards on
the NE.
The supports the following NE performance event management functions:
l Setting NE performance event monitoring
l Setting the start/end time of performance events
l Enabling/Disabling the reporting of UAT events
For details about these functions, see the manuals or online Help of the NMS.
E.2 Board Performance Event Management

The performance event management function is only applicable to the board on which users
have configured this function.
Table E-1 Board performance event management function

Function Applicable Board
Setting 15-minute/24- SL1DA, EMS6, SL1D, SP3S, SP3D, CSHN, SL4D, ODU,
hour performance IFX2, IFU2, IF1, ISU2, ISX2, ML1, MD1, EFP8, ISV3, ISM6,
monitoring CQ1
Setting 15-minute/24- SL1DA, EMS6, SL1D, SP3S, SP3D, CSHN, SL4D, ODU,
hour performance event IFX2, IFU2, IF1, ISU2, ISX2, ML1, MD1, EFP8, ISV3, ISM6,
auto-reporting CQ1
Setting performance SL1DA, EMS6, SL1D, SL4D, SP3S, SP3D, IFX2, IFU2, IF1,
thresholds ISU2, ISX2, ML1, MD1, EFP8, CSHN, ISV3, ISM6, CQ1
Resetting the SL1DA, SL1D, SL4D, SP3S, SP3D, ODU, IFX2, IFU2, IF1,
performance register ISU2, ISX2, ISM6, ISV3
Generating performance SL1DA, EMS6, SL1D, SL4D, SP3S, SP3D, IFX2, IFU2, IF1,
threshold-crossing ISU2, ISX2, ML1, MD1, EFP8, ISV3, ISM6, CQ1
alarms
Monitoring UAT events SL1DA, EMS6, SL1D, SL4D, SP3S, SP3D, IFX2, IFU2, IF1,
ISU2, ISX2, EFP8, ISV3, ISM6, CQ1
Monitoring CSES SL1DA, EMS6, SL1D, SL4D, SP3S, SP3D, IFX2, IFU2, IF1,
performance events ISU2, ISX2, EFP8, ISV3, ISM6, CQ1

Maintenance Guide F Alarm Suppression Relationship
F Alarm Suppression Relationship
When the alarm suppression function is disabled on an NE, the root alarm and certain
correlated alarms are reported if a fault occurs on this NE. After the alarm suppression
function is enabled, the reporting of the correlated alarms is suppressed according to the
relationship between alarms when the root alarm is reported. The alarm suppression
relationship can be classified into the suppression relationship between intra-board alarms and
suppression relationship between inter-board alarms.
F.1 Alarm Suppression on TDM Plane

This section describes the alarm suppression relationship for SDH/PDH signals and IF signals
on the TDM plane.
F.2 Alarm Suppression on the Data Plane
This section describes the alarm suppression relationship for Ethernet, MPLS tunnel, PW,
ATM/IMA, PPP/MLPPP, and EoS/EoPDH services.

F.1 Alarm Suppression on TDM Plane

This section describes the alarm suppression relationship for SDH/PDH signals and IF signals
on the TDM plane.
Intra-board Alarm Suppression on TDM Plane
Table F-1 Suppression relationship between intra-board alarms (IF1 board)

Root Alarm Suppressed Alarm
MW_LOF R_LOS, R_LOC, MW_FEC_UNCOR, R_LOF, MW_LIM,

MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS, MS_RDI,
MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD, HP_UNEQ,
HP_TIM, HP_SLM, HP_RDI, HP_LOM, HP_REI
R_LOC R_LOF, MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD,

MS_AIS, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
HP_UNEQ, HP_TIM, HP_SLM, HP_RDI, HP_LOM, HP_REI
R_LOF MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS,

MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
MS_AIS MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,

B1_EXC B1_SD, MS_REI
AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM,

HP_RDI, HP_LOM, HP_REI
AU_LOP B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM, HP_RDI,

HP_LOM, HP_REI
B3_EXC B3_SD
HP_UNEQ HP_TIM
Table F-2 Suppression relationship between intra-board alarms (IFU2/IFX2/ISU2/ISX2/

ISV3/ISM6 board, E1+Ethernet service mode)
MW_LOF R_LOC, R_LOF, MW_LIM, MW_RDI, MW_BER_EXC,

MW_BER_SD, MW_FEC_UNCOR, MW_E1_LOST
R_LOC R_LOF, MW_LIM, MW_RDI, MW_BER_EXC, MW_BER_SD

R_LOF MW_LIM, MW_RDI, MW_BER_EXC, MW_BER_SD,

MW_E1_LOST
MW_BER_E MW_BER_SD
XC
TU_AIS TU_LOP, LP_TIM, LP_UNEQ, LP_RDI, LP_REI, BIP_EXC,

BIP_SD
TU_LOP LP_TIM, LP_UNEQ, LP_RDI, LP_REI, BIP_EXC, BIP_SD,
LP_UNEQ LP_RDI, LP_RFI
LP_RDI LP_REI
BIP_EXC BIP_SD
Table F-3 Suppression relationship between intra-board alarms (ISU2/ISX2/ISV3/ISM6

board, STM-1+Ethernet service mode)
MW_LOF R_LOC, MW_FEC_UNCOR, R_LOF, MW_LIM, MW_RDI,

B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS, MS_RDI, MS_REI,
AU_AIS, AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM,
HP_SLM, HP_RDI, HP_LOM, HP_REI, MW_E1_LOST
MW_LIM MW_RDI
R_LOC R_LOF, MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD,

MS_AIS, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
R_LOF MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS,

HP_UNEQ, HP_TIM, HP_SLM, HP_RDI, HP_LOM, HP_REI,
MW_E1_LOST
MS_AIS MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,

AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM,

HP_RDI, HP_LOM, HP_REI
AU_LOP B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM, HP_RDI,

HP_LOM, HP_REI
B3_EXC B3_SD
HP_UNEQ HP_TIM

MS_RDI MS_REI
MS_AIS B2_EXC, B2_SD
HP_UNEQ HP_RDI, HP_LOM
R_LOF HP_REI
HP_RDI HP_REI
Table F-4 Suppression relationship between intra-board alarms (SL1D/SL1DA/SL4D board)
LSR_NO_FIT R_LOS, R_LOC, R_LOF, J0_MM, B1_EXC, B1_SD, MS_AIS,

ED B2_EXC, B2_SD, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC,
B3_SD, HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM,
HP_LOM, IN_PWR_LOW, IN_PWR_HIGH, LASER_CLOSED,
LASER_MOD_ERR_EX, TF, OUT_PWR_ABN
R_LOS R_LOF, J0_MM, B1_EXC, B1_SD, MS_AIS, B2_EXC, B2_SD,

HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM, HP_LOM,
IN_PWR_LOW
R_LOC R_LOF, J0_MM, B1_EXC, B1_SD, MS_AIS, B2_EXC, B2_SD,

HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM, HP_LOM
R_LOF J0_MM, B1_EXC, B1_SD, MS_AIS, B2_EXC, B2_SD, MS_RDI,

MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD, HP_UNEQ,
HP_TIM, HP_RDI, HP_REI, HP_SLM, HP_LOM
MS_AIS B2_EXC, B2_SD, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC,

B3_SD, HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM,
HP_LOM
MS_RDI MS_REI
AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_RDI,

HP_REI, HP_SLM, HP_LOM
AU_LOP B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_RDI, HP_REI,

HP_SLM, HP_LOM
HP_UNEQ HP_TIM, HP_RDI, HP_LOM
HP_RDI HP_REI
B3_EXC B3_SD

Table F-5 Suppression relationship between intra-board alarms (SP3S/SP3D board)

TU_AIS TU_LOP, LP_SLM, DOWN_E1_AIS, LP_R_FIFO, LP_UNEQ,

LP_TIM, LP_RFI, LP_RDI, LP_REI, BIP_EXC, BIP_SD
TU_LOP LP_SLM, DOWN_E1_AIS, LP_R_FIFO, LP_UNEQ, LP_TIM,

LP_RFI, LP_RDI, LP_REI, BIP_EXC, BIP_SD
LP_UNEQ LP_TIM, LP_RFI, LP_RDI, BIP_EXC, BIP_SD
LP_RDI LP_REI
BIP_EXC BIP_SD
T_ALOS E1_LOS, UP_E1_AIS, DDN_LFA
E1_LOS UP_E1_AIS
UP_E1_AIS DDN_LFA
Table F-6 Suppression relationship between intra-board alarms (CSHN board)

PG_LINK_F PG_PRT_DEGRADED
AIL
LICENSE_L LCS_LIMITED
OST
LCS_EXPIR LCS_LIMITED
ED
LCS_FILE_N LCS_LIMITED
OT_EXIST
Table F-7 Suppression relationship between intra-board alarms (CSHNU board)

PG_LINK_F PG_PRT_DEGRADED
AIL
LICENSE_L LCS_LIMITED
OST
LCS_EXPIR LCS_LIMITED
ED

LCS_FILE_N LCS_LIMITED
OT_EXIST
TEMP_ALA TEMP_OVER
RM
Table F-8 Suppression relationship between intra-board alarms (PIU board)

POWER_AB THUNDERALM
NORMAL
Table F-9 Suppression relationship between intra-board alarms (FAN board)

POWER_AL FAN_FAIL, FAN_AGING

M
FAN_FAIL FAN_AGING
Inter-board Alarm Suppression on TDM Plane

The inter-board alarm suppression means that, when services are configured between two
boards on the same NE, the service alarm generated by the source board suppresses the
service alarm generated by the sink board. The TDM plane supports alarm suppression
between line/IF boards and tributary boards.
Table F-10 Inter-board Alarm Suppression on TDM Plane (IF board - IF board)
R_LOS, R_LOC, MS_AIS, AU_AIS, TU_AIS

AU_LOP, R_LOF
MW_LOF, MW_LIM TU_AIS
MW_LOF, MW_RDI, R_LOF MW_E1_LOST

Table F-11 Inter-board Alarm Suppression on TDM Plane (IF board - Tributary board)

AU_LOP, R_LOF
MW_LOF, MW_LIM TU_AIS
Table F-12 Inter-board Alarm Suppression on TDM Plane (Line board - Tributary board)

AU_LOP, R_LOF
F.2 Alarm Suppression on the Data Plane

This section describes the alarm suppression relationship for Ethernet, MPLS tunnel, PW,
ATM/IMA, PPP/MLPPP, and EoS/EoPDH services.
Intra-board Alarm Suppression on the Data Plane
Table F-13 Suppression relationship between intra-board alarms (Ethernet Port)
LSR_NO_FIT LASER_SHUT, ETH_LOS, TF, LSR_WILL_DIE, OUT_PWR_ABN

ED
LASER_MO LASER_SHUT, IN_PWR_ABN, OUT_PWR_ABN,

D_ERR LSR_BCM_ALM, TEM_HA, TEM_LA,ETH_LOS, TF,
LSR_WILL_DIE,OUT_PWR_ABN,LSR_BCM_ALM
LASER_SHU LSR_BCM_ALM, LSR_WILL_DIE, OUT_PWR_ABN

T
TF OUT_PWR_ABN, LSR_WILL_DIE
ETH_EFM_D ETH_EFM_REMFAULT
F
ETH_EFM_R ETH_EFM_EVENT
EMFAULT
ETH_AUTO_ LASER_SHUT
LINK_DOW
N
LPT_CFG_C LASER_SHUT
LOSEPORT

ETH_LOS ETH_NO_FLOW, IN_PWR_LOW, IN_PWR_HIGH, ARP_FAIL,

LOCAL_FAULT, REMOTE_FAULT
LASER_MO IN_PWR_HIGH,IN_PWR_LOW,OUT_PWR_HIGH,OUT_PWR_L
DULE_MISM OW,TEM_HA,TEM_LA,LSR_BCM_ALM,LSR_WILL_DIE
ATCH
Table F-14 Suppression relationship between intra-board alarms (MPLS Tunnel)

MPLS_TUNN MPLS_TUNNEL_MISMATCH, MPLS_TUNNEL_LOCV,

EL_MISMER MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess,
GE MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
MPLS_TUNNEL_UNEXPMEP, MPLS_TUNNEL_UNEXPPER
MPLS_TUNN MPLS_TUNNEL_LOCV, MPLS_TUNNEL_UNKNOWN,

EL_MISMAT MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF,
CH MPLS_TUNNEL_SD, MPLS_TUNNEL_UNEXPMEP,

EL_FDI MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF,
MPLS_TUNNEL_SD, MPLS_TUNNEL_UNEXPMEP,
MPLS_TUNN MPLS_TUNNEL_MISMATCH, MPLS_TUNNEL_LOCV,

EL_UNEXP MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess,
MEG MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
MPLS_TUNNEL_UNEXPMEP, MPLS_TUNNEL_UNEXPPER

EL_UNEXP MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF,
MEP MPLS_TUNNEL_SD, MPLS_TUNNEL_UNEXPPER

EL_AIS MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF,
MPLS_TUNNEL_SD, MPLS_TUNNEL_UNEXPMEP,
MPLS_TUNN MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess,

EL_LOCV MPLS_TUNNEL_SF
MPLS_TUNN MPLS_TUNNEL_SD
EL_SF

Table F-15 Suppression relationship between intra-board alarms (PW)

MPLS_PW_ MPLS_PW_MISMATCH, MPLS_PW_LOCV,

MISMERGE MPLS_PW_UNKNOWN, MPLS_PW_Excess, MPLS_PW_SF,
MPLS_PW_SD, MPLS_PW_UNEXPMEP, MPLS_PW_UNEXPPER
MPLS_PW_ MPLS_PW_LOCV, MPLS_PW_UNKNOWN, MPLS_PW_Excess,

MISMATCH MPLS_PW_SF, MPLS_PW_SD, MPLS_PW_UNEXPMEP,
MPLS_PW_UNEXPPER
MPLS_PW_U MPLS_PW_MISMATCH, MPLS_PW_LOCV,

NEXPMEG MPLS_PW_UNKNOWN, MPLS_PW_Excess, MPLS_PW_SF,
MPLS_PW_SD, MPLS_PW_UNEXPMEP, MPLS_PW_UNEXPPER
MPLS_PW_U MPLS_PW_LOCV, MPLS_PW_UNKNOWN, MPLS_PW_Excess,

NEXPMEP MPLS_PW_SF, MPLS_PW_SD, MPLS_PW_UNEXPPER
MPLS_PW_A MPLS_PW_LOCV, MPLS_PW_UNKNOWN, MPLS_PW_Excess,

IS MPLS_PW_SF, MPLS_PW_SD, MPLS_PW_UNEXPMEP,
MPLS_PW_UNEXPPER
MPLS_PW_L MPLS_PW_UNKNOWN, MPLS_PW_Excess, MPLS_PW_SF

OCV
MPLS_PW_S MPLS_PW_SD
F
MPLS_PW_L MPLS_PW_LOCV, MPLS_PW_SF, MPLS_PW_SD

CK
Table F-16 Suppression relationship between intra-board alarms (Tunnel APS)

ETH_APS_P ETH_APS_LOST
ATH_MISMA
TCH
ETH_APS_L ETH_APS_TYPE_MISMATCH, ETH_APS_SWITCH_FAIL

OST
Table F-17 Suppression relationship between intra-board alarms (PW APS)

PWAPS_SWI PWAPS_LOST, PWAPS_PATH_MISMATCH,

TCH_FAIL PWAPS_TYPE_MISMATCH
PWAPS_LOS PWAPS_PATH_MISMATCH, PWAPS_TYPE_MISMATCH

T

Table F-18 Suppression relationship between intra-board alarms (ETH OAM)

ETH_CFM_ ETH_CFM_LOC
MISMERGE
ETH_CFM_U
NEXPERI
ETH_CFM_A
IS
Table F-19 Suppression relationship between intra-board alarms (CES services)

CES_LOSPK CES_STRAYPKT_EXC, CES_JTROVR_EXC,

T_EXC CES_JTRUDR_EXC
CES_STRAY CES_MISORDERPKT_EXC, CES_MALPKT_EXC

PKT_EXC
Table F-20 Suppression relationship between intra-board alarms (ATM/IMA services)

IMA_GROU VC_LOC, VP_LOC

P_LE_DOW
N
ALM_IMA_L ALM_IMA_LODS
IF
ALM_E1RAI ALM_IMA_RFI, ALM_IMA_RE_RX_UNUSABLE
T_ALOS UP_E1_AIS
UP_E1_AIS LFA, ALM_E1RAI
LFA LMFA, ALM_IMA_LIF, ALM_E1RAI
LMFA ALM_IMA_LIF
Table F-21 Suppression relationship between intra-board alarms (PPP)

PPP_LCP_FA PPP_NCP_FAIL
IL

Table F-22 Suppression relationship between intra-board alarms (EoS/EoPDH)

TU_AIS_VC1 LP_TIM_VC12, LP_SLM_VC12, LP_UNEQ_VC12, LP_RDI_VC12

2
TU_LOP_VC LP_TIM_VC12, LP_SLM_VC12, LP_UNEQ_VC12LP_RDI_VC12

12
LP_UNEQ_V LFA
C12
BIP_EXC BIP_SD
Table F-23 Suppression relationship between intra-board alarms (tunnel service - PW service)
MPLS_TUNN MPLS_PW_LOCV
EL_LOCV
MPLS_TUNN MPLS_PW_BDI
EL_BDI
MPLS_TUNN MPLS_PW_RDI
EL_RDI
MPLS_TUNN MPLS_PW_OAMFAIL
EL_OAMFAI
L
MPLS_TUNN MPLS_PW_LOCV
EL_LOCK
Inter-board Alarm Suppression on the Data Plane

The inter-board alarm suppression means that, when services are configured between two
boards on the same NE, the service alarm generated by the source board suppresses the
service alarm generated by the sink board. The data plane supports alarm suppression between
interface/IF boards and switching boards.

Table F-24 Suppression relationship between inter-board alarms (Ethernet Interface board-
Switching board)
LSR_NO_FIT MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL,

ED, MPLS_TUNNEL_FDI, MPLS_TUNNEL_BDI,
ETH_LOS, MPLS_TUNNEL_AIS, MPLS_TUNNEL_RDI,
LASER_MO MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
D_ERR MPLS_PW_UNKNOWN, MPLS_PW_Excess,
MPLS_TUNNEL_MISMERGE, MPLS_TUNNEL_MISMATCH,
MPLS_PW_UNEXPMEG, MPLS_TUNNEL_UNEXPMEP
Table F-25 Suppression relationship between inter-board alarms (IF board-Switching board)
R_LOC MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL
Table F-26 Suppression relationship between inter-board alarms (PPP interface board-
Switching board)
PPP_NCP_FA MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL,

IL, MPLS_TUNNEL_BDI
MP_DOWN

Maintenance Guide G Indicators of Boards
G Indicators of Boards
Indicators of Boards
Table G-1 Status explanation for indicators on the CSHN

Indicator State Meaning
STAT On (green) The board is working properly.
On (red) The board hardware is faulty.
Off l The board is not working.

l The board is not created.
l There is no power supplied to the
board.
PROG Blinks on (green) and off Software is being loaded to the board
at 100 ms intervals during the board power-on or reset
process.
Blinks on (green) and off The board software is in BIOS boot

at 300 ms intervals state during the board power-on or reset
process.
Blinks on (green) and off The active system control board is

at 1s intervals synchronizing data to the standby
system control board.
On (green) l The board is being powered on or

being reset, and the upper layer
software is being initialized.
l The board is running and the
software is running normally.
Blinks on (red) and off at The BOOTROM self-check fails during

100 ms intervals the board power-on or reset process.

On (red) l The memory self-check fails or

loading upper layer software fails
during the board power-on or reset
process.
l The logic file or upper layer
software is lost during the board
running process.
l The pluggable storage card is faulty.
l If database synchronization between
the active and standby system
control boards fails, the PROG
indicator on the standby system
control board is steady red.
SYNC On (green) The clock is working properly.
On (red) The clock source is lost or a clock

switchover occurs.
SRV On (green) The system is working properly.
On (red) A critical or major alarm is generated in

the system.
On (yellow) A minor or remote alarm is generated

in the system.
ACT On (green) In a 1+1 protected system, the board

works as the active one.
In an unprotected system, the board has
been activated.
Off In a 1+1 protected system, the board

works as the standby one.
In an unprotected system, the board is
not activated.
LOS1 On (red) The first line optical port is reporting

the R_LOS alarm.
Off The first line optical port is free of

R_LOS alarms.
LOS2 On (red) The second optical port on the line is

reporting the R_LOS alarm.
Off The second optical port on the line is

free of R_LOS alarms.
LINK1 On (green) The connection at the GE1 port is

working properly.

Off The connection at the GE1 port is

interrupted.
ACT1 On or blinking (yellow) Data is being transmitted or received at

the GE1 port.
Off No data is being transmitted or received

at the GE1 port.
LINK2 On (green) The connection at the GE2 port is

working properly.
Off The connection at the GE2 port is

interrupted.
ACT2 On or blinking (yellow) Data is being transmitted or received at

the GE2 port.
Off No data is being transmitted or received

at the GE2 port.
CRIT On (red) A critical alarm occurs on the NE.
MAJ On (orange) A major alarm occurs on the NE.
MIN On (yellow) A minor alarm occurs on the NE.
Table G-2 Status explanation for indicators on the CSHNA


l The board has not been created.
board.
process.

at 300 ms intervals state during the board power-on or
reset process.



Blinks on (red) and off at The BOOTROM self-check fails

100 ms intervals during the board power-on or reset
process.

process.
running process.
l If database synchronization
between the active and standby
system control boards fails, the
PROG indicator on the standby
system control board is steady red.

switchover occurs.
On (red) A critical or major alarm is generated

in the system.

in the system.

In an unprotected system, the board
has been activated.

not activated.
USB USB Blinks (red) The USB flash drive is online but
flash faulty, or the NE does not support the
drive USB flash drive.
Blinks on (yellow) and Data is being backed up to or

off at 300 ms intervals recovered from the USB flash drive.

On (red) Backing up data to or recovering data

from the USB flash drive failed.
On (green) l A USB flash drive is online.

l Data backup or recovery is
complete.
Off The USB flash drive is offline or the

NE cannot identify the USB flash
drive.
WLAN Steady green The WLAN module has been

module identified and is working properly.
Steady red The WLAN module is faulty.
Off l No WLAN module is connected

to the USB port.
l The WLAN module connected to
the USB port cannot be identified.

the R_LOS alarm.

R_LOS alarms.


L/A1-L/A2 On (green) The port is properly connected and is

not transmitting or receiving data.
On (red) An optical power alarm is reported

(applicable only to optical ports).
Blinks (yellow) The port is receiving or transmitting

data.
Off The port is not connected or is

incorrectly connected.

Table G-3 Status explanation for indicators on the CSHNU


board.
process.

reset process.



process.

process.
running process.

switchover occurs.


in the system.

in the system.

has been activated.

not activated.



complete.

drive.


to the USB port.

the R_LOS alarm.

R_LOS alarms.



L/A, L/A1, and L/A2 On (green) Port is connected correctly but is not
receiving or transmitting data.
Blinks on (red) and off at Port has received extremely high

300 ms intervals optical power (applicable only to an
optical port).
Blinks on (red) for 300 Port has received extremely low

ms and off for 700 ms at optical power (applicable only to an
1000 ms intervals optical port).
Blinks (yellow) Port is receiving or transmitting data.

Table G-4 Status explanation for indicators on the CSHNA


board.
process.

reset process.




process.

process.
running process.

switchover occurs.

in the system.

in the system.

has been activated.

not activated.




complete.

drive.


to the USB port.

the R_LOS alarm.

R_LOS alarms.


L/A1-L/A2 On (green) The port is properly connected and is

not transmitting or receiving data.
On (red) An optical power alarm is reported

(applicable only to optical ports).
Blinks (yellow) The port is receiving or transmitting

data.


Table G-5 Status explanation for indicators on the IF1

STAT On (green) The board is working

properly.
On (red) The board hardware is

faulty.
Off l The board is not

working.
l There is no power
supplied to the board.
SRV On (green) The services are normal.
On (red) A critical or major alarm

occurs in the services.
On (yellow) A minor or remote alarm

LINK On (green) The radio link is normal.
On (red) The radio link is faulty.
ODU On (green) The ODU is working

properly.
On (red) l The ODU is reporting

critical or major alarms.
l There is no power
supplied to the ODU.
On (yellow) The ODU is reporting minor

alarms.
Blinks on (yellow) and off at The antennas are not

300 ms intervals aligned.
Off The ODU is offline.
RMT On (yellow) The remote equipment is

reporting defects.
Off The remote equipment is

free of defects.
ACT On (green) l In a 1+1 protected

system, the board works
as the active one.
l In an unprotected
system, the board has
been activated.

Off l In a 1+1 protected

as the standby one.
l In an unprotected
system, the board is not
activated.
Table G-6 Status explanation for indicators on the IFU2


l There is no power supplied to the board.
On (red) A critical or major alarm occurs in the

services.
On (yellow) A minor or remote alarm occurs in the

services.
ODU On (green) The ODU is working properly.
On (red) l The ODU is reporting critical or major

alarms.
l There is no power supplied to the ODU.
On (yellow) The ODU is reporting minor alarms.
Blinks on (yellow) The antennas are not aligned.

and off at 300 ms
intervals
RMT On (yellow) The remote equipment is reporting defects.
Off The remote equipment is free of defects.

ACT On (green) l In a 1+1 protected system, the board

l In an unprotected system, the board has
been activated.
Off l In a 1+1 protected system, the board

l In an unprotected system, the board is
not activated.
Table G-7 Status explanation for indicators on the ISU2


properly.

faulty.

working.
l There is no power



properly.

l There is no power

alarms.



reporting defects.

free of defects.

as the active one.
l In an unprotected
been activated.

as the standby one.
l In an unprotected
activated.
Table G-8 Status explanation for indicators on the IFX2

XPIC On (green) The XPIC input signal is

normal.
On (red) The XPIC input signal is

lost.
Off The XPIC function is

disabled.

properly.

faulty.

working.
l There is no power




properly.

l There is no power

alarms.


reporting defects.

free of defects.

as the active one.
l In an unprotected
been activated.

as the standby one.
l In an unprotected
activated.
Table G-9 Status explanation for indicators on the ISX2

XPIC On (green) The XPIC input signal is

normal.
On (red) The XPIC input signal is

lost.

Off The XPIC function is

disabled.

properly.

faulty.

working.
l There is no power



properly.

l There is no power

alarms.


reporting defects.

free of defects.


as the active one.
l In an unprotected
been activated.

as the standby one.
l In an unprotected
activated.
Table G-10 Status explanation for indicators on an ISV3 board

XPIC On (green) XPIC input signals are

normal.
On (red) XPIC input signals are lost.
Off XPIC is disabled.

properly.

faulty.
Off The board is not working,

not created, or not powered
on.
SRV On (green) Services are normal.
On (red) A critical or major alarm has

been reported.

has been reported.

properly.

On (red) The ODU has reported a

critical or major alarm, or
was not powered on.
On (yellow) The ODU has reported a

minor alarm.
Blinks on (yellow) and off at Antennas are not well

RMT On (yellow) The remote equipment has

reported a defect.

free of defects.
ACT On (green) In a 1+1 protected system,

the board is working as the
main board.
In an unprotected system,
the board has been
activated.
Off In a 1+1 protected system,

the board is working as the
standby board.
In an unprotected system,
the board has not been
activated.
Table G-11 Status explanation for indicators on an ISM6 board


properly.

faulty.

on.

been reported.


has been reported.
LINK1 On (green) The first microwave link is

normal.
On (red) The first microwave link is

faulty.
Off l The ODU connected to

the IF1 port is offline.
l No logical board is
configured for the ODU
connected to IF1 port.
ACT1 On (green) l In a 1+1 protected

system, the first
microwave link is
working as the main link.
l In an unprotected
system, the first
microwave link has been
activated.

system, the first
microwave link is
working as the standby
link.
l In an unprotected
system, no logical board
is added for the ODU
LINK2 On (green) The second microwave link

is normal.
On (red) The second microwave link

is faulty.
Off l The ODU connected to

the IF2 port is offline.
l No logical board is
configured for the ODU

ACT2 On (green) l In a 1+1 protected

system, the second
microwave link is
working as the main link.
l In an unprotected
system, the second
microwave link has been
activated.

system, the second
microwave link is
working as the standby
link.
l In an unprotected
system, no logical board
is added for the ODU
Table G-12 Status explanation for indicators on the EM6T/EM6F


board.

system.
On (yellow) A minor alarm occurs in the system.
Off There is no power supplied to the system.
PROG Blinks on (green) and off at Software is being loaded to the board
100 ms intervals during the power-on or resetting process of
the board.
Blinks on (green) and off at The board software is in BIOS boot state
the board.

On (green) l When the board is being powered on or

being reset, the upper layer software is
being initialized.
l When the board is running, the
Blinks on (red) and off at 100 The BOOTROM self-check fails during
ms intervals the power-on or resetting process of the
board.
On (red) l The memory self-check fails or loading

upper layer software fails during the
power-on or resetting process of the
board.
l The logic file or upper layer software is
lost during the running process of the
board.
LINK1a On (green) The GE1 port is connected correctly and is

not receiving or transmitting data.
Blinking (green) The GE1 port is receiving or transmitting

data.
Off The GE1 port is not connected or is

LINK2a On (green) The GE2 port is connected correctly and is

Blinking (green) The GE2 port is receiving or transmitting

data.

NOTE
a: The LINK1 and LINK2 indicators are available only on the EM6F and indicate the states of the
corresponding GE ports.
Table G-13 Status explanation for indicators on the EM6TA/EM6FA



board.

system.
the board.
the board.

being initialized.
board.
On (red) The memory self-check fails or loading

power-on or resetting process of the board.
The logic file or upper layer software is
board.
The pluggable storage card is faulty.
L/A1a On (green) The GE1 port is connected correctly and is

Blinking (yellow) The GE1 port is receiving or transmitting

data.

L/A2a On (green) The GE2 port is connected correctly and is


Blinking (yellow) The GE2 port is receiving or transmitting

data.

NOTE
a: The L/A1 and L/A2 indicators are available only on the EM6FA and indicate the states of the
corresponding GE ports.
Table G-14 Status explanation for indicators on an EG4/EG4P board

Off The board is not working, not created, or

not powered on.
On (red) A critical or major alarm has been

reported.
On (yellow) A minor alarm has been reported.
Off No service is configured.
L/A1 On (green) Port GE1 is connected correctly but is not

(optical/ receiving or transmitting data.
electrical
port 1) Blinks on (red) and off at 300 Port GE1 has received extremely high
ms intervals optical power (applicable only to an
optical port).
Blinks on (red) for 300 ms Port GE1 has received extremely low
and off for 700 ms at 1000 ms optical power (applicable only to an
intervals optical port).
Blinks (yellow) Port GE1 is receiving or transmitting data.
Off Port GE1 is not connected or is incorrectly

connected.

electrical
optical port).


connected.

(electrical receiving or transmitting data.
port 3)

connected.

(electrical receiving or transmitting data.
port 4)

connected.
P1 On (green) Power over Ethernet port 1 is enabled.
Off Power over Ethernet port 1 is disabled or is

working abnormally.
P2 On (green) Power over Ethernet port 2 is enabled.
Off Power over Ethernet port 2 is disabled or is

working abnormally.
NOTE
Indicators P1 and P2 are available only on the front panels of EG4P boards, indicating the power supply
status of power-over-Ethernet ports.
Table G-15 Status explanation for indicators on an EM6 board

Off The board is not working, not created, or

not powered on.
On (red) A critical or major alarm has been

reported.

On (yellow) A minor alarm has been reported.

electrical
optical port).

connected.

electrical
optical port).

connected.

electrical
optical port).

connected.

electrical
port 4)

Blinks on (red) and off at 300 Port GE4 has received extremely high
optical port).

connected.
Table G-16 Status explanation for indicators on an EX1


properly.

faulty.
Off l The board is not working

or created.
l There is no power
SRV On (green) The system/service is

normal.

occurs in the system/service.

occurs in the system/service.
L/A On (green) The port is connected

correctly (link up), but is not
receiving or transmitting
data.
Blinks (red) three times The port on the board

every second, 300 ms on receives too strong power.
and 300 ms off
Blinks (red) once every The port on the board

second, 300 ms on and 700 receives too weak power.
ms off

Blinks (orange) The port is connected

correctly (link up), and is
receiving and transmitting
data.
Off The optical fiber is not

connected to the port, or the
port is abnormal (link down/
LOS).
Table G-17 Status explanation for indicators on the EMS6

board.
the board.
the board.
On (green) l The upper layer software is being

initialized during the power-on or
resetting process of the board.
l The software is running properly
during the running process of the
board.
board.

board.
board.

SRV On (green) The system is working normally.

system.
LINK1 On (green) The GE1 port is connected correctly.
Blinks on (red) and off at 300 The receive optical power at the GE1
ms intervals optical port is higher than the upper
threshold.
Blinks 300 ms on (red) and The receive optical power at the GE1
700 ms off optical port is lower than the lower
threshold.

ACT1 Blinking (yellow) The GE1 port is receiving or transmitting

data.
Off The GE1 port is not receiving or

transmitting data.
LINK2 On (green) The GE2 port is connected correctly.
Blinks on (red) and off at 300 The receive optical power at the GE2
ms intervals optical port is higher than the upper
threshold.
Blinks 300 ms on (red) and The receive optical power at the GE2
700 ms off optical port is lower than the lower
threshold.

ACT2 Blinking (yellow) The GE2 port is receiving or transmitting

data.
Off The GE2 port is not receiving or

transmitting data.
Table G-18 Status explanation for indicators on the EFP8


board.
the board.
the board.

being initialized.
board.

board.
board.

system.
Table G-19 Status explanation for indicators on the SL1D/SL1DA


properly.

faulty.


working.
l There is no power


Off The services are not

configured.
LOS1 On (red) The first port of the SL1D/

SL1DA is reporting the
R_LOS alarm.
Off The first port of the SL1D/

SL1DA is free of R_LOS
alarms.
LOS2 On (red) The second port of the

SL1D/SL1DA is reporting
the R_LOS alarm.
Off The second port of the

SL1D/SL1DA is free of
R_LOS alarms.
Table G-20 Status explanation for indicators on the SP3S/SP3D


properly.

faulty.

working.
l There is no power




configured.
Table G-21 Status explanation for indicators on the ML1/MD1


properly.

faulty.

working.
l There is no power



configured.
Table G-22 Status explanation for indicators on a CQ1 board


properly.

faulty.

on.


been reported.

has been reported.
LOS1 On (red) The first port has reported

an R_LOS alarm.
Off The first port does not report

any R_LOS alarms.
LOS2 On (red) The second port has

reported an R_LOS alarm.
Off The second port does not

report any R_LOS alarms.
LOS3 On (red) The third port has reported

an R_LOS alarm.
Off The third port does not

LOS4 On (red) The fourth port has reported

an R_LOS alarms.
Off The fourth port does not

Table G-23 Status explanation for indicators on the AUX


board.

system.

On (yellow) A minor or remote alarm occurs in the

system.
Off There is no power supplied to the

system.
Table G-24 Status explanation for indicators on the PIU

Indicator Status Description
PWR On (green) The power supply is normal.
Off There is no power supply.
ALM On (orange) The board is in the initialization state.
On (red) An alarm is reported on the PIU.
Off No alarm occurs.
Table G-25 Status explanation for indicators on the FAN

FAN On (green) The fan is working properly.
On (red) The fan is faulty.
Off The fan is not powered on or is not installed.


RTN 980 V100R009C10 Maintenance Guide 02 PDF

Uploaded by

Document Information

Original Title

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 980 V100R009C10 Maintenance Guide 02 PDF

Uploaded by

Copyright:

Available Formats

OptiX RTN 980 Radio Transport System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2017-05-20) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX RTN 980 V100R009C10

iManager U2000 V200R016C60

This document is intended for:

l Network planning engineer

Indicates an imminently hazardous situation

Issue 02 (2017-05-20) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Indicates a potentially hazardous situation

Calls attention to important information,

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Issue 02 (2017-05-20) Huawei Proprietary and Confidential iii

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Updates in Issue 02 (2017-05-20) Based on Product Version V100R009C10

- Fixed known defects.

Issue 02 (2017-05-20) Huawei Proprietary and Confidential iv

Updates in Issue 01 (2016-12-30) Based on Product Version V100R009C10

Issue 02 (2017-05-20) Huawei Proprietary and Confidential v

About This Document.....................................................................................................................ii

2 Notices for High-Risk Operations........................................................................................... 19

Issue 02 (2017-05-20) Huawei Proprietary and Confidential vi

4.3.5 Browsing the Performance Event Threshold-Crossing Records............................................................................... 45

Issue 02 (2017-05-20) Huawei Proprietary and Confidential vii

5.1 General Troubleshooting Procedure........................................................................................................................... 100

6 Part Replacement....................................................................................................................... 176

Issue 02 (2017-05-20) Huawei Proprietary and Confidential viii

6.17.1 Board Storage Media............................................................................................................................................. 206

7 Database Backup and Restoration......................................................................................... 209

8 Common Maintenance Operations........................................................................................ 228

Issue 02 (2017-05-20) Huawei Proprietary and Confidential ix

8.4.1 Setting Loopback for the SDH Optical Interface Board..........................................................................................271

A Alarm Reference....................................................................................................................... 307

Issue 02 (2017-05-20) Huawei Proprietary and Confidential x

A.2.14 EMS6.................................................................................................................................................................... 341

Issue 02 (2017-05-20) Huawei Proprietary and Confidential xi

Issue 02 (2017-05-20) Huawei Proprietary and Confidential xii

A.3.66 CPU_BUSY.......................................................................................................................................................... 440

Issue 02 (2017-05-20) Huawei Proprietary and Confidential xiii

A.3.108 EX_ETHOAM_CC_LOS................................................................................................................................... 497

Issue 02 (2017-05-20) Huawei Proprietary and Confidential xiv

A.3.150 K2_M.................................................................................................................................................................. 548

Issue 02 (2017-05-20) Huawei Proprietary and Confidential xv

A.3.192 LP_RFI............................................................................................................................................................... 603

Issue 02 (2017-05-20) Huawei Proprietary and Confidential xvi

A.3.234 MPLS_PW_UNEXPMEP.................................................................................................................................. 649

Issue 02 (2017-05-20) Huawei Proprietary and Confidential xvii