RTN 980 V100R019C10 Maintenance Guid

OptiX RTN 980 Radio Transport System
V100R019C10
Maintenance Guide
Issue 01
Date 2019-12-31
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. i

Maintenance Guide Contents
Contents
1 About This Document.............................................................................................................1

2 Safety Precautions...................................................................................................................4
2.1 General Safety Precautions.................................................................................................................................................. 5
2.2 Warning and Safety Symbols.............................................................................................................................................. 6
2.3 Electrical Safety........................................................................................................................................................................ 7
2.4 Environment of Flammable Gas...................................................................................................................................... 10
2.5 Storage Batteries................................................................................................................................................................... 10
2.6 Radiation.................................................................................................................................................................................. 12
2.6.1 Safe Usage of Optical Fibers......................................................................................................................................... 12
2.6.2 Electromagnetic Exposure.............................................................................................................................................. 14
2.6.3 Forbidden Areas................................................................................................................................................................. 15
2.6.4 Laser....................................................................................................................................................................................... 15
2.6.5 Microwave............................................................................................................................................................................ 16
2.7 Working at Heights.............................................................................................................................................................. 16
2.7.1 Hoisting Heavy Objects................................................................................................................................................... 17
2.7.2 Using Ladders..................................................................................................................................................................... 18
2.8 Mechanical Safety.................................................................................................................................................................19
2.9 Other Precautions................................................................................................................................................................. 20
3 Notices for High-Risk Operations......................................................................................22

3.1 Operation Guide for the Toggle Lever Switch.............................................................................................................22
3.2 Operation Guide for the IF Jumper.................................................................................................................................25
3.3 Operation Guide for the IF Cables.................................................................................................................................. 26
3.4 Operation Guide for the IF Board................................................................................................................................... 28
4 Routine Maintenance........................................................................................................... 30
5 Network Monitoring.............................................................................................................35
5.1 Checking the Board Status................................................................................................................................................ 35
5.2 Alarm and Performance Data Query............................................................................................................................. 36
5.2.1 Browsing Current Alarms................................................................................................................................................ 36
5.2.2 Browsing Historical Alarms............................................................................................................................................ 40
5.2.3 Browsing Current Performance Events...................................................................................................................... 42
5.2.4 Browsing Historical Performance Events...................................................................................................................43
5.2.5 Browsing the Performance Event Threshold-Crossing Records......................................................................... 45
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. ii

5.2.6 Browsing UAT Events....................................................................................................................................................... 46

5.3 Microwave Link Performance Query.............................................................................................................................. 48
5.3.1 Querying the Historical Transmit Power and Receive Power............................................................................. 48
5.3.2 Querying the SNR Values of a Radio Link................................................................................................................ 49
5.3.3 Browsing Current Performance Events of the radio link......................................................................................50
5.3.4 Browsing Historical Performance Data of a Radio Link.......................................................................................51
5.4 Ethernet Performance Query............................................................................................................................................ 52
5.4.1 Browsing Current Ethernet Performance.................................................................................................................. 52
5.4.2 Configuring Ethernet Performance Threshold-Crossing Parameters............................................................... 57
5.4.3 Setting Parameters for Monitoring Historical Ethernet Performance............................................................. 61
5.4.4 Browsing Historical Ethernet Performance Data....................................................................................................62
5.5 Ethernet Port Traffic Monitoring..................................................................................................................................... 66
5.5.1 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports....................................... 66
5.5.2 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization......................................................................67
5.6 Long-term Network Performance Monitoring............................................................................................................68
5.6.1 Creating a Performance Monitoring Template....................................................................................................... 68
5.6.2 Creating a Performance Monitoring Instance......................................................................................................... 70
5.6.3 Browsing the Real-Time Data of a Performance Monitoring Instance........................................................... 72
5.6.4 Browsing the Historical Data of a Performance Monitoring Instance............................................................ 74
5.7 Report Query.......................................................................................................................................................................... 74
5.7.1 Querying the Microwave Link Information Report................................................................................................ 74
5.7.2 Querying the Network-wide License Report............................................................................................................ 75
5.7.3 Querying the Microwave Configuration Report......................................................................................................77
5.7.4 Querying the Board Information Report................................................................................................................... 78
5.7.5 Querying the Board Manufacturing Information Report.................................................................................... 79
5.7.6 Querying the ODU Information Report..................................................................................................................... 80
5.8 Alarm and Performance Management Setting.......................................................................................................... 81
5.8.1 Configuring the Performance Monitoring Status of NEs.....................................................................................81
5.8.2 Setting Severity and Auto Reporting Status of Alarms........................................................................................ 83
5.8.3 Suppressing Alarms for Monitored Objects..............................................................................................................83
5.8.4 Suppressing Alarms for NEs........................................................................................................................................... 84
5.8.5 Reversing Alarms for Service Ports..............................................................................................................................85
5.8.6 Setting the Reporting of Alarms and Performance Events for an IF Port and the Corresponding ODU
............................................................................................................................................................................................................ 86
5.8.7 Setting Trigger Conditions of AIS Insertion.............................................................................................................. 87
5.8.8 Setting Trigger Conditions of UNEQ Insertion........................................................................................................ 88
5.8.9 Setting Bit Error Thresholds for Service Ports..........................................................................................................88
5.8.10 Setting the Alarm Threshold for Insufficient Fade Margin............................................................................... 89
5.8.11 Setting Monitoring and Auto-Report Status of Performance Events............................................................90
5.8.12 Setting Performance Thresholds................................................................................................................................ 91
5.8.13 Resetting Performance Registers............................................................................................................................... 91
6 Troubleshooting.....................................................................................................................93
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. iii

6.1 General Troubleshooting Procedure............................................................................................................................... 94

6.2 Troubleshooting Service Interruptions........................................................................................................................... 96
6.3 Troubleshooting the Radio Link.....................................................................................................................................103
6.4 Troubleshooting Bit Errors in TDM Services.............................................................................................................. 110
6.5 Troubleshooting Pointer Justifications........................................................................................................................ 115
6.6 Troubleshooting the Interconnection with SDH Equipment................................................................................119
6.7 Troubleshooting the Interconnection with PDH Equipment................................................................................122
6.8 Troubleshooting Native Ethernet Service Faults...................................................................................................... 126
6.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane...............................................................................129
6.10 Troubleshooting MPLS Tunnels................................................................................................................................... 135
6.11 Troubleshooting CES Services...................................................................................................................................... 139
6.12 Troubleshooting ATM Services.................................................................................................................................... 146
6.13 Troubleshooting Ethernet Services Carried by PWs............................................................................................. 152
6.14 Troubleshooting DCN Faults........................................................................................................................................ 156
6.15 Troubleshooting Orderwire Faults.............................................................................................................................. 160
6.16 Typical Cases...................................................................................................................................................................... 162
6.16.1 Transient Link Unavailability Due to Multi-path Fading.................................................................................162
6.16.2 Transoceanic Link Transient Unavailability Due to Insufficient Height Difference between Diversity
Antennas....................................................................................................................................................................................... 164
6.16.3 Link Unavailability Due to Inter-building Reflection........................................................................................ 165
6.16.4 Unidirectional Link Availability Due to Interference........................................................................................ 166
6.16.5 Bit Errors on Microwave Links.................................................................................................................................. 167
6.16.6 Poor Reliability Due to Network Planning Errors.............................................................................................. 168
7 Part Replacement................................................................................................................170
7.1 Removing a Board.............................................................................................................................................................. 171
7.2 Inserting a Board................................................................................................................................................................ 174
7.3 Replacing the SDH Optical Interface Board.............................................................................................................. 176
7.4 Replacing the Channelized STM-1 Processing Board.............................................................................................178
7.5 Replacing the PDH Interface Board............................................................................................................................. 179
7.6 Replacing the Smart E1 Interface Board.................................................................................................................... 179
7.7 Replacing the Ethernet Interface Board..................................................................................................................... 180
7.8 Replacing an IF Board....................................................................................................................................................... 182
7.9 Replacing an Single-Channel IF Board with the ISM6...........................................................................................184
7.10 Replacing the CF Card.................................................................................................................................................... 188
7.11 Replacing the System Control, Switching and Timing Board........................................................................... 189
7.12 Replacing the Auxiliary Board..................................................................................................................................... 194
7.13 Replacing the Fan Board............................................................................................................................................... 195
7.14 Replacing the Power Board.......................................................................................................................................... 197
7.15 Replacing the SFP............................................................................................................................................................ 198
7.16 Replacing an ODU........................................................................................................................................................... 200
7.17 Replacing an IF Cable..................................................................................................................................................... 203
7.18 Erasing Data in the Repair Parts................................................................................................................................. 205
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. iv

7.18.1 Board Storage Media...................................................................................................................................................205

7.18.2 Removing the CF Card................................................................................................................................................ 205
7.18.3 Formatting the Flash Memory................................................................................................................................. 206
8 Database Backup and Restoration..................................................................................208

8.1 NE Database.........................................................................................................................................................................208
8.2 Backing Up the Database Manually............................................................................................................................ 210
8.3 Setting the Database Backup Policy............................................................................................................................ 212
8.3.1 Setting the User-Defined Backup Policy................................................................................................................. 212
8.3.2 Enable the Backup Policy of the Device.................................................................................................................. 214
8.3.3 Disable the Backup Policy of the Device.................................................................................................................215
8.4 Restoring the Database by NMS................................................................................................................................... 217
8.5 Recovering Databases from a USB Flash Drive........................................................................................................220
8.6 Restoring Databases for an NE from Its Peer NE....................................................................................................222
8.7 Restoring Databases from Local NEs.......................................................................................................................... 224
9 Common Maintenance Operations.................................................................................227

9.1 Microwave Link Troubleshooting.................................................................................................................................. 228
9.1.1 Monitoring Radio Link Indicators.............................................................................................................................. 228
9.1.2 Scanning Interfering Signals....................................................................................................................................... 230
9.1.3 Muting/Unmuting an ODU......................................................................................................................................... 231
9.1.4 Turning On/Off the Soft Power Switch of an ODU.............................................................................................232
9.1.5 Performing a PRBS Test for the IF Board................................................................................................................ 233
9.2 Ethernet Service Troubleshooting................................................................................................................................. 235
9.2.1 Querying the Attributes of an Ethernet Port.........................................................................................................235
9.2.2 Using IP Ping Commands to Locate Ethernet Service Faults........................................................................... 236
9.2.3 Monitoring Ethernet Packets Through Port Mirroring....................................................................................... 242
9.2.4 Monitoring Ethernet Packets by Using Port Traffic Mirroring.........................................................................243
9.2.5 Capturing Headers of Specified Ethernet Packets............................................................................................... 245
9.2.6 Using the Ethernet Test Frames................................................................................................................................. 247
9.3 TDM/CES Service Troubleshooting............................................................................................................................... 248
9.3.1 Setting the On/Off State of the Laser..................................................................................................................... 248
9.3.2 Setting the ALS Function.............................................................................................................................................. 249
9.3.3 Performing a PRBS Test for the Smart E1 Processing Board............................................................................250
9.3.4 Performing a PRBS Test for the Tributary Board.................................................................................................. 253
9.3.5 Querying the Impedance of an E1 Channel.......................................................................................................... 256
9.4 Software Loopback............................................................................................................................................................ 257
9.4.1 Setting Loopback for the SDH Optical Interface Board.....................................................................................257
9.4.2 Setting Loopback for the Channelized STM-1 Processing Board................................................................... 260
9.4.3 Setting Loopback for the Tributary Board.............................................................................................................. 261
9.4.4 Setting a Loopback for the Smart E1 Processing Board.................................................................................... 263
9.4.5 Setting a Loopback for the Packet-plane Ethernet Interface Board..............................................................264
9.4.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board..................................................... 266
9.4.7 Setting Loopback for the IF Board............................................................................................................................ 269
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. v

9.4.8 Setting Software Loopback for the NE.................................................................................................................... 272

9.4.9 Setting Software Loopback for the Microwave Link........................................................................................... 273
9.4.10 Locating a Fault by Performing Loopback Operations.................................................................................... 274
9.5 Hardware Loopback...........................................................................................................................................................275
9.6 Reset....................................................................................................................................................................................... 276
9.6.1 Cold Reset.......................................................................................................................................................................... 276
9.6.2 Warm Reset....................................................................................................................................................................... 277
9.7 Setting the Automatic Release Function.................................................................................................................... 278
9.8 Querying Site Information...............................................................................................................................................279
9.9 Querying Power Consumption of Boards...................................................................................................................281
9.10 Querying Optical Power and Alarm Thresholds of SDH Ports......................................................................... 283
9.11 Preventing Service Loops............................................................................................................................................... 283
9.11.1 Setting the Enabling Status of Automatic Service Loop Detection for NEs............................................. 283
9.11.2 Enabling the Automatic Broadcast Packet Suppression Function............................................................... 287
9.11.3 Enabling Loop Detection Upon MAC Address Flapping..................................................................................289
9.12 Switching the System Control Unit and the Cross-Connect Unit.................................................................... 290
9.13 Cleaning Fiber Connectors and Adapters................................................................................................................ 291
9.13.1 Cleaning Fiber Connectors by Using Cartridge Cleaners................................................................................ 291
9.13.2 Cleaning Fiber Connectors by Using Lens Tissue.............................................................................................. 293
9.13.3 Cleaning Fiber Adapters by Using Optical Cleaning Sticks............................................................................ 294
10 Alarm Reference................................................................................................................296
10.1 Alarm List (in Alphabetical Order)............................................................................................................................ 296
10.2 Alarms and Handling Procedures............................................................................................................................... 317
10.2.1 ACR_LOCK_FAIL............................................................................................................................................................. 317
10.2.2 AES_MAC_ERR................................................................................................................................................................319
10.2.3 ALM_E1RAI...................................................................................................................................................................... 320
10.2.4 ALM_GFP_dCSF..............................................................................................................................................................320
10.2.5 ALM_GFP_dLFD............................................................................................................................................................. 322
10.2.6 ALM_IMA_LIF................................................................................................................................................................. 323
10.2.7 ALM_IMA_LODS............................................................................................................................................................ 324
10.2.8 ALM_IMA_RE_RX_UNUSABLE................................................................................................................................... 325
10.2.9 ALM_IMA_RE_TX_UNUSABLE................................................................................................................................... 327
10.2.10 ALM_IMA_RFI.............................................................................................................................................................. 328
10.2.11 AM_DOWNSHIFT....................................................................................................................................................... 330
10.2.12 APS_FAIL........................................................................................................................................................................ 332
10.2.13 APS_INDI....................................................................................................................................................................... 333
10.2.14 APS_MANUAL_STOP................................................................................................................................................. 334
10.2.15 APS_STATUS_INDI...................................................................................................................................................... 335
10.2.16 ARP_FAIL........................................................................................................................................................................338
10.2.17 ARP_MAC_MISMATCH.............................................................................................................................................. 339
10.2.18 ARP_SPOOF.................................................................................................................................................................. 339
10.2.19 ATMPW_UNKNOWNCELL_EXC..............................................................................................................................341
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. vi

10.2.20 AU_AIS........................................................................................................................................................................... 342

10.2.21 AU_LOP.......................................................................................................................................................................... 343
10.2.22 B1_EXC........................................................................................................................................................................... 344
10.2.23 B1_SD............................................................................................................................................................................. 347
10.2.24 B2_EXC........................................................................................................................................................................... 349
10.2.25 B2_SD............................................................................................................................................................................. 352
10.2.26 B3_EXC........................................................................................................................................................................... 354
10.2.27 B3_EXC_VC3................................................................................................................................................................. 357
10.2.28 B3_SD............................................................................................................................................................................. 359
10.2.29 B3_SD_VC3....................................................................................................................................................................361
10.2.30 BAT1TEMP_SENSOR_FAIL....................................................................................................................................... 364
10.2.31 BAT2TEMP_SENSOR_FAIL....................................................................................................................................... 365
10.2.32 BD_NOT_INSTALLED................................................................................................................................................. 366
10.2.33 BD_STATUS................................................................................................................................................................... 367
10.2.34 BDTEMP_SENSOR_FAIL............................................................................................................................................ 369
10.2.35 BGPBACKTRANSITION.............................................................................................................................................. 370
10.2.36 BIOS_STATUS............................................................................................................................................................... 372
10.2.37 BIP_EXC.......................................................................................................................................................................... 373
10.2.38 BIP_SD............................................................................................................................................................................ 375
10.2.39 BOOTROM_BAD......................................................................................................................................................... 377
10.2.40 BRDCASTRATIO_OVER............................................................................................................................................. 378
10.2.41 BUS_ERR........................................................................................................................................................................ 380
10.2.42 CA_CFG_MISMATCH.................................................................................................................................................. 387
10.2.43 CES_ACR_LOCK_ABN................................................................................................................................................. 389
10.2.44 CES_APS_INDI.............................................................................................................................................................. 391
10.2.45 CES_APS_MANUAL_STOP........................................................................................................................................ 393
10.2.46 CES_JTROVR_EXC........................................................................................................................................................ 394
10.2.47 CES_JTRUDR_EXC....................................................................................................................................................... 395
10.2.48 CES_K1_K2_M.............................................................................................................................................................. 396
10.2.49 CES_K2_M..................................................................................................................................................................... 398
10.2.50 CES_LOSPKT_EXC........................................................................................................................................................ 399
10.2.51 CES_MALPKT_EXC...................................................................................................................................................... 400
10.2.52 CES_MISORDERPKT_EXC..........................................................................................................................................401
10.2.53 CES_RDI......................................................................................................................................................................... 402
10.2.54 CES_STRAYPKT_EXC................................................................................................................................................... 403
10.2.55 CESPW_OPPOSITE_ACFAULT.................................................................................................................................. 403
10.2.56 CESPW_OPPOSITE_RAI............................................................................................................................................. 404
10.2.57 CFCARD_FAILED.......................................................................................................................................................... 405
10.2.58 CFCARD_FULL.............................................................................................................................................................. 406
10.2.59 CFCARD_OFFLINE.......................................................................................................................................................407
10.2.60 CFCARD_W_R_DISABLED......................................................................................................................................... 409
10.2.61 CHCS............................................................................................................................................................................... 410
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. vii

10.2.62 CLK_LOCK_FAIL........................................................................................................................................................... 411

10.2.63 CLK_NO_TRACE_MODE............................................................................................................................................ 413
10.2.64 COMBO_PORT_CFG_MISMATCH.......................................................................................................................... 414
10.2.65 COMMUN_FAIL........................................................................................................................................................... 415
10.2.66 COM_EXTECC_FULL................................................................................................................................................... 417
10.2.67 CONFIG_NOSUPPORT.............................................................................................................................................. 418
10.2.68 CPU_BUSY..................................................................................................................................................................... 421
10.2.69 DBMS_DELETE............................................................................................................................................................. 422
10.2.70 DBMS_ERROR.............................................................................................................................................................. 423
10.2.71 DBMS_PROTECT_MODE...........................................................................................................................................426
10.2.72 DB_UNSAVE................................................................................................................................................................. 427
10.2.73 DCN_CHANNEL_BITERROR..................................................................................................................................... 428
10.2.74 DCNCFG_NOT_COMMIT.......................................................................................................................................... 430
10.2.75 DCNLINK_OVER.......................................................................................................................................................... 431
10.2.76 DCNSIZE_OVER........................................................................................................................................................... 432
10.2.77 DDN_LFA....................................................................................................................................................................... 433
10.2.78 DOWN_E1_AIS.............................................................................................................................................................434
10.2.79 DEVICE_AUTH_FAIL................................................................................................................................................... 435
10.2.80 DROPRATIO_OVER.................................................................................................................................................... 436
10.2.81 E1_LOS........................................................................................................................................................................... 438
10.2.82 ELAN_SMAC_FLAPPING........................................................................................................................................... 439
10.2.83 ENERGY_CFG_MISMATCH....................................................................................................................................... 441
10.2.84 ENERGY_INPROCESS................................................................................................................................................. 443
10.2.85 ENVHUM_SENSOR_FAIL.......................................................................................................................................... 444
10.2.86 ENVTEMP_SENSOR_FAIL......................................................................................................................................... 445
10.2.87 ENVTEMP1_SENSOR_FAIL....................................................................................................................................... 446
10.2.88 ENVTEMP2_SENSOR_FAIL....................................................................................................................................... 447
10.2.89 ERPS_BLOCK................................................................................................................................................................. 449
10.2.90 ERPS_CFM_FAIL........................................................................................................................................................... 450
10.2.91 ERPS_IN_PROTECTION............................................................................................................................................. 451
10.2.92 ERPS_NOT_COMPLETE............................................................................................................................................. 452
10.2.93 ETH_APS_LOST............................................................................................................................................................ 453
10.2.94 ETH_APS_PATH_MISMATCH...................................................................................................................................455
10.2.95 ETH_APS_SWITCH_FAIL............................................................................................................................................ 456
10.2.96 ETH_APS_TYPE_MISMATCH.................................................................................................................................... 457
10.2.97 ETH_AUTO_LINK_DOWN.........................................................................................................................................458
10.2.98 ETH_CFM_AIS.............................................................................................................................................................. 459
10.2.99 ETH_CFM_LOC............................................................................................................................................................. 460
10.2.100 ETH_CFM_MISMERGE............................................................................................................................................ 464
10.2.101 ETH_CFM_RDI........................................................................................................................................................... 467
10.2.102 ETH_CFM_UNEXPERI.............................................................................................................................................. 470
10.2.103 ETH_EFM_DF............................................................................................................................................................. 473
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. viii

10.2.104 ETH_EFM_EVENT..................................................................................................................................................... 474

10.2.105 ETH_EFM_LOOPBACK.............................................................................................................................................476
10.2.106 ETH_EFM_REMFAULT............................................................................................................................................. 478
10.2.107 ETH_LINK_DOWN.................................................................................................................................................... 479
10.2.108 ETH_LOS......................................................................................................................................................................480
10.2.109 ETH_NO_FLOW......................................................................................................................................................... 483
10.2.110 ETH_PWR_SUPPLY_FAIL......................................................................................................................................... 484
10.2.111 ETHOAM_DISCOVER_FAIL.................................................................................................................................... 485
10.2.112 ETHOAM_RMT_CRIT_FAULT.................................................................................................................................486
10.2.113 ETHOAM_RMT_LOOP.............................................................................................................................................488
10.2.114 ETHOAM_RMT_SD.................................................................................................................................................. 489
10.2.115 ETHOAM_SELF_LOOP.............................................................................................................................................491
10.2.116 ETHOAM_VCG_SELF_LOOP.................................................................................................................................. 493
10.2.117 EX_ETHOAM_CC_LOS............................................................................................................................................. 495
10.2.118 EX_ETHOAM_MPID_CNFLCT................................................................................................................................ 496
10.2.119 EXT_SYNC_LOS..........................................................................................................................................................497
10.2.120 EXT_TIME_LOC.......................................................................................................................................................... 499
10.2.121 FAN_AGING................................................................................................................................................................ 500
10.2.122 FAN_FAIL..................................................................................................................................................................... 501
10.2.123 FCS_ERR.......................................................................................................................................................................502
10.2.124 FDBSIZEALM_ELAN................................................................................................................................................. 504
10.2.125 FLOW_EXC_LCS......................................................................................................................................................... 505
10.2.126 FLOW_OVER.............................................................................................................................................................. 506
10.2.127 GNE_CONNECT_FULL............................................................................................................................................. 507
10.2.128 GPSMOD_INVALID.................................................................................................................................................. 508
10.2.129 GPSMOD_LOCK_FAIL.............................................................................................................................................. 510
10.2.130 GSP_RSVP_NB_AUTH_ERR.................................................................................................................................... 511
10.2.131 GSP_RSVP_NB_DOWN........................................................................................................................................... 512
10.2.132 GSP_TNNL_DOWN.................................................................................................................................................. 513
10.2.133 HARD_ERR.................................................................................................................................................................. 516
10.2.134 HARD_BAD................................................................................................................................................................. 518
10.2.135 HARD_NONSUPPORT.............................................................................................................................................520
10.2.136 HP_CROSSTR............................................................................................................................................................. 522
10.2.137 HP_LOM...................................................................................................................................................................... 523
10.2.138 HP_RDI......................................................................................................................................................................... 525
10.2.139 HP_REI......................................................................................................................................................................... 525
10.2.140 HP_SLM....................................................................................................................................................................... 526
10.2.141 HP_TIM........................................................................................................................................................................ 527
10.2.142 HP_UNEQ....................................................................................................................................................................528
10.2.143 HPAD_CROSSTR....................................................................................................................................................... 529
10.2.144 IF_CABLE_ABN.......................................................................................................................................................... 530
10.2.145 IF_CABLE_OPEN........................................................................................................................................................ 532
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. ix

10.2.146 IF_INPWR_ABN......................................................................................................................................................... 533

10.2.147 IF_MODE_UNSUPPORTED.................................................................................................................................... 535
10.2.148 IGSP_ENTRIES_EXC.................................................................................................................................................. 536
10.2.149 IMA_GROUP_LE_DOWN........................................................................................................................................ 538
10.2.150 IMA_GROUP_RE_DOWN....................................................................................................................................... 539
10.2.151 IMA_TXCLK_MISMATCH........................................................................................................................................ 540
10.2.152 IN_PWR_ABN............................................................................................................................................................. 541
10.2.153 IN_PWR_HIGH........................................................................................................................................................... 543
10.2.154 IN_PWR_LOW............................................................................................................................................................ 544
10.2.155 INSUFFCNT_MEM_SPACE......................................................................................................................................545
10.2.156 INSUFFCNT_FLSH_SPACE...................................................................................................................................... 547
10.2.157 INTEMP_SENSOR_FAIL........................................................................................................................................... 548
10.2.158 ISIS_LSP_SEQ_EXCEED............................................................................................................................................ 549
10.2.159 ISIS_SEQ_REACH_MAX........................................................................................................................................... 551
10.2.160 ISISADJACENCYCHANGE....................................................................................................................................... 552
10.2.161 J0_MM......................................................................................................................................................................... 554
10.2.162 K1_K2_M..................................................................................................................................................................... 554
10.2.163 K2_M............................................................................................................................................................................ 556
10.2.164 KMC_KEY_SYNC_FAIL..............................................................................................................................................558
10.2.165 L3V_TRAP_THRE_EXCEED..................................................................................................................................... 559
10.2.166 L3V_TRAP_VRF_DOWN.......................................................................................................................................... 560
10.2.167 LAG_BWMM.............................................................................................................................................................. 561
10.2.168 LAG_DOWN............................................................................................................................................................... 562
10.2.169 LAG_MEMBER_DOWN........................................................................................................................................... 563
10.2.170 LAG_PORT_FAIL........................................................................................................................................................ 565
10.2.171 LAG_VC_PORT_FAIL.................................................................................................................................................567
10.2.172 LAN_LOC..................................................................................................................................................................... 569
10.2.173 LASER_CHECK_ERR.................................................................................................................................................. 571
10.2.174 LASER_CLOSED......................................................................................................................................................... 572
10.2.175 LASER_MOD_ERR..................................................................................................................................................... 572
10.2.176 LASER_MOD_ERR_EX.............................................................................................................................................. 574
10.2.177 LASER_MODULE_MISMATCH.............................................................................................................................. 575
10.2.178 LASER_SHUT.............................................................................................................................................................. 577
10.2.179 LCAS_FOPR................................................................................................................................................................. 577
10.2.180 LCAS_FOPT................................................................................................................................................................. 579
10.2.181 LCAS_PLCR.................................................................................................................................................................. 581
10.2.182 LCAS_PLCT.................................................................................................................................................................. 582
10.2.183 LCAS_TLCR.................................................................................................................................................................. 584
10.2.184 LCAS_TLCT.................................................................................................................................................................. 585
10.2.185 LCD................................................................................................................................................................................587
10.2.186 LCS_DAYS_OF_GRACE............................................................................................................................................ 589
10.2.187 LCS_EXPIRED.............................................................................................................................................................. 590
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. x

10.2.188 LCS_FILE_NOT_EXIST.............................................................................................................................................. 591

10.2.189 LCS_LIMITED.............................................................................................................................................................. 592
10.2.190 LFA................................................................................................................................................................................ 595
10.2.191 LINK_ERR.................................................................................................................................................................... 597
10.2.192 LMFA............................................................................................................................................................................ 598
10.2.193 LOCAL_FAULT............................................................................................................................................................ 600
10.2.194 LOOP_ALM................................................................................................................................................................. 601
10.2.195 LP_CROSSTR.............................................................................................................................................................. 604
10.2.196 LP_R_FIFO................................................................................................................................................................... 605
10.2.197 LP_RDI.......................................................................................................................................................................... 606
10.2.198 LP_RDI_VC12............................................................................................................................................................. 607
10.2.199 LP_RDI_VC3................................................................................................................................................................ 608
10.2.200 LP_REI.......................................................................................................................................................................... 609
10.2.201 LP_REI_VC12.............................................................................................................................................................. 610
10.2.202 LP_REI_VC3................................................................................................................................................................. 611
10.2.203 LP_RFI...........................................................................................................................................................................612
10.2.204 LP_SLM........................................................................................................................................................................ 613
10.2.205 LP_SLM_VC12............................................................................................................................................................ 614
10.2.206 LP_SLM_VC3.............................................................................................................................................................. 615
10.2.207 LP_T_FIFO................................................................................................................................................................... 616
10.2.208 LP_TIM......................................................................................................................................................................... 617
10.2.209 LP_TIM_VC12............................................................................................................................................................. 618
10.2.210 LP_TIM_VC3............................................................................................................................................................... 619
10.2.211 LP_UNEQ.....................................................................................................................................................................620
10.2.212 LP_UNEQ_VC12........................................................................................................................................................ 621
10.2.213 LP_UNEQ_VC3........................................................................................................................................................... 622
10.2.214 LPS_UNI_BI_M........................................................................................................................................................... 624
10.2.215 LPT_AUTH_FAIL........................................................................................................................................................ 625
10.2.216 LPT_CFG_CLOSEPORT.............................................................................................................................................626
10.2.217 LPT_INEFFECT........................................................................................................................................................... 627
10.2.218 LPT_RFI........................................................................................................................................................................ 628
10.2.219 LSR_BCM_ALM.......................................................................................................................................................... 630
10.2.220 LSR_NO_FITED.......................................................................................................................................................... 631
10.2.221 LSR_WILL_DIE............................................................................................................................................................632
10.2.222 LTI.................................................................................................................................................................................. 633
10.2.223 MAC_EXT_EXC........................................................................................................................................................... 635
10.2.224 MAC_FCS_EXC........................................................................................................................................................... 636
10.2.225 MAC_FCS_SD............................................................................................................................................................. 637
10.2.226 MOD_COM_FAIL...................................................................................................................................................... 638
10.2.227 MOD_TYPE_MISMATCH........................................................................................................................................ 640
10.2.228 MP_DELAY.................................................................................................................................................................. 641
10.2.229 MP_DOWN................................................................................................................................................................. 642
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xi

10.2.230 MPLSLDPSESSIONDOWN..................................................................................................................................... 644

10.2.231 MPLSLSP_TBL_LACK................................................................................................................................................ 645
10.2.232 MPLS_PW_AIS........................................................................................................................................................... 647
10.2.233 MPLS_PW_CSF.......................................................................................................................................................... 648
10.2.234 MPLS_PW_BDI........................................................................................................................................................... 649
10.2.235 MPLS_PW_Excess..................................................................................................................................................... 650
10.2.236 MPLS_PW_LCK.......................................................................................................................................................... 651
10.2.237 MPLS_PW_LOCK....................................................................................................................................................... 651
10.2.238 MPLS_PW_LOCV....................................................................................................................................................... 652
10.2.239 MPLS_PW_MISMATCH........................................................................................................................................... 654
10.2.240 MPLS_PW_MISMERGE............................................................................................................................................655
10.2.241 MPLS_PW_OAMFAIL............................................................................................................................................... 657
10.2.242 MPLS_PW_RDI........................................................................................................................................................... 658
10.2.243 MPLS_PW_SD............................................................................................................................................................ 659
10.2.244 MPLS_PW_SF............................................................................................................................................................. 660
10.2.245 MPLS_PW_UNEXPMEG...........................................................................................................................................661
10.2.246 MPLS_PW_UNEXPMEP........................................................................................................................................... 662
10.2.247 MPLS_PW_UNEXPPER............................................................................................................................................ 663
10.2.248 MPLS_PW_UNKNOWN.......................................................................................................................................... 664
10.2.249 MPLS_TUNNEL_AIS................................................................................................................................................. 664
10.2.250 MPLS_TUNNEL_BDI.................................................................................................................................................665
10.2.251 MPLS_TUNNEL_EXCESS......................................................................................................................................... 666
10.2.252 MPLS_TUNNEL_FDI................................................................................................................................................. 667
10.2.253 MPLS_TUNNEL_LOCV............................................................................................................................................. 668
10.2.254 MPLS_TUNNEL_LOCK............................................................................................................................................. 670
10.2.255 MPLS_TUNNEL_MISMATCH................................................................................................................................. 671
10.2.256 MPLS_TUNNEL_MISMERGE................................................................................................................................. 672
10.2.257 MPLS_TUNNEL_OAMFAIL..................................................................................................................................... 673
10.2.258 MPLS_TUNNEL_RDI.................................................................................................................................................674
10.2.259 MPLS_TUNNEL_SD.................................................................................................................................................. 675
10.2.260 MPLS_TUNNEL_SF................................................................................................................................................... 676
10.2.261 MPLS_TUNNEL_UNEXPMEG................................................................................................................................ 677
10.2.262 MPLS_TUNNEL_UNEXPMEP................................................................................................................................. 678
10.2.263 MPLS_TUNNEL_UNEXPPER.................................................................................................................................. 679
10.2.264 MPLS_TUNNEL_UNKNOWN................................................................................................................................ 680
10.2.265 MS_AIS......................................................................................................................................................................... 681
10.2.266 MS_CROSSTR............................................................................................................................................................. 682
10.2.267 MS_RDI........................................................................................................................................................................ 684
10.2.268 MS_REI......................................................................................................................................................................... 685
10.2.269 MSAD_CROSSTR....................................................................................................................................................... 686
10.2.270 MULTI_RPL_OWNER............................................................................................................................................... 687
10.2.271 MW_AM_TEST........................................................................................................................................................... 688
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xii

10.2.272 MW_BER_EXC............................................................................................................................................................ 689

10.2.273 MW_BER_SD.............................................................................................................................................................. 693
10.2.274 MW_CFG_MISMATCH.............................................................................................................................................697
10.2.275 MW_CONT_WAVE................................................................................................................................................... 701
10.2.276 MW_E1_LOST............................................................................................................................................................ 702
10.2.277 MW_FEC_UNCOR..................................................................................................................................................... 702
10.2.278 MW_LIM...................................................................................................................................................................... 707
10.2.279 MW_LINK_INTERFERENCE.................................................................................................................................... 709
10.2.280 MW_LOF..................................................................................................................................................................... 710
10.2.281 MW_RDI...................................................................................................................................................................... 716
10.2.282 NEIP_CONFUSION................................................................................................................................................... 717
10.2.283 NE_DCN_MODE........................................................................................................................................................ 719
10.2.284 NESF_LOST................................................................................................................................................................. 720
10.2.285 NESOFT_MM............................................................................................................................................................. 722
10.2.286 NO_BD_SOFT............................................................................................................................................................ 724
10.2.287 NP1_MANUAL_STOP.............................................................................................................................................. 725
10.2.288 NP1_SW_FAIL............................................................................................................................................................ 726
10.2.289 NP1_SW_INDI............................................................................................................................................................ 727
10.2.290 NTP_SYNC_FAIL........................................................................................................................................................ 728
10.2.291 OCD.............................................................................................................................................................................. 729
10.2.292 ODC_BATTERY_CURRENT_ABN.......................................................................................................................... 730
10.2.293 ODC_BATTERY_PWRDOWN................................................................................................................................. 732
10.2.294 ODC_DOOR_OPEN.................................................................................................................................................. 734
10.2.295 ODC_FAN_FAILED.................................................................................................................................................... 736
10.2.296 ODC_HUMI_ABN...................................................................................................................................................... 737
10.2.297 ODC_LOAD_PWRDOWN....................................................................................................................................... 739
10.2.298 ODC_MDL_ABN........................................................................................................................................................ 742
10.2.299 ODC_POWER_FAIL................................................................................................................................................... 743
10.2.300 ODC_SMOKE_OVER................................................................................................................................................ 746
10.2.301 ODC_SURGE_PROTECTION_FAIL........................................................................................................................ 747
10.2.302 ODC_TEC_ALM.......................................................................................................................................................... 749
10.2.303 ODC_TEMP_ABN...................................................................................................................................................... 750
10.2.304 ODC_WATER_ALM................................................................................................................................................... 752
10.2.305 OSPFNBRSTATECHANGE....................................................................................................................................... 754
10.2.306 OUT_PWR_ABN........................................................................................................................................................ 756
10.2.307 OUT_PWR_HIGH...................................................................................................................................................... 757
10.2.308 OUT_PWR_LOW....................................................................................................................................................... 758
10.2.309 OUT1TEMP_SENSOR_FAIL.................................................................................................................................... 759
10.2.310 OUT2TEMP_SENSOR_FAIL.................................................................................................................................... 760
10.2.311 PASSWORD_NEED_CHANGE................................................................................................................................762
10.2.312 PATCH_BD_EXCLUDE.............................................................................................................................................. 762
10.2.313 PATCH_BD_MATCH_FAIL....................................................................................................................................... 763
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xiii

10.2.314 PATCH_CHGSCC_NOTMATCH............................................................................................................................. 764

10.2.315 PATCH_OP_TIMEOUT............................................................................................................................................. 765
10.2.316 PATCH_INIT_FAIL..................................................................................................................................................... 766
10.2.317 PATCH_PKGERR........................................................................................................................................................ 767
10.2.318 PATCH_MATCH_NO_START.................................................................................................................................. 768
10.2.319 PING_LOS....................................................................................................................................................................770
10.2.320 PING_ARP_MISMATCH........................................................................................................................................... 771
10.2.321 PG_LINK_FAIL............................................................................................................................................................ 772
10.2.322 PG_PRT_DEGRADED................................................................................................................................................ 773
10.2.323 PLA_CFG_MISMATCH............................................................................................................................................. 774
10.2.324 PLA_DOWN................................................................................................................................................................ 779
10.2.325 PLA_MEMBER_DOWN_EXT.................................................................................................................................. 780
10.2.326 PLA_PKT_ERR............................................................................................................................................................. 784
10.2.327 PORTMODE_MISMATCH....................................................................................................................................... 785
10.2.328 PORT_EXC_TRAFFIC.................................................................................................................................................786
10.2.329 PORT_MODULE_OFFLINE..................................................................................................................................... 787
10.2.330 POWER_ABNORMAL.............................................................................................................................................. 789
10.2.331 POWER_ALM............................................................................................................................................................. 790
10.2.332 PRO_PKT_FLOODING............................................................................................................................................. 792
10.2.333 PPP_LCP_FAIL.............................................................................................................................................................794
10.2.334 PPP_NCP_FAIL........................................................................................................................................................... 795
10.2.335 PTP_SOURCE_SWITCH........................................................................................................................................... 796
10.2.336 PTP_TIME_ADJUST_OFF......................................................................................................................................... 797
10.2.337 PTP_TIMESTAMP_ABN........................................................................................................................................... 798
10.2.338 PW_APS_DEGRADED.............................................................................................................................................. 800
10.2.339 PW_APS_OUTAGE.................................................................................................................................................... 800
10.2.340 PW_DOWN................................................................................................................................................................. 801
10.2.341 PW_DROPPKT_EXC.................................................................................................................................................. 802
10.2.342 PW_NO_TRAFFIC......................................................................................................................................................803
10.2.343 PWAPS_LOST............................................................................................................................................................. 805
10.2.344 PWAPS_PATH_MISMATCH.................................................................................................................................... 806
10.2.345 PWAPS_SWITCH_FAIL............................................................................................................................................. 807
10.2.346 PWAPS_TYPE_MISMATCH..................................................................................................................................... 808
10.2.347 PWD_ENCRYPT_RISK.............................................................................................................................................. 809
10.2.348 R_LOC........................................................................................................................................................................... 809
10.2.349 R_LOF........................................................................................................................................................................... 811
10.2.350 R_LOS........................................................................................................................................................................... 813
10.2.351 R_OOF.......................................................................................................................................................................... 815
10.2.352 RADIO_FADING_MARGIN_INSUFF.....................................................................................................................817
10.2.353 RADIO_MUTE............................................................................................................................................................ 819
10.2.354 RADIO_RSL_BEYONDTH........................................................................................................................................ 820
10.2.355 RADIO_RSL_HIGH.................................................................................................................................................... 821
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xiv

10.2.356 RADIO_RSL_LOW..................................................................................................................................................... 822

10.2.357 RADIO_TSL_HIGH.................................................................................................................................................... 824
10.2.358 RADIO_TSL_LOW......................................................................................................................................................824
10.2.359 RELAY_ALARM_CRITICAL...................................................................................................................................... 825
10.2.360 RELAY_ALARM_IGNORE........................................................................................................................................ 826
10.2.361 RELAY_ALARM_MAJOR.......................................................................................................................................... 827
10.2.362 RELAY_ALARM_MINOR.......................................................................................................................................... 827
10.2.363 REMOTE_FAULT........................................................................................................................................................ 828
10.2.364 RMFA............................................................................................................................................................................ 829
10.2.365 RPS_INDI..................................................................................................................................................................... 830
10.2.366 RS_CROSSTR.............................................................................................................................................................. 832
10.2.367 RTC_FAIL..................................................................................................................................................................... 834
10.2.368 RT_TBL_LACK............................................................................................................................................................. 834
10.2.369 S1_SYN_CHANGE..................................................................................................................................................... 835
10.2.370 SYNC_FAIL.................................................................................................................................................................. 837
10.2.371 SEC_RADIUS_FAIL.....................................................................................................................................................838
10.2.372 SECU_ALM.................................................................................................................................................................. 840
10.2.373 SLAVE_BAD................................................................................................................................................................ 841
10.2.374 SOFTWARE_UNCOMMIT....................................................................................................................................... 844
10.2.375 SRV_LOOP_LD........................................................................................................................................................... 845
10.2.376 SRV_SHUTDOWN_LD............................................................................................................................................. 847
10.2.377 SSL_CERT_DAMAGED............................................................................................................................................. 848
10.2.378 SSL_CERT_NOENC................................................................................................................................................... 849
10.2.379 SSL_CERT_TO_EXPIRE............................................................................................................................................. 850
10.2.380 STORAGE_FAIL.......................................................................................................................................................... 851
10.2.381 STORM_CUR_QUENUM_OVER............................................................................................................................853
10.2.382 SUBNET_RT_CONFLICT.......................................................................................................................................... 853
10.2.383 SWDL_ACTIVATED_TIMEOUT.............................................................................................................................. 855
10.2.384 SWDL_AUTOMATCH_INH..................................................................................................................................... 856
10.2.385 SWDL_BD_MATCH_FAIL........................................................................................................................................ 857
10.2.386 SWDL_CHGMNG_NOMATCH.............................................................................................................................. 858
10.2.387 SWDL_COMMIT_FAIL............................................................................................................................................. 859
10.2.388 SWDL_INPROCESS................................................................................................................................................... 860
10.2.389 SWDL_NEPKGCHECK.............................................................................................................................................. 861
10.2.390 SWDL_PKG_NOBDSOFT........................................................................................................................................ 862
10.2.391 SWDL_PKGVER_MM................................................................................................................................................862
10.2.392 SWDL_ROLLBACK_FAIL.......................................................................................................................................... 863
10.2.393 SYN_BAD..................................................................................................................................................................... 864
10.2.394 SYNC_C_LOS.............................................................................................................................................................. 866
10.2.395 SYNC_DISABLE.......................................................................................................................................................... 867
10.2.396 SYSLOG_COMM_FAIL............................................................................................................................................. 868
10.2.397 T_ALOS........................................................................................................................................................................ 869
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xv

10.2.398 T_LOC........................................................................................................................................................................... 870

10.2.399 TEM_HA...................................................................................................................................................................... 871
10.2.400 TEM_LA........................................................................................................................................................................872
10.2.401 TEMP_ALARM............................................................................................................................................................873
10.2.402 TEMP_OVER............................................................................................................................................................... 874
10.2.403 TF................................................................................................................................................................................... 876
10.2.404 THUNDERALM.......................................................................................................................................................... 876
10.2.405 TIME_LOCK_FAIL...................................................................................................................................................... 878
10.2.406 TIME_NO_TRACE_MODE....................................................................................................................................... 879
10.2.407 TR_LOC........................................................................................................................................................................ 880
10.2.408 TU_AIS......................................................................................................................................................................... 882
10.2.409 TU_AIS_VC12............................................................................................................................................................. 884
10.2.410 TU_AIS_VC3................................................................................................................................................................885
10.2.411 TU_LOP........................................................................................................................................................................ 887
10.2.412 TU_LOP_VC12............................................................................................................................................................ 888
10.2.413 TU_LOP_VC3.............................................................................................................................................................. 890
10.2.414 TUNNEL_APS_DEGRADED.................................................................................................................................... 892
10.2.415 TUNNEL_APS_OUTAGE.......................................................................................................................................... 893
10.2.416 UHCS............................................................................................................................................................................ 894
10.2.417 UNIPTP_SRC_LOSS...................................................................................................................................................895
10.2.418 UNIPTP_SRC_SWITCH............................................................................................................................................. 896
10.2.419 UNIPTP_SRC_NEGO_FAIL...................................................................................................................................... 898
10.2.420 UP_E1_AIS...................................................................................................................................................................899
10.2.421 USB_FILE_UNSEC......................................................................................................................................................900
10.2.422 USB_PROCESS_FAIL................................................................................................................................................. 901
10.2.423 V5_VCAIS.................................................................................................................................................................... 903
10.2.424 VC_AIS.......................................................................................................................................................................... 903
10.2.425 VC_LOC........................................................................................................................................................................ 905
10.2.426 VC_RDI......................................................................................................................................................................... 907
10.2.427 VCAT_LOA.................................................................................................................................................................. 909
10.2.428 VCAT_LOM_VC12..................................................................................................................................................... 910
10.2.429 VCAT_LOM_VC3....................................................................................................................................................... 911
10.2.430 VCAT_SQM_VC12..................................................................................................................................................... 913
10.2.431 VCAT_SQM_VC3....................................................................................................................................................... 914
10.2.432 VOLT_LOS................................................................................................................................................................... 916
10.2.433 VP_AIS.......................................................................................................................................................................... 917
10.2.434 VP_LOC........................................................................................................................................................................ 919
10.2.435 VP_RDI......................................................................................................................................................................... 921
10.2.436 W_R_FAIL.................................................................................................................................................................... 923
10.2.437 WRG_BD_TYPE.......................................................................................................................................................... 924
10.2.438 XPIC_LOS..................................................................................................................................................................... 925
11 Performance Event Reference........................................................................................ 927
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xvi

11.1 Performance Events (by Event Type)........................................................................................................................ 927

11.1.1 SDH/PDH Performance Event List.......................................................................................................................... 927
11.1.2 Radio Performance Events.........................................................................................................................................931
11.1.3 MPLS PW Performance Events................................................................................................................................. 934
11.1.4 Other Performance Events........................................................................................................................................ 935
11.2 Performance Events and Handling Procedures......................................................................................................938
11.2.1 ATPC_P_ADJUST and ATPC_N_ADJUST................................................................................................................. 938
11.2.2 AMDOWNCNT and AMUPCNT................................................................................................................................ 939
11.2.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW........................................................................................................... 940
11.2.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR................................................................................................. 941
11.2.5 CPUUSAGEMAX, CPUUSAGEMIN, CPUUSAGECUR, and CPUUSAGEAVG................................................. 941
11.2.6 CURPOSITIVEPDV and CURNEGATIVEPDV.......................................................................................................... 942
11.2.7 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and E1_LSES_SDH.................................................................. 942
11.2.8 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS...................................................................................................944
11.2.9 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and FEC_UNCOR_BLOCK_CNT................................................... 945
11.2.10 HPBBE, HPES, HPSES, HPCSES, and HPUAS......................................................................................................946
11.2.11 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS.............................................................................. 947
11.2.12 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS.......................................................................................................948
11.2.13 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG.................................................................................................. 950
11.2.14 IF_MSE_MAX, IF_MSE_MIN, IF_MSE_AVG, and IF_MSE_CUR......................................................................950
11.2.15 LSBIASMAX, LSBIASMIN, and LSBIASCUR......................................................................................................... 951
11.2.16 LSIOPMAX, LSIOPMIN, and LSIOPCUR............................................................................................................... 952
11.2.17 LSOOPMAX, LSOOPMIN, and LSOOPCUR....................................................................................................... 952
11.2.18 LSTMPMAX, LSTMPMIN, and LSTMPCUR......................................................................................................... 953
11.2.19 LPBBE, LPES, LPSES, LPCSES, and LPUAS........................................................................................................... 953
11.2.20 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS....................................................................................955
11.2.21 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV.......................................................................................... 956
11.2.22 MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY..................................... 956
11.2.23 MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET.............................................................. 957
11.2.24 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and AVGPOSITIVEDELAY.....................................................958
11.2.25 MAXNEGATIVEDELAY, MINNEGATIVEDELAY, and AVGNEGATIVEDELAY...............................................958
11.2.26 MEMUSAGEAVG, MEMUSAGECUR, MEMUSAGEMAX, and MEMUSAGEMIN...................................... 959
11.2.27 MIMO_CAPACITY_CUR, MIMO_CAPACITY_MIN, MIMO_CAPACITY_MAX, MIMO_CAPACITY_AVG
......................................................................................................................................................................................................... 960
11.2.28 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and MPLS_PW_UAS...................................................... 960
11.2.29 MPLS_PW_LS_N, MPLS_PW_SLS_N, MPLS_PW_CSLS_N, and MPLS_PW_UAS_N.................................961
11.2.30 MSBBE, MSES, MSSES, MSCSES, and MSUAS...................................................................................................962
11.2.31 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS........................................................................... 963
11.2.32 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR...........................................................................................964
11.2.33 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and PG_IF_UAS................................................................. 965
11.2.34 RPLMAX, RPLMIN, and RPLCUR............................................................................................................................ 966
11.2.35 RSBBE, RSES, RSSES, RSCSES, and RSUAS......................................................................................................... 967
11.2.36 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG.................................................................................................. 968
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xvii

11.2.37 RSOOF and RSOFS..................................................................................................................................................... 969

11.2.38 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16, QAMWS32, QAMWS64, QAMWS128,
QAMWS256, QAMWS512, QAM_L_WS512, QAMWS1024, QAM_L_WS1024, QAM_L_WS2048,
QAMWS2048, QAMWS4096, QAMWS8192..................................................................................................................... 970
11.2.39 TLBMAX, TLBMIN, and TLBCUR............................................................................................................................ 971
11.2.40 RLHTT, RLLTT, TLHTT, TLLTT................................................................................................................................... 972
11.2.41 TPLMAX, TPLMIN, and TPLCUR............................................................................................................................ 973
11.2.42 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG...................................................................................................973
11.2.43 TUPJCHIGH, TUPJCLOW, and TUPJCNEW..........................................................................................................974
11.2.44 TX_BWUTIL_EXCS,RX_BWUTIL_EXCS, TX_BWUTIL_EXCS_MIN, RX_BWUTIL_EXCS_MIN,
TX_BWUTIL_EXCS_MID, RX_BWUTIL_EXCS_MID, TX_BWUTIL_EXCS_MAX, and RX_BWUTIL_EXCS_MAX...975
11.2.45 XPD_MAX, XPD_MIN and XPIC_XPD_VALUE..................................................................................................... 976
12 RMON Event Reference................................................................................................... 978

12.1 RMON Performance Entries List on the Packet-Plane........................................................................................ 978
12.1.1 EM6F/EM6T/EM6FA/EM6TA..................................................................................................................................... 978
12.1.2 EG2D............................................................................................................................................................................... 1007
12.1.3 EX1...................................................................................................................................................................................1035
12.1.4 EG4/EG4P...................................................................................................................................................................... 1064
12.1.5 IFU2/IFX2.......................................................................................................................................................................1098
12.1.6 ISU2/ISX2/ISV3/ISM6................................................................................................................................................ 1124
12.1.7 ISM8................................................................................................................................................................................ 1156
12.1.8 ML1/MD1...................................................................................................................................................................... 1189
12.1.9 CQ1................................................................................................................................................................................. 1206
12.1.10 CSHN............................................................................................................................................................................ 1213
12.1.11 CSHNA......................................................................................................................................................................... 1240
12.1.12 CSHNU......................................................................................................................................................................... 1294
12.1.13 EM6............................................................................................................................................................................... 1354
12.1.14 EFP8/EMS6................................................................................................................................................................. 1387
12.2 RMON Performance Entries List on the EoS/EoPDH-Plane............................................................................ 1391
12.2.1 EFP8................................................................................................................................................................................ 1391
12.2.2 EMS6............................................................................................................................................................................... 1399
12.3 RMON Events and Handling Procedures............................................................................................................... 1407
12.3.1 ETHDROP...................................................................................................................................................................... 1408
12.3.2 ETHEXCCOL.................................................................................................................................................................. 1409
12.3.3 ETHLATECOL................................................................................................................................................................ 1410
12.3.4 RXBBAD......................................................................................................................................................................... 1411
12.3.5 TXDEFFRM.................................................................................................................................................................... 1412
12.3.6 ETHUNDER................................................................................................................................................................... 1413
12.3.7 ETHOVER.......................................................................................................................................................................1413
12.3.8 ETHFRG.......................................................................................................................................................................... 1414
12.3.9 ETHJAB........................................................................................................................................................................... 1415
12.3.10 ETHCOL....................................................................................................................................................................... 1416
12.3.11 ETHFCS........................................................................................................................................................................ 1417
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xviii

12.3.12 ATMPW_LOSPKTS.................................................................................................................................................... 1418

12.3.13 ATMPW_MISORDERPKTS...................................................................................................................................... 1419
12.3.14 ATMPW_UNKNOWNCELLS.................................................................................................................................. 1419
12.3.15 ATM_CORRECTED_HCSERR.................................................................................................................................. 1420
12.3.16 ATM_UNCORRECTED_HCSERR........................................................................................................................... 1421
12.3.17 CES_MISORDERPKTS.............................................................................................................................................. 1422
12.3.18 CES_STRAYPKTS........................................................................................................................................................1422
12.3.19 CES_MALPKTS........................................................................................................................................................... 1423
12.3.20 CES_JTRUDR...............................................................................................................................................................1424
12.3.21 CES_JTROVR............................................................................................................................................................... 1424
12.3.22 CES_LOSPKTS............................................................................................................................................................ 1425
13 Alarm Management....................................................................................................... 1427

13.1 NE Alarm Management.............................................................................................................................................. 1427
13.2 Board Alarm Management.........................................................................................................................................1427
13.2.1 Setting the Alarm Severity...................................................................................................................................... 1427
13.2.2 Alarm Suppression..................................................................................................................................................... 1428
13.2.3 Alarm Auto-Report.................................................................................................................................................... 1428
13.2.4 Alarm Reversion..........................................................................................................................................................1428
13.2.5 Setting Alarm Thresholds........................................................................................................................................ 1429
13.2.6 AIS Insertion................................................................................................................................................................. 1456
13.2.7 UNEQ Insertion........................................................................................................................................................... 1457
14 Performance Event Management............................................................................... 1458

14.1 NE Performance Event Management..................................................................................................................... 1458
14.2 Board Performance Event Management............................................................................................................... 1458
15 Alarm Suppression Relationship................................................................................. 1460

15.1 Alarm Suppression on TDM Plane........................................................................................................................... 1460
15.2 Alarm Suppression on the Data Plane................................................................................................................... 1466
16 Indicators of Boards....................................................................................................... 1472
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xix

Maintenance Guide 1 About This Document
1 About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX RTN 980 V100R019C10
NCE V100R019C00
Since V100R019C00, the OptiX RTN 980 no longer supports EFP8, EMS6, CSHN, EM6TA,
EM6FA, EM6T and EM6F boards.
Intended Audience
This document provides the guidelines to maintaining OptiX RTN 980. It also
describes the alarms and performance events that are required for troubleshooting
during the maintenance.
This document is intended for:
● Network planning engineer

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

avoided, will result in death or serious injury.
Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. 1

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

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

avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Supplements the important information in the main text.

NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
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.
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 B01 (2019-12-31) Based on Product Version V100R019C10

This document is the first beta issue for the V100R019C10 product version.

Maintenance Guide 2 Safety Precautions
2 Safety Precautions
This topic describes the safety precautions that you must follow when installing,
operating, and maintaining Huawei devices.
2.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.
2.2 Warning and Safety Symbols
Before using the equipment, note the following warning and safety symbols on
the equipment.
2.3 Electrical Safety
This topic describes safety precautions for high voltage, lightning strikes, high
leakage current, power cables, fuses, and ESD.
2.4 Environment of Flammable Gas
This topic describes safety precautions for the operating environment of a device.
2.5 Storage Batteries
This topic describes safety precautions for operations of storage batteries.
2.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
2.7 Working at Heights
This topic describes safety precautions for working at heights.
2.8 Mechanical Safety
This topic describes safety precautions for drilling holes, handling sharp objects,
operating fans, and carrying heavy objects.
2.9 Other Precautions
This topic describes safety precautions for removing and inserting boards, binding
signal cables, and routing cables.

2.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.
● Only trained and qualified personnel are permitted to install, operate, and
maintain a device.
● Only certified professionals are permitted to remove the safety facilities, and
to troubleshoot and maintain the device.
● Only the personnel authenticated or authorized by Huawei are permitted to
replace or change the device or parts of the device (including software).
● 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.
● When installing the device, always connect the grounding facilities first. When
removing the device, always disconnect the grounding facilities last.
● Ensure that the grounding conductor is intact.
● Do not operate the device in the absence of a suitably installed grounding
conductor.
● 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
● When there is a risk of a lightning strike, do not operate the fixed terminal or
touch the cables.
● 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.
The preceding requirements apply to wireless fixed station terminals.

● To avoid electric shocks, do not connect safety extra-low voltage (SELV)
circuits to telephone-network voltage (TNV) circuits.
● Do not look into optical ports without eye protection. Otherwise, human eyes
may be hurt by laser beams.
● 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.
● 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
● Before any operation, install the device firmly on the ground or other rigid
objects, such as on a wall or in a rack.
● When the system is working, ensure that the ventilation hole is not blocked.
● When installing the front panel, use a tool to tighten the screws firmly, if
required.
● After installing the device, clean up the packing materials.
2.2 Warning and Safety Symbols

Before using the equipment, note the following warning and safety symbols on
the equipment.
Table 2-1 lists the warning and safety symbols of the OptiX RTN 980 and their
meanings.
Table 2-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.

Symbol Indication
This symbol is for the laser class.

A notice with this symbol indicates the class of the
laser. Avoid direct exposure to the laser beams.
Otherwise, it may damage you eyes or skin.
A notice with this symbol indicates where the

subrack is grounded.
A notice with this symbol indicates that the air

filter should be cleaned periodically.
This symbol is for fan safety.

A notice with this symbol indicates that the fan
leaves should not be touched when the fan is
rotating.
2.3 Electrical Safety

This topic describes safety precautions for high voltage, lightning strikes, high
leakage current, power cables, fuses, and ESD.
High Voltage
● 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.
● 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.
Do not perform operations on high voltage, AC power, towers, or backstays in

stormy weather conditions.
High Leakage Current
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
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.
● Before installing or removing power cables, you must power off the device.
● Before connecting a power cable, you must ensure that the label on the
power cable is correct.
Device with Power On
Installing or removing a device is prohibited if the device is on.
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
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).
● 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.
● 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 2-1 shows the method of wearing an ESD wrist strap.

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

This topic describes safety precautions for the operating environment of a device.
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.
2.5 Storage Batteries

This topic describes safety precautions for operations of storage batteries.
Before operating a storage battery, you must read the safety precautions carefully
and be familiar with the method of connecting a storage battery.
● Incorrect operations of storage batteries cause hazards. During operation,

prevent any short-circuit, and prevent the electrolyte from overflowing or
leakage.
● 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.

● 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:
● Use special insulation tools.
● Wear an eye protector and take effective protection measures.
● Wear rubber gloves and a protection coat to prevent the hazard caused by
the overflowing electrolyte.
● When handling the storage battery, ensure that its electrodes are upward.
Leaning or reversing the storage battery is prohibited.
● 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
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:
● Sodium bicarbonate (NaHCO3)
● 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.
2.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
2.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.
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:
● 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.
● Non-woven lens tissue
● Special compressed gas
● Cotton stick (medical cotton or long fiber cotton)
● Special cleaning roll, used with the recommended cleaning solvent
● 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

● Use an attenuator if the optical power is excessively high. A high received
optical power damages the optical interface.
● Directly connect an attenuator to a slanting optical interface. Install the
attenuator on the IN port instead of the OUT port.
● 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 2-2 shows a slanting optical interface, and Figure 2-3 shows a level optical
interface.

Figure 2-2 Slanting optical interface
Figure 2-3 Level optical interface
2.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.
2.6.3 Forbidden Areas

The topic describes requirements for a forbidden area.
● 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.
● A physical barrier and an eye-catching warning flag should be available in
each forbidden area.
2.6.4 Laser
This topic describes safety precautions for lasers.
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:
● All operations should be performed by authorized personnel who have

completed the required training courses.
● Wear a pair of eye-protective glasses when you are handling lasers or fibers.
● Ensure that the optical source is switched off before disconnecting optical
fiber connectors.
● 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.

● Use an optical power meter to measure the optical power and ensure that the
optical source is switched off.
● Before opening the front door of an optical transmission device, ensure that
you are not exposed to laser radiation.
● 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:
● Only trained personnel are permitted to cut and splice fibers.

● 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.
2.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.
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.
2.7 Working at Heights

This topic describes safety precautions for working at heights.
When working at heights, be cautious to prevent objects from falling down.
The requirements for working at heights are as follows:
● The personnel who work at heights must be trained.

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

2.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.
When heavy objects are being hoisted, do not walk below the cantilever or hoisted
objects.
● Only trained and qualified personnel can perform hoisting operations.

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

2.7.2 Using Ladders

This topic describes safety precautions for using ladders.
Checking Ladders
● Before using a ladder, check whether the ladder is damaged. After checking
that the ladder is in good condition, you can use the ladder.
● 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 2-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 2-5 Slanting a ladder
Climbing Up a Ladder
When climbing up a ladder, pay attention to the following points:
● Ensure that the center of gravity of your body does not deviate from the
edges of the two long sides.
● Before operations, ensure that your body is stable to reduce risks.
● 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 2-6.

Figure 2-6 Ladder top being one meter higher than the roof
2.8 Mechanical Safety

This topic describes safety precautions for drilling holes, handling sharp objects,
operating fans, and carrying heavy objects.
Drilling Holes
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.
● Before drilling a hole on the cabinet, remove the cables inside the cabinet.
● Wear an eye protector when drilling holes. This is to prevent eyes from being
injured by the splashing metal scraps.
● Wear protection gloves when drilling holes.
● Take measures to prevent the metallic scraps from falling into the cabinet.
After the drilling, clean up the metallic scraps.
Sharp Objects
Wear protection gloves when carrying the device. This is to prevent hands from
being injured by the sharp edges of the device.

Fans
● 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.
● 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.
● 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.
● 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.
● 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.
● 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.
2.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.
● Slide the board along the guide rails.

● Do not contact one board with another to avoid short-circuits or damage.
● 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:
● When installing cables, ensure that the environment temperature is above
0°C.
● 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.
● 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
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
Before installing or removing an IF cable, you must turn off the power switch of
the IF board.

Maintenance Guide 3 Notices for High-Risk Operations
3 Notices for High-Risk Operations
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.
3.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.
3.2 Operation Guide for the IF Jumper
Before installing or removing IF jumpers, shut down the ODU power supply to
prevent personal injuries and damage to the IF boards or ODU.
3.3 Operation Guide for the IF Cables
Before installing or removing IF cables, shut down the ODU power supply to
3.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.
3.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 switch is applied to the IF board to control the power supply to the
ODU, as shown in Figure 3-1.
ISM6 and ISM8 boards do not have any toggle lever switches.

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

3.2 Operation Guide for the IF Jumper

Before installing or removing IF jumpers, shut down the ODU power supply to
Precautions
NOTICE
● For an IF board with a power switch, do not disconnect/connect the IF jumper

with power on.
● For the IF boards without a power switch (ISM6 and ISM8), do not remove and
insert the IF jumper without loads. That is, ensure that the IF jumper is
connected to the IF cable and ODU.
● The IF1 port on the dual-channel ODU is used to supply power to the ODU.
● When the dual-channel IF board or IDU is connected to the dual-channel ODU,
only the IF1 port on the IF board/IDU can supply power to the ODU.
Procedure
Step 1 For an IF board with a power switch:
1. Follow instructions in 3.1 Operation Guide for the Toggle Lever Switch to
power off the ODU.

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/ISM8) 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
3.3 Operation Guide for the IF Cables

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

Precautions
NOTICE

with power on.
Procedure
1. Turn off the ODU power switch by referring to 3.1 Operation Guide for the
Toggle Lever Switch.
Do not remove the IF cable when the ODU/RFU power supply is not shut
down.
2. Install or remove the IF cables.

Step 2 For an IF board (ISM6/ISM8) without a power switch:

2. Install or remove the IF cable.
----End
3.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

with power on.
Procedure
1. Turn off the ODU power switch on the IF board by referring to 3.1 Operation
Guide for the Toggle Lever Switch.

Do not remove the IF cable when the ODU power supply is not shut down.
2. Disconnect the IF jumper or IF cable.

3. Remove or install the IF board.
Step 2 For an IF board without a power switch (ISM6/ISM8):
2. Disconnect the IF jumper/IF cable.
3. Remove or install the IF board.
----End

Maintenance Guide 4 Routine Maintenance
4 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.
Microwave equipment requires professional preventive maintenance inspection (PMI)

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

Maintenance Item Recomm Check Point
ended
Maintena
nce Cycle
Checking the NE Status Every day ● If the NE icon is green, the NE

operates properly.
● If the NE icon is gray, the NE is
unreachable due to DCN faults.
● If the NE icon is in other colors,
alarms are reported or
exceptions occur. You need to
troubleshoot in time.


ended
Maintena
nce Cycle
Browse Current Alarms Every day ● Handle the alarms by referring

to Alarms and Handling
Procedures.
● For port alarms related to the
interconnected equipment, see
Reversing Alarms for Service
Ports to reduce the number of
alarms and prevent interference
to emergent alarms.
Browsing Historical Alarms Every By finding causes of and solutions

week to historical alarms, you can take
precautions to avoid related faults.
Browsing UAT Events Every ● Security events are generally

week records of normal operations.
Investigate the illegal
operations if there are any.
● Abnormal events about
equipment have been properly
solved.
Browsing Current Every ● Gauge type performance events

Performance Events week such as the board temperature
and laser power are stable.
Browsing Historical Every
Performance Events week ● Bit error type performance
events meet requirements on
link availability.
Querying the Historical Every ● Historical received signal levels

Transmit Power and Receive week do not exceed the fade margin
Power for a long time.
● 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.


ended
Maintena
nce Cycle
Testing N+1 Protection Half a For equipment that is configured

Switching year with N+1 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.
You can use the performance management system (PMS) on the U2000NCE 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.

Item Specifications
Historical ● Sixteen 15-minute historical performance events

performance ● Six 24-hour historical performance events
events (excluding
NOTE
RMON For the following performance events, an NE can store thirty 24-
performance hour historical performance events and six hundred and seventy
events) two 15-minute historical performance events:
● IF_BBE, IF_ES, IF_SES, IF_UAS
● IF_SNR_AVG, IF_SNR_MAX, IF_SNR_MIN
● RSL_AVG, RSL_MAX, RSL_MIN
● TSL_AVG, TSL_MIN, TSL_MAX
● FEC_BEF_COR_ER, FEC_UNCOR_BLOCK_CNT
● MAXPHASEOFFSET
● MAXFREQDEV
● 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 ● Sixteen 30-second historical performance events

performance ● Ninety-six 30-minute historical performance events
events
● Forty 15-minute historical performance events
● 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

Maintenance Item Recommended Check Point
Maintenance Cycle
Checking the Every two months The site environment

telecommunications meets equipment
room 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
Perform a complete check appearance is in good
after a level-8 or higher- condition, without the
level hurricane, an coating being damaged
earthquake, or other
unexpected circumstances.
or corroded.
Checking the hybrid NOTICE The hybrid coupler is

In high-corrosion areas, fixed and secure, with
couplera
check whether outdoor
components and fasteners
intact appearance and
are loose due to corrosion. free from damage or
If yes, take rust- and corrosion to the paint.
corrosion-proof measures
Checking the antennaa or replace the corroded The antenna is tightly
components or fasteners. placed and does not
deviate from the
designed angle.
Checking the IF cable The exterior of the cable

and flexible waveguidea is 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 A radio link is not

condition blocked by any visible
object.
a:Surface corrosion may occur near the pollution source. If the coating is damaged, contact
the local Huawei office for maintenance. An area close to a pollution source refers to the
area that covers a radius within any of the following values:
● 3.7 km away from salty waters (such as an ocean and salty water).
● 3 km away from severe pollution sources (such as iron refinery works, and coal mines).
● 2 km away from intermediate pollution sources (such as chemical plants, rubber
processing works, and electroplating workshops).
● 1 km away from light pollution sources (such as food processing works, leather working
plants, and heating boilers).

Maintenance Guide 5 Network Monitoring
5 Network Monitoring
5.1 Checking the Board Status

You can learn about the board status in a visual manner by checking the slot
diagram.
5.2 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.
5.3 Microwave Link Performance Query
This section describes operations related to microwave link performance query.
5.4 Ethernet Performance Query
This section describes operations related to Ethernet performance query.
5.5 Ethernet Port Traffic Monitoring
This section describes operations related to Ethernet traffic monitoring on
Ethernet ports and microwave ports.
5.6 Long-term Network Performance Monitoring
The U2000NCE centrally monitors long-term performance of various Huawei
devices through the Performance Management System (PMS).
5.7 Report Query
This section describes operations related to report query. You can obtain network
information from reports.
5.8 Alarm and Performance Management Setting
This section describes operations related to alarm and performance management.
5.1 Checking the Board Status

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

Prerequisites
You must be an NM user with NE maintainer authority or higher.
Tools, Equipment, and Materials

NCE
Procedure
Step 1 Query board running status.
Complete the following step to query board running status from the WebLCT:
Click the Slot Layout tab in NE Explorer.
----End
5.2 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.
5.2.1 Browsing Current Alarms

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


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

Step 3 View alarm information.
Step 4 Contact troubleshooting personnel in a timely manner for alarm handling.

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

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 NCE, you can browse the network-wide alarms based on the alarm severity by
clicking the alarm indicators in the upper right corner.
● You can click (red) to browse the network-wide critical alarms.
● You can click (orange) to browse the network-wide major alarms.
● You can click (yellow) to browse the network-wide minor alarms.
● You can click (light-blue) to browse the network-wide warning

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

● Red: critical alarm

● Orange: major alarm
● Yellow: minor alarm
● Purple: warning
● Light blue: event
5.2.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.

NCE
Procedure
Step 1 Open the historical alarm window.

Step 3 View alarm information.

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
5.2.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
● 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.
● You must be an NM user with NE maintainer authority or higher.

NCE
Web LCT also supports this operation and the steps are the similar to those on the NCE.
Procedure
Step 1 Open the performance data window.

Step 2 View current performance data.
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
5.2.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
● 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.

NCE
Procedure
Step 1 Open the performance data window.
Step 2 View historical performance data.

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
The Web LCT does not support data source selection.
----End
5.2.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

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

Step 2 Query performance threshold-crossing records.
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
5.2.6 Browsing UAT Events

Learn about the severe abnormalities on the transmission line by browsing UAT
events.

Prerequisites
Tools, Instruments, and Materials

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

----End
5.3 Microwave Link Performance Query

This section describes operations related to microwave link performance query.
5.3.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
● You must be an NM user with NE operator authority or higher.
● The corresponding IF boards and the ODUs connected to the IF boards must
be added to the NE Panel.

NCE
Procedure
Step 1 Query historical receive power or transmit power information.

----End
5.3.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
● The IF boards and the ODUs to which the IF boards are connected have been
added in the NE Panel.

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

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

NCE
Procedure
Step 1 Navigate to the microwave link performance statistics window.
If the Microwave Link Performance Statistics option is not displayed in the Operations
menu on the right, click , on the right of the Operations menu and add the option from
the Maintenance menu.
Step 2 Browse current performance data of the microwave link.

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

NCE
Procedure
Step 1 Navigate to the microwave link performance statistics window.
If the Microwave Link Performance Statistics option is not displayed in the Operations
menu on the right, click , on the right of the Operations menu and add the option from
the Maintenance menu.
Step 2 Browse historical performance data of the microwave link.

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
5.4 Ethernet Performance Query

This section describes operations related to Ethernet performance query.
Context
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).
5.4.1 Browsing Current Ethernet Performance

After setting the RMON statistics group. you can browse real-time Ethernet
performance statistics.
Prerequisites
● The corresponding board must be added in the NE Panel.

NCE

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

Performa Browsed Navigation Path
nce Object
Object
Basic Ethernet Select the corresponding board from the Object Tree in
performa porta the NE Explorer. Choose Performance > RMON
nce/ Performance from the Function Tree.
Extended NOTE
performa a: Packet Ethernet ports include FE/GE ports, Integrated IP
nce microwave ports, PORT8 on the EMS6 board, and PORT10 on
the EFP8 board.
PLA PLA 1. In the NE Explorer, select the required NE from the

group group Object Tree and choose Configuration > Physical
performa Link Aggregation.
nce 2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the

group group Object Tree and choose Configuration > Link
performa Configuration.
nce 2. Select the desired XPIC group, right-click, and choose
1+1 1+1 1. In the NE Explorer, select the required NE from the

group group Object Tree and choose Configuration > IF 1+1
performa Protection.
nce 2. Select the desired 1+1 protection group, right-click,
and choose Browse Performance from the shortcut
menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the

tunnel Tunnel Object Tree and choose Configuration > MPLS
performa Management > Unicast Tunnel Management from
nce the Function Tree.
2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s),
menu.


nce Object
Object
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE

PW PWE3 Explorer. Choose Configuration > Ethernet Service
performa service Management > E-Line Service from the Function
nce Tree.
2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE

performa E-Line Explorer. Choose Configuration > Ethernet Service
nce service Management > E-Line Service from the Function
Tree.
2. Select one or more UNI-UNI E-Line services, right-
click the service(s), and choose Browse Performance
from the shortcut menu.
CES-PW CES 1. In the NE Explorer, select the NE from the Object Tree
performa service and choose Configuration > CES Service
nce Management from the Function Tree.
CES 2. Select one or more CES services, right-click the
performa service(s), and choose Browse Performance from the
nce shortcut menu.
ATM/IMA Smart E1 Select the corresponding board from the Object Tree in
(access port the NE Explorer. Choose Performance > RMON
side) Performance from the Function Tree.
performa
nce
ATM-PW ATM 1. In the NE Explorer, select the NE from the Object Tree
performa PWE3 and choose Configuration > ATM Service
nce service Management from the Function Tree.
ATM 2. Select one or more ATM PWE3 services, right-click
PWE3 the service(s), and choose Browse Performance from
performa the shortcut menu.
nce
Port Ports 1. Select the NE from the Object Tree in the NE

traffic that Explorer. Choose Configuration > QoS Management
classificat perform > Policy Management > Port Policy from the
ion complex Function Tree.
performa traffic 2. Click the Application Object tab.
nce classifica
tion 3. Select one or multiple ports, right-click and choose
NOTE
Complete the operation of Creating Traffic before monitoring
the port traffic classification performance.


nce Object
Object
Port Egress For FE/GE ports:

priority queues 1. Select the NE from the Object Tree in the NE
performa Explorer. Choose Configuration > Interface
nce Management > Ethernet Interface from the
Function Tree.
2. Click the Basic Attributes tab.
3. Select one or multiple ports, right-click and choose
4. Select the desired egress queue in the Object drop-
down list.
For Integrated IP microwave ports:
1. Select the NE from the Object Tree in the NE
Explorer. Choose Configuration > Interface
Management > Microwave Interface from the
Function Tree.
down list.
Port DS Ports in 1. Select the NE from the Object Tree in the NE

domain a DS Explorer. Choose Configuration > QoS Management
performa domain > Diffserv Domain Management > Diffserv Domain
2. Select the desired DS domain.
3. Click the Application Object tab.
ETHOAM E-Line 1. In the NE Explorer, select the required NE from the

802.1ag service Object Tree and choose Configuration > Ethernet
OAM Management > Ethernet Service OAM
Management.
2. Select the desired MEP, right-click, and choose
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the

OAM Object Tree and choose Configuration > MPLS
Management > Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.


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 5-2 EoS/EoPDH plane

Performa Browse Navigation Path
nce Object
Object
Basic Ethernet In the NE Explorer, select the EFP8 or EMS6 board from
performa porta the Object Tree and choose Performance > RMON
nce Performance from the Function Tree.
NOTE
Extended a:
performa ● EoS Ethernet ports include PORT1 to PORT7 on the EMS6
nce board.
● EoPDH Ethernet ports include PORT1 to PORT9 on the EFP8
VCG- VCTRUN
board.
other K port
performa
nce
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.
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End

5.4.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
● The corresponding boards must be added in the NE Panel.

NCE
Procedure

nce Object
Object
Extended NOTE
the EFP8 board.




nce Object
Object

menu.

menu.

nce Tree.
shortcut menu.

Tree.
nce shortcut menu.
performa
nce


nce Object
Object
nce

nce classifica
NOTE

Function Tree.
down list.
Function Tree.
down list.


nce Object
Object


Management.



nce Object
Object
NOTE
Extended a:
nce board.
board.


nce Object
Object
VCG- VCTRUN
other K port
performa
nce
Function Tree.
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
5.4.3 Setting Parameters for Monitoring Historical Ethernet

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

NCE
Context
To set parameters for monitoring historical Ethernet performance of multiple NEs on the NCE,
choose Performance > RMON History Control Group Management from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance >
RMON History Control Group.

Step 2 Set the parameters of the historical control group.

Step 3 Click Apply. Close the displayed dialog box.
----End
5.4.4 Browsing Historical Ethernet Performance Data

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

NCE
Procedure

nce Object
Object
Extended NOTE
the EFP8 board.



nce Object
Object


menu.

menu.

nce Tree.
shortcut menu.

Tree.
nce shortcut menu.


nce Object
Object
performa
nce
nce

nce classifica
NOTE

Function Tree.
down list.
Function Tree.
down list.


nce Object
Object


Management.



nce Object
Object
NOTE
Extended a:
nce board.
board.


nce Object
Object
VCG- VCTRUN
other K port
performa
nce
Function Tree.
Step 2 Click the History Group tab.
Step 3 Set the parameters of the historical group.

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

This section describes operations related to Ethernet traffic monitoring on
Ethernet ports and microwave ports.
5.5.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

NCE

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.
----End
5.5.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 5.5.1 Setting Traffic, Physical Bandwidth, or
Bandwidth Utilization of Ethernet Ports.

NCE

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
NCE. To collect statistics about the traffic based on Tunnel/PW/egress queue/
VLAN, see 5.4.1 Browsing Current Ethernet Performance or 5.4.4 Browsing
Historical Ethernet Performance Data.
Procedure
Step 1 Query traffic, physical bandwidth, and bandwidth utilization.
----End
5.6 Long-term Network Performance Monitoring

The U2000NCE centrally monitors long-term performance of various Huawei
devices through the Performance Management System (PMS).
5.6.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.


NCE
The Web LCT does not support this operation.
Context
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.
Step 2 Create an RMON TCA monitoring template.

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

NCE

Procedure
Step 1 Open the Create Monitoring Instance dialog box.
Step 2 Select monitoring resources.
Step 3 Select the monitoring template..

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.
Skip this step for the OptiX RTN 980, which does not support the setting of monitoring time.
Step 5 Close the dialog box.
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
5.6.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
● There is at least one performance monitoring instance.

NCE
Procedure
Step 1 Open the real-time monitoring window.
Step 2 View real-time performance data.
----End

5.6.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
● There is at least one performance monitoring instance.

NCE
Procedure
Step 1 Open the historical performance data window.
Step 2 View historical performance data.
----End
5.7 Report Query

This section describes operations related to report query. You can obtain network
information from reports.
5.7.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

NCE
Procedure
Step 1 Query the microwave link information report.
----End
5.7.2 Querying the Network-wide License Report

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

NCE

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

----End
5.7.3 Querying the Microwave Configuration Report

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

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

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

NCE
Procedure
Step 1 Open the board information query window.

Step 3 View query results.
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
5.7.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

NCE

Procedure
Step 1 Query the board manufacturing information report.
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
Manufacturing information of all boards is displayed in Board Details Information Report.
----End
5.7.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

NCE

Procedure
Step 1 Query ODU information.
----End
5.8 Alarm and Performance Management Setting

This section describes operations related to alarm and performance management.
Context
The performance management in this section does not cover Ethernet performance
5.8.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

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

Time Settings from the main menu.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose
Performance > NE Performance Monitoring Time from the Function Tree.
Step 2 Configure the performance monitoring parameters of the NEs.
1. Select 15-Minute or 24-Hour.
2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour
Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
– 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
5.8.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

NCE
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
5.8.3 Suppressing Alarms for Monitored Objects

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

NCE

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.
----End
5.8.4 Suppressing Alarms for NEs

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

NCE

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.
----End
5.8.5 Reversing Alarms for Service Ports

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

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


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

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

NCE
Procedure
Step 1 Set the reporting of alarms and performance events for an IF port and the
corresponding ODU.

----End
5.8.7 Setting Trigger Conditions of AIS Insertion

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

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

----End
5.8.8 Setting Trigger Conditions of UNEQ Insertion

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

NCE
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.
----End
5.8.9 Setting Bit Error Thresholds for Service Ports

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


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

NCE
Procedure
Step 1 Specify Alarm Threshold for Fade Margin Shortage.

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

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

----End
5.8.12 Setting Performance Thresholds

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

NCE
Procedure
Step 2 Choose Performance > Performance Threshold from the Function Tree.
Step 3 Set Threshold Value.
Step 4 Click Apply.

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


NCE
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 6 Troubleshooting
6 Troubleshooting
This guide describes the general troubleshooting procedure and the methods of
rectifying the common faults.
6.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.
6.2 Troubleshooting Service Interruptions
The service interruption fault indicates the service transmission failure due to an
equipment fault or a link fault.
6.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.
6.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.
6.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.
6.6 Troubleshooting the Interconnection with SDH Equipment
An interconnection fault occurs when the NE fails in transmitting SDH services
with other SDH equipment.
6.7 Troubleshooting the Interconnection with PDH Equipment
An interconnection fault occurs when the NE fails in transmitting PDH services
with other PDH equipment.
6.8 Troubleshooting Native Ethernet Service Faults
An Ethernet service fault may be the Ethernet service interruption or Ethernet
service deterioration.
6.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.
6.10 Troubleshooting MPLS Tunnels
This section describes how to troubleshoot MPLS tunnels by using the MPLS—TP
OAM function or MPLS Ping/Traceroute function.
6.11 Troubleshooting CES Services
This section describes how to troubleshoot CES services that are interrupted or
degraded.
6.12 Troubleshooting ATM Services
This section describes how to troubleshoot ATM services that are interrupted or
degraded.
6.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.
6.14 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.
6.15 Troubleshooting Orderwire Faults
If orderwire calls cannot get through when services are normal, there is an
orderwire fault.
6.16 Typical Cases
This section describes typical microwave link troubleshooting cases.
6.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 6-1 General troubleshooting procedure

Table 6-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:
● 6.2 Troubleshooting Service Interruptions
● 6.3 Troubleshooting the Radio Link
● 6.4 Troubleshooting Bit Errors in TDM Services
● 6.5 Troubleshooting Pointer Justifications
● 6.6 Troubleshooting the Interconnection with SDH
Equipment
● 6.7 Troubleshooting the Interconnection with PDH
Equipment
● 6.8 Troubleshooting Native Ethernet Service Faults
● 6.9 Troubleshooting Ethernet Service on the EoS/EoPDH
Plane
● 6.10 Troubleshooting MPLS Tunnels
● 6.11 Troubleshooting CES Services
● 6.12 Troubleshooting ATM Services
● 6.13 Troubleshooting Ethernet Services Carried by PWs
● 6.14 Troubleshooting DCN Faults
● 6.15 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.
6.2 Troubleshooting Service Interruptions

The service interruption fault indicates the service transmission failure due to an
equipment fault or a link fault.

Fault Causes
● The operation is improper.
The configuration data changes, the loopback is performed, the cable is
replaced, or the board is replaced.
● The transmission NE or link is faulty.
● 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 6-2 Description of the general procedure

Table 6-2 Description of the main procedure

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

● Modifying data configuration
● Performing loopback operations
● Shutting down the laser
● Muting the ODU
● Replacing boards/cables
● 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 6-3. If alarms are reported
on the NE, browse the current alarms.
4 Generally, the following alarms can be cleared on the NMS:

● APS_MANUAL_STOP, APS_FAIL
● ARP_FAIL
● BD_NOT_INSTALLED, DBMS_ERROR, NESOFT_MM,
NESF_LOST
● ETH_APS_LOST
● ETH_APS_SWITCH_FAIL, ETH_APS_TYPE_MISMATCH
● HP_TIM, HP_UNEQ
● IMA_GROUP_LE_DOWN, IMA_GROUP_RE_DOWN
● LOOP_ALM
● J0_MM
● LPS_UNI_BI_M
● LP_SLM, LP_TIM, LP_UNEQ
● RADIO_MUTE
● MW_CFG_MISMATCH
● WRG_BD_TYPE
● 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 6-3 shows the field maintenance operation
sheet.
Table 6-3 Field maintenance operation sheet

Maintained on Maintained by
Actual Step Step in the Troubleshooting Remarks

Entire Procedure Result

Figure 6-3 Field troubleshooting sub-procedure

Table 6-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:

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

Comment Description
No.

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

● HP_LOM, HP_UNEQ
● B3_EXC

● T_ALOS
● TU_AIS, TU_LOP, LP_UNEQ
● 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.
6.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:
● Equipment faults, including outdoor component faults, cable faults, and

power supply faults

● Propagation faults, including fading, interference, and poor line of sight (LOS)
● Poor construction quality, including poor antenna/component installation,
poor grounding, and poor waterproofing
Figure 6-4 Radio link faults
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 6-5 Fading phenomena and causes

Fading Type Fading Phenomena Fading Cause
Classifie Down The RSL is lower than the ● Multi-path fading

d by RSL fading RSL after free space fading. ● Duct-type fading
The difference can be tens
of decibels. ● Rain fading
Up The RSL is higher than the ● Interference

fading RSL in the free space. The ● Long delay caused by
difference can be 10-odd terrain reflection
decibels.

Fading Type Fading Phenomena Fading Cause
Classifie Fast The fading lasts from ● Multi-path fading

d by fading several milliseconds to tens ● Duct-type fading
fading of seconds.
duration ● Long delay caused by
Generally, fast fading is terrain reflection
caused by multipath fading.
It occurs 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.
Slow The fading lasts from tens ● Generally, slow up fading

fading of seconds to several hours. is caused by interference.
● 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 6-5 Procedure for troubleshooting the radio link

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

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

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

● MW_LOF, MW_LIM, MW_RDI
● MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR
● RADIO_RSL_HIGH, RADIO_RSL_LOW
● RADIO_RSL_BEYONDTH
● AM_DOWNSHIFT
4 RSL is the major reference for locating and handling propagation faults.
Follow instructions in 5.3.3 Browsing Current Performance Events of
the radio link and 5.3.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 ● 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 9.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.
● 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:
● 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.
● 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.
● 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>.
● 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.
● 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:
● 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.
● 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:
● Multi-path fading: Faults occur periodically, for example, at the day-
and-night alternating time period.
● Duct-type fading: random fast fading
To handle fast fading, proceed as follows:
● 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.
● 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.
● 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.


● During the commissioning, ensure that the antenna is aligned properly, to
prevent possible incipient faults.
● 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.
6.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 6-7 Bit errors

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

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

errors that the line processing ● RS_CROSSTR
unit or the IF board that
works in SDH mode ● RSBBE, RSES, RSSES, RSCSES,
through the B1 overhead RSUAS
byte in the RS 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 ● B2_EXC, B2_SD

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

errors that the line board ● HP_CROSSTR
detects through the B2
byte in the MS overhead ● HPBBE, HPES, HPSES, HPCSES,
HPUAS

Bit Error Description Related Alarm and Performance

Type Event
LP bit Refer to the bit errors ● BIP_EXC, BIP_SD

errors that the tributary board ● LP_CROSSTR
or IF board detects
through the V5 byte in ● LPBBE, LPES, LPSES, LPCSES,
the VC-12 overhead LPUAS
Fault Causes
Table 6-8 Causes of bit errors

Fault Common Fault Cause
There are IF bit ● 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.
● 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.
● The IF board at the local end or opposite end is faulty.
There are RS bit ● 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.
● The line processing unit or IF board is faulty.
● The clock unit is faulty.
● 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 ● The line processing unit or IF board is faulty.
RS bit errors but ● The quality of the clock over the network declines.
there are MS bit
errors or HP bit When the quality of the clock over the network
errors. declines, a pointer justification event occurs.
● The working temperature of the line processing unit or
IF board is excessively high.

Fault Common Fault Cause
There are only LP ● The tributary board is faulty.

bit errors. ● The cross-connect unit is faulty.
● The working temperature of the board is excessively
high.
● The working temperature of the cross-connect unit is
excessively high.
● 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 6-6 Procedure for troubleshooting bit errors

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

Comment Description
No.

● TEMP_ALARM
● HARD_BAD
2 See 6.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 6.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.
The TDM services mentioned refer to Native TDM services.

The handling procedure applies when the STM-1e port is faulty
● During the routine maintenance, check bit error performance events
periodically and handle them in time.
● 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.
6.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:
● AUPJCHIGH
● AUPJCLOW
● AUPJCNEW
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:
● TUPJCHIGH

● TUPJCLOW
● TUPJCNEW
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
● 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.
● The fiber connections are incorrect. As a result, a timing loop occurs.
● The quality of the clock source declines, the clock unit is faulty, or there are
other clock-related faults.
● 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 6-7 Procedure for troubleshooting pointer justifications

Table 6-10 Description of the procedure for troubleshooting pointer justifications
Comment Description
No.

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

● Check whether there are two clock reference sources on the
entire network.
● 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.

Comment Description
No.
5 Replace the possibly faulty boards.

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.
6.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
● 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.
● The overhead bytes at both ends are inconsistent.
● The indexes of the SDH interfaces do not meet the requirements.
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 6-8 Procedure for troubleshooting the interconnection with SDH

equipment

Table 6-11 Description of the procedure for troubleshooting the interconnection

with SDH equipment
Comment Description
No.

● J0_MM
● HP_TIM
● LP_TIM
● HP_SLM
● LP_SLM

● Check whether all the equipment and the DDF in the
equipment room are jointly grounded.
● Check whether the shield layer of the coaxial cable connector
on the DDF is connected to the protection ground.
● 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:

● Mean launched optical power
● Receiver sensitivity
● Overload optical power
● Permitted frequency deviation of the input interface
Common indexes of the electrical interfaces:
● 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.
6.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
● There is an impedance mismatch between interfaces.
● The equipment is not grounded properly.
● The cable performance deteriorates.
● 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 6-9 Procedure for troubleshooting the interconnection with PDH

equipment

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

● Check whether all the equipment and the DDF in the
telecommunications room are jointly grounded.
● Check whether the shield layers of the coaxial cable connectors
on the DDF are connected to the protection ground.
● 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.

● Check whether the wires of the cable are correctly connected.
● Check whether the cable is broken or pressed.
● 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:

● Input jitter tolerance
● Output jitter
● Output frequency deviation
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.

6.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 6-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 Such as ETH_CFM_AIS, ETH_CFM_LCO, and

alarms 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 Such as FLOW_OVER, MAC_EXT_EXC,

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

alarms MW_BER_SD.
Fault Causes
● 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.

● The equipment at the local end is faulty.

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

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

Table 6-14 Description of the procedure for troubleshooting Ethernet services

configured in an end-to-end manner
Comment Description
No.

● Whether a loopback is set for the Ethernet port
● Whether a loopback is set for the transmission line
● 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
● 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.
● If the Ethernet port connecting the peer equipment has a too
high or too low receive rate, the peer equipment is faulty.
● 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.
● 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.
● 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.
6.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
● 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.
● The equipment at the local end is faulty.
● The line board is faulty or has bit errors.
● The interconnected equipment is faulty.
● The network cable is faulty.
● 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 6-11 Procedure for troubleshooting Ethernet service faults

Table 6-16 Description of the procedure for troubleshooting Ethernet service

faults
Comment Description
No.

● Whether a loopback is set for the transmission line
● 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
● 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.
● 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:

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

Comment Description
No.

● ETH_LOS
● FLOW_OVER
● ALM_GFP_dCSF
● ALM_GFP_dLFD
● FCS_ERR
● LCAS_PLCT
● LCAS_TLCT
● LCAS_PLCR
● LCAS_TLCR
● LCAS_FOPT
● 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 11 Performance Event

Reference.

Figure 6-12 Procedure for troubleshooting an RMON performance event
Table 6-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.

● Check the Ethernet cable. If the Ethernet cable is not qualified,
replace it with a new one.
● 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.

● Whether the port operating rates on the equipment at both
ends are the same
● Whether the working modes (full duplex or half duplex) of the
Ethernet port on the equipment at both ends are the same
● 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.)

● Whether the flow control method is the same.
● 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.
6.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:
● MPLS tunnels fail to be created, and services are unavailable.

● MPLS tunnels are faulty, and services are interrupted.
● MPLS APS switching fails, services are interrupted, and packet loss or bit
errors occur.
Table 6-18 Common faults of MPLS tunnels
Symptom Alarm Board
MPLS HARD_BAD, TEMP_ALARM, CSHN

tunnels are WRG_BD_TYPE, BUS_ERR, BD_STATUS,
faulty. 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
● 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.
● The local NE is faulty.
● The transmission link is faulty or has bit errors.
● Service bandwidth decreases due to an AM downshift.
● 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 6-13 Procedure for troubleshooting MPLS tunnels

Table 6-19 Description of the procedure for troubleshooting MPLS tunnels

Comment Description
No.

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

● 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
● AM_DOWNSHIFT
● MW_CFG_MISMATCH
● MW_LIM
● MW_LOF
● MW_BER_EXC
● MW_BER_SD
● MW_RDI
● 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:
● ARP_FAIL
● MPLS_TUNNEL_BDI
● MPLS_TUNNEL_Excess
● MPLS_TUNNEL_FDI
● MPLS_TUNNEL_LOCV
● MPLS_TUNNEL_MISMATCH
● MPLS_TUNNEL_MISMERGE
● MPLS_TUNNEL_OAMFAIL
● MPLS_TUNNEL_SD
● MPLS_TUNNEL_SF
● MPLS_TUNNEL_UNKNOWN
● MPLS_TUNNEL_AIS
● MPLS_TUNNEL_RDI
● MPLS_TUNNEL_UNEXPMEG
● MPLS_TUNNEL_UNEXPMEP
● MPLS_TUNNEL_UNEXPPER

Learn about the working principle and protocol configuration of MPLS tunnels
before troubleshooting MPLS tunnels.
6.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 6-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, BD_STATUS,
interrupted CES_LOSPKT_EXC
.
AM_DOWNSHIFT ISV3, ISU2, ISX2, IFU2,
MW_CFG_MISMATCH IFX2
CES HARD_BAD, TEMP_ALARM, CSHN, ML1, MD1, CQ1

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

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

1. Check whether the data is modified, whether the line is looped back, and
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 6-14 Procedure for troubleshooting CES services

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

Comme Description
nt No.

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

● 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
● AM_DOWNSHIFT
● MW_CFG_MISMATCH
● MW_LIM
● MW_LOF
● MW_BER_EXC
● MW_BER_SD
● MW_RDI
● MW_FEC_UNCOR

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

If the PW fails to be pinged, check the following:
● Check whether the hardware and cable connections on the UNI
side are normal.
● Check whether PWE3 service configurations on the UNI side are
correct.
● Check whether port working mode and tag attribute
configurations on the UNI side are consistent with those at the
peer end.
4 Run PW ping or LSP Tracerout to check whether the MPLS tunnel is

faulty.
Handle the tunnel fault by referring to instructions in 6.10
Troubleshooting MPLS Tunnels.
Check whether PW configurations are correct. If the configurations
are incorrect, re-configure the PW according to the network plan.

● CES_JTROVR_EXC
● CES_JTRUDR_EXC
● CES_LOSPKT_EXC
● CES_MALPKT_EXC
● CES_MISORDERPKT_EXC
● CES_STRAYPKT_EXC

● T_ALOS
● UP_E1_AIS
● LFA
● LMFA
● ALM_E1RAI

● CES_MISORDERPKT
● CES_LOSPKT
● CES_MALPKT
● CES_JTRUDR
● CES_JTROVR
● 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.
6.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 6-22 Common faults of ATM services
Symptom Alarm Board
ATM HARD_BAD, TEMP_ALARM, CSHN, ML1, MD1

services are WRG_BD_TYPE, BUS_ERR, BD_STATUS,
interrupted 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
opposite end.


1. Check whether the data is modified, whether the link is looped back, and
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 6-15 Procedure for troubleshooting ATM services

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

Comment Description
No.

● Whether a loopback is set for the E1 port
● Whether the parameter settings of ATM VPI/VCI, PWE3 CW,
PW, and Tunnel are consistent between the source end and the
sink end.
● 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
● Check whether the network bandwidth is sufficient for the
service traffic.

Comment Description
No.

● 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
● AM_DOWNSHIFT
● MW_CFG_MISMATCH
● MW_LIM
● MW_LOF
● MW_BER_EXC
● MW_BER_SD
● MW_RDI
● MW_FEC_UNCOR
3 Check whether the PW is faulty using the PW ping function.

If the PW fails to be pinged, perform the following checks:
● Check whether the hardware and cable connections on the UNI
side are normal.
● Check whether PWE3 service configurations on the UNI side are
correct.
● 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 6.10
Troubleshooting MPLS Tunnels.
Check whether PW configurations are correct. If the configurations
are incorrect, re-configure the PW according to the network plan.

Comment Description
No.

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

● T_ALOS
● UP_E1_AIS
● LFA
● LMFA

● ATMPW_UNKNOWNCELLS
● 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.
6.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 TEMP_ALARM EG4, EG4P, EG2D, EM6TA, EM6FA,

services 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
opposite end.

1. Check whether the data is modified, whether the link is looped back, and
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 6-16 Procedure for troubleshooting Ethernet services

Table 6-25 Description of the procedure for troubleshooting Ethernet services

configured in an end-to-end manner
Comment Description
No.

● 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
● 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.
● If the Ethernet port connecting the peer equipment has a too
high or too low receive rate, the peer equipment is faulty.
● 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.
● 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.
● 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.
6.14 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 6-26 Fault symptoms and causes

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

their service ports like air ● Cause 2: DCN parameters are incorrectly set.
interfaces and Ethernet
ports are unreachable to ● Cause 3: System control boards are faulty.
their NMS.
NEs connected through ● Cause 1: The network cable of the NMS is

their NMS ports are disconnected or damaged.
unreachable to their ● Cause 2: DCN parameters are incorrectly set.
NMS.
● Cause 3: System control boards are faulty.
A few NEs are ● Cause 1: DCN parameters are incorrectly set.

unreachable or their ● Cause 2: An NE ID or NE IP address conflict
connection to the NMS is occurs between NEs on the DCN subnet.
unstable.
● Cause 3: The DCN subnet is too large.
● Cause 4: The system control unit of the NE is
faulty.

Figure 6-17 Procedure for troubleshooting DCN faults

Table 6-27 Procedure description for troubleshooting DCN faults

Mark Operation Typical Symptom Measures
1 Locate the Locate the faulty NE ● If the faulty NE has a service fault, rectify
faulty NE. based on a DCN the service fault first.
networking diagram. ● If an unreachable NE connects to its NMS
● If all NEs within an through an external DCN, verify that the
area are external DCN equipment or the cable used
unreachable to for DCN connection is working correctly.
their NMS, the
unreachable NE
closest to a normal
NE is probably the
faulty NE.
● If only one NE is
unreachable to its
NMS, the NE is the
faulty NE.
2 Handle ● The faulty NE ● Handle hardware alarms based on the

hardware reports hardware maintenance and fault management
faults. alarms like procedure.
HARD_BAD. ● Remove and then install, or replace the
● Check whether the network 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 ● Check for unplanned NE IDs and NE IP

incorrect operations are addresses in the ECC routing table of the
configurations performed before a faulty NE's upstream NE. If there is an
. faulty NE becomes unplanned NE ID or IP address in the ECC
unreachable to its routing table, the faulty NE is incorrectly
NMS: configured. To rectify the fault, log in to the
● Modifying NE faulty NE using the unplanned NE ID and NE
attributes or NE IP address on the NMS and correct the
communication settings.
settings ● Change the DCC settings or inband DCN
● Adding a new NE settings of the faulty NE to interrupt the
to the network, or DCN channel between the faulty NE and its
replacing the faulty upstream NE. Then, check for the ID and IP
NE or its system address of the faulty NE in the ECC routing
control board 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.
● 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.
● Verify that static routes are correctly set on
the faulty NE's upstream NE.
● 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 If there is a large number of NEs in the routing
DCN subnet NEs in the IP routing table, the DCN subnet is too large in size and
size. table or ECC routing some NEs on the DCN subnet may occasionally
table of the faulty become unreachable to their NMS. It is
NE's upstream NE. 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 ● Verify that a minimum of 192 kbit/s

NMS occasionally become bandwidth is allocated to the inband DCN. If
information unreachable to their the allocated bandwidth is lower than 192
loss. NMS. kbit/s, packets from the NMS may be lost.
● 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 ● The NE fails to be ● Search for the IP address of the faulty NE on

no-response logged in to onsite. the NMS.
problems. ● The NE does not ● If the IP address is not found, or if the IP
respond to address is found but the NMS still cannot
commands. reach the faulty NE, restart the OptiX RTN
980 after a power-off, in a authorized
maintenance window which service can be
interrupted.
6.15 Troubleshooting Orderwire Faults

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

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

Figure 6-18 Procedure for troubleshooting orderwire faults

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

● Check whether the ring current switch "RING" on the phone set
is set to "ON".
● Check whether the dialing mode switch is set to "T", namely,
the dual tone multi-frequency mode.
● 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.

● Whether all orderwire phone numbers on a subnet are of the
same length
● Whether all orderwire phone numbers on a subnet are unique
● Whether the overhead bytes of all the NEs on a subnet are the
same
● 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.
6.16 Typical Cases

This section describes typical microwave link troubleshooting cases.
6.16.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

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

6.16.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.
To protect long-distance cross-ocean radio links against multipath fading, take the
following measures during network planning:
● Ensure that the fading margin is greater than or equal to 30 dB.
● 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.
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.
6.16.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 6-19.
Figure 6-19 Microwave link between buildings

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.
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.
6.16.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:
● The ODU cannot support the new IF mode of high modulation and of large
capacity after the link capacity is expanded.
● The link is interrupted because the receive power cannot meet the sensitivity
requirement in the new IF mode.
● 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.
6.16.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.
6.16.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 6-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 6-20 Using the ITU-R-P.530-7/8 method
Figure 6-21 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 7 Part Replacement
7 Part Replacement
Part replacement is a method frequently used to locate faults. The replacement

operation varies according to the specific part type.
Table 7-1 Part replacement description
Part Name Operation Tool
CQ1 7.4 Replacing the ● ESD wrist strap

Channelized STM-1 ● Screwdriver
Processing Board
● NCE
SL1D, SL1DA 7.3 Replacing the SDH ● Fiber extractor
Optical Interface Board
EX1, EG4, 7.7 Replacing the Ethernet

EG4P, EM6T, Interface Board
EM6F, EMS6,
EM6TA,
EM6FA, EM6
and EFP8
CF card 7.10 Replacing the CF Card
CSHN, CSHNA 7.11 Replacing the System

and CSHNU Control, Switching and
Timing Board
AUX 7.12 Replacing the Auxiliary

Board
SP3D and SP3S 7.5 Replacing the PDH ● ESD wrist strap
Interface Board ● Screwdriver
ISM6, ISV3, 7.8 Replacing an IF Board ● NCE
ISX2, ISU2, IF1,
IFU2, ISM8 and
IFX2

Part Name Operation Tool
PIU 7.14 Replacing the Power

Board
ML1 and MD1 7.6 Replacing the Smart E1

Interface Board
FAN 7.13 Replacing the Fan ● ESD wrist strap

Board ● NCE
ODU 7.16 Replacing an ODU ● Wrench (torque wrench)

● NCE
● Silicon
● Waterproof adhesive tape
IF cable 7.17 Replacing an IF Cable ● Multimeter

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

● Tweezer Fiber extractor
● NCE
7.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 7-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.
Use fiber removers to remove fibers or network cables.
Figure 7-2 Tweezer fiber remover
Step 3 Remove the board.

1. Loosen the screws on the panel of the board.
Figure 7-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.
As shown in Figure 7-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 7-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
7.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 7-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 7-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
7.3 Replacing the SDH Optical Interface Board

When the SDH optical interface board is replaced, the unprotected services on the
board are interrupted.

Prerequisites
● You must know the impact of board replacement.
● You must know the specific position of the board to be replaced.
● You must know the service protection and protection channels of the board to
be replaced.
● 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.

● ESD wrist strap
● Screwdriver
● NCE
● 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
7.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
be replaced.
● 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.

● ESD wrist strap
● Screwdriver
● NCE
● Fiber remover
Procedure
Step 2 Optional: If the services on the board are configured with linear MSP, ensure that
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


----End
7.5 Replacing the PDH Interface Board

When the PDH interface board is replaced, the services on the board are
interrupted.
Prerequisites
be replaced.
● 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.

● ESD wrist strap
● Screwdriver
● NCE
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

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

When the Smart E1 Interface board is replaced, the services on the board are
interrupted.

Prerequisites
be replaced.
● 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 manufacturing information to obtain the version
of the board to be replaced.

● ESD wrist strap
● Screwdriver
● NCE
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
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.
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
7.7 Replacing the Ethernet Interface Board

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



● ESD wrist strap
● Screwdriver
● NCE
● 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.
switching.
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.
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.

Step 9 Optional: If the forced switching has been performed for the services, release the
forced switching.
----End

7.8 Replacing an IF Board

When an IF board is replaced, unprotected services on the board are interrupted.
Prerequisites
be replaced.
● 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 manufacturing information to obtain the version

● ESD wrist strap
● Screwdriver
● NCE
Precautions
IF boards support hot swap. After a substitute board is installed, it enters the
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.

switching.
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.
switching.
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.
switching.
Step 6 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.
switching.
Step 7 Optional: If the IF board is configured with the XPIC function, see 9.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 Turn off the ODU-PWR switch on the IF

be 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
replaced ODU.

Step 10 Check and verify that the version and type of the spare board are the same as the
version and type of the board to be replaced.
Step 11 Ensure that the ODU-PWR switch on the front panel of the spare IF board is
turned off.
Skip this step when replacing a dual-channel IF board (ISM6 and ISM8).


If... Then...
A single-channel IF board needs to Turn on the ODU-PWR switch on the

be replaced front panel of the IF board.
NOTICE
To turn on the ODU-PWR switch, pull the
switch to the "I" position.
A dual-channel IF board needs to be Turn on the soft power switch of the

replaced ODU.

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 9.1.3 Muting/Unmuting
an ODU and unmute the ODU at the opposite end.
----End
7.9 Replacing an Single-Channel IF Board with the

ISM6
When the single-channel IF board (IFU2/IFX2/ISU2/ISX2/ISV3) needs to be
replaced with the dual-channel IF board ISM6, perform this operation. When an IF
board is replaced, services on the board are interrupted.
Prerequisites
● You must know the specific position of the board to be replaced. The IF
boards only can be repalced at the same slot.
● Check whether the IF boards of the NEs at the high and low sites do not have
fiber connections. If yes, delete the fibers before replacing the boards.
Figure 7-11 NEs with the fiber connection


● ESD wrist strap
● Screwdriver
● NCE
Precautions
IF boards support hot swap. After a substitute board is installed, it enters the
Only the 1+0 configuration is supported. All services on the single-channel IF
board (IFU2/IFX2/ISU2/ISX2/ISV3) are switched to the IF1 port on the ISM6.
NOTICE
This operation requires a cold reset on the NE. All services on the NE are
interrupted.
Procedure
Step 2 Optional: On the NE Panel, perform the following operations to replace the IF
board. The following uses RTN 950A as an example to describe how to replace
ISU2. The operations on other boards of other products are similar.

If slot 04 on the NE panel changes to ISM6, the board is replaced successfully.

After confirming that the board is replaced successfully, perform the subsequent
operations.

Step 3 Turn off the ODU-PWR switch on the front panel of the IDU.
NOTICE
To turn off the ODU-PWR switch, pull the switch lever outwards slightly and set
the switch to the "O" position.
Step 4 Remove the IF cable from the IF board to be replaced.

Step 5 Remove the board to be replaced.
Step 6 Check and verify that the version and type of the ISM6 board.
Step 7 Insert the ISM6 board.
Step 8 Connect the IF cable removed in step 4 to the IF1 port on the new ISM6 board.
Step 10 Turning On the Soft Power Switch of an ODU.
Step 11 Observe the LINK1 and ACT1 indicators on the replaced ISM6 board. The
indicators should be on and green.

Step 12 Query the current alarms of the ISM6 board.

Step 13 Optional: Perform a cold reset on the SCC board or power off the NE. If there are
active and standby system control boards, reset the active control board first.
Step 14 Optional: Observe the indicators on the ISM6 board to ensure that the link
recovers.
----End
7.10 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
● You must be aware of the impact of CF card replacement.
● You must know the specific position of the CF card to be replaced.
● You must be a user with "NE maintainer" authority or higher.
● You must obtain a spare CF card that has the same capacity as the CF card to
be replaced.

● ESD wrist strap
● NCE
● 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 9.12 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
There should be no new alarms.
Step 10 Optional: If the manual switching has been performed on the board, release the
manual switching.
----End
7.11 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

Prerequisites
● You must be aware of the impact of board replacement.
be replaced.
● 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.

● ESD wrist strap
● Screwdriver
● NCE
● Fiber remover
● 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
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 10.2.134
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

control, the power supply and remove the board.
switching, 2. Verify that the version and type of the spare board
and timing (including the patch version) are correct.
board is
NOTE
configured If the spare board and the board to be replaced have different
patch versions, contact Huawei technical support 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 7.10 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
▪ In the process of restoring the NE database, the PROG

indicator on the board blinks green for about 20 minutes.
▪ 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.
▪ 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,

control, and timing board, switch services from the working
switching, board to the protection board. For details, see 9.12
and timing Switching the System Control Unit and the Cross-
boards are Connect Unit.
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
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
▪ 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.
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, If the NE is running, back up the NE data to the USB flash
and timing drive.
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. Removing a 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. Inserting a Board.
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:
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.
Restore NE configuration data by referring to 8.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.

If... Then...
7. Query the current alarms of the board. There should be

no new alarms.
Two system 1. Query the current alarms of the board.

control, 2. Before replacing a working system control, switching, and
switching, timing board, switch services from the working board to the
and timing protection board. For details, see 9.12 Switching the
boards are System Control Unit and the Cross-Connect Unit.
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.
3. After completing the protection switchover, Remove the
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
7.12 Replacing the Auxiliary Board

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

Prerequisites

● ESD wrist strap
● Screwdriver
● NCE
● Fiber remover
Procedure
Step 4 Insert the spare board.

There should be no new alarms on the auxiliary board.
----End
7.13 Replacing the Fan Board

The IDU cannot perform air cooling in the process of fan board replacement.
Therefore, you need to replace the fan board within three minutes.
Prerequisites
query the board manufacturing information to learn about the version of
the board to be replaced.
Impact on system
● Replacing the fan board does not impact services.

● If the fan board replacement exceeds three minutes, the device may become
faulty due to heat dissipation failure.

● ESD wrist strap
● NCE
Precautions
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

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

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

● ESD wrist strap
● Screwdriver
● NCE

Precautions
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
----End
7.15 Replacing the SFP

When the small form pluggable (SFP) is replaced, the unprotected services on the
optical/electrical port are interrupted.
Prerequisites
● You must know the impact of SFP replacement.
● You must know the specific position of the SFP to be replaced.
● You must know the service protection and protection channels of the SFP to
be replaced.
● 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
SFP to be replaced.
● The method of replacing the AE 905S module embedded in an Atom GPS
system is similar to the method of replace the SFP. During module
replacement, select and use another clock source.


● ESD wrist strap
● Tweezer fiber remover
● NCE
Procedure
Step 2 Optional: If SNCP is configured for services at the optical interface, ensure that
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 Optional: If SSM protection has been configured for the clock source and the
current Atom GPS is the network clock source, ensure that the system has
switched to another clock source.
1. Query the clock synchronization status.
2. Re-configure the clock source.
Step 5 Record the cable connections of SFP or AE 905S, and then disconnect cables.
Step 6 Check the types of the spare SFP and the SFP to be replaced, and remove SFP or
AE 905S module.

● Hold the extraction lever to remove the optical module.
● Press the release button before removing STM-1 electrical module or AE 905S module.
Step 7 Insert the standby SFP or AE 905S module and reconnect cables based on the
record.

Step 9 Optional: If the forced switching has been performed on the board, release the
forced switching.
Step 11 If another clock source has been configured, re-configure the Atom GPS as the
clock source.
----End
7.16 Replacing an ODU

When an ODU is replaced, the unprotected services on the ODU are interrupted.
Prerequisites
● You must know the impact of ODU replacement.
● You must know the specific positions of the ODU to be replaced and the IF
board connected to the ODU.

● The spare ODU must be at hand, whose type and frequency band must be the
same as the type of the ODU to be replaced.

● Ejector lever (torque wrench)
● NCE
● Silicon
Precautions
● Before replacing an ODU, power off the ODU.

● 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
● 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.
● 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 Turn off the ODU-PWR switch on the IF
a single-channel IF board board.
NOTICE
The ODU to be replaced connects to Turn off the soft power switch of the
a dual-channel IF board ODU.
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 Loosen the four latches of the ODU and
ODU with a waveguide interface disconnect the ODU from the antenna,
the hybrid coupler, or ODU adapter.
You need to remove the RTN 600 Remove the ODU from the post.
ODU with a coaxial interface
You need to remove the RTN XMC Loosen the captive screws on the ODU
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 See the RTN 600 ODU Quick
with a waveguide interface Installation Guide.
You need to install a new RTN 600 ODU See the RTN 600 ODU Quick
with a 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 Turn on the ODU-PWR switch on the
a single-channel IF board front panel of the IF board.
NOTICE
The ODU to be replaced connects to Turn on the soft power switch of the
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

7.17 Replacing an IF Cable

When an IF cable is replaced, the unprotected services on the IF cable are
interrupted.
Prerequisites
● You must know the impact of IF cable replacement.
● You must know the specific positions of the IF cable to be replaced and the IF
board connected to the IF jumper.
● 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.

● Multimeter
● Ejector lever
● Electro-technical knife
● File
● Installation parts and accessories of the connector
● 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 Turn off the ODU-PWR switch on the IF
a single-channel IF board board.
NOTICE
The ODU to be replaced connects to Turn off the soft power switch of the
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 See the Installation Reference and
the IF cable make new connectors for the IF cable.
You need to replace the IF cable with Replace the IF cable with a new one.
a 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 Turn on the ODU-PWR switch on the
a single-channel IF board front panel of the IF board.
NOTICE
The ODU to be replaced connects to Turn on the soft power switch of the
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

7.18 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.
7.18.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
7-2, the types of storage media supported by the system control boards for the
OptiX RTN 980 are listed.
Table 7-2 Types of storage media on the system control boards
Board Storage Media
CSHN/CSHNA ● Flash memory (integrated on the

system control board)
● 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.
CSHNA boards do not provide DIP switches.
7.18.2 Removing the CF Card

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

● ESD wrist strap or ESD glove

● 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 7-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 Remove the CF card.
Step 3 Place the removed CF card to an ESD bag.
----End
7.18.3 Formatting the Flash Memory

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

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

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.
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.
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 8 Database Backup and Restoration
8 Database Backup and Restoration
The OptiX RTN 980 supports database backup and restoration through the NMS.
8.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.
8.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.
8.3 Setting the Database Backup Policy
8.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.
8.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.
8.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.
8.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.
8.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:
● 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.
● 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.
● 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:
● An NE backs up DRDB data to the FDB within five minutes after NE
configuration data is modified.
● Perform two backups of DRDB data to different areas on the FDB every 24
hours.
● 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:
● 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).
● On the NMS, FDB data can be backed up to an NMS server manually or at
specified intervals.
● 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.
● 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.

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.
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
● 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.
● When the NE is cold reset, the system control unit restores data from FDB0
and FDB1.
● When the data in both FDB0 and FDB1 is damaged, data can be restored
from the dedicated partition of the flash memory.
● On the NMS, the FDB data in flash memory can be restored from an NMS
server without interruption of TDM services.
● 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.
● 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.
8.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
● You must be an NM user with NE administrator authority or higher.

● You must log in to the NE.

NCE
Procedure
Step 1 On the NMS, choose Maintenance > 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.
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 OSS Server or OSS 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
8.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.
The scheduled database backup function allows you to back up NE data at a specified time
to prevent NE data loss. You are advised to enable the scheduled backup function for the
NCE.
8.3.1 Setting the User-Defined Backup Policy

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

NCE

Each NE has a default data backup policy.
● Database packages are backed up once at 2:00.
● The default backup policy is disabled by default.
● A maximum of five database packages can be backed up.
● Data changes do not trigger any backup operations.
Procedure
Step 1 Choose Maintenance > 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 Set Policy dialog box is displayed.
Step 8 Set Policy Name, Period Backup Policy, and Period Save Policy.
● If The Added NE's Policy Status is set to Enable, the NMS performs the backup
operation within the specified period, day, and time.
● 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
8.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.

NCE

Procedure

Step 3 Right click the selected NE, Click Enable Backup Policy.
----End
8.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

NCE
Procedure
Then, the NE Backup Policy Management dialog box is displayed.

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

----End
8.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
● The data to be restored must be backed up.

NCE
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.
OptiX RTN 980 supports use of old-version backup files to restore the database.
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 Maintenance > NE Software Management > NE Data
Backup/Restoration from the Main Menu.

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.
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 OSS Server or OSS 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.
● 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.
● 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.
● If Deliver To Board Activate is selected, the EFP8/EMS6 board will be instructed to
perform a cold reset during database activation.
● If Deliver To Board Activate is unselected, the EFP8/EMS6 board will not be cold reset.
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
8.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
● The NE database has been backed up.
● You have logged in to the NE on the NMS.

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

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.
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.
Step 3 Insert the USB flash drive in the USB port on the OptiX RTN 980.
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 The loading of Remove the USB flash

yellow and then turns commissioning data is drive.
steady green. complete.
NOTE
● When the indicator is
blinking yellow, do not
remove the USB flash
drive. Otherwise, the
data loading may be
interrupted.
● 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 ● Copy the

faulty and fails to get commissioning data
online. to another USB flash
NOTE drive.
Another possible cause is ● Repeat 1 to load the
that the USB flash drive is
commissioning data
not properly inserted.
to the NE.

Status of the USB Data Loading Status Operation

Indicator
The indicator blinks red. The type of the USB ● Copy the
flash drive is incorrect or commissioning data
an error occurs when the to another USB flash
NE attempts to read/ drive.
write the USB flash drive. ● Repeat 1 to load the
NOTE commissioning data
Preparing Documents and to the NE.
Tools provides the USB
flash drive types that the
OptiX RTN 980 supports.
The indicator is steady The loaded Reload the data:

red. commissioning data is ● Save the correct NE
abnormal. software and
commissioning data
scripts in the correct
directories of the USB
flash drive.
● Repeat 1 to load the
commissioning data
to the NE.
----End
8.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.

NCE
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.
Step 2 Check the execution results.

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

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

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 9 Common Maintenance Operations
9 Common Maintenance Operations
This section introduces common maintenance operations.
9.1 Microwave Link Troubleshooting

This section describes common maintenance operations related to microwave link
troubleshooting.
9.2 Ethernet Service Troubleshooting
This section describes common maintenance operations related to Ethernet service
troubleshooting.
9.3 TDM/CES Service Troubleshooting
This section describes common maintenance operations related to TDM/CES
service troubleshooting.
9.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.
9.5 Hardware Loopback
Hardware loopback refers to the loopback operation performed by changing the
physical connection.
9.6 Reset
Reset is an important method of troubleshooting software faults. Reset is
classified into cold reset, warm reset.
9.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.
9.8 Querying Site Information
You can query microwave site information and ODU information.
9.9 Querying Power Consumption of Boards
This section describes how to query power consumption of the ODU and each
board.

9.10 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.
9.11 Preventing Service Loops
You can enable the automatic service loopback detection function or the
automatic broadcast packet suppression function to prevent service loops.
9.12 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.
9.13 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.
9.1 Microwave Link Troubleshooting

This section describes common maintenance operations related to microwave link
troubleshooting.
9.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
● The time and time zone of an NE on which microwave link indicators are
sampled must be the same as those on the NMS.

NCE
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.
Step 3 Query the monitoring result.

----End
9.1.2 Scanning Interfering Signals

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

NCE
● When interfering signals are scanned, services and DCN communication are
interrupted.
● If the other RFUs on the same BU are muted, 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.
● Short-haul microwave uses ODUs, and long-haul microwave uses RFUs.
Procedure
Step 1 Scan interfering signals.
● ODU Frequency Scan.

----End
9.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
● The corresponding IF boards and the ODUs connected to the IF boards must
be added to the NE Panel.

NCE
Procedure
● Mute/Unmute an ODU.

----End
9.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
● The mapping IF board and ODUs have been added on the NE Panel.

NCE
Procedure
● Turn on/off the soft power switch of an ODU.

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

NCE
Precautions
Two PRBS test types are available, PRBS frames are transmitted through the
specified E1 timeslot or transmitted as Ethernet frames.
Figure 9-1 PRBS test of the IF Board

NOTICE
● During the PRBS test, the services in the tested path are interrupted.
● The PRBS test can be performed only in one path and in one direction at one
time.
● During the PRBS test, ensure that the PRBS function is enabled on both the
local end and peer end.
● 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 9.4.7
Setting Loopback for the IF Board.
Step 2 Start a PRBS test on the IF board.
Step 3 View test results.

----End
9.2 Ethernet Service Troubleshooting

This section describes common maintenance operations related to Ethernet service
troubleshooting.
9.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

NCE

Procedure
Step 1 Optional: Query the attributes of the FE or GE port on the packet plane.
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.

1. In NE Explorer, select the required NE from the Object Tree.
2. Choose Configuration > Interface Management > Microwave Interface
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.
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.
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
9.2.2 Using IP Ping Commands to Locate Ethernet Service

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


NCE
Context
Two types of IP ping functions are supported:
● 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 9-2.
● 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
9-2.
Figure 9-2 Application of the IP ping functions
Precautions
● IP ping can be enabled only for UNI Ethernet ports.
● IP ping can be enabled only for a maximum of four ports on an NE.
● E-Aggr services do not support far-end IP ping.
● 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.
● 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.
● 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.
● The maximum length of the IP ping packet is 1494 bytes.
Sample IP Ping Connection

Figure 9-3 shows the test procedure, using the Ethernet service between PORT1
on NE1 and PORT1 on NE2 as an example.
Figure 9-3 Networking diagram
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
● 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.

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.
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 Go to the next step.

from 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.
Response packets are received Services are normal. Therefore,

from the NodeB. end fault diagnosis.
e. On NE2, initiate near-end IP ping to the NodeB (that is, ping 137.0.0.2).
If... Then...

the NodeB. Handle the fault.
Response packets are received A transmission network fault

from the NodeB. occurs between NE1 and NE2.
Handle the fault.
● 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.
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.
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 Services are normal. Therefore,

from the NodeB. end 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 Go to the next step.

from NE1.

the 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 A fault occurs between NE2 and

from NE2. the NodeB. Handle the fault.
The operation times out A transmission network fault

occurs between NE1 and NE2.
Handle the fault.
----End

9.2.3 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

NCE
Context
Figure 9-4 Schematic diagram of Ethernet port mirroring
The port mirroring can be performed in two directions.

For the physical ports:
● 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.
● 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:
● In the upstream direction, the ports mirror the data transmitted from the
VCTRUNK to the TDM side.
● In the downstream direction, the ports mirror the data transmitted from the
TDM side to the VCTRUNK.

Precautions
EG4/EG4P/EM6 boards of the OptiX RTN 980 do not support port mirroring in the
egress direction.
● The SCC board is CSHUF.
● The Ethernet port of the EG4/EG4P/EM6 is used as the mirroring port.
● The accessed service traffic is greater than the capability of the mirroring
port.
● the traffic limit of the monitoring port is greater than that of the mirroring
port.
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
9.2.4 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

NCE
Context
Figure 9-5 Traffic mirroring over Ethernet ports
Port traffic mirroring duplicates only service traffic matching the specified rule to
the listening port.
Precautions
● One NE supports a maximum of four port traffic mirroring (only ingress) or port
mirroring configurations.
● One port supports only one port traffic mirroring configuration. If port traffic mirroring
is configured, ingress port mirroring cannot be configured.
● 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.
● 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.
● 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.
● MPLS packets can be mirrored only by Ethernet frame header before the MPLS label.
● Only data boards support port traffic mirroring.
● After port traffic mirroring is configured, traffic mirroring rules must not be modified or
deleted.

Procedure
Step 1 Configure the port traffic mirroring function.
----End
9.2.5 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
● Ethernet services have been created, and service packets are being forwarded.
● The port is not configured with complex traffic classification.

NCE
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).
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
● 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.
● On the OptiX RTN 980, packet headers cannot be captured from the slave
port of an inter-board LAG.
● 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.
● The OptiX RTN 980 allows header capturing only from ingress packets.
● 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.
● On the OptiX RTN 980, the packet header capturing function cannot be
enabled for Layer 3 ports or mixed (Layer 2+Layer 3) ports.
● 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
● Capture headers of Layer 2 packets.
● Capture headers of Layer 3 packets.

----End
9.2.6 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
● The service traffic is encapsulated or mapped by using the GFP method.

NCE
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 9-6 Ethernet test frames between Ethernet boards

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.
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.
9.3 TDM/CES Service Troubleshooting

This section describes common maintenance operations related to TDM/CES
service troubleshooting.
9.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

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

NCE
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
9.3.3 Performing a PRBS Test for the Smart E1 Processing

Board
embedded test system on the Smart E1 processing Board.
Prerequisites

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

Figure 9-7 PRBS test in the tributary direction
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
9-8.
Figure 9-8 PRBS test in the NNI direction
Precautions
NOTICE
time.
● 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.
● 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.

Procedure
Step 1 Configure a loopback as required by referring to Figure 9-7 and Figure 9-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

----End
9.3.4 Performing a PRBS Test for the Tributary Board

embedded test system on the tributary Board.
Prerequisites

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

Figure 9-9 PRBS test in the tributary direction
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
9-10.
Figure 9-10 PRBS test in the cross-connect direction

Precautions
NOTICE
time.
● 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.
Procedure
Step 1 Configure a loopback as required by referring to Figure 9-9 and Figure 9-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.

----End
9.3.5 Querying the Impedance of an E1 Channel

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

NCE
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
9.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
● 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.
● Loopback operations on E-LAN services may cause network storms and service
interruptions.
9.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

NCE
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 9-11 Optical/electrical interface inloop
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 9-12 Optical/electrical interface outloop
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 9-13 VC-4 path outloop
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 9-14 VC-4 path inloop
Precautions
NOTICE
● The services may be interrupted at the port or on the path where the loopback
is performed.
● A software loopback may be released automatically after a certain period (five
minutes, by defaults). For details, see 9.7 Setting the Automatic Release
Function.
Procedure
Step 1 Select the SDH optical interface board from the NE Explorer.
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

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

NCE
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 9-15 Optical/electrical interface inloop
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 9-16 Optical/electrical interface outloop

Precautions
NOTICE
is performed.
Function.
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
9.4.3 Setting Loopback for the Tributary Board

The tributary board supports the tributary inloop and outloop.
Prerequisites

NCE
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 9-17 Tributary inloop
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 9-18 Tributary outloop
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
9.4.4 Setting a Loopback for the Smart E1 Processing Board

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

NCE
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 9-19 E1 inloop
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 9-20 E1 outloop

Precautions
NOTICE
is performed.
● A software loopback may be released automatically within a period (5 minutes,
by default). For details, see 9.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.
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
9.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

NCE

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 9-21 Ethernet port inloop
Precautions
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
● A loopback operation results in service interruption.

Function.
NOTICE
● 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.
● 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.
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
9.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

NCE

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.
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 9-22 Ethernet port inloop
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.
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.

Precautions
NOTICE
● A loopback operation may interrupt the services on the port where the
loopback is performed.
● A software loopback may be automatically released within a period (five
minutes by default). For details, see 9.7 Setting the Automatic Release
Function.
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
inloop Tree.
2. Select By Function.
3. Select the required VC-12 path.
VC-3 path 1. Choose Configuration > SDH Interface from the Function
inloop 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
9.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

NCE
Context
The IF port inloop is a process wherein the IF signals are looped back at the
modem unit towards the backplane.
Figure 9-25 IF port inloop
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 9-26 IF port outloop
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 9-27 Composite port inloop
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 9-28 Composite port outloop

Precautions
NOTICE
is performed.
Function.
● 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.
● 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.
Steps for configuring a loopback for an IF board on the U2000NCE 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.
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 >

loopback Microwave Interface from the Function Tree.
2. Select Loopback Attributes.
and set Composite port loopback.

MAC loopback 1. Choose Configuration > Interface Management >

Microwave Interface from the Function Tree.
2. Select Loopback Attributes.
and set MAC Loopback.
Step 3 Click Apply.

Step 4 Click OK to close the dialog box.
Then, a dialog box is displayed.
----End
9.4.8 Setting Software Loopback for the NE

This task sets the loopback for the object on an NE.
Prerequisites

NCE
Precautions
NOTICE
is performed.
Function.
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
9.4.9 Setting Software Loopback for the Microwave Link

This task sets the loopback for the object on a single-hop radio link.
Prerequisites

NCE
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
9.4.10 Locating a Fault by Performing Loopback Operations

Loopback is a common method of locating the fault.
Prerequisites

NCE
Service Trail
Figure 9-29 shows how to locate a fault by performing a loopback operation.

Figure 9-29 Service trail
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
9.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.
● 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.
● PDH cable loopback indicates that the receive and transmit PDH cables are
connected through a short-circuiting cable or connector on the DDF.
● 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
● 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.
● Loopback operations on E-LAN services may cause network storms and service
interruptions.
9.6 Reset
Reset is an important method of troubleshooting software faults. Reset is
classified into cold reset, warm reset.
9.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

NCE

Precautions
NOTICE
● Cold reset causes service interruption because it is similar to the procedure of

removing and inserting a board.
● Do not configure a board that is being reset.
● Do not modify IF configurations when an ODU is being reset. Otherwise, the
configurations may be incorrect or do not take effect.
● The XMC-5D ODU can be cold reset only a whole, rather than on a per-channel
basis.
● 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 NCE, 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
9.6.2 Warm Reset

Warm reset is a process wherein the board software is reset but the board is not
re-initiated.
Prerequisites

NCE
Precautions
During warm reset, the board software is reset but the services are not
interrupted.

NOTICE
● When a board is reset, protocols running on the board may be interrupted.

● Do not configure a board that is being reset.
● 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 NCE, 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
9.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

NCE
Procedure
Step 1 Choose Configuration > Auto NE Function Disabling from the Main Menu.

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
9.8 Querying Site Information

You can query microwave site information and ODU information.
Prerequisites

NCE
Procedure
Step 1 Query the microwave site visualization information report.

Step 2 Query the ODU board information report.

----End
9.9 Querying Power Consumption of Boards

This section describes how to query power consumption of the ODU and each
board.
Prerequisites

NCE

Procedure
Step 1 Choose Configuration > NE Power 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

9.10 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

NCE
Procedure
Step 1 Query the optical power and alarm thresholds of SDH ports.
----End
9.11 Preventing Service Loops

You can enable the automatic service loopback detection function or the
automatic broadcast packet suppression function to prevent service loops.
9.11.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

NCE
Context
● Principle of E-LAN service loop detection: Special LD packets are sent (DA is a
special unicast packet, and SA indicates source MAC address. VLAN tags are
encapsulated based on the port that initiates the detection, and service
information is encapsulated into the payload of LD packets). The VLAN ID of
LD packets is the same as that of service packets, and the intermediate NE
may forward LD packets as service packets. If the NE receives the LD packets
sent by itself from the same VPN (the SVL bridge is determined according to
the DA and SA, and the IVL bridge is determined according to the DA, SA, and
VLAN), the system considers that a loop exists.
● Automatic loop detection is enabled by default upon service creation and the
port status change.
● If automatic loop detection is enabled upon service creation: service loop
detection will be automatically initiated on the first and last VLANs in the
VLAN list after a logical port is added to the E-LAN. If a loop is detected on
either of the two VLANs, the logical port is disabled. If new VLANs are added
on a logical port, service loop detection will be automatically initiated on the
first and last VLANs among the new VLANs. If a loop is detected on either of
the two VLANs, all the newly added VLANs are disabled.
● If automatic loop detection is enabled upon the port status change, service
loop detection will be automatically initiated on all logical ports on a physical
port after the physical port changes from down to up. If multiple VLANs are
accessed to a logical port, service loop detection will be initiated on any two
VLANs. If a loop is detected, the logical port is disabled and the
SRV_SHUTDOWN_LD alarm is reported.

Limitation and Impact

● After the function is enabled, loop detection will be initiated only when new services are
created or the physical port changes from down to up. If a loop occurs when neither of
the preceding conditions is met (such as a third-party network loop), it cannot be
detected automatically or disabled.
● If the LD packets sent by an NE are discarded during transmission (including but not
limited to link congestion, link bit error, transient link interruption, and board reset), the
service loop cannot be detected.
● If service loop detection is automatically initiated, after a loop is detected and the
service is disabled, the disabled service cannot be automatically enabled after the loop
is eliminated. The disabled service can only be enabled manually by the user. For details,
see Operation Procedure.
● After automatic service loop detection is enabled, an LD packet is sent every second. If a
loop is detected within three consecutive detection periods (a period of five seconds),
the system considers that a loop exists and the service is disabled. If no loop is detected
within three consecutive detection periods (a period of five seconds), the system
considers that no loop exists and the detection stops.
● Two VLANs on a logical port are randomly selected for automatic service loop detection.
When loops occur on some VLANs on the logical port: if no loop occurs on the selected
VLANs but loops occur on the other VLANs on the logical port, the loop cannot be
detected and the service cannot be disabled. If loops occur on the selected VLANs but
no loop occurs on the other VLANs on the logical port, the VLANs where no loop occurs
are disabled.
● When services are disabled, the NNI of the S-Aware bridge disables all NNIs on the
physical port where the NNI of the S-Aware bridge is configured, and the E-LAN services
of other types only disable the logical port where a loop is detected.
● For VPLSs in IVL mode, when no UNI is configured, the NNI does not support automatic
service loop detection.
● When a loop occurs in a network but no broadcast storm occurs, automatic loop
detection may cause services to be disabled.
Precautions
When a loop occurs in a network but no broadcast storm occurs, automatic loop
detection may cause services to be disabled. If this occurs in a live network,
disable the function of automatic loop detection on the NE and re-enable the
disabled service. After that, eliminate the loop and enable the function again.
Procedure
Step 1 In the NE Explorer, select an NE from the object tree. Choose Diagnosis &
Maintenance > E-LAN LD Test Management from the function tree.
Step 2 Select Auto or Disabled.

Step 3 Click Apply.
----End
Procedure for handling the service is shutdown

1. Synchronize NE alarms, and check whether the SRV_SHUTDOWN_LD alarm
occurs on the NE. If the alarm occurs, find the service that is disabled
according to alarm details.
a. If the VUNI is disabled, the format of alarm location information is
L2VPN(Service ID)_VUNI(VUNI ID)_Port. As shown in the following figure,
the alarm location information indicates that the VUNI on port 3 on
board 5 in E-LAN 2 on NEs (9–44042) is disabled.
2. In the NE Explorer located by the alarm information, select Configuration

Ethernet Service Management E-LAN Service from the function tree. Find
and select the E-LAN service according to the service ID reported by the
SRV_SHUTDOWN_LD alarm, and choose Manual Loop Detection.
3. Select UNI or NNI information, and click Service Status List. After the Service
Status List is displayed, check the service status. Enable indicates that the

service is not blocked, and Disable indicates that the service is blocked by
loop detection. Select the blocked service, and click Enable to re-enable the
service.
● Check the services before re-enabling the blocked services. If a loop exists, disrupt the
loop before re-enabling the blocked service.
● Service interruption persisting after the service is re-enabled indicates that a loop exists.
Delete the service and check the physical loop.
9.11.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

NCE
Context
Upon detection of MAC address flapping, an NE reports 10.2.82
ELAN_SMAC_FLAPPING alarms.

Precautions
● EG2D boards support the suppression of broadcast, unknown multicast, and unknown
unicast packets.
● EX1 boards support the suppression of broadcast, unknown multicast, and unknown
unicast packets.
● EG4/EG4P boards support the suppression of only broadcast packets.
● EM6T/EM6F/EM6TA/EM6FA boards support the suppression of only broadcast packets.
● IFU2/IFX2 boards support the suppression of broadcast, unknown multicast, and
unknown unicast packets.
● ISU2/ISX2 boards support the suppression of broadcast, unknown multicast, and
unknown unicast packets.
● ISV3 boards support the suppression of broadcast, unknown multicast, and unknown
unicast packets.
● ISM6 boards support the suppression of only broadcast packets.
● 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.
● 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.
● 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.
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.

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

NCE
Procedure
Step 1 Enable loop detection upon MAC address flapping.

----End
9.12 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

NCE
Procedure
Step 1 Select the desired NE from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > Board 1+1 Protection from the Function Tree.
Step 3 In 1+1 Protection List, select Cross-Connect Protection Pair.

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.
----End
9.13 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.
9.13.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
● Disconnect both ends of the fiber. Ensure that there is no laser light on the
fiber connectors.
● 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 9-30 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 9-31 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 9-32 Dragging the fiber tip slightly on the other cleaning area
Step 4 Release the lever to close the cleaning area.
----End
9.13.2 Cleaning Fiber Connectors by Using Lens Tissue

When there is no cartridge cleaners, use the lens tissue for cleaning fiber
connectors.
Prerequisites
● Disconnect both ends of the fiber. ensure that there is no laser light on the
fiber connectors.
● Inspect the fiber connector with a fiber microscope to ensure that the fiber
connectors are contaminated.

● Clean solvent
● Non-woven lens tissue
● 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.
● The fiber cleaning tissue or lint-free wipes can substitute the non-woven lens tissue.
● 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 9-33 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:
● First spray it into the air because the initial spray of condensation may
contain certain sediment.
● Ensure that the injector nozzle is as close as possible to (but does not touch)
the connector surface.
----End
9.13.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
● 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 9.3.1 Setting the
On/Off State of the Laser.
● Inspect the fiber adapter with a fiber microscope to ensure that the fiber
adapter is contaminated.

● Optical cleaning sticks
● Clean solvent
● 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.
● The medical cotton or long fiber cotton can substitute the optical cleaning stick.
● 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.
● 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:
● First spray the compressed gas into the air because the initial spray of
condensation gas may contain some sediment.
● Ensure that the injector nozzle is as close as possible to (but does not touch)
the inner surface of the connector.
----End

Maintenance Guide 10 Alarm Reference
10 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.
10.1 Alarm List (in Alphabetical Order)

The following table lists all the possible alarms generated by the OptiX RTN 980 in
alphabetical order.
10.2 Alarms and Handling Procedures
This chapter describes all the alarms on the OptiX RTN 980 in alphabetical order
and how to handle these alarms.
10.1 Alarm List (in Alphabetical Order)

The following table lists all the possible alarms generated by the OptiX RTN 980 in
alphabetical order.
Table 10-1 Alarm list
Alarm Name Description Alarm

Severity
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 Major

framing procedure (GFP) frames
ALM_IMA_LIF Frame delimitation is out-of-frame at Major

the local end of the IMA link.
ALM_IMA_LODS Differential delay of the IMA link Major

crosses the threshold.


Severity
ALM_IMA_RE_RX_UNUSA The IMA link on the opposite NE fails Minor

BLE in the receive direction.
ALM_IMA_RE_TX_UNUSA The IMA link on the opposite NE fails Minor

BLE in the transmit direction.
ALM_IMA_RFI Frame delimitation is out-of-frame at Major

the 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 Major

switching
APS_STATUS_INDI APS status indication Major
APS_MANUAL_STOP MS protocol stopped manually Minor
ARP_FAIL An Ethernet port fails to learn the Major

MAC address of the remote end
using the ARP.
ARP_MAC_MISMATCH The MAC address of the static ARP Major

entry is different from the actual
MAC address.
ARP_SPOOF An ARP spoofing attack. Major
ATMPW_UNKNOWNCELL The number of unknown ATM cells Major

_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 Minor

(B1)
B1_SD Signal degradation due to excessive Minor

regenerator section errors (B1)
B2_EXC Excessive multiplex section errors Major

(B2)

multiplex section errors (B2)
B3_EXC Excessive higher order path bit errors Major

(B3)
B3_EXC_VC3 Excessive B3 bit errors in a VC-3 path Major


Severity

higher order path bit errors (B3)
B3_SD_VC3 Signal degradation due to excessive Minor

VC-3 path (B3) bit errors
BAT1TEMP_SENSOR_FAIL The temperature sensor of battery Major

group 1 fails.
BAT2TEMP_SENSOR_FAIL The temperature sensor of battery Major

group 2 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 Minor

BIP errors
BOOTROM_BAD BOOTROM data check fails. Major
BRDCASTRATIO_OVER The ratio of broadcast traffic exceeds Major

the threshold.
BUS_ERR Bus errors Critical
CA_CFG_MISMATCH The CA group configurations are Critical

inconsistent.
CES_ACR_LOCK_ABN The locking function of CES ACR Minor

service clock is abnormal.
CES_APS_INDI Packet MSP protocol state indication Major
CES_APS_MANUAL_STOP The MSP protocol is disabled Minor

manually.
CES_JTROVR_EXC The amount of jitter buffer overflow Major

crosses the specified threshold.
CES_JTRUDR_EXC The amount of jitter buffer Major

underflow crosses the specified
threshold.
CES_K1_K2_M K1 and K2 mismatch Minor


Severity
CES_K2_M K2 mismatch Minor
CES_LOSPKT_EXC The number of lost packets crosses Major

the specified threshold in a time unit.
CES_MALPKT_EXC The number of deformed packets Major

crosses the specified threshold in a
time unit.
CES_MISORDERPKT_EXC The number of lost disordered Major

packets crosses the specified
threshold in a time unit.
CES_RDI Remote defect indication Minor
CES_STRAYPKT_EXC The number of error packets crosses Major

the specified threshold in a time unit.
CESPW_OPPOSITE_ACFAU The AC circuit on the opposite NE is Major

LT 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_DISABLED Writing/Reading the CF card is Major

disabled.
CHCS Correctable cell errors Minor
CLK_LOCK_FAIL Clock locking fails Major
CLK_NO_TRACE_MODE The clock source is not in locked Minor

mode.
COMBO_PORT_CFG_MIS A configuration mismatch occurs Critical

MATCH between cascade ports.
COMMUN_FAIL Inter-board communication fails. Major
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 Major

state.
DBMS_ERROR Errors in the processing of system Critical

databases


Severity
DBMS_PROTECT_MODE System databases in protection mode Critical
DB_UNSAVE Configuration persistency prohibited Critical
DCN_CHANNEL_BITERRO Bit errors occur in the DCN channel. Major

R
DCNCFG_NOT_COMMIT The configured DCN subnet ID has Minor

not been committed.
DCNLINK_OVER There is an excessive number of DCN Major

links.
DCNSIZE_OVER Oversized DCN network Major
DDN_LFA The frame alignment signal of Major

framed E1 services is lost.
DOWN_E1_AIS Alarm indication of 2 Mbit/s Minor

downstream signals
DEVICE_AUTH_FAIL Anti-theft verification fails on a Major

device.
DROPRATIO_OVER The number of lost packets due to Minor

port congestion crosses the
threshold.
E1_LOS Loss of 2 Mbit/s line signals Minor
ELAN_SMAC_FLAPPING The source MAC address learned by Major

an E-LAN service flaps.
ENERGY_CFG_MISMATCH NEs at both ends of a link have Minor

inconsistent energy control
configurations.
ENERGY_INPROCESS Energy control is ongoing on the link. Warning
ENVHUM_SENSOR_FAIL The ambient humidity sensor of the Major

cabinet fails.
ENVTEMP_SENSOR_FAIL The ambient temperature sensor of Major

the cabinet fails.
ENVTEMP1_SENSOR_FAIL The ambient temperature sensor 1 of Major

the cabinet fails.
ENVTEMP2_SENSOR_FAIL The ambient temperature sensor 2 of Major

the cabinet fails.
ERPS_IN_PROTECTION Indicates that a node on the EPRS Minor

ring is faulty.
ERPS_BLOCK ERPS_BLOCK Minor


Severity
ERPS_CFM_FAIL The MEP bound to an ERPS instance Major

fails.
ERPS_NOT_COMPLETE The ERPS configuration is Minor

incomplete.
ETH_APS_LOST Loss of APS frames Minor
ETH_APS_PATH_MISMAT The working and protection paths of Major

CH the APS protection group differ
between the two ends.
ETH_APS_SWITCH_FAIL Protection switching failure Minor
ETH_APS_TYPE_MISMATC Protection scheme mismatch Major

H
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 Minor

point (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 Major

end
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 Critical

is 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 Critical

port
ETHOAM_DISCOVER_FAIL Discovery failure is detected by point- Minor

to-point Ethernet OAM.
ETHOAM_RMT_CRIT_FAU Severe faults are detected by point- Minor

LT to-point Ethernet OAM at the remote
end.


Severity
ETHOAM_RMT_LOOP A remote loopback is detected by Minor

point-to-point Ethernet OAM.
ETHOAM_RMT_SD Remote Ethernet performance Minor

degradation is detected by point-to-
point Ethernet OAM.
ETHOAM_SELF_LOOP An MAC port loopback is detected by Major

point-to-point Ethernet OAM.
ETHOAM_VCG_SELF_LOO A VCTRUNK port loopback is Major

P detected by point-to-point Ethernet
OAM.
EX_ETHOAM_CC_LOS Loss of periodical continuity check Critical

packets
EX_ETHOAM_MPID_CNFL Conflict of maintenance point IDs Major

CT
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 Minor

table are all used
FLOW_OVER excess data traffic received by Minor

Ethernet ports
FLOW_EXC_LCS The traffic exceeds the maximum Minor

capacity allowed by the license.
GNE_CONNECT_FULL The number of gateway connections Minor

exceeds the threshold.
GPSMOD_INVALID The GPS module fails Major
GPSMOD_LOCK_FAIL The clock of the GPS module fails to Major

lock satellite signals
GSP_RSVP_NB_AUTH_ERR An RSVP neighbor authentication Major

error occurs.
GSP_RSVP_NB_DOWN An RSVP neighbor becomes Major

unreachable.
GSP_TNNL_DOWN A tunnel is interrupted. Major
HARD_BAD Hardware faults Critical


Severity
HARD_ERR Minor hardware faults Minor
HARD_NONSUPPORT Board hardware does not support a Major

certain function.
HP_CROSSTR Threshold-crossing performance Minor

event of the higher order path
HP_LOM Loss of multiframes in the higher Major

order path
HP_RDI Higher order path remote defect Minor

indication
HP_REI Higher order path remote error Warning

indication
HP_SLM Higher order path signal label Minor

mismatch
HP_TIM High order path trace identifier Minor

mismatch
HP_UNEQ Unequipped higher order path Minor
HPAD_CROSSTR Adaptation performance threshold- Minor

crossing of the higher order path
IF_CABLE_ABN The IF cable is faulty. Minor
IF_CABLE_OPEN IF cables are disconnected. Major
IF_INPWR_ABN The power supplied by an IF board to Major

an ODU is abnormal.
IF_MODE_UNSUPPORTED Preset IF working mode is not Major

supported.
IGSP_ENTRIES_EXC The number of IGMP Snooping Minor

multicast table entries exceeds its
upper threshold
IMA_GROUP_LE_DOWN The IMA group at the local end fails. Major
IMA_GROUP_RE_DOWN The IMA group at the remote end Major

fails.
IMA_TXCLK_MISMATCH The transmit clock modes at the two Minor

ends 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


Severity
INSUFFCNT_MEM_SPACE The memory file system space is Critical

insufficient.
INSUFFCNT_FLSH_SPACE The flash file system space is Critical

insufficient.
INTEMP_SENSOR_FAIL The air intake vent temperature Major

sensor of 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.
ISISADJACENCYCHANGE The status of an IS-IS neighbor Major

changes.
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_EXCEED The number of private network route Major

prefixes exceeds the threshold.
L3V_TRAP_VRF_DOWN All ports on a private network are Major

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

module on the board does not match
the type of the optical interface.


Severity
LASER_MOD_ERR_EX The type of the pluggable optical Major

module on the board does not match
LASER_MODULE_MISMAT The type of the pluggable optical Major

CH module on the board does not match
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 Major

in the grace period.
LCS_EXPIRED The license file has expired and its Critical

grace period has timed out.
LCS_FILE_NOT_EXIST An NE fails to detect the ESDP Critical

license file.
LCS_LIMITED The capacity of the configured Major

services exceeds the range permitted
by the license file.
LFA Out of frame state of E1 frames 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 Minor

Ethernet port.
LOOP_ALM A loopback occurs. Minor


Severity
LP_CROSSTR Performance threshold-crossing of Minor

the lower order path
LP_R_FIFO FIFO overflow on the receive side of Minor

LP_RDI Lower order path remote defect Minor

indication
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 Minor

indication
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 Minor

indication
LP_SLM Lower order path signal label Minor

mismatch
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 Minor

LP_TIM Lower order path trace identifier Minor

mismatch
LP_TIM_VC12 VC-12 path trace identifier mismatch Minor
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 Minor

at one end and dual-ended at the
other end.
LPT_AUTH_FAIL LPT authentication failure. Major
LPT_CFG_CLOSEPORT The LPT closes the access port of the Major

local NE.


Severity
LPT_INEFFECT LPT function failed Major
LPT_RFI Link state pass-through function fails Critical

at the remote end.
LSR_BCM_ALM Laser bias current crossing the Major

threshold
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 Major

layer crosses the threshold.
MAC_FCS_EXC The software detects that the Major

number of bit errors at the MAC
layer crosses the threshold.
MAC_FCS_SD Signal degrade bit errors at the MAC Major

layer 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
MPLS_PW_Excess Excessive trail termination source Warning

identifiers (TTSIs) are received on the
PW.
MPLS_PW_LCK The server layer (tunnel) of MPLS Major

PW 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 Major

identifiers (TTSIs) on the PW do not
match with the specified one.


Severity
MPLS_PW_MISMERGE The trail termination source Major

identifiers (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 Critical

correct 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 Major

packet in 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 Minor

layer
MPLS_TUNNEL_LOCV Loss of tunnel connectivity Major
MPLS_TUNNEL_MISMATC The trail termination source Major

H identifiers (TTSIs) on the tunnel do
not match with the specified one.
MPLS_TUNNEL_MISMERG The trail termination source Major

E identifiers (TTSIs) are mismerged on
the tunnel.
MPLS_TUNNEL_OAMFAIL The OAM protocol negotiation Minor

between 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


Severity
MPLS_TUNNEL_UNEXPME Unexpected MEG ID in the CCM Critical

G packet
MPLS_TUNNEL_UNEXPME Unexpected MEP ID in the CCM Major

P packet
MPLS_TUNNEL_UNEXPPE Unexpected period of the CCM Major

R packet
MPLS_TUNNEL_UNKNOW Unknown defects on the tunnel Major

N
MS_AIS Multiplex section alarm indication Major
MS_CROSSTR Multiplex section performance Minor

threshold-crossing
MS_RDI Multiplex section remote defect Minor

indication
MS_REI Multiplex section remote error Warning

indication
MSAD_CROSSTR Multiplex section adaptation Minor

performance 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 Minor

errors on radio links
MW_CFG_MISMATCH Configuration mismatch on radio Critical

links
MW_CONT_WAVE Continuous wave Minor
MW_E1_LOST Loss of E1 signals Major
MW_FEC_UNCOR Microwave frames have the errors Minor

that cannot be corrected by using the
forward error correction (FEC)
technology.
MW_LIM Label mismatch on radio links Major
MW_LINK_INTERFERENCE There is air interface interference on Warning

the microwave link.
MW_LOF Loss of microwave frames Critical


Severity
MW_RDI Remote defect indication on radio Minor

links
NE_DCN_MODE The device is working under DCN Major

mode.
NEIP_CONFUSION IP address is conflict Major
NESF_LOST The NE software is lost. Critical
NESOFT_MM The software in the main area is Major

different from that in the standby
area.
NO_BD_SOFT The board software is lost. Critical
NP1_MANUAL_STOP The N+1 protection protocol is Minor

stopped 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 Minor

fails.
OCD Out of cell delimitation Major
ODC_BATTERY_CURRENT Abnormal current of the storage Major

_ABN battery
ODC_BATTERY_PWRDOW The storage battery fails to supply Major

N power for the equipment.
ODC_DOOR_OPEN The door of an outdoor cabinet is Critical

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

power voltage.
ODC_SMOKE_OVER Smoke occurs in an outdoor cabinet. Critical
ODC_SURGE_PROTECTIO The surge protection function of the Critical

N_FAIL outdoor cabinet fails.


Severity
ODC_TEC_ALM The TEC air conditioning module in Major

the cabinet fails.
ODC_TEMP_ABN The ambient temperature of the Minor

cabinet or 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 Major

power is excessively high.
OUT_PWR_LOW Indicates that the output optical Major

power is excessively low.
OUT1TEMP_SENSOR_FAIL The air outlet temperature sensor of Major

the cabinet fails.
OUT2TEMP_SENSOR_FAIL The external recycling outlet Major

temperature 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_NOTMA Patch package mismatch due to Major

TCH system control board replacement
PATCH_MATCH_NO_STAR Board patch match does not start. Minor

T
PATCH_OP_TIMEOUT Patch package operation timeout Minor
PATCH_INIT_FAIL patch initialize failed Major
PATCH_PKGERR Abnormal patch package Minor
PG_LINK_FAIL Links of the 1+1 protection group Critical

fail.
PG_PRT_DEGRADED The working link or protection link of Major

the 1+1 protection group is faulty.
PING_ARP_MISMATCHL The MAC addresses in the static and Minor

dynamic ARP entries conflict with
each other.


Severity
PING_LOS Ping failure Minor
PLA_CFG_MISMATCH Inconsistent PLA configurations Critical
PLA_DOWN PLA group is faulty Major
PLA_MEMBER_DOWN_EX A member link of the PLA group is Minor

T faulty.
PLA_PKT_ERR Packet reassembly fails in the receive Major

direction.
PORTMODE_MISMATCH The working mode of the remote FE Minor

port does not match that of the local
FE port.
PORT_EXC_TRAFFIC The traffic is higher than the port Major

bandwidth threshold.
PORT_MODULE_OFFLINE The SFP module is offline. Major
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_TIME_ADJUST_OFF PTP time adjustment function is Minor

disabled
PTP_TIMESTAMP_ABN PTP time stamp abnormality Major
PW_DROPPKT_EXC The number of lost packets in a PW Warning

PW_NO_TRAFFIC The PW has no traffic. Critical
PWAPS_LOST Loss of APS frames Minor
PWAPS_PATH_MISMATCH The working and protection paths of Major

the APS protection group differ
between the two ends.
PWAPS_SWITCH_FAIL Protection switching failure Minor
PWAPS_TYPE_MISMATCH Protection scheme mismatch Major
PW_APS_DEGRADED The PW APS protection group is Major

degraded.


Severity
PW_APS_OUTAGE The PW APS protection group is Major

unavailable.
PWD_ENCRYPT_RISK The user password encryption mode Major

of an 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 Critical

frame on the receive line side
R_OOF The out-of-frame fault occurs on the Critical

receive line side.
RADIO_FADING_MARGIN_ Radio fading margin is insufficient. Minor

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_CRITICAL There are critical alarm inputs. Critical
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 Minor

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

insufficient.


Severity
RTC_FAIL The real-time clock (RTC) of the Major

system 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_LOOP_LD Ethernet service loop alarm Major
SRV_SHUTDOWN_LD Ethernet services are interrupted. Major
SSL_CERT_DAMAGED A user-customized SSL certificate file Critical

is damaged.
SSL_CERT_NOENC Certificate file of SSL is not encrypted Major
SSL_CERT_TO_EXPIRE A customized SSL certificate file is Critical

about to expire.
STORAGE_FAIL A memory failure occurs. Critical
STORM_CUR_QUENUM_O The number of alarms on an NE is Minor

VER only 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 Critical

OUT performed during software package
loading.
SWDL_AUTOMATCH_INH The automatic match function is Minor

disabled.
SWDL_BD_MATCH_FAIL The swdl_bd_match_fail is an alarm Minor

indicating that a board fails to match
the board software.
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 Warning

performed on the NE.


Severity
SWDL_NEPKGCHECK Certain files in the package stored in Critical

flash memory are lost.
SWDL_PKG_NOBDSOFT The software package does not Minor

contain 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 Minor

system control board is disabled.
SYSLOG_COMM_FAIL The communication between the NE Major

and 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
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 Minor

in the 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


Severity
TUNNEL_APS_DEGRADED The tunnel protection group Major

degrades.
TUNNEL_APS_OUTAGE The tunnel protection group is Major

unavailable
UHCS Uncorrectable cell errors Minor
UNIPTP_SRC_LOSS Unicast PTP clock source failure Major
UNIPTP_SRC_SWITCH Unicast PTP clock source switching Minor
UNIPTP_SRC_NEGO_FAIL Unicast PTP protocol negotiation Major

failure
UP_E1_AIS Alarm indication of 2 Mbit/s Minor

upstream signals
USB_FILE_UNSEC The USB flash drive used by the NE is Major

insecure.
USB_PROCESS_FAIL Data restoration from a USB flash Minor

drive fails
V5_VCAIS Bits 5-7 in the V5 byte of a VC-12 Major

path 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
VCAT_LOM_VC12 Loss of multiframe of VC-12 path Major

virtual concatenation
VCAT_LOM_VC3 The virtually concatenated Major

multiframes in 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


Severity
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
10.2 Alarms and Handling Procedures

This chapter describes all the alarms on the OptiX RTN 980 in alphabetical order
and how to handle these alarms.
10.2.1 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
Alarm Severity Alarm Type
Major Equipment alarm
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 ● 0x01: indicates that the phase-locked loop (PLL) is in holdover
or free-run mode.
● 0x02: indicates that the Sync timestamp remains unchanged
when the Precision Time Protocol (PTP) clock is synchronized.
● 0x03: indicates that the PDV on the transport network exceeds
the upper threshold.
● 0x04: indicates that the ACR algorithm is in the quick lockout
phase.
Impact on the System

When this alarm occurs, the clock of the downstream NE is abnormal.
Possible Causes
● Cause 1: The frequency deviation of the clock source or the delay of the
intermediate network exceeds the upper threshold.
● 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 11.2.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

10.2.2 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
● Cause 1: AES is enabled at only one end of the link or authentication codes
are different at the two ends of the link.
● 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 10.2.273 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

10.2.3 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
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
10.2.4 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
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2, Parameter Indicate the ID of the alarmed VCTRUNK. For example,
3 0x00 0x01 indicate that the alarm is reported in
VCTRUNK 1.

When this alarm occurs, services are interrupted.
Possible Causes
● Cause 1: Timeslot binding is different at the source and sink VCTRUNKs.
● Cause 2: The radio link performance degrades.
● 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

10.2.5 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
table.
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,
Parameter 3 0x00 0x01 indicate that the alarm is reported in
VCTRUNK 1.

Possible Causes
● Cause 1: Bit errors occur on certain links or certain links are faulty.
● 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
10.2.6 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
table.
Name Meaning
Parameter 1, Parameter 2 Indicate the ATM Trunk ID.

● 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.
● After this alarm is cleared, the affected IMA link becomes available.
Possible Causes
● Cause 1: The path that carries the IMA link reports the SDH alarms, such as
R_LOS, R_LOF, and MS_AIS.
● Cause 2: The IMA protocol negotiation fails between the two ends.
● 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
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 7.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.
10.2.7 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
table.
Name Meaning

The IMA links are unavailable.
Possible Causes
● Cause 1: The maximum differential delay is configured incorrectly.
● 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.
10.2.8 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
table.
Name Meaning

Possible Causes
Procedure
If... Then...

If... Then...

Board.
----End
Related Information
None
10.2.9 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
table.
Name Meaning

Possible Causes

Procedure
If... Then...
If... Then...

Board.
----End
Related Information
None
10.2.10 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
table.
Name Meaning

Possible Causes
Procedure
If... Then...
If... Then...

Board.
----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.
10.2.11 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 10-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.
AM mode shifts in the two microwave directions are independent of each other.
Figure 10-1 Process of reporting an AM_DOWNSHIFT alarm

Attribute
Parameters
None

When the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.
Possible Causes
● Cause 1: The external factors (for example, the climate) cause the
degradation of the working channels.
● Cause 2: There are interferences around the working channels.
● Cause 3: The ODU at the transmit end has abnormal transmit power.
● 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

10.2.12 APS_FAIL
Description
The APS_FAIL is an alarm indicating that the MS protection switching fails.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
● 0x01: linear MS protection

● 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
● Cause 1: The parameters of the MSP protocol are set incorrectly.
● 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 End the alarm handling.
is restarted
The alarm persists after the protocol is Contact Huawei engineers to
restarted handle the alarm.
----End
Related Information
None
10.2.13 APS_INDI
Description
The APS_INDI alarm indicates that MS protection switching occurs.
Attribute
Parameters
table.
Name Meaning
● 0x01: linear MS protection

● 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.
10.2.14 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped
manually.
Attribute
Minor Processing alarm

Parameters
table.
Name Meaning
● 0x01: linear MS protection.

● 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.
10.2.15 APS_STATUS_INDI
Description
The APS_STATUS_INDI alarm indicates that multiplex section protection (MSP)
switching occurs.

Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the type of a protection group.
● The 0x01 value indicates a linear MSP group.
● The 0x02 value indicates a ring MSP group.
Parameter 2 Indicate the ID of the protection group that reports the alarm.

This alarm does not affect services. Howerver, if the protection path becomes
faulty, services will be interrupted.
Possible Causes
The possible causes of this alarm are as follows:
● Cause 1: The R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that triggers
MSP swtiching is generated.
● Cause 2: An external switching command has been issued to the protection
group.
● Cause 3: The attributes of the MSP group are incorrectly configured.
● Cause 4: The MSP protocol is abnormal.
● Cause 5: The SCC board is faulty.
● Cause 6: A certain service board is faulty.
Procedure
Step 1 Cause 1: The R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that triggers MSP
swtiching is generated.
If... Then...
There is an R_LOS, R_LOF, MS_AIS, or Preferentially clear the R_LOS, R_LOF,

B2_EXC alarm. MS_AIS, or B2_EXC alarm.

If... Then...
There is a B2_SD alarm. Disable SD switching and then clear

the B2_SD alarm if SD switching is
enabled.
Step 2 Cause 2: An external switching command has been issued to the protection group.
1. Check whether the MSP group is in the manual, forced, or locked switching
state. If yes, release the switching and check whether the alarm is cleared.
Step 3 Cause 3: The attributes of the MSP group are incorrectly configured.
1. Issue the MSP configuration again. Then, check whether the alarm is cleared.
Step 4 Cause 4: The MSP protocol is abnormal.

1. Restart the MSP protocol. Then, check whether the alarm is cleared.
NOTICE
Restarting the MSP protocol will interrupt services. Exercise caution when
performing this operation.
Step 5 Cause 5: The SCC board is faulty.

1. Check whether the SCC board is faulty. If yes, replace it by following the
instructions provided in 7.11 Replacing the System Control, Switching and
Timing Board. Then, check whether the alarm is cleared.
NOTICE
Replacing the SCC board will interrupt services. Exercise caution when performing
this operation.
Step 6 Cause 6: A certain service board is faulty.

1. Check whether a service board is faulty. If yes, replace it by following the
instructions provided in 7.8 Replacing an IF Board. Then, check whether the
alarm is cleared.
NOTICE
Replacing the service board interrupts services. Exercise caution when performing
this operation.
----End
Related Information
None

10.2.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
● 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.
● 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
10.2.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
● Cause 1: The MAC address configuration is incorrect.
● 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
10.2.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
table.
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:
● A large number of CPU resources are occupied. As a result, the system is
unstable and the protocol status jitters.
● 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 technical support
engineers.
----End

Related Information
None
10.2.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
● Cause 1: PW control words mismatch.
● Cause 2: PW types mismatch.
● 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

10.2.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
● Cause 1: The opposite NE inserts the AU_AIS alarm.
● Cause 2: The transmit unit of the opposite NE is faulty.
● Cause 3: The receive unit of the local NE is faulty.
Procedure
1. Cause 1: The opposite NE inserts the AU_AIS alarm.
If... Then...
The alarm that triggers the AU_AIS Clear the alarm immediately.
insertion occurs
No such alarms that trigger the Go to Cause 2.

AU_AIS insertion occur
2. Cause 2: The transmit unit of the opposite NE is faulty.

a. Replace the line board at the opposite end.
If... Then...
The alarm is cleared after The fault is rectified. End the

replacement alarm handling.
The alarm persists after Go to the next step.

replacement

b. Replace the system control, cross-connect, and timing board at the

opposite end.
3. Cause 3: The receive unit of the local NE is faulty.
a. Replace the alarmed board.
Related Information
None
10.2.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
● Cause 1: The transmit unit of the opposite NE is faulty.
Procedure
1. Cause 1: The transmit unit of the opposite NE is faulty.
a. Replace the line board at the opposite end
If... Then...
The alarm is cleared after The fault is rectified. End the

replacement alarm handling.

If... Then...

replacement

opposite end.
Related Information
None
10.2.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
● Cause 1: The line performance degrades (if the alarm is reported by an SDH
optical interface board).
● Cause 2: The line performance degrades (if the alarm is reported by an IF
board).
● Cause 3: The network clock quality degrades.
● Cause 4: The board is faulty (if the alarm is reported by an SDH optical
interface board).

● Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
1. Cause 1: The line performance degrades (if the alarm is reported by an SDH
a. 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 5.2.3 Browsing Current Performance Events.
If... Then...
The transmit power of the Replace the SFP on the opposite

opposite NE is over low NE.
The transmit power of the The fiber is faulty. Go to the next

opposite NE is normal, but the step.
receive power of the local NE is
close to the value (for example,
within ±3 dB) of the receiver
sensitivity.
b. 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 is faulty. Go to the next
the fiber step.
The errors do not vary with the Ensure that the board is normal.
change of the fiber.
c. 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.
2. Cause 2: The line performance degrades (if the alarm is reported by an IF
board).
a. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or
RPS_INDI alarm is reported. If yes, clear the alarm.
3. Cause 3: The network clock quality degrades.
a. Check the network clock status of the alarmed NE.

If... Then...
The clock source of the local NE is The clock may become

different from the clock source of asynchronous and B1 errors may
the opposite NE occur. Reconfigure the clock
source, 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
clock of the opposite NE form a service interruption. In this case,
timing loop reconfigure the clock source and
release the timing loop.
4. Cause 4: The board is faulty (if the alarm is reported by an SDH optical
interface board).
a. 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
optical interfaces are looped back alarmed line unit is located on
the local NE.
The fault is rectified after the Replace the board where the
the opposite NE.
5. Cause 5: The board is faulty (if the alarm is reported by an IF board).

a. 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 the local NE.
back
The fault is rectified after the Replace the alarmed IF board on

multiplexing interface is looped the opposite NE.
back
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
Handle the errors of TDM services.

10.2.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
board).
interface board).
Procedure
If... Then...


If... Then...

sensitivity.
If... Then...
the fiber step.
board).
If... Then...

and opposite NE.
interface board).

If... Then...
the local NE.
the opposite NE.

local NE.
If... Then...
back

back
Related Information
10.2.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
board).
interface board).
Procedure
If... Then...


sensitivity.
If... Then...
the fiber step.
board).


If... Then...

and opposite NE.
interface board).
If... Then...
the local NE.
the opposite NE.

local NE.
If... Then...
back

back
Related Information

10.2.25 B2_SD
Description
errors (in 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 B2_EXC alarm threshold (10-3 by default).
Attribute
Minor Service alarm
Parameters
None

The service performance on the port degrades.
Possible Causes
board).
interface board).
Procedure
If... Then...


If... Then...

sensitivity.
If... Then...
the fiber step.
board).
If... Then...

and opposite NE.
interface board).

If... Then...
the local NE.
the opposite NE.

local NE.
If... Then...
back

back
Related Information
10.2.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
board).
interface board).
Procedure
If... Then...


sensitivity.
If... Then...
the fiber step.
board).


If... Then...

and opposite NE.
interface board).
If... Then...
the local NE.
the opposite NE.

local NE.
If... Then...
back

back
Related Information

10.2.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
table.
Name Meaning
Parameter 1 Has a fixed value of 0x01.
Parameter 2, Indicate the ID of the VC-3 path that reports the alarm.
Parameter 3 For 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
● Cause 1: Higher-level bit error alarms occur in the system.
● Cause 2: The line performance deteriorates (the alarm is reported by an
Ethernet optical port).
Ethernet electrical port).
● 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 Replace the optical
low module at the opposite
site.
The transmit power at the opposite site is A fiber is faulty. Go to the
normal, but the receive power at the local next step.
site is close to the 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...
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 Replace the Ethernet processing
Ethernet port is looped back board at the opposite site.
----End
Related Information
None
10.2.28 B3_SD
Description
errors (in 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 B3_EXC alarm threshold (10-3 by default).
Attribute
Minor Service alarm
Parameters
None

The service performance on the port degrades.
Possible Causes
board).
interface board).

Procedure
If... Then...


sensitivity.
If... Then...
the fiber step.
board).
If... Then...

and opposite NE.

If... Then...
interface board).
If... Then...
the local NE.
the opposite NE.

local NE.
If... Then...
back

back
Related Information
10.2.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
table.
Name Meaning
Parameter 2, Indicate the ID of the path that reports the alarm. For
Parameter 3 example, 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
● Cause 1: Higher-level bit error alarms occur in the system.
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.
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 Replace the optical
low module at the opposite
site.
The transmit power at the opposite site is A fiber is faulty. Go to the
normal, but the receive power at the local next step.
site is close to the 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
If... Then...
electrical port).
1. Check whether the cable grounding, cable connectors, and cables are
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 Replace the Ethernet processing
Ethernet port is looped back board at the opposite site.
----End

Related Information
None
10.2.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
● Cause 1: The temperature sensor of battery group 1 is faulty.
● Cause 2: The control board of the cabinet is faulty.
● Cause 3: Cables are misconnected or damaged.
● 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.
Step 2 Cause 2: The control board of the cabinet is faulty.

1. Replace the cabinet.
If... Then...

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
10.2.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
● Cause 1: The temperature sensor of battery group 2 is faulty.
● 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
10.2.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
table.

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
10.2.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:
● Cause 1 of the alarm reported by a board of the IDU: The board is installed in
an incorrect slot.

● Cause 2 of the alarm reported by a board of the IDU: The board and the
backplane are not connected properly.
● Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
● 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:
● Cause 1 of the alarm reported by the ODU: The other alarms are generated.
● Cause 2 of the alarm reported by the ODU: The ODU is faulty.
Procedure
1. Cause 1 of the alarm reported by a board of the IDU: The board is installed in
an incorrect slot.
a. Check whether the logical slot and physical slot of the alarmed board are
consistent. For details, see 5.1 Checking the Board Status.
If... Then...
The alarmed board is installed in Install the board in a correct slot.

an incorrect slot
The alarmed board is installed in a Ensure that the board and the
correct slot backplane are connected properly.
2. Cause 2 of the alarm reported by a board of the IDU: The board and the
backplane are not connected properly.
a. Remove and insert the alarmed board.
If... Then...
The alarm is cleared after the The fault is rectified. End the
board is removed and inserted alarm handling.
The alarm persists after the board Ensure that the board is normal.
is removed and inserted
3. Cause 3 of the alarm reported by a board of the IDU: The slot is

faulty.Contact Huawei technical support engineers to handle the fault of the
slot.
a. Contact Huawei technical support engineers to handle the fault of the
slot.
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.
b. If a vacant slot is available, insert the board in the vacant slot and add
the board again. Then, the board can work normally.
4. Cause 4 of the alarm reported by a board of the IDU: A certain board is faulty.

If... Then...
board is replaced alarm handling.
The alarm persists after the board Ensure that the slot is normal.
is replaced
5. Cause 1 of the alarm reported by the ODU: The other alarms are generated.
a. 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 Clear the alarm immediately.

preceding alarms
The IF board does not report any Replace the alarmed ODU.
of the preceding alarms
6. Cause 2 of the alarm reported by the ODU: The ODU is faulty.

a. Replace the alarmed ODU.
Related Information
None
10.2.34 BDTEMP_SENSOR_FAIL
Description
The BDTEMP_SENSOR_FAIL is an alarm indicating that the board temperature
Attribute

Parameters
None

The board temperature data of the TCU cannot be collected.

Possible Causes
● Cause 1: The board temperature sensor is faulty.
● 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
10.2.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
table.
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
● Cause 1: The BGP configurations change.

● 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
10.2.36 BIOS_STATUS
Description
The BIOS_STATUS alarm indicates that the alarmed board is in the BIOS state.
Attribute
Major Processing alarm
Parameters
table.
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
● Cause 1: The board software is lost.
● Cause 2: The board software becomes abnormal.
● 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.
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
10.2.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
● Cause 1: The line performance degrades (if the alarm is reported by an E1
service board).
● Cause 2: The line performance degrades (if the alarm is reported by a Hybrid
IF board).
● Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
● Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
1. Cause 1: The line performance degrades (if the alarm is reported by an E1
service board).
a. 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 Clear the alarm immediately.

alarms
No such alarms occur Ensure that the board is normal.
2. Cause 2: The line performance degrades (if the alarm is reported by a Hybrid
IF board).
a. Check whether any alarm occurs on the tributary board or IF board that
transmits the service signal. If yes, clear the alarm immediately.
3. Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
a. 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.
4. Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).

a. Replace the Hybrid IF board. Then, check whether the alarm is cleared.
If... Then...

Related Information
The alarm parameters have the meanings listed in Table 10-2 when EMS6 board
report the alarm.
Table 10-2 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.
10.2.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
● Cause 1: The line performance degrades (if the alarm is reported by an E1
service board).
● Cause 2: The line performance degrades (if the alarm is reported by a Hybrid
IF board).
● Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
● Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
1. Cause 1: The line performance degrades (if the alarm is reported by an E1
service board).
a. 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 Clear the alarm immediately.

alarms
No such alarms occur Ensure that the board is normal.
2. Cause 2: The line performance degrades (if the alarm is reported by a Hybrid
IF board).
a. Check whether any alarm occurs on the tributary board or IF board that
transmits the service signal. If yes, clear the alarm immediately.
3. Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
a. Replace the board where the E1 service unit is located. Then, check
If... Then...

4. Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
a. Replace the Hybrid IF board. Then, check whether the alarm is cleared.
If... Then...


Related Information
The alarm parameters have the meanings listed in Table 10-3 when EMS6 board
report the alarm.
Table 10-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.
10.2.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
table.
Name Meaning

Name Meaning
Parameter 2, Parameter 3 Indicates the type of the BOOTROM

damage.
● 0x00, 0x01: damage of the basic
BIOS
● 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.
● When the NE is already started, the BOOTROM_BAD alarm does not affect
the system and services.
● 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
● Cause 1: The basic BIOS is damaged.
● Cause 2: The extended BIOS is damaged.
● Cause 3: The BOOTROM database is damaged.
● Cause 4: The system control switch and timing board is faulty.
Procedure
Step 1 Replace the alarmed board.
----End
Related Information
None
10.2.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
table.
Name Meaning
Parameter 1 Indicates the service flow direction.
● 0x00: receive direction
● 0x01: transmit direction

When this alarm exists, a broadcast storm may occur.
Possible Causes
● Cause 1: A service loop is formed.
● Cause 2: The broadcast packet suppression threshold is improperly set in IPTV
scenarios.
● 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

10.2.41 BUS_ERR
Description
The BUS_ERR alarm indicates a bus fault or a data service exception on an NE.
Attribute
Table 10-4
Critical Equipment alarm
Parameters
table.

Name Meaning
Parameter 1 For a service board or a switching and

timing board, Parameter 1 indicates
the bus error type.
● 0x01: BUS_LOS
● 0x02: BUS_OOF
● 0x03: BUS_LOF
● 0x04: BUS_OOA
● 0x05: BUS_RX_DOWN
● 0x06: BUS_TX_DOWN
● 0x07: BUS_SPI_DOWN
● 0x08: BUS_SCI_ERR
● 0x09: BUS_OPP_CLK_LOC
● 0x0a: BUS_SERDS_ERR
● 0x0b: BUS_MII_ERR
● 0x0c: BUS_HW_ERR
● 0x0d: BUS_FE_ERR or anti-theft
verification failure on a device
● 0x0e: BUS_EMIF_ERR
● 0x0f: BUS_IIC_ERR
● 0x10: BUS_GE_LINK_ERR
● 0x11: BUS_EMIF
For a system control board:
● Parameter 1 is set to
0x32\0x33\0x30\0x31\0x34. For
details about the meanings of
Parameter 1, see Parameter 2.
● 0x0c: Indicates that the SCC board's
online/offline state detected by the
service board is consistent with the
actual online/offline state of the
SCC board.
● 0x11: Indicates that the link status
of the chip port is abnormal.
For CSHNU and CSHLU boards,
0x11 indicates the connection
status of the internal chip is
abnormal.
● 0x09: Indicates that the serdes of
the logical backplane port is
unlocked (only for CSHNA and
CSHL boards).

Name Meaning
● 0x0a: Indicates the link status of the

logical backplane port is abnormal
(only for CSHNA and CSHL boards).
For an IF board, meanings of
Parameter 1 are as follows:
● 0x00: Bus signals from the analog
to digital converter (ADC) to the
modem are abnormal in the
downlink direction.
● 0x01: Bus signals from the ADC to
the modem are abnormal in the
uplink direction.
● 0x02: Bus signals from the modem
to the ADC are abnormal in the
downlink direction.
● 0x03: IF signals from the backplane
are abnormal.
● 0x04: The phase-locked loop (PLL)
on a data service serial interface is
out of lock.
● 0x05: Decapsulation of data
services is abnormal in the
downlink direction.
● 0x06: Communication between the
master and slave boards in a PLA
group is abnormal.
● 0x07: The packet segment sequence
numbers of the master and slave
PLA boards do not match.
● 0x08: Services on a PLA member
are abnormal.
● 0x09: The Telecom bus detects B2
bit errors.
● 0x0a: The MIMO Serdes backplane
bus is abnormal.
● 0x0b: The logic is abnormal.
● 0x0c: The Telecom bus from the
active system control board to the
board is faulty.

Name Meaning
Parameter 2 For a service board,

When Parameter 1 is set to a value
that falls within the range from 0x01
to 0x11, Parameter 2 indicates 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.
the system frame header signal
transmitted between the active and
standby system control boards is
lost.
the TELECOM or LVDS bus between
the system control board and
service board is faulty.
● Parameter 1 is 0x33 and Parameter
2 is set to the board ID:
– When Parameter 3 is 0x1, the
cross-connection bus between
the Telecom bus and the service
board is faulty in the uplink
direction.
cross-connection bus between
the Telecom bus and the service
board is faulty in the downlink
direction.
● When Parameter 1 is 0x34, the BID
SMB bus is faulty.
● Parameter 1 is set to 0x0c:
– If Parameter 2 is set to 0x3/0x4,
the actual online/offline state of
SCC board A/B is inconsistent
with the SCC board A/B's online/
offline state detected by the
service board.
the actual active/standby state
of SCC board A/B is inconsistent
with the SCC board A/B's active/
standby state detected by the
service board

Name Meaning

the actual working status of SCC
board A/B is inconsistent with
the SCC board A/B's working
status detected by the service
board.
NOTE
SCC A is inserted in the slot with a
smaller slot ID, and SCC B is inserted in
the slot with a larger slot ID.
For an IF board,
● Parameter 1 is 0x05:
– When Parameter 2 is 0x01,
decapsulation of data services on
port 1 is abnormal in the
downlink direction.
decapsulation of data services on
port 2 is abnormal in the
downlink direction.
services on port 1 in the PLA
group are abnormal.
services on port 2 in the PLA
group are abnormal.
Telecom bus is faulty in the
downstream direction (only for
ISM8 boards).
– When Parameter 2 is 0x03, B2
bit errors occur in the
downstream of the first VC-4 in
the telecom bus.
– When Parameter 2 is 0x04, B2
bit errors occur in the
downstream of the second VC-4
in the telecom bus.
● Parameter 1 is 0x0b:
board FPGA is abnormal, causing
the packet end flag to be
abnormal.

Name Meaning

board FPGA is abnormal, causing
no data output from the header
compression module.
– Parameter 2 is 0x04, an
upstream packet modification
error occurs.
upstream GFP decapsulation
asynchronization occurs.
– When Parameter 2 is 0x06, an
upstream MVB1 bit error occurs.
– When Parameter 2 is 0x07, DCC
loss occurs.
● Parameter 1 is 0x0a:
MIMO serdes backplane bus on
port 1 is abnormal.
MIMO serdes backplane bus on
port 2 is abnormal.
Parameter 3, Parameter 4 Indicates the service board ID.

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:
● Cause 1: The board is not properly inserted.

● Cause 2: Service configurations or basic configurations (such as the number of
E1 services) on an IF board are incorrect.
● Cause 3: A certain board is faulty.
● Cause 4: A board that has the anti-theft verification function enabled is
inserted into an NE that does not support this function.
● Cause 5: The NE backplane is faulty.
● Cause 6: The board of the peer NE is faulty.
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 MW_CFG_MISMATCH alarm on IF
boards). If any alarms indicating incorrect service configurations or basic
configurations are reported, clear them.
3.
Step 3 Cause 3: A certain board is faulty.
1. Perform a cold reset on the alarmed board. Then, check whether the alarm is
cleared.
If... Then...
Yes The fault has been rectified, and no

further action is required.
No Replace the board.
4.
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. On the NMS, query the board that reports the BUS_ERR alarm, 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.
Step 5 Cause 5: The NE backplane is faulty.
1. On the NMS, query the board that reports the BUS_ERR alarm, and remove
the board from the NE or reset the board. If the alarm persists, go to Step
5.2.
2. Replace the chassis backplane by following instructions in Part Replacement.
Step 6 Cause 6: The board of the peer NE is faulty.
1. Perform a cold reset on the board. For details, see Cold Reset.
2. Replace the faulty board. For details, see Part Replacement.
Step 7 Check whether the BUS_ERR alarm is cleared. If the alarm persists, contact Huawei
----End

Related Information
The alarm parameters have the meanings listed in Table 1 when the EMS6 board
reports the alarm.
Table 10-5 Alarm parameters of EMS6

Name Meaning
Parameter 1 Indicates the bus error type.

0x10: The Serdes bus of the GE bridge
is faulty.
10.2.42 CA_CFG_MISMATCH
Description
The CA_CFG_MISMATCH alarm indicates that the CA group configurations are
inconsistent.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the CA group ID of an NE.

Name Meaning
Parameter 2 ● 0x01: The information

configurations of the CA group are
inconsistent.
● 0x02: The bandwidth configurations
of the CA group are inconsistent.
● 0x03: The modulation schemes of
the CA groups are inconsistent.
● 0x04: The transmit frequencies of
the CA groups are inconsistent.
● 0x05: The T/R spacings of the CA
group are inconsistent.
● 0x06: The transmit power of the CA
group is inconsistent.
● 0x07: The maximum transmit
power of the CA group is
inconsistent.
● 0x08:The ATPC enabling status of
the CA group is different.
● 0x09: The ATPC thresholds of the
CA group are inconsistent.
● 0x0a: The ATPC enabling status of
the CA group is inconsistent.
● 0x0b: The mute status of the CA
group is inconsistent.
Parameter 3 ● 0x01: The configurations of CA

members are inconsistent.
● 0x02: The CA group configurations
of two NEs are inconsistent.

The microwave link is unavailable.
Possible Causes
● Cause 1: The configurations of members in the CA group are inconsistent.
● Cause 2: The CA group configurations of two cascaded NEs are inconsistent.
Procedure
1. Cause 1: The configurations of members in the CA group are inconsistent.
a. Check whether the configurations of members in the CA group are
consistent.

If... Then...
Yes Go to 2.
No Modify the inconsistent

configurations, For details, see CA
User Guide.
b. Check whether the CA_CFG_MISMATCH alarm is cleared. If the alarm

persists, go to 2.
2. Cause 2: The CA group configurations of two cascaded NEs are inconsistent.
a. Check whether the configurations of the cascaded NEs are consistent.
If... Then...
Yes Go to b.
No Modify the inconsistent

configurations, For details, see CA
User Guide.
b. Check whether the CA_CFG_MISMATCH alarm is cleared. If the alarm

persists, contact Huawei technical support engineers.
Related Information
None
10.2.43 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
table.

Name Meaning
Parameter 1 to Parameter 4 Indicate the index of PW that carries

the services associated with the ACR
clock source.
Parameter 5 Indicates clock mode.

● 0x01: tracing mode.
● 0x02: holdover mode.
● 0x03: free-run mode.
Parameter 6 Indicates whether the clock is locked.

● 0x00: unlocked.
● 0x01: locked.

Service quality is affected.
Possible Causes
● Cause 1: CES ACR services are unavailable or have alarms.
● Cause 2: The network is unstable.
● 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 5.2.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 5.2.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 5.2.1
Browsing Current Alarms.
2. Handle the alarms. For details, see 10.2 Alarms and Handling Procedures.
----End
Related Information
None

10.2.44 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
table.
Name Meaning
Parameter 1 Indicates the ID of the MSP protection group.

● 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.
● This alarm does not affect the services. If the protection channel fails at this
time, the services are interrupted.
Possible Causes
● Cause 1: An external command is issued to trigger switching (such as manual
switching, forced switching, exercise switching, and lockout of switching).
● 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.
● Cause 3: The attributes of the MSP protection group are incorrectly
configured.
● 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 whether the alarm is cleared. If the
exercise switching alarm persists, go to Step 2.
The MSP is not in any of the Go to Step 2.

preceding 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
R_LOS, R_LOF, MS_AIS, or switching state, and the CES_APS_INDI alarm is
B2_EXC alarm reported. Clear 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
B2_SD alarm whether the CES_APS_INDI alarm is cleared. If
the alarm persists, go to the next step.
The interface board is in After the cold resetting ends, go to step 3 and
the cold resetting state identify the cause of the cold resetting.
The MSP is not in any of Go to the next step.

the 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
is set to automatically switched from the protection channel to the
Revertive working channel once 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
is set to Non- to the working channel after the working channel
Revertive recovers, and the 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 7 Part Replacement.
----End
Related Information
None
10.2.45 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


table.
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
10.2.46 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
● Cause 1: The size of buffer area is set to a low value.
● 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
10.2.47 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
● Cause 1: Signals degrade on the link.
● Cause 2: The PSN network clocks used for the transmission of CES services are
not synchronized.
● Cause 3: The link is looped.
● Cause 4: The link is congested.
● 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 6.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
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
10.2.48 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
● 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.
3. If the alarm persists, replace the interface board. For details, see 7.11
Replacing the System Control, Switching and Timing Board.
----End
Related Information
None

10.2.49 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
● 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.
3. If the alarm persists, replace the interface board. For details, see 7.11
----End

Related Information
None
10.2.50 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
data.
----End
Related Information
Packets are lost when the sequence numbers of received packets are greater than
expected.

10.2.51 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
Possible Causes
● Cause 1: The RTP head enabling status is different between the two ends of
the PW.
● 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.

10.2.52 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 6.3 Troubleshooting the Radio Link.


data.
----End
Related Information
Packets are disordered when the sequence numbers of received packets are
smaller than expected.

10.2.53 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 6.3 Troubleshooting the Radio Link.


data.
----End
Related Information
None

10.2.54 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
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.
10.2.55 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
10.2.56 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
10.2.57 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
● Cause 1: The CF card fails to be initialized.
● Cause 2: The file system of the CF card does not match.
● 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
10.2.58 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
table.

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.
● 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.
10.2.59 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
● Cause 1: The CF card is not inserted.
● Cause 2: The CF card is in poor contact with the system control and
● Cause 3: The CF card is faulty.
● 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
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
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
2. If yes, perform a cold reset on the system control and communication board.
Then, check whether the alarm is cleared.
3. If the alarm persists, replace the system control and communication board.
----End
Related Information
None
10.2.60 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.
10.2.61 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
● Cause 1: A few bit errors occur in the receive tunnel corresponding to the
alarmed ATM port.
● 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
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 9.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 7.6 Replacing
the Smart E1 Interface Board.

Board replacement is not recommended because the alarm does not affect the
services.
----End
Related Information
None
10.2.62 CLK_LOCK_FAIL
Description
The CLK_LOCK_FAIL is an alarm indicating a clock locking failure.
Attribute
Parameters
table.
Name Meaning
Parameter 1 ● 0x01: indicates that the phase-

locked loop (PLL) is in holdover or
free-run mode.
● 0x02: indicates that the timestamp
in the Sync message remains the
same in Precision Time Protocol
(PTP) synchronization mode.
● 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
● Cause 1: Frequency deviation of the clock source has crossed the upper
threshold in physical synchronization mode.
● Cause 2: The physical link where the clock source resides is faulty in physical
synchronization mode.
● Cause 3: Frequency deviation of the clock source has crossed the upper
threshold in IEEE 1588v2 synchronization mode.
● Cause 4: The physical link where the clock source resides is faulty in IEEE
1588v2 synchronization mode.
Procedure
1. Cause 1: Frequency deviation of the clock source has crossed the upper
threshold in physical synchronization mode.
a. Check whether high-level bit error alarms or performance events have
been reported on the NMS. If yes, handle them immediately.
b. 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.
c. 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.
2. Cause 2: The physical link where the clock source resides is faulty in physical
synchronization mode.
a. If there is an external clock source, check whether the NE reports the
SYNC_C_LOS alarm. If yes, clear the alarm immediately.
b. If the CLK_LOCK_FAIL alarm persists, 7.11 Replacing the System
Control, Switching and Timing Board.
3. Cause 3: Frequency deviation of the clock source has crossed the upper
threshold in IEEE 1588v2 synchronization mode.
a. Check whether high-level bit error alarms or performance events have
been reported on the NMS. If yes, handle them immediately.
b. 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.
4. Cause 4: The physical link where the clock source resides is faulty in IEEE
1588v2 synchronization mode.
a. If the SYN_BAD alarm exists, clear the alarm immediately.
b. If the alarm persists, contact Huawei technical support engineers to
handle the alarm.
Related Information
None

10.2.63 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
table.
Name Meaning
Parameter 1 Indicates the clock mode.

● 0x01: holdover
● 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
● Cause 1: The system clock source priority table is not configured.
● Cause 2: All the clock sources in the clock source priority table fail.
Procedure
1. Cause 1: The system clock source priority table is not configured.
a. Configure the system clock source priority table. For details, see
Configuring the Clock Sources.
2. Cause 2: All the clock sources in the clock source priority table fail.

a. 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 Handle the alarm that occurs on

line clock the line board.
The synchronization source is an Handle the alarm that occurs on

IF clock the IF board.

tributary clock the tributary board.

Ethernet clock the Ethernet board.
Related Information
None
10.2.64 COMBO_PORT_CFG_MISMATCH
Description
The COMBO_PORT_CFG_MISMATCH alarm indicates a configuration mismatch
between cascade ports. This alarm is reported when a cascade port is configured
in a workgroup (for example, a CA group) but its connected cascade port is not in
the workgroup.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the type of the cascade port.

● 0x01: XPIC cascade port
● 0x02: CA cascade port
Parameter 2 Indicates the slot ID of the IF board

providing the cascade port at one end.
Parameter 3 Indicates the slot ID of the IF board

providing the cascade port at the other
end.

The microwave link is unavailable.
Possible Causes
The cable connection over the cascade ports is inconsistent with the NE
configuration.
Procedure
1. Check whether the cable connection over the cascade ports is consistent with
the NE configuration.
If... Then...
It is consistent The alarm is incorrectly reported,

and no further action is required.
It is inconsistent Connect the cable according to the

slot IDs of the boards in the inter-
board workgroup.
Related Information
None
10.2.65 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
table.
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

Parameter 3 generated. Parameter 2 is always 0x00. Parameter 3 has
the following meanings:
0x03: inter-board Ethernet communication
Parameter 4, Parameters 4 and 5 are reserved, and their values are

Parameter 5 always 0xFF.

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
● Cause 1: A certain board is reset.
● Cause 2: A board and the backplane are connected improperly.
● Cause 4: A slot is faulty.
● Cause 5: When the active and standby system control boards switch over,
communication between them are interrupted transiently.
Procedure
1. Cause 1: A certain board is reset.
a. After you reset the board, the alarm is cleared automatically.
2. Cause 2: A board and the backplane are connected improperly.

a. Remove and insert the alarmed board. For details, see 7.1 Removing a
Board and 7.2 Inserting a Board. Then, check whether the alarm is
cleared.
If... Then...
board is removed and inserted alarm handling.
The alarm persists after the board Clear the alarm according to the
is replaced. solution for the alarm that is
generated when a board is faulty.
3. Cause 3: The alarmed board is faulty.

a. Replace the alarmed board, and then check whether the alarm is cleared.
For details, see 7 Part Replacement.
If... Then...
The alarm persists after the board Clear the alarm according to the
is replaced solution for the alarm that is
generated when a slot is faulty.
4. Cause 3: A slot is faulty.

a. Contact Huawei technical support engineers to handle the faulty slot.
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.
b. 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.
5. Cause 5: When the active and standby system control boards switch over,
communication between them are interrupted transiently.
a. It is normal that this alarm is reported during the switchover, so this
alarm does not need to be handled.
Related Information
None
10.2.66 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
table.
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
10.2.67 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
Table 10-6
Major Equipment Alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates that the configuration data

does not meet the requirements.
● 0x01: The frequency is set
incorrectly.
● 0x02: The T/R spacing is set
incorrectly.
● 0x03: The transmit power is set
incorrectly.
● 0x04: The ATPC threshold is set
incorrectly.
● 0x05: The bandwidth is set
incorrectly.
● 0x06: The modulation mode is set
incorrectly.
● 0x0a: The frequency configuration
does not meet the frequency range
corresponding to the T/R spacing.
● 0x0c: The ATPC 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
● Cause 1: The type and configuration parameters of the ODU do not match
the requirements.

● Cause 2: The AM parameters are incorrectly changed. (This cause can be

verified only when Parameter 1 is 0x03.)
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 is 0x01–0x03. Go to Step 1.2.
The alarm parameter is 0x04–0x06. Go to 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 network .

planning and design requirements. Use the ODU with a correct model.
The parameter does not meet the .

network planning and design Modify the ODU port parameters.
requirements.
3. Check whether the parameters of the IF port meet the network planning
requirements. For details, see Configuring a Single-Hop Radio Link.
If... Then...
The parameter meets the network Replace the IF board.

planning and design requirements.
The parameters does not meet the Configuring a Single-Hop Radio

network planning and design Link.
requirements.
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 configured transmit power does not exceed the maximum rated
power of the ODU in AM guaranteed capacity mode.
If... Then...
The preceding conditions are met .

and the transmit power needs to Cold reset the alarmed ODU.
be adjusted.
The preceding conditions are met, , modify the ODU port

and it is not necessary to adjust parameters, and change the
the transmit power. transit power to the original value.
----End
Related Information
None
10.2.68 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
● 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.
● 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
10.2.69 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
● Cause 1: A database is deleted.

Procedure
Step 1 Follow instructions in 8.4 Restoring the Database by NMS to restore the
database.
----End
Related Information
None
10.2.70 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
table.

Name Meaning
Parameter 1 Indicates the error code.

● 0x00: The NE is running properly.
● 0x01: The database is being
checked.
● 0x02: The database is undergoing a
periodical backup.
● 0x04: The system is faulty.
● 0x08: Data on the active system
control board and that on the
standby system control board are
inconsistent.
● 0x10: Incremental data fails to be
backed up.
backed up to the NVRAM.
backed up to the flash memory.
Parameter 2 Indicates the storage area of the

database.
● 0x00: OFS1
● 0x01: OFS2
● 0x02: DRDB storage area
● 0x03: MDB storage area
● 0x04: TDRDB storage area
● 0x05: CF storage area
● 0x06: shared storage area
● 0x0C: NVRAM storage area
Parameter 3 Indicates the database ID.

● 0x00: all storage areas
● 0x01 to 0xFF: database in which the
error occurs

Name Meaning
Parameter 4 Indicates the error type.

● When Parameter 1 is 0x01, a
storage area check error occurs.
– 0x01: An error occurs when a list
file is generated in the storage
area.
– 0x02: An error occurs in
database file verification.
– 0x04: The database record
header is incorrect.
● When Parameter 1 is 0x02, a
periodic backup error occurs.
– 0x01: The flash memory space is
insufficient, resulting in a
database persistence failure.
– 0x02: Syserr check for a database
fails.
● When Parameter 1 is 0x10,
incremental data recycling or
backup fails.
– 0x02: Syserr check for a database
fails.
incremental data fails to be written
into NVRAM.
– 0x01: The NVRAM is exhausted.
– 0x02: Data headers saved in the
NVRAM are abnormal.
incremental backup on small files
fails.
– 0x01: The file system in the flash
memory fails to generate small
files.
Parameter 5 Reserved fields

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
1. Obtain NE backup data (backed up periodically by the NCE or backed up
manually) or NE service configuration information.
2. Contact Huawei technical support engineers for handling the alarm.
3. In case of emergency, 7.11 Replacing the System Control, Switching and
Timing Board and restore the database or reconfigure service data.
Related Information
None
10.2.71 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. 7.11 Replacing the System Control, Switching and Timing Board.
----End
Related Information
None
10.2.72 DB_UNSAVE
Description
The DB_UNSAVE alarm indicates that new configurations are not allowed to be
saved to the database on the SCC board. This alarm is reported when a
configuration is added to the database in scenarios where configurations are not
allowed.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates that new configurations are not allowed to be saved to

the database.
● New configurations cannot be saved when the database is in the
package loading state.

New configurations cannot be saved to the database.
Possible Causes
From the package loading activation state to commit end state, if the set-
forbidswitch command is issued to enable the configuration switch and a
configuration change is detected, this alarm will be reported. After the
configuration is successfully committed, the alarm will be cleared.
Procedure
Step 1 The software is in the package loading upgrade state. You need to submit the
software.
Step 2 If the alarm persists, contact Huawei engineers for help.
----End

Related Information
From the package loading activation state to commit end state, if the set-
forbidswitch command is issued to enable the configuration switch and a
configuration change is detected, this alarm will be reported. After the
configuration is successfully committed, the alarm will be cleared.
10.2.73 DCN_CHANNEL_BITERROR
Description
The DCN_CHANNEL_BITERROR alarm indicates that bit errors occur in the
outband DCN channel.
Attribute
Parameters
table.
Name Meaning
Parameters 1–2 Indicate the slot ID of a board associated with the outband DCN
channel.
Parameters 3–4 Indicate the subboard ID of a board associated with the

outband DCN channel.
Parameters 5–6 Indicate the port of a board associated with the outband DCN
channel.
Parameter 7 Indicates the type of the outband DCN channel.
Parameter 8 ● 0x01: Indicates a protocol-layer fault.

● 0x02: Indicates a physical-layer fault.
● 0x03: Indicates that the sending queue of the DCN channel
overflows.

This alarm does not affect services. It may interrupt the outband DCN
communication of the corresponding port.

Possible Causes
Possible causes of this alarm are as follows:
● Cause 1: The outband DCN link is faulty.
● Cause 2: The system control board or a service board is faulty.
● Cause 3: There are excessive network packets on the DCN channel.
Procedure
Step 1 Cause 1: The outband DCN link is faulty.
1. Check whether the outband DCN link at the local end is faulty.
a. Use the alarm parameters to determine the port for which this alarm is
generated.
b. Check whether the optical power of the port falls within the normal
range. If not, adjust the optical power. For details about the optical power
specifications, see 9.10 Querying Optical Power and Alarm Thresholds
of SDH Ports.
c. Check whether the fiber connected to the port is faulty. If the fiber is
faulty, replace it.
d. Check whether the optical module connected to the port is faulty. If the
optical module is faulty, replace it. For details, see 7.15 Replacing the
SFP.
2. Check whether the outband DCN link at the peer end is faulty.
The steps are the same as those in Step 1.1.
Step 2 Cause 2: The system control board or a service board is faulty.

1. Check whether the system control board or a service board at the local end is
faulty.
a. If the active and standby system control boards are configured, perform
an active/standby switchover.
If only the active system control board is configured, cold reset the system
control board. This operation may interrupt services.
b. Check whether the alarm is cleared. If the alarm persists, cold reset the
board. For details, see 9.6.1 Cold Reset.
NOTICE
The operation interrupts services.
c. Check whether the alarm is cleared. If the alarm persists, replace the
board. For details, see 7 Part Replacement.
2. Check whether the system control board or a service board at the peer end is
faulty.
The steps are the same as those in Step 2.1.
Step 3 Cause 3: There are excessive network packets on the DCN channel.

1. Check whether the DCNSIZE_OVER alarm is reported. If yes, preferrentially

clear it. For details, see DCNSIZE_OVER.
2. Check whether some alarms or events are frequently reported on the NE. If
yes, preferentially clear them.
Step 4 Check whether the DCN_CHANNEL_BITERROR alarm is cleared. If the alarm

persists, contact Huawei technical support engineers.
----End
Related Information
The NMS displays only one such alarm when multiple DCN_CHANNEL_BITERROR
alarms are reported for the same NE. The extended alarm parameter indicates the
DCN_CHANNEL_BITERROR alarm that is the most recently reported. You can check
Alarm Log to view information about all the DCN_CHANNEL_BITERROR alarms
reported for the NE.
10.2.74 DCNCFG_NOT_COMMIT
Description
The DCNCFG_NOT_COMMIT alarm indicates that the DCN subnet ID is not
submitted within one hour after being configured.
Attribute
Parameters
None

None
Possible Causes
Cause 1: The DCN subnet ID is not submitted within one hour after being
configured.
Procedure
Step 1 Cause 1: The DCN subnet ID is not submitted within one hour after being
configured.
1. Submit the configured DCN subnet ID. After the submitting, the alarm is
automatically cleared.

2. Check whether the alarm is cleared. If the alarm persists, restore the DCN
subnet ID to the original value.
technical support engineers.
----End
Related Information
None
10.2.75 DCNLINK_OVER
Description
The DCNLINK_OVER alarm indicates that the number of links on a DCN exceeds
the recommended value.
Attribute
Parameters
table.
Name Meaning
Parameter 1 ● 0x01: The total number of OSPF neighbors on the DCN exceeds
the recommended value.
● 0x02: The total number of OSPF neighbors to the same peer NE
on the DCN exceeds the recommended value.

When the alarm occurs, the system performance may be affected. As a result, the
NE generating this alarm or its neighboring NEs may fail to be managed.
Possible Causes
● Cause 1: The total number of OSPF neighbors on the DCN exceeds the
recommended value.
● 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
10.2.76 DCNSIZE_OVER
Description
The DCNSIZE_OVER is an alarm indicating an over-sized DCN network.
Attribute
Parameters
table.
Name Meaning
Parameter 1, Parameter 2 If these parameters are 0xFF 0xFF, the

NE works in L2DCN mode. Otherwise,
these parameters indicate the current
size of the DCN subnet.
Parameters 1–5 If these parameters are 0xFFFFFFFFFF,

the NE works in L2DCN mode. In other
cases, the first four bytes indicate the
DCN network scale, and the fifth byte
is reserved for future use.

● Some NEs become unreachable to the NMS because DCN packets cannot be
forwarded timely due to insufficient CPU resources.

● 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
Related Information
None
10.2.77 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
● Cause 1: The interconnected user equipment is faulty.
● Cause 2: The service frame format is configured incorrectly.
● 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).
10.2.78 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
● Cause 1: The opposite NE transmits the E1_AIS alarm.
● Cause 2: An upstream alarm triggers this alarm.
● 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 Clear the alarm immediately.
UP_E1_AIS or T_ALOS alarm
The opposite NE does not report the Ensure that the board on the local
UP_E1_AIS or T_ALOS alarm NE 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, and MW_LIM .
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,
If... Then...
The alarm is cleared The fault is rectified. End the alarm handling.
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
10-7.
Table 10-7 Alarm Parameters of EFP8

Name Meaning
Parameter 1 0x01, indicates optical interface

number.
Parameter 2, Parameter 3 Indicates the number of the path.
10.2.79 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
See anti-theft information, please refer to Configuring NE Anti-Theftand Querying
the Anti-Theft Status of Boards.
10.2.80 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
table.
Name Meaning
Parameter 1 Indicates the direction in which traffic

● 0x00: The ratio of lost packets in
the receive direction exceeds the
threshold.
● 0x01: The ratio of lost packets in
the transmit direction exceeds the
threshold.

Service packet loss occurs.
Possible Causes
● Cause 1: Service configuration is incorrect.
● Cause 2: Actual traffic exceeds the configured port bandwidth or committed
information rate (CIR).
● Cause 3: In PLA/EPLA/EPLA+ IF protection scenarios, packets are continuously
sent in the transmit direction when all protection members are in the link-
down state.
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 committed
information rate (CIR).
1. 5.5.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.
Step 3 Cause 3: In PLA/EPLA/EPLA+ IF protection scenarios, packets are continuously sent

in the transmit direction when all protection members are in the link-down state.
1. Check the port status and configure port services again according to the
network plan.
----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.
10.2.81 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
● Cause 1: The cable is not connected or the cable is faulty.
● Cause 2: The opposite NE is faulty.
● 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.

If... Then...
The cable is prepared incorrectly Redo the cable.
Step 2 Cause 2: The opposite NE is faulty.

1. Rectify the fault on the opposite NE.
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
10.2.82 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
table.
Name Meaning
Parameters 1 to 6 Indicate the source MAC address that flaps.
Parameter 7,
Indicate the VLAN ID.
Parameter 8
Parameter 9 Indicate the type of the port that learns the source MAC
address before the flapping occurs.
● 0x02: UNI
● 0x03: NNI

Name Meaning
Parameter 10 Indicates the board ID before the flapping occurs.
Parameter 11 Indicates the subboard ID before the flapping occurs.
Parameter 12, Indicate the ID of the port that learns the source MAC
Parameter 13 address before the flapping occurs.
Parameters 14 to 17 Indicate the ID of the UNI or NNI that learns the source
MAC address before the flapping occurs.
Parameter 18 Indicates the type of the port that learns the source
MAC address after the flapping occurs.
● 0x02: UNI
● 0x03: NNI
Parameter 19 Indicates the board ID after the flapping occurs.
Parameter 20 Indicates the subboard ID after the flapping occurs.
Parameter 21, Indicate the ID of the port that learns the source MAC
Parameter 22 address after the flapping occurs.
Parameters 23 to 26 Indicate the ID of the UNI or NNI that learns the source
MAC address after the flapping occurs.

● When the ELAN_SMAC_FLAPPING alarm is generated, network storms may
occur.
● 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
10.2.83 ENERGY_CFG_MISMATCH
Description
The ENERGY_CFG_MISMATCH indicates inconsistent energy control configurations.
It is reported when NEs at both ends of a link have inconsistent energy control
configurations.
Attribute
Minor Service alarm
Parameters
When you view an alarm on the network management system, select it. In the
Alarm Details area, parameters related to the alarm are displayed. The alarm
parameters are in the following format: Alarm Parameters (hex): parameter 1
parameter 2 ... parameter N. For details about each parameter, refer to the
following table.
Name Meaning
Parameter 1 Indicates the energy control object.
Parameter 2, Parameter 3 Indicate the IDs of the PLA groups.

Name Meaning
Parameter 4 Indicates the failure type.

● 0x00: indicates that the settings of
the energy control switches at both
ends of the link are inconsistent.
● 0x01:indicates that the upper
bandwidth usage thresholds
configured at both ends of the link
are inconsistent.
● 0x02: indicates that the lower
bandwidth usage thresholds
configured at both ends of the link
are inconsistent.
● 0x03: indicates the durations of the
sliding windows at both ends of the
link are inconsistent.
● 0x04: indicates that the start time
of the sliding windows at both ends
of the link is inconsistent.
● 0x05: indicates that the end time of
the sliding windows at both ends of
the link is inconsistent.
● 0x06: indicates that the scheduled
ODU power-on configurations at
both ends of the link are
inconsistent.
● 0x07: The energy-saving modes are
inconsistent.

Energy control does not take effect.
Possible Causes
● Cause 1: The settings of the energy control switches at both ends of the link
are inconsistent.
● Cause 2: The upper bandwidth usage thresholds configured at both ends of
the link are inconsistent.
● Cause 3: The lower bandwidth usage thresholds configured at both ends of
the link are inconsistent.
● Cause 4: The durations of the sliding windows at both ends of the link are
inconsistent.
● Cause 5: The start time of the sliding windows at both ends of the link is
inconsistent.
● Cause 6: The end time of the sliding windows at both ends of the link is
inconsistent.

● Cause 7: The scheduled ODU power-on configurations at both ends of the link
are inconsistent.
● Cause 8: The energy-saving modes are inconsistent.
Procedure
1. Based on the failure type, check whether the energy control configurations at
both ends of the link are consistent.
If... Then...
They are consistent The alarm is misreported, and no

further action is required.
They are inconsistent Set the energy control parameters to

the same values for NEs at both
ends of the link.
Related Information
None
10.2.84 ENERGY_INPROCESS
Description
The ENERGY_INPROCESS alarm indicates that energy control is ongoing on the
link. It is reported when the power consumption of the link is below the lower
power consumption limit and energy control is performed.
Attribute
Warning Communication alarm
Parameters
None

The link having energy controlled is disconnected, and services are interrupted.
Possible Causes
If the power consumption of the link is lower than the lower power consumption
limit, the ODU is automatically powered off.

Procedure
1. Contact Huawei technical support engineers.
Related Information
None
10.2.85 ENVHUM_SENSOR_FAIL
Description
The ENVHUM_SENSOR_FAIL is an alarm indicating that the ambient humidity
Attribute
Parameters
None

The ambient humidity data of the PMU cannot be collected.
Possible Causes
● Cause 1: The ambient humidity sensor is faulty.
● 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
10.2.86 ENVTEMP_SENSOR_FAIL
Description
The ENVTEMP_SENSOR_FAIL is an alarm indicating that the ambient temperature
Attribute
Parameters
None

The ambient temperature data of the TCU cannot be collected.
Possible Causes
● Cause 1: The ambient temperature sensor is faulty.
● 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
10.2.87 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
● Cause 1: Ambient temperature sensor 1 is faulty.
● 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
10.2.88 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
● Cause 1: Ambient temperature sensor 2 is faulty.
● 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
10.2.89 ERPS_BLOCK
Description
The ERPS_BLOCK alarm indicates that a port on the ERPS ring is blocked when
protection switching is triggered.
Attribute

Minor Equipment Alarm
Parameters
table.
Name Meaning
Parameter 1 - Parameter 2 ID of ERPS instance.

The alarm does not affect the system.
Possible Causes
Cause 1: When ERPS protection switching occurs, a port on the ERPS ring is
blocked.
Procedure
Step 1 Cause 1: When ERPS protection switching occurs, a port on the ERPS ring is
blocked.
1. In revertive mode, check ERPS_BLOCK the alarm to determine the blocked
point. After the fault is rectified, the alarm is automatically cleared.
2. In non-revertive mode, after the fault is rectified, perform the clear operation
on the owner node to clear the alarm.
----End

Related Information
None
10.2.90 ERPS_CFM_FAIL
Description
The ERPS_CFM_FAIL is an alarm indicating that the MEP bound with an ERPS
instance is faulty. This alarm is reported when the MEP bound with an ERPS
instance detects connectivity loss or when the local end receives a fault indication
from the remote end.
Attribute
Parameters
table.
Name Meaning
Parameters 1–2 Indicates the ID of the ERPS instance.
Parameter 3 Indicates the cause of an OAM fault.

● 0x01: indicates that the local MEP detects connectivity loss.
● 0x02: indicates a peer-MEP fault.

The generation of the ERPS_CFM_FAIL alarm indicates that the link connectivity is
abnormal. If multiple such alarms are generated on the ERPS ring, multiple faults
occur, causing the possibility of service interruption. You need to rectify these
faults immediately.
Possible Causes
Cause 1: The local MEP detects connectivity loss.
Cause 2: The local MEP receives a fault indication from the peer MEP.

Procedure
Step 1 Cause 1: The local MEP detects connectivity loss.
1. Check whether the ETH_CFM_LOC alarm exists. If yes, clear this alarm
following the instructions provided by ETH_CFM_LOC.
2. Check the MEP configuration to ensure that the configuration at both ends is
consistent.
3. Check the VPN service configuration to ensure that the configuration at both
ends is consistent.
4. Check whether there are alarms about the physical link layer. If yes, clear the
alarms.
5. Check the bandwidth usage. If the bandwidth is exhausted, increase the
bandwidth or eliminate the root causes of illegal data transmission.
Step 2 Cause 2: The local MEP receives a fault indication from the peer MEP.
1. Check whether the ETH_CFM_RDI alarm exists. If yes, clear this alarm
following the instructions provided by ETH_CFM_RDI.
2. Perform the operation as described in Step 1.2.
Step 3 Check whether the ERPS_CFM_FAIL alarm is cleared. If the alarm persists, contact
Huawei technical support engineers.
----End
Related Information
None
10.2.91 ERPS_IN_PROTECTION
Description
ERPS_IN_PROTECTION indicates that EPRS ring is in protection mode.
Attribute
Parameters
table.

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.
● 0x01: east
● 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.
10.2.92 ERPS_NOT_COMPLETE
Description
The ERPS_NOT_COMPLETE alarm indicates that the ERPS configuration is
incomplete.
Attribute

Parameters
table.
Name Meaning
Parameters 1–2 Indicate the ERPS ID.

When this alarm is generated, ERPS does not take effect.
Possible Causes
Cause 1: The ERPS configuration is incomplete.
Procedure
Step 1 Cause 1: The ERPS configuration is incomplete.
1. Check whether ERPS is correctly configured for all nodes on the physical ring.
2. If ERPS is correctly configured, check whether the alarm is cleared. If the
alarm persists, contact Huawei technical support engineers.
----End
Related Information
The ERPS_NOT_COMPLETE alarm is not reported in the following cases:

● The ERPS ring network is in the single-port state.
● The ERPS ring node is in the forced switching (FS), signal failure (SF), or manual
switching (MS) state.
● The virtual channel is not enabled.
10.2.93 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
● Cause 1: The opposite NE is not configured with the APS protection.
● Cause 2: The APS protection group is deactivated.
● Cause 3: The settings of the APS protection group differ between the two
ends.
● 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 Go to the next step.
protection
The opposite NE is configured with the APS Go to Cause 2.
protection
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 Activate the APS protocol at
end the end.
The APS protocol is activated at both Go to Cause 3.
ends
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
10.2.94 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
● Cause 1: The configured working and protection paths differ between the two
ends.
● 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
10.2.95 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
10.2.96 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
table.
Name Meaning
Parameter 1 Indicates the specific difference.
● 0x01: Indicates that the switching type is different.
● 0x02: Indicates that the switching direction is different.
● 0x03: Indicates that the revertive mode is different.

This alarm may cause the APS protection failure, and therefore the service
protection fails.
Possible Causes
● Cause 1: The switching type is different.
● Cause 2: The switching direction is different.
● 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
10.2.97 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
● Cause 1: The radio link connected to the alarmed port is faulty.
● 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
10.2.98 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
table.
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) ● 0x01: The port is in the ingress direction.
● 0x02: The port is in the egress direction.

Name Meaning
Parameter 8 (level) Indicates the maintenance domain (MD) level of the local
MEP.
● 0x00: operator MEP level (low)
● 0x01: operator MEP level (medium)
● 0x02: operator MEP level (high)
● 0x03: provider MEP level (low)
● 0x04: provider MEP level (high)
● 0x05: consumer MEP level (low)
● 0x06: consumer MEP level (medium)
● 0x07: consumer MEP level (high)
NOTE
Consumer indicates the customer, provider indicates the supplier,
and operator indicates the carrier.

● When this alarm occurs, the loopback (LB) and link trace (LT) detection
functions are disabled.
● 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
10.2.99 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
table.
Name Meaning
Parameters 1 to 4 (port) Indicates the ID of the alarmed port.
Parameters 5 and 6 (VLAN ID) Indicates the VLAN ID of the MEP.
Parameter 7 (direction) Indicates the direction of the local

MEP.
● 0x00: The port is direction
insensitive.
● 0x01: The port is in the ingress
direction.
● 0x02: The port is in the egress
direction.
Parameter 8 (level) Indicates the MD level of the local

MEP.
● 0x06: consumer MEP level
(medium)
NOTE
Consumer indicates the user, provider
indicates the supplier, and operator
indicates the carrier.
Parameter 9, Parameter 10 (RMEPID) Indicates the ID of the remote MEP.


● When the ETH_CFM_LOC alarm occurs, the LB and LT detection functions of
Ethernet service OAM are unavailable.
● The service between the relevant standard MEPs may be interrupted.
Possible Causes
● Cause 1: The line between the local standard MEP and the remote standard
MEP is interrupted.
● Cause 2: The Ethernet service in the maintenance association (MA) to which
the local MEP belongs is faulty.
● Cause 3: Serious congestion occurs on the network.
Procedure
1. Cause 1: The line between the local standard MEP and the remote standard
MEP is interrupted.
a. 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 Connect the physical links

improperly properly.
The physical links are connected Go to Cause 2.

properly
2. Cause 2: The Ethernet service in the maintenance association (MA) to which

the local MEP belongs is faulty.
a. 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

incorrectly service to ensure consistency at
two ends.
The service is configured correctly Go to Cause 3.
3. Cause 3: Serious congestion occurs on the network.

a. 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.
Related Information
The Table 10-8 describes the meanings of the parameters in the ETH_CFM_LOC
alarm reported by the EoS/EoPDH plane.

Table 10-8 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.
Parameter 17 Indicates the direction of the local

MEP.
insensitive.
direction.
direction.
Parameter 18 Indicates the MD level of the local

MEP.
(medium)
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.

10.2.100 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
table.
Name Meaning

MEP.
insensitive.
direction.
direction.

Name Meaning

MEP.
(medium)
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
● Cause 1: The names of the maintenance domain and the maintenance
alliance that the standard MEPs correspond to are inconsistent.
● Cause 2: The levels of the maintenance domains that the standard MEPs
correspond to are different.
● Cause 3: The physical connection is incorrect.
Procedure
1. Cause 1: The names of the maintenance domain and the maintenance
alliance that the standard MEPs correspond to are inconsistent.
a. 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.

2. Cause 2: The levels of the maintenance domains that the standard MEPs
correspond to are different.
a. 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

The levels are the same Go to Cause 3.
3. Cause 3: The physical connection is incorrect.

a. Check the physical connection of the Ethernet service route and rectify
the fault of the physical connection if any.
Related Information

Name Meaning

(0x01 - 0x10) + 0x80.

MEP.
insensitive.
direction.
direction.

Name Meaning

MEP.
(medium)
NOTE
10.2.101 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
table.
Name Meaning

Name Meaning

MEP.
insensitive.
direction.
direction.

MEP.
(medium)
NOTE
Parameter 9, Parameter 10 (RMEPID) Indicates the ID of the remote MEP.

● When the ETH_CFM_RDI alarm occurs, the loopback (LB) and link trace (LT)
detection functions of Ethernet service OAM are unavailable.
● The service between the relevant standard MEPs may be interrupted.
Possible Causes
● Cause 1: The remote MEP fails to receive the correct CCM packet.
Procedure
1. Cause 1: The remote MEP fails to receive the correct CCM packet.
a. Determine the alarmed port according to the alarm parameter.
b. Check whether the remote MEP that is connected to the port reports the
ETH_CFM_MISMERGE, ETH_CFM_UNEXPERI, or ETH_CFM_LOC alarm.

Related Information

Name Meaning

(0x01 - 0x10) + 0x80.

MEP.
insensitive.
direction.
direction.

MEP.
(medium)
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.

10.2.102 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
table.
Name Meaning

MEP.
insensitive.
direction.
direction.

Name Meaning

MEP.
(medium)
NOTE

● When the ETH_CFM_UNEXPERI alarm occurs, the LB and LT detection
functions of Ethernet service OAM are unavailable.
● The service may become abnormal due to the loop.
Possible Causes
● Cause 1: No remote MEP is configured.
● 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.
● Cause 3: The service is looped back and the looped packet is received.
Procedure
1. Cause 1: No remote MEP is configured.
a. Check whether the remote MEP is configured. If not, configure the
remote MEP first.
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.
a. 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


If... Then...
The CC periods are the same Go to the next step.
b. 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.
3. Cause 3: The service is looped back and the looped packet is received.
a. Check whether any loop exists at each IP port of the service trail. If yes,
release the loop and clear the alarm.
Related Information

Name Meaning

(0x01 - 0x10) + 0x80.

MEP.
insensitive.
direction.
direction.

Name Meaning

MEP.
(medium)
NOTE
10.2.103 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
table.

Name Meaning
Parameter 1 Indicates the reason why the negotiation fails.

● 0x01: The local link is faulty.
● 0x02: The local end fails to receive any OAM packets in a
specified period.
● 0x03: The OAM settings of the opposite end do not meet the
requirements of the local end.
● 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
● Cause 1: The physical port of the local end is faulty.
● Cause 2: The point to point OAM protocol is not enabled at the opposite end.
● 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
10.2.104 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
table.
Name Meaning
Parameter 1 Indicates the type of the link event.

● 0x01: errored symbol period.
● 0x02: errored frame.
● 0x03: errored frame period.
● 0x04: errored frame seconds summary.

When the ETH_EFM_EVENT alarm occurs, the service at the alarmed port may be
interrupted.
Possible Causes
● Cause 1: The physical port at the local end is faulty.
● Cause 2: The equipment at the opposite end is faulty.
Procedure
1. Cause 1: The physical port at the local end is faulty.
a. Check whether the physical port is faulty. If yes, replace the board
where the Ethernet port is located.
2. Cause 2: The equipment at the opposite end is faulty.
a. Rectify the fault of the equipment at the opposite end.
3. Cause 3: The line performance deteriorates (the alarm is reported by an
a. 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 Replace the optical module at

opposite site is too low the opposite site.
The transmit power at the A fiber is faulty. Go to the next

opposite site is normal, but the step.
receive power at the local site is
close to the receiver sensitivity
(for example, a difference within
±3 dB)
b. 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
If... Then...
The alarm persists Go to Cause 1 or 2.
4. Cause 4: The line performance deteriorates (the alarm is reported by an

a. Check whether the cable grounding, cable connectors, and cables are
b. Check whether the alarm is cleared.
If... Then...
The alarm persists Go to Cause 1 or 2.
Related Information
None
10.2.105 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
table.
Name Meaning
Parameter 1 Indicates the state of the loopback.
● 0x01: The local end initiates a loopback.

● 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
● Cause 1: The local end initiates a loopback.
● 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

10.2.106 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
table.
Name Meaning
Parameter 1 Indicates the fault type at the opposite end.
● 0x01: link fault.
● 0x02: dying gasp.
● 0x03: critical event.

When the ETH_EFM_REMFAULT alarm occurs, the service at the alarmed port may
be interrupted.
Possible Causes
● 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 Reset the opposite NE, and the alarm
frequently is cleared.

If... Then...
The opposite NE is not reset Rectify the fault on the opposite NE.
frequently

----End
Related Information
None
10.2.107 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
● Cause 1: The alarmed port and its opposite port work in different modes.
● Cause 2: The network cable is not correctly connected to the alarmed port.
● 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.

If... Then...
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
10.2.108 ETH_LOS
Description
The ETH_LOS alarm indicates the loss of Ethernet port connection.
Attribute
Parameters


table.
Name Meaning
Parameter 1 Indicates the port ID of the board

where the alarm is generated.
Parameter 2, Parameter 3 The parameters have a fixed value of

0x01.
Parameters
None

When the ETH_LOS alarm occurs, the service at the alarmed port is interrupted.
Possible Causes
● 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.
● Cause 2: The optical module types on the transmit end and receive end are
different.
● Cause 3: The cable or fiber is faulty.
● Cause 4: The local receive end is faulty.
● Cause 5: The remote transmit end is faulty.
Procedure
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.
a. 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 port Correctly set the working modes
work in different modes of the transmit port and receive
port.
Set the encapsulation modes of
10GE interfaces at both ends to be
consistent.
The transmit port and receive port Go to Cause 2.

work in the same mode

2. Cause 2: The optical module types on the transmit end and receive end are
different.
a. 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.
3. Cause 3: The cable or fiber is faulty.

a. Check the network cable or fiber jumper connected to the alarmed port.
If... Then...
The network cable is loose or Connect the network cable

damaged properly or replace the damaged
network cable.
The connector of the fiber jumper Clean the connector.

is dirty
The connector or fiber is damaged Insert the connector properly or

replace the damaged fiber jumper.
The connection is normal Go to Cause 4.
4. Cause 4: The local receive end is faulty.

a. 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.
5. Cause 5: The remote transmit end is faulty.

a. Check whether any fault occurs on the equipment interconnected with
the alarmed port.
b. Rectify the fault.
Related Information
None

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

● 0x00: Rx direction.
● 0x01: Tx direction.

When this alarm occurs, it indicates that the alarmed port has no flow.
Possible Causes
● Cause 1: The port is enabled and in link up state, but is configured with no
service.
● 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.
● 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
1. Determine the MAC port number, alarmed board, and cause according to the
parameters.
2. Cause 1: No services are configured.
a. Configure the Ethernet service.
3. Cause 2: No services are available.
If... Then...
No services are available in the Check whether the service is normal

transmit direction at the local end.
No services are available in the Check whether the service is normal

receive direction at the remote end.
Related Information
None
10.2.110 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
● Cause: The board is faulty.

Procedure
Step 1 Cause: The board is faulty.
1. 7.7 Replacing the Ethernet Interface Board.
----End
Related Information
None
10.2.111 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
table.
Name Meaning
Parameter 1 Indicates the ID of the alarmed port.
Parameter 2, The values are always 0x00 0x01.

Parameter 3

Name Meaning
Parameter 4 Indicates the reason why the negotiation fails.

● 0x01: A fault occurs at the local receive link.
● 0x02: The local end fails to transmit OAM packets.
● 0x03: The OAM packets from the opposite end are not
received.
● 0x04: The OAM configuration of the opposite end does not
meet the requirements of the local end.
● 0x05: The OAM configuration of the local end does not
meet the requirements of the opposite end.
● 0x06-0xff: other unknown reasons.

The OAM function based on IEEE 802.3ah is unavailable.
Possible Causes
● Cause 1: The physical port of the local end is faulty.
● Cause 2: The P2P OAM protocol is not enabled at the opposite end.
● 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
10.2.112 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
table.
Name Meaning
Parameter 2, The values are always 0x00 0x01.

Parameter 3
Parameter 4 Indicates the type of the fault.

● 0x01: A link fault occurs at the port of the opposite
end.
● 0x02: Irrecoverable problems such as the power failure
occur at the opposite end.
● 0x03-0xff: other faults.

When this alarm occurs, the services on the link may be interrupted.
Possible Causes
● Cause 1: A link fault occurs at the remote MEP.
● Cause 2: Irrecoverable problems such as power failure occur at the remote
MEP.
● 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.

----End
Related Information
None
10.2.113 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
table.
Name Meaning
Parameter 2, Parameter 3 The values are always 0x00 0x01.
Parameter 4 ● 0x01: The loopback is initiated.

● 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
● Cause 1: The local end issues a loopback command and the opposite end
responds to the command.
● 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
10.2.114 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
table.
Name Meaning
Parameter 2, Parameter 3 The values are always 0x00 0x01.
Parameter 4 Indicates the type of the received link event.

● 0x01: errored frame event
● 0x02: errored frame period event
● 0x03: errored frame second event

When this alarm occurs, the performance of services degrades.
Possible Causes
● Cause 1: The link event notification function is enabled at the opposite end.
● Cause 2: The link performance thresholds of the opposite end are
inappropriate.
● 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
10.2.115 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
table.
Name Meaning
Parameter 1 This parameter has a fixed value of 0x01.
Parameter 2, Indicate the VCTRUNK ID.

Parameter 3
Parameter 4 Indicates the loopback type.

● 0x01: The port is self-looped.
● 0x02: The board is self-looped.
● 0x03-0xff: unknown types.
● 0x04: The MAC address flaps.

Name Meaning
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
● 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.
● Cause 2: Two ports of the board are connected through cables or two ports of
the board are connected to the same LAN.
Procedure
1. Determine the loopback type according to Parameter 1, and then handle the
loopback accordingly.
If... Then...
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 Manually release the PHY/MAC

configured at the port loopback (or wait five 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 is Connect the cable properly to

self-looped release the self-loop.
The port is connected to a LAN that Release the loopback on the LAN, or
has a loopback break the connection between the
port and the LAN, to release the
self-loop.
3. Cause 2: Two ports of the board are connected through cables or two ports of
the board are connected to the same LAN.

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

through cables the self-loop.
The two ports are connected to Break the connection between a

the same network port and the LAN to release the
self-loop.
Related Information
None
10.2.116 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
table.
Name Meaning
Parameter 1 This parameter has a fixed value of 0x01.
Parameter 2, Indicate the VCTRUNK ID.

Parameter 3

Name Meaning
Parameter 4 Indicates the loopback type.

● 0x02: The board is self-looped.
● 0x03-0xff: unknown types.
● 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
● Cause 1: A loopback occurs on the lines connected to one VCTRUNK.
● 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

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

● PORT number, Parameter 9 is 0x00.
● VCTRUNK number, Parameter 9 is 0x80.
Parameter 13 Indicates the MD level of the local MEP.
Parameter 14 to Parameter 17 Indicates the ID of the remote MEP.
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
● Cause 1: The line between two MEPs is interrupted.

● Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs
are faulty.
● 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.
data.
----End
Related Information
None
10.2.118 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
table.
Name Meaning
Parameter 5, Parameter 6 Indicates the ID of the alarmed port.

● PORT number, Parameter 9 is 0x00.
● VCTRUNK number, Parameter 9 is 0x80.
Parameter 9 Indicates the MD level of the local MEP.

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
10.2.119 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm of the loss of the external clock source.

Attribute
Parameters
table.
Name Meaning
Parameter 1 ● 0x01: the first external clock source

● 0x02: the second external clock source

● 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.
● 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
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.
a. 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.
b. 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.
Related Information
None
10.2.120 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm of the loss of the external time source.
Attribute

Parameters
table.
Name Meaning
Parameter 1 ● 0x01: link failure on a port

● 0x02: unchanged second value in time of day (TOD)
information, or unavailable second pulse, or degraded second
pulse
● 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
● Cause 1: The link at a port is faulty.
● 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
10.2.121 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
table.
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
10.2.122 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan is faulty.
Attribute
Parameters
table.
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:
● 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.
● 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
● Cause 1: The board and the backplane are connected improperly.
● 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 The fault is rectified. End the alarm
is removed and inserted handling.
The alarm persists after the board is Go to Cause 2.

removed and inserted
Step 2 Cause 2: Fan failure occurs.

1. Replace the alarmed fan board.
----End
Related Information
None
10.2.123 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
table.

Name Meaning
Indicate the VCTRUNK number where the alarm

Parameter 2, Parameter 3
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
● Cause 1: The encapsulation protocols or encapsulation parameters are
inconsistent at both ends of services.
● 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.

1. Replace the alarmed board.
----End
Related Information
None
10.2.124 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:
● Cause 1: The value of Address Detection Upper Threshold is too small.
● Cause 2: The E-LAN service is attacked.
Procedure
● 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.
● 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
10.2.125 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

10.2.126 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
table.
Name Meaning
Parameter 1 Indicates the receive or transmit direction in which traffic crosses
the specified threshold.
● 0x00: the receive direction
● 0x01: the transmit direction

When the FLOW_OVER alarm occurs, the extra data may be discarded.
Possible Causes
● Cause 1: The traffic threshold is very low.
● Cause 2: The opposite end transmits excessive data flow.
● 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
10.2.127 GNE_CONNECT_FULL
Description
GNE_CONNECT_FULL is an alarm indicating that the number of connections
between the device and terminal exceeds the threshold.
Attribute
Parameters
table.
Name Meaning
Parameters 1 to 2 Indicate the type of the connection for

which this alarm is generated.
● When Parameter 1 is set to 0x05
and Parameter 2 is set to 0x78, the
number of TCP connections for port
1400 exceeds the threshold.
number of SSL connections for port
5432 exceeds the threshold.
total number of TCP and SSL
connections exceeds the threshold.


After this alarm is reported, the same type of connections can no longer be
established between the device and terminal, affecting DCN communication.
Possible Causes
The number of gateway connections exceeds the threshold.
Procedure
1. Check all the connections and delete unused connections so that new
connections can be established.
Related Information
None.
10.2.128 GPSMOD_INVALID
Description
The GPSMOD_INVALID alarm is generated when the GPS module fails.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Parameter 1 has the following meanings:
● 0x01: The I2C interface of the GPS module is abnormal.

● 0x02: The phase-locked loop (PLL) chip interface of the GPS
module is abnormal.
● 0x03: The GPS chip of the GPS module is abnormal.
● 0x04: The memory chip of the GPS module is abnormal.
● 0x05: The Serdes interface of the GPS module is abnormal.
● 0x06: The internal 1PPS signal of the GPS module is abnormal.
● 0x07: The internal clock source signal of the GPS module is
abnormal.
● 0x08: The system clock of the GPS module is abnormal.
● 0x09: The voltage of the GPS module is abnormal.
● 0x0A: The temperature sensor of the GPS module is abnormal.
● 0x0B: The antenna of the GPS module is abnormal.
● 0x0C: The temperature of the GPS module exceeds the specified
threshold.

The services may be affected.
Possible Causes
● Cause 1: The I2C interface of the GPS module is abnormal.
● Cause 2: The PLL chip interface of the GPS module is abnormal.
● Cause 3: The GPS chip of the GPS module is abnormal.
● Cause 4: The memory chip of the GPS module is abnormal.
● Cause 5: The Serdes interface of the GPS module is abnormal.
● Cause 6: The internal 1PPS signal of the GPS module is abnormal.
● Cause 7: The internal clock source signal of the GPS module is abnormal.
● Cause 8: The system clock of the GPS module is abnormal.
● Cause 9: The voltage of the GPS module is abnormal.
● Cause 10: The temperature sensor of the GPS module is abnormal.
● Cause 11: The antenna of the GPS module is abnormal.
● Cause 12: The temperature of the GPS module exceeds the specified
threshold.
Procedure
Step 1 Reset the GPS module.
Step 2 Check whether the alarm is cleared. If the alarm persists, replace the GPS module.
For details, see Replacing the SFP.

support engineers.
----End
Related Information
None
10.2.129 GPSMOD_LOCK_FAIL
Description
The GPSMOD_LOCK_FAIL alarm is generated when the clock of the GPS module is
unlocked.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Parameter 1 has the following meanings:
● 0x01: The frequency is unlocked.
● 0x02: The time is unlocked.

The services may be affected.
Possible Causes
● Cause 1: The clock of the GPS module fails to be locked.
Procedure
Step 1 Adjust the GPS antenna and check that it is not blocked. If it is blocked, clear the
obstacles or move it.
Step 2 Check whether the alarm is cleared. If the alarm persists, replace the GPS antenna
system. For details, see the Atom GPS Installation Guide.

support engineers.
----End
Related Information
None
10.2.130 GSP_RSVP_NB_AUTH_ERR
Description
The GSP_RSVP_NB_AUTH_ERR alarm indicates a Resource Reservation Protocol
(RSVP) neighbor authentication error.
Attribute
Parameters
table.
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
10.2.131 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
table.
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
● Cause 1: RSVP is disabled on the RSVP neighbor.
● Cause 2: There is no reachable route to the RSVP neighbor.
● Cause 3: The link between the local NE and the RSVP neighbor is faulty.
● 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.
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
10.2.132 GSP_TNNL_DOWN
Description
The GSP_TNNL_DOWN alarm indicates that an RSVP-TE tunnel is faulty.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the cause of the RSVP-TE tunnel fault. The values are as
follows:
● 0x01: indicates a route calculation failure.
● 0x02: indicates a signaling response time-out.
● 0x03: indicates a bandwidth resource request error.
● 0x04: indicates that the resources (including interface and
label information) requested by RSVP are invalid.
● 0x05: indicates a label allocation failure.
● 0x06: indicates a cross-connection control failure.
● 0x07: indicates a tunnel cross-connection setup failure.
● 0x08: indicates an unavailable data link.
● 0x09: indicates a signaling negotiation failure.
● 0x0a: indicates an unknown cause.
● 0x0b: indicates a link fault.
● 0x0c: indicates an RSVP tunnel creation failure.
● 0x0d: indicates a restoration failure during an RSVP restart.
● 0x0e: indicates an RSVP summary refresh time-out.
● 0x0f: indicates an RSVP GR time-out.
● 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
● 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.
● 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.
● 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.
● 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.
● 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

10.2.133 HARD_ERR
Description
The HARD_ERR alarm indicates a hardware error. This alarm is reported when
there are minor hardware errors Minor alarm.
Attribute
Parameters
Name Meaning
Parameter 1 ● 0x01: The clock chip is faulty.

● 0x02: The JTAG self-check fails.
● 0x03: The chip self-check fails.
● 0x04: The port is faulty.
● 0x05: The peripheral is faulty.
● 0x06: The clock PLL is unlocked.
● 0x07: The MDIO bus is abnormal.
● 0x09: The 1588 clock server is
abnormal.
● 0x14: The storage component is
faulty.

Name Meaning
Parameter 2 ● When Parameter 1 is set to 0x14,

Parameter 2 indicates the ID of the
faulty storage component.
When Parameter 2 is set to 0x12,
the network port is abnormal.
● Parameter 1 is set to 0x04:
the communication between the
active and standby LAN switches is
faulty.
temperature chip 1 or the
corresponding IIC is faulty.
temperature chip 2 or the
corresponding IIC is faulty.
● Parameter 1 is set to 0x05:
the USB output current limiting is
abnormal.
reading the temperature register
through the IIC bus is abnormal.
100M clock PLL is unlocked.
and Parameter 2 is set to 0x01,
network port detection is abnormal.
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 faulty board.
----End
Related Information
None
10.2.134 HARD_BAD
Description
The HARD_BAD alarm indicates that hardware is faulty.
Attribute
Parameters
table.
Name Meaning
Parameter 1, Parameter 2, Parameter 3 Indicate the internal fault detected by

the board. For details 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
● Cause 1: The board that reports the HARD_BAD alarm and the backplane are
not connected properly.
● Cause 2: The board that reports the HARD_BAD alarm or system control,
switching, and timing board is faulty.
● 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 7.1 Removing a Board and 7.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 7 Part Replacement.
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, see Mapping
between physical boards and logical boards.
Table 10-12 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 7 Part
Replacement.
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.

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
10.2.135 HARD_NONSUPPORT
Description
The HARD_NONSUPPORT alarm indicates that board hardware does not support
the configuration issued by the system control board or that the total power
consumption of all inserted boards exceeds the upper power consumption limit.
Attribute
Parameters
table.

Name Meaning
Parameter 1 ● 0x01: indicates that the board does

not support the ETH PWE3 control
word function.
● 0x02: indicates that the board does
not support the system control
board's bus rate of 2.5 Gbit/s.
● 0x03: indicates that the PW OAM
does not support the control word
mode.
● 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.
● 0x05: indicates that the power
consumption exceeds the upper
limit.
● 0x06: The power consumption of
the PIU exceeds the limit.

When this alarm occurs, the corresponding function becomes unavailable. If the
power consumption exceeds the specified threshold, services may be affected.
Possible Causes
● 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.
● Cause 3: The system control board is configured to disable the generic
associated channel label (GAL) for the PW OAM.
● Cause 4: The transmit optical power of the board is modified, or the
configured transmit optical power exceeds the specified range.
● Cause 5: The power consumption power of the NE exceeds the upper limit.
● Cause 6: The power consumption of the PIU exceeds the limit.
Procedure
Step 1 Causes 1, 2, and 3:
1. Replace the board that does not support this feature with a capable one. For
details about the functions and features supported by a board, see "IDU
Hardware Description." For details about how to replace a board, 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, adjust the transmit optical power within the power
range supported by the board. Check whether the alarm is cleared.
3. If this alarm is not cleared, replace the board. For details, see "Parts
Replacement".
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 Cause 6: The power consumption of the PIU exceeds the limit.
1. Reduce the number of IF boards or ODUs, and then check whether the alarm
is cleared.
2. If the alarm persists, replace the power board with one of the latest version.
Step 5 Check whether the alarm is cleared. If the alarm is not cleared, contact Huawei
----End
Related Information
None
10.2.136 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
table.

Name Meaning
Parameter 1 Indicates the performance monitoring

period:
● 0x01: 15 minutes
● 0x02: 24 hours
Parameter 2, Parameter 3 Indicate the ID of a performance event

that causes the alarm.
● 0x30: HPBBE
● 0x31: HPES
● 0x32: HPSES
● 0x33: HPFEBBE
● 0x34: HPFEES
● 0x35: HPFESES
● 0x36: HPUAS
● 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 5.2.5
Browsing the Performance Event Threshold-Crossing Records.
2. Handle the threshold-crossing performance event.
----End
Related Information
None
10.2.137 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
● Cause 1: The service level is inconsistently configured at both ends.
● Cause 2: The transmit unit of the peer NE is faulty.
Procedure
1. Cause 1: The service level is inconsistently configured at both ends.
a. 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.
2. Cause 2: The transmit unit of the peer NE is faulty.
a. Replace the alarmed board on the local NE. 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 system control,

cross-connect, and timing board
on the peer NE.

Related Information
None

10.2.138 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
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
10.2.139 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
and indicates 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
10.2.140 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
● 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.
● 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
10.2.141 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
● 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...
configuration is changed alarm handling.
The alarm persists after the Go to the next step.
configuration is 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
10.2.142 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
● 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.
● 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
10.2.143 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


table.
Name Meaning
Parameter 1 Indicates the performance monitoring period:
● 0x02: 24 hours
Parameter 2, Indicate the ID of a performance event that causes the
Parameter 3 alarm.
● 0xaa: TUPJCHIGH
● 0xab: TUPJCLOW
● 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 5.2.5
Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None
10.2.144 IF_CABLE_ABN
Description
The IF_CABLE_ABN alarm indicates that the IF cable is faulty.

Attribute
Parameters
When you view an alarm on the network management system, select it. In the
Alarm Details area, parameters related to the alarm are displayed. The alarm
parameters are in the following format: Alarm Parameters (hex): parameter 1
parameter 2 ... parameter N. For details about each parameter, refer to the
following table.
Name Meaning
Parameter 1 0x01: The IF cable is faulty.

Services carried over the IF port generating the alarm may experience bit errors or
even be interrupted.
Possible Causes
● Cause 1: The voltage of the power supply is low.
● Cause 2: The impedance increases due to factors such as aging of the IF cable
or corrosion of the port.
Procedure
Step 1 Cause 1: The voltage of the power supply is low.
1. Check whether the power board reports POWER_ABNORMAL.
If... Then...
The alarm is reported Check whether the power cable is

broken, damaged, or incorrectly
connected by referring to the
descriptions of POWER_ABNORMAL.
The alarm is not reported Go to the next step.
Step 2 Cause 2: The impedance increases due to factors such as aging of the IF cable or
corrosion of the port.
1. Locate the faulty IF cable based on the alarm information, and repair or
replace the IF cable.

support engineers.
----End
Related Information
None
10.2.145 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
● Cause 1: The IF cable is loose or faulty.
● Cause 2: The IF port on the IF board is damaged.
● Cause 3: The power module of the ODU is faulty.
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
1. Cause 1: The IF cable is loose or faulty.
a. 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 improperly See the Installation Reference and

None of the above make new connectors for the IF
cable.
Go to the next step.
b. Check whether the surface of the IF fiber jumper and the IF cable is
damaged.
If... Then...
The cable does not meet the Replace the cable with a qualified
requirement one.
The cable meets the requirement Go to Cause 2 or Cause 3.
2. Cause 2: The IF port on the IF board is damaged.

a. Replace the alarmed IF board.
3. Cause 3: The power module of the ODU is faulty.
a. Replace the ODU connected to the alarmed IF port.
Related Information
None.
10.2.146 IF_INPWR_ABN
Description
The IF_INPWR_ABN is an aarm indicating that the power supplied by an IF board
to an ODU is abnormal.
Attribute
Parameters
In the Alarm Details area, parameters related to the alarm are displayed. The
alarm parameters are in the following format: Alarm Parameters (hex): parameter
1 parameter 2 ... parameter N. For details about each parameter, refer to the
following table.

Name Meaning
Parameter 1 ● 0x01: Indicates that the input power

of the ODU is too high.
● 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
● Cause 1: The IF board is faulty.
● Cause 2: The IF cable is faulty.
● Cause 3: The ODU is faulty.
● 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

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

If... Then...
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:
● The logical slot ID of an OptiX RTN 910A/950/950A ODU is the logical slot ID
of the IF board connected to the ODU plus 20.
● The logical slot ID of an OptiX RTN 980 ODU is the logical slot ID of the IF
board connected to the ODU plus 50.
For dual-IF boards:
● 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 dual-channel 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 dual-IF board plus 50.
● The logical slot ID of the OptiX RTN 910A/950/950A/980 ODU connected to
the second IF port is the logical slot ID of the ODU connected to the first IF
port plus 20.
10.2.147 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
table.

Name Meaning
Parameter 1 Indicates the ID of the FPGA file that is loaded to the board.
● 0x01 indicates that FPGA file 250 is loaded.
● 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
● 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 technical support engineers to upgrade the software and
the FPGA file.
----End
Related Information
None
10.2.148 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


table.
Name Meaning
Parameter 1 Indicates whether the number of IGMP Snooping multicast table

entries exceeds its upper threshold.
● 0x00: indicates that the number of IGMP Snooping multicast
table entries does not exceed its upper threshold.
table entries exceeds its upper threshold.
Parameter 2 Indicates whether the number of IGMP Snooping multicast group

members exceeds its upper threshold.
group members does not exceed its upper threshold.
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
● Cause 1: The configured upper threshold for the number of IGMP Snooping
multicast table entries is too small.
● 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
10.2.149 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
● Cause 1: The IMA links on the local NE are faulty.
● 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.
occurs Activate 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
10.2.150 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
● Cause 1: The IMA links on the remote NE are faulty.
● 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.
occurs Activate 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
10.2.151 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.
● 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.
● 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.
10.2.152 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
● Cause 1: The transmit power of the opposite NE is over high or over low.
● Cause 2: The model of the selected optical module is incorrect.
● Cause 3: The optical module at the receive end is faulty.
● Cause 4: The fiber performance degrades.
Procedure
1. Cause 1: The transmit power of the opposite NE is over high or over low.
a. 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 Replace the optical module.

not meet the requirement
The transmit optical power is over Add a proper attenuator to reduce

high the receive optical power.
2. Cause 2: The model of the selected optical module is incorrect.

a. 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.
3. Cause 3: The optical module at the receive end is faulty.

a. 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 technical support engineers to replace the optical module.
4. Cause 4: The fiber performance degrades.
If... Then...
The connector of the fiber jumper is Clean fiber connectors.

dirty
The connector or fiber is damaged Insert the connector properly or

replace the damaged fiber jumper.
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.

10.2.153 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
● 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.
1. Browse current performance events, and query the performance event of
the transmit optical power on the opposite NE.
Option Description
t optical power does not meet the Contact Huawei engineers to replace
requirement the optical module.
The transmit optical power meets Add a proper attenuator to reduce the
the requirement 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.
Option Description
are incorrect Contact Huawei engineers to replace the optical
module.
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 technical support 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.
10.2.154 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
● Cause 1: The transmit power of the opposite NE is over low.
● Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over low.
1. Browse current performance events, and query the performance event of
the transmit optical power on the opposite NE.
Option Description
t optical power does not meet the Contact Huawei engineers to
requirement replace the optical module.

Option Description
The transmit optical power meets the Go to Cause 2.
requirement
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 Contact Huawei engineers to replace the optical
module.
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.
Option Description
optical power meets the requirement Contact Huawei engineers to
replace the optical module.
The receive optical power does not Go to Cause 4.
meet the 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
cleaned alarm handling.
The alarm persists after the connector is Replace the fiber.
cleaned
----End
Related Information
The optical power threshold set for the IN_PWR_LOW alarm is higher than the
sensitivity point.
SDH Interface Performance.
10.2.155 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
table.
Name Meaning
Parameter 1 Indicates the resource type.
● 0x00: mfs
Parameter 2 Indicates that the current memory space utilization.
Parameters 3 to 5 These parameters are reserved. Their values are always 0xff.

● Package loading fails.
● 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 technical
----End
Related Information
None

10.2.156 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
table.
Name Meaning
Parameter 1 Indicates the resource type.
● 0x00: ofs1
● 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 technical
----End
Related Information
None
10.2.157 INTEMP_SENSOR_FAIL
Description
The INTEMP_SENSOR_FAILL is an alarm indicating that the air inlet temperature
Attribute
Parameters
None

The air inlet temperature data of the TCU cannot be collected.
Possible Causes
● Cause 1: The air inlet temperature sensor is faulty.
● 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
10.2.158 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
table.
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
Cause 1: The LSP serial number generated exceeds the upper threshold.
Procedure
Step 1 If the ISIS_LSP_SEQ_EXCEED alarm is reported, the instance system of IS-IS enters
1. On the NMS, continuously check the LSP serial number generated by the local
router.
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 The device runs properly, and no

incremented normally. action is required.
The LSP serial number is Go to the next step.

incremented by 1 at 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.
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

10.2.159 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
table.
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
Possible Causes
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.
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 The device runs properly, and no

incremented normally. action is required.
The LSP serial number is Go to the next step.

incremented by 1 at 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.
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.
----End
Related Information
None
10.2.160 ISISADJACENCYCHANGE
Description
The ISISADJACENCYCHANGE alarm indicates that the status of an IS-IS neighbor
changes.
Attribute
Parameters
table.

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
● Cause 1: The IS-IS configurations are incorrect.
● Cause 2: The link between the local NE and the IS-IS neighbor is faulty.
● 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
10.2.161 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
10.2.162 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
table.
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
● Cause 1: The switching modes configured at both ends are single-ended
switching and dual-ended switching separately.
● 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...
The alarm persists Replace the alarmed board.
----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
10.2.163 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
table.
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
● Cause 1: Two NEs of the linear MSP group are configured with different
protection modes (1+1 or 1:N).
● Cause 2: The MSP protocol is stopped when the protection switching occurs.
● 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

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.
10.2.164 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
● Cause 1: The database on the alarmed NE is abnormal.
● 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 technical support engineers to handle
the alarm.
----End
Related Information
None

10.2.165 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
table.
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
● Cause 1: Data configuration is incorrect.
● Cause 2: The maximum number of route prefixes in a VPN instance routing
table is set to a small value.
● 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
10.2.166 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
table.
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:
● 0x01: active
● 0x02: notInService
Parameters 41-44 Indicate the VPN instance running

status.
● 0x01: up
● 0x02: down


The VPN service is interrupted.
Possible Causes
● Cause 1: The VPN instance is not bound with any interfaces.
● 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
10.2.167 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
10.2.168 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
10.2.169 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
table.
Name Meaning
Parameter 1, Indicates the slot ID of the alarmed board.

Parameter 2
Parameter 3 Indicates the ID of the alarmed subboard. The value is

always 0xff.
Parameter 4, Indicates the ID of the alarmed port.

Parameter 5
Parameter 6 Indicates the cause that makes the port unavailable.

● 0x01: The port link is faulty or disabled.
● 0x02: The port fails to receive the LACP packets.
● 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
● Cause 1: The port link is faulty or disabled.
● Cause 2: The port receives no LACP packets.
● Cause 3: The port works in half-duplex mode or not in Auto-Negotiation
mode.
● Cause 4: The port is self-looped.
Procedure
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

2.

3.

4.

5.
2. Cause 1: The port link is faulty or disabled.

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

3. Cause 2: The port receives no LACP packets.

a. 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.
4. Cause 3: The port works in half-duplex mode or not in Auto-Negotiation
mode.
a. 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.
b. On the NMS, change the working mode of the port into full-duplex and
Auto-Negotiation.
5. Cause 4: The port is self-looped.
a. Check whether the port is self-looped. For details, see 9.2.1 Querying the
Attributes of an Ethernet Port. If the port is self-looped, release the
selfloop. For details, see 9.4.5 Setting a Loopback for the Packet-plane
Ethernet Interface Board.
Related Information
None
10.2.170 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
table.
Name Meaning
Parameter 1 Indicates the number of the IP port.
Parameter 2, Parameter 3 The values are always 0x01.

Name Meaning
Parameter 4 Indicates the cause of the protection

failure.
● 0x01: The link of the port is faulty
or fails.
● 0x02: The port is in half-duplex
mode.
● 0x03: The port fails to receive the
LACP packets.
● 0x04: The port detects the selfloop.
● 0x05: Other unknown reasons.
Parameter 5 The value is always 0xff.

Possible Causes
● Cause 1: The port is disabled or the link is faulty.
● Cause 2: The port is in the half-duplex mode.
● Cause 3: The port fails to receive the LCAP packets.
● Cause 4: The port detects a selfloop.
● 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 Reconfigure the LAG group.

configured
The LAG group is properly Go to the next step.

configured
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

----End
Related Information
None
10.2.171 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
table.
Name Meaning
Parameter 2, Indicate the number of the faulty VCG port in the LAG.
Parameter 3 Parameter 2 indicates the most significant bits and
Parameter 3 indicates the least significant bits.
Parameter 4 Indicates the cause of the protection failure.

● 0x01: The link of the port is faulty or fails.
● 0x03: The port fails to receive the LACP packets.
● 0x04: The link of the port is configured into a loop.
● 0x05: other unknown reasons.

Possible Causes
● Cause 1: The link of the port is faulty or fails.
● Cause 2: The port fails to receive the LCAP packets.
● Cause 3: The port detects a selfloop.
● 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
----End
Related Information
None
10.2.172 LAN_LOC
Description
The LAN_LOC is an alarm indicating the Ethernet communication failure.
Attribute
Parameters


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

Parameter 3 reported.
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
● Cause 1: The cable is not connected to the network port, or the cable is faulty.
● Cause 2: The network port is faulty.
● 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 7.11 Replacing the System Control,
Switching and Timing Board.
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 7.11
----End
Related Information
None

10.2.173 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:
● Cause 1: The optical module is faulty.

● 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

10.2.174 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
10.2.175 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
● Cause 1: The optical module installed at the optical interface does not match
the rate of the optical interface.
● Cause 2: The small form-factor pluggable (SFP) module does not match the
interface type.
Procedure
1. Cause 1: The optical module installed at the optical interface does not match
a. Check whether the optical module installed at the optical interface
matches the rate of the optical interface. For details, see Querying the
Board Manufacturing Information Report.
If... Then...
The optical module does not Contact Huawei technical support

match the rate of the optical engineers to replace the optical
interface module with one that matches the
rate of the optical interface.
The optical module matches the Go to Cause 2.

rate of the optical interface
2. Cause 2: The SFP module does not match the interface type.
a. Check whether the port type is correctly set and whether the SFP type is
correct according to the network plan.
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.
3. Cause 3: The optical module is faulty.

a. Replace the faulty optical module.

If... Then...
The alarm is cleared after the End the alarm handling.

optical module is replaced
The alarm persists after the Go to Cause 3.

optical module is replaced
4. Cause 4: A certain board is faulty.

Related Information
None
10.2.176 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
● Cause 1: The optical module installed at the optical interface does not match
● 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 5.7.5 Querying the Board
Manufacturing Information Report.
Option Description
module does not match the rate Contact Huawei engineers to replace
of the optical interface the optical module with one that
matches the rate of the optical
interface.
The optical module matches the Go to Cause 2.
rate of 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 See Configuring an SFP Port.to rectify the
set 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 End the alarm handling.
replaced
The alarm persists after the optical module is Go to Cause 3.
replaced

----End
Related Information
None
10.2.177 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
● Cause 1: The type of the optical module inserted into an optical port
mismatches the optical module type supported by the physical board.
● Cause 2: For EX1 and EG4 boards integrated on the RTN 980 and RTN 980L, a
commercial-class optical module is used.
Procedure
● 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 Go to the next step.

inserted into an optical port is the
required optical module type
The type of the optical module Replace the optical module with a
inserted into an optical port is not module of the supported type.
the required optical module type.
● 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.

● Check whether the alarm is cleared. If the alarm persists, contact Huawei
----End
Related Information
None
10.2.178 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
10.2.179 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
table.
Name Meaning
Parameter 2, Parameter Indicate the ID of the alarmed VCTRUNK. For

3 example, 0x00 0x01 indicate that the alarm is
reported in VCTRUNK 1.

The Ethernet service is not normal.
Possible Causes
● Cause 1: Configuration data of the LCAS protocol is incorrect.
● 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 Go to Cause 2.
both ends 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 Correct the configuration
NEs are incorrect data.
The configurations of the local and opposite Go to Cause 2.
NEs 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
10.2.180 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
table.

Name Meaning


The Ethernet service is not normal.
Possible Causes
● Cause 1: Configuration data of the LCAS protocol is incorrect.
● 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 Go to Cause 2.
ends 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 Correct the configuration
NEs are incorrect data.
The configurations of the local and opposite Go to Cause 2.
NEs 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
10.2.181 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
table.
Name Meaning


The available Ethernet service bandwidth is smaller than the configured
bandwidth.
Possible Causes
● 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.

● Cause 2: Some paths in the transmit direction of the remote site are faulty.
● 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 remote site is different from that at the local site.
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 details, see Dynamically Increasing/
physical paths or bound with Decreasing the VCTRUNK
different timeslots 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
10.2.182 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
table.
Name Meaning

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
● 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.
● Cause 2: Some paths in the receive direction of the remote site are faulty.
● 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 remote site is different from that at the local site.
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 For details, see Dynamically
or 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
10.2.183 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
table.
Name Meaning
Parameter 2, Parameter Indicates the ID of the alarmed VCTRUNK. For

reported in VCTRUN 1.

There is no available bandwidth in the receive direction, and the Ethernet services
are interrupted.

Possible Causes
● Cause 1: No VCTRUNK is bound to the remote port.
● Cause 2: Paths in the transmit direction of the remote site are faulty.
● 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 Go to Cause 2.
added,
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
10.2.184 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
table.
Name Meaning


There is no available bandwidth in the transmit direction, and the Ethernet
services are interrupted.
Possible Causes
● Cause 1: No VCTRUNK is bound to the remote port.
● Cause 2: Paths in the receive direction of the remote site are faulty.
● 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.
No VCTRUNK has been Go to Cause 2.
added,
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
10.2.185 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

● 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
● 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.
● 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.
● 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 alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and
B3_EXC.
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
9.6.1 Cold Reset.
2. If the LCD alarm persists, replace the alarmed board. For details, see 7.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
● For the external ATM port, the threshold of generating the LCD alarm is seven
cells.
● For a VC-4 VCTRUNK port, the threshold of generating the LCD alarm is 360
cells.
● 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.

10.2.186 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
table.
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:
● 0x00: The license file is naturally invalid.
● 0x01: The license file is forcibly invalid.
● 0x02: The ESN does not match.
● 0x03: The V/R version does not match.
● 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
● Cause 1: The license file has expired, but is in the grace period of 60 days.
● 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.
● 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
10.2.187 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
table.
Name Meaning
Parameters 1 Indicate the days since the grace period of a license has expired
and 2 or the ID of the expired license.
Parameter 3 Indicates the cause for the license file to become invalid:
● 0x00: The license file is naturally invalid.
● 0x01: The license file is forcibly invalid.
● 0x02: The ESN does not match.
● 0x03: The V/R version does not match.
● 0x04: Both the ESN and V/R version do not match.
● 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
● Cause 1: The system has run for more than 60 days after the license file
expired.
● 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
10.2.188 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

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

Name Meaning
Parameter 1 Indicates the alarm cause.
● 0x01: The service capacity exceeds the capacity authorized by

the license file.
● 0x02: The AM license capacity exceeds the capacity authorized
● 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.
● 0x04: The 1588v2 capacity exceeds the capacity authorized by
the license file.
● 0x05: The ATM/IMA capacity exceeds the capacity authorized by
the license file.
● 0x06: The air port LAG capacity exceeds the capacity authorized
● 0x07: The E1PRIOR function is restricted.
● 0x08: The synchronous Ethernet capacity exceeds the capacity
authorized by the license file.
● 0x09: The air port compression capacity exceeds the capacity
authorized by the license file
● 0x0a: The MPLS service license capacity exceeds the capacity
authorized by the license file.
● 0x0b: The PLA license capacity exceeds the capacity authorized
● 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.
● 0x0d: The GE port capacity exceeds the capacity authorized by
the license file.
● 0x0e: No XPIC license is available.
● 0x0f: No ERPS license is available.
● 0x10: The number of configured VC-12 cross connections
exceeds the number authorized by the license file.
● 0x11: The number of ports configured with the 1024QAM
modulation scheme exceeds the number authorized by the
license file.
● 0x12: No microwave 1+1 protection license is available.
● 0x13: No enhanced QoS license is available.
● 0x14: The capacity configured for the COMBO port exceeds the
licensed capacity.
● 0x15: No second-IF-port license is available.
● 0x16: No MPLS-TP OAM license is available.
● 0x17: No WRED license is available.
● 0x18: No AMAC license is available.

Name Meaning
● 0x19: L3 functions are restricted.
● 0x1a: No HQoS license is available.
● 0x1b: No L2DCN license is available.
● 0x1c: No ITU-T Y.1731 license is available.
● 0x1d: No LLDP license is available.
● 0x1e: No STM-1 license is available.
● 0x1f: No PoE license is available.
● 0x20: No IS3 mode license is available.
● 0x21: No IP FPM license is available.
● 0x22: The 62.5M or 125M sub-bandwidth function is restricted.
● 0x23: The 1.25 Gbit/s CPRI function is restricted.
● 0x24: The 2.5 Gbit/s CPRI function is restricted.
● 0x25: The 250M bandwidth extension function is restricted.
● 0x26: The 2048QAM function is restricted.
● 0x27: The enhanced N+1 function is restricted.
● 0x28: The total capacity over air interfaces on an NE exceeds the
total licensed capacity.
● 0x29: The number of configurable IF air interfaces exceeds the
licensed capacity.
● 0x2a: The 2048QAM function is restricted.
● 0x2b: The AES function is restricted.
● 0x2c: The 4096QAM function is restricted.
● 0x2d: The XPIC capacity on an ISM6 board exceeds the licensed
capacity.
● 0x2E: The virtual master function is restricted.
● 0x2F: The virtual AP function is restricted.
● 0x30: The number of connected virtual APs exceeds the upper
threshold.
● 0x32: The number of boards supporting Super Dual Band
exceeds the limit authorized by the license file.
● 0x34: The license for the bandwidth notification function is not
loaded.
● 0x36: The number of boards with the anti-theft function
enabled exceeds the license threshold.
● 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
● Cause 1: The configured capacity exceeds the licensed capacity.
● 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.
10.2.190 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
table.

Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is
always 0x01.
Parameter 2, Parameter 3 Indicates the path ID.

● When this alarm occurs, the alarmed E1 link is unavailable, and the available
links in the IMA group are reduced.
● If the VCTRUNK link binds only one member, the service is interrupted when
the LFA alarm occurs.
● 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:
● 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 7.7 Replacing the
Ethernet Interface Board or 7.6 Replacing the Smart E1 Interface Board.
----End
Related Information
Basic frame

10.2.191 LINK_ERR
Description
The LINK_ERR alarm indicates that a data link is faulty.
Attribute
Parameters
table.
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
Parameter 3 example, 0x00 0x01 indicate that the alarm is reported by
path 1.

Services in the alarmed path are interrupted.
Possible Causes
● Cause 1: The optical fiber connected to the Ethernet optical port is faulty.
● Cause 2: The working modes of the ports at the local and opposite ends are
different.
● 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 Set the working modes of
and opposite ends are different the ports to the same.
The working modes of the ports at the local Go to the next step.
and 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 9.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
10.2.192 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
table.
Name Meaning
always 0x01.

Name Meaning
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:

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

10.2.193 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:
● Cause 1: The peer NE is faulty.
● 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 NCE 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 NCE. 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.
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,
----End
Related Information
None
10.2.194 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a loop occurs.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the type of loopback.

● 0x00: optical/electrical port inloop
● 0x01: optical/electrical port outloop
● 0x02: path inloop
● 0x03: path outloop
● 0x04: loopback on the user side
● 0x05: loopback on the multiplexing
side
● 0x06: SPI inloop
● 0x07: SPI outloop
● 0x08: ATM layer inloop
● 0x09: ATM layer outloop
● 0x0A: PHY layer inloop
● 0x0B: PHY layer outloop
● 0x0C: MAC layer inloop
● 0x0D: MAC layer outloop
● 0x0E: VC-4 timeslot inloop
● 0x0F: VC-4 timeslot outloop
● 0x10: VC-3 timeslot inloop
● 0x11: VC-3 timeslot outloop
● 0x12: VC-12 timeslot inloop
● 0x13: VC-12 timeslot outloop
● 0x14: IF outloop
● 0x15: IF inloop
● 0x16: RF inloop
● 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
1. Cause 1: A loop is performed on the local NE.
a. Determine the type of loopback according to the alarm parameter.

b. Find out the cause of the loopback, and set the loopback status of the
alarmed port to Non-Loopback.For details, see 9.4 Software Loopback.
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).
Parameter 4 Indicates loopback types.

● 0x00: inloops at optical/electrical
ports
● 0x01: outloops at optical/electrical
ports
● 0x02: inloops at paths
● 0x03: outloops at paths
● 0x04: loopbacks on the client side
● 0x05: loopbacks on the combination
wave side
● 0x08: inloops at the ATM layer
● 0x09: outloops at the ATM layer
● 0x0A: inloops at the PHY layer
● 0x0B: outloops at the PHY layer
● 0x0C: inloops at the MAC layer
● 0x0D: outloops at the MAC layer
● 0x0E: inloops at VC-4 timeslots
● 0x0F: outloops at VC-4 timeslots
● 0x10: inloops at VC-3 timeslots
● 0x11: outloops at VC-3 timeslots
● 0x12: inloops at VC-12 timeslots
● 0x13: outloops at VC-12 timeslots
● 0x14: outloops at IF ports
● 0x15: inloops at IF ports
● 0x16: inloops at RF ports
● 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.
10.2.195 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 order path error crosses the preset threshold.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning

period:
● 0x02: 24 hours

Name Meaning
Parameter 2, Parameter 3 Indicate the ID of a performance event

that causes the alarm.
● 0x90: LPBBE
● 0x91: LPES
● 0x92: LPSES
● 0x93: LPFEBBE
● 0x94: LPFEES
● 0x95: LPFESES
● 0x96: LPUAS
● 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 order path error crosses the preset threshold.
----End
Related Information
None
10.2.196 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
● 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
occurs details, see 11.2.43 TUPJCHIGH,
TUPJCLOW, and TUPJCNEW.
The TU pointer justification does Go to Cause 2.
not occur

----End
Related Information
None
10.2.197 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
and indicates the lower order path remote receive failure.
Procedure
and indicates the lower order path remote receive failure.
1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None
10.2.198 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
table.
Name Meaning
always 0x01.

Name Meaning
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
10.2.199 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
table.
Name Meaning

Name Meaning

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
10.2.200 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
and indicates the lower order path remote errors.
Procedure
and indicates the lower order path remote errors.
1. Handle the LP_BBE performance event on the opposite NE.
----End
Related Information
None
10.2.201 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
table.
Name Meaning
always 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
10.2.202 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
table.
Name Meaning

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
10.2.203 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
and indicates the lower order path remote failure.
Procedure
and indicates the lower order path remote failure.
1. Handle the lower order path alarm on the opposite NE.
----End

Related Information
None
10.2.204 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
by the remote site.
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

10.2.205 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
table.
Name Meaning
always 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
by the remote site.
Procedure
Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site
by the remote site.
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
10.2.206 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
table.
Name Meaning

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

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

10.2.209 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
table.
Name Meaning
always 0x01.

None
Possible Causes
● 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.
● 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
10.2.210 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
table.
Name Meaning

None
Possible Causes
● Cause 1: Byte J1 to be received at the local site does not match with byte J1
to be transmitted at the opposite site.
● 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 at the opposite site.
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
10.2.211 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.
● 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.
● 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 Configure services for the
not configured with services tributary path at the remote
site.
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
10.2.212 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
table.
Name Meaning
always 0x01.

Name Meaning

If the alarm is generated due to incorrect service configurations, the services are
interrupted.
Possible Causes
the tributary path at the remote site is not configured with services.
● Cause 2: The cross-connection configuration at the intermediate nodes is
incorrect.
Procedure
tributary path at the remote site is not configured with services.
1. Check whether the tributary path at the remote site is configured with
If... Then...
The tributary path at the remote site is not Configure
configured with services services.
The tributary path at the remote site is configured Go to Cause 2.
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
10.2.213 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
table.
Name Meaning

The services in the path are unavailable. If the services are configured with
protection, protection switching is triggered.
Possible Causes
the tributary path at the opposite site is not.
● Cause 2: The cross-connection configuration at the intermediate sites is
incorrect.
Procedure
tributary path at the opposite site is not.
1. Check whether the tributary path at the opposite site is configured with
If... Then...
The tributary path at the opposite site is not Configure
configured with services services.
The tributary path at the opposite site is configured Go to Cause 2.
with 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 not, reconfigure the cross-connections. For details, see Querying
TDM Services.
----End
Related Information
None
10.2.214 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
table.
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:
● The switching modes (single-ended or dual-ended) at the local and remote
sites are different.

● The last three bits of the K2 byte are set to the indicated mode.
● 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
10.2.215 LPT_AUTH_FAIL
Description
The LPT_AUTH_FAIL alarm indicates that LPT authentication fails.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the LPT type.
Parameters 2–5 If the LPT type is uniport, these parameters indicate the slot
ID and subboard ID. Otherwise, the value of these parameters
is 0xFFFFFFFF.
Parameters 6–9 If the LPT type is uniport, these parameters indicate the
subboard ID. Otherwise, the value of these parameters is
0xFFFFFFFF.
Parameters 10–12 If the LTP type is uniport, these parameters indicate the port
ID. Otherwise, these parameters indicate the index number of
PW, QINQ, or L2NET.


When the alarm is generated, LPT packet authentication fails, causing a network
fault.
Possible Causes
● Cause 1: LPT packet authentication fails.
Procedure
Step 1 Cause 1: LPT packet authentication fails.
1. Check whether the authentication keys are consistently configured for the
nodes. If not, reconfigure the authentication keys.
2. Check whether a packet attack occurs. If yes, isolate the attack source.
----End
Related Information
None
10.2.216 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
table.
Name Meaning
Parameter 1, Parameter 2 Indicates the board ID.

Name Meaning
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
● 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
10.2.217 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


table.
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
required version. For details, see 7 Part Replacement.
The LPT function is not Delete the configuration of the LPT. For details,
required see LPT Configuration.
----End
Related Information
None
10.2.218 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
table.
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
● Cause 1: The remote port fails due to the alarms such as ETH_LOS and
LSR_NO_FITED, or the remote port is disabled.
● 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 Handle the link fault alarms. Focus on the
occurs R_LOS and MW_LOF alarms and handle them
first.
No link fault alarm Go to Cause 2.
occurs
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
10.2.219 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
● Cause 1: The laser is aged.
● 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
10.2.220 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
● 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. 7.15 Replacing the SFP.
----End
Related Information
None
10.2.221 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
● Cause 1: The laser is aged.
● Cause 2: The detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The laser is aged.
1. 7.15 Replacing the SFP.
Step 2 Cause 2: The detection circuit of the board is faulty.
1. Replacing the alarm Board.
----End

Related Information
None
10.2.222 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
table.
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
● Cause 1: The clock configuration is incorrect.
● Cause 2: All the clock sources in the clock source priority table fail.
● Cause 3: A fiber cut or a cable cut occurs.
● Cause 4: The synchronization source is set to the manual reversion mode.
● Cause 5: No input is available from the external clock source.
● Cause 6: The board is faulty.
Procedure
1. Cause 1: The clock configuration is incorrect.

a. 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.
2. Cause 2: All the clock sources in the clock source priority table fail.
a. Troubleshoot the synchronization sources based on the clock source
priority table.
If... Then...
The synchronization source is an Handle the EXT_SYNC_LOS alarm.

external clock

line clock the line board.

IF clock the IF board.

tributary clock the tributary board.

Ethernet clock the Ethernet board.
3. Cause 3: A fiber cut or a cable cut occurs.

a. Connect the fiber or cable properly.
4. Cause 4: The synchronization source is set to the manual reversion mode.
a. See Modifying the Recovery Parameter of the Clock Source, and set the
clock source to the automatic reversion mode.
5. Cause 5: No input is available from the external clock source.
a. See Configuring Clock Sources for External Clock Output, and configure
the clock source that provides external clock signals.
6. Cause 6: The board is faulty.
a. Replace the board.
Related Information
None

10.2.223 MAC_EXT_EXC
Description
The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the threshold crossing type.

● 0x01: ETHDROP threshold crossing
● 0x02: ETHEXCCOL threshold crossing
● 0x03: RXBBAD threshold crossing

When the MAC_EXT_EXC alarm occurs, the performance of services degrades.
Possible Causes
● Cause 1: ETHDROP threshold crossing. The number of packet loss events
crosses the upper threshold.
● Cause 2: ETHEXCCOL threshold crossing. The number of frames unsuccessfully
transmitted after successive collisions crosses the upper threshold.
● Cause 3: RXBBAD threshold crossing. The number of bytes in received bad
packets crosses the upper threshold.
Procedure
1. Check whether the working modes of the ports at the transmit and receive
ends are the same.
a. 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
receive ends work in different ports at the transmit and receive
modes or in half-duplex mode ends to full-duplex or auto-
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.
2. Handle the problem that the opposite site transmits packets abnormally.
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.
4. Replace the faulty board.
Related Information
None
10.2.224 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
Attribute
Parameters
table.

Name Meaning
Parameter 1 ● 0x00: indicates that a performance threshold is crossed.

● 0x01: indicates bit-error-triggered switching.

When the MAC_FCS_EXC alarm occurs, the performance of services degrades.
Possible Causes
● Cause 1: The performance of the line signals degrades.
● Cause 2: The input optical power is abnormal.
● 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 9.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 connectors and the receive port of the processing board.For
details, see 9.13 Cleaning Fiber Connectors and Adapters.
----End
Related Information
None
10.2.225 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
● Cause 1: Line signals degrade.
● Cause 2: Input optical power is abnormal.
● 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 9.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 9.13 Cleaning Fiber Connectors and Adapters.
----End
Related Information
None
10.2.226 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that module communicates
abnormally.

Attribute
Parameters
table.
Name Meaning
Parameter 1 For the SCC board, Parameter 1 indicates the virtual slot ID of the
module that fails to communicate with the central switching board.
For the interface board, 0x11 indicates that the communication
between the SCC board and ARM interface board fails.

The related operations cannot be performed by using the NMS and the
performance information of each module cannot be queried.
Possible Causes
● Cause 1: The software processing of the related modules of the board is
faulty.
● 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 9.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 7.11 Replacing the System
Control, Switching and Timing Board.
----End
Related Information
None

10.2.227 MOD_TYPE_MISMATCH
Description
The MOD_TYPE_MISMATCH alarm indicates that a mismatched port module is
detected.
Attribute

Critical Maloperation
Parameters
table.
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 Replace the optical/electrical
the same as the actual type of the SFP SFP module. Ensure that the
module new SFP module is of the correct
type.

If... Then...
The preset type of the SFP module is Reset the type of the SFP
different from the actual type of the module.
SFP module
----End
Related Information
None
10.2.228 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
table.
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
● Cause 1: The signal quality of the MP group members deteriorates.
● 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
2. If the alarm persists, replace the cable connecting to the port that reports the
alarm. Then, check whether the alarm is cleared.
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
10.2.229 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
table.

Name Meaning
Parameter 1 Indicates the cause of the failure.

● 0x00: unknown
● 0x01: indicates that the number of the MP group members is
less than the specified number.
● 0x02: indicates that the configurations at both ends of the MP
group are inconsistent.
● 0x03: indicates that the NCP protocol of the MP group is
running improperly.

● When this alarm occurs, all services that the MP group carries are interrupted.
● 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
● Cause 1: The number of the valid activated MP group members is less than
that of the minimum activated links.
● Cause 2: The configurations at both ends of the MP group are inconsistent.
● Cause 3: The NCP protocol on the member links of the MP group is running
improperly.
● Cause 4: The physical link is interrupted.
● 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
10.2.230 MPLSLDPSESSIONDOWN
Description
The MPLSLDPSESSIONDOWN alarm indicates the interruption of an LDP session.
Attribute
Parameters
table.
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
● Cause 1: Parameters configured for the service interfaces are incorrect.
● Cause 2: The LDP configurations at both ends are inconsistent.
● Cause 3: The link between the local NE and its neighbor NE is faulty.
● 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.

1. Rectify the fault.
----End
Related Information
None
10.2.231 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
table.
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.

● 0x01: ingress label
● 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

10.2.232 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

10.2.233 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

10.2.234 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 Rectify the fault on the remote NE.
faulty,
The physical link between the local NE Rectify the fault on the physical link.
and the remote NE is faulty,
The bandwidth allocated to the PW is Increase the bandwidth of the PW.

fully occupied,
----End
Related Information
None

10.2.235 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
Parameters
None

Services may be interrupted if excessive redundant packets are received.
Possible Causes
● Cause 1: Multiple PWs are configured with the same label and PW ID.
● 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
10.2.236 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
10.2.237 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
10.2.238 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
● Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
● Cause 2: The OAM is different between the ends of the PW.
● Cause 3: The PW that carries services is faulty.
● Cause 4: The remote NE of the PW is faulty.
● Cause 5: The service interface is configured incorrectly.
● Cause 6: Serious congestion occurs on the network.
Procedure
1. Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
a. Check whether the remote NE of the PW stops transmitting CV/FFD
packets.
If... Then...
The remote NE of the PW stops Enable the CV/FFD detection and

transmitting CV/FFD packets then check whether the alarm
clears.
The remote NE of the PW keeps Go to Cause 2.

transmitting CV/FFD packets
2. Cause 2: The OAM is different between the ends of the PW.

a. 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.
3. Cause 3: The PW that carries services is faulty.
a. 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.
b. 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...
4. Cause 4: The remote NE of the PW is faulty.

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

b. 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...
5. Cause 5: The service interface is configured incorrectly.

a. Check whether the service interface is configured correctly according to
service planning.
b. If not, reconfigure the service interface. Then, check whether the
MPLS_PW_LOCV alarm is cleared.
If... Then...
6. Cause 6: Serious congestion occurs on the network.

a. Check whether the bandwidth allocated to the faulty tunnel is fully
occupied.
b. If yes, increase the bandwidth of the PW or eliminate the sources that
transmit a large amount of invalid data.
7. Check whether the alarm is cleared. If the alarm is not cleared, contact
Related Information
None
10.2.239 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
Name Meaning
Parameters 1-4 (reported upon reception of MPLS Indicate the peer LSR ID.
OAM(Y.1711) packets)
Parameters 1-48 ( reported upon reception of MPLS- Indicate the peer MEG ID.
TP OAM(Y.1731) packets)

Services are interrupted or the packets from other PWs are received.
Possible Causes
● 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
10.2.240 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

Attribute
Parameters
Name Meaning

Services are interrupted or the packets from other PWs are received.
Possible Causes
● 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

----End
Related Information
None

10.2.241 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 switched to the protection PW.
Possible Causes
Cause 1: The OAM function is enabled only on the NE at one end of the PW.
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.
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 10.2.257
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 10.2.238 MPLS_PW_LOCV
occur on NEs at both ends of the PW. If yes, clear them immediately.

----End
Related Information
None
10.2.242 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
10.2.243 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
● Cause 1: The bandwidth of the PW is fully occupied.
● Cause 2: The physical port has bit errors or packet loss.
● 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.
2. If yes, increase the bandwidth of the PW or eliminate the sources that
transmit a large 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
10.2.244 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
● Cause 1: The bandwidth of the PW is fully occupied.
● Cause 2: The physical port has bit errors or packet loss.
● 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.
2. If yes, increase the bandwidth of the PW or eliminate the sources that
transmit a large 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
10.2.245 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
Name Meaning

When this alarm occurs, the MEP receives CCM packets of other PWs.
Possible Causes
● Cause 1: MEG IDs configured on NEs at both ends of the PW are different.
● 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
10.2.246 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
Name Meaning

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

packets of 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
10.2.248 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
10.2.249 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
10.2.250 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
10.2.251 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
10.2.252 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.

● 0x00: NORMAL
● 0x01: SERVER
● 0x02: PEERME
● 0x03: LOCV
● 0x04: MISMATCH
● 0x05: MISMERGE
● 0x06: EXCESS
● 0x06: UNKNOWN


Possible Causes
Cause 1: The upstream NE detects that the physical link that carries the tunnel is
faulty.
Procedure
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 Clear these alarms first.

MW_BER_EXC, MW_BER_SD,
MW_FEC_UNCOR and MW_LOF,
are reported
Optical module-related or board- Clear these alarms first.

related hardware alarms are
generated on the transmit board of
the local NE, such as HARD_BAD
and LSR_NO_FITED
Related Information
None
10.2.253 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
● 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.
● Cause 2: Severe congestion occurs on the network.
● Cause 4: The physical link between the two ends is faulty.
Procedure
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.
a. Check whether the MPLS OAM settings are the same at the two ends.
b. If the MPLS OAM settings are different at the two ends, change them to
the same.
If... Then...
2. Cause 2: Severe congestion occurs on the network.

a. 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
If... Then...

a. 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.
b. If the alarm persists, check whether optical module-related or board-

related hardware alarms are generated on the NEs at both ends of the

link, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms

first.
c. Then, check whether the MPLS_TUNNEL_LOCV alarm clears.
If... Then...
4. Cause 4: The physical link between the two ends is faulty.

a. Check whether any fiber or cable is damaged. If yes, replace the damaged
fiber or cable.
Related Information
None
10.2.254 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
10.2.255 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
Attribute
Parameters
Name Meaning

When this alarm occurs, services are interrupted or packets from other tunnels are
received.
Possible Causes
● 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.

yes, connect the fiber or cable properly.
----End
Related Information
None
10.2.256 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
Name Meaning


When this alarm occurs, the packets from other tunnels are received.
Possible Causes
● 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.

yes, connect the fiber or cable properly.
----End
Related Information
On the NE, the label of each MPLS tunnel is unique.
10.2.257 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
● Cause 1: The OAM function is enabled and the detection mode is auto-
sensing on one end and is disabled on the other end.
● 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
10.2.258 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
10.2.259 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
● Cause 1: Excessive bit errors occur.
● 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
----End
Related Information
None
10.2.260 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
● Cause 1: Excessive bit errors occur.
● 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
10.2.261 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
Name Meaning

When this alarm occurs, the sink NE receives CCM packets of other tunnels.
Possible Causes
● Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel.
● 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
10.2.262 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
Name Meaning

packets of 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
10.2.263 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

packets of 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
10.2.264 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
● Cause 1: The OAM settings differ at the two ends.
● 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
10.2.265 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
Possible Causes
● Cause 1: The transmit unit of the opposite station is faulty.
● Cause 2: The receive unit of the local site is faulty.
Procedure
1. Cause 1: The transmit unit of the opposite station is faulty.
a. 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
b. Replace the board and then check whether the alarm is cleared.
If... Then...
The alarm is cleared after End the fault handling.

replacement

replacement
c. Replace the system control, cross-connect, and timing board at the

opposite end.
If... Then...
The alarm is cleared after the End the fault handling.

board replacement
The alarm persists after the board Go to Cause 2.

replacement
2. Cause 2: The receive unit of the local site is faulty.

Related Information
None
10.2.266 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
table.
Name Meaning

period:
● 0x02: 24 hours
Parameter 2, Parameter 3 Parameter 2 is always 0x00. Parameter

3 indicate the ID of a performance
event that causes the alarm and has
● 0x10: MSBBE
● 0x11: MSES
● 0x12: MSSES
● 0x13: MSFEBBE
● 0x14: MSFEES
● 0x15: MSFESES
● 0x16: MSUAS
● 0x21: MSFEUAS

A large number of bit errors occur in the services, and the services may be
interrupted.
Possible Causes
● Cause 1: Services are interrupted for a long time.
● Cause 2: The MS BER performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
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
5.2.5 Browsing the Performance Event Threshold-Crossing Records.
2. Handle the performance event that crosses the threshold.
----End
Related Information
None
10.2.267 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
10.2.268 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

10.2.269 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
table.
Name Meaning
Parameter 1 Indicates the performance monitoring period:
● 0x02: 24 hours
Parameter 2, Indicate the ID of a performance event that causes the
Parameter 3 alarm.
● 0x2a: AUPJCHIGH
● 0x2b: AUPJCLOW
● 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 5.2.5 Browsing the Performance Event Threshold-
Crossing Records.
----End
Related Information
None
10.2.270 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that the ring network contains
several RPL_OWNER nodes.
Attribute
Parameters
table.
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
1. Cause 1: The related data is configured incorrectly.

a. Reconfigure the ERPS protection. For details, see Creating Ethernet Ring
Protection Instances.
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.
10.2.271 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
● 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

10.2.272 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
● Cause 1: Signal attenuation on the radio link is very heavy.
● Cause 4: An interference event occurs.
Procedure
1. Cause 1: Signal attenuation on the radio link is very heavy.
a. 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 5.3.1 Querying the Historical Transmit Power and Receive Power.

If... Then...
The RSL is lower than the receiver Follow the steps:

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.
The RSL is higher than the Slow up fading occurs. Follow the
specified RSL of the network. The steps:
offset value is tens of decibels. 1. Follow instructions in 9.1.2
The duration is from tens of Scanning Interfering Signals
seconds to several hours. to scan the frequency spectrum
around the radio link and check
for co-frequency interference
and bias-frequency
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.

If... Then...
The RSL is lower than the Slow down fading occurs.

specified RSL of the network. The Generally, the radio link may be
offset value is tens of decibels. faulty in both directions, because
The duration is from tens of slow fading is imposed by the
seconds to several hours. transmission path. Contact the
network planning department to
make the following changes:
● Increase the installation height
of the antenna.
● Reduce the transmission
distance.
● Increase the antenna gain.
● Increase the transmit power.
If the RSL is lower than or higher Fast fading occurs. Contact the
than the specified RSL of the network planning department to
network and if the duration is make the following changes:
from several milliseconds to tens ● Adjust the position of the
of seconds. antenna to block the reflected
wave or make the reflection
point fall on the ground that
has a small reflection
coefficient, therefore reducing
the multipath fading.
● Adjust the RF configuration to
make the links in the 1+1 SD
configuration.
● 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.
● Increase the fading margin.

Locate the fault by looping back the opposite station and excluding the
position one by one. Follow the steps:
a. Perform an inloop on the IF port at the local end. For details, see 9.4.7
Setting Loopback for the IF Board. Check whether the fault at the local
end is rectified after the loopback.
If... Then...
The fault at the opposite end is Replace the IF board.

not rectified

If... Then...
The fault at the opposite end is Go to the next step.

rectified
b. Check whether the cable connector is prepared according to the

requirement. If any cable connector does not meet the requirement,
make a new connector.
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 Replace the ODU at the

not rectified opposite end.
The fault at the opposite end is End the alarm handling.

rectified

If... Then...

not rectified

rectified

If... Then...
The fault at the opposite end is Replace the ODU at the local
not rectified end.

rectified

4. Cause 4: An interference event occurs.

a. Follow instructions in 9.1.2 Scanning Interfering Signals to scan the
frequency spectrum around the radio link and check for co-frequency
interference and bias-frequency interference.
b. Use a spectrum analyzer to analyze the interference source.
c. Contact the spectrum management department to clear the interference
spectrum or change plans to minimize the interference.
Related Information
None
10.2.273 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

If... Then...

the requirement.
range.
requirement.
and bias-frequency
interference.
the interference.

If... Then...

of the antenna.
distance.
configuration.
other antenna.

If... Then...

not rectified

If... Then...

rectified

If... Then...


rectified

If... Then...

not rectified

rectified

If... Then...
not rectified end.

rectified


Related Information
None
10.2.274 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
Critical Equipment Alarm
Parameters
The Alarm Details field displays the related parameters of the alarm. The alarm
parameter2...parameterN. The following table provides details about each
parameter.

Name Meaning
Parameter 1 Indicates the cause of the fault.

● 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.
● 0x02: The AM enabling is different.
● 0x03: The 1588 overhead enabling
is different.
● 0x04: The modulation mode is
different.
● 0x05: The service mode is different.
● 0x06: The number of STM-1 signals
is different.
● 0x09: The IP header compression
enabling is different.
● 0x0A: AES configurations at two
ends of a link are inconsistent.
● 0x10: The IF board or its working
mode does not match the type of
the RF unit.
● 0x12: Configurations of enhanced
compression at both ends of a link
are inconsistent.
● 0x13: The ATPC enabling status is
different on both ends of a link.
● 0x15: The IF link latency modes are
inconsistent.
● 0x16: Port 1 on the XMC-5D ODU is
connected to port 2 on the dual-
port IF board.
● 0x17: The sink port for IF
convergence is connected to the
slave port (IF2 port) of XMC-5D
ODU.
● 0x19: The ODU's multiplexing mode
does not match the IF cable
connection mode.

Name Meaning
Parameter 2 When the value of Parameter 1 is

0x09:
● 0x01: The air interface compression
at L2 is different.
● 0x02: The air interface compression
at L3 is different.
When the value of Parameter 1 is
0x0A:
● 0x01: AES is enabled only at one
end of a link.
● 0x02: AES message authentication
codes (MACs) are inconsistent at
both ends of a link.
When the value of Parameter 1 is
0x12:
● 0x01: The enabling/disabling
statuses of enhanced compression
for CS7 queues are inconsistent at
for CS6 queues are inconsistent at
for EF queues are inconsistent at
for AF4 queues are inconsistent at

Name Meaning
for BE queues are inconsistent at

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.
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
● 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.
● Cause 2: The AM enabling is different on both ends of a radio link.
● Cause 3: The 1588 overhead enabling is different on both ends of a radio link.
● Cause 4: The modulation mode is different on both ends of a radio link.
● Cause 5: The service mode is different on both ends of a radio link.
● Cause 6: The number of STM-1 signals is different on both ends of a radio
link.
● Cause 7: The IP header compression is different on both ends of a radio link.
● Cause 8: The AES configuration is different on both ends of a radio link.
● Cause 9: The IF board or its working mode does not match the type of the RF
unit.
● Cause 10: The enhanced compression status (enabled or disabled) is different
at the two ends of a radio link.
● Cause 11: The ATPC enabling status is different on both ends of a radio link.
● Cause 12: The IF link latency modes are inconsistent.
Procedure
1. Determine the possible cause of the alarm according to the alarm parameters.
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.
Related Information
If both the MW_CFG_MISMATCH and MW_LOF alarms are generated,
preferentially handle the MW_LOF alarm.

10.2.275 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
● Cause 1: The continuous wave function is enabled.
● Cause 2: The MW_LOF alarm exists on the radio link and an outloop is
performed on the IF port or composite port.
● 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 9.4.7 Setting Loopback for the IF
Board.
2. Clear the MW_LOF alarm.
Step 3 Cause 3: The IF unit is faulty.

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

10.2.276 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
table.
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
10.2.277 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

If... Then...

the requirement.
range.
requirement.
and bias-frequency
interference.
the interference.

If... Then...

of the antenna.
distance.
configuration.
other antenna.

If... Then...

not rectified

If... Then...

rectified

If... Then...


rectified

If... Then...

not rectified

rectified

If... Then...
not rectified end.

rectified


Related Information
None
10.2.278 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
● Cause 1: The link ID of the local site does not match with the link ID of the
opposite station.
● 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.
● Cause 3: The antenna receives the radio signals from the other stations,
because the direction of the antenna is set incorrectly.
● 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 Delete the working XPIC group

not meet the requirement of the that is configured incorrectly and
planning create the other working XPIC
group again.
The polarization direction meets Go to the next step.

the 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
requirement of the planning the XPIC IF board according to the
planning. For details, see Creating
an XPIC Working Group.
The link ID meets the requirement Go to the next step.

of 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.
10.2.279 MW_LINK_INTERFERENCE
Description
The MW_LINK_INTERFERENCE alarm indicates that air interface interference exists
on the microwave link. This alarm is reported when an NE detects interference
(multipath interference or co-channel interference) over the air interface of the
microwave link.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of interference over

the air interface.
● 0x01: multi-path selective fading.
● 0x02: in-band channel interference.

If interference occurs over the air interface of the microwave link, services carried
over the port generating the alarm may experience bit errors or even be
interrupted.
Possible Causes
● Cause 1: The NE detects multipath selective fading over the air interface of
the microwave link.
● Cause 2: The NE detects in-band channel interference over the air interface of
the microwave link.

Procedure
Step 1 Cause 1: The NE detects multipath selective fading over the air interface of the
microwave link.
1. Check antenna installation and verify whether the elevation of the antenna
meets requirements.
If... Then...
Requirements are not met Adjust the elevation of the antenna.
Requirements are met Go to the next step.
2. Add 1+1 SD protection groups as planned. For details, see Creating an IF 1+1
Protection Group.
Step 2 Cause 2: The NE detects in-band channel interference over the air interface of the
microwave link.
1. Remove the interference source. If the interference source cannot be removed,
replan frequency information to avoid the interference source.
support engineers.
----End
Related Information
None
10.2.280 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
● Cause 1: The other alarms are generated.
● 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.
● 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.
● Cause 6: The receive power of the ODU is abnormal.
Procedure
1. Cause 1: The other alarms are generated.
a. 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
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.
a. 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.
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.
a. Ensure that the type of the ODU at the local site is consistent with the
type of the ODU at the opposite station.

b. 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.
a. 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
▪ BD_STATUS
▪ VOLT_LOS
▪ IF_CABLE_OPEN
▪ RADIO_MUTE
▪ RADIO_TSL_HIGH
▪ RADIO_TSL_LOW
▪ TEMP_ALARM
b. Locate the fault by looping back the opposite station.
Follow the steps:
i. erform an inloop on the IF port at the opposite end. For details, see
9.4.7 Setting Loopback for the IF Board. Check whether the fault at
the opposite end is rectified after the loopback.
If... Then...

not rectified

rectified
ii. Check whether the cable connector is prepared according to the

iii. Check whether the IF cable is wet, broken, or pressed. Replace the
cable that does not meet the requirement.
iv. Then, check whether the fault at the opposite end is rectified.
If... Then...


rectified


a. Locate the fault by looping back the opposite station.
Follow the steps:
i. Perform an inloop on the IF port at the local end. For details, see
9.4.7 Setting Loopback for the IF Board. Check whether the fault at
the local end is rectified after the loopback.
If... Then...

not rectified

rectified
ii. Check whether the cable connector is prepared according to the

iii. Check whether the IF cable is wet, broken, or pressed. Replace the
cable that does not meet the requirement.
iv. Check whether the fault at the local end is rectified.
If... Then...
not rectified end.

rectified
6. Cause 6: The receive power of the ODU is abnormal.

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

the requirement.
range.
requirement.
offset value is tens of decibels. 1. Check for co-channel
The duration is from tens of interference. For details, see
seconds to several hours. 9.1.2 Scanning Interfering
Signals.
the interference.

If... Then...

of the antenna.
distance.
configuration.
other antenna.

Follow the steps:
a. Check for co-channel interference. For details, see 9.1.2 Scanning
Interfering Signals.

Related Information
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.
10.2.281 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 905 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 905 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:
● MW_LOF
● R_LOF

● R_LOC
● MW_FEC_UNCOR
● XPIC_LOS
● MW_BER_SD
● MW_BER_EXC
● If RTN 905 are cascaded at the remote end to implement the PLA function,
the remote NE may report an NB_UNREACHABLE alarm.
----End
Related Information
None
10.2.282 NEIP_CONFUSION
Description
The NEIP_CONFUSION alarm indicates an NE IP address conflict. (Several NEs use
the same IP address.)
Attribute
Parameters
table.
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:

● Case 1: The NE IP address on the network conflicts with the local NE IP

address, access control IP address, or fixed IP address.
● Case 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
1. Case 1: The NE IP address on the network conflicts with the local NE IP
address, access control IP address, or fixed IP address.
a. Perform the following operations based on actual conditions.
If... Then...
The NE IP address on the network Change the local/peer NE IP

conflicts with the local NE IP address or access control IP
address, access control IP address, address based on the network
or fixed IP address. plan. For details, see Setting NE IP
Communication Parameters.
The NE IP address on the network Modify the peer NE IP address. For

conflicts with the fixed IP address details, see Setting NE IP
(192.168.102.1). Communication Parameters.
2. Case 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.
a. Determine whether the user wants to disconnect the fiber or network
cable.
If... Then...
The user wants to disconnect the Disconnect the fiber or network

fiber or network cable, cable. Then check whether the
alarm is cleared. If the alarm
persists, go to 4.
The user does not want to Go to 3.b.

disconnect the fiber or network
cable,
b. Determine the DCN type according to the network plan, and perform
operations accordingly.
If... Then...
Inband DCN is used, Disable the DNC port between the

directly connected ports. For
details, see Configuring Port DCN
in Reference. Then check whether
the alarm is cleared. If the alarm
persists, go to 4.

If... Then...
Outband DCN is used, Disable the DCC channel between

the directly connected ports. For
details, see Configuring the DCC
Channel in Reference. Then check
whether the alarm is cleared. If
the alarm persists, go to 4.
Related Information
The NMS displays only one such alarm when multiple NEIP_CONFUSION alarms
are reported for the same NE. The extended alarm parameter indicates the
NEIP_CONFUSION alarm that is the most recently reported. You can check Alarm
Log to view information about all the NEIP_CONFUSION alarms reported for the
NE.
10.2.283 NE_DCN_MODE
Description
The NE_DCN_MODE alarm indicates that the device enters the DCN mode when
encountering an exception during an upgrade.
Attribute
Parameters
None


When the NE_DCN_MODE alarm is generated, services are interrupted and the
device enters the maintenance mode.
Possible Causes
● Cause 1: During an upgrade, when the database is lost or damaged, the
device enters the DCN mode.
● Cause 2: After the device is rolled back from an upgrade, if it becomes
unreachable to the NMS for a long time, the device enters the DCN mode.
● Cause 3: During an upgrade, the device resets repeatedly, causing it to enter
the DCN mode.
Procedure
Step 1 Cause 1: During an upgrade, when the database is lost or damaged, the device
enters the DCN mode.
1. If the database has been backed up, restore it. For details, see 8 Database
Backup and Restoration.
2. If the database has not been backed up, reset the device and configure
services again.
Step 2 Cause 2: After the device is rolled back from an upgrade, if it becomes
unreachable to the NMS for a long time, the device enters the DCN mode.
Perform the same operations as in Step 1.
Step 3 Cause 3: During an upgrade, the device resets repeatedly, causing it to enter the
DCN mode.
1. Perform the rollback operation.
2. Check whether the NE_DCN_MODE alarm is cleared. If the alarm persists,
contact Huawei technical support engineers.
----End
Related Information
None
10.2.284 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
table.
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.

● 0x01: If the first bit is 1, it indicates that the file does
not exist.
● 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
● Cause 1: No new NE software is loaded after the existing NE software is
erased.
● Cause 2: Loading the NE software is unsuccessful.
Procedure
1. Cause 1: No new NE software is loaded after the existing NE software is
erased.
Cause 2: Loading the NE software is unsuccessful.
a. Check whether the alarm is caused by the loading operation.

If... Then...
The alarm is caused by the Contact the Huawei technical

loading operation support engineers to reload the
software.
The alarm is not caused by the Go to the next step.

loading operation

a. For details, see 7.11 Replacing the System Control, Switching and
Timing Board.
Related Information
None
10.2.285 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.
● This alarm occurs when the first software system in the system control,
switching, and timing board is inconsistent with the second software system.
● This alarms occurs when the time for which the system waits after the
software package is loaded exceeds 24 hours.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the location of the file.

● 0x01: the files in the flash memory
● 0x02: the software that is currently
running
● 0x03: the software in the CF card
Parameter 2, Parameter 3 Indicate the IDs of the inconsistent

files in the flash memory of the system
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.

● 0x04: The file versions in the master
and slave areas of a single system
control board are inconsistent.
● 0x08: The file versions in the active
and standby system control boards
are inconsistent.
● 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
● Cause 1: The software running on the active and standby SCC boards has
different versions.
● Cause 2: The software stored in the ofs1 and ofs2 areas of the active SCC
board has different versions.
● Cause 3: The software stored in the mapping directories of active and standby
SCC boards has different versions.
● 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
----End
Related Information
None
10.2.286 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the board software is lost.
Attribute
Parameters
table.

Name Meaning
Parameter 2, Parameter 3 Indicates the number of the lost file.

● If the board software is lost, the board fails to work normally.
● 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
10.2.287 NP1_MANUAL_STOP
Description
The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol
is disabled manually.
Attribute
Parameters
table.
Name Meaning
Parameter 1, Indicates the ID of the alarmed protection group. For
Parameter 2 example, 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
10.2.288 NP1_SW_FAIL
Description
The NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.
Attribute

Parameters
table.
Name Meaning
Parameter 1, Indicates the ID of the alarmed protection group. For
protection group 1.

The services cannot be switched. If the current paths are unavailable, the services
are interrupted.

Possible Causes
● Cause 1: The parameters of the N+1 protection for the alarmed node are set
incorrectly.
● 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 Set the parameters of the N+1
are set incorrectly protection correctly.
The parameters of the N+1 protection Go to Cause 2.
are set 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 End the alarm handling.
protocol is restarted.
The alarm persists after the protocol Contact the Huawei technical
is restarted support engineers to handle the
alarm.
----End
Related Information
None
10.2.289 NP1_SW_INDI
Description
The NP1_SW_INDI is an alarm indicating that the N+1 protection switching is
detected.
Attribute


Parameters
table.
Name Meaning
Parameter1, Indicates the ID of the alarmed protection group. For
protection group 1.

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
10.2.290 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
● Cause 1: The NTP server is not configured or is configured incorrectly.
● Cause 2: The NTP server cannot communicate with the NE.
● 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
10.2.291 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
● 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.
● 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 alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and
B3_EXC.
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
9.6.1 Cold Reset.
2. If the OCD alarm persists, replace the alarmed board. For details, see 7.6
----End
Related Information
None
10.2.292 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


table.
Name Meaning
Parameter 1 Indicates the cause of the alarm.
● 0x01: The internal current loop of the storage battery is broken.

● 0x02: The recharge current of the storage battery is very high.
● 0x03: The storage battery is discharged unevenly.

The equipment may fail to work normally, or event the equipment is damaged.
Possible Causes
● Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.
● Cause 2: The positive and negative polarities of the storage battery are
connected inversely.
● Cause 3: The power module frame is faulty.
● Cause 4: The power monitoring module is faulty.
● 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
reported solution to the ODC_MDL_ABN alarm.

If... Then...
The ODC_MDL_ABN alarm is not Replace the power module.
reported
----End
Related Information
None
10.2.293 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
table.
Name Meaning
● 0x01: power-off due to low voltage
● 0x02: power-off due to NMS control
● 0x03: power-off due to human interference
● 0x04: power-off due to high temperature

The equipment does not have backup a power supply.
Possible Causes
● Cause 1 of power-off due to NMS control: The storage battery fails to provide
power for the equipment due to NMS control.
● Cause 1 of power-off due to local human interference: The BAT button on the
front panel of the PMU is set to OFF.

● Cause 1 of power-off due to low voltage: The AC input power is abnormal.

● Cause 2 of power-off due to low voltage: The power module is faulty.
● Cause 3 of power-off due to low voltage: The power monitoring module is
faulty.
● 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.
● Cause 2 of power-off due to high temperature: The temperature of the
storage battery is very high.
● 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 Connect the cable
incorrect. properly.
The AC power cable is deteriorated and Replace the cable.
damaged.

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
appropriate alarm is 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
10.2.294 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
● Cause 1: The door access alarm is set incorrectly.
● Cause 2: The cabinet door is open.
● Cause 3: The cable between the door sensor and the monitor device is
connected incorrectly.
● Cause 4: The door sensor is faulty.
● Cause 5: The monitor device is faulty.
● 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
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 Connect the cable properly.
loose
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...

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
10.2.295 ODC_FAN_FAILED
Description
The ODC_FAN_FAILED is an alarm indicating that the fan is faulty.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the position of the fault.
● 0x01: The internal fan is faulty.
● 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
● Cause 1: The fan cable is connected incorrectly.

● Cause 2: The fan is faulty.

● 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
10.2.296 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
table.
Name Meaning
● 0x01: The relative humidity is very high.
● 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
● Cause 1: The threshold that results in an alarm is set incorrectly.
● Cause 2: The cable between the humidity sensor and the monitoring
equipment is connected incorrectly.
● Cause 3: The humidity sensor is faulty.
● 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
If... Then...
The humidity threshold is set Perform the operations required when
correctly the alarm is generated due to cause 2.
The humidity threshold is set Set the humidity threshold to an
incorrectly appropriate value.
Step 2 Cause 2: The cable between the humidity sensor and the monitoring equipment is
If... Then...
The cable is connected incorrectly or Connect the cable properly.
is loose
The cable is deteriorated and Handle the exceptions of the cable.
damaged
The cable is not deteriorated and Perform the operations required
damaged when the 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
10.2.297 ODC_LOAD_PWRDOWN
Description
The ODC_LOAD_PWRDOWN is an alarm indicating that the secondary load is
powered off.
Attribute
Parameters
table.
Name Meaning
● 0x01: power-off due to low voltage

● 0x02: power-off due to background control
● 0x03: power-off due to startup in the case of low temperature
● 0x04: power-off due to high temperature

The services on the secondary load are interrupted.
Possible Causes
● Cause 1 of power-off due to NMS control: The load is powered off due to
NMS control.
● Cause 1 of power-off due to low voltage: The AC input power is abnormal.
● Cause 2 of power-off due to low voltage: The power module is faulty.
● Cause 3 of power-off due to low voltage: The power monitoring module is
faulty.

● Cause 1 of power-off due to low temperature: The cabinet temperature is very

low.
● Cause 2 of power-off due to low temperature: The ambient temperature
sensor is faulty.
● 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.
● Cause 2 of power-off due to high temperature: The cabinet temperature is
very high.
● 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 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...
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 Rectify the fault of the heat exchange.
not work properly
The heat exchanger works Perform the operations required when the
properly alarm is 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
The threshold is Perform the operations required when the
appropriate alarm is generated by cause 2 of power-off
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 Rectify the fault of the heat exchange.
not work properly
The heat exchanger works Perform the operations required when the
properly alarm is generated by cause 3 of power-off
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.
10.2.298 ODC_MDL_ABN
Description
The ODC_MDL_ABN is an alarm indicating that the power module is abnormal.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the ID of the alarmed power module.
Parameter 2, Indicates the cause of the alarm.

Parameter 3
● 0x01: The power module is switched off.
● 0x02: The power module is faulty.
● 0x03: The power module stops self-protection.
● 0x04: The power module fails to communicate with the
power monitoring module, or the power module is not in
position.
● 0x05: The number of PSUs configured on the NMS is
incorrect.
● 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
● Cause 1: The number of PSUs configured on the NMS is incorrect.

● Cause 2: The power module is not in position.

● Cause 3: The power module is faulty.
● 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
10.2.299 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
table.

Name Meaning
Parameter 1 Indicates the type of the fault.
● 0x56: The AC input power is very high.
● 0x57: The AC input power is very low.
● 0x58: The DC output power is very high.
● 0x59: The DC output power is very low.
● 0x5b: No AC input power is available.
● 0x5c: The AC power voltage is abnormal.

● If the AC input power voltage is abnormal, the equipment is powered on by
the storage battery and cannot work for a long time.
● If the DC output power voltage is abnormal, the services on the equipment
are interrupted.
Possible Causes
● Cause 1: The AC input power voltage is abnormal.
● 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 Connect the cable properly.
loose
The cable is deteriorated and Handle the exceptions of the
damaged cable.

If... Then...
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 Rectify the fault of the power
power abnormally module at the base station.
The AC power grid distributes the Go to the next step.
power normally
5. The monitoring equipment is faulty.
If... Then...
The monitoring equipment is Rectify the fault of the monitoring
faulty equipment.
The monitoring equipment is Perform the operations required when
not faulty the 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 Rectify the fault of the
sufficient monitoring equipment.
----End
Related Information
None

10.2.300 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
● Cause 1: The smoke alarm is set incorrectly.
● Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.
● Cause 3: The cable between the smoke sensor and the monitoring equipment
is connected incorrectly.
● 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 planning information.
If... Then...
The smoke alarm is set Perform the operations required when
The smoke alarm is set Set the smoke alarm correctly.
incorrectly
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
1. Check whether the cable between the sensor and the monitoring equipment
is connected correctly.

If... Then...
is loose
The cable is deteriorated and Replace the cable.
damaged
damaged when 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
10.2.301 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
table.

Name Meaning
Parameter 1 Indicates the type of the alarm.
● 0x01: AC surge protection alarm
● 0x02: DC surge protection alarm

The AC surge protection function of the cabinet is disabled.
Possible Causes
● Cause 1: The alarm is set incorrectly.
● Cause 2: The cable between the lightning sensor and the monitoring
● Cause 3: The lightning sensor is faulty.
● 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 generated due to cause 2.
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
1. Check the cable connection between the sensor and the monitoring
equipment.
If... Then...
is loose
The cable is deteriorated and Replace the cable.
damaged
to cause 3.
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 Perform the operations required
lightning arrestor works properly when the alarm is generated due
to cause 5.
The alarm output end of the Replace the lightning arrestor.
lightning arrestor does not work
properly
Step 5 Cause 5: The associated monitoring equipment is faulty.

----End
Related Information
None
10.2.302 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
● Cause 1: The TEC cable is connected incorrectly.
● Cause 2: The TEC module is faulty.
● 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
10.2.303 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
table.

Name Meaning
● 0x01: The ambient temperature is higher than the upper

threshold.
● 0x01: The ambient temperature is lower than the lower
threshold.
Parameter 2 Indicates the temperature type.
● 0x01: The temperature at the air outlet is very high or low.

● 0x0b: Ambient temperature 1 is very high or low.
● 0x0c: Ambient temperature 2 is very high or low.
● 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
● Cause 1: The temperature threshold that results in an alarm is set incorrectly.
● Cause 2: The cable between the temperature sensor and the monitoring
● 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
If... Then...
The temperature alarm is set Perform the operations required when
The temperature alarm is set Set the temperature alarm correctly.
incorrectly
Step 2 Cause 2: The cable between the temperature sensor and the monitoring

If... Then...
The cable is connected incorrectly Connect the cable properly.
or is loose
damaged
to cause 3.
Step 3 Cause 3: The temperature sensor is faulty.

If... Then...

----End
Related Information
None
10.2.304 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
● Cause 1: The water alarm is set incorrectly.
● Cause 2: Certain water enters the cabinet.
● Cause 3: The cable between the water sensor and the monitoring equipment
is connected incorrectly.
● 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 planning information.
If... Then...
The water alarm is set Perform the operations required when
The water alarm is set Set the water alarm correctly.
incorrectly
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
If... Then...
The cable is connected incorrectly Connect the cable properly.
or is loose
damaged
to cause 4.
Step 4 Cause 4: The sensor is faulty.

----End
Related Information
None

10.2.305 OSPFNBRSTATECHANGE
Description
The OSPFNBRSTATECHANGE alarm indicates that the OSPF neighbor state
changes.
Attribute

Parameters
table.
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.
● 0x01: Down
● 0x02: Attempt
● 0x03: Init
● 0x04: 2-Way
● 0x05: ExStart
● 0x06: Exchange
● 0x07: Loading
● 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.

Name Meaning
Parameter 101 to Parameter Indicate the name of the VPN instance.
131
Parameter 132 to Parameter Indicate the alarm cause.
135

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.
State changes from Down to Full: Down > Init > 2-way > Exstart > Exchange > Loading
>Full
Possible Causes
● Cause 1: OSPF configurations are changed at the peer end.
● Cause 2: The peer port is faulty.
● 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

10.2.306 OUT_PWR_ABN
Description
The OUT_PWR_ABN alarm indicates that the output optical power is abnormal.
Attribute
Parameters
table.
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
● Cause 1: The output optical power is too high or low.
Procedure
1. Cause 1: The output optical power is too high or low.
a. Browse optical power performance events.
If... Then...
The output optical power does not Replace the optical module.
meet the requirement

If... Then...
The output optical power is too Add a proper attenuator to reduce

high the input optical power.
2. Cause 2: A board is faulty.

Related Information
None
10.2.307 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
● Cause 1: The input optical power is excessively high.
● 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 Remove and re-insert the optical
good contact with the optical module.
port,
The optical module is faulty, Replace the optical module. For the
method, see 7.15 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
10.2.308 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
● Cause 1: The input optical power is excessively low.
● 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 Remove and re-insert the optical
good contact with the optical module.
port,
The optical module is faulty, Replace the optical module. For the
method, see 7.15 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
10.2.309 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
● Cause 1: The air outlet temperature sensor is faulty.
● 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...

Step 4 Cause 4: The air outlet temperature sensor is not installed.

1. Install the air outlet temperature sensor.
----End
Related Information
None
10.2.310 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
● Cause 1: The external cycling air outlet temperature sensor is faulty.
● 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
10.2.311 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
● Cause 1: The default user password has not been changed.
● Cause 2: The default WLAN password has not been changed.
● 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
10.2.312 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
10.2.313 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
10.2.314 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

10.2.315 PATCH_OP_TIMEOUT
Description
The PATCH_OP_TIMEOUT alarm indicates that the time for which the system
waits after the patch is downloaded or activated exceeds the specified time.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the current status of the

patch.
● 0x04 indicates that the patch is in
the downloaded state.
● 0x06 indicates that the patch is in
the installed state.

None
Possible Causes
Cause: The time for which the system waits after the patch is downloaded or
activated exceeds the specified time.
Procedure
Step 1 Check whether the patch package is correct. If yes, perform the activate and
submit operations for it to take effect. Otherwise, perform the rollback operation.
Step 2 Check whether the PATCH_OP_TIMEOUT alarm is cleared. If the alarm persists,
----End

Related Information
None
10.2.316 PATCH_INIT_FAIL
Description
The PATCH_INIT_FAIL alarm indicates that the patch initialization fails.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the cause of the patch

initialization failure:
● 0x01: The version mismatches.
● 0x02: The board type mismatches.
● 0x03: The patch status is incorrect.
● 0x04: The patch file list fails to be
obtained.
● 0x05: The patch file mismatches.
● 0x06: The patch fails to be loaded.
● 0x07: The patch fails to be
activated.
● 0x08: The patch fails to be
submitted.
● 0xff: Other causes.

The patch function cannot take effect as scheduled.

Possible Causes
● Cause 1: The patch file, version, and board type mismatch.
● Cause 2: The patch file fails to be loaded, activated or submitted during
initialization.
Procedure
Step 1 Cause 1: The patch file, version, and board type mismatch.
1. Delete the incorrect patch. The PATCH_INIT_FAIL alarm will be cleared after
the incorrect patch is deleted.
2. Verify that the patch file, version and board type match the current
equipment. Then, reinstall the patch.
Step 2 Cause 2: The patch file fails to be loaded, activated or submitted during
initialization.
1. Load, activate, and submit the patch file again.
2. Check whether the PATCH_INIT_FAIL alarm is cleared. If the alarm persists,
----End
Related Information
None
10.2.317 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.
When this alarm is reported, services are not interrupted.

Possible Causes
● Cause 1: A patch package is incorrect.
● Cause 2: A patch package has been damaged.
● Cause 3: A patch package has been deleted.
Procedure
Step 1 Load a correct patch package.
----End
Related Information
None
10.2.318 PATCH_MATCH_NO_START
Description
The PATCH_MATCH_NO_START alarm indicates that the system control board
does not initiate board patch matching.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the slot ID of the system

control board that fails to initiate the
matching.

Name Meaning
Parameter 2 Indicates the reason why the system

control board fails to initate the
matching.
● 0x01: indicates that the primary
status of loading a software
package is Normal but the
secondary status of loading the
software package is not Normal.
● 0x02: indicats that the system
control board is replaced.
● 0x03: indicates that the patch is
being restored externally.
● 0x04: indicates that the software
switch is on (this is not reported if
the status of loading a software
package is not Normal).
● 0x05: indicates that the patch
status on the NE side is not Run.
● 0x06: indicates that the patch
package check result is incorrect.
● 0xFF: indicates an unknown reason.

This alarm does not affect services. Software upgrade in patch package loading
mode is not affected, but a patch package fails to be matched for the board.
Possible Causes
● Cause 1: The system control board does not initiate board patch matching.
Procedure
Step 1 Cause 1: The system control board does not initiate board patch matching.
1. Check whether the status of loading a software package is correct. If the
primary status is Normal but the secondary status is not Normal, wait several
minutes.
2. Check whether the alarm is cleared. If not, reload the software package.
3. Check whether the alarm is cleared. If not, contact Huawei technical support
engineers.
----End
Related Information
None

10.2.319 PING_LOS
Description
The PING_LOS alarm indicates that IP Ping fails.
Attribute
Parameters
table.
Name Meaning
Parameters 1–4 Indicate the destination IP address.
Parameter 5 Indicates the IP Ping type.

● 0x00: indicates the local end.
● 0x01: indicates the remote end.
Parameters 6–7 Indicate the VLAN ID.
Parameter 8 Indicates the VLAN priority.
Parameters 9–10 Indicate the inner VLAN ID.
Parameter 11 Indicates the inner VLAN priority.
Parameter 12 Indicates the alarm type.

● 0x01: indicates that sending Ping
packets fails or times out.
● 0x03: indicates that the Ping packet
checksum is incorrect.
● 0x12–0xff: reserved for future use.

None
Possible Causes
● Cause 1: The Ping packet checksum is incorrect.

● Cause 2: The Ping operation times out.

● Cause 3: Sending Ping packets fails.
Procedure
Step 1 Cause 1: The Ping packet checksum is incorrect.
1. Check whether there are links from the local to peer end that encounter bit
errors.
2. Check whether the ETH_LOS and ETH_LINK_DOWN alarms are generated. If
yes, clear these alarms.
Step 2 Cause 2: The Ping operation times out.

1. Check whether services are faulty. If yes, rectify the fault following the
instructions provided in 9.2 Ethernet Service Troubleshooting.
Step 3 Cause 3: Sending Ping packets fails.

1. Check whether the dynamic ARP list contains the destination IP address. If
not, check whether the static ARP list contains the destination IP address. If
not, add the destination IP address to the static ARP list.
----End
Related Information
None
10.2.320 PING_ARP_MISMATCH
Description
The PING_ARP_MISMATCH alarm indicates that the dynamic ARP and static ARP
conflict in the ping operation.
Attribute
Parameters
table.

Name Meaning
Parameters 1–4 Indicate the IP addresses that conflict.

None
Possible Causes
The MAC addresses learnt by the static ARP conflicts with that learnt by the
dynamic ARP.
Procedure
Step 1 Check whether the MAC address learnt by the static ARP conflicts with that learnt
by the dynamic ARP. If yes, remove the static ARP. For details, see Remove the
static ARP.
----End
Related Information
None
10.2.321 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.
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
10.2.322 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
table.
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.

Name Meaning
Parameter 4 Indicates the fault type.

● 0x01: indicates that another service alarm exists.
● 0x02: indicates that the protection group is in the lockout state.
● 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
● Cause 1: A service or hardware alarm exists on the board that has reported
the alarm.
● 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 10.2.349
R_LOF, 10.2.280 MW_LOF, and 10.2.134 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,
----End
Related Information
None
10.2.323 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
table.
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:
● 0x00: The PLA group is not configured on the IF board of
the peer NE.
● 0x03: The number of member links in the PLA group is
different at both ends.
● 0x04: Local member ports and peer member ports do not
belong to the same PLA group.
● 0x06: Configurations of enhanced compression for CS7
queues in PLA groups at both ends of a microwave link are
inconsistent.
● 0x07: Configurations of enhanced compression for CS6
inconsistent.
● 0x08: Configurations of enhanced compression for EF
inconsistent.
● 0x09: Configurations of enhanced compression for AF4
inconsistent.
● 0x0A: Configurations of enhanced compression for AF3
inconsistent.
● 0x0B: Configurations of enhanced compression for AF2
inconsistent.
● 0x0C: Configurations of enhanced compression for AF1
inconsistent.
● 0x0D: Configurations of enhanced compression for BE
inconsistent.
● 0x0E: The PLA capacities are inconsistent at the two ends of
a microwave link.
● 0x0F: The PLA scheduling types are inconsistent at the two
ends of a microwave link.
● 0x10: The PLA priority thresholds are inconsistent at the two
ends of a microwave link.
● 0x11: The priorities of PLA members are inconsistent at the
two ends of a microwave link.
● 0x12: The local-end PLA member port and the remote-end
PLA member port have different port rates.

Name Meaning
● 0x13: The channel configurations of PLA members are
inconsistent at the two ends of a link.
● 0x14: The channel configurations of the master and slave
devices in a PLA group are inconsistent.
● 0x17: The CC enabling status is inconsistent in EPLA groups
at two ends of a link.
● 0x18: The bandwidths are inconsistent for the main and
standby NEs.
● 0x19: The versions are inconsistent for the main and standby
NEs.
● 0x1a: The EPLA WTR status of PLA group is inconsistent at
the two ends of a microwave link.
● 0x1b: The minimum number of enabled EPLA links in a PLA
group are inconsistent at the two ends of a microwave link.
● 0x1c: The types of the master and slave PLA groups are
inconsistent.
● 0x80: Under the current or guaranteed capacities of
members in an EPLA or SDB group, the air-interface
Ethernet bandwidth is smaller than the CC packet
bandwidth.
● 0x81: The air-interface capacity configured for a member in
an EPLA/SDB group exceeds the backplane slot bandwidth
of the member.
Parameters 5– When Parameters 3-4 are 0x80,

11
● Parameters 5-6 indicate the slot ID.
● Parameter 7 indicates the subboard ID.
● Parameters 8-9 indicate the port ID.
● Parameters 10-11 indicate the channel ID.

The services carried by the radio link are unavailable.
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
● Cause 1: The PLA group is configured on the local NE, but not configured on
the peer NE.
● Cause 2: Frame header compression is enabled for only one NE.
● Cause 3: The number of member links in the PLA group is different at both
ends.

● Cause 4: Local member ports and peer member ports do not belong to the
same PLA group.
● Cause 5: Enhanced compression is enabled for only one NE.
● Cause 6: The Super EPLA configurations are inconsistent at the two ends of
the microwave link.
● Cause 7: The CC enabling status is different on two ends of the microwave
link.
● Cause 8: Under the current or guaranteed capacity of the microwave link, the
air-interface Ethernet bandwidth is smaller than the CC packet bandwidth.
● Cause 9: The types of the master and slave PLA groups are inconsistent.
● Cause 10: The air-interface capacity configured for a member in an EPLA/SDB
group exceeds the backplane slot bandwidth of the member.
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.
If... Then...
The configurations do not comply Re-configure the PLA group

with the network plan according to the network plan.
The configurations comply with the Verify the IF cable connections

network plan between the IF 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.
Step 7 Cause 7: The CC enabling status is different on two ends of the microwave link.
1. Set the CC enabling status consistently at two ends of the microwave link.
Step 8 Cause 8: Under the current or guaranteed capacity of the microwave link, the air-
interface Ethernet bandwidth is smaller than the CC packet bandwidth.
1. Set the air-interface Ethernet bandwidth to a value larger than 512 (kbit/s)
under the current or guaranteed capacity.
Step 9 Cause 9: The types of the master and slave PLA groups are inconsistent.
1. Delete either of the groups and add a new one of a consistent workgroup
type.
Step 10 Cause 10: The air-interface capacity configured for a member in an EPLA/SDB
group exceeds the backplane slot bandwidth of the member.
1. Configure a lower bandwidth or modulation scheme for the member to keep
the slot capacity within limit.
----End
Related Information
None
10.2.324 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.
The PLA in this section refers to EPLA.
Attribute
Major Service alarm

Parameters
table.
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
10.2.325 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


table.
Name Meaning
Parameter 1 and Parameter 2 Indicate the ID of the Super EPLA

group. For example, 0x00 0x08
indicates that the protection group ID
is 8. For details, see Parameter
Examples.
Parameter 3 to Parameter 6 Indicate the NE ID. For example, 0x00

0x09 0xac 0x02 indicates 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 Parameter 8 Indicate the slot ID of the board. For

example, 0x00 0x01 indicates 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 Parameter 11 Indicate the port ID. For example, 0x00
0x05 indicates port 5.
Parameter 12 and Parameter 13 Indicate the path ID. For example,

0x00 0x01 indicates path 1.
Parameter 14 Indicate the fault cause.

● 0x00: indicates connectivity loss.
● 0x01: indicates a remote fault.
● 0x02: CC loopback.
● 0x03: forced switching.
● 0x04: hardware fault.
● 0x05: link fault.
● 0x06: configuration mismatch.
● 0x07: WTR.
● 0x08: symmetry.

Available bandwidth of the Super EPLA group decreases. If a PLA_DOWN alarm is
also reported, services are interrupted.

Possible Causes
● Cause 1: The general-band microwave link in the super EPLA group at the
local end is faulty.
● Cause 2: An IF board in the super EPLA group at the local end is faulty.
● Cause 3: The E-band microwave link in the super EPLA group at the local end
is faulty.
● Cause 4: The E-band device in the super EPLA group at the local end is faulty.
● Cause 5: The cascaded NE is faulty.
● Cause 6: The cascade port is faulty.
● Cause 7: Loss of connectivity occurs on a member link of the Super EPLA
group.
● 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 10-2 Parameter Example 1
● Parameters 1 and 2 (0x00 0x08) indicate that the protection group ID is 8.

● 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.
● Parameters 7 and 8 (0x00 0x01) indicate that the slot ID is 1.
● Parameter 9 takes a fixed value of 0xff.
● Parameters 10 and 11 (0x00 0x05) indicate that the port ID is 5.
● Parameters 12 and 13 (0x00 0x01) indicate that the path ID is 1.
● Parameter 14 (0x00) indicates that the fault cause is loss of connectivity.
Figure 10-3 Parameter Example 2
● Parameters 1 and 2 (0x00 0x01) indicate that the protection group ID is 1.

● 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.
● Parameters 7 and 8 (0x00 0x04) indicate that the slot ID is 4.
● Parameter 9 takes a fixed value of 0xff.
● Parameters 10 and 11 (0x00 0x01) indicate that the port ID is 1.

10.2.326 PLA_PKT_ERR
Description
The PLA_PKT_ERR alarm indicates that packet reassembly fails in the receive
direction.
Attribute
Major Service alarm
Parameters
table.
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 7.11 Replacing the System Control, Switching and
Timing Board.
----End

Related Information
None
10.2.327 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.
Both GE and FE ports support the PORTMODE_MISMATCH alarm.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Parameter 1, Parameter 2 Indicate the working mode of the FE

port.
● 0x01:10M half-duplex
● 0x02:10M full-duplex

When the PORTMODE_MISMATCH alarm occurs, the service on the local NE is not
affected.

Possible Causes
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
10.2.328 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC alarm indicates that the traffic over a port exceeds its
threshold.
Attribute
Major Service alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the traffic in the receive or transmit direction exceeds its
threshold.
● 0x00: indicates the receive direction.
● 0x01: indicates the transmit direction.

Services are congested.

Possible Causes
● Cause 1: The configured bandwidth limit is too low.
● 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 5.5.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
10.2.329 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE alarm indicates that a SFP module is offline.
Attribute
Parameters
table.

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 Reserved. 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
receive/transmit a service Basic 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

module SFP 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
10.2.330 POWER_ABNORMAL
Description
The POWER_ABNORMAL is an alarm indicating that the input power supply is
abnormal.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the number of the voltage

channel.
● 0x01: the first channel of voltage
● 0x02: the second channel of voltage
Parameter 2 Indicates the type of the alarm.

● 0x00: voltage loss
● 0x01: undervoltage
● 0x02: overvoltage

When the POWER_ABNORMAL alarm occurs, the power supply is abnormal, and
therefore the board may fail to work normally.

Possible Causes
● Cause 1: The power cable is cut, damaged, or incorrectly connected.
● 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
10.2.331 POWER_ALM
Description
The POWER_ALM is an alarm indicating that the power module is abnormal.
Attribute
Parameters
table.

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.
● 0x01: The -5 V power supply is
faulty.
● 0x02: The power supply for the
power amplifier is faulty.
Parameter 2 Indicates the alarm types.

● 0x01: under-voltage
● 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:
● Cause 1: The input power or the PIU is abnormal.
● Cause 2: The power module is abnormal.
If the alarm is reported on the ODU, the cause is as follows:
● 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 7 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 7.16 Replacing an ODU.
----End

Related Information
None
10.2.332 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
table.
Name Meaning
Parameters 1 to 2 Indicate the slot ID.

Name Meaning
Parameters 3 to 4 Indicate the packet type.

● 0x00: LAG
● 0x01: IP Ping
● 0x02: ERPS
● 0x03: MSTP
● 0x04: IGMP
● 0x05: LPT
● 0x06: ARP
● 0x07: DCN
● 0x08: FIBERFIND
● 0x16: LLDP
● 0x1b: TPLB
● 0x1c: PWPING
● 0x1d: LSPTRACE
● 0x1e: LSPPING
● 0x1f: ETHOAM
● 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

10.2.333 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
● Cause 1: Parameter configurations on the opposite port are inconsistent with
those on the local port.
● Cause 2: The network is congested or its quality is poor, which causes
improper running of the LCP protocol.
● 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,
3. For an optical interface, shut down and then start the laser. Then, check
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
10.2.334 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
● 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

10.2.335 PTP_SOURCE_SWITCH
Description
The PTP_SOURCE_SWITCH is an alarm indicating a switchover between PTP time
sources.
Attribute
Parameters
table.
Name Meaning
Parameters 1 and 2 Indicate 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.
Parameters 4 and 5 Indicate the ID of the port before the

switching.
Parameters 6 to 9 Indicate the ID 1 of the grandmaster

clock before the switching.

clock before the switching.
Parameter 14, Parameter 15 Indicate 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.
Parameters 17 and 18 Indicate the ID of the port after the

switching.

clock after the switching.

Name Meaning

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
● Cause 1: The physical link between the local NE and the clock source is faulty.
● Cause 2: Information about the grandmaster clock such as the priority 1,
quality level, and priority 2 has changed.
● 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
10.2.336 PTP_TIME_ADJUST_OFF
Description
The PTP_TIME_ADJUST_OFF alarm indicates that the PTP time adjustment
function is disabled.
Attribute
Minor alarm Equipment Alarm

Parameters
None.

When this alarm occurs, the time of the local NE may fail to be synchronized with
that of the downlink NE, causing bit errors in services.
Possible Causes
Cause 1: The time adjustment function is disabled.
Procedure
Step 1 Cause 1: The time adjustment function is disabled.
1. Enable the time adjustment function.
----End
Related Information
None.
10.2.337 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


parameter2...parameterN. The following table provides details about each
parameter.
Name Meaning
Parameter 1 ● 0x02: indicates that timestamp t1

remains unchanged in three
consecutive seconds.
● 0x03: indicates that timestamp t2
remains unchanged in three
● 0x04: indicates that timestamps t1
and t2 remain unchanged in three
Parameter 2 ● 0x02: indicates that timestamp t3

remains unchanged in 17
● 0x03: indicates that timestamp t4
remains unchanged in 17
● 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
● Cause 1: The P/E attributes are different on the PTP ports of the local and
opposite NEs.
● Cause 2: The transmit NE is faulty.
● 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
10.2.338 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
10.2.339 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
10.2.340 PW_DOWN
Description
The PW_DOWN alarm indicates that a PW is disconnected.
Attribute
Parameters


table.
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
● Cause 1: Configurations are changed at the peer end.
● Cause 2: Severe network congestion occurs.
● 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
10.2.341 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
table.
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
10.2.342 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
table.
Name Meaning
Parameter 1 Indicates the direction in which traffic

is unavailable.
● 0x00: RX direction
● 0x01: TX direction

When this alarm occurs, the PW has no traffic and PW services are interrupted.
Possible Causes
● Cause 1: No service is configured.
● Cause 2: The local services are abnormal and therefore no packet is
transmitted to the peer end.
● Cause 3: The peer services are abnormal and therefore no packet is
transmitted to the local end.
● 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.

If... Then...
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 7
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
10.2.343 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
● Cause 1: The remote NE of the PW is not configured with any protection
group.
● 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
10.2.344 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
ends.
● Cause 2: Certain physical links are incorrectly connected.

Procedure
ends.
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
10.2.345 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
ends.
● Cause 2: Certain physical links are incorrectly connected.
Procedure
ends.
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
10.2.346 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
● Cause 1: The configured protection modes (1+1 protection or 1:1 protection)
differ at the two ends of the PW.
● Cause 2: The configured switching modes (single-ended or dual-ended) differ
at the two ends of the PW.
● 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
10.2.347 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
10.2.348 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
a. At the local end, perform an inloop on the port of the alarmed board. For
details, see 9.4 Software Loopback.
If... Then...
The alarm persists after the Replace the alarmed opposite

loopback board.
The alarm is cleared after the Go to Cause 2.

loopback

a. Replace alarmed opposite board.
If... Then...
The alarm persists after the board Replace the system control,
is replaced switch&timing board at the
opposite end.
Related Information
None

10.2.349 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
● Cause 1: Certain alarms are generated (if the alarm is reported by an IF
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 Go to Cause 3.

is performed
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH
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 Go to Cause 3 or 4

exchange
The line port of the opposite station Troubleshoot the optical fibers.
reports the R_LOF alarm
Step 3 Cause 3: The transmit unit of the opposite station is faulty.

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.

replacement
Step 4 Cause 4: The receive unit of the local site is faulty.

----End
Related Information

10.2.350 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
● Cause 1: Other alarms trigger the R_LOS alarm (if the R_LOS alarm is
reported by an IF board).
● Cause 2: The line performance deteriorates (if the R_LOS alarm is reported by
an SDH line board).
● Cause 3: The TDM cascade cable connection is abnormal (if the R_LOS alarm
is reported by a TDM cascading interface board).
● Cause 4: The transmit unit of the peer NE is faulty.
● Cause 6: No fiber jumper is connected to the optical port on the board that
reports the R_LOS alarm.
● Cause 7: The laser on the peer NE is closed.
● Cause 8: A fiber cut occurs on the transmission line.
● 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.
Step 5 Cause 5: The receive unit of the local NE is faulty.
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.
10.2.351 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

● When this alarm occurs, services are interrupted, and the AIS signal is inserted
on the downstream NE.
● 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
● Cause 1: The transmit cable is faulty, and the fiber connector is loose or
contaminated.

● Cause 2: The receive board on the local NE is faulty.

● 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 Go to Step 3.

abnormal
The transmit optical power of the opposite board is Go to the next step.
normal
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 Go to the next step.
low
The receive optical power of the local board is too Go to Step 2.

high
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 9.13 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 9.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 7.15 Replacing the SFP. Otherwise, replace the faulty board.
For details, see 7.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
10.2.352 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
● Cause 1: The ODU fault of the transmit end causes the abnormal transmit
power.

● Cause 2: The direction of the antenna is deflected.

● Cause 3: The transmission environment changes.
● 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 Go to Cause 2.
the 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 Adjust the direction of the
deflected antenna.
The direction of the antenna is not Go to Cause 3.
deflected
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
changes for re-planning the transmission trail.
The transmission environment Go to Cause 4.
does 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

10.2.353 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
● Cause 1: The other alarms are generated.
● Cause 2: The transmitter of the local site is muted manually.
● Cause 3: The IF board is faulty, causing abnormal IF output.
● 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

10.2.354 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
● Cause 1: Antennas are not aligned during the equipment commissioning.
● 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

10.2.355 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
Possible Causes
● Cause 1: The local ODU is faulty.
● Cause 2: There is a strong interference source nearby.
● Cause 3: The transmit power of the opposite ODU is very high.
Procedure
Step 1 Cause 1: The local ODU is faulty.
1. 7.16 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

10.2.356 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 lower 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
● Cause 1: Other alarms occur at the opposite station.
● Cause 2: The transmit power of the opposite station is very low.
● Cause 3: The local ODU is faulty.
● Cause 5: The transmit and receive frequencies of the local ODU and the peer
ODU do not match.
● Cause 6: The receive power of the ODU is inconsistent in horizontal
polarization direction of the antenna and in the vertical polarization direction.
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.
● RADIO_MUTE
● CONFIG_NOSUPPORT
● RADIO_TSL_LOW
● 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.
Step 4 Cause 4: Signal attenuation on the radio link is very heavy.

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
7 Part Replacement
6. Check whether the antenna gain at both the transmit and receive ends meets
the requirement.
If not, replace the antenna.
Step 5 Cause 5: The transmit and receive frequencies of the local ODU and the peer ODU
do not match.
1. Reconfigure the operating frequencies of the ODU.
Refer to Configuring a Single-Hop Radio Link and set the transmit frequency
of the local ODU to be the same as the receive frequency of the peer ODU
and the receive frequency of the local ODU to be the same as the transmit
frequency of the peer ODU.
Step 6 Cause 6: The receive power of the ODU is inconsistent in horizontal polarization
direction of the antenna and in the vertical polarization direction.
1. Refer to Configuring a Single-Hop Radio Link and set the receive power of the
ODU to the same value in the horizontal polarization direction of the antenna
and in the vertical polarization direction.
----End

Related Information
None
10.2.357 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
10.2.358 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
10.2.359 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
10.2.360 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.
meanings of the alarms. Then, the RELAY_ALARM_IGNORE alarm is cleared.
----End

Related Information
None
10.2.361 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
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.
meanings of the alarms. Then, the RELAY_ALARM_MAJOR alarm is cleared.
----End
Related Information
None
10.2.362 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

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.
meanings of the alarms. Then, the RELAY_ALARM_MINOR alarm is cleared.
----End
Related Information
None
10.2.363 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:
● Cause 1: The peer NE reports a LOCAL_FAULT alarm.
● 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 NCE. If the
peer NE reports a LOCAL_FAULT alarm, clear the LOCAL_FAULT alarm by
following instructions in 10.2.193 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,
----End
Related Information
None
10.2.364 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
table.

Name Meaning
always 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
10.2.365 RPS_INDI
Description
The RPS_INDI is an alarm indicating that the radio protection switching is
detected.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the ID of the protection group.
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
● 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
1. Determine the type of the protection switching based on the alarm
parameters.
2. Cause 1 of HSB switching: An external switching event occurs. That is, the
NMS issues a command to trigger the switching.
a. 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 Find the cause and release the
switching or manual switching switching immediately.
The switching is not the forced Go to Cause 2 of HSB switching.

switching or manual switching
3. Cause 2 of HSB switching: An automatic switching event occurs. That is, the
equipment is faulty, or the service is defective.
a. 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
● 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.
4. Cause 3 of HSB switching: A reverse switching event occurs.
a. Query whether the active and standby IF boards report the MW_RDI
alarm. If yes, take priority to clear the MW_RDI alarm.
Related Information
None
10.2.366 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
table.
Name Meaning

period:
● 0x02: 24 hours

Name Meaning
Parameter 2, Parameter 3 Parameter 2 is always 0x00. Parameter

3 indicate the ID of a performance
event that causes the alarm and has
● 0x01: RSBBE
● 0x02: RSES
● 0x03: RSSES
● 0x04: RSOOF
● 0x05: RSOFS
● 0x06: RSUAS

A large number of bit errors occur in the services, and the services may be
interrupted.
Possible Causes
● Cause 1: Services are interrupted for a long time.
● 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.
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
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 5.2.5 Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None

10.2.367 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
● Cause 1: The RTC on the system control board is abnormal.
● 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. 5.2.1 Browsing Current Alarms, and if theboard reports the TEMP_ALARM
alarm, clear this alarm first.
----End
Related Information
None
10.2.368 RT_TBL_LACK
Description
The RT_TBL_LACK alarm indicates that routing table resources are insufficient.

Attribute
Parameters
table.
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
10.2.369 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1
byte mode.

Attribute
Parameters
table.
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.
● Cause 1: The original clock source is lost.
● Cause 2: The fiber is cut off.
● Cause 3: The external BITS is interrupted.
● 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
10.2.370 SYNC_FAIL
Description
The SYNC_FAIL alarm indicates that the batch backup on SCC boards fails.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the cause of the failure.
● 0x1F: The database backup fails.

● 0x20: Software version verification fails on the main and standby
SCC boards.
● 0x21: Communication between the main and standby SCC
boards fails.
● 0x22: The main and standby SCC boards have different data
after an upgrade.
● 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
● Cause 1: The main and standby SCC boards have different versions of
software.

● Cause 2: Databases on the main and standby SCC boards are damaged.
● Cause 3: The main and standby SCC boards have different data after an
upgrade.
● Cause 4: Communication between the main and standby SCC boards fails.
● 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 5.7.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 7.11 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
5.2.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 9.6.2 Warm Reset.
----End
Related Information
None
10.2.371 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
table.
Name Meaning
Parameter 1 to Parameter 16 Indicates the username.

A user cannot log in to an NE.
Possible Causes
● Cause 1: The active period of the account expires.
● Cause 2: Configurations on the RADIUS server are incorrect, such as
passwords and access policies.
● Cause 3: There are unauthenticated login attempts.
● 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
10.2.372 SECU_ALM
Description
The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the terminal type used in the login.
● 0x01: indicates the network management (NM) port.
● 0x02: indicates the local maintenance terminal (LMT).
● 0x03: indicates the command line.
● 0x04: indicates the TL1 port.
● 0x05: indicates the SNMP port.
● 0x06: Indicates the web port.
● 0x07: indicates the LCD terminal.
● 0x08: indicates the Tookit terminal.
● 0x09: indicates the shell terminal.
● 0x0A: indicates the FTP terminal.
● 0x0B: indicates the SSH terminal.
Parameters 2
Indicates the errors that occur in the login.
and 3
Parameters 4 Indicates the first two characters of the user name that is
and 5 locked upon login authentication failure.


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.
10.2.373 SLAVE_BAD
Description
The SLAVE_BAD alarm indicates that the connection between the alarmed board
and the standby system control and timing board fails or that the connection
between the alarmed board and the GE bus of the standby system control and
timing board fails.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the fault type on the standby

system control and timing board.
Indicates the fault type on the
connection between the alarmed
board and the GE bus of the standby
system control and timing board.
● 0x00: The cross-connect bus is
faulty.
● 0x01: The standby clock unit is
faulty.
● 0x02: The standby system control
unit is faulty.
● 0x03: The service bus is faulty or
the GE bus of the standby system
control and timing board is faulty.
● 0x04: The Telecom bus from the
standby system control board to the
board is faulty.
Parameters 2 and 3 ● Indicate the slot ID of a board when

the system control board performs
the reporting.
● Indicate the slot ID of the standby
system control board when the
service board performs the
reporting.

Name Meaning
Parameter 4 This parameter is valid only when the

value of parameter 1 is 0x01. This
parameter indicates the cause of the
fault.
● 0x01: The slave 38M system clock is
lost.
● 0x02: The slave TOP 38M clock is
lost.
● 0x03: The slave clock 8 is abnormal.
● 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.
● 0x01: The SMB bus is faulty.
● 0x02: The Telecom bus is faulty.
● 0x03: The overhead is abnormal.
● 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.
● 0x05: The IIC bus is faulty.
● 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.
Parameter 5 When Parameter 1 is set to 0x03 and

Parameter 4 is set to 0x03, the
overheads are abnormal.
● 0x01: The upstream bus (from
service boards to the SCC board) is
faulty.
● 0x02: The downstream bus (from
the SCC board to service boards) is
faulty.

When this alarm occurs, the active system control and timing board works in
unprotected mode.

Possible Causes
● Cause 1: The standby system control and timing board is faulty.
● Cause 3: The chassis is faulty.
● Cause 4: The connection between the alarmed board and the GE bus of the
standby system control and timing board 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.
Step 4 Cause 4: The connection between the alarmed board and the GE bus of the
standby system control and timing board is faulty.
1. Replace the standby system control and timing board by following
instructions in7.11 Replacing the System Control, Switching and Timing
Board.
2. Replace the alarmed board by following instructions in 7.8 Replacing an IF
Board.
----End
Related Information
None
10.2.374 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
10.2.375 SRV_LOOP_LD
Description
The SRV_LOOP_LD alarm indicates that an Ethernet service loop occurs. This
alarm is reported when such a loop is detected. This alarm is cleared when the
loop is removed.
Attribute
Major Service alarm
Parameters
table.

Name Meaning
Parameters 1–2 Indicate the VLAN ID of the service

that encounters a loop. Value range:
0x001 to 0xffe
Parameter 3 Indicates the type of the receive port

when a loop is detected.
● 0x00: UNIPHY
● 0x01: QinQ
● 0x02: PW
Parameters 4–8 Parameter 3 is 0x00:

● Parameters 4–5 indicate the slot ID.
● Parameter 6 indicates the subboard
ID.
● Parameters 7–8 indicate the port
number.
Parameter 3 is 0x01:
● Parameters 4–7 indicate the QinQ
ID.
● Parameters 4–7 indicate the receive
label ID of the PW.

A loop exists on the network.
Possible Causes
Cause 1: A loop on the network is detected.
Procedure
Step 1 Cause 1: A loop on the network is detected.
1. Identify the node that causes the loop and rectify it. Then, check whether the
alarm is cleared.
2. If the alarm persists, contact Huawei technical support engineers.
----End
Related Information
None

10.2.376 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
table.
Name Meaning
Parameters 1–2 Indicate the VLAN ID of the service

that encounters a loop. Value range:
0x001 to 0xffe
Parameter 3 Indicates the type of the receiving port

when the LD detects a network loop
(compared with the port initiating the
LD detection).
● 0x00: UNIPHY
● 0x01: QinQ
● 0x02: PW
Parameters 4–8 Parameter 3 is 0x00:

● Parameters 4–5 indicate the slot ID.
● Parameter 6 indicates the subboard
ID.
● Parameters 7–8 indicate the port
number.
● Parameters 4–7 indicate the QinQ
ID.
● Parameters 4–7 indicate the receive
label ID of the PW.


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 loopback is detected at the port that reports an alarm.
2. If loopback is detected, identify the topology of the service that causes the
loop and remove the service configuration. Then, the alarm clears
automatically.
3. Check whether the SRV_SHUTDOWN_LD alarm is cleared. If the alarm
persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
10.2.377 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 NCE, and load and activate the customized SSL certificate file
again. For details, see the section about loading board-level software in the
Network Cloud Engine Product Documentation.
----End
Related Information
None
10.2.378 SSL_CERT_NOENC
Description
SSL_CERT_NOEN indicates the certificate file of SSL is not encrypted.
Attribute
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
10.2.379 SSL_CERT_TO_EXPIRE
Description
The SSL_CERT_TO_EXPIRE alarm indicates that a customized SSL certificate file is
about to expire or has expired. This alarm is automatically cleared after the SSL
certificate file is reloaded and activated.
Attribute
Critical Security alarm
Parameters
table.
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 or has expired.
Procedure
Step 1 Cause: A customized SSL certificate file is about to expire or has expired.
1. Log in to the NCE and load and activate the customized SSL certificate file
again. For details, see the section about loading board-level software in the
Network Cloud Engine Product Documentation.
----End

Related Information
None
10.2.380 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
table.
Name Meaning
Parameter 1 Indicates the memory fault type.

● 0x01: DDR fault
● 0x02: CPU cache fault (reserved)
● 0x04: NOR flash memory fault
● 0x08: NAND flash memory fault
● 0x10: SATA/CF fault

Name Meaning
Parameter 2 Indicates the fault cause. The meanings of Parameter 2 vary

with the value of Parameter 1.
When the value of Parameter 1 is 0x01:
● 0x01: ECC single-bit error
● 0x04: BootROM fault
● 0x08: overall failure
● 0x04: bad block rate of over 20%
● 0x02: not OK displayed in S.M.A.R.T. information
● 0x04: insufficient remaining backup blocks
● 0x08: memory card not detected
Parameter 3, These parameters are reserved. Their values are always 0xff.
Parameter 4,
Parameter 5

● A read or write error will occur in the file system.
● The memory lifespan is about to end.
Possible Causes
● 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

10.2.381 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
10.2.382 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
table.
Name Meaning
Parameter 1 to Indicate the IP address of the subnet whose route is covered
Parameter 4 by the NE 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.
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 ● 129.9.0.0/255.255.0.0/129.9.0.1/direct/

(destination IP Ethernet
address/subnet ● 129.9.0.0/255.255.255.0/129.9.0.2/OSPF/IF
mask/gateway/ ● 129.9.0.1/255.255.255.255/127.0.0.1/direct/
protocol/interface) loop
● 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 ● 129.9.0.0/255.255.255.0/129.9.0.1/direct/

(destination IP Ethernet
address/subnet ● 129.9.0.0/255.255.0.0/129.9.0.2/OSPF/air
mask/gateway/ interface
protocol/interface) ● 129.9.0.2/255.255.255.255/127.0.0.1/direct/
loop
● 129.9.0.1/255.255.255.0/129.9.0.2/direct/IF
10.2.383 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
● Cause 1: The package loading or diffusion task is suspended during package
activation.
● 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 Perform the package loading to the NE again.
normal
----End
Related Information
None
10.2.384 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
10.2.385 SWDL_BD_MATCH_FAIL
Description
The SWDL_BD_MATCH_FAIL alarm indicates a board software matching failure.
This alarm is reported if matching the board software version to the NE version
fails during an NE upgrade or downgrade.
Attribute

Parameters
None

When the board software fails to automatically match, it cannot be upgraded or
downgraded.
Possible Causes
● Cause 1: An error occurs when data is read from or written to the board file
system or flash memory.
● Cause 2: Communication between the board and the system control board
fails.
● Cause 3: Free space of the board is insufficient.
Procedure
Step 1 Cause 1: An error occurs when data is read from or written to the board file
system or flash memory.
1. Warm reset the board.
2. Check whether the alarm is cleared. If the alarm is not cleared, remove and
insert the board.
3. Check whether the alarm is cleared. If the alarm persists, replace the board.
Step 2 Cause 2: Communication between the board and the system control board fails.
1. Check the communication between the board and system control board. If the
physical communication is abnormal, first rectify this fault.
2. Check whether the alarm is cleared. If the alarm persists, warm reset the
board.
3. Check whether the alarm is cleared. If the alarm is not cleared, remove and
insert the board.
4. Check whether the alarm is cleared. If the alarm persists, replace the board.
Step 3 Cause 3: Free space of the board is insufficient.

1. Contact Huawei technical support engineers to release board storage space.
----End
Related Information
None
10.2.386 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
10.2.387 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
10.2.388 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
10.2.389 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

● If this alarm occurs during package loading, package loading fails.
● 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

10.2.390 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
10.2.391 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
10.2.392 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
10.2.393 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the quality of the synchronization source
declines.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the virtual channel ID of the

1588 unicast ACR.

The NE clock fails to be locked.

Possible Causes
● Cause 1: The quality of the synchronization source declines.
Procedure
1. Cause 1: The quality of the synchronization source declines.
a. Take different measures based on the traced synchronization source.
If... Then...
The traced synchronization source Perform Steps 1.b to 1.d.

is an external clock
The traced synchronization source Replace the system control,

is a line clock switching&timing board of the
upstream NE.
b. 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.
c. Check whether the opposite equipment that provides the clock source is
faulty.
If... Then...
The equipment functions normally Go to the next step.
d. 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.

a. 7.11 Replacing the System Control, Switching and Timing Board.
Related Information
None

10.2.394 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 fiber is faulty (in the case of tracing the line clock source) or the
fiber connection is incorrect.
● Cause 2: There is no input from the external clock source (in the case of
tracing the external clock source).
Procedure
1. On the NMS, check whether alarms causing the loss of the clock source are
generated on the NE.
a. See Querying the Clock Synchronization Status, troubleshoot the
synchronization sources of the lost clock source based on the clock source
priority table.
If... Then...
The synchronization source is an Check whether EXT_SYNC_LOS is

external clock generated. If yes, preferentially
handle this alarm.
The synchronization source is an Check whether any of the

IF clock. following alarms is generated:
R_LOF, R_LOC, MW_LIM,
LOOP_ALM, MW_LOF, and
B1_EXC. If yes, preferentially
handle this alarm.

If... Then...
The synchronization source is a Check whether any of the

line clock. following alarms is generated:
R_LOS, MS_AIS, B2_EXC, and
LOOP_ALM. If yes, preferentially
handle this alarm.
The synchronization source is a Check whether T_ALOS or

tributary clock. LOOP_ALM (non-CES mode) is
generated. If yes, preferentially
handle this alarm.
The synchronization source is a Check whether any of the

packet clock. following alarms is generated:
ETH_LOS, ETH_LINK_DOWN, and
LOOP_ALM. If yes, preferentially
handle this alarm.
2. If the clock source priority table is incorrectly configured, correct this

configuration. For details, see Parameter Description: Clock Source Priority
Table.
3. If the synchronization source is a packet clock, check whether the port is
configured or negotiated to be the 10M full-duplex/10M half-duplex mode. If
yes, correct the configuration or negotiation. For details, see Configuring
Ethernet Ports.
If the working mode is configured or negotiated to be the 10M full-duplex/10M half-

duplex mode, the packet clock fails to be synchronized to the Ethernet port.
4. Check whether the SYNC_C_LOS alarm is cleared. If the alarm persists, contact
Related Information
EXT_SYNC_LOS, R_LOF, R_LOC, MW_LIM, LOOP_ALM, MW_LOF, B1_EXC, R_LOS,
MS_AIS, B2_EXC, T_ALOS, ETH_LINK_DOWN, and ETH_LOS.
10.2.395 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 7.11 Replacing the System Control, Switching and Timing Board.
----End
Related Information
None.
10.2.396 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
10.2.397 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
● Cause 1: No 2Mbit/s services are received on the port.
● 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 Transmit the services to the port or delete the
received 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
10.2.398 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
● Cause 1: The cross-connect and timing board is faulty.
● Cause 2: The line board is faulty.
Procedure
1. Cause 1: The cross-connect and timing board is faulty.
a. Replace the system control, cross-connect, and timing board at the
local end.
If... Then...

is replaced
2. Cause 2: The line board is faulty.

Related Information
None
10.2.399 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
● 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 7.15 Replacing the SFP or Replacing the Alarming Board.
----End
Related Information
None
10.2.400 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
● 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 7.15 Replacing the SFP or Replacing the Alarming Board.
----End
Related Information
None
10.2.401 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the board temperature crosses the
threshold.
Attribute
Minor Environmental alarm
Parameters
table.
Name Meaning
Parameter 1 ● 0x01: The temperature crosses the upper threshold.

● 0x02: The temperature crosses the lower threshold.

The board fails to work normally.
Possible Causes
● Cause 1: The board temperature crosses the threshold.
● Cause 2: The temperature detection circuit of the board is faulty.
Procedure
1. Cause 1: The board temperature crosses the threshold.
a. If the alarm is reported by the ODU, take appropriate measures (for
example, installing a sunshade) to control the temperature.
b. 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 Adjust the temperature control

work abnormally devices.
The temperature control devices Go to the next step.

work normally
c. Check whether the heat dissipation hole on the IDU is covered or

blocked.
If... Then...
The heat dissipation hole is Clear or remove the covering

covered or blocked materials or obstacles.
The heat dissipation hole is not Go to Cause 2.

covered or blocked
2. Cause 2: The temperature detection circuit of the board is faulty.

a. If the ambient temperature is normal and no other heat dissipation
problems exist, replace the alarmed board.
Related Information
None
10.2.402 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature of the board
Attribute
Parameters
table.

Name Meaning
Parameter 1 ● 0x01: The temperature crosses the upper threshold.
● 0x02: The temperature crosses the lower threshold.

When this alarm occurs, the board cannot work properly.
Possible Causes
● Cause 1: The board temperature crosses the threshold.
● 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
malfunction devices.
The temperature control devices Go to the next step.
work 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 Go to the next step.
covered or 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

10.2.403 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
● Cause 1: The laser module is damaged.
● Cause 2: The laser is aged out.
Procedure
Step 1 7.15 Replacing the SFP.
----End
Related Information
None
10.2.404 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
table.
Name Meaning
Parameter 1 Indicates the PIU that reports the alarm.

● 0x01: PIU1
● 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:
● 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

10.2.405 TIME_LOCK_FAIL
Description
The TIME_LOCK_FAIL is an alarm indicating a time locking failure.
Attribute
Parameters
table.
Name Meaning
Parameter 1 ● 0x01: indicates that the time

synchronization is disabled or the
1588v2 port is not traced.
● 0x02: indicates that the clock is
unlocked because phase
discrimination value within the
given time exceeds the upper
threshold.
● 0x03: indicates that the forward
delay is abnormal.
● 0x04: indicates that the backward
delay is abnormal.
● 0x05: indicates that the
accumulated offset value within the
given time exceeds 240 ns.
● 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
10.2.406 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
table.
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
● Cause 1: The clock source priority table is not configured when an external
clock interface is used to trace the upstream NE clock.
● Cause 2: The link between the traced upstream time source and the NE is
faulty.
● 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
10.2.407 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


table.
Name Meaning
Parameter 1 Indicates the slot ID of the board that loses the clock.
● 0x01: board with a smaller slot ID.
● 0x02: board with a larger slot ID.
● 0x03: two boards.

● If the protection cross-connect board is faulty, the services are not affected.
● If the working cross-connect board is faulty, the services are switched,
therefore causing transient service interruption.
Possible Causes
● Cause 1: If one board reports this alarm, the board hardware is faulty.
● 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
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
3. If the alarm persists, remove and insert the protection cross-connect board,
and then check whether the alarm is cleared.
4. If the alarm persists, replace the protection cross-connect board.
----End

Related Information
None
10.2.408 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
● Cause 2: The line is faulty.
● Cause 3: The board at the opposite end is faulty.
● Cause 4: The board at the local end is faulty.
Procedure
1. Cause 1: Configuration data is incorrect.
a. 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.
2. Cause 2: The line is faulty.

a. Check whether a line alarm that causes AIS insertion is reported on the
service trail.

For details about the line alarms that cause AIS insertion, see 13.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.
b. See 9.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 Go to Cause 3.

faulty
The board at the local end is Go to Cause 4.

faulty
3. Cause 3: The board at the opposite end is faulty.

a. Replace the faulty board at the opposite end.
4. Cause 4: The board at the local end is faulty.
a. Replace the board where the local line unit resides.
If... Then...

is replaced

local end.
If... Then...

is replaced
c. Replace the alarmed board.
Related Information
None

10.2.409 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
table.
Name Meaning
always 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
● Cause 2: The line is faulty.
● Cause 3: The board at the opposite site is faulty.
● 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
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.
For details about the line alarms that cause AIS insertion, see 13.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 9.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 7.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.
The alarm persists after the board is Go to the next step.
replaced
2. Replace the alarmed board at the local site
----End
Related Information
None
10.2.410 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
table.
Name Meaning

The services in the alarmed TU-3 paths are interrupted. If the services are
configured with protection, protection switching is triggered.
Possible Causes
● Cause 1: SDH service configuration data is incorrect.
● 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
incorrect configuration data.
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.

For the line alarms that will cause AIS insertion, see 13.2.6 AIS Insertion.
If... Then...
A line alarm that will cause AIS Rectify the SDH service
insertion is reported configuration data.
No line alarm is reported Go to step 3.
Step 3 Follow instructions in 9.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.
Step 4 Cause 3: The board at the opposite end is faulty.

1. Replace the faulty board at the opposite end.
Step 5 Cause 4: The board at the local end is faulty.

1. Follow instructions in 7.3 Replacing the SDH Optical Interface Board to
replace the line board at the local end.
If... Then...
2. Follow instructions in 7.11 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
10.2.411 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
● Cause 1: The system control, cross-connect, and timing board is faulty.
● Cause 2: The tributary board is faulty.
Procedure
1. Cause 1: The system control, cross-connect, and timing board is faulty.
a. Replace the system control, cross-connect, and timing board at the
local end.
If... Then...

is replaced
2. Cause 2: The tributary board is faulty.

a. Replace the board where the tributary unit resides.
Related Information
None
10.2.412 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
table.
Name Meaning
always 0x01.

Services in the alarmed TU path are interrupted. If the services are configured with
protection, protection switching is also triggered.
Possible Causes
● Cause 2: The board at the opposite site is faulty.
● 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
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 9.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 7.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
10.2.413 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
table.
Name Meaning


The services in the alarmed TU-3 path are interrupted. If the services are
configured with protection, protection switching is triggered.
Possible Causes
● 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
incorrect configuration data.
The SDH service configuration data is Go to step 2.
correct
Step 2 Follow instructions in 9.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.
Step 3 Cause 2: The board at the opposite end is faulty.

1. Replace the faulty board at the opposite end.
Step 4 Cause 3: The board at the local end is faulty.

1. Follow instructions in 7.3 Replacing the SDH Optical Interface Board to
replace the line board at the local end.
If... Then...
2. Follow instructions in 7.11 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
10.2.414 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 5.2.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.
The relevant alarms are as follows:

● Hardware alarms: Such as HARD_BAD, POWER_ALM, BD_STATUS,

COMMUN_FAILand LASER_MOD_ERR.
● Link alarms: Such as ETH_LOS, ETH_AUTO_LINK_DOWN,
ETH_EFM_LOOPBACK, LOOP_ALM, PORTMODE_MISMATCH, and
LAG_DOWN.
● Radio link alarms: Such as MW_LOF, MW_LIM.
Step 5 Refer to 5.2.1 Browsing Current Alarms, check whether any alarms are generated
in the failed tunnel. If yes, take priority to clear them.
The relevant alarms are as follows:

● MPLS_TUNNEL_BDI
● MPLS_TUNNEL_Excess
● MPLS_TUNNEL_FDI
● MPLS_TUNNEL_LOCV
● MPLS_TUNNEL_MISMATCH
● MPLS_TUNNEL_MISMERGE
● MPLS_TUNNEL_OAMFAIL
● MPLS_TUNNEL_SD
● MPLS_TUNNEL_SF
● MPLS_TUNNEL_UNKNOWN
● MPLS_TUNNEL_AIS
● MPLS_TUNNEL_RDI
● MPLS_TUNNEL_UNEXPMEG
● MPLS_TUNNEL_UNEXPMEP
● MPLS_TUNNEL_UNEXPPER
----End
Related Information
None
10.2.415 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 6.10 Troubleshooting MPLS Tunnels.
----End
Related Information
None
10.2.416 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
● Cause 1: A few bit errors occur in the receive path related to the ATM port
which reports the UHCS alarm.
● 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
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 9.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 7.6 Replacing
the Smart E1 Interface Board.
----End
Related Information
None
10.2.417 UNIPTP_SRC_LOSS
Description
The UNIPTP_SRC_LOSS alarm indicates that the unicast PTP clock source fails.
Attribute

Parameters
table.

Name Meaning
Parameter 1 Indicates the packet type.
Parameter 2 Indicates the ACR port ID.

When this alarm is generated, unicast PTP packets are transmitted abnormally. As
a result, clock synchronization may be affected or even fails.
Possible Causes
Cause 1: The network is faulty.
Cause 2: The system control, cross-connect, and timing board is faulty.
Procedure
Step 1 Cause 1: The network is faulty.
1. Check whether there are alarms about bit errors, FCS error packets, or the
abnormal optical power. If yes, first clear these alarms.
2. Check whether the physical link connection is correct. If not, reconnect the
fibers.
3. Clean the optical modules. For details, see 9.13 Cleaning Fiber Connectors
and Adapters.
Step 2 Cause 2: The system control, cross-connect, and timing board is faulty.
1. Check whether the alarm is cleared. If the alarm persists, cold reset the
system control, cross-connect, and timing board. For details, see 9.6.1 Cold
Reset.
control, cross-connect, and timing board. For details, see 7.11 Replacing the
System Control, Switching and Timing Board.
----End
Related Information
None
10.2.418 UNIPTP_SRC_SWITCH
Description
The UNIPTP_SRC_SWITCH alarm indicates that the unicast PTP clock source is
switched.

Attribute
Parameters
table.
Name Meaning
Parameters 1–2 Indicate the ID of the unicast PTP clock source before the
switching.
Parameters 3–4 Indicate the ID of the unicast PTP clock source after the
switching.

When this alarm is generated, unicast PTP packets are transmitted abnormally. As
a result, clock synchronization may be affected or even fails.
Possible Causes
● Cause 1: The link used for sending unicast PTP packets is faulty.
● Cause 2: The clock configuration is modified.
● Cause 3: The clock server is faulty.
Procedure
Step 1 Cause 1: The link used for sending unicast PTP packets is faulty.
1. Rectify the link.
Step 2 Cause 2: The clock configuration is modified.
1. Reconfigure the clock.
2. Check whether the UNIPTP_SRC_NEGO_FAIL and UNIPTP_SRC_LOSS alarms
are generated. If yes, clear these alarms.
Step 3 Cause 3: The clock server is faulty.
1. Check whether the alarm is cleared. If the alarm persists, cold reset the
system control, cross-connect, and timing board. For details, see 9.6.1 Cold
Reset.

----End
Related Information
None
10.2.419 UNIPTP_SRC_NEGO_FAIL
Description
The UNIPTP_SRC_NEGO_FAIL alarm indicates that the unicast PTP protocol
negotiation fails.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the packet type.
● 0x01: indicates that Announce negotiation fails.
● 0x02: indicates that Sync negotiation fails.
● 0x03: indicates that Delay negotiation fails.
Parameter 2 Indicates the ACR port ID.

When this alarm is generated, the clock source cannot be traced normally.
Possible Causes
● Cause 1: The clock service fails or the clock server denies authorization.
● Cause 2: The configuration is incorrect.

Procedure
Step 1 Cause 1: The clock service fails or the clock server denies authorization.
1. Check whether the unicast PTP clock service is configured correctly. If not,
correct the configuration.
2. Identify the reason why the clock server denies authorization.
If... Then...
The number of Slave entities Plan the clock network again to reduce the
on the server reaches the number of Slave entities on the server. For
upper threshold. details, see Configuring the Clock.
The server cannot meet the Modify the frequency at which PTP packets
Slave entity's frequency at are sent. For details, see Setting
which PTP packets are sent. Parameters for PTP Clock Packets.
Step 2 Cause 2: The configuration is incorrect.

1. Ensure that the service configuration is correct. Then, use the Ping and
Trace_route functions to ensure tunnel connectivity. For details, see Verifying
MPLS Tunnels in an End-to-End Mode.
2. Ensure that the physical connection is consistent with the service
configuration.
Step 3 If the alarm persists, perform the following operations:

1. Cold reset the system control, cross-connect, and timing board. For details,
see 9.6.1 Cold Reset.
----End
Related Information
None
10.2.420 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
● Cause 1: The opposite equipment transmits the AIS signal.
● 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 Rectify the fault on the opposite
AIS signal equipment.
The opposite equipment does not Go to Cause 2.
transmit the AIS signal
Step 2 Cause 2: The receive unit of the tributary board on the local equipment is faulty.
----End
Related Information
None
10.2.421 USB_FILE_UNSEC
Description
The USB_FILE_UNSEC alarm indicates that the USB flash drive used by the NE is
insecure.
Attribute
Parameters


table.
Name Meaning
Parameter 1 Indicates the alarm cause.
● 0x01: The file is not encrypted.
● 0x02: Decryption fails.
● 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
● Cause 1: The file is not encrypted.
● Cause 2: Decryption fails.
● 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
10.2.422 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 ● 0x01 indicates data recovery.
● 0x02 indicates data backup.
Parameter 2 Indicates the file type.
● 0x01: indicates the software package.

● 0x02: indicates the patch package.
● 0x03: indicates the system parameter area.
● 0x04: indicates the script.
● 0x05: indicates the database.
● 0x06: indicates the license file.
● 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
● Cause 1: Recovering data from a USB disk fails.
● 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

10.2.423 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
● 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
Step 3 If the alarm persists, Replace the alarming board.
----End
Related Information
None
10.2.424 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
table.
Name Meaning
Parameter 1 Indicates the direction of ATM connection.

● 0x01: forward
● 0x02: backward
Parameter 2 Indicates the segment and end attribute of ATM connection.

● 0x01: segment
● 0x02: end

● 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.
● 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
● Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted
to the downstream.
● 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.
● 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 abnormal in the receive direction and therefore inserts AIS cells to the
downstream.
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.
● If an NE is set with the segment end point attribute, it can retrieve the alarms
that are generated at the segment and end.
● If an NE is set with the segment point attribute, it can retrieve the alarms that
are generated at a segment.
● If an NE is set with the end point attribute, it can retrieve the alarms that are
generated at an end.
● 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.
10.2.425 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
table.
Name Meaning

● 0x01: forward
● 0x02: backward

● 0x01: segment
● 0x02: end

● 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.
● In other cases, the service is interrupted when the alarm occurs.
● When this alarm occurs, the system automatically inserts AIS cells to the
downstream.
Possible Causes
● Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled
on the upstream NE.
● Cause 2: No bandwidth is available on the local NE.
path is 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
is abnormal in the receive direction.
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
10.2.426 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
table.
Name Meaning

● 0x01: forward
● 0x02: backward

Name Meaning

● 0x01: segment
● 0x02: end

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

10.2.427 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
table.
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
10.2.428 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
table.
Name Meaning
always 0x01.

The alarmed path is unavailable. If the LCAS function is disabled, the services in
the path are interrupted.
Possible Causes
● Cause 1: Bit errors occur on the line.
● Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
● 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 7.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 Go to Cause 2.
reported
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
10.2.429 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
table.
Name Meaning

The path that reports the alarm is unavailable. If the LCAS function is disabled,
Possible Causes
● Cause 1: Bit errors occur in the line.
● Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect.
● 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 7.7 Replacing the Ethernet Interface Board to replace
the board at the opposite site.
2. Replace the alarmed board and then check whether the alarm clears.
If... Then...

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 Handle the VCAT_LOA alarm
path 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 7.7 Replacing the
persists Ethernet Interface Board to replace the
alarmed board at the local site.
----End
Related Information
None
10.2.430 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
table.

Name Meaning
always 0x01.

The alarmed path is unavailable. If the LCAS function is disabled, services are
interrupted.
Possible Causes
● Cause 1: Bit errors occur on certain links or certain links are faulty.
● 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
10.2.431 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
table.
Name Meaning

The path that reports the alarm is unavailable. If the LCAS function is disabled,
Possible Causes
● Cause 1: Bit errors occur on a link or a link is faulty.
● 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 End the alarm handling.
board is replaced

If... Then...
The VCAT_SQM_VC3 alarm persists after the Contact Huawei technical
board is replaced support engineers.
----End
Related Information
None
10.2.432 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power voltage is unavailable.
Attribute
Parameters
table.
Name Meaning

The ODU that is connected to the IF board that reports this alarm fails to work.
Possible Causes
● Cause 1: The output power is abnormal.
● 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
connected to the dual-channel IF the ODU.
board is 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 Go to the next step.

switch is 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
10.2.433 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
table.
Name Meaning

● 0x01: forward
● 0x02: backward

● 0x01: segment
● 0x02: end

● 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.
● 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
● Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to
the downstream.
path is 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.
is abnormal in the receive direction and therefore inserts AIS cells to the
downstream.
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
10.2.434 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
table.
Name Meaning

● 0x01: forward
● 0x02: backward

● 0x01: segment
● 0x02: end

● 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.
● In other cases, the service is interrupted when the alarm occurs.
● When this alarm occurs, the system automatically inserts AIS cells to the
downstream.
● The VP_LOC is suppressed when the VP_AIS occurs.
Possible Causes
● Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled
on the upstream NE.
● Cause 2: No bandwidth is available on the local NE.
path is 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. 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
is abnormal in the receive direction.
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
10.2.435 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
table.
Name Meaning

● 0x01: forward
● 0x02: backward

Name Meaning

● 0x01: segment
● 0x02: end

● 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
● Cause 1: The VP_AIS occurs in the receive direction of the downstream VP
connection.
Procedure
● 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 9.6.1 Cold
Reset.
b. If the alarm persists, replace the alarmed board. For details, see 7.6
----End
Related Information
End and Segment
Segment End Point

10.2.436 W_R_FAIL
Description
The W_R_FAIL is an alarm indicating a failure of reading or writing chip register.
Attribute
Parameters
table.
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

10.2.437 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
● 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 Change the configuration data.
planning requirement
The board type meets the planning Go to Cause 2.

requirement
Step 2 Cause 2: The board of an incorrect type is installed.

1. Replace the board of an incorrect type.
----End
Related Information
None

10.2.438 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
● Cause 1: The radio link is faulty.
● Cause 2: The XPIC cable is faulty.
For ISM6 boards, ignore this cause.

● 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 End the alarm handling.
is replaced

replaced
2. Replace the ODU that is connected to the paired XPIC IF board.

If... Then...
The alarm is cleared after the ODU End the alarm handling.
is replaced
The alarm persists after the ODU is Replace the alarmed XPIC IF
replaced board.
----End
Related Information
None

Maintenance Guide 11 Performance Event Reference
11 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.
11.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.
11.2 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.
11.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.
11.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 11-1 Pointer Justification Performance Events
Event Name Description
AUPJCHIGH Indicates the count of positive AU

pointer justifications.
AUPJCLOW Indicates the count of negative AU

AUPJCNEW Indicates the count of new AU pointer

justifications.

TUPJCHIGH Indicates the count of positive TU

TUPJCLOW Indicates the count of negative TU

TUPJCNEW Indicates the count of new TU pointer

justifications.
Table 11-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.
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 11-3 Multiplex Section Error Performance Events

MSBBE Indicates the multiplex section

MSES Indicates the multiplex section errored

second.

MSSES Indicates the multiplex section severely

errored second.
MSCSES Indicates the multiplex section

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 11-4 Higher Order Path Error Performance Events

HPBBE Indicates the higher order path

HPES Indicates the higher order path errored

second.
HPSES Indicates the higher order path

HPCSES Indicates the higher order path

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 11-5 Lower Order Path Error Performance Events

LPBBE Indicates the lower order path

LPES Indicates the lower order path errored

second.
LPSES Indicates the lower order path severely

errored second.
LPCSES Indicates the lower order path

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 11-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 severely errored second.
Table 11-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.
11.1.2 Radio Performance Events

The radio performance events are performance events of the radio link bit errors,
ATPC, AM, and power.
Table 11-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 11-9 FEC performance events

FEC_BEF_COR_ER FEC bit error rate before correction
FEC_UNCOR_BLOCK_CNT FEC uncorrected block count
Table 11-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 ratio

Table 11-11 ATPC performance events

ATPC_P_ADJUST Positive ATPC adjustment
ATPC_N_ADJUST Negative ATPC adjustment
Table 11-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

mode

mode
AMDOWNCNT Count of the downshift of the AM

scheme
AMUPCNT Count of the upshift of the AM

scheme

Table 11-13 XPIC performance events

XPD_MAX Maximum XPD value
XPD_MIN Minimum XPD value
XPIC_XPD_VALUE XPIC XPD value
Table 11-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 11-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
11.1.3 MPLS PW Performance Events

This section lists MPLS PW performance events.

Table 11-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
11.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 11-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 11-18 Board temperature performance events
BDTEMPMAX Maximum value of board temperature
BDTEMPMIN Minimum value of board temperature
BDTEMPCUR Current value of board temperature
Table 11-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 11-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 11-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
MAXNEGATIVEDELAY Maximum negative PDV
MINNEGATIVEDELAY Minimum negative PDV
AVGNEGATIVEDELAY Average negative PDV
CURNEGATIVEPDV Current negative PDV value
Table 11-22 Memory usage performance events

MEMUSAGEAVG Average memory usage
MEMUSAGECUR Current memory usage
MEMUSAGEMAX Maximum memory usage
MEMUSAGEMIN Minimum memory usage
Table 11-23 Bandwidth usage threshold-crossing time events

TX_BWUTIL_EXCS Time for which the bandwidth usage

at the transmit direction exceeds the
RX_BWUTIL_EXCS Time for which the bandwidth usage

at the receive direction exceeds the
TX_BWUTIL_EXCS_MIN The total time for which the

bandwidth usage at the transmit
direction exceeds the minimum
threshold.

RX_BWUTIL_EXCS_MIN The total time for which the

bandwidth usage at the receive
direction exceeds the minimum
threshold.
TX_BWUTIL_EXCS_MID The total time for which the

direction exceeds the middle threshold.
RX_BWUTIL_EXCS_MID The total time for which the

bandwidth usage at the receive
direction exceeds the middle threshold.
TX_BWUTIL_EXCS_MAX The total time for which the

direction exceeds the maximum
threshold.
RX_BWUTIL_EXCS_MAX the total time for which the bandwidth

usage at the receive direction exceeds
the maximum threshold.
11.2 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.
11.2.1 ATPC_P_ADJUST and ATPC_N_ADJUST
Description
● 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.
● 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
11.2.2 AMDOWNCNT and AMUPCNT

Description
● AMDOWNCNT indicates the count of the AM downshifts on a board in the
current performance statistics period.
● 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
● When the value of the performance event is larger, more AM scheme are
made.
● 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.
11.2.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW
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.
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
AUPJCLOW 1500 30000
AUPJCNEW 1500 30000
Possible Causes
The NE clock is out-of-synchronization.

Procedure
Step 1 See 6.5 Troubleshooting Pointer Justifications for handling.
----End
11.2.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR

Description
● BDTEMPMAX indicates the maximum temperature of a board.
● BDTEMPMIN indicates the minimum temperature of a board.
● 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.
11.2.5 CPUUSAGEMAX, CPUUSAGEMIN, CPUUSAGECUR, and

CPUUSAGEAVG
Description
● CPUUSAGEMAX indicates the maximum CPU usage.
● CPUUSAGEMIN indicates the minimum CPU usage.
● CPUUSAGECUR indicates the current CPU usage.
● CPUUSAGEAVG indicates the average CPU usage.
Attribute
Performance event cell SYS_CPU_CONDITION
Unit Percentage


None
Relevant Alarms
None
11.2.6 CURPOSITIVEPDV and CURNEGATIVEPDV

Description
● CURPOSITIVEPDV indicates the current positive packet delay variation (PDV).
● 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 packet delay variation (PDV), the easier the clock is to be restored.
Related Alarms
When the PDV exceeds the acceptable range, the clock is unlocked and the
ACR_LOCK_FAIL alarm is reported.
11.2.7 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and

E1_LSES_SDH
Description
● The E1_LCV_SDH is a performance event indicating the E1 line side code
violation count.
● The E1_LLOSS_SDH is a performance event indicating the E1 line side loss-of-
signal seconds.
● 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.
● The E1_LSES_SDH is a performance event indicating the E1 line side code
violation severely errored second.

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

11.2.8 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS

Description
● 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.
● E1_ES indicates the E1 errored second.
Errored second (ES) refers to a second in which one or more errored blocks
are detected.
● 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.
● 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.
● 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
11.2.9 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and

FEC_UNCOR_BLOCK_CNT
Description
● FEC_BEF_COR_ER indicates the BER before the FEC is performed.
This event indicates the impact of the external environment on the
transmission.
● FEC_COR_BYTE_CNT indicates the number of bytes corrected through the FEC.
This event indicates the impact of the FEC.
● 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_CNT
)
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.
11.2.10 HPBBE, HPES, HPSES, HPCSES, and HPUAS
Description
● 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.
● HPES indicates the higher order path errored second.
● 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.
● 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.
● 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
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 6.4 Troubleshooting Bit Errors in TDM Services for handling.
----End
11.2.11 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS
Description
● 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.
● HPFEES indicates the higher order path far end errored second.
FEES indicates that the ES occurs at the opposite end.
● HPFESES indicates the higher order path far end severely errored second.
FESES indicates that the SES occurs at the opposite end.
● HPFECSES indicates the higher order path far end consecutive severely errored
second.
FECSES indicates that the CSES occurs at the opposite end.
● 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
11.2.12 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS

Description
● IF_BBE indicates the radio link background block error.

● IF_ES indicates the radio link errored second.

● IF_SES indicates the radio link severely errored second.
lost.
● IF_CSES indicates the radio link consecutively severely errored second.
seconds.
● IF_UAS indicates the radio link unavailable second.
● IF_BER indicates the radio link bit error ratio.
The BER is the number of bit errors divided by the total number of bits
transferred on a microwave link within a specified interval. You can obtain the
BER by multiplying the value of the IF_BER performance event reported by the
NMS with by 10-10.
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
11.2.13 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG

Description
● IF_SNR_MAX indicates the maximum signal to noise ratio.
● IF_SNR_MIN indicates the minimum signal to noise ratio.
● 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
11.2.14 IF_MSE_MAX, IF_MSE_MIN, IF_MSE_AVG, and

IF_MSE_CUR
Description
● IF_MSE_MAX indicates the maximum MSE.
● IF_MSE_MIN indicates the minimum MSE.
● IF_MSE_AVG indicates the average MSE.
● 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
11.2.15 LSBIASMAX, LSBIASMIN, and LSBIASCUR

Description
● LSBIASMAX indicates the maximum laser bias current.
● LSBIASMIN indicates the minimum laser bias current.
● LSBIASCUR indicates the current laser bias current.
Attribute
Performance event cell LSBISA
Unit 0.1 mA
Impact on system
If the bias current of the laser is over-high or over-low, the laser may be damaged.
Related Alarms
If the receive optical power at the opposite site is abnormal, the LSR_BCM_ALM
alarm is reported.

11.2.16 LSIOPMAX, LSIOPMIN, and LSIOPCUR
Description
● LSIOPMAX indicates the maximum input optical power at an optical interface.
● LSIOPMIN indicates the minimum input optical power at an optical interface.
● LSIOPCUR indicates the current input optical power at an optical interface.
Attribute
Performance event cell LSIOP
Unit 0.1 dBm
Impact on system
In normal cases, the receive optical power is 3 dB higher than the receiver
sensitivity, and 5 dB lower than the overload power.
If the receive optical power is over-low or over-high, bit errors occur and even
Related Alarms
● If the receive optical power is lower than the receiver sensitivity, the
IN_PWR_LOW alarm is reported.
● If the receive optical power is higher than the overload power, the
IN_PWR_HIGH alarm is reported.
11.2.17 LSOOPMAX, LSOOPMIN, and LSOOPCUR
Description
● LSOOPMAX indicates the maximum output optical power of the laser.
● LSOOPMIN indicates the minimum output optical power of the laser.
● LSOOPCUR indicates the current output optical power of the laser.
Attribute
Performance event cell LSOOP
Unit 0.1dBm

Impact on system
In normal cases, the receive optical power is 3 dB higher than the receiver
If the transmit optical power is over-low or over-high, the receive optical power at
the opposite site is over-low or over-high accordingly. As a result, bit errors occur
and even services are interrupted.
Related Alarms
● If the receive optical power at the peer site is lower than the receiver
sensitivity, the IN_PWR_LOW alarm is reported.
● If the receive optical power at the peer site is higher than the overload power,
the IN_PWR_HIGH alarm is reported.
11.2.18 LSTMPMAX, LSTMPMIN, and LSTMPCUR

Description
● LSTMPMAX indicates the maximum working temperature of the laser.
● LSTMPMIN indicates the minimum working temperature of the laser.
● LSTMPCUR indicates the current working temperature of the laser.
Attribute
Performance event cell LSTMP
Unit 0.1°C
Impact on system
If the working temperature of the laser is over-high or over-low, the performance
of the laser degrades and bit errors or other faults occur.
Related Alarms
None
11.2.19 LPBBE, LPES, LPSES, LPCSES, and LPUAS

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

lost.
● LPCSES indicates the lower order path consecutive severely errored second.
seconds.
● 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
11.2.20 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS
Description
● LPFEBBE indicates the lower order path far end background block error.
FEBBE indicates that the BBE occurs at the opposite end.
● LPFEES indicates the lower order path far end errored second.
FEES indicates that the ES occurs at the opposite end.
● LPFESES indicates the lower order path far end severely errored second.
FESES indicates that the SES occurs at the opposite end.
● LPFECSES indicates the lower order path far end consecutive severely errored
second.
FECSES indicates that the CSES occurs at the opposite end.
● 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
11.2.21 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV

Description
● MAXFREQDEV indicates the maximum frequency offset.
● MINFREQDEV indicates the minimum frequency offset.
● 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.
11.2.22 MAXMEANPATHDELAY, MINMEANPATHDELAY, and

AVGMEANPATHDELAY
Description
● MAXMEANPATHDELAY indicates the maximum path delay between the
master and slave clocks.
● MINMEANPATHDELAY indicates the minimum path delay between the master
and slave clocks.
● 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
11.2.23 MAXPHASEOFFSET, MINPHASEOFFSET, and

AVGPHASEOFFSET
Description
● MAXPHASEOFFSET indicates the maximum time deviation between the
● MINPHASEOFFSET indicates the minimum time deviation between the master
and slave clocks.
● 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.
11.2.24 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and

AVGPOSITIVEDELAY
Description
● MAXPOSITIVEDELAY indicates the maximum positive delay between the
● MINPOSITIVEDELAY indicates the minimum positive delay between the
● 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
11.2.25 MAXNEGATIVEDELAY, MINNEGATIVEDELAY, and

AVGNEGATIVEDELAY
Description
● MAXNEGATIVEDELAY indicates that the maximum reverse delay between the
● MINNEGATIVEDELAY indicates that the minimum reverse delay between the

● AVGNEGATIVEDELAY indicates that the average reverse delay between the

Attribute
Performance event cell PTP_NTD
Unit ns
Impact on System
The difference between the maximum and minimum values reflects the delay
variation. A larger difference affects the clock performance.
Related Alarms
An excessively large PDV value causes the clock to be unlocked and therefore
ACR_LOCK_FAIL is reported.
11.2.26 MEMUSAGEAVG, MEMUSAGECUR, MEMUSAGEMAX,

and MEMUSAGEMIN
Description
● MEMUSAGEMAX indicates the maximum memory usage.
● MEMUSAGEMIN indicates the minimum memory usage.
● MEMUSAGECUR indicates the current memory usage.
● 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

11.2.27 MIMO_CAPACITY_CUR, MIMO_CAPACITY_MIN,

MIMO_CAPACITY_MAX, MIMO_CAPACITY_AVG
Description
● MIMO_CAPACITY_CUR:indicates the current capacity of the MIMO protection
group.
● MIMO_CAPACITY_MIN:indicates the minimum capacity of the MIMO
protection group.
● MIMO_CAPACITY_MAX:indicates the maximum capacity of the MIMO
protection group.
● MIMO_CAPACITY_AVG:indicates the average capacity of the MIMO protection
group.
Attribute
Performance event cell MIMO_SYNTHETICAL_CAPACITY
Unit Mbit/s
Impact on System
In a performance measurement period, smaller capacity of a MIMO protection
group indicates lower link status modulation mode and poorer link status, which
has negative impacts on the service quality.
Procedure
Check the status of the MIMO link and adjust the link.
11.2.28 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and

MPLS_PW_UAS
Description
● MPLS_PW_LS indicates the packet loss seconds of the PW service.
● MPLS_PW_SLS indicates the severe packet loss seconds of the PW service.
● MPLS_PW_CSLS indicates the consecutive severe packet loss seconds of the
PW service.
● 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.
11.2.29 MPLS_PW_LS_N, MPLS_PW_SLS_N, MPLS_PW_CSLS_N,

and MPLS_PW_UAS_N
Description
● MPLS_PW_LS_N indicates packet loss seconds of PW services at the local end.
● MPLS_PW_SLS_N indicates severe packet loss seconds of PW services at the
local end.
● MPLS_PW_CSLS_N indicates consecutive severe packet loss seconds of PW
services at the local end.
● 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.

11.2.30 MSBBE, MSES, MSSES, MSCSES, and MSUAS
Description
● MSBBE indicates the multiplex section background block error.
● MSES indicates the multiplex section errored second.
● MSSES indicates the multiplex section severely errored second.
lost.
● MSCSES indicates the multiplex section consecutive severely errored second.
seconds.
● 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


Threshold Threshold
MSES 50 100
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
----End
11.2.31 MSFEBBE, MSFEES, MSFESES, MSFECSES, and

MSFEUAS
Description
● 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.
● MSFEES indicates the multiplex section far end errored second.
Far end errored second (FEES) indicates that the ES occurs at the opposite
end.
● 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.
● 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.
● 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
11.2.32 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

Description
● OSPITMPMAX indicates the maximum temperature of a laser core.
● OSPITMPMIN indicates the minimum temperature of a laser core.
● 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
11.2.33 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and

PG_IF_UAS
Description
● PG_IF_BBE indicates the protection group background block error.
errored blocks in the unavailable and severely errored seconds.
● PG_IF_ES indicates the protection group errored second.
are detected.
● PG_IF_SES indicates the protection group severely errored second.
● PG_IF_CSES indicates the protection group consecutive severely errored
second.
● 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
Related Alarms
PG_LINK_FAIL, PG_PRT_DEGRADED


Threshold Threshold
PG_IF_BBE 1500 15000
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
11.2.34 RPLMAX, RPLMIN, and RPLCUR

Description
● RPLMAX indicates the maximum receive optical power at an optical interface.
● RPLMIN indicates the minimum receive optical power at an optical interface.
● 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
If the receive optical power is very low or very high, bit errors occur and even
Related Alarms
● If the transmit optical power is lower than the receiver sensitivity, the
IN_PWR_LOW alarm is reported.

● If the receive optical power is higher than the overload power, the
IN_PWR_HIGH alarm is reported.
11.2.35 RSBBE, RSES, RSSES, RSCSES, and RSUAS
Description
● RSBBE indicates the regenerator section background block error.
errored blocks in the unavailable and severely errored seconds.
● RSES indicates the regenerator section errored second.
are detected.
● RSSES indicates the regenerator section severely errored second.
● RSCSES indicates the regenerator section consecutive severely errored second.
● RSUAS indicates the regenerator section unavailable second.
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
----End
11.2.36 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG
Description
● RSL_MAX indicates the maximum radio received signal level.
● RSL_MIN indicates the minimum radio received signal level.
● RSL_CUR indicates the current radio received signal level.
● 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 services are interrupted.
Related Alarms
If the radio received signal level crosses the specific threshold, the
RADIO_RSL_HIGH or RADIO_RSL_LOW alarm is reported.
11.2.37 RSOOF and RSOFS

Description
● 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.
● 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
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 6.4 Troubleshooting Bit Errors in
TDM Services for handling.
----End
11.2.38 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16,

QAMWS32, QAMWS64, QAMWS128, QAMWS256,
QAMWS512, QAM_L_WS512, QAMWS1024, QAM_L_WS1024,
QAM_L_WS2048, QAMWS2048, QAMWS4096, QAMWS8192
Description
● QPSKWS indicates the working duration of the QPSK mode.
● QPSK_S_WS indicates the working duration of the QPSKWS Strong mode.
● QAMWS16 indicates the working duration of the 16QAM mode.
● QAM_S_WS16 indicates the working duration of the 16QAM Strong mode.
● QAM_L_WS512 indicates the working duration of the 512QAM 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)
Light)
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
11.2.39 TLBMAX, TLBMIN, and TLBCUR
Description
● TLBMAX indicates the maximum transmit bias current of the laser.

● TLBMIN indicates the minimum transmit bias current of the laser.

● 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.
11.2.40 RLHTT, RLLTT, TLHTT, TLLTT
Description
● The RLHTT indicates the duration when the ODU at the local end has a
receive power lower than the upper threshold.
● The RLLTT indicates the duration when the ODU at the local end has a receive
power lower than the lower threshold.
● The TLHTT indicates the duration when the ODU at the local end has a transit
power higher than the upper threshold.
● 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
11.2.41 TPLMAX, TPLMIN, and TPLCUR

Description
● TPLMAX indicates the maximum transmit optical power at an optical
interface.
● TPLMIN indicates the minimum transmit optical power at an optical interface.
● 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
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 services are interrupted.
Related Alarms
● If the transmit optical power at the opposite site is lower than the receiver
sensitivity, the IN_PWR_LOW alarm is reported.
● If the receive optical power at the opposite site is higher than the overload
power, the IN_PWR_HIGH alarm is reported.
11.2.42 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Description
● TSL_MAX indicates the maximum radio transmitted signal level.
● TSL_MIN indicates the minimum radio transmitted signal level.
● TSL_CUR indicates the current radio transmitted signal level.
● 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 services are interrupted.
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.
11.2.43 TUPJCHIGH, TUPJCLOW, and TUPJCNEW
Description
● 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.
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 6.5 Troubleshooting Pointer Justifications for handling.
----End
11.2.44 TX_BWUTIL_EXCS,RX_BWUTIL_EXCS,
TX_BWUTIL_EXCS_MIN, RX_BWUTIL_EXCS_MIN,
TX_BWUTIL_EXCS_MID, RX_BWUTIL_EXCS_MID,
TX_BWUTIL_EXCS_MAX, and RX_BWUTIL_EXCS_MAX
Description
● TX_BWUTIL_EXCS indicates the total time for which the bandwidth usage at
the transmit direction exceeds the specified threshold in a period.
● RX_BWUTIL_EXCS indicates the total time for which the bandwidth usage at
the receive direction exceeds the specified threshold in a period.
● TX_BWUTIL_EXCS_MIN indicates the total time for which the bandwidth
usage at the transmit direction exceeds the minimum threshold.
● RX_BWUTIL_EXCS_MIN indicates the total time for which the bandwidth
usage at the receive direction exceeds the minimum threshold.
● TX_BWUTIL_EXCS_MID indicates the total time for which the bandwidth
usage at the transmit direction exceeds the middle threshold.
● RX_BWUTIL_EXCS_MID indicates the total time for which the bandwidth
usage at the receive direction exceeds the middle threshold.
● TX_BWUTIL_EXCS_MAX indicates the total time for which the bandwidth
usage at the transmit direction exceeds the maximum threshold.
● RX_BWUTIL_EXCS_MAX indicates the total time for which the bandwidth
usage at the receive direction exceeds the maximum threshold.

Attribute
Performance event cell TX_BWUTIL_EXC_SEC

(TX_BWUTIL_EXCS)
RX_BWUTIL_EXC_SEC
(RX_BWUTIL_EXCS)
TX_BWUTIL_EXC_SEC_MIN
(TX_BWUTIL_EXCS_MIN)
RX_BWUTIL_EXC_SEC_MIN
(RX_BWUTIL_EXCS_MIN)
TX_BWUTIL_EXC_SEC_MID
(TX_BWUTIL_EXCS_MID)
RX_BWUTIL_EXC_SEC_MID
(RX_BWUTIL_EXCS_MID)
TX_BWUTIL_EXC_SEC_MAX
(TX_BWUTIL_EXCS_MAX)
RX_BWUTIL_EXC_SEC_MAX
(RX_BWUTIL_EXCS_MAX)
Unit Second
Impact on System
None
Related Alarms
None
Possible Causes
The bandwidth usage exceeds the specified threshold in a certain period.
Procedure
Step 1 Check the bandwidth usage.
Step 2 Check the bandwidth usage against each threshold in a certain period.
Step 3 If the bandwidth usage exceeds the maximum threshold for a long time, upgrade
the bandwidth for the NE.
----End
11.2.45 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
● XPD_MAX and XPD_MIN: The events have no impact on the system.
● XPIC_XPD_VALUE: When the XPIC function is disabled, the performance event
does not affect the system.
● 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 12 RMON Event Reference
12 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.
12.1 RMON Performance Entries List on the Packet-Plane

This section lists RMON performance entries on the packet plane by logical board.
12.2 RMON Performance Entries List on the EoS/EoPDH-Plane
This section lists RMON performance entries on the EoS/EoPDH plane by board
type.
12.3 RMON Events and Handling Procedures
This chapter describes the RMON events that indicate Ethernet service
abnormalities and how to handle these events.
12.1 RMON Performance Entries List on the Packet-

Plane
This section lists RMON performance entries on the packet plane by logical board.
12.1.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, Port DS domain performance and LAG
performance.
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,
see Performance counting method and calculation method list.

Table 12-1 Performance counting method and calculation method list

Performance Counting Method Calculation 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 among all Takes the maximum value among
sampling periods counts in all sampling periods within a
statistical period as the historical
performance count.
Minimum value obtained among all Takes the minimum value among
performance count.
Value obtained in the last sampling Takes the count of the last sampling
period period within a statistical period as the
historical performance count.
Average value of counts in all Takes the average value of counts in

sampling periods all sampling periods within a statistical
period as the historical performance
count.
Table 12-2 Basic performance entry list (EM6F/EM6T/EM6FA/EM6TA)

Brief Full Perform Perform Remarks
Name Name ance ance
of a of 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
RXPKTS received. packets are included.
ETHDRO Indicates Times Accumul ETHDROP indicates the number of packet loss events
P the ated caused by insufficient Ethernet chip resources. The
packet value count is not the number of discarded packets but the
loss number of times packet loss is detected.
events.


Name Name ance ance
ance ance Method
Entry Entry
RXOCTE Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in
TS the ated received packets (including bad packets), including
bytes value framing bits but not FCS bytes.
received. 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.
RXMULC Indicates Packets Accumul RXMULCAST indicates the total number of received
AST the ated good packets with multicast destination addresses,
multicas value excluding broadcast packets.
t
packets
received.
RXBRDC Indicates Packets Accumul RXBRDCAST indicates the total number of received
AST the ated good packets with broadcast destination addresses,
broadcas value excluding multicast packets.
t
packets
received.
ETHOVE Indicates Packets Accumul Indicates the number of received packets that are
R the ated longer than MTU bytes (including FCS bytes but not
oversize value framing bits) and do not contain any other errors.
d
packets
received.
ETHJAB Indicates Packets Accumul Indicates the total number of received packets that
the ated are longer than MTU bytes (including FCS bytes but
oversize value not framing bits) and contain FCS errors or
d error alignment errors.
packets
received.
ETHUN Indicates Packets Accumul Undersized packets are the packets shorter than 64
DER the ated bytes (including FCS bytes but not framing bits).
undersiz value
ed
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
ETHFRG Indicates Packets Accumul ETHFRG indicates the number of received packets
the ated that are shorter than 64 bytes (including FCS bytes
fragmen value but not framing bits) and contain FCS errors or
ts alignment errors. Increase of the count is normal
received. because noise collisions exist.
ETHCOL Indicates Times Accumul -

the ated
collision value
s.
PORT_R Indicates 0.0001 Average Bandwidth utilization = (Number of received bytes x

X_BW_U the value of 8/Monitoring period)/Configured or actual
TILIZATI bandwid counts bandwidth
ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.
PORT_T Indicates 0.0001 Average Bandwidth utilization = (Number of transmitted

X_BW_U the value of bytes x 8/Monitoring period)/Configured or actual
ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.

Table 12-3 Extended performance entry list (EM6F/EM6T/EM6FA/EM6TA)

Name Name ance ance
ance ance Method
Entry Entry
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast
the ated packets are included.
packets value
transmit
ted.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted
TS the ated packets (including bad packets), including framing
bytes value bits but not FCS bytes.
transmit
ted
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an
the FCS ated integral number of octets in length but do not pass
errored value the FCS check.
frames. NOTE
This count does not include undersized frames and
oversized frames.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the ated
bytes in value
received
good
packets.
TXBGOO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the ated
bytes in value
transmit
ted
good
packets.
RXBBAD Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
the ated
bytes in value
received
bad
packets.


Name Name ance ance
ance ance Method
Entry Entry
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmit
ted.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast
AST the ated packets.
unicast value
packets
received.
TXMULC Indicates Packets Accumul The multicast packets that are discarded or fail to be
multicas value
t
packets
transmit
ted.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
broadcas value
t
packets
transmit
ted.
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate obtained
RAMESP of good in the
EED full- last
frame samplin
bytes g period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
EED full- last
frame samplin
bytes g period
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
RXFULLB Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
GOOD the ated
good value
full-
frame
bytes
received.
TXFULLB Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
RXPAUS Indicates Frames Accumul RXPAUSE indicates the number of MAC flow control
E the ated frames with the PAUSE opcode.
pause value
frames
received.
TXPAUS Indicates Frames Accumul TXPAUSE indicates the number of MAC flow control
pause value
frames
transmit
ted.
ETHLAT Indicates Times Accumul Indicates the number of collisions that are detected
ECOL the late ated after a timeslot period elapses. The late collisions
collision value indicate that the diameter of a LAN is too large.
s.
ETHEXC Indicates Frames Accumul -

COL the ated
frames value
unsucces
sfully
transmit
ted after
consecut
ive
collision
s.


Name Name ance ance
ance ance Method
Entry Entry
TXDEFF Indicates Frames Accumul Indicates the number of frames whose first
RM the ated transmission is delayed because transmission media
frames value are busy, excluding the number of frames whose
that are transmission is delayed due to collisions.
deferred
in
transmis
sion.
RX_DRO Packet 0.0001 Average The discarded packets ratio in the ingress direction,
P_RATIO loss rate value of that is, number of actually drop packets/received
in the counts packets.
ingress in all
direction samplin
g
periods
TX_DRO Packet 0.0001 Average The discarded packets ratio in the egress direction,
P_RATIO loss rate value of that is, number of actually drop packets/transmitted
egress in all
direction samplin
g
periods
ETH_RX_ Indicates kbit/s Maximu Maximum throughput = Number of received bytes

THROU the m value (including inter-frame gaps and preambles)/
GHPUT_ maximu obtained Monitoring period
MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry
ETH_RX_ Indicates kbit/s Minimu Minimum throughput = Number of received bytes

GHPUT_ minimu obtained Monitoring period
MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.
ETH_RX_ Indicates kbit/s Average Average throughput = Number of received bytes

THROU the value of (including inter-frame gaps and preambles)/
GHPUT_ average counts Monitoring period
AVG through in all
put on a samplin
port in g
the periods
receive
direction
.
Indicates kbit/s Maximu

the m value
maximu obtained
m among
ETH_TX_ transmit all
THROU through samplin Throughput at the transmit direction = Total number
GHPUT_ put of a g of received bytes (including the preamble and frame
MAX port. periods gap)/Measurement period
Indicates kbit/s Minimu

the m value
minimu obtained
m among
MIN port. periods gap)/Measurement period


Name Name ance ance
ance ance Method
Entry Entry
Indicates kbit/s Average

the value of
average counts
ETH_TX_ transmit in all
AVG port. periods gap)/Measurement period

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -
RXBPS Indicates Bits/s Value Bit rate in the receive direction = Number of received
the bit obtained bytes x 8/Monitoring period
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
TXBPS Indicates Bits/s Value Bit rate in the transmit direction = Number of
the bit obtained transmitted bytes x 8/Monitoring period
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
RXPPS Indicates Packets/ Value Packet rate in the receive direction = Number of
the s obtained received packets/Monitoring period
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.
TXPPS Indicates Packets/ Value Packet rate in the transmit direction = Number of
the s obtained transmitted packets/Monitoring period
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.
RXBRDC Broadca 0.0001 Average Ratio of broadcast and multicast packets to all
AST_RAT st traffic value of packets in the receive direction
IO ratio in counts
the in all
receive samplin
direction g
periods
TXBRDC Broadca 0.0001 Average Ratio of broadcast and multicast packets to all
AST_RAT st traffic value of packets in the transmit direction
IO ratio in counts
the in all
transmit samplin
direction g
periods


Name Name ance ance
ance ance Method
Entry Entry
PORT_R Indicates 0.0001 Average Average bandwidth utilization on a specified port in

X_BW_U the value of the receive direction = (Number of received bytes x
TILIZATI average counts 8/Monitoring period)/Configured or actual
ON_AVG bandwid in bandwidth
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.
Indicates 0.0001 Maximu Maximum bandwidth utilization on a specified port

the m value in the receive direction = (Number of received bytes x
maximu of 8/Monitoring period)/Configured or actual
m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .
Indicates 0.0001 Minimu Minimum bandwidth utilization on a specified port in

the m value the receive direction = (Number of received bytes x
minimu of 8/Monitoring period)/Configured or actual
m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry
Indicates 0.0001 Average Average bandwidth utilization on a specified port in

the value of the transmit direction = (Number of transmitted
average counts bytes x 8/Monitoring period)/Configured or actual
bandwid in bandwidth
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .

the m value in the transmit direction = (Number of transmitted
maximu of bytes x 8/Monitoring period)/Configured or actual
m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

the m value the transmit direction = (Number of transmitted
minimu of bytes x 8/Monitoring period)/Configured or actual
m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .

Table 12-4 Port traffic classification performance entry list (EM6F/EM6T/EM6FA/EM6TA)

Name Name ance ance
ance ance Method
Entry Entry
QOS_PO Indicates Packets Accumul -

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
MarkedY number value
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.
PORTST Indicates Packets Accumul -

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
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
PING_D of in the packets matching the traffic classification rule in the
ROPRAT packet last egress direction
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
QOS_PO Indicates 0.0001 Value Proportion of packets marked in red in the ingress
RTCAR_ the obtained direction = Number of packets marked in red in the
Marked proporti in the ingress direction/Number of packets matching the
RedRATI on of last traffic classification rule in the ingress direction
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
QOS_PO Indicates Packets/ Value Packet rate in the receive direction = Number of
RTSTRM the s obtained received packets/Monitoring period
_RX_PPS packet in the
rate in last
the samplin
receive g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
QOS_PO Indicates Packets/ Value Packet rate in the transmit direction = Number of
RTSTRM the s obtained transmitted packets/Monitoring period
_TX_PPS packet in the
rate in last
the samplin
transmit g period
direction
of a
matched
flow.
QOS_PO Indicates Bytes Accumul -

RTSTRM the ated
_RCVMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
received
packets
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
transmit
ted
packets
of a
matched
flow.
QOS_PO Indicates Bits/s Value Bit rate in the receive direction = Number of received
RTSTRM the bit obtained bytes (including inter-frame gaps and preambles) x
_RX_BPS rate in in the 8/Monitoring period
the last
receive samplin
direction g period
of a
matched
flow.
QOS_PO Indicates Bits/s Value Bit rate in the transmit direction = Number of
RTSTRM the bit obtained transmitted bytes (including inter-frame gaps and
_TX_BPS rate in in the preambles) x 8/Monitoring period
the last
transmit samplin
direction g period
of a
matched
flow.

Table 12-5 Port priority performance entry list (EM6F/EM6T/EM6FA/EM6TA)

Name Name ance ance
ance ance Method
Entry Entry
QOS_PO Indicates 0.0001 Average Packet loss rate in an egress queue = Number of
RTQUEU the ratio value of discarded packets with a priority in the egress queue/
E_DROP of counts Number of packets with the priority in the egress
RATIO packet in all queue
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.
QOS_PRI Indicates Packets Accumul -

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.
QOS_PRI Indicates Bytes Accumul -

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry
PORT_P Indicates Packets Accumul -

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.
PORT_P Indicates Bytes Accumul -

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.
PORT_P Indicates Bits/s Value Bit rate = Number of transmitted bytes x 8/

RI_TX_B the bit obtained Monitoring period
PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry
PORT_P Indicates Packets/ Value Packet rate = Number of transmitted packets/

RI_TX_P the s obtained Monitoring period
PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.
Table 12-6 Port DS domain performance entry list (EM6F/EM6T/EM6FA/EM6TA)

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


Name Name ance ance
ance ance Method
Entry Entry
DS_CVL Indicates Bytes Accumul -

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.
DS_SVLA Indicates Packets Accumul -

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.
DS_SVLA Indicates Bytes Accumul -

NPRI_BY the ated
TES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry
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_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.
Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic
classifications or port DS domains.

Table 12-7 LAG performance entry list (EM6F/EM6T/EM6FA/EM6TA)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.
received. NOTE
If the packets received by an /EG2D/EX1 board are larger
than the MTU, byte count is calculated based on actual
packet size.
t
packets
received.
t
packets
received.
d
packets
received.
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
undersiz value
ed
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
transmit
ted
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.
pause value
frames
transmit
ted.

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
12.1.2 EG2D
The RMON performance that the EG2D board supports includes basic
performance, extended performance, port traffic classification performance, port
priority performance, Port DS domain performance and LAG performance.



count.
performance count.
performance count.

count.
Table 12-9 Basic performance entry list (EG2D)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.


Name Name ance ance
ance ance Method
Entry Entry
received. NOTE
packet size.
t
packets
received.
t
packets
received.
d
packets
received.
packets
received.
undersiz value
ed
packets
received.


Name Name ance ance
ance ance Method
Entry Entry

the ated
collision value
s.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
Table 12-10 Extended performance entry list (EG2D)

Name Name ance ance
ance ance Method
Entry Entry
packets value
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
transmit
ted
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.
pause value
frames
transmit
ted.
s.

COL the ated
frames value
unsucces
sfully
transmit
ted after
consecut
ive
collision
s.
deferred
in
transmis
sion.


Name Name ance ance
ance ance Method
Entry Entry
P_RATIO loss rate value of that is, number of actually drop packets/ received
ingress in all
direction samplin
g
periods
P_RATIO loss rate value of that is, number of actually drop packets/ transmitted
egress in all
direction samplin
g
periods

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.

the m value
maximu obtained
m among

the m value
minimu obtained
m among

the value of
average counts

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -


Name Name ance ance
ance ance Method
Entry Entry

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry
PORT_R Indicates 0.0001 Maximu Maximum bandwidth utilization on a specified port

X_BW_U the m value in the receive direction = (Number of received bytes x
TILIZATI maximu of 8/Monitoring period)/Configured or actual
ON_MA m counts bandwidth
X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.
PORT_R Indicates 0.0001 Minimu Minimum bandwidth utilization on a specified port in

X_BW_U the m value the receive direction = (Number of received bytes x
TILIZATI minimu of 8/Monitoring period)/Configured or actual
ON_MIN m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.
PORT_T Indicates 0.0001 Average Average bandwidth utilization on a specified port in

X_BW_U the value of the transmit direction = (Number of transmitted
TILIZATI average counts bytes x 8/Monitoring period)/Configured or actual
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry
PORT_T Indicates 0.0001 Maximu Maximum bandwidth utilization on a specified port

X_BW_U the m value in the transmit direction = (Number of transmitted
TILIZATI maximu of bytes x 8/Monitoring period)/Configured or actual
X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.
PORT_T Indicates 0.0001 Minimu Minimum bandwidth utilization on a specified port in

X_BW_U the m value the transmit direction = (Number of transmitted
TILIZATI minimu of bytes x 8/Monitoring period)/Configured or actual
bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.
PKT64 Packets Packets Accumul The total number of packets (including bad packets)
Received ated received and transmitted that were 64 octets in
and value length (excluding framing bits but including FCS
Transmit octets).
ted(64
Octets in
Length)
PKT65 Packets Packets Accumul The total number of packets (including bad packets)
Received ated reveived and transmitted that were between 65 and
and value 127 octets in length inclusive (excluding framing bits
Transmit but including FCS octets).
ted(65~
127
Octets in
Length)


Name Name ance ance
ance ance Method
Entry Entry
PKT128 Packets Packets Accumul The total number of received and transmitted
received ated packets (including bad packets) whose length is
and value between 128 and 255 bytes (excluding framing bits,
transmit but including FCS bytes).
ted
(128-25
5 bytes
in
length)
ted
(256-51
1 bytes
in
length)
ted
(512-10
23 bytes
in
length)
and value between 1024 and 1518 bytes (excluding framing
transmit bits, but including FCS bytes).
ted
(1024-1
518
bytes in
length)

Table 12-11 Port traffic classification performance entry list (EG2D)

Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
rate in last
the samplin
receive g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
rate in last
the samplin
transmit g period
direction
of a
matched
flow.
Table 12-12 Port priority performance entry list (EG2D)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.

Table 12-13 Port DS domain performance entry list (EG2D)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

NPRI_BY the ated
TES 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_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

Table 12-14 LAG performance entry list (EG2D)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.
received. NOTE
packet size.
t
packets
received.
t
packets
received.
d
packets
received.
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
undersiz value
ed
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
transmit
ted
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.
pause value
frames
transmit
ted.

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.
12.1.3 EX1
The RMON performance that the EX1 board supports includes basic performance,
extended performance, port traffic classification performance, port priority
performance, Port DS domain performance and LAG performance.



count.
performance count.
performance count.

count.
Table 12-16 Basic performance entry list (EX1)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received. NOTE
packet size.
t
packets
received.
t
packets
received.
d
packets
received.
packets
received.
undersiz value
ed
packets
received.


Name Name ance ance
ance ance Method
Entry Entry

the ated
collision value
s.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.

Table 12-17 Extended performance entry list (EX1)

Name Name ance ance
ance ance Method
Entry Entry
packets value
transmit
ted.
transmit
ted
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.


Name Name ance ance
ance ance Method
Entry Entry
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.
pause value
frames
transmit
ted.
s.

COL the ated
frames value
unsucces
sfully
transmit
ted after
consecut
ive
collision
s.


Name Name ance ance
ance ance Method
Entry Entry
deferred
in
transmis
sion.
ingress in all
direction samplin
g
periods
egress in all
direction samplin
g
periods

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.

the m value
maximu obtained
m among

the m value
minimu obtained
m among


Name Name ance ance
ance ance Method
Entry Entry

the value of
average counts

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.

Table 12-18 Port traffic classification performance entry list (EX1)

Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
rate in last
the samplin
receive g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
rate in last
the samplin
transmit g period
direction
of a
matched
flow.

RTSTRM the ated
_RCVMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
received
packets
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
transmit
ted
packets
of a
matched
flow.
the last
receive samplin
direction g period
of a
matched
flow.
the last
transmit samplin
direction g period
of a
matched
flow.

Table 12-19 Port priority performance entry list (EX1)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.
Table 12-20 Port DS domain performance entry list (EX1)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain


Name Name ance ance
ance ance Method
Entry Entry

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.

NPRI_BY the ated
TES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

P_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.
Table 12-21 LAG performance entry list (EX1)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received. NOTE
packet size.
t
packets
received.
t
packets
received.
d
packets
received.
packets
received.
undersiz value
ed
packets
received.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.
transmit
ted


Name Name ance ance
ance ance Method
Entry Entry
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.
pause value
frames
transmit
ted.

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.
● Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic
● When the port serves as a single-service port or the master port for PLA, EPLA, EPLA+,
or SD group members, QoS performance statistics can be reported. When the port
serves as a slave port for PLA, EPLA, EPLA+, or SD group members, QoS performance
statistics cannot be reported.
12.1.4 EG4/EG4P
The RMON performance that the EG4/EG4P board supports includes basic



count.
performance count.
performance count.

count.
Table 12-23 Basic performance entry list (EG4/EG4P)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received. NOTE
If the packets received by an EG4/EG4P board are larger
packet size.
t
packets
received.
t
packets
received.
ETHOVE Indicates Packets Accumul Oversized packets are the packets larger than MTU
R the ated (including FCS bytes but not framing bits).
oversize value NOTE
d For EG4/EG4P boards, an oversized packet is larger than
packets 1518 bytes.
received.
ETHJAB Indicates Packets Accumul ETHJAB indicates the number of received packets
the ated that are larger than MTU (including FCS bytes but
packets NOTE
received. For EG4/EG4P boards, an oversized error packet is larger
than 1518 bytes.


Name Name ance ance
ance ance Method
Entry Entry
undersiz value
ed
packets
received.

the ated
collision value
s.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
RXPKT64 Packets Packets Accumul Indicates the total number of received packets
received ated (including corrupted packets) with a length of 64
(64 value bytes (including FCS bytes but not framing bits).
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
received ated (including corrupted packets) with a length of 65 to
(65-127 value 127 bytes (including FCS bytes but not framing bits).
bytes in
length)
8 received ated (including corrupted packets) with a length of 128 to
5 bytes
in
length)
1 bytes
in
length)
(512-10 value 1023 bytes (including FCS bytes but not framing
23 bytes bits).
in
length)
24 received ated (including corrupted packets) with a length of 1024
(1024-1 value to 1518 bytes (including FCS bytes but not framing
518 bits).
bytes in
length)

Table 12-24 Extended performance entry list (EG4/EG4P)

Name Name ance ance
ance ance Method
Entry Entry
packets value
transmit
ted.
transmit
ted
frames. NOTE
For EG4/EG4P boards, this count includes undersized frames
and oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.


Name Name ance ance
ance ance Method
Entry Entry
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.
pause value
frames
transmit
ted.
s.

COL the ated
frames value
unsucces
sfully
transmit
ted after
consecut
ive
collision
s.


Name Name ance ance
ance ance Method
Entry Entry
deferred
in
transmis
sion.
ingress in all
direction samplin
g
periods
egress in all
direction samplin
g
periods

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.

the m value
maximu obtained
m among

the m value
minimu obtained
m among


Name Name ance ance
ance ance Method
Entry Entry

the value of
average counts

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -
TXPKT64 Packets Packets Accumul Indicates the total number of transmitted packets
transmit ated (including corrupted packets) with a length of 64
ted (64 value bytes (including FCS bytes but not framing bits).
bytes in
length)
transmit ated (including corrupted packets) with a length of 65 to
ted value 127 bytes (including FCS bytes but not framing bits).
(65-127
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
8 transmit ated (including corrupted packets) with a length of 128 to
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
ted value 1023 bytes (including FCS bytes but not framing
(512-10 bits).
23 bytes
in
length)
24 transmit ated (including corrupted packets) with a length of 1024
ted value to 1518 bytes (including FCS bytes but not framing
(1024-1 bits).
518
bytes in
length)
ted value to MTU bytes (including FCS bytes but not framing
(1519 bits).
bytes to
the MTU
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(1519 value to MTU bytes (including FCS bytes but not framing
bytes to bits).
the MTU
in
length)
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .

Table 12-25 Port traffic classification performance entry list (EG4/EG4P)

Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
rate in last
the samplin
receive g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
rate in last
the samplin
transmit g period
direction
of a
matched
flow.

RTSTRM the ated
_RCVMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
received
packets
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
transmit
ted
packets
of a
matched
flow.
the last
receive samplin
direction g period
of a
matched
flow.
the last
transmit samplin
direction g period
of a
matched
flow.

Table 12-26 Port priority performance entry list (EG4/EG4P)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.
Table 12-27 Port DS domain performance entry list (EG4/EG4P)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain


Name Name ance ance
ance ance Method
Entry Entry

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.

NPRI_BY the ated
TES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

P_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.
Table 12-28 LAG performance entry list (EG4/EG4P)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received. NOTE
packet size.
t
packets
received.
t
packets
received.
d
packets
received.
packets
received.
undersiz value
ed
packets
received.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.
transmit
ted


Name Name ance ance
ance ance Method
Entry Entry
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.
pause value
frames
transmit
ted.
bytes in
length)
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
23 bytes bits).
in
length)
518 bits).
bytes in
length)
bytes to bits).
the MTU
in
length)
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.
When the EG4 port serves as a single-service port or the master port for PLA, EPLA, EPLA+,
or SD group members, QoS performance statistics can be reported. When the EG4 port
12.1.5 IFU2/IFX2
The RMON performance that the IFU2/IFX2 board supports includes basic



count.
performance count.
performance count.

count.
Table 12-30 Basic performance entry list (IFU2/IFX2)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received. NOTE
If the packets received by an IFU2/IFX2 board are larger
than the MTU, byte count is calculated based on MTU.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
Table 12-31 Extended performance entry list (IFU2/IFX2)

Name Name ance ance
ance ance Method
Entry Entry
packets value
transmit
ted.
transmit
ted
frames. NOTE
For the IFU2/IFX2 board, this count does not include
undersized frames and oversized frames.


Name Name ance ance
ance ance Method
Entry Entry
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
ingress in all
direction samplin
g
periods
egress in all
direction samplin
g
periods

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.

the m value
maximu obtained
m among

the m value
minimu obtained
m among

the value of
average counts

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -


Name Name ance ance
ance ance Method
Entry Entry

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
RX_MAX Air Mbps Maximu Air interface bandwidth when the bandwidth usage
_BW_UTI interface m value reaches the maximum value in the receive direction
LIZATIO bandwid of
N_CAPA th with counts
CITY maximu in
m RX samplin
bandwid g
th usage periods
over a
port


Name Name ance ance
ance ance Method
Entry Entry
TX_MAX Air Mbps Maximu Air interface bandwidth when the bandwidth usage
_BW_UTI interface m value reaches the maximum value in the transmit direction
LIZATIO bandwid of
CITY maximu in
m TX samplin
bandwid g
th usage periods
over a
port
Table 12-32 Port traffic classification performance entry list (IFU2/IFX2)

Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.


Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
the last
receive samplin
direction g period
of a
matched
flow.
the last
transmit samplin
direction g period
of a
matched
flow.

Table 12-33 Port priority performance entry list (IFU2/IFX2)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.
Table 12-34 Port DS domain performance entry list (IFU2/IFX2)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain


Name Name ance ance
ance ance Method
Entry Entry

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.

NPRI_BY the ated
TES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

P_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.
Table 12-35 LAG performance entry list (IFU2/IFX2)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received. NOTE
packet size.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.
transmit
ted
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
● Integrated IP microwave ports support this parameter.

12.1.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, Port DS domain performance and LAG performance.



count.
performance count.
performance count.

count.
Table 12-37 Basic performance entry list (ISU2/ISX2/ISV3/ISM6)

Name Name ance ance
ance ance Method
Entry Entry
RXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast
packets value
received.


Name Name ance ance
ance ance Method
Entry Entry
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.
received. NOTE
If the packets received by an ISU2/ISX2/ISV3/ISM6 board are
larger than the MTU, byte count is calculated based on
MTU.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
bytes in
length)
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length)


Name Name ance ance
ance ance Method
Entry Entry
518 bits).
bytes in
length)
Table 12-38 Extended performance entry list (ISU2/ISX2/ISV3/ISM6)

Name Name ance ance
ance ance Method
Entry Entry
packets value
transmit
ted.
transmit
ted
frames. NOTE
For the ISU2/ISX2/ISV3/ISM6 board, this count does not
include undersized frames and oversized frames.
OD the ated
bytes in value
received
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
P_RATIO loss rate value of that is, number of actually drop packets/received
ingress in all
direction samplin
g
periods


Name Name ance ance
ance ance Method
Entry Entry
P_RATIO loss rate value of that is, number of actually drop packets/transmitted
egress in all
direction samplin
g
periods
bytes to bits).
the MTU
in
length)
bytes in
length
(65-127
bytes in
length))
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.

the m value
maximu obtained
m among

the m value
minimu obtained
m among

the value of
average counts


Name Name ance ance
ance ance Method
Entry Entry

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry
LIZATIO bandwid of
CITY maximu in
m RX samplin
bandwid g
th usage periods
over a
port
LIZATIO bandwid of
CITY maximu in
m TX samplin
bandwid g
th usage periods
over a
port
Table 12-39 Port traffic classification performance entry list (ISU2/ISX2/ISV3/ISM6)

Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.


Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
a rate in last
the samplin
receive g period
direction
of a
matched
flow.
a rate in last
the samplin
transmit g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_RCVMA number value
TCHBYT of bytes
ESa (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
received
packets
of a
matched
flow.

RTSTRM the ated
_SNDMA number value
TCHBYT of bytes
ESa (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
transmit
ted
packets
of a
matched
flow.
the last
receive samplin
direction g period
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
the last
transmit samplin
direction g period
of a
matched
flow.
aThe RTN 980L/980/950/905 does not support this measurement item.
Table 12-40 Port priority performance entry list (ISU2/ISX2/ISV3/ISM6)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry
ECMPRS Indicates 0.0001 Value Compression ratio of Ethernet packets after

_RATIO the obtained traversing the enhanced compression module =
compres in the Number of bytes after compression/Number of bytes
sion last before compression
ratio of samplin NOTE
the g period Only ISV3 boards support this performance entry.
enhance
d
compres
sion
module.
Table 12-41 Port DS domain performance entry list (ISU2/ISX2/ISV3/ISM6)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain


Name Name ance ance
ance ance Method
Entry Entry

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.

NPRI_BY the ated
TES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

P_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.
Table 12-42 LAG performance entry list (ISU2/ISX2/ISV3/ISM6)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received. NOTE
packet size.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.
transmit
ted
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)
bytes to bits).
the MTU
in
length)
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length)
518 bits).
bytes in
length)

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
● Integrated IP microwave ports support this parameter.

12.1.7 ISM8
The RMON performance that the ISM8 board supports includes basic



count.
performance count.
performance count.

count.
Table 12-44 Basic performance entry list (ISM8)

Name Name ance ance
ance ance Method
Entry Entry

the ated


Name Name ance ance
ance ance Method
Entry Entry
events.
received.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
bytes in
length)
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length)


Name Name ance ance
ance ance Method
Entry Entry
518 bits).
bytes in
length)
Table 12-45 Extended performance entry list (ISM8)

Name Name ance ance
ance ance Method
Entry Entry
packets value
transmit
ted.
transmit
ted
frames.
OD the ated
bytes in value
received
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
ingress in all
direction samplin
g
periods


Name Name ance ance
ance ance Method
Entry Entry
egress in all
direction samplin
g
periods

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

the m value
maximu obtained
m among

the m value
minimu obtained
m among

the value of
average counts

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -


Name Name ance ance
ance ance Method
Entry Entry
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(1519 bits).
bytes to
the MTU
in
length)
bytes to bits).
the MTU
in
length)
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
LIZATIO bandwid of
CITY maximu in
m RX samplin
bandwid g
th usage periods
over a
port


Name Name ance ance
ance ance Method
Entry Entry
LIZATIO bandwid of
CITY maximu in
m TX samplin
bandwid g
th usage periods
over a
port
Table 12-46 Port traffic classification performance entry list (ISM8)

Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.


Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
rate in last
the samplin
receive g period
direction
of a
matched
flow.
rate in last
the samplin
transmit g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_RCVMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
received
packets
of a
matched
flow.

RTSTRM the ated
_SNDMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
transmit
ted
packets
of a
matched
flow.
the last
receive samplin
direction g period
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
the last
transmit samplin
direction g period
of a
matched
flow.
Table 12-47 Port priority performance entry list (ISM8)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.

Table 12-48 Port DS domain performance entry list (ISM8)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

NPRI_BY the ated
TES 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_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

Table 12-49 LAG performance entry list (ISM8)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.
received.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.
transmit
ted
frames. NOTE
oversized frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)
bytes in
length)
5 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
1 bytes
in
length)
23 bytes bits).
in
length)
518 bits).
bytes in
length)
RXPKT15 Indicates Packets Accumul Indicates the total number of received packets
19 the ated (including corrupted packets) with a length of 1519
count of value to MTU bytes (including FCS bytes but not framing
received bits).
packets
with a
length
of over
1518
bytes
(errored
packets
included
)
TXPKT64 Indicates Packets Accumul Indicates the total number of transmitted packets
the ated (including corrupted packets) with a length of 64
count of value bytes (including FCS bytes but not framing bits).
transmit
ted 64-
byte
packets
(errored
packets
included
)


Name Name ance ance
ance ance Method
Entry Entry
the ated (including corrupted packets) with a length of 65 to
count of value 127 bytes (including FCS bytes but not framing bits).
transmit
ted
packets
with a
length
of 65 to
127
bytes
(errored
packets
included
)
8 the ated (including corrupted packets) with a length of 128 to
transmit
ted
packets
with a
length
of 128
to 255
bytes
(errored
packets
included
)


Name Name ance ance
ance ance Method
Entry Entry
transmit
ted
packets
with a
length
of 256
to 511
bytes
(errored
packets
included
)
count of value 1023 bytes (including FCS bytes but not framing
transmit bits).
ted
packets
with a
length
of 512
to 1023
bytes
(errored
packets
included
)


Name Name ance ance
ance ance Method
Entry Entry
count of value to 1518 bytes (including FCS bytes but not framing
transmit bits).
ted
packets
with a
length
of 1024
to 1518
bytes
(errored
packets
included
)
count of value to MTU bytes (including FCS bytes but not framing
transmit bits).
ted
packets
with a
length
of over
1518
bytes
(errored
packets
included
)

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

X bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.

bandwid in
th samplin
utilizatio g
n on a periods
port in
the
transmit
direction
.
12.1.8 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.



count.
performance count.
performance count.

count.
Table 12-51 ATM PWE3 performance entry list (ML1/MD1)

Name Name ance ance
ance ance Method
Entry Entry
Indicates Cells Accumul

the ated
ATMPW count of value
_SNDCE transmit
LLS ted cells. -


Name Name ance ance
ance ance Method
Entry Entry
ATMPW Indicates Cells Accumul -

_RCVCEL the ated
LS count of value
received
cells.
ATMPW Indicates Cells Accumul -

_UNKN the ated
OWNCE count of value
LLS unknow
n cells.
Table 12-52 ATM/IMA performance entry list on the access side (ML1/MD1)
Name Name ance ance
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
correcta
ble HCS
error
cells
received.
ATM_U Indicates Cells Accumul ATM_UNCORRECTED_HCSERR is used to determine

NCORRE the ated whether cell loss occurs on a port.
CTED_H number value
CSERR of
uncorrec
table
HCS
error
cells
received.


Name Name ance ance
ance ance Method
Entry Entry
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.
ATM_RC Indicates Cells Accumul ATM_RCVIDLECELLS is used to determine whether

VIDLECE the total ated cells are properly processed at the ATM physical
LLS number value layer.
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
transmit
ted cells.
ATM_IF_ Indicates Cells/s Maximu -

INRATE_ the m value
MAX maximu obtained
m rate among
of all
normal samplin
cells g
received periods
on the
port.
ATM_IF_ Indicates Cells/s Minimu -

INRATE_ the m value
MIN minimu obtained
m rate among
of all
normal samplin
cells g
received periods
on the
port.


Name Name ance ance
ance ance Method
Entry Entry
ATM_IF_ Indicates Cells/s Average -

INRATE_ the value of
AVG average counts
rate of in all
normal samplin
cells g
received periods
on the
port.
ATM_IF_ Indicates Cells/s Maximu -

OUTRAT the m value
E_MAX maximu obtained
m rate among
of all
normal samplin
cells g
transmit periods
ted on
the port.
ATM_IF_ Indicates Cells/s Minimu -

OUTRAT the m value
E_MIN minimu obtained
m rate among
of all
normal samplin
cells g
transmit periods
ted on
the port.
ATM_IF_ Indicates Cells/s Average -

OUTRAT the value of
E_AVG average counts
rate of in all
normal samplin
cells g
transmit periods
ted on
the port.


Name Name ance ance
ance ance Method
Entry Entry
ATM_CE Indicates 0.0001 Value Percentage of valid cells = (Total number of cells -
LL_AVAI the obtained Number of HEC-detected error cells)/Total number of
LABILITY percenta in the cells
ge of last
valid samplin
cells. g period

ON th in all
utilizatio samplin
n rate of g
the port periods
in the
receive
direction
.

ON th in all
utilizatio samplin
n rate of g
the port periods
in the
transmit
direction
.
ATM_U Indicates Cells/s Maximu ATM_UNI1_INRATE_MAX is based on VPIs/VCIs.

NI1_INR the m value
ATE_MA maximu obtained
X m rate among
of all
receiving samplin
correct g
cells on periods
the
UNI1
side of
ATM
connecti
ons.


Name Name ance ance
ance ance Method
Entry Entry
ATM_U Indicates Cells/s Minimu ATM_UNI1_INRATE_MIN is based on VPIs/VCIs.

NI1_INR the m value
ATE_MI minimu obtained
N m rate among
of all
receiving samplin
correct g
cells on periods
the
UNI1
side of
ATM
connecti
ons.
ATM_U Indicates Cells/s Average ATM_UNI1_INRATE_AVG is based on VPIs/VCIs.

NI1_INR the value of
ATE_AV average counts
G rate of in all
receiving samplin
correct g
cells on periods
the
UNI1
side of
ATM
connecti
ons.
ATM_U Indicates Cells/s Maximu ATM_UNI1_OUTRATE_MAX is based on VPIs/VCIs.

NI1_OU the m value
TRATE_ maximu obtained
MAX m rate among
of all
transmit samplin
ting g
correct periods
cells on
the
UNI1
side of
ATM
connecti
ons.


Name Name ance ance
ance ance Method
Entry Entry
ATM_U Indicates Cells/s Minimu ATM_UNI1_OUTRATE_MIN is based on VPIs/VCIs.

NI1_OU the m value
TRATE_ minimu obtained
MIN m rate among
of all
transmit samplin
ting g
correct periods
cells on
the
UNI1
side of
ATM
connecti
ons.
ATM_U Indicates Cells/s Average ATM_UNI1_OUTRATE_AVG is based on VPIs/VCIs.

NI1_OU the value of
TRATE_A average counts
VG rate of in all
transmit samplin
ting g
correct periods
cells on
the
UNI1
side of
ATM
connecti
ons.
ATM_U Indicates Cells/s Maximu ATM_UNI2_INRATE_MAX is based on VPIs/VCIs.

NI2_INR the m value
ATE_MA maximu obtained
X m rate among
of all
receiving samplin
correct g
cells on periods
the
UNI2
side of
ATM
connecti
ons.


Name Name ance ance
ance ance Method
Entry Entry
ATM_U Indicates Cells/s Minimu ATM_UNI2_INRATE_MIN is based on VPIs/VCIs.

NI2_INR the m value
ATE_MI minimu obtained
N m rate among
of all
receiving samplin
correct g
cells on periods
the
UNI2
side of
ATM
connecti
ons.
ATM_U Indicates Cells/s Average ATM_UNI2_INRATE_AVG is based on VPIs/VCIs.

NI2_INR the value of
ATE_AV average counts
G rate of in all
receiving samplin
correct g
cells on periods
the
UNI2
side of
ATM
connecti
ons.
ATM_U Indicates Cells/s Maximu ATM_UNI2_OUTRATE_MAX is based on VPIs/VCIs.

NI2_OU the m value
TRATE_ maximu obtained
MAX m rate among
of all
transmit samplin
ting g
correct periods
cells on
the
UNI2
side of
ATM
connecti
ons.


Name Name ance ance
ance ance Method
Entry Entry
ATM_U Indicates Cells/s Minimu ATM_UNI2_OUTRATE_MIN is based on VPIs/VCIs.

NI2_OU the m value
TRATE_ minimu obtained
MIN m rate among
of all
transmit samplin
ting g
correct periods
cells on
the
UNI2
side of
ATM
connecti
ons.
ATM_U Indicates Cells/s Average ATM_UNI2_OUTRATE_AVG is based on VPIs/VCIs.

NI2_OU the value of
TRATE_A average counts
VG rate of in all
transmit samplin
ting g
correct periods
cells on
the
UNI2
side of
ATM
connecti
ons.
ATM_U Indicates Cells Accumul ATM_UNI1_INCELLS is used to determine whether

NI1_INC the total ated ATM connections are normal.
ELLS number value
of
receiving
correct
cells on
the
UNI1
side of
ATM
connecti
ons.


Name Name ance ance
ance ance Method
Entry Entry
ATM_U Indicates Cells Accumul ATM_UNI1_OUTCELLS is used to determine whether

NI1_OU the total ated ATM connections are normal.
TCELLS number value
of
transmit
ting
correct
cells on
the
UNI1
side of
ATM
connecti
ons.
ATM_U Indicates Cells Accumul ATM_UNI2_INCELLS is used to determine whether

NI2_INC the total ated ATM connections are normal.
ELLS number value
of
receiving
correct
cells on
the
UNI2
side of
ATM
connecti
ons.
ATM_U Indicates Cells Accumul ATM_UNI2_OUTCELLS is used to determine whether

NI2_OU the total ated ATM connections are normal.
TCELLS number value
of
transmit
ting
correct
cells on
the
UNI2
side of
ATM
connecti
ons.

Table 12-53 CES performance entry list (ML1/MD1)

Name Name ance ance
ance ance Method
Entry Entry
CES_MIS Indicates Packets Accumul -

ORDERP the ated
KTS number value
of lost
disorder
ed
packets.
CES_STR Indicates Packets Accumul -

AYPKTS the ated
number value
of mis-
connect
ed
packets.
CES_MA Indicates Packets Accumul -

LPKTS the ated
number value
of
deforme
d
frames.
CES_JTR Indicates Times Accumul -

UDR the ated
number value
of jitter
buffer
underflo
ws.

OVR the ated
number value
of jitter
buffer
overflow
s.
CES_LOS Indicates Packets Accumul -

PKTS the ated
number value
of lost
packets.


Name Name ance ance
ance ance Method
Entry Entry
CES_RX_ Indicates Packets Accumul -

PKTS the ated
number value
of
received
packets.
CES_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmit
ted
packets.
Table 12-54 PW performance entry list (ML1/MD1)

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


Name Name ance ance
ance ance Method
Entry Entry
MPLS_P Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by
W_FLR the obtained the source - Number of packets received by the
packet in the sink)/Number of packets transmitted by the source
loss rate last
on the samplin
PW. g period
MPLS_P Indicates Packets Accumul Number of lost packets = Number of packets

W_FL the ated transmitted by the source - Number of packets
packet value received by the sink (Both numbers are detected by
loss the performance monitoring scheme of OAM.)
number
on the
PW.
MPLS_P Indicates µs Value Frame delay = Time when the source sends a request
W_FD the obtained packet - Time when the source receives the response
frame in the packet
delay on last
the PW. samplin
g period
MPLS_P Indicates µs Value Frame delay variation is the difference between two
W_FDV the obtained frame delay test results.
frame in the
delay last
variation samplin
on the g period
PW.

Table 12-55 PPP performance entry list (ML1/MD1)

Name Name ance ance
ance ance Method
Entry Entry
PPP_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmit
ted PPP
packets.
PPP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmit
ted 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.

FCSPKTS the ated
number value
of PPP
packets
that
received
FCS
faults.


Name Name ance ance
ance ance Method
Entry Entry

LOSPKTS the ated
number value
of PPP
packets
dropped
in the
transmit
ting
process.

LOSPKTS the ated
number value
of
relieved
abnorm
al PPP
packets.
PPP_RX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of received bytes x
BW_UTI the PPP obtained 8/Monitoring period)/Configured or actual
LIZATIO bandwid in the bandwidth
N th usage last
in the samplin
receive g period
direction
.
PPP_TX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of transmitted

BW_UTI the PPP obtained bytes x 8/Monitoring period)/Configured or actual
N th usage last
in the samplin
transmit g period
direction
.

Table 12-56 MLPPP performance entry list (ML1/MD1)

Name Name ance ance
ance ance Method
Entry Entry
MP_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmit
ted MP
packets.
MP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmit
ted 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.

ERRPKTS the ated
number value
of
received
MP
packets.


Name Name ance ance
ance ance Method
Entry Entry
MP_TX_ Indicates Packets Accumul The transmitted MP packets include service and
TOTALP the total ated protocol packets.
KTS number value
of
transmit
ted MP
packets.
MP_RX_ Indicates Packets Accumul The received MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
received
MP
packets.
MP_RX_ Indicates 0.0001 Value MP bandwidth usage = (Number of received bytes x

BW_UTI the MP obtained 8/Monitoring period)/Configured or actual
N th usage last
in the samplin
receive g period
direction
.
MP_TX_ Indicates 0.0001 Value MP bandwidth usage = (Number of transmitted bytes

BW_UTI the MP obtained x 8/Monitoring period)/Configured or actual
N th usage last
in the samplin
transmit g period
direction
.
12.1.9 CQ1
The RMON performance that the MP1 board supports includes CES performance,
PW performance, PPP performance, and MLPPP performance.



count.
performance count.
performance count.

count.

Table 12-58 CES performance entry list (MP1)

Name Name ance ance
ance ance Method
Entry Entry

the ated
number value
of lost
CES_MIS disorder
ORDERP ed
KTS packets. -
CES_STR Indicates Packets Accumul -

AYPKTS the ated
number value
of mis-
connect
ed
packets.
CES_MA Indicates Packets Accumul -

LPKTS the ated
number value
of
deforme
d
frames.

UDR the ated
number value
of jitter
buffer
underflo
ws.

OVR the ated
number value
of jitter
buffer
overflow
s.
CES_LOS Indicates Packets Accumul -

PKTS the ated
number value
of lost
packets.


Name Name ance ance
ance ance Method
Entry Entry
CES_RX_ Indicates Packets Accumul -

PKTS the ated
number value
of
received
packets.
CES_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmit
ted
packets.
Table 12-59 PW performance entry list (MP1)

Name Name ance ance
ance ance Method
Entry Entry

PKTS the ated
number value
of
packets
received
from
PWs.

Table 12-60 PPP performance entry list (MP1)

Name Name ance ance
ance ance Method
Entry Entry

PKTS the ated
number value
of
transmit
ted PPP
packets.
PPP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmit
ted PPP
packets.

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.

FCSPKTS the ated
number value
of PPP
packets
that
received
FCS
faults.


Name Name ance ance
ance ance Method
Entry Entry

LOSPKTS the ated
number value
of PPP
packets
dropped
in the
transmit
ting
process.

LOSPKTS the ated
number value
of
relieved
abnorm
al PPP
packets.
PPP_RX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of received bytes x
BW_UTI the PPP obtained 8/Monitoring period)/Configured or actual
N th usage last
in the samplin
receive g period
direction
.
PPP_TX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of transmitted

BW_UTI the PPP obtained bytes x 8/Monitoring period)/Configured or actual
N th usage last
in the samplin
transmit g period
direction
.

Table 12-61 MLPPP performance entry list (MP1)

Name Name ance ance
ance ance Method
Entry Entry
MP_TX_ Indicates Packets Accumul -

PKTS the ated
number value
of
transmit
ted MP
packets.
MP_TX_ Indicates Bytes Accumul -

BYTES the ated
number value
of bytes
of
transmit
ted MP
packets.

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.

ERRPKTS the ated
number value
of
received
MP
packets.


Name Name ance ance
ance ance Method
Entry Entry
MP_TX_ Indicates Packets Accumul The transmitted MP packets include service and
TOTALP the total ated protocol packets.
KTS number value
of
transmit
ted MP
packets.
MP_RX_ Indicates Packets Accumul The received MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
received
MP
packets.
MP_RX_ Indicates 0.0001 Value MP bandwidth usage = (Number of received bytes x

BW_UTI the MP obtained 8/Monitoring period)/Configured or actual
N th usage last
in the samplin
receive g period
direction
.
MP_TX_ Indicates 0.0001 Value MP bandwidth usage = (Number of transmitted bytes

BW_UTI the MP obtained x 8/Monitoring period)/Configured or actual
N th usage last
in the samplin
transmit g period
direction
.
12.1.10 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.



count.
performance count.
performance count.

count.

Table 12-63 L2VPNa performance entry list (CSHN)

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

CVBYTES the ated
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
CVPKTS the ated of a 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
CVBYTES the ated a service.
number value
of bytes
received
on the
V-UNI.


Name Name ance ance
ance ance Method
Entry Entry
VLAN_R Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring
X_BPS the bit obtained period
rate in in the
the last
receive samplin
direction g period
of a
VLAN to
which a
V-UNI
belongs.
VLAN_R Indicates Packets/ Value Packet rate = Number of received packets/Monitoring

X_PPS the s obtained period
packet in the
rate in last
the samplin
receive g period
direction
of a
VLAN to
which a
V-UNI
belongs.
Table 12-64 Tunnel performance entry list (CSHN)

Name Name ance ance
ance ance Method
Entry Entry
TUNNEL Indicates Packets Accumul Indicates the number of packets received in the
_REVERS the ated reverse tunnel of a bidirectional transit tunnel.
E_RCVPK number value
TS of
packets
received
in the
reverse
tunnel.


Name Name ance ance
ance ance Method
Entry Entry
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in the reverse
_REVERS the ated tunnel of a bidirectional transit tunnel.
E_RCVBY number value
TES of bytes
received
in the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets received in a tunnel.
_RCVPKT the ated
S number value
of
packets
received
in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in a tunnel.
_RCVBYT the ated
ES number value
of bytes
received
in the
tunnel.
TUNNEL Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring
_REVERS the bit obtained period
E_RX_BP rate in in the
S the last
receive samplin
direction g period
of a
reverse
tunnel.
TUNNEL Indicates Packets/ Value Packet rate = Number of received packets/Monitoring

_REVERS the s obtained period
E_RX_PP packet in the
S rate in last
the samplin
receive g period
direction
of a
reverse
tunnel.


Name Name ance ance
ance ance Method
Entry Entry
_RX_BPS the bit obtained period
rate in in the
the last
receive samplin
direction g period
of a
monitor
ed
object.

_RX_PPS the s obtained period
packet in the
rate in last
the samplin
receive g period
direction
of a
monitor
ed
object.
Table 12-65 L2VPN PW performance entry list (CSHN)

Name Name ance ance
ance ance Method
Entry Entry

PKTS the ated
number value
of
packets
received
on the
PW.


Name Name ance ance
ance ance Method
Entry Entry

BYTES the ated
number value
of bytes
received
on the
PW.
PW_DR Indicates Packets Accumul -

OPPKTS the ated
number value
of
packets
discarde
d on the
PW.
PW_RX_ Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring
BPS the bit obtained period
rate in in the
the last
receive samplin
direction g period
of a
monitor
ed
object.
PW_RX_ Indicates Packets/ Value Packet rate = Number of received packets/Monitoring

PPS the s obtained period
packet in the
rate in last
the samplin
receive g period
direction
of a
monitor
ed
object.

Table 12-66 ETH OAM performance entry list (CSHN)

Name Name ance ance
ance ance Method
Entry Entry
ETH_CF Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by
M_FLR the obtained the source MEP - Number of packets received by the
Ethernet in the sink MEP)/Number of packets transmitted by the
service last source MEP
packet samplin
loss rate. g period
ETH_CF Indicates Packets Accumul Number of lost packets = Number of packets

M_FL the ated transmitted by the source - Number of packets
number value received by the sink (Both numbers are detected by
of the performance monitoring scheme of OAM.)
discarde
d
Ethernet
service
packets.
ETH_CF Indicates µs Value Frame delay = Time when the source MEP sends a
M_FD the obtained request packet - Time when the source MEP receives
Ethernet in the the response packet
service last
delay. samplin
g period
ETH_CF Indicates µs Value Frame delay variation is the difference between two
M_FDV the obtained frame delay test results.
Ethernet in the
service last
delay samplin
variation g period
.
M_FLR_P the obtained the source MEP - Number of packets received by the
RIn packet in the sink MEP)/Number of packets transmitted by the
NOTE loss rate last source MEP
0≤n≤ of the samplin
7 Ethernet g period
service
with a
priority
of n.


Name Name ance ance
ance ance Method
Entry Entry

M_FL_PR the ated transmitted by the source - Number of packets
In number value received by the sink (Both numbers are detected by
NOTE of lost the performance monitoring scheme of OAM.)
0≤n≤ packets
7 in the
Ethernet
service
with a
priority
of n.
ETH_CF Indicates µs Value Bidirectional frame delay = Time when the source
M_FD_P the obtained sends a request packet - Time when the source
RIn delay of in the receives the response packet
NOTE the last
0≤n≤ Ethernet samplin
7 service g period
with a
priority
of n.
ETH_CF Indicates µs Value Frame delay variation is the difference between two
M_FDV_ the obtained frame delay test results.
PRIn delay in the
NOTE variation last
7 Ethernet g period
service
with a
priority
of n.

Table 12-67 MPLS-TP OAM performance entry list (CSHN)

Name Name ance ance
ance ance Method
Entry Entry
loss rate last
on the samplin
PW. g period
W_FLR_ the obtained the source - Number of packets received by the
N packet in the sink)/Number of packets transmitted by the source
loss rate last
on the samplin
PW at g period
the near
end.

number
on the
PW.

W_FL_N the ated transmitted by the source - Number of packets
of lost the performance monitoring scheme of OAM.)
packets
on the
PW at
the near
end.
MPLS_P Indicates µs Value Frame delay = Time when the source sends a request
frame in the packet
delay on last
the PW. samplin
g period


Name Name ance ance
ance ance Method
Entry Entry
MPLS_P Indicates µs Value Frame delay variation is the difference between two
frame in the
delay last
variation samplin
on the g period
PW.
MPLS_T Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by
UNNEL_ the obtained the source - Number of packets received by the
FLR packet in the sink)/Number of packets transmitted by the source
loss rate last
in the samplin
tunnel. g period
FLR_N packet in the sink)/Number of packets transmitted by the source
loss rate last
on the samplin
tunnel g period
at the
near
end.
MPLS_T Indicates Packets Accumul Number of lost packets = Number of packets

UNNEL_ the ated transmitted by the source - Number of packets
FL packet value received by the sink (Both numbers are detected by
number
in the
tunnel.

FL_N number value received by the sink (Both numbers are detected by
packets
on the
tunnel
at the
near
end.


Name Name ance ance
ance ance Method
Entry Entry
MPLS_T Indicates µs Value Frame delay = Time when the source sends a request
UNNEL_ the obtained packet - Time when the source receives the response
FD frame in the packet
delay in last
the samplin
tunnel. g period
MPLS_T Indicates µs Value Frame delay variation is the difference between two
UNNEL_ the obtained frame delay test results.
FDV frame in the
delay last
variation samplin
in the g period
tunnel.
Table 12-68 1+1/XPIC performance entry list (CSHN)

Name Name ance ance
ance ance Method
Entry Entry
RXPKTS Indicates Packets Accumul

the ated
received. packets are included.
events.
Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in

the ated received packets (including bad packets), including
RXOCTE bytes value framing bits but not FCS bytes.
TS received.


Name Name ance ance
ance ance Method
Entry Entry
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
RXPKT64 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
received ated
(64 value
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
received ated
(65-127 value
bytes in
length)
8 received ated
(128-25 value
5 bytes
in
length)
6 received ated
(256-51 value
1 bytes
in
length)
2 received ated
(512-10 value
23 bytes
in
length)
(1024-1 value to MTU bytes (including FCS bytes but not framing
518 bits).
bytes in
length)
packets value
transmit
ted.
transmit
ted


Name Name ance ance
ance ance Method
Entry Entry
frames.
D the ated
bytes in value
received
good
packets.
OD the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes to bits).
the MTU
in
length)
Table 12-69 PLA/1+1/XPIC performance entry list (CSHN)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.

TS received.
t
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
bytes in
length)
bytes in
length)
5 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
1 bytes
in
length)
23 bytes bits).
in
length)
518 bits).
bytes in
length)
packets value
transmit
ted.
transmit
ted
frames.
D the ated
bytes in value
received
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
OD the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)
(65-127
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes to bits).
the MTU
in
length)
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods
a:
● VUNI represents virtual UNI, represents the sink or source of services on the UNI side.
● The E-LAN services transmitted by the OptiX RTN 980 do not support the VLAN-based
and VUNI-based RMON performance statistics.
12.1.11 CSHNA
The RMON performance that the CSHNA board supports includes L2VPN



count.
performance count.
performance count.

count.
Table 12-71 Basic performance entry list of an Ethernet port (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
bytes in
length)
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(128-25 value 255 bytes (including FCS bytes but not framing bits)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length)
518 bits).
bytes in
length)
ETHUN Indicates Packets Accumul An undersized packet has less than 64 bytes
DER the ated (including FCS bytes but excluding framing bits).
number value
of
received
packets
that are
undersiz
ed but
error-
free.


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .

Table 12-72 Extended performance entry list of an Ethernet port (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
bytes to bits).
the MTU
in
length)
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.

the m value
maximu obtained
m among

the m value
minimu obtained
m among

the value of
average counts

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -


Name Name ance ance
ance ance Method
Entry Entry

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
Table 12-73 L2VPNa performance entry list (CSHNA)

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

CVBYTES the ated
number value
of bytes
in the
packets
received
at the V-
UNI
VLAN.


Name Name ance ance
ance ance Method
Entry Entry
VUNI_R Indicates Packets Accumul Indicates the number of packets received on a V-UNI
CVPKTS the ated of a 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
CVBYTES the ated a service.
number value
of bytes
received
on the
V-UNI.
VLAN_R Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring
X_BPS the bit obtained period
rate in in the
the last
receive samplin
direction g period
of a
VLAN to
which a
V-UNI
belongs.
VLAN_R Indicates Packets/ Value Packet rate = Number of received packets/Monitoring

X_PPS the s obtained period
packet in the
rate in last
the samplin
receive g period
direction
of a
VLAN to
which a
V-UNI
belongs.

Table 12-74 Tunnel performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
TS of
packets
received
in the
reverse
tunnel.
TES of bytes
received
in the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets received in a tunnel.
_RCVPKT the ated
S number value
of
packets
received
in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in a tunnel.
_RCVBYT the ated
ES number value
of bytes
received
in the
tunnel.
_REVERS the bit obtained period
E_RX_BP rate in in the
S the last
receive samplin
direction g period
of a
reverse
tunnel.


Name Name ance ance
ance ance Method
Entry Entry

_REVERS the s obtained period
E_RX_PP packet in the
S rate in last
the samplin
receive g period
direction
of a
reverse
tunnel.
_RX_BPS the bit obtained period
rate in in the
the last
receive samplin
direction g period
of a
monitor
ed
object.

_RX_PPS the s obtained period
packet in the
rate in last
the samplin
receive g period
direction
of a
monitor
ed
object.

Table 12-75 L2VPN PW performance entry list (CSHNA)

Name Name ance ance
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
discarde
d on the
PW.
PW_RX_ Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring
BPS the bit obtained period
rate in in the
the last
receive samplin
direction g period
of a
monitor
ed
object.


Name Name ance ance
ance ance Method
Entry Entry
PW_RX_ Indicates Packets/ Value Packet rate = Number of received packets/Monitoring

PPS the s obtained period
packet in the
rate in last
the samplin
receive g period
direction
of a
monitor
ed
object.
Table 12-76 ETH OAM performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
M_FLR the obtained the source MEP - Number of packets received by the
Ethernet in the sink MEP)/Number of packets transmitted by the
service last source MEP
packet samplin
loss rate. g period

of the performance monitoring scheme of OAM.)
discarde
d
Ethernet
service
packets.
ETH_CF Indicates μs Value Frame delay = Time when the source MEP sends a
M_FD the obtained request packet - Time when the source MEP receives
Ethernet in the the response packet
service last
delay. samplin
g period


Name Name ance ance
ance ance Method
Entry Entry
ETH_CF Indicates μs Value Frame delay variation is the difference between two
M_FDV the obtained frame delay test results.
Ethernet in the
service last
delay samplin
variation g period
.
M_FLR_P the obtained the source MEP - Number of packets received by the
RIn packet in the sink MEP)/Number of packets transmitted by the
NOTE loss rate last source MEP
7 Ethernet g period
service
with a
priority
of n.

M_FL_PR the ated transmitted by the source - Number of packets
In number value received by the sink (Both numbers are detected by
NOTE of lost the performance monitoring scheme of OAM.)
0≤n≤ packets
7 in the
Ethernet
service
with a
priority
of n.
ETH_CF Indicates μs Value Bidirectional frame delay = Time when the source
M_FD_P the obtained sends a request packet - Time when the source
RIn delay of in the receives the response packet
NOTE the last
7 service g period
with a
priority
of n.


Name Name ance ance
ance ance Method
Entry Entry
ETH_CF Indicates μs Value Frame delay variation is the difference between two
M_FDV_ the obtained frame delay test results.
PRIn delay in the
NOTE variation last
7 Ethernet g period
service
with a
priority
of n.
Table 12-77 MPLS-TP OAM performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
loss rate last
on the samplin
PW. g period
W_FLR_ the obtained the source - Number of packets received by the
N packet in the sink)/Number of packets transmitted by the source
loss rate last
on the samplin
PW at g period
the near
end.

number
on the
PW.


Name Name ance ance
ance ance Method
Entry Entry

packets
on the
PW at
the near
end.
MPLS_P Indicates μs Value Frame delay = Time when the source sends a request
frame in the packet
delay on last
the PW. samplin
g period
MPLS_P Indicates μs Value Frame delay variation is the difference between two
frame in the
delay last
variation samplin
on the g period
PW.
FLR packet in the sink)/Number of packets transmitted by the source
loss rate last
on the samplin
tunnel. g period
FLR_N packet in the sink)/Number of packets transmitted by the source
loss rate last
on the samplin
tunnel g period
at the
near
end.


Name Name ance ance
ance ance Method
Entry Entry

FL packet value received by the sink (Both numbers are detected by
number
in the
tunnel.

packets
on the
tunnel
at the
near
end.
MPLS_T Indicates μs Value Frame delay = Time when the source sends a request
UNNEL_ the obtained packet - Time when the source receives the response
FD frame in the packet
delay in last
the samplin
tunnel. g period
MPLS_T Indicates μs Value Frame delay variation is the difference between two
UNNEL_ the obtained frame delay test results.
FDV frame in the
delay last
variation samplin
in the g period
tunnel.

Table 12-78 1+1/XPIC performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.

TS received.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
bytes in
length)
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length)


Name Name ance ance
ance ance Method
Entry Entry
518 bits).
bytes in
length)
packets value
transmit
ted.
transmit
ted
frames.
D the ated
bytes in value
received
good
packets.
OD the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.


Name Name ance ance
ance ance Method
Entry Entry
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)
bytes to bits).
the MTU
in
length)

Table 12-79 N+1 performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.

TS received.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
packets value
transmit
ted.
transmit
ted
frames.
D the ated
bytes in value
received
good
packets.
OD the ated
bytes in value
transmit
ted
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
Table 12-80 NMS port performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

the ated
number value
of
received Corrupted packets, broadcast packets, and multicast
packets. packets are included.


Name Name ance ance
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
corrupte
RXOCTE d
TS packets).
t
packets
received.
t
packets
received.
PORT_R Indicates 0.0001 Average Bandwidth utilization on a port in the receive

X_BW_U the value of direction = (Number of received bytes x 8/Monitoring
TILIZATI bandwid counts period)/Configured or actual bandwidth
ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry
PORT_T Indicates 0.0001 Average Bandwidth utilization on a port in the transmit

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
bytes in
length)
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length)


Name Name ance ance
ance ance Method
Entry Entry
518 bits).
bytes in
length).
TXPKTS Indicates Packets Accumul Corrupted packets, broadcast packets, and multicast
number value
of
transmit
ted
packets.
TXOCTE Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
TS the ated
number value
of bytes
in
transmit
ted
packets
(includin
g
corrupte
d
packets).
D the ated
number value
of bytes
in error-
free
packets
transmit
ted.
OD the ated
number value
of bytes
in error-
free
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
TXUNIC Indicates Packets Accumul The packets that are dropped and fail to be
number value
of
unicast
packets
transmit
ted.
RXUNIC Indicates Packets Accumul Only error-free packets are included.

AST the ated
number value
of error-
free
unicast
packets
received.
TXMULC Indicates Packets Accumul The packets that are dropped and fail to be
number value
of
multicas
t
packets
transmit
ted.
TXBRDC Indicates Packets Accumul The packets that are dropped and fail to be
number value
of
broadcas
t
packets
transmit
ted.
RXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
RAMESP of in the
EED receiving last
error- samplin
free full- g period
frame
bits.


Name Name ance ance
ance ance Method
Entry Entry
TXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
RAMESP of in the
EED transmit last
ting samplin
error- g period
free full-
frame
bits.
RXFULLB Indicates Bytes Accumul FCS bytes and framing bits are included.
GOOD the ated
number value
of error-
free full-
frame
bytes
received.
TXFULLB Indicates Bytes Accumul FCS bytes and framing bits are included.
GOOD the ated
number value
of error-
free full-
frame
bytes
transmit
ted.
bytes in
length).
(65-127
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes to bits).
the MTU
in
length)
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
loss rate in all
in the samplin
receive g
direction periods
.
TX_DRO Indicates 0.0001 Average Packet loss rate in the transmit direction = Number
P_RATIO the value of of discarded packets/Total number of transmitted
packet counts packets
loss rate in all
in the samplin
transmit g
direction periods
.

Table 12-81 Port traffic classification performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
rate in last
the samplin
receive g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
rate in last
the samplin
transmit g period
direction
of a
matched
flow.
Table 12-82 Port priority performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.
Table 12-83 Port DS domain performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain


Name Name ance ance
ance ance Method
Entry Entry

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.

NPRI_BY the ated
TES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

P_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

Table 12-84 PLA/EPLA performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
ETH_RX_ Indicates kbit/s Maximu

THROU the m value
GHPUT_ maximu obtained
MAX m among
through all
put on a samplin
port in g
the periods
receive Maximum throughput = Number of received bytes
direction (including inter-frame gaps and preambles)/
. Monitoring period
ETH_RX_ Indicates kbit/s Minimu

THROU the m value
GHPUT_ minimu obtained
MIN m among
through all
put on a samplin
port in g
the periods
receive Minimum throughput = Number of received bytes
. Monitoring period
ETH_RX_ Indicates kbit/s Average

THROU the value of
GHPUT_ average counts
AVG through in all
put on a samplin
port in g
the periods
receive Average throughput = Number of received bytes
. Monitoring period
ETH_TX_ Indicates kbit/s Maximu

THROU the m value
MAX m among
transmit all
through samplin Throughput at the transmit direction = Total number
put of a g of received bytes (including the preamble and frame
port. periods gap)/Measurement period


Name Name ance ance
ance ance Method
Entry Entry
ETH_TX_ Indicates kbit/s Minimu

THROU the m value
MIN m among
transmit all
ETH_TX_ Indicates kbit/s Average

THROU the value of
AVG transmit in all

the ated
events.

TS received.
t
packets
received.
t
packets
received.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all NOTE
utilizatio samplin The maximum bandwidth of an enhanced physical link
n on a g aggregation (EPLA) group is 2.5 Gbit/s. If the physical
port in periods bandwidth configured for an EPLA group exceeds 2.5 Gbit/s,
bandwidth utilization is still calculated based on 2.5 Gbit/s.
the
receive
direction
.

ON th in all NOTE
the
transmit
direction
.

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
bytes in
length)
bytes in
length)
5 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
1 bytes
in
length)
23 bytes bits).
in
length)
518 bits).
bytes in
length)
packets value
transmit
ted.
P_RATIO the value of of packets lost in the transmit direction/Total number
packet counts of transmitted packets
loss rate in all
in the samplin
transmit g
direction periods
.
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
TXBPS Indicates Bit/s Value Bit rate in the transmit direction = Number of
rate in in the
the last
transmit samplin
direction g period
.
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.
the second obtained transmitted packets/Monitoring period
packet in the
rate in last
the samplin
transmit g period
direction
.
TX_DRO Indicates Packets Accumul -

P_PKTS the ated
number value
of
packets
lost in
the
transmit
direction
.
transmit
ted


Name Name ance ance
ance ance Method
Entry Entry
frames.
D the ated
bytes in value
received
good
packets.
OD the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes to bits).
the MTU
in
length)
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods
a:
● VUNI represents virtual UNI, represents the sink or source of services on the UNI side.
● The E-LAN services transmitted by the OptiX RTN 980 do not support the VLAN-based
and VUNI-based RMON performance statistics.
12.1.12 CSHNU
The RMON performance that the CSHNU board supports includes L2VPN



count.
performance count.
performance count.

count.
Table 12-86 Basic performance entry list of an Ethernet port (CSHNU)

Name Name ance ance
ance ance Method
Entry Entry
ETHDRO Indicates Times Accumul ETHDROP indicates the number of events in which
P that ated packet loss occurs due to resource deficiency. This
packets value count is not the number of discarded packets but the
are lost. number of times that packets are discarded.
R that ated longer than MTU bytes (including FCS bytes but not
packets
are
received.


Name Name ance ance
ance ance Method
Entry Entry
ETHUN Indicates Packets Accumul Indicates the number of received packets that
DER that ated contain fewer than 64 bytes (including FCS bytes but
undersiz value not framing bits) and do not contain any other
e errors.
packets
are
received.
PORT_R Indicates 0.0001 Average Bandwidth utilization on a specified port in the

X_BW_U the value of receive direction = (Number of received bytes x 8/
TILIZATI bandwid counts Monitoring period)/Configured or actual bandwidth
ON th in
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

X_BW_U the value of direction = (Number of transmitted bytes x 8/
TILIZATI bandwid counts Monitoring period)/Configured or actual bandwidth
ON th in
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
Indicates Bytes Accumul Indicates the total number of bytes (including FCS
RXOCTE bytes ated bytes but not framing bits) in received packets
TS received. value (including corrupted packets).
RXMULC Indicates Packets Accumul Indicates the total number of received good packets
AST multicas ated (excluding broadcast packets) whose destination
t value address is a multicast address.
packets
received.
RXBRDC Indicates Packets Accumul Indicates the total number of received good packets
AST broadcas ated (excluding multicast packets) whose destination
t value address is a broadcast address.
packets
received.
RXPKTS Indicates Packets Accumul Indicates the total number of received packets,
packets ated including corrupted packets, broadcast packets, and
received. value multicast packets.


Name Name ance ance
ance ance Method
Entry Entry
packets ated (including corrupted packets) with a length of 64
received value bytes (including FCS bytes but not framing bits).
(64
bytes in
length).
packets ated (including corrupted packets) with a length of 65 to
received value 127 bytes (including FCS bytes but not framing bits).
(65–127
bytes in
length).
8 packets ated (including corrupted packets) with a length of 128 to
(128–
255
bytes in
length).
(256–
511
bytes in
length).
received value 1023 bytes (including FCS bytes but not framing
(512– bits).
1023
bytes in
length).
24 packets ated (including corrupted packets) with a length of 1024
received value to MTU bytes (including FCS bytes but not framing
(1024– bits).
1518
bytes in
length).

Table 12-87 Extended performance entry list of an Ethernet port (CSHNU)

Name Name ance ance
ance ance Method
Entry Entry
ETHFCS Indicate Frames Accumul Indicates the number of received frames that contain
s FCS ated an integer number of bytes and FCS check errors.
errored value
frames.
PORT_R Indicate 0.0001 Average Average bandwidth utilization on a specified port in

X_BW_U s the value of the receive direction = (Number of received bytes x 8/
TILIZATI average counts Monitoring period)/Configured or actual bandwidth
ON_AVG bandwid in
th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.
Indicate 0.0001 Maximu Maximum bandwidth utilization on a specified port in

s the m value the receive direction = (Number of received bytes x 8/
maximu of Monitoring period)/Configured or actual bandwidth
m counts
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .
Indicate 0.0001 Minimu Minimum bandwidth utilization on a specified port in

s the m value the receive direction = (Number of received bytes x 8/
minimu of Monitoring period)/Configured or actual bandwidth
m counts
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry
Indicate 0.0001 Average Average bandwidth utilization on a specified port in

s the value of the transmit direction = (Number of transmitted
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .
Indicate 0.0001 Maximu Maximum bandwidth utilization on a specified port in

s the m value the transmit direction = (Number of transmitted
m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .
Indicate 0.0001 Minimu Minimum bandwidth utilization on a specified port in

s the m value the transmit direction = (Number of transmitted
m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry
RX_DRO Indicate 0.0001 Average Packet loss rate in the receive direction = Number of
P_RATIO s the value of discarded packets/Total number of received packets
packet counts
loss rate in
in the samplin
receive g
direction periods
.
TX_DRO Indicate 0.0001 Average Packet loss rate in the transmit direction = Number of
P_RATIO s the value of discarded packets/Total number of transmitted
loss rate in
in the samplin
transmit g
direction periods
.
TXBGOO Indicate Bytes Accumul Indicates the total number of bytes (including FCS
D s the ated bytes but not framing bits) in transmitted good
number value packets.
of bytes
in the
transmit
ted
good
packets.
RXBGO Indicate Bytes Accumul Indicates the total number of bytes (including FCS
OD s the ated bytes but not framing bits) in received good packets.
number value
of bytes
in
received
good
packets.
RXBRDC Indicate 0.0001 Average Indicates the ratio of broadcast and multicast packets
AST_RAT s the value of to all packets in the receive direction.
IO broadca counts
st traffic in
ratio in samplin
the g
receive periods
direction
.


Name Name ance ance
ance ance Method
Entry Entry
TXBRDC Indicate 0.0001 Average Indicates the ratio of broadcast and multicast packets
AST_RAT s the value of to all packets in the transmit direction.
IO broadca counts
st traffic in
ratio in samplin
the g
transmit periods
direction
.
TXUNIC Indicate Packets Accumul Indicates the total number of transmitted unicast
AST s unicast ated packets, including discarded packets and packets that
packets value fail to be transmitted.
transmit
ted.
RXUNIC Indicate Packets Accumul Indicates the total number of good unicast packets
AST s unicast ated that are received.
packets value
received.
TXMULC Indicate Packets Accumul Indicates the total number of transmitted multicast
AST s ated packets, including discarded packets and packets that
multicas value fail to be transmitted.
t
packets
transmit
ted.
TXBRDC Indicate Packets Accumul Indicates the total number of transmitted broadcast
AST s ated packets, including discarded packets and packets that
broadca value fail to be transmitted.
st
packets
transmit
ted.
RXGOO Indicate Kbit/s Current Indicates the rate of received good packets, including
DFULLF s the bit value of framing bits (20 bytes) and FCS bytes.
RAMESP rate of counts
EED good in
full- samplin
frame g
packets periods
received.


Name Name ance ance
ance ance Method
Entry Entry
TXGOO Indicate Kbit/s Current Indicates the rate of transmitted good packets,
DFULLF s the bit value of including framing bits (20 bytes) and FCS bytes.
RAMESP rate of counts
EED good in
full- samplin
frame g
packets periods
transmit
ted.
RXFULLB Indicate Bytes Accumul Indicates the total number of bytes in received good
GOOD s good ated packets, including framing bits (20 bytes) and FCS
full- value bytes.
frame
bytes
received.
TXFULLB Indicate Bytes Accumul Indicates the total number of bytes in transmitted
GOOD s good ated good packets, including framing bits (20 bytes) and
full- value FCS bytes.
frame
bytes
transmit
ted.
TX_HS_T Indicate 0.0001 Current Ratio of high-priority service traffic to bandwidth for
RAFF_B s the value of high-priority services in the transmit direction =
W_RATI ratio of counts Number of transmitted bytes x 8/Monitoring period/
O high- in Bandwidth for high-priority services.
priority samplin NOTE
service g This performance entry is supported only by Super EPLA.
traffic to periods
bandwid
th for
high-
priority
services
in the
transmit
direction
.
TXPKTS Indicate Packets Accumul Indicates the total number of transmitted packets,
s ated including corrupted packets, broadcast packets, and
packets value multicast packets.
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
TXBPS Indicate Bit/s Current Bit rate in the transmit direction = Number of
s the bit value of transmitted bytes x 8/Monitoring period
rate in counts
the in
transmit samplin
direction g
. periods
TXPPS Indicate Packets/ Current Packet rate in the transmit direction = Number of
s the second value of transmitted packets/Monitoring period
packet counts
rate in in
the samplin
transmit g
direction periods
.
TXOCTE Indicate Bytes Accumul Indicates the total number of bytes (including FCS
TS s bytes ated bytes but not framing bits) in transmitted packets
transmit value (including corrupted packets).
ted.
RXBBAD Indicate Bytes Accumul Indicates the total number of bytes (including FCS
s bytes ated bytes but not framing bits) in received corrupted
in value packets.
received
corrupte
d
packets.
RXPKT15 Indicate Packets Accumul Indicates the total number of received packets
19 s the ated (including corrupted packets) with a length of 1519
number value to MTU bytes (including FCS bytes but not framing
of bits).
received
packets
(includi
ng
corrupte
d
packets)
with a
length
greater
than
1518
bytes.


Name Name ance ance
ance ance Method
Entry Entry
TXPKT64 Indicate Packets Accumul Indicates the total number of transmitted packets
s the ated (including corrupted packets) with a length of 64
number value bytes (including FCS bytes but not framing bits).
of
transmit
ted
packets
(includi
ng
corrupte
d
packets)
with a
length
of 64
bytes.
s the ated (including corrupted packets) with a length of 65 to
number value 127 bytes (including FCS bytes but not framing bits).
of
transmit
ted
packets
(includi
ng
corrupte
d
packets)
with a
length
of 65 to
127
bytes.


Name Name ance ance
ance ance Method
Entry Entry
8 s the ated (including corrupted packets) with a length of 128 to
of
transmit
ted
packets
(includi
ng
corrupte
d
packets)
with a
length
of 128
to 255
bytes.
of
transmit
ted
packets
(includi
ng
corrupte
d
packets)
with a
length
of 256
to 511
bytes.


Name Name ance ance
ance ance Method
Entry Entry
number value 1023 bytes (including FCS bytes but not framing
of bits).
transmit
ted
packets
(includi
ng
corrupte
d
packets)
with a
length
of 512
to 1023
bytes.
number value to 1518 bytes (including FCS bytes but not framing
of bits).
transmit
ted
packets
(includi
ng
corrupte
d
packets)
with a
length
of 1024
to 1518
bytes.


Name Name ance ance
ance ance Method
Entry Entry
number value to MTU bytes (including FCS bytes but not framing
of bits).
transmit
ted
packets
with a
length
greater
than
1518
bytes.
Indicate Packets Accumul

s the ated
number value
of
packets
lost in
the
transmit
TX_DRO direction
P_PKTS . -
Table 12-88 L2VPNa performance entry list (CSHNU)

Brief Full Perform Perfor Remarks
Name Name ance mance
of a of a Count Counti
Perform Perform Unit ng
ance ance Metho
Entry Entry d
Indicates Packets Accum

the ulated
number value
of
packets
received
at the V-
VLAN_R UNI
CVPKTS VLAN. -


ance ance Metho
Entry Entry d
VLAN_R Indicates Bytes Accum -

CVBYTES the ulated
number value
of bytes
in the
packets
received
at the V-
UNI
VLAN.
VLAN_S Indicates Packets Accum -

NDPKTS the ulated
number value
of
packets
transmit
ted at
the V-
UNI
VLAN.
VLAN_S Indicates Bytes Accum -

NDBYTE the ulated
S number value
of bytes
in the
packets
transmit
ted at
the V-
UNI
VLAN.
VUNI_R Indicates Packets Accum Indicates the number of packets received on the
CVPKTS the ulated specified V-UNI of the specified service.
number value
of
packets
received
on the
V-UNI.


ance ance Metho
Entry Entry d
VUNI_R Indicates Bytes Accum Indicates the number of bytes received on the
CVBYTES the ulated specified V-UNI of the specified service.
number value
of bytes
received
on the
V-UNI.
VUNI_S Indicates Packets Accum Indicates the number of packets transmitted on the
NDPKTS the ulated specified V-UNI of the specified service.
number value
of
packets
transmit
ted on
the V-
UNI.
VUNI_S Indicates Bytes Accum Indicates the number of bytes in the packets
NDBYTE the ulated transmitted on the specified V-UNI of the specified
S number value service.
of bytes
transmit
ted on
the V-
UNI.
VLAN_R Indicates Bit/s Current Bit rate in the receive direction of the specified V-UNI
X_BPS the bit value VLAN = Number of received bytes x 8/Monitoring
rate in of period
the counts
receive in
direction sampli
of the V- ng
UNI periods
VLAN.
VLAN_R Indicates Packets/ Current Packet rate in the receive direction of the specified V-
X_PPS the second value UNI VLAN = Number of received packets/Monitoring
packet of period
rate in counts
the in
receive sampli
direction ng
of the V- periods
UNI
VLAN.


ance ance Metho
Entry Entry d
VLAN_T Indicates Bit/s Current Bit rate in the transmit direction of the specified V-
X_BPS the bit value UNI VLAN = Number of transmitted bytes x 8/
rate in of Monitoring period
the counts
transmit in
direction sampli
of the V- ng
UNI periods
VLAN.
VLAN_T Indicates Packets/ Current Packet rate in the transmit direction of the specified V-
X_PPS the second value UNI VLAN = Number of transmitted bytes x 8/
packet of Monitoring period
rate in counts
the in
transmit sampli
direction ng
of the V- periods
UNI
VLAN.
Table 12-89 Tunnel performance entry list (CSHNU)

Name Name ance ance
ance ance Method
Entry Entry
TS of
packets
received
in the
reverse
tunnel.


Name Name ance ance
ance ance Method
Entry Entry
TES of bytes
received
in the
reverse
tunnel.
_RCVPKT the ated specified tunnel.
S number value
of
packets
received
in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes in the packets received
_RCVBYT the ated in the specified tunnel.
ES number value
of bytes
received
in the
tunnel.
TUNNEL Indicates Bit/s Current Bit rate in the receive direction of the reverse tunnel
_REVERS the bit value of = Number of received bytes x 8/Monitoring period
E_RX_BP rate in counts
S the in
receive samplin
direction g
of the periods
reverse
tunnel.
TUNNEL Indicates Packets/ Current Packet rate in the receive direction of the reverse
_REVERS the second value of tunnel = Number of received packets/Monitoring
E_RX_PP packet counts period
S rate in in
the samplin
receive g
direction periods
of the
reverse
tunnel.


Name Name ance ance
ance ance Method
Entry Entry
TUNNEL Indicates Packets Accumul Indicates the number of packets transmitted in the
_REVERS the ated specified tunnel.
E_SNDP number value
KTS of
packets
transmit
ted in
the
reverse
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes in the packets
_REVERS the ated transmitted in the specified tunnel.
E_SNDB number value
YTES of bytes
transmit
ted in
the
reverse
tunnel.
TUNNEL Indicates Bit/s Current Bit rate in the transmit direction of the reverse tunnel
_REVERS the bit value of = Number of transmitted bytes x 8/Monitoring period
E_TX_BP rate in counts
S the in
transmit samplin
direction g
of the periods
reverse
tunnel.
TUNNEL Indicates Packets/ Current Packet rate in the transmit direction of the reverse
_REVERS the second value of tunnel = Number of transmitted packets/Monitoring
E_TX_PP packet counts period
S rate in in
the samplin
transmit g
direction periods
of the
reverse
tunnel.


Name Name ance ance
ance ance Method
Entry Entry
TUNNEL Indicates Bit/s Current Bit rate in the receive direction of a specified
_RX_BPS the bit value of monitored object = Number of received bytes x 8/
rate in counts Monitoring period
the in
receive samplin
direction g
. periods
TUNNEL Indicates Packets/ Current Packet rate in the receive direction of a specified
_RX_PPS the second value of monitored object = Number of received packets/
packet counts Monitoring period
rate in in
the samplin
receive g
direction periods
.
TUNNEL Indicates Packets Accumul Indicates the number of packets transmitted in the
_SNDPK the ated specified tunnel.
TS number value
of
packets
transmit
ted in
the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes in the packets
_SNDBY the ated transmitted in the specified tunnel.
TES number value
of bytes
transmit
ted in
the
tunnel.
TUNNEL Indicates Bit/s Current Bit rate in the transmit direction of the specified
_TX_BPS the bit value of tunnel = Number of transmitted bytes x 8/Monitoring
rate in counts period
the in
transmit samplin
direction g
of the periods
tunnel.


Name Name ance ance
ance ance Method
Entry Entry
TUNNEL Indicates Packets/ Current Packet rate in the transmit direction of the specified
_TX_PPS the second value of tunnel = Number of transmitted packets/Monitoring
packet counts period
rate in in
the samplin
transmit g
direction periods
of the
tunnel.
Table 12-90 L2VPN PW performance entry list (CSHNU)

Name Name ance ance
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
discarde
d on the
PW.


Name Name ance ance
ance ance Method
Entry Entry
PW_RX_ Indicates Bit/s Current Bit rate in the receive direction of a specified
BPS the bit value of monitored object = Number of received bytes x 8/
rate in counts Monitoring period
the in
receive samplin
direction g
. periods
PW_RX_ Indicates Packets/ Current Packet rate in the receive direction of a specified
PPS the second value of monitored object = Number of received packets/
packet counts Monitoring period
rate in in
the samplin
receive g
direction periods
.
PW_SND Indicates Packets Accumul Indicates the number of packets transmitted on the
PKTS the ated specified PW.
number value
of
packets
transmit
ted on
the PW.
PW_SND Indicates Bytes Accumul Indicates the number of bytes transmitted on the
BYTES the ated specified PW.
number value
of bytes
transmit
ted 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 counts
the in
transmit samplin
direction g
of the periods
PW.


Name Name ance ance
ance ance Method
Entry Entry
PW_TX_ Indicates Packets/ Current Packet rate in the transmit direction of the specified
PPS the second value of PW = Number of transmitted packets/Monitoring
packet counts period
rate in in
the samplin
transmit g
direction periods
of the
PW.
Table 12-91 ETH OAM performance entry list (CSHNU)

Name Name ance ance
ance ance Method
Entry Entry
ETH_CF Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by
M_FLR the value of the source MEP - Number of packets received by the
packet counts sink MEP)/Number of packets transmitted by the
loss rate in source MEP
of the samplin
Ethernet g
service. periods

of lost the performance monitoring mechanism of OAM.)
packets
of the
Ethernet
service.
ETH_CF Indicates μs Current E-Line service delay = Time when the source MEP
M_FD the value of sends a request packet - Time when the source MEP
Ethernet counts receives the response packet
service in
delay. samplin
g
periods


Name Name ance ance
ance ance Method
Entry Entry
ETH_CF Indicates μs Current The frame delay variation is the difference between
M_FDV the value of two frame delay test results.
Ethernet counts
service in
delay samplin
variation g
. periods
ETH_CF Indicates 0.0001 Current Packet loss rate = (Number of packets with priority n
M_FLR_P the value of transmitted by the source MEP - Number of packets
RIn packet counts with priority n received by the sink MEP)/Number of
NOTE loss rate in packets with priority n transmitted by the source
0≤n≤ of the samplin MEP
7 Ethernet g
service periods
with a
priority
of n (0 ≤
n ≤ 7).
ETH_CF Indicates Packets Accumul Number of lost packets = Number of packets with
M_FL_PR the ated priority n transmitted by the source - Number of
In number value packets with priority n received by the sink (Both
NOTE of lost numbers are detected by the performance
0≤n≤ packets monitoring mechanism of OAM.)
7 in the
Ethernet
service
with
priority
n.
ETH_CF Indicates μs Current Bidirectional frame delay = Time when the source
M_FD_P the value of sends a request packet with priority n - Time when
RIn delay of counts the source receives the response packet with priority
NOTE the in n
7 service g
with periods
priority
n.


Name Name ance ance
ance ance Method
Entry Entry
ETH_CF Indicates μs Current The frame delay variation is the difference between
M_FDV_ the value of two frame delay test results.
PRIn delay counts
NOTE variation in
7 Ethernet g
service periods
with
priority
n.
Table 12-92 MPLS-TP OAM performance entry list (CSHNU)

Name Name ance ance
ance ance Method
Entry Entry
MPLS_P Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by
W_FLR the value of the source - Number of packets received by the
packet counts sink)/Number of packets transmitted by the source
loss rate in
of the samplin
PW. g
periods
MPLS_P Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by
W_FLR_ the value of the source - Number of packets received by the
N packet counts sink)/Number of packets transmitted by the source
loss rate in
on the samplin
PW at g
the near periods
end.

packets
in the
PW.


Name Name ance ance
ance ance Method
Entry Entry

packets
on the
PW at
the near
end.
MPLS_P Indicates μs Current Frame delay = Time when the source sends a request
W_FD the value of packet - Time when the source receives the response
frame counts packet
delay on in
the PW. samplin
g
periods
MPLS_P Indicates μs Current The frame delay variation is the difference between
W_FDV the value of two frame delay test results.
frame counts
delay in
variation samplin
on the g
PW. periods
MPLS_T Indicates 0.0001 Current Packet loss rate = (Number of packets transmitted by
UNNEL_ the value of the source - Number of packets received by the
FLR packet counts sink)/Number of packets transmitted by the source
loss rate in
of the samplin
tunnel. g
periods
MPLS_T Indicates 0.01% Current Packet loss rate = (Number of packets transmitted by
UNNEL_ the value of the source - Number of packets received by the
FLR_N packet counts sink)/Number of packets transmitted by the source
loss rate in
in the samplin
tunnel g
at the periods
near
end.


Name Name ance ance
ance ance Method
Entry Entry

FL number value received by the sink (Both numbers are detected by
packets
in the
tunnel.

packets
in the
tunnel
at the
near
end.
MPLS_T Indicates μs Current Frame delay = Time when the source sends a request
UNNEL_ the value of packet - Time when the source receives the response
FD frame counts packet
delay in in
the samplin
tunnel. g
periods
MPLS_T Indicates μs Current The frame delay variation is the difference between
UNNEL_ the value of two frame delay test results.
FDV frame counts
delay in
variation samplin
in the g
tunnel. periods

Table 12-93 1+1/XPIC performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.

TS received.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry
PORT_R Average 0.0001 Average Average bandwidth utilization of the specified receive
X_BW_U bandwid value of port, that is, (number of actually received bytes x 8)/
TILIZATI th counts time unit/configured or actual bandwidth.
ON_AVG utilizatio in all
n of the samplin
receive g
port periods
PORT_R Maximu 0.0001 Maximu Maximum bandwidth utilization of the specified

X_BW_U m m value receive port, that is, (number of actually received
TILIZATI bandwid among bytes x 8/time unit)/configured or actual bandwidth.
ON_MA th counts
X utilizatio in
n of the samplin
receive g
port periods
PORT_R Minimu 0.0001 Minimu Minimum bandwidth utilization of the specified

ON_MIN th counts
utilizatio in
n of the samplin
receive g
port periods

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
PORT_T Average 0.0001 Average Average bandwidth utilization of the specified receive
X_BW_U bandwid value of port, that is, (number of actually received bytes x 8/
TILIZATI th counts time unit)/configured or actual bandwidth.
n of the samplin
receive g
port periods


Name Name ance ance
ance ance Method
Entry Entry
PORT_T Maximu 0.0001 Maximu Maximum bandwidth utilization of the specified

X_BW_U m m value transmit port, that is, (number of actually
TILIZATI bandwid among transmitted bytes x 8/time unit)/configured or actual
ON_MA th counts bandwidth.
X utilizatio in
n of the samplin
transmit g
port periods
PORT_T Minimu 0.0001 Maximu Minimum bandwidth utilization of the specified

ON_MIN th counts bandwidth.
utilizatio in
n of the samplin
transmit g
port periods
bytes in
length)
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
23 bytes bits).
in
length)
518 bits).
bytes in
length)
packets value
transmit
ted.
transmit
ted
frames.
D the ated
bytes in value
received
good
packets.
OD the ated
bytes in value
transmit
ted
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)
bytes to bits).
the MTU
in
length)

Table 12-94 N+1 performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.

TS received.
t
packets
received.
t
packets
received.

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry
X_BW_U bandwid value of port, that is, (number of actually received bytes x 8)/
TILIZATI th counts time unit/configured or actual bandwidth.
n of the samplin
receive g
port periods

ON_MA th counts
X utilizatio in
n of the samplin
receive g
port periods

ON_MIN th counts
utilizatio in
n of the samplin
receive g
port periods

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
n of the samplin
receive g
port periods


Name Name ance ance
ance ance Method
Entry Entry

X utilizatio in
n of the samplin
transmit g
port periods

utilizatio in
n of the samplin
transmit g
port periods
packets value
transmit
ted.
transmit
ted
frames.
D the ated
bytes in value
received
good
packets.


Name Name ance ance
ance ance Method
Entry Entry
OD the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.
broadcas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.

Table 12-95 NMS port performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry

the ated
number value
of
received Corrupted packets, broadcast packets, and multicast
packets. packets are included.
ETHOVE Packets Accumul The total number of received packets (excluding

R Oversize ated framing bits, but including FCS bytes) that are longer
packets value than the value of MTU and that do not have any
received other errors.
ETHUN Undersiz Packets Accumul The total number of received packets (excluding
DER e ated framing bits, but including FCS bytes) that have a
packets value length of smaller than 64 bytes, and that do not
received have any other errors.
Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
the ated
number value
of bytes
in
received
packets
(includin
g
corrupte
RXOCTE d
TS packets).
t
packets
received.
t
packets
received.


Name Name ance ance
ance ance Method
Entry Entry
PORT_R Indicates 0.0001 Average Bandwidth utilization on a port in the receive

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.
n of the samplin
receive g
port periods

ON_MA th counts
X utilizatio in
n of the samplin
receive g
port periods

ON_MIN th counts
utilizatio in
n of the samplin
receive g
port periods


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
n of the samplin
receive g
port periods

X utilizatio in
n of the samplin
transmit g
port periods

utilizatio in
n of the samplin
transmit g
port periods
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length).
518 bits).
bytes in
length).
TXPKTS Indicates Packets Accumul Corrupted packets, broadcast packets, and multicast
number value
of
transmit
ted
packets.


Name Name ance ance
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
transmit
ted
packets
(includin
g
corrupte
d
packets).
D the ated
number value
of bytes
in error-
free
packets
transmit
ted.
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
number value
of
unicast
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
RXUNIC Indicates Packets Accumul Only error-free packets are included.

AST the ated
number value
of error-
free
unicast
packets
received.
TXMULC Indicates Packets Accumul The packets that are dropped and fail to be
number value
of
multicas
t
packets
transmit
ted.
TXBRDC Indicates Packets Accumul The packets that are dropped and fail to be
number value
of
broadcas
t
packets
transmit
ted.
RXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
RAMESP of in the
EED receiving last
error- samplin
free full- g period
frame
bits.
TXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
RAMESP of in the
EED transmit last
ting samplin
error- g period
free full-
frame
bits.


Name Name ance ance
ance ance Method
Entry Entry
RXFULLB Indicates Bytes Accumul FCS bytes and framing bits are included.
GOOD the ated
number value
of error-
free full-
frame
bytes
received.
TXFULLB Indicates Bytes Accumul FCS bytes and framing bits are included.
GOOD the ated
number value
of error-
free full-
frame
bytes
transmit
ted.
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)
bytes to bits).
the MTU
in
length)
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
loss rate in all
in the samplin
receive g
direction periods
.


Name Name ance ance
ance ance Method
Entry Entry
P_RATIO the value of of discarded packets/Total number of transmitted
loss rate in all
in the samplin
transmit g
direction periods
.
Table 12-96 PLA/EPLA performance entry list (CSHNA)

Name Name ance ance
ance ance Method
Entry Entry
ETH_RX_ Indicates kbit/s Maximu

THROU the m value
MAX m among
through all
put on a samplin
port in g
the periods
receive Maximum throughput = Number of received bytes
. Monitoring period
ETH_RX_ Indicates kbit/s Minimu

THROU the m value
MIN m among
through all
put on a samplin
port in g
the periods
receive Minimum throughput = Number of received bytes
. Monitoring period


Name Name ance ance
ance ance Method
Entry Entry
ETH_RX_ Indicates kbit/s Average

THROU the value of
AVG through in all
put on a samplin
port in g
the periods
receive Average throughput = Number of received bytes
. Monitoring period
ETH_TX_ Indicates kbit/s Maximu

THROU the m value
MAX m among
transmit all
ETH_TX_ Indicates kbit/s Minimu

THROU the m value
MIN m among
transmit all
ETH_TX_ Indicates kbit/s Average

THROU the value of
AVG transmit in all

the ated
events.


Name Name ance ance
ance ance Method
Entry Entry

TS received.
t
packets
received.
t
packets
received.

ON th in all NOTE
the
receive
direction
.

ON th in all NOTE
the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .


Name Name ance ance
ance ance Method
Entry Entry

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes in
length)
5 bytes
in
length)
1 bytes
in
length)
23 bytes bits).
in
length)
518 bits).
bytes in
length)
packets value
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
TX_HS_T Ratio of 0.0001 Current Ratio of high-priority service traffic to bandwidth for
RAFF_B traffic to value of high-priority services in the transmit direction =
W_RATI bandwid counts (Number of transmitted bytes x 8/Monitoring
O th for in period)/Bandwidth for high-priority services.
high- samplin
priority g
services periods
in the
transmit
direction
P_RATIO the value of of packets lost in the transmit direction/Total number
packet counts of transmitted packets
loss rate in all
in the samplin
transmit g
direction periods
.
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
TXBPS Indicates Bit/s Value Bit rate in the transmit direction = Number of
rate in in the
the last
transmit samplin
direction g period
.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.
the second obtained transmitted packets/Monitoring period
packet in the
rate in last
the samplin
transmit g period
direction
.
TX_DRO Indicates Packets Accumul -

P_PKTS the ated
number value
of
packets
lost in
the
transmit
direction
.
transmit
ted
frames.


Name Name ance ance
ance ance Method
Entry Entry
D the ated
bytes in value
received
good
packets.
OD the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)
(1519 bits).
bytes to
the MTU
in
length)


Name Name ance ance
ance ance Method
Entry Entry
bytes to bits).
the MTU
in
length)
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods
a:
● VUNI indicates a virtual UNI, corresponding to the UNI-side source or end of a service.
● The E-LAN service of the OptiX RTN 980 does not support RMON performance statistics
based on VUNI and VLAN.
12.1.13 EM6
The RMON performance that the EM6 board supports includes basic performance,
extended performance, port traffic classification performance, port priority
performance, and Port DS domain performance.



count.
performance count.
performance count.

count.
Table 12-98 Basic performance entry list (EM6)

Name Name ance ance
ance ance Method
Entry Entry

the ated
events.
received.


Name Name ance ance
ance ance Method
Entry Entry
t
packets
received.
t
packets
received.
ETHOVE Indicates Packets Accumul Oversized packets are the packets larger than MTU
R the ated (including FCS bytes but not framing bits).
oversize value
d
packets
received.
ETHJAB Indicates Packets Accumul ETHJAB indicates the number of received packets
the ated that are larger than MTU (including FCS bytes but
packets
received.
undersiz value
ed
packets
received.

the ated
collision value
s.


Name Name ance ance
ance ance Method
Entry Entry

ON th in all
utilizatio samplin
n on a g
port in periods
the
receive
direction
.

ON th in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction
.
bytes in
length)
bytes in
length)
5 bytes
in
length)


Name Name ance ance
ance ance Method
Entry Entry
1 bytes
in
length)
23 bytes bits).
in
length)
518 bits).
bytes in
length)
Table 12-99 Extended performance entry list (EM6)

Name Name ance ance
ance ance Method
Entry Entry
packets value
transmit
ted.
transmit
ted


Name Name ance ance
ance ance Method
Entry Entry
frames.
OD the ated
bytes in value
received
good
packets.
D the ated
bytes in value
transmit
ted
good
packets.
the ated
bytes in value
received
bad
packets.
unicast value
packets
transmit
ted.
unicast value
packets
received.
multicas value
t
packets
transmit
ted.


Name Name ance ance
ance ance Method
Entry Entry
broadcas value
t
packets
transmit
ted.
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmit
ted.
GOOD the ated
good value
full-
frame
bytes
received.
GOOD the ated
good value
full-
frame
bytes
transmit
ted.
pause value
frames
received.


Name Name ance ance
ance ance Method
Entry Entry
pause value
frames
transmit
ted.
s.

COL the ated
frames value
unsucces
sfully
transmit
ted after
consecut
ive
collision
s.
deferred
in
transmis
sion.
ingress in all
direction samplin
g
periods


Name Name ance ance
ance ance Method
Entry Entry
egress in all
direction samplin
g
periods

MAX m among
through all
put on a samplin
port in g
the periods
receive
direction
.

MIN m among
through all
put on a samplin
port in g
the periods
receive
direction
.

AVG through in all
put on a samplin
port in g
the periods
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

the m value
maximu obtained
m among

the m value
minimu obtained
m among

the value of
average counts

the ated
packet value
loss
count in
the
transmit
TX_DRO direction
P_PKTS . -

the ated
packet value
loss
count in
the
receive
RX_DRO direction
P_PKTS . -


Name Name ance ance
ance ance Method
Entry Entry
bytes in
length)
(65-127
bytes in
length)
(128-25
5 bytes
in
length)
(256-51
1 bytes
in
length)
(512-10 bits).
23 bytes
in
length)
(1024-1 bits).
518
bytes in
length)


Name Name ance ance
ance ance Method
Entry Entry
(1519 bits).
bytes to
the MTU
in
length)
bytes to bits).
the MTU
in
length)
rate in in the
the last
receive samplin
direction g period
of an
Ethernet
port.
rate in in the
the last
transmit samplin
direction g period
of an
Ethernet
port.
packet in the
rate in last
the samplin
receive g period
direction
of an
Ethernet
port.


Name Name ance ance
ance ance Method
Entry Entry
packet in the
rate in last
the samplin
transmit g period
direction
of an
Ethernet
port.
IO ratio in counts
the in all
receive samplin
direction g
periods
IO ratio in counts
the in all
transmit samplin
direction g
periods

th samplin
utilizatio g
n on a periods
port in
the
receive
direction
.


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_R port in
X_BW_U the
TILIZATI receive
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_R the
X_BW_U receive
TILIZATI direction
ON_MIN .

th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_AVG .


Name Name ance ance
ance ance Method
Entry Entry

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
PORT_T port in
X_BW_U the
TILIZATI transmit
ON_MA direction
X .

m counts bandwidth
bandwid in
th samplin
utilizatio g
n on a periods
port in
PORT_T the
X_BW_U transmit
TILIZATI direction
ON_MIN .

Table 12-100 Port traffic classification performance entry list (EM6)

Name Name ance ance
ance ance Method
Entry Entry

RTCAR_ the ated
Marked number value
RedPKTS of red
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
ellowPK of
TS yellow
packets
after
traffic
monitori
ng is
enabled.

RTCAR_ the ated
Marked number value
GreenPK of green
TS packets
after
traffic
monitori
ng is
enabled.

RTSTRM the ated
_RCVMA number value
TCHPKT of
S packets
received
in the
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHPKT of
S packets
transmit
ted in
the
matched
flow.

RM_SHA the ated
PING_D number value
ROPPKT of
S packets
discarde
d due to
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.


Name Name ance ance
ance ance Method
Entry Entry
IO loss due samplin
to g period
network
congesti
on when
the
traffic
shaping
function
is
enabled
in the
egress
direction
.
O packets samplin
marked g period
in red
when
the
traffic
policing
function
is
enabled.
rate in last
the samplin
receive g period
direction
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry
rate in last
the samplin
transmit g period
direction
of a
matched
flow.

RTSTRM the ated
_RCVMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
received
packets
of a
matched
flow.


Name Name ance ance
ance ance Method
Entry Entry

RTSTRM the ated
_SNDMA number value
TCHBYT of bytes
ES (excludi
ng inter-
frame
gaps
and
preambl
es) in
the
transmit
ted
packets
of a
matched
flow.
the last
receive samplin
direction g period
of a
matched
flow.
the last
transmit samplin
direction g period
of a
matched
flow.

Table 12-101 Port priority performance entry list (EM6)

Name Name ance ance
ance ance Method
Entry Entry
loss due samplin
to g
congesti periods
on in
egress
queues
with
different
priorities
.

_DROPP the ated
KTS number value
of
packets
discarde
d in the
services
with
different
priorities
.

_DROPB the ated
YTES number value
of bytes
discarde
d in the
services
with
different
priorities
.


Name Name ance ance
ance ance Method
Entry Entry

RI_SNDP the ated
KTS number value
of
packets
transmit
ted in
egress
queues
with
different
priorities
.

RI_SNDB the ated
YTES number value
of bytes
in the
packets
transmit
ted in
egress
queues
with
different
priorities
.

PS rates of in the
egress last
queues samplin
with g period
different
priorities
in the
transmit
direction
.


Name Name ance ance
ance ance Method
Entry Entry

PS packet in the
rate of last
egress samplin
queues g period
with
different
priorities
in the
transmit
direction
.
Table 12-102 Port DS domain performance entry list (EM6)

Name Name ance ance
ance ance Method
Entry Entry

ANPRI_P the ated
KTS number value
of
packets
with
matched
C-VLAN
priorities
in the
DS
domain


Name Name ance ance
ance ance Method
Entry Entry

ANPRI_B the ated
YTES number value
of bytes
in the
packets
with
matched
C-VLAN
priorities
in the
DS
domain.

NPRI_PK the ated
TS number value
of
packets
with
matched
S-VLAN
priorities
in the
DS
domain.

NPRI_BY the ated
TES number value
of bytes
in the
packets
with
matched
S-VLAN
priorities
in the
DS
domain.


Name Name ance ance
ance ance Method
Entry Entry

P_PKTS the ated
number value
of
packets
with
matched
IP DSCP
priorities
in the
DS
domain.

P_BYTES the ated
number value
of bytes
in the
packets
with
matched
IP DSCP
priorities
in the
DS
domain.
Table 12-103 LAG performance entry list (EM6)

Name Name of ance ance
of a a Count Countin
ance ance Method
Entry Entry

the ated


ance ance Method
Entry Entry
ETHDRO Indicates Times Accumul ETHDROP indicates the number of packet loss
P the ated events caused by insufficient Ethernet chip resources.
packet value The count is not the number of discarded packets
loss but the number of times packet loss is detected.
events.
TS the bytes ated received packets (including bad packets), including
received. value framing bits but not FCS bytes.
multicast value excluding broadcast packets.
packets
received.
t packets
received.
oversized value framing bits) and do not contain any other errors.
packets
received.
oversized value not framing bits) and contain FCS errors or
error alignment errors.
packets
received.
undersize value
d packets
received.
fragment value but not framing bits) and contain FCS errors or
s alignment errors. Increase of the count is normal


ance ance Method
Entry Entry

TILIZATI bandwidt counts bandwidth
ON h in all
utilizatio samplin
n on a g
port in periods
the
receive
direction.

TILIZATI bandwidt counts bandwidth
ON h in all
utilizatio samplin
n on a g
port in periods
the
transmit
direction.
packets value
transmitt
ed.
TS the bytes ated packets (including bad packets), including framing
transmitt value bits but not FCS bytes.
ed
frames. NOTE
oversized frames.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are
OD the bytes ated excluded.
in value
received
good
packets.


ance ance Method
Entry Entry
TXBGOO Indicates Bytes Accumul FCS bytes are included, but framing bits are
D the bytes ated excluded.
in value
transmitt
ed good
packets.
RXBBAD Indicates Bytes Accumul FCS bytes are included, but framing bits are
the bytes ated excluded.
in value
received
bad
packets.
unicast value
packets
transmitt
ed.
unicast value
packets
received.
multicast value
packets
transmitt
ed.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to
AST the ated be transmitted are included.
broadcas value
t packets
transmitt
ed.


ance ance Method
Entry Entry
EED full- last
frame samplin
bytes g period
received.
EED full- last
frame samplin
bytes g period
transmitt
ed.
GOOD the good ated
full- value
frame
bytes
received.
GOOD the good ated
full- value
frame
bytes
transmitt
ed.
pause value
frames
received.
pause value
frames
transmitt
ed.


ance ance Method
Entry Entry
(64 bytes value bytes (including FCS bytes but not framing bits).
in
length)
bytes in
length)
bytes in bits).
length)
bytes in bits).
length)
3 bytes bits).
in
length)
18 bytes bits).
in
length)
bytes to bits).
the MTU
in
length)


ance ance Method
Entry Entry
transmitt ated (including corrupted packets) with a length of 64
ed (64 value bytes (including FCS bytes but not framing bits).
bytes in
length)
transmitt ated (including corrupted packets) with a length of 65 to
ed value 127 bytes (including FCS bytes but not framing bits).
(65-127
bytes in
length)
8 transmitt ated (including corrupted packets) with a length of 128
ed value to 255 bytes (including FCS bytes but not framing
(128-255 bits).
bytes in
length)
(256-511 bits).
bytes in
length)
(512-102 bits).
3 bytes
in
length)
(1024-15 bits).
18 bytes
in
length)


ance ance Method
Entry Entry
ed (1519 value to MTU bytes (including FCS bytes but not framing
bytes to bits).
the MTU
in
length)

ON_AVG bandwidt in bandwidth
h samplin
utilizatio g
n on a periods
port in
the
receive
direction.

X_BW_U the m value in the receive direction = (Number of received bytes
TILIZATI maximu of x 8/Monitoring period)/Configured or actual
X bandwidt in
h samplin
utilizatio g
n on a periods
port in
the
receive
direction.
PORT_R Indicates 0.0001 Minimu Minimum bandwidth utilization on a specified port

X_BW_U the m value in the receive direction = (Number of received bytes
TILIZATI minimu of x 8/Monitoring period)/Configured or actual
bandwidt in
h samplin
utilizatio g
n on a periods
port in
the
receive
direction.


ance ance Method
Entry Entry

ON_AVG bandwidt in bandwidth
h samplin
utilizatio g
n on a periods
port in
the
transmit
direction.

X bandwidt in
h samplin
utilizatio g
n on a periods
port in
the
transmit
direction.
PORT_T Indicates 0.0001 Minimu Minimum bandwidth utilization on a specified port

bandwidt in
h samplin
utilizatio g
n on a periods
port in
the
transmit
direction.

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


count.
performance count.
performance count.

count.

Table 12-105 Basic performance entry list (EFP8/EMS6)

Name Name ance ance
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
TXBGOO transmit
D ted FCS bytes are included but framing bits are excluded.
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
RXPKTS received value packets are included.
Broadca Packets Accumul

st ated RXBRDCAST indicates the total number of received
RXBRDC packets value good packets with broadcast destination addresses,
AST received excluding multicast packets.
Multicas Packets Accumul

t ated RXMULCAST indicates the total number of received
RXMULC packets value good packets with multicast destination addresses,
AST received excluding broadcast packets.
Table 12-106 Extended performance entry list (EFP8/EMS6)

Name Name ance ance
ance ance Method
Entry Entry
RXGOO Bit rate kbit/s Value FCS bytes and framing bits (20 bits) are included.
DFULLF of good obtained
RAMESP frames in the
EED received last
samplin
g period


Name Name ance ance
ance ance Method
Entry Entry
TXGOO Bit rate kbit/s Value FCS bytes and framing bits (20 bits) are included.
DFULLF of good obtained
RAMESP frames in the
EED transmit last
ted samplin
g period
RXFULLB Number Bytes Accumul FCS bytes and framing bits (20 bits) are included.
GOOD of bytes ated
in good value
frames
received
TXFULLB umber Bytes Accumul FCS bytes and framing bits (20 bits) are included.
GOOD of bytes ated
in good value
frames
transmit
ted
TXMULC Multicas Packets Accumul The packets that are dropped and fail to be
AST t ated transmitted are included.
packets value
transmit
ted
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
AST packets ated transmitted are included.
transmit value
ted
TXBRDC Broadca Packets Accumul The packets that are dropped and fail to be
AST st ated transmitted are included.
packets value
transmit
ted
RXPAUS Pause Frames Accumul RXPAUSE indicates the number of received MAC flow
E frames ated control frames whose operation code is PAUSE.
received value


Name Name ance ance
ance ance Method
Entry Entry
TXPAUS Pause Frames Accumul TXPAUSE indicates the number of transmitted MAC
E frames ated flow control frames whose operation code is PAUSE.
transmit value
ted
ETHDRO Packet Times Accumul ETHDROP indicates the number of events in which
P loss ated packet loss occurs due to resource deficiency.
event value
ETHOVE Oversize Packets Accumul Indicates the number of received packets that are
R d ated longer than MTU bytes (including FCS bytes but not
packets value framing bits) and do not contain any other errors.
received
ETHJAB Oversize Packets Accumul Indicates the total number of received packets that
d error ated are longer than MTU bytes (including FCS bytes but
packets value not framing bits) and contain FCS errors or
received alignment errors.
ETHFCS Frames Frames Accumul Frames that contain an integer number of bytes and
with FCS ated FCS errors. Ultra-long or ultra-short frames are
errors value excluded.
(MAC_F
CS)
RXBBAD Number Bytes Accumul FCS bytes are included but framing bits are excluded.
of bytes ated
in the value
corrupt
packets
received
ETH_RX_ Maximu kbit/s Maximu ETH_RX_THROUGHPUT_MAX indicates the maximum

THROU m m value throughput at the receive direction of an interface
GHPUT_ receive obtained and equals to total number of received bytes
MAX through among (including the preamble and frame gap) divided by
put of all the measurement period.
an samplin
interface g
periods


Name Name ance ance
ance ance Method
Entry Entry
ETH_RX_ Minimu kbit/s Minimu ETH_RX_THROUGHPUT_MIN indicates the minimum

THROU m m value throughput at the receive direction of an interface
GHPUT_ receive obtained and equals to total number of received bytes
MIN through among (including the preamble and frame gap) divided by
put of all the measurement period.
an samplin
interface g
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
GHPUT_ through counts and equals to total number of received bytes
AVG put of in all (including the preamble and frame gap) divided by
an samplin the measurement period.
interface g
periods
12.2 RMON Performance Entries List on the EoS/

EoPDH-Plane
This section lists RMON performance entries on the EoS/EoPDH plane by board
type.
12.2.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.

Table 12-107 Basic performance entry list (EFP8)

Brief Name Full Perfor Perform RemarksSource Port Source Port
of a Name of mance ance
Performan a Count Countin
ce Entry Perform Unit g
ance Method
Entry
RXOCTETS Bytes Bytes Accumul RXOCTETS indicates the total PORT1 to

received ated number of bytes in received PORT9
value packets (including bad packets),
including framing bits but not
FCS bytes.
RXPKTS Packets Packet Accumul Bad packets, broadcast packets,

received s ated and multicast packets are
value included.
RXBRDCAST Broadcas Packet Accumul RXBRDCAST indicates the total

t packets s ated number of received good packets
received value with broadcast destination
addresses, excluding multicast
packets.
RXMULCAS Broadcas Packet Accumul RXMULCAST indicates the total

T t packets s ated number of received good packets
received value with multicast destination
addresses, excluding broadcast
packets.
RXPKT64 Packets Packet Accumul Indicates the total number of

received s ated received packets (including
(64 bytes value corrupted packets) with a length
in of 64 bytes (including FCS bytes
length) but not framing bits).

(65-127 value corrupted packets) with a length
bytes in of 65 to 127 bytes (including FCS
length) bytes but not framing bits).

bytes in of 128 to 255 bytes (including
length) FCS bytes but not framing bits).


Brief Name Full Perfor Perform RemarksSource Port Source Port

ance Method
Entry

3 bytes of 512 to 1023 bytes (including
in FCS bytes but not framing bits).
length)

length)
ETHOVER Indicates Packet Accumul Indicates the number of received

the s ated packets that are longer than
oversized value MTU bytes (including FCS bytes
packets but not framing bits) and do not
received. contain any other errors.
ETHJAB Indicates Packet Accumul Indicates the total number of

the s ated received packets that are longer
oversized value than MTU bytes (including FCS
error bytes but not framing bits) and
packets contain FCS errors or alignment
received. errors.
ETHUNDER Undersiz Packet Accumul Indicates the number of received PORT1 to

ed s ated packets that are shorter than 64 PORT8
packets value bytes (including FCS bytes but
received not framing bits) and do not
contain any other errors except
for FCS errors.
ETHFRG Fragmen Packet Accumul Indicates the total number of

ts s ated received packets that have FCS or
received value alignment errors (FCS bytes are
included but framing bits are
excluded). The count increases
because of noise collisions.

Table 12-108 Extended performance entry list (EFP8)

Brief Name Full Perfor Perform Remarks Source Port
ance Method
Entry
RXGOODFU Indicates kbit/s Value Framing bits (20 bytes) and FCS PORT1 to
LLFRAMESP the rate obtained bytes are included. PORT9
EED of good in the
full- last
frame sampling
bits period
received.
TXGOODFU Indicates kbit/s Value Framing bits (20 bytes) and FCS
LLFRAMESP the rate obtained bytes are included.
EED of good in the
full- last
frame sampling
bits period
transmitt
ed.
RXFULLBG Indicates Bytes Accumul Framing bits (20 bytes) and FCS
OOD the good ated bytes are included.
full- value
frame
bytes
received.
TXFULLBG Indicates Bytes Accumul Framing bits (20 bytes) and FCS
full- value
frame
bytes
transmitt
ed.
TXMULCAS Indicates Packet Accumul The multicast packets that are

T the s ated discarded or fail to be
multicast value transmitted are included.
packets
transmitt
ed.
RXCTLPKTS Control Frame Accumul -

frames s ated
received value


ance Method
Entry
TXOCTETS Bytes Bytes Accumul Indicates the total number of

transmitt ated bytes (including those in bad
ed value packets) transmitted (including
FCS bytes but not framing bits).
TXPKTS Packets Packet Accumul Bad packets, broadcast packets,

transmitt s ated and multicast packets are
ed value included.
TXCTLPKTS Control Frame Accumul -

frames s ated
transmitt value
ed
TXPKT64 Packets Packet Accumul Indicates the total number of

transmitt s ated transmitted packets (including
ed (64 value corrupted packets) with a length
bytes in of 64 bytes (including FCS bytes

ed value corrupted packets) with a length
(65-127 of 65 to 127 bytes (including FCS
bytes in bytes but not framing bits).
length)

(128-255 of 128 to 255 bytes (including
bytes in FCS bytes but not framing bits).
length)

length)

3 bytes FCS bytes but not framing bits).
in
length)


ance Method
Entry

in
length)
RXUNICAST Unicast Packet Accumul RXUNICAST indicates the number

packets s ated of good unicast packets.
received value
TXUNICAST Unicast Packet Accumul The unicast packets that are

packets s ated discarded or fail to be
transmitt value transmitted are included.
ed
TXBRDCAST Broadcas Packet Accumul The broadcast packets that are

t packets s ated discarded or fail to be
transmitt value transmitted are included.
ed
RXPAUSE Pause Frame Accumul RXPAUSE indicates the number

frames s ated of MAC flow control frames with
received. value the PAUSE opcode.
TXPAUSE Pause Frame Accumul TXPAUSE indicates the number of

frames s ated MAC flow control frames with
transmitt value the PAUSE opcode.
ed
PKT64 Packets Packet Accumul Indicates the total number of

received s ated received and transmitted packets
and value (including corrupted packets)
transmitt with a length is of 64 bytes
ed (64 (including FCS bytes but not
bytes in framing bits).
length)

transmitt with a length is of 65 to 127
ed bytes (including FCS bytes but
(65-127 not framing bits).
bytes in
length)


ance Method
Entry

bytes in
length)

bytes in
length)

3 bytes
in
length)

18 bytes
in
length)
ETHFCS Frames Frame Accumul Frames that contain an integer

with FCS s ated number of bytes and FCS errors.
errors value Ultra-long or ultra-short frames
(MAC_FC are excluded.
S)


ance Method
Entry
ETHALI Alignme Frame Accumul An alignment error frame

nt error s ated contains a fractional number of
frames value bytes and fails to pass the FCS
check.
ETH_RX_TH Maximu kbit/s Maximu ETH_RX_THROUGHPUT_MAX

ROUGHPUT m m value indicates the maximum
_MAX receive obtained throughput at the receive
throughp among direction of an interface and
ut of an all equals to total number of
interface sampling received bytes (including the
periods preamble and frame gap) divided
by the measurement period.
ETH_RX_TH Minimu kbit/s Minimu ETH_RX_THROUGHPUT_MIN

ROUGHPUT m m value indicates the minimum
_MIN receive obtained throughput at the receive
throughp among direction of an interface and
ut of an all equals to total number of
interface sampling received bytes (including the
periods preamble and frame gap) divided
by the measurement period.
ETH_RX_TH Average kbit/s Average ETH_RX_THROUGHPUT_AVG

ROUGHPUT receive value of indicates the average throughput
_AVG throughp counts in at the receive direction of an
ut of an all interface and equals to total
interface sampling number of received bytes
periods (including the preamble and
frame gap) divided by the
measurement period.
Table 12-109 VCGperformance entry list (EFP8)

ance Method
Entry
VCG_TXGO Good Packet Accumul - VCTRUNK1 to

ODPACKET packets s ated VCTRUNK16
S transmitt value
ed


ance Method
Entry
VCG_TXPAC Packets Packet Accumul Bad packets, broadcast packets,

KETS transmitt s ated and multicast packets are
ed value included.
VCG_TXOCT Bytes Bytes Accumul Bad packets are included (FCS

ETS transmitt ated bytes are included but framing
ed value bits are excluded).
VCG_RXGO Good Packet Accumul -

ODPACKET packets s ated
S received value
VCG_RXPAC Packets Packet Accumul Bad packets, broadcast packets,

KETS received s ated and multicast packets are
value included.
VCG_RXOC Bytes Bytes Accumul Bad packets are included (FCS

TETS received ated bytes are included but framing
value bits are excluded).
VCG_TXSPE Speed of kbit/s Value Bad packets are included (FCS

ED bytes obtained bytes are included but framing
transmitt in the bits are excluded).
ed last
sampling
period
VCG_RXSPE Speed of kbit/s Value Bad packets are included (FCS

received in the bits are excluded).
last
sampling
period
12.2.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.

Table 12-110 Basic performance entry list (EMS6)

ance Method
Entry
RXOCTETS Indicates Bytes Accumul RXOCTETS indicates the total PORT1 to

the bytes ated number of bytes in received PORT7
received. value packets (including bad packets),
including framing bits but not
FCS bytes.
RXBRDCAST Indicates Packet Accumul RXBRDCAST indicates the total

the s ated number of received good packets
broadcas value with broadcast destination
t packets addresses, excluding multicast
received. packets.
RXMULCAS Indicates Packet Accumul RXMULCAST indicates the total

T the s ated number of received good packets
broadcas value with multicast destination
t packets addresses, excluding broadcast
received. packets.
ETHOVER Indicates Packet Accumul Indicates the number of received

the s ated packets that are longer than
oversized value MTU bytes (including FCS bytes
packets but not framing bits) and do not
received. contain any other errors.
RXPKTS Indicates Packet Accumul Bad packets, broadcast packets,

the s ated and multicast packets are
packets value included.
received.
ETHJAB Indicates Packet Accumul Indicates the total number of

the s ated received packets that are longer
oversized value than MTU bytes (including FCS
error bytes but not framing bits) and
packets contain FCS errors or alignment
received. errors.


ance Method
Entry
ETHFCS The Frame Accumul -

number s ated
of value
frames
that
have FCS
check
errors-
ETHUNDER Undersiz Packet Accumul Indicates the number of received

ed s ated packets that are shorter than 64
packets value bytes (including FCS bytes but
received not framing bits) and do not
contain any other errors except
for FCS errors.
ETHFRG Fragmen Packet Accumul Indicates the total number of

ts s ated received packets that have FCS or
received value alignment errors (FCS bytes are
included but framing bits are
excluded). The count increases
because of noise collisions.

(64 bytes value corrupted packets) with a length
in of 64 bytes (including FCS bytes

bytes in of 65 to 127 bytes (including FCS
length) bytes but not framing bits).




ance Method
Entry

length)

length)
ETHALI The Frame Accumul An alignment error frame PORT3 to

number s ated contains a fractional number of PORT6
of value bytes and fails to pass the FCS
alignmen check.
t error
frames
Table 12-111 Extended performance entry list (EMS6)

ance Method
Entry
RXCTLPKTS Control Frame Accumul - PORT1 to

frames s ated PORT7
received value
TXOCTETS Bytes Bytes Accumul Indicates the total number of

transmitt ated bytes (including those in bad
ed value packets) transmitted (including
FCS bytes but not framing bits).
TXPKTS Packets Packet Accumul Bad packets, broadcast packets,

transmitt s ated and multicast packets are
ed value included.


ance Method
Entry
TXCTLPKTS Control Frame Accumul -

frames s ated
transmitt value
ed

ed (64 value corrupted packets) with a length
bytes in of 64 bytes (including FCS bytes

(65-127 of 65 to 127 bytes (including FCS
bytes in bytes but not framing bits).
length)

length)

length)

in
length)

in
length)


ance Method
Entry

transmitt with a length is of 64 bytes
ed (64 (including FCS bytes but not
bytes in framing bits).
length)

bytes in
length)

bytes in
length)

bytes in
length)

3 bytes
in
length)


ance Method
Entry

18 bytes
in
length)
RXGOODFU Indicates kbit/s Value Framing bits (20 bytes) and FCS
EED of good in the
full- last
frame sampling
bits period
received.
TXGOODFU Indicates kbit/s Value Framing bits (20 bytes) and FCS
EED of good in the
full- last
frame sampling
bits period
transmitt
ed.
RXFULLBG Indicates Bytes Accumul Framing bits (20 bytes) and FCS
full- value
frame
bytes
received.
TXFULLBG Indicates Bytes Accumul Framing bits (20 bytes) and FCS
full- value
frame
bytes
transmitt
ed.


ance Method
Entry
TXMULCAS Indicates Packet Accumul The multicast packets that are

T the s ated discarded or fail to be
multicast value transmitted are included.
packets
transmitt
ed.
RXUNICAST Indicates Packet Accumul RXUNICAST indicates the number

the s ated of good unicast packets.
unicast value
packets
received.
TXUNICAST Indicates Packet Accumul The unicast packets that are

the s ated discarded or fail to be
unicast value transmitted are included.
packets
transmitt
ed.
TXBRDCAST Indicates Packet Accumul The broadcast packets that are

the s ated discarded or fail to be
broadcas value transmitted are included.
t packets
transmitt
ed.
RXPAUSE Indicates Frame Accumul RXPAUSE indicates the number

the s ated of MAC flow control frames with
pause value the PAUSE opcode.
frames
received.
TXPAUSE Indicates Frame Accumul TXPAUSE indicates the number of

the s ated MAC flow control frames with
pause value the PAUSE opcode.
frames
transmitt
ed.

Table 12-112 VCGperformance entry list (EMS6)

ance Method
Entry
VCG_TXGO Good Packet Accumul - VCTRUNK1 to

ODPACKET packets s ated VCTRUNK8
S transmitt value
ed
VCG_TXPAC Packets Packet Accumul Bad packets, broadcast packets,

KETS transmitt s ated and multicast packets are
ed value included.
VCG_TXOCT Bytes Bytes Accumul Bad packets are included (FCS

ETS transmitt ated bytes are included but framing
ed value bits are excluded).
VCG_RXGO Good Packet Accumul -

ODPACKET packets s ated
S received value
VCG_RXPAC Packets Packet Accumul Bad packets, broadcast packets,

KETS received s ated and multicast packets are
value included.
VCG_RXOC Bytes Bytes Accumul Bad packets are included (FCS

TETS received ated bytes are included but framing
value bits are excluded).
VCG_TXSPE Speed of kbit/s Value Bad packets are included (FCS

transmitt in the bits are excluded).
ed last
sampling
period
VCG_RXSPE Speed of kbit/s Value Bad packets are included (FCS

received in the bits are excluded).
last
sampling
period
12.3 RMON Events and Handling Procedures

This chapter describes the RMON events that indicate Ethernet service
abnormalities and how to handle these events.

12.3.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.
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.
● The lower threshold is not set to a non-zero value.

● 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 Change the lower threshold to 0.
lower threshold
The number is higher than the Manually decrease the traffic transmitted
upper threshold from the opposite end. If the problem
persists, go to the next step.
Step 2 Replace the involved part.
----End
Reference
None

12.3.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 Change the lower threshold to 0.
threshold
The number is higher than the upper Go to the next step.
threshold
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 Set the working modes of the ports
ends work in inconsistent modes, or any on the equipment at both ends to
port works in half-duplex mode full-duplex or auto-negotiation, so
that these ports work in consistent
modes.
The ports on the equipment at both Go to the next step.
ends work in consistent modes and no
ports work in half-duplex mode
----End
Reference
None

12.3.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...
threshold
threshold
ends.
If... Then...
modes.
Step 3 Check whether the network diameter of the LAN is very large according to the
networking planning information.
If... Then...
The network diameter Divide the network and deploy equipment to different
is very large buses or 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.

If... Then...
The network diameter Go to the next step.
is appropriate
----End
Reference
None
12.3.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...
threshold
threshold
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
12.3.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...
threshold
threshold
ends.
If... Then...
modes.
----End

Reference
None
12.3.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 Rectify the fault on the
that is shorter than 64 bytes opposite equipment.
The opposite end does not transmit the Go to the next step.
packet that is shorter than 64 bytes
----End
Reference
None
12.3.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 Notify the opposite
that is longer than the maximum frame length equipment that the length of
set for the local equipment transmitted frames should be
changed.
The opposite equipment does not transmit the Go to the next step.
packet that is longer than the maximum frame
length set for the local equipment
----End
Reference
None
12.3.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
● The working modes of the ports on the equipment at both ends are not
consistent.

● 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 Change the working mode of the local port so
not consistent that the ports on the equipment at both ends
work in consistent modes.
set to the half-duplex mode.
If... Then...
The working modes are not set to Go to the next step.
the half-duplex mode
The working modes are set to the Change the working modes of the ports on
half-duplex mode the equipment at both ends to the full-
duplex mode or adaptive mode.
----End
12.3.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
● The working modes of the ports on the equipment at both ends are not
consistent.
Procedure
consistent.

If... Then...
The working modes are Go to the next step.
consistent
The working modes are Change the working mode of the local port so
not consistent that the ports on the equipment at both ends
work in consistent modes.
----End
12.3.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
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...
threshold
threshold
ends.
If... Then...
modes.

If... Then...
----End
Reference
None
12.3.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
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...
threshold
threshold
ends.

If... Then...
The ports on the equipment at both Change the working modes of the ports
ends work in inconsistent modes on the equipment at both ends so that
they can work in consistent modes
ends work in consistent modes
----End
Reference
None
12.3.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 6.3 Troubleshooting the Radio
Link.
Step 2 Remove the interference source near the equipment and then check whether the
performance event is cleared.
ends.
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
12.3.13 ATMPW_MISORDERPKTS
Description
The ATMPW_MISORDERPKTS is a performance event indicating the number of
disordered ATM PW packets.

None
Possible Causes
Procedure
Link.
ends.
cleared.
equipment.
----End
Related Information
None
12.3.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
Link.
ends.
cleared.
equipment.
----End
Related Information
None
12.3.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
ends.
cleared.
equipment.
----End
Related Information
None
12.3.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 6.3 Troubleshooting the Radio Link and handle the fault on the radio
link.
cleared.
equipment.
----End

Related Information
None
12.3.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 6.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
12.3.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
12.3.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

12.3.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 6.3 Troubleshooting the Radio Link.
Step 2 Synchronize the PSN network clock by setting clock synchronization, reducing
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
12.3.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.
Link.
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
12.3.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
Link.
----End
Related Information
None

Maintenance Guide 13 Alarm Management
13 Alarm Management
The alarm management on the OptiX RTN 980 is classified into the NE alarm
management and board alarm management.
13.1 NE Alarm Management

The NE alarm management function set by user is applicable to all the boards on
the NE.
13.2 Board Alarm Management
The board alarm management function is only applicable to the board on which
users have configured this function.
13.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:
● Settings of the alarm storage mode
● Setting of the alarm delay
● Setting of the alarm reversion mode
For details about these functions, see the manuals or online Help of the NMS.
13.2 Board Alarm Management

The board alarm management function is only applicable to the board on which
users have configured this function.
13.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.

● 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.
● 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.
● 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.
● 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.
13.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.
13.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.
13.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.
● Non-revertive (Disable)
In this mode, the alarms are monitored by default and alarm reversion cannot
be enabled for a port.
● 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.
● 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:
● For OptiX RTN 980, only R_LOS, T_ALOS, MW_LOF, ETH_LOS, and LAN_LOC
alarms support alarm reversion.
● Alarm reversion is set based on ports. Configurations are required at both the
NE level and the port level.
● Alarm reversion does not change the actual status of alarms on the board, as
well as the indication status of the alarm indicators.
● 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.
13.2.5 Setting Alarm Thresholds

This section lists the alarms whose thresholds can be configured and hyperlinks to
the detailed configuration operations.
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 13-1 Bit error alarm thresholds

Alarm Descriptio Performan Threshold Default Reference
Name n ce Item Range Threshold
HP_CROSS Performanc HPBBE 0-65535 1500 (15 Setting

TR e (15 minutes) Performan
threshold- minutes) 15000 (24 ce
crossing of 0-1048575 hours) Thresholds
the higher (24 hours)
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 1500 (15

(15 minutes)
minutes) 15000 (24
0-1048575 hours)
(24 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 Performanc TUPJCHIG 0-1677721 1500 (15

SSTR e H 5L (15 minutes)
threshold- minutes) 30000 (24
crossing of 0-6710886 hours)
higher 3L (24
order path hours)
adaptation
TUPJCLOW 0-1677721 1500 (15
5L (15 minutes)
minutes) 30000 (24
0-6710886 hours)
3L (24
hours)


TUPJCNEW 0-1677721 1500 (15

5L (15 minutes)
minutes) 30000 (24
0-6710886 hours)
3L (24
hours)
LP_CROSST Performanc LPBBE 0-65535 1500 (15

R e (15 minutes)
the lower (24 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 1500 (15

(15 minutes)
minutes) 15000 (24
0-1048575 hours)
(24 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 Performanc AUPJCHIG 0-65535 1500 (15

OSSTR e H (15 minutes)
multiplex (24 hours)
section
adaptation AUPJCLOW 0-65535 1500 (15
(15 minutes)
minutes) 30000 (24
0-1048575 hours)
(24 hours)
AUPJCNEW 0-65535 1500 (15

(15 minutes)
minutes) 30000 (24
0-1048575 hours)
(24 hours)
MW_BER_E Excessive - 10-8-10-3 10-3 Setting Bit

XC bit errors Error
on Thresholds
microwave for Service
links Ports
MW_BER_S Signal - 10-9-10-4 10-6

D degrade
(SD) due
to
excessive
bit errors
on
microwave
links
B1_SD Regenerato - 10-9-10-4 10-6

r section
(B1) SD
B1_EXC Excessive - 10-8-10-3 10-3

bit errors
in the
regenerato
r 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 - 10-9-10-4 10-6

order path
(B3) SD
B3_EXC Excessive - 10-8-10-3 10-3

bit errors
in the
higher
order path
(B3)
B3_EXC_VC Excessive - 10-8-10-3 10-3

3 bit errors
in VC-3
paths (B3)
B3_SD_VC3 VC-3 path - 10-9-10-4 10-6

(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 13-2 Physical condition alarm thresholds

Alarm Description Threshold Default Reference
Name Range Threshold
ODC_TEMP Outdoor Upper Upper Setting the

_ABN cabinet threshold threshold: Temperature
temperature range: 20-80 65°C and Humidity
(°C) Lower Alarm
Lower threshold: Thresholds for
threshold -20°C the PMU
range: -40-10
(°C)

Alarm Description Threshold Default Reference

Name Range Threshold
RADIO_FAD Insufficient 100 dB-350 dB 140 dB Setting the

ING_MARGI microwave Alarm
N_INSUFF fade margin Threshold for
Insufficient
Fade Margin
TEMP_OVE Board - - In the NE

R operating Explorer, select
temperature the desired
board and
choose
Configuration
>
Environment
Monitor
Configuration
>
Environment
Monitor
Interface
from the
Function Tree.
Then specify
the upper and
lower
thresholds.
TEMP_ALAR Board - - In the NE

M operating Explorer, select
temperature 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 13-3 RMON alarm thresholds

MAC_FCS_ Bit errors ETHFCS 10GE: Upper Configurin

EXC detected at 0-65535 threshold: g Ethernet
the MAC (frames) 90 Performan
layer Lower ce
exceed the threshold: Threshold-
upper 0 Crossing
threshold. Parameter
GE: Upper s
0-15000 threshold:
(frames) 9
Lower
threshold:
0
100M: Upper
0-65535 threshold:
(frames) 1
Lower
threshold:
0
10M: Upper
0-20480 threshold:
(frames) 1
Lower
threshold:
0
MAC_FCS_ SD - 10-6-10-5 0
SD detected at
the MAC
layer
exceeds
the upper
threshold.
PORT_EXC_ The PORT_RX_B 0-100 (%) Upper

TRAFFIC bandwidth W_UTILIZA threshold:
utilization TION 100%
of a port Lower
exceeds threshold:
the upper 75%
threshold.


PORT_TX_B 0-100 (%) Upper

W_UTILIZA threshold:
TION 100%
Lower
threshold:
75%
MAC_EXT_ Bit errors ETHDROP 10GE: Upper

EXC at the MAC 0-150000 threshold:
layer (times) 90
exceed the Lower
upper threshold:
threshold. 0
GE: Upper
0-15000 threshold:
(times) 9
Lower
threshold:
0
100M: Upper
0-204800 threshold:
(times) 1
Lower
threshold:
0
10M: Upper
0-20480 threshold:
(times) 1
Lower
threshold:
0
4G: Upper
0-15000 threshold:
(times) 36
Lower
threshold:
0
2.5G: Upper
0-15000 threshold:
(times) 9
Lower
threshold:
0


400M: Upper
0-204800 threshold:
(times) 4
Lower
threshold:
0
ETHEXCCO 10GE: Upper

L 0-65535 threshold:
(frames) 10
Lower
threshold:
0
GE: Upper
0-15000 threshold:
(frames) 10
Lower
threshold:
0
100M: Upper
0-65535 threshold:
(frames) 10
Lower
threshold:
0
10M: Upper
0-20480 threshold:
(frames) 10
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: Upper
0-248 threshold:
(bytes) 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 - 1-100 0
SD PW
MPLS_PW_ SF on a PW - 1-100 0
SF
CES_LOSPK The - 0-1000 Upper

T_EXC number of threshold:
CES 100
packets Lower
lost within threshold:
a certain 5
period
exceeds
the upper
threshold.


CES_MISO The - 0-1000 Upper

RDERPKT_E number of threshold:
XC CES 100
packets Lower
lost due to threshold:
disorder 5
within a
certain
period
exceeds
the upper
threshold.
CES_STRAY The - 0-1000 Upper

PKT_EXC number of threshold:
errored 100
CES Lower
packets threshold:
within a 5
certain
period
exceeds
the upper
threshold.
CES_MALP The - 0-1000 Upper

KT_EXC number of threshold:
deformed 100
CES Lower
packets threshold:
within a 5
certain
period
exceeds
the upper
threshold.
CES_JTRUD The - 0-1000 Upper

R_EXC number of threshold:
jitter buffer 100
underflows Lower
exceeds threshold:
the upper 5
threshold.


CES_JTROV The - 0-1000 Upper

R_EXC number of threshold:
jitter buffer 100
overflows Lower
exceeds threshold:
the upper 5
threshold.
DROPRATI The QOS_PORT 0-100 (%) Upper

O_OVER number of QUEUE_DR threshold:
packets OPRATIO 0.1%
lost due to Lower
congestion threshold:
exceeds 0
the upper
threshold. QOS_PORT 0-100 (%) Upper
CAR_Marke threshold:
dRedRATIO 0.1%
Lower
threshold:
0
PORTSTRM 0-100 (%) Upper

_SHAPING_ threshold:
DROPRATI 0.1%
O Lower
threshold:
0
TX_DROP_ 0-100 (%) Upper

RATIO threshold:
30%
Lower
threshold:
25%
FLOW_OVE The traffic PORT_PRI_ 10GE: 0-259 Upper

R exceeds SNDBYTES (bytes) threshold:
the upper 118750000
threshold. 0 (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:
117230000
0 (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:
117230000
0 (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_B 10GE: 0-259 Upper

YTES (bytes) threshold:
117230000
0 (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

BYTES (bytes) threshold:
117230000
0 (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

117230000
0 (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_RCV 10GE: 0-259 Upper

117230000
0 (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_SND 10GE: 0-259 Upper

117230000
0 (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_RCVBY 10GE: 0-259 Upper

TES (bytes) threshold:
117230000
0 (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_SNDBY 10GE: 0-259 Upper

TES (bytes) threshold:
117230000
0 (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

ULLFRAME 0-1500000 threshold:
SPEED 000 9500000
(kbit/s) (kbit/s)
Lower
threshold:
7500000
(kbit/s)
GE: Upper
0-1500000 threshold:
00 (kbit/s) 950000
(kbit/s)
Lower
threshold:
750000
(kbit/s)
100M: Upper
0 (kbit/s) 95000
(kbit/s)
Lower
threshold:
75000
(kbit/s)
10M: Upper
(kbit/s) 9500
(kbit/s)
Lower
threshold:
7500
(kbit/s)
4G: Upper
00 (kbit/s) 3800000
(kbit/s)
Lower
threshold:
3000000
(kbit/s)


2.5G: Upper
00 (kbit/s) 2375000
(kbit/s)
Lower
threshold:
1875000
(kbit/s)
400M: Upper
0 (kbit/s) 380000
(kbit/s)
Lower
threshold:
300000
(kbit/s)
TXGOODF 10GE: Upper

ULLFRAME 0-1500000 threshold:
SPEED 000 9500000
(kbit/s) (kbit/s)
Lower
threshold:
7500000
(kbit/s)
GE: Upper
00 (kbit/s) 950000
(kbit/s)
Lower
threshold:
750000
(kbit/s)
100M: Upper
0 (kbit/s) 95000
(kbit/s)
Lower
threshold:
75000
(kbit/s)


10M: Upper
(kbit/s) 9500
(kbit/s)
Lower
threshold:
7500
(kbit/s)
4G: Upper
00 (kbit/s) 3800000
(kbit/s)
Lower
threshold:
3000000
(kbit/s)
2.5G: Upper
00 (kbit/s) 2375000
(kbit/s)
Lower
threshold:
1875000
(kbit/s)
400M: Upper
0 (kbit/s) 380000
(kbit/s)
Lower
threshold:
300000
(kbit/s)
RXOCTETS 10GE: Upper

000 (bytes) 100000000
0 (bytes)
Lower
threshold:
750000000
(bytes)


GE: Upper
00 (bytes) 100000000
(bytes)
Lower
threshold:
75000000
(bytes)
100M: Upper
0 (bytes) 10000000
(bytes)
Lower
threshold:
7500000
(bytes)
10M: Upper
(bytes) 1000000
(bytes)
Lower
threshold:
750000
(bytes)
TXOCTETS 10GE: Upper

000 (bytes) 100000000
0 (bytes)
Lower
threshold:
750000000
(bytes)
GE: Upper
00 (bytes) 100000000
(bytes)
Lower
threshold:
75000000
(bytes)


100M: Upper
0 (bytes) 10000000
(bytes)
Lower
threshold:
7500000
(bytes)
10M: Upper
(bytes) 1000000
(bytes)
Lower
threshold:
750000
(bytes)
Table 13-4 Other alarm thresholds

Alarm Name Description Threshold Default Reference
Range Threshold
L3V_TRAP_TH The number 1-100 The allowed -

RE_EXCEED of private maximum
network number of
prefixes route prefixes
exceeds the is not limited
upper for the VPN
threshold. instance IPv4
address
family.

Alarm Name Description Threshold Default Reference

Range Threshold
FDBSIZEALM_ E-LAN Upper Upper In the NE

ELAN forwarding threshold threshold: Explorer,
table entries range: 80-100 95% select the
are (%) Lower desired NE
exhausted. Lower threshold: and choose
threshold 90% Configuratio
range: 60-100 n > 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_ENTRIES The number Upper Upper Configuring

_EXC of IGMP threshold threshold: the IGMP
snooping range: 80-100 100% Snooping
entries (%) Lower Protocol
exceeds the Lower threshold:
upper threshold 80%
threshold. range: 60-100
(%)

13.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 13-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
● 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.
● 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.
● When the IFX2 and IFU2 board detect the MW_LOF, MW_LIM, or R_LOF alarm, it
forcibly inserts the AIS.

13.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 13-6 Setting of the UNEQ insertion

Trigger Condition Default Value Applicable Board
T_ALOS Disabled SP3S and SP3D

Service path being not in Disabled
use

Maintenance Guide 14 Performance Event Management
14 Performance Event Management
The performance event management is classified into the NE performance event

management and board performance event management.
14.1 NE Performance Event Management

The NE performance event management function set by user is applicable to all
the boards on the NE.
14.2 Board Performance Event Management
The performance event management function is only applicable to the board on
which users have configured this function.
14.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:
● Setting NE performance event monitoring
● Setting the start/end time of performance events
● Enabling/Disabling the reporting of UAT events
For details about these functions, see the manuals or online Help of the NMS.
14.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 14 Performance Event Management
Table 14-1 Board performance event management function

Function Applicable Board
Setting 15- SL1DA, EMS6, SL1D, SP3S, SP3D, CSHN, SL4D, ODU,
minute/24-hour IFX2, IFU2, IF1, ISU2, ISX2, ML1, MD1, EFP8, ISV3, ISM6,
performance CQ1
monitoring
Setting 15- SL1DA, EMS6, SL1D, SP3S, SP3D, CSHN, SL4D, ODU,
minute/24-hour IFX2, IFU2, IF1, ISU2, ISX2, ML1, MD1, EFP8, ISV3, ISM6,
performance event CQ1
auto-reporting
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 SL1DA, EMS6, SL1D, SL4D, SP3S, SP3D, IFX2, IFU2, IF1,
performance ISU2, ISX2, ML1, MD1, EFP8, ISV3, ISM6, CQ1
threshold-crossing
alarms
Monitoring UAT SL1DA, EMS6, SL1D, SL4D, SP3S, SP3D, IFX2, IFU2, IF1,
events 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 15 Alarm Suppression Relationship
15 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.
15.1 Alarm Suppression on TDM Plane

This section describes the alarm suppression relationship for SDH/PDH signals and
IF signals on the TDM plane.
15.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.
15.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 15-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, HP_UNEQ,
HP_TIM, HP_SLM, HP_RDI, HP_LOM, HP_REI
MS_AIS MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD, HP_UNEQ,

B1_EXC B1_SD, MS_REI
AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM,

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 15-2 Suppression relationship between intra-board alarms (IFU2/IFX2/ISU2/

ISX2/ISV3/ISM6/ISM8 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_EX MW_BER_SD
C
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 15-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,
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,

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, HP_UNEQ,

AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM,

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 15-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_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_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 15-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 15-6 Suppression relationship between intra-board alarms (CSHN board)

PG_LINK_FAI PG_PRT_DEGRADED
L
LCS_EXPIRE LCS_LIMITED
D
LCS_FILE_NO LCS_LIMITED
T_EXIST
Table 15-7 Suppression relationship between intra-board alarms (CSHNU board)

PG_LINK_FAI PG_PRT_DEGRADED
L
LCS_EXPIRE LCS_LIMITED
D
LCS_FILE_NO LCS_LIMITED
T_EXIST
TEMP_ALAR TEMP_OVER
M
Table 15-8 Suppression relationship between intra-board alarms (PIU board)

POWER_AB THUNDERALM
NORMAL

Table 15-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 15-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 15-11 Inter-board Alarm Suppression on TDM Plane (IF board - Tributary
board)

AU_LOP, R_LOF
MW_LOF, MW_LIM TU_AIS
Table 15-12 Inter-board Alarm Suppression on TDM Plane (Line board - Tributary
board)

AU_LOP, R_LOF

15.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 15-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_MOD LASER_SHUT, IN_PWR_ABN, OUT_PWR_ABN, LSR_BCM_ALM,

_ERR TEM_HA, TEM_LA, ETH_LOS, TF, LSR_WILL_DIE ,
OUT_PWR_ABN, LSR_BCM_ALM
LASER_SHUT LSR_BCM_ALM, LSR_WILL_DIE, OUT_PWR_ABN,

OUT_PWR_HIGH, OUT_PWR_LOW
TF OUT_PWR_ABN, LSR_WILL_DIE
ETH_EFM_D ETH_EFM_REMFAULT
F
ETH_EFM_RE ETH_EFM_EVENT
MFAULT
MAC_FCS_EX MAC_FCS_SD
C
ETH_AUTO_ LASER_SHUT
LINK_DOWN
LPT_CFG_CL LASER_SHUT
OSEPORT
ETH_LOS ETH_NO_FLOW, IN_PWR_LOW, IN_PWR_HIGH, ARP_FAIL,

LOCAL_FAULT, REMOTE_FAULT
LASER_MOD IN_PWR_HIGH,IN_PWR_LOW,OUT_PWR_HIGH,OUT_PWR_LO
ULE_MISMA W,TEM_HA,TEM_LA,LSR_BCM_ALM,LSR_WILL_DIE
TCH

Table 15-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, MPLS_TUNNEL_SD,
CH MPLS_TUNNEL_UNEXPMEP, MPLS_TUNNEL_UNEXPPER

EL_FDI MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
MPLS_TUNN MPLS_TUNNEL_MISMATCH, MPLS_TUNNEL_LOCV,

EL_UNEXPM MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess,
EG MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,

EL_UNEXPM MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
EP MPLS_TUNNEL_UNEXPPER

EL_AIS MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
MPLS_TUNN MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess,

EL_LOCV MPLS_TUNNEL_SF
MPLS_TUNN MPLS_TUNNEL_SD
EL_SF
Table 15-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 15-16 Suppression relationship between intra-board alarms (Tunnel APS)

ETH_APS_PA ETH_APS_LOST
TH_MISMAT
CH
ETH_APS_LO ETH_APS_TYPE_MISMATCH, ETH_APS_SWITCH_FAIL

ST
Table 15-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 15-18 Suppression relationship between intra-board alarms (ETH OAM)

ETH_CFM_M ETH_CFM_LOC
ISMERGE
ETH_CFM_U
NEXPERI
ETH_CFM_AI
S

Table 15-19 Suppression relationship between intra-board alarms (CES services)

CES_LOSPKT CES_STRAYPKT_EXC, CES_JTROVR_EXC, CES_JTRUDR_EXC

_EXC
CES_STRAYP CES_MISORDERPKT_EXC, CES_MALPKT_EXC

KT_EXC
Table 15-20 Suppression relationship between intra-board alarms (ATM/IMA

services)
IMA_GROUP VC_LOC, VP_LOC

_LE_DOWN
ALM_IMA_LI ALM_IMA_LODS
F
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 15-21 Suppression relationship between intra-board alarms (PPP)

PPP_LCP_FAI PPP_NCP_FAIL
L
Table 15-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_VC1 LP_TIM_VC12, LP_SLM_VC12, LP_UNEQ_VC12LP_RDI_VC12

2
LP_UNEQ_V LFA
C12

BIP_EXC BIP_SD
Table 15-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_OAMFAIL
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 15-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, MPLS_TUNNEL_AIS,
ETH_LOS, MPLS_TUNNEL_RDI, MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
LASER_MOD MPLS_PW_UNKNOWN, MPLS_PW_Excess,
_ERR MPLS_TUNNEL_MISMERGE, MPLS_TUNNEL_MISMATCH,
MPLS_PW_UNEXPMEG, MPLS_TUNNEL_UNEXPMEP
Table 15-25 Suppression relationship between inter-board alarms (IF board-

Switching board)
R_LOC MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL

Table 15-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 16 Indicators of Boards
16 Indicators of Boards
Indicators of Boards
Table 16-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 ● The board is not working.

● The board is not created.
● There is no power supplied to
the board.
PROG Blinks on (green) and Software is being loaded to the

off at 100 ms intervals board during the board power-on
or reset process.
Blinks on (green) and The board software is in BIOS boot

off at 300 ms intervals state during the board power-on
or reset process.
Blinks on (green) and The active system control board is

off at 1s intervals synchronizing data to the standby
system control board.
On (green) ● The board is being powered on

or being reset, and the upper
layer software is being
initialized.
● The board is running and the
software is running normally.
Blinks on (red) and off The BOOTROM self-check fails

at 100 ms intervals during the board power-on or
reset process.

On (red) ● The memory self-check fails or

loading upper layer software
fails during the board power-on
or reset process.
● The logic file or upper layer
software is lost during the
board running process.
● The pluggable storage card is
faulty.
● 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 synchronization sources are

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

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

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

Off No data is being transmitted or

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 16-2 Status explanation for indicators on the CSHNA


● The board has not been
created.
the board.

or reset process.
Blinks on (green) and The board software is in BIOS

off at 300 ms intervals boot state during the board
power-on or reset process.
Blinks on (green) and The active system control board

off at 1s intervals is synchronizing data to the
standby system control board.

On (green) ● The board is being powered

on or being reset, and the
upper layer software is being
initialized.

reset process.
On (red) ● The memory self-check fails

or loading upper layer
software fails during the
board power-on or reset
process.
between the active and
standby system control boards
fails, the PROG indicator on
the standby system control
board is steady red.

lost.




USB USB Blinks (red) The USB flash drive is online but
flash faulty, or the NE does not
drive support the 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) ● A USB flash drive is online.

● 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 ● No WLAN module is

connected to the USB port.
● The WLAN module connected
to the USB port cannot be
identified.

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.
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 16-3 Status explanation for indicators on the CSHNU


created.
the board.

or reset process.



initialized.

reset process.


process.

lost.





drive.

failed.


complete.

flash drive.

properly.

identified.


of R_LOS alarms.

alarm.

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 Port has received extremely high

at 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 optical power (applicable only to
at 1000 ms intervals an optical port).
Blinks (yellow) Port is receiving or transmitting

data.


Table 16-4 Status explanation for indicators on the CSHNA


created.
the board.

or reset process.



initialized.

reset process.


process.

lost.





drive.

failed.


complete.

flash drive.

properly.

identified.


of R_LOS alarms.

alarm.

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 16-5 Status explanation for indicators on the IF1

STAT On (green) The board is working

properly.
On (red) The board hardware is

faulty.
Off ● The board is not

working.
● The board is not
created.
● 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) ● The ODU is reporting

critical or major
alarms.
supplied to the ODU.
On (yellow) The ODU is reporting

minor alarms.
Blinks on (yellow) and The antennas are not

off at 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) ● 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.
system, the board is
not activated.
Table 16-6 Status explanation for indicators on the IFU2


● 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) ● The ODU is reporting critical or

major alarms.
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) ● In a 1+1 protected system, the

● In an unprotected system, the
Off ● In a 1+1 protected system, the

● In an unprotected system, the
Table 16-7 Status explanation for indicators on the ISU2


properly.

faulty.

working.
created.




properly.

critical or major
alarms.

minor alarms.


reporting defects.

free of defects.

system, the board
works as the active
one.
been activated.

system, the board
one.
not activated.
Table 16-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.
created.



properly.

critical or major
alarms.

minor alarms.


reporting defects.

free of defects.


system, the board
works as the active
one.
been activated.

system, the board
one.
not activated.
Table 16-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.
created.




properly.

critical or major
alarms.

minor alarms.


reporting defects.

free of defects.

system, the board
works as the active
one.
been activated.

system, the board
one.
not activated.
Table 16-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.

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

working as the main
board.
In an unprotected
been activated.

Off In a 1+1 protected

working as the standby
board.
In an unprotected
not been activated.
Table 16-11 Status explanation for indicators on an ISM6 board


properly.

faulty.

not powered on.

has been reported.

has been reported.
LINK1 On (green) The first microwave link

is normal.
On (red) The first microwave link

is faulty.
Off ● The ODU connected

to the IF1 port is
offline.
● No logical board is
configured for the
ODU connected to IF1
port.

ACT1 On (green) ● In a 1+1 protected

system, the first
microwave link is
working as the main
link.
system, the first
microwave link has
been activated.

system, the first
microwave link is
working as the
standby link.
system, no logical
board is added for the
port.
LINK2 On (green) The second microwave

link is normal.
On (red) The second microwave

link is faulty.
Off ● The ODU connected

to the IF2 port is
offline.
● No logical board is
configured for the
port.

system, the second
microwave link is
working as the main
link.
system, the second
microwave link has
been activated.


system, the second
microwave link is
working as the
standby link.
system, no logical
board is added for the
port.
Table 16-12 Description of the indicators on an ISM8 board


properly.

faulty.
Off The board is not working,

not created, or not
powered on.

reported.
Steady yellow A minor or remote alarm

is reported.
L/A On (green) The port is connected

correctly and is not
receiving or transmitting
data.
Blinking on (red) for 300 Port COMBO port has

ms and off for 300 ms received too strong power
repeatedly (applicable only to optical
ports).
Blinking on (red) for 300 Port COMBO port has

ms and off for 700 ms received too weak power
repeatedly (applicable only to optical
ports).
Blinking (yellow) The COMBO port is

receiving or transmitting
data.

Off The COMBO port is not

connected or is incorrectly
connected.
LINK1 On (green) The first microwave link is

normal.
On (red) The first microwave link is

faulty.
Off ● The ODU connected to

port IF1 is not powered
on.
● No ODU logic board is
configured for port IF1.

system, the first
microwave link works
as the main one.
system, the first
microwave link has
been activated.

system, the first
as the standby one.
system, no ODU logic
board is configured for
port IF1.
LINK2 On (green) The second microwave link

is normal.
On (red) The second microwave link

is faulty.
Off ● The ODU connected to

port IF2 is not powered
on.
● ODU logic board is
configured for port IF2.


system, the second
as the main one.
system, the second
microwave link has
been activated.

system, the second
as the standby one.
system, no ODU logic
board is configured for
port IF2.
Table 16-13 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 Software is being loaded to the board
at 100 ms intervals during the power-on or resetting
process of the board.
Blinks on (green) and off The board software is in BIOS boot

at 300 ms intervals state during the power-on or
resetting process of the board.

On (green) ● When the board is being powered

on or being reset, the upper layer
software is being initialized.
● When the board is running, the
Blinks on (red) and off at The BOOTROM self-check fails during

100 ms intervals the power-on or resetting process of
the board.

loading upper layer software fails
during the power-on or resetting
software is lost during the running
faulty.
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

data.
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 16-14 Status explanation for indicators on the EM6TA/EM6FA



board.

system.

system.



the board.
On (red) The memory self-check fails or

The logic file or upper layer software
is lost during the running process of
the board.
The pluggable storage card is faulty.
L/A1a On (green) The GE1 port is connected correctly

data.
Blinking (yellow) The GE1 port is receiving or

transmitting data.


L/A2a On (green) The GE2 port is connected correctly

data.
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 16-15 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

(optical/ not receiving or transmitting data.
electrical
port 1) Blinks on (red) and off at Port GE1 has received extremely high
300 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 optical power (applicable only to an
1000 ms intervals optical port).
Blinks (yellow) Port GE1 is receiving or transmitting

data.
Off Port GE1 is not connected or is



electrical Blinks on (red) and off at Port GE2 has received extremely high
port 2) 300 ms intervals optical power (applicable only to an
optical port).

data.


(electrical not receiving or transmitting data.
port 3)
data.


(electrical not receiving or transmitting data.
port 4)
data.

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

data.


electrical
optical port).

data.


electrical
optical port).


data.


electrical
optical port).

data.

Table 16-17 Status explanation for indicators on an EX1


properly.

faulty.

working or created.
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
and 300 ms off power.
Blinks (red) once every The port on the board

second, 300 ms on and receives too weak power.
700 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 16-18 Status explanation for indicators on the EMS6


board.


On (green) ● The upper layer software is being

initialized during the power-on or
● The software is running properly
during the running process of the
board.

the board.

faulty.
SRV On (green) The system is working normally.

system.

system.
LINK1 On (green) The GE1 port is connected correctly.
Blinks on (red) and off at The receive optical power at the GE1
300 ms intervals optical port is higher than the upper
threshold.
Blinks 300 ms on (red) The receive optical power at the GE1

and 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 The receive optical power at the GE2
300 ms intervals optical port is higher than the upper
threshold.
Blinks 300 ms on (red) The receive optical power at the GE2

and 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 16-19 Status explanation for indicators on the EFP8


board.



the board.


faulty.

system.

system.
Table 16-20 Status explanation for indicators on the SL1D/SL1DA


properly.

faulty.

working.
created.


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 16-21 Status explanation for indicators on the SP3S/SP3D


properly.

faulty.

working.
created.



configured.
Table 16-22 Status explanation for indicators on the ML1/MD1


properly.

faulty.


working.
created.



configured.
Table 16-23 Status explanation for indicators on a CQ1 board


properly.

faulty.

not powered on.

has 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
alarm.
Off The fourth port does not

Table 16-24 Status explanation for indicators on the AUX

the board.
On (red) A critical or major alarm occurs in

the system.
On (yellow) A minor or remote alarm occurs in

the system.

system.
Table 16-25 Status explanation for indicators on the PIU
Indicator Status Description
PWR On (green) The power supply is

normal.
Off There is no power supply.

Indicator Status Description
ALM On (orange) The board is in the

initialization state.
On (red) An alarm is reported on

the PIU/PIUA.
Off No alarm occurs.
Table 16-26 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 V100R019C10 Maintenance Guid

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RTN 980 V100R019C10 Maintenance Guid

Uploaded by

Copyright:

Available Formats

OptiX RTN 980 Radio Transport System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. i

1 About This Document.............................................................................................................1

3 Notices for High-Risk Operations......................................................................................22

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. ii

5.2.6 Browsing UAT Events....................................................................................................................................................... 46

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. iii

6.1 General Troubleshooting Procedure............................................................................................................................... 94

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. iv

7.18.1 Board Storage Media...................................................................................................................................................205

8 Database Backup and Restoration..................................................................................208

9 Common Maintenance Operations.................................................................................227

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. v

9.4.8 Setting Software Loopback for the NE.................................................................................................................... 272

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. vi

10.2.20 AU_AIS........................................................................................................................................................................... 342

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. vii

10.2.62 CLK_LOCK_FAIL........................................................................................................................................................... 411

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. viii

10.2.104 ETH_EFM_EVENT..................................................................................................................................................... 474

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. ix

10.2.146 IF_INPWR_ABN......................................................................................................................................................... 533

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. x

10.2.188 LCS_FILE_NOT_EXIST.............................................................................................................................................. 591

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xi

10.2.230 MPLSLDPSESSIONDOWN..................................................................................................................................... 644

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xii

10.2.272 MW_BER_EXC............................................................................................................................................................ 689

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xiii

10.2.314 PATCH_CHGSCC_NOTMATCH............................................................................................................................. 764

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xiv

10.2.356 RADIO_RSL_LOW..................................................................................................................................................... 822

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xv

10.2.398 T_LOC........................................................................................................................................................................... 870

11 Performance Event Reference........................................................................................ 927

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xvi

11.1 Performance Events (by Event Type)........................................................................................................................ 927

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xvii

11.2.37 RSOOF and RSOFS..................................................................................................................................................... 969

12 RMON Event Reference................................................................................................... 978

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xviii

12.3.12 ATMPW_LOSPKTS.................................................................................................................................................... 1418

13 Alarm Management....................................................................................................... 1427

14 Performance Event Management............................................................................... 1458

15 Alarm Suppression Relationship................................................................................. 1460

16 Indicators of Boards....................................................................................................... 1472

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. xix

1 About This Document

Product Name Version

OptiX RTN 980 V100R019C10

This document is intended for:

● Network planning engineer

Indicates a hazard with a high level of risk which, if not

Issue 01 (2019-12-31) Copyright © Huawei Technologies Co., Ltd. 1

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

Indicates a hazard with a low level of risk which, if not

Indicates a potentially hazardous situation which, if not

Supplements the important information in the main text.

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.