RTN 380 V100R019C00 Maintenance Guide

OptiX RTN 380 Radio Transmission System
V100R019C00
Maintenance Guide
Issue 02
Date 2020-06-30
HUAWEI TECHNOLOGIES CO., LTD.

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

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

Maintenance Guide About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX RTN 380 V100R019C00
NCE V100R019C00
Intended Audience
This document provides the guidelines to maintaining the OptiX RTN 380. 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 an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

avoided, may result in minor or moderate injury.
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. ii

Symbol Description

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

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

boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen

are in Courier New.
Command Conventions
The command conventions that may be found in this document are defined as
follows.
Boldface The keywords of a command line are in boldface.
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.
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iii

[ 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
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Issue 02 (2020-06-30) Based on Product Version V100R019C00

This issue is the second release for the product version V100R019C00.
Update Description
Entire document All the screenshots of the U2000 are

replaced by the screenshots of the
NCE.
- Fixed the known bugs.
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iv

Issue 01 (2019-5-30) Based on Product Version V100R019C00

This issue is the first release for the product version V100R019C00.
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. v

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

1 Safety Precautions...................................................................................................................1
1.1 General Safety Precautions.................................................................................................................................................. 2
1.2 Warning and Safety Symbols.............................................................................................................................................. 3
1.3 Electrical Safety........................................................................................................................................................................ 4
1.4 Environment of Flammable Gas........................................................................................................................................ 5
1.5 Storage Batteries..................................................................................................................................................................... 6
1.6 Radiation.................................................................................................................................................................................... 8
1.6.1 Safe Usage of Optical Fibers............................................................................................................................................8
1.6.2 Electromagnetic Exposure................................................................................................................................................. 8
1.6.3 Forbidden Areas....................................................................................................................................................................9
1.6.4 Laser......................................................................................................................................................................................... 9
1.6.5 Microwave............................................................................................................................................................................ 10
1.7 Working at Heights.............................................................................................................................................................. 10
1.7.1 Hoisting Heavy Objects................................................................................................................................................... 10
1.7.2 Using Ladders..................................................................................................................................................................... 11
1.8 Mechanical Safety.................................................................................................................................................................13
1.9 Other Precautions................................................................................................................................................................. 14
2 Routine Maintenance Items............................................................................................... 16

3 Troubleshooting.....................................................................................................................19
3.1 General Troubleshooting Procedure............................................................................................................................... 19
3.2 Troubleshooting Microwave Link Faults........................................................................................................................23
3.3 Troubleshooting Ethernet Service Faults...................................................................................................................... 31
3.4 Troubleshooting DCN Faults............................................................................................................................................. 34
4 Part Replacement.................................................................................................................. 38
4.1 Replacing an OptiX RTN 380............................................................................................................................................ 38
4.2 Replacing an SFP Module.................................................................................................................................................. 41
5 Database Backup and Restoration.................................................................................... 43

5.1 NE Database........................................................................................................................................................................... 43
5.2 Backing Up the Database Manually............................................................................................................................... 45
5.3 Backing Up the Database Periodically...........................................................................................................................46
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vi

5.3.1 Setting the User-Defined Backup Policy....................................................................................................................46

5.3.2 Executing the Backup Policy of the Device...............................................................................................................48
5.3.3 Suspending the Backup Policy of the Device........................................................................................................... 49
5.4 Restoring the Database by NMS..................................................................................................................................... 50
5.5 Restoring Databases for an NE from Its Peer NE...................................................................................................... 54
5.6 Restoring Databases from a USB Flash Drive............................................................................................................. 55
6 Monitoring a Network......................................................................................................... 58
6.1 Browsing Alarms and Performance Data..................................................................................................................... 58
6.1.1 Browsing Current Alarms................................................................................................................................................ 59
6.1.2 Browsing History Alarms................................................................................................................................................ 62
6.1.3 Browsing Current Performance Events...................................................................................................................... 64
6.1.4 Browsing History Performance Events....................................................................................................................... 66
6.1.5 Browsing the Performance Event Threshold-Crossing Records......................................................................... 67
6.2 Browsing Performance Data of a Microwave link..................................................................................................... 68
6.2.1 Browsing Historical Transmit Power and Receive Power.....................................................................................69
6.2.2 Querying the SNR of a Microwave Link.................................................................................................................... 69
6.2.3 Browsing Current Performance Events of a Microwave link.............................................................................. 70
6.2.4 Browsing Historical Performance Data of a Microwave link..............................................................................71
6.3 Browsing Ethernet Performance Data........................................................................................................................... 72
6.3.1 Browsing Current Performance Events of Ethernet............................................................................................... 72
6.3.2 Setting the Ethernet Performance Threshold-Crossing Parameter.................................................................. 73
6.3.3 Configuring the Parameters for Ethernet Historical Performance Monitoring............................................ 74
6.3.4 Browsing Ethernet Historical Performance Data....................................................................................................75
6.4 Monitoring Ethernet Traffic Volumes at Ports............................................................................................................75
6.4.1 Enabling Flow Monitoring, Physical Bandwidth Monitoring, and Bandwidth Usage Monitoring for
Ports.................................................................................................................................................................................................. 75
6.4.2 Querying the Traffic Volume, Physical Bandwidth, and Bandwidth Usage of a Port................................76
6.5 Monitoring Entire-Network Performance in a Long Term..................................................................................... 77
6.5.1 Creating a Performance Monitoring Template....................................................................................................... 77
6.5.2 Creating a Performance Monitoring Instance......................................................................................................... 79
6.5.3 Browsing the Real-Time Data of a Performance Monitoring Instance........................................................... 82
6.5.4 Browsing the Historical Data of a Performance Monitoring Instance............................................................ 83
6.6 Querying a Report................................................................................................................................................................ 84
6.6.1 Querying the Board Information Report................................................................................................................... 84
6.6.2 Querying the Board Manufacturing Information Report.................................................................................... 86
6.6.3 Querying the Microwave Link Information Report................................................................................................ 87
6.6.4 Querying the Network-wide License Report............................................................................................................ 88
6.7 Setting Alarm and Performance Management Functions...................................................................................... 89
6.7.1 Configuring the Performance Monitoring Status of NEs.....................................................................................89
6.7.2 Suppressing Alarms.......................................................................................................................................................... 89
6.7.3 Reversing Alarms for Ports............................................................................................................................................. 90
6.7.4 Setting Bit Error Thresholds for Microwave Ports.................................................................................................. 91
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vii

6.7.5 Setting Monitoring and Auto-Report Status of Performance Events.............................................................. 92

6.7.6 Setting Performance Thresholds.................................................................................................................................. 93
6.7.7 Resetting Performance Registers................................................................................................................................. 94
7 Common Maintenance Operations................................................................................... 95

7.1 Software Loopback............................................................................................................................................................... 96
7.1.1 Setting Port Loopbacks for NEs.................................................................................................................................... 96
7.1.2 Setting the Loopback on a Microwave Link............................................................................................................. 98
7.2 Resetting an NE..................................................................................................................................................................... 99
7.3 Common Operations for Handling Microwave Link Faults..................................................................................100
7.3.1 Monitoring Microwave link Indicators..................................................................................................................... 100
7.3.2 Scanning Interfering Signals....................................................................................................................................... 102
7.3.3 Muting/Unmuting an NE............................................................................................................................................. 104
7.3.4 Performing a PRBS Test at an Air Interface........................................................................................................... 104
7.3.5 Enabling the Consecutive Wave Detection Function.......................................................................................... 106
7.3.6 Microwave 1+1 Protection Switching....................................................................................................................... 106
7.3.7 Querying the AM Status............................................................................................................................................... 107
7.3.8 Querying ATPC Adjustment Records........................................................................................................................ 108
7.4 Common Operations for Handling Ethernet Service Faults................................................................................ 109
7.4.1 Querying the Attributes of an Ethernet Port.........................................................................................................109
7.4.2 Using IP Ping Commands to Locate Ethernet Service Faults........................................................................... 109
7.4.3 Capturing Headers of Specified Ethernet Packets............................................................................................... 114
7.4.4 Monitoring Ethernet Packets Through Port Mirroring....................................................................................... 116
7.4.5 Configuring IP Packet Coloring and Statistics Collection.................................................................................. 118
7.4.6 Checking Ethernet Service Performance Using TWAMP Light........................................................................ 121
7.5 Setting the Automatic Release Function.................................................................................................................... 123
7.6 Querying Power Consumption of NE.......................................................................................................................... 125
7.7 Enabling the Power-Saving Mode for an NE............................................................................................................ 126
7.8 Enabling Automatic Fault Recovery............................................................................................................................. 127
7.9 Querying Site Information...............................................................................................................................................128
7.10 Querying the Microwave Link Information Report.............................................................................................. 129
7.11 Querying Optical Power and Alarm Thresholds of Optical Ports................................................................... 130
A Alarm Reference................................................................................................................. 132

A.1 Alarm List.............................................................................................................................................................................. 132
A.2 Alarms and Handling Procedures................................................................................................................................. 142
A.2.1 AM_DOWNSHIFT............................................................................................................................................................ 142
A.2.2 ARP_FAIL............................................................................................................................................................................ 143
A.2.3 ARP_MAC_MISMATCH.................................................................................................................................................. 144
A.2.4 ARP_SPOOF...................................................................................................................................................................... 145
A.2.5 BDTEMP_SENSOR_FAIL.................................................................................................................................................146
A.2.6 BOOTROM_BAD.............................................................................................................................................................. 147
A.2.7 BRDCASTRATIO_OVER.................................................................................................................................................. 148
A.2.8 BUS_ERR.............................................................................................................................................................................149
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. viii

A.2.9 CLK_LOCK_FAIL................................................................................................................................................................ 153

A.2.10 CLK_NO_TRACE_MODE.............................................................................................................................................. 154
A.2.11 COM_EXTECC_FULL..................................................................................................................................................... 155
A.2.12 DBMS_DELETE............................................................................................................................................................... 156
A.2.13 DBMS_ERROR................................................................................................................................................................ 157
A.2.14 DBMS_PROTECT_MODE.............................................................................................................................................160
A.2.15 DB_UNSAVE................................................................................................................................................................... 161
A.2.16 DCNCFG_NOT_COMMIT............................................................................................................................................ 162
A.2.17 DCN_CHANNEL_BITERROR....................................................................................................................................... 162
A.2.18 DCNLINK_OVER............................................................................................................................................................ 164
A.2.19 DCNSIZE_OVER............................................................................................................................................................. 165
A.2.20 DEVICE_AUTH_FAIL..................................................................................................................................................... 166
A.2.21 DROPRATIO_OVER...................................................................................................................................................... 167
A.2.22 ERPS_BLOCK................................................................................................................................................................... 168
A.2.23 ELAN_SMAC_FLAPPING............................................................................................................................................. 169
A.2.24 ERPS_IN_PROTECTION............................................................................................................................................... 171
A.2.25 ERPS_NOT_COMPLETE............................................................................................................................................... 172
A.2.26 ETH_APS_LOST.............................................................................................................................................................. 174
A.2.27 ETH_APS_PATH_MISMATCH.....................................................................................................................................175
A.2.28 ETH_APS_SWITCH_FAIL.............................................................................................................................................. 176
A.2.29 ETH_APS_TYPE_MISMATCH...................................................................................................................................... 177
A.2.30 ETH_AUTO_LINK_DOWN...........................................................................................................................................178
A.2.31 ETH_CFM_AIS................................................................................................................................................................ 179
A.2.32 ETH_CFM_LOC............................................................................................................................................................... 180
A.2.33 ETH_CFM_MISMERGE................................................................................................................................................. 182
A.2.34 ETH_CFM_RDI................................................................................................................................................................ 184
A.2.35 ETH_CFM_UNEXPERI................................................................................................................................................... 185
A.2.36 ETH_EFM_DF.................................................................................................................................................................. 187
A.2.37 ETH_EFM_EVENT.......................................................................................................................................................... 188
A.2.38 ETH_EFM_LOOPBACK................................................................................................................................................. 189
A.2.39 ETH_EFM_REMFAULT.................................................................................................................................................. 191
A.2.40 ETH_LINK_DOWN........................................................................................................................................................ 192
A.2.41 ETH_LOS.......................................................................................................................................................................... 193
A.2.42 ETH_NO_FLOW............................................................................................................................................................. 194
A.2.43 ETHOAM_SELF_LOOP................................................................................................................................................. 195
A.2.44 FDBSIZEALM_ELAN......................................................................................................................................................197
A.2.45 FLOW_OVER................................................................................................................................................................... 198
A.2.46 GNE_CONNECT_FULL................................................................................................................................................. 199
A.2.47 HARD_BAD..................................................................................................................................................................... 200
A.2.48 HARD_ERR...................................................................................................................................................................... 201
A.2.49 IN_PWR_ABN................................................................................................................................................................. 202
A.2.50 INSUFFCNT_MEM_SPACE.......................................................................................................................................... 204
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. ix

A.2.51 INSUFFCNT_FLSH_SPACE.......................................................................................................................................... 205

A.2.52 KMC_KEY_SYNC_FAIL.................................................................................................................................................. 206
A.2.53 LAG_DOWN.................................................................................................................................................................... 207
A.2.54 LAG_MEMBER_DOWN................................................................................................................................................208
A.2.55 LASER_MOD_ERR......................................................................................................................................................... 210
A.2.56 LASER_SHUT.................................................................................................................................................................. 211
A.2.57 LCS_DAYS_OF_GRACE................................................................................................................................................. 212
A.2.58 LCS_EXPIRED.................................................................................................................................................................. 213
A.2.59 LCS_FILE_NOT_EXIST................................................................................................................................................... 214
A.2.60 LCS_LIMITED.................................................................................................................................................................. 215
A.2.61 LCS_TRIAL_PERIOD...................................................................................................................................................... 217
A.2.62 LICENSE_LOST............................................................................................................................................................... 218
A.2.63 LOOP_ALM..................................................................................................................................................................... 219
A.2.64 LSR_BCM_ALM.............................................................................................................................................................. 220
A.2.65 LSR_NO_FITED.............................................................................................................................................................. 221
A.2.66 LSR_WILL_DIE................................................................................................................................................................ 222
A.2.67 LTI...................................................................................................................................................................................... 222
A.2.68 MAC_EXT_EXC............................................................................................................................................................... 224
A.2.69 MAC_FCS_EXC................................................................................................................................................................ 225
A.2.70 MAC_FCS_SD.................................................................................................................................................................. 227
A.2.71 MOD_COM_FAIL........................................................................................................................................................... 228
A.2.72 MPLS_PW_AIS................................................................................................................................................................ 229
A.2.73 MPLS_PW_BDI............................................................................................................................................................... 230
A.2.74 MPLS_PW_CSF............................................................................................................................................................... 231
A.2.75 MPLS_PW_Excess.......................................................................................................................................................... 232
A.2.76 MPLS_PW_LCK............................................................................................................................................................... 233
A.2.77 MPLS_PW_LOCK........................................................................................................................................................... 233
A.2.78 MPLS_PW_LOCV........................................................................................................................................................... 234
A.2.79 MPLS_PW_MISMATCH............................................................................................................................................... 236
A.2.80 MPLS_PW_MISMERGE................................................................................................................................................ 237
A.2.81 MPLS_PW_OAMFAIL....................................................................................................................................................238
A.2.82 MPLS_PW_RDI............................................................................................................................................................... 239
A.2.83 MPLS_PW_SD................................................................................................................................................................. 240
A.2.84 MPLS_PW_SF..................................................................................................................................................................241
A.2.85 MPLS_PW_UNEXPMEG............................................................................................................................................... 242
A.2.86 MPLS_PW_UNEXPMEP............................................................................................................................................... 243
A.2.87 MPLS_PW_UNEXPPER................................................................................................................................................. 244
A.2.88 MPLS_PW_UNKNOWN............................................................................................................................................... 245
A.2.89 MPLS_TUNNEL_AIS......................................................................................................................................................245
A.2.90 MPLS_TUNNEL_BDI..................................................................................................................................................... 246
A.2.91 MPLS_TUNNEL_Excess................................................................................................................................................ 247
A.2.92 MPLS_TUNNEL_FDI..................................................................................................................................................... 248
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. x

A.2.93 MPLS_TUNNEL_LOCK................................................................................................................................................. 249

A.2.94 MPLS_TUNNEL_LOCV................................................................................................................................................. 250
A.2.95 MPLS_TUNNEL_MISMATCH..................................................................................................................................... 251
A.2.96 MPLS_TUNNEL_MISMERGE...................................................................................................................................... 252
A.2.97 MPLS_TUNNEL_OAMFAIL......................................................................................................................................... 253
A.2.98 MPLS_TUNNEL_RDI..................................................................................................................................................... 254
A.2.99 MPLS_TUNNEL_SD.......................................................................................................................................................255
A.2.100 MPLS_TUNNEL_SF..................................................................................................................................................... 256
A.2.101 MPLS_TUNNEL_UNEXPMEG.................................................................................................................................. 257
A.2.102 MPLS_TUNNEL_UNEXPMEP................................................................................................................................... 258
A.2.103 MPLS_TUNNEL_UNEXPPER.................................................................................................................................... 259
A.2.104 MPLS_TUNNEL_UNKNOWN.................................................................................................................................. 260
A.2.105 MULTI_RPL_OWNER................................................................................................................................................. 261
A.2.106 MW_AM_TEST............................................................................................................................................................. 262
A.2.107 MW_BER_EXC.............................................................................................................................................................. 262
A.2.108 MW_BER_SD................................................................................................................................................................ 265
A.2.109 MW_CFG_MISMATCH...............................................................................................................................................267
A.2.110 MW_CONT_WAVE..................................................................................................................................................... 269
A.2.111 MW_FEC_EXC.............................................................................................................................................................. 270
A.2.112 MW_FEC_UNCOR....................................................................................................................................................... 273
A.2.113 MW_LIM........................................................................................................................................................................ 275
A.2.114 MW_LOF....................................................................................................................................................................... 276
A.2.115 MW_RDI........................................................................................................................................................................ 279
A.2.116 NB_CFG_MISMATCH................................................................................................................................................. 280
A.2.117 NB_UNREACHABLE................................................................................................................................................... 283
A.2.118 NE_DCN_MODE.......................................................................................................................................................... 284
A.2.119 NEIP_CONFUSION..................................................................................................................................................... 285
A.2.120 NESF_LOST................................................................................................................................................................... 286
A.2.121 NESOFT_MM............................................................................................................................................................... 287
A.2.122 NTP_SYNC_FAIL.......................................................................................................................................................... 289
A.2.123 OUT_PWR_ABN.......................................................................................................................................................... 290
A.2.124 PASSWORD_NEED_CHANGE..................................................................................................................................291
A.2.125 PATCH_BD_EXCLUDE................................................................................................................................................ 291
A.2.126 PATCH_BD_MATCH_FAIL......................................................................................................................................... 292
A.2.127 PATCH_PKGERR.......................................................................................................................................................... 293
A.2.128 PATCH_INIT_FAIL........................................................................................................................................................294
A.2.129 PATCH_OP_TIMEOUT............................................................................................................................................... 295
A.2.130 PING_ARP_MISMATCH............................................................................................................................................. 296
A.2.131 PING_LOS......................................................................................................................................................................296
A.2.132 PLA_CFG_MISMATCH............................................................................................................................................... 298
A.2.133 PLA_DOWN.................................................................................................................................................................. 300
A.2.134 PLA_MEMBER_DOWN_EXT.................................................................................................................................... 301
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xi

A.2.135 PLA_PKT_ERR............................................................................................................................................................... 303

A.2.136 PORT_BER_SD............................................................................................................................................................. 304
A.2.137 PORT_EXC_TRAFFIC...................................................................................................................................................305
A.2.138 PORTMODE_MISMATCH......................................................................................................................................... 306
A.2.139 POWER_ALM............................................................................................................................................................... 307
A.2.140 PRO_PKT_FLOODING............................................................................................................................................... 308
A.2.141 PTP_SOURCE_SWITCH............................................................................................................................................. 309
A.2.142 PTP_TIME_ADJUST_OFF........................................................................................................................................... 311
A.2.143 PTP_TIMESTAMP_ABN............................................................................................................................................. 312
A.2.144 PW_APS_DEGRADED................................................................................................................................................ 314
A.2.145 PW_APS_OUTAGE...................................................................................................................................................... 315
A.2.146 PW_DROPPKT_EXC.................................................................................................................................................... 315
A.2.147 PW_NO_TRAFFIC........................................................................................................................................................316
A.2.148 PWAPS_LOST............................................................................................................................................................... 318
A.2.149 PWAPS_PATH_MISMATCH...................................................................................................................................... 319
A.2.150 PWAPS_SWITCH_FAIL............................................................................................................................................... 320
A.2.151 PWAPS_TYPE_MISMATCH....................................................................................................................................... 320
A.2.152 PWD_ENCRYPT_RISK................................................................................................................................................ 321
A.2.153 R_LOF............................................................................................................................................................................. 322
A.2.154 R_LOS............................................................................................................................................................................. 325
A.2.155 RADIO_FADING_MARGIN_INSUFF....................................................................................................................... 327
A.2.156 RADIO_MUTE.............................................................................................................................................................. 328
A.2.157 RADIO_RSL_BEYONDTH.......................................................................................................................................... 329
A.2.158 RADIO_RSL_HIGH...................................................................................................................................................... 330
A.2.159 RADIO_RSL_LOW....................................................................................................................................................... 331
A.2.160 RADIO_TSL_HIGH...................................................................................................................................................... 333
A.2.161 RADIO_TSL_LOW........................................................................................................................................................333
A.2.162 REFLECTOR_IP_CNFLCT............................................................................................................................................334
A.2.163 RPS_INDI....................................................................................................................................................................... 335
A.2.164 S1_SYN_CHANGE....................................................................................................................................................... 337
A.2.165 SEC_RADIUS_FAIL.......................................................................................................................................................338
A.2.166 SECU_ALM.................................................................................................................................................................... 339
A.2.167 SRV_LOOP_LD............................................................................................................................................................. 340
A.2.168 SRV_SHUTDOWN_LD............................................................................................................................................... 341
A.2.169 SSL_CERT_DAMAGED............................................................................................................................................... 343
A.2.170 SSL_CERT_NOENC..................................................................................................................................................... 343
A.2.171 SSL_CERT_TO_EXPIRE............................................................................................................................................... 344
A.2.172 STORAGE_FAIL............................................................................................................................................................ 345
A.2.173 STORM_CUR_QUENUM_OVER..............................................................................................................................347
A.2.174 SUBNET_RT_CONFLICT............................................................................................................................................ 348
A.2.175 SWDL_ACTIVATED_TIMEOUT................................................................................................................................ 350
A.2.176 SWDL_COMMIT_FAIL............................................................................................................................................... 351
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xii

A.2.177 SWDL_INPROCESS..................................................................................................................................................... 352

A.2.178 SWDL_NEPKGCHECK................................................................................................................................................ 352
A.2.179 SWDL_PKGVER_MM..................................................................................................................................................353
A.2.180 SYN_BAD....................................................................................................................................................................... 354
A.2.181 SWDL_ROLLBACK_FAIL............................................................................................................................................ 356
A.2.182 SYNC_C_LOS................................................................................................................................................................ 356
A.2.183 SYSLOG_COMM_FAIL............................................................................................................................................... 358
A.2.184 TEM_HA........................................................................................................................................................................ 359
A.2.185 TEM_LA..........................................................................................................................................................................360
A.2.186 TEMP_ALARM..............................................................................................................................................................360
A.2.187 TF..................................................................................................................................................................................... 362
A.2.188 TIME_LOCK_FAIL........................................................................................................................................................ 362
A.2.189 TIME_LOS......................................................................................................................................................................364
A.2.190 TIME_NO_TRACE_MODE......................................................................................................................................... 365
A.2.191 TUNNEL_APS_DEGRADED...................................................................................................................................... 366
A.2.192 TUNNEL_APS_OUTAGE............................................................................................................................................ 367
A.2.193 USB_FILE_UNSEC........................................................................................................................................................368
A.2.194 USB_PROCESS_FAIL................................................................................................................................................... 369
A.2.195 VERSION_NOTSUPPORT......................................................................................................................................... 371
B Performance Event Reference.......................................................................................... 372

B.1 Performance Event List.....................................................................................................................................................372
B.1.1 Microwave Performance Events................................................................................................................................. 372
B.1.2 MPLS Tunnel/PW Performance Events.................................................................................................................... 375
B.1.3 Other Performance Events...........................................................................................................................................376
B.2 Performance Events and Handling Procedures........................................................................................................ 378
B.2.1 AMDOWNCNT and AMUPCNT.................................................................................................................................. 379
B.2.2 ATPC_P_ADJUST and ATPC_N_ADJUST................................................................................................................... 380
B.2.3 CPUUSAGEMAX, CPUUSAGEMIN, CPUUSAGECUR, and CPUUSAGEAVG................................................... 380
B.2.4 MEMUSAGEMAX, MEMUSAGEMIN, MEMUSAGECUR, and MEMUSAGEAVG...........................................381
B.2.5 MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY.......................................... 381
B.2.6 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR....................................................................................................382
B.2.7 FEC_UNCOR_BLOCK_CNT............................................................................................................................................ 383
B.2.8 IF_BBE, IF_ES, IF_SES, IF_CSES, IF_UAS, and IF_BER............................................................................................ 383
B.2.9 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG.......................................................................................................385
B.2.10 IF_MSE_MAX, IF_MSE_MIN, IF_MSE_AVG, and IF_MSE_CUR........................................................................ 385
B.2.11 MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET................................................................ 386
B.2.12 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and MPLS_PW_UAS........................................................ 387
B.2.13 MPLS_PW_LS_N, MPLS_PW_SLS_N, MPLS_PW_CSLS_N, and MPLS_PW_UAS_N................................... 387
B.2.14 MPLS_TUNNEL_LS, MPLS_TUNNEL_SLS, MPLS_TUNNEL_CSLS, and MPLS_TUNNEL_UAS................388
B.2.15 MPLS_TUNNEL_LS_N, MPLS_TUNNEL_SLS_N, MPLS_TUNNEL_CSLS_N, and MPLS_TUNNEL_UAS_N
......................................................................................................................................................................................................... 389
B.2.16 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR............................................................................................. 389
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xiii

B.2.17 PATEMPMAX, PATEMPMIN, and PATEMPCUR...................................................................................................390

B.2.18 PORT_BER_CNT............................................................................................................................................................. 390
B.2.19 QAM_S_WS16, QAMWS16, QAMWS32, QAMWS64, QPSKWS, QPSK_S_62P5M_WS,
QPSK_S_125M_WS, QPSK_S_250M_WS, QPSK_S_500M_WS, QPSK_S_750M_WS.............................................. 391
B.2.20 RLHTT, RLLTT, TLHTT, and TLLTT.............................................................................................................................392
B.2.21 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG.................................................................................................... 393
B.2.22 TLBMAX, TLBMIN, and TLBCUR.............................................................................................................................. 394
B.2.23 TPLMAX, TPLMIN, and TPLCUR............................................................................................................................... 394
B.
2.24 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,RX_BWUTIL_EXCS_MAX...................................................395
B.2.25 RPLMAX, RPLMIN, and RPLCUR.............................................................................................................................. 397
B.2.26 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG..................................................................................................... 397
C RMON Event Reference..................................................................................................... 399

C.1 RMON Performance Entry List...................................................................................................................................... 399
C.2 RMON Events and Handling Procedures................................................................................................................... 425
C.2.1 ETHDROP........................................................................................................................................................................... 425
C.2.2 ETHFCS............................................................................................................................................................................... 426
C.2.3 ETHFRG.............................................................................................................................................................................. 427
C.2.4 ETHJAB............................................................................................................................................................................... 428
C.2.5 ETHOVER........................................................................................................................................................................... 428
C.2.6 ETHUNDER........................................................................................................................................................................ 429
C.2.7 RXBBAD.............................................................................................................................................................................. 430
D Alarm Suppression Relationship..................................................................................... 432
Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xiv

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

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

1.1 General Safety Precautions

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

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

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

The installation and maintenance personnel of Huawei devices must receive strict
training and be familiar with the proper operation methods and safety precautions
before any operation.
● 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 protection ground (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.
1.2 Warning and Safety Symbols

Before using the equipment, note the following warning and safety symbols on
the equipment.
Table 1-1 lists the warning and safety symbols of the OptiX RTN 380 and their
meanings.
Table 1-1 Warning and safety symbols of the OptiX RTN 380
Label Label Name Description
ESD protection label Indicates that the equipment

is sensitive to static
electricity.
Radiation warning label Indicates that the equipment

generates electromagnetic
radiation.

Label Label Name Description
High temperature warning Indicates that the equipment

label surface temperature may
exceed 70°C when the
ambient temperature is
higher than 55°C. Wear
protective gloves to handle
the equipment.
Grounding label Indicates the grounding

position of a chassis.
1.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.
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.
1.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.
1.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.

1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
1.6.1 Safe Usage of Optical Fibers

The laser beam can cause damage to your eyes. Hence, you must exercise caution
when using optical fibers.
When installing or maintaining optical fibers, avoid direct eye exposure to the
laser beams launched from the optical interface 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 optical
distribution frame (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
1.6.2 Electromagnetic Exposure

This topic describes safety precautions for electromagnetic exposure.
If multiple transmit antennas are installed on a tower or backstay, keep away

from the transmit directions of the antennas when you install or maintain an
antenna locally.

NOTICE
Ensure that all personnel are beyond the transmit direction of a working antenna.
1.6.3 Forbidden Areas

The topic describes requirements for a forbidden area.
● 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.
1.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.
1.6.5 Microwave
When installing and maintaining the equipment of Huawei, follow the safety
precautions of microwave to ensure the safety of the human body and the
equipment.
Strong radio frequency can harm the human body.
When installing or maintaining an aerial on the tower or mast that is installed

with multiple aerials, switch off the transmitter in advance.
1.7 Working at Heights

This topic describes safety precautions for working at heights.
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.
1.7.1 Hoisting Heavy Objects

This topic describes the safety precautions for hoisting heavy objects that you
must follow when installing, operating, and maintaining Huawei devices.

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 1-1.
Figure 1-1 Hoisting heavy objects
1.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 1-2.
When using a ladder, to prevent the ladder from sliding, ensure that the wider feet
of the ladder are downward, or take protection measures for the ladder feet.
Ensure that the ladder is placed securely.
Figure 1-2 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 1-3.

Figure 1-3 Ladder top being one meter higher than the roof
1.8 Mechanical Safety

This topic describes safety precautions for drilling holes, handling sharp objects,
operating fans, and carrying heavy objects.
Drilling Holes
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.
1.9 Other Precautions

This topic describes safety precautions for removing and inserting boards, binding
signal cables, and routing cables.
Removing and Inserting a Board
NOTICE
When inserting a board, wear an ESD wrist strap or ESD gloves, and handle the
board gently to avoid distorting pins on the backplane.
● 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.

Maintenance Guide 2 Routine Maintenance Items
2 Routine Maintenance Items
Routine maintenance operations are performed to detect and rectify hidden faults
before the hidden faults cause damage to equipment and affect services.
Routine Maintenance Items Carried Out on the NMS
Table 2-1 Routine maintenance items carried out on the NMS

Maintenance Item Recomme Remarks
nded
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.
Browsing Current Alarms Every day ● Handle the alarms by referring to A.

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

week historical alarms, you can take
precautions to avoid related faults.

Maintenance Item Recomme Remarks

nded
Maintena
nce Cycle
Browsing History Every ● Gauge type performance events

Performance Events week such as the board temperature and
laser power are stable.
● Bit error type performance events
meet requirements on link
availability.
● Historical received signal levels do
not exceed the fade margin for a
long time.
Testing 1+1 protection Half a Applies only to the equipment that is

Switching year configured in 1+1 protection mode.
NOTE
During the 1+1 protection switching, the
protected services are interrupted. Hence, it
is recommended that you perform the 1+1
protection switching when the traffic is
light.
Field Maintenance Items for Outdoor Equipment
Table 2-2 Field maintenance items for outdoor equipment

Maintenance Item Recommende Remarks
d
Maintenance
Cycle
Checking the appearance of Half a year The OptiX RTN 380 is fixedly
the OptiX RTN 380a. NOTE mounted and its appearance is
Perform a in good condition, without the
complete coating being damaged or
check after a corroded.
level-8 or
Checking the appearance and higher-level The antenna is tightly placed
hurricane, an
azimuth of the antenna. and does not deviate from the
earthquake,
or other designed angle.
unexpected
Checking the appearance of circumstances. The hybrid coupler is fixedly
the hybrid coupler. mounted and its appearance is
in good condition, without the
coating being damaged or
corroded.

Maintenance Item Recommende Remarks

d
Maintenance
Cycle
Checking the appearance and The shield layer of the power

connection of outdoor cables. cable is intact with the
connectors being
waterproofed. The feeder clip
and binding strap are
tightened.
a: 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).
Power on the OptiX RTN 380 within 24 hours of unpacking. During maintenance, the
power-off time of the equipment cannot be longer than 24 hours.

Maintenance Guide 3 Troubleshooting
3 Troubleshooting
This chapter describes the general troubleshooting procedure and methods of

rectifying common faults.
3.1 General Troubleshooting Procedure

Fault symptoms should be recorded in details during troubleshooting. In China,
customers can report problems and get technical support by dialing the 24-hour
hotline 400-830-2118. In other regions, customers should contact the local
representative office of Huawei.
3.2 Troubleshooting Microwave Link Faults
Microwave link faults refer to interruptions or performance deterioration of
microwave links. After microwave link faults occur, an NE reports alarms such as
MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR, or MW_LOF.
3.3 Troubleshooting Ethernet Service Faults
Ethernet service faults refer to Ethernet service interruptions or deterioration.
3.4 Troubleshooting DCN Faults
A data communication network (DCN) fault prevents the network management
system (NMS) from reaching an NE because of failed or unstable communication
between the NMS and the NE.
3.1 General Troubleshooting Procedure

Fault symptoms should be recorded in details during troubleshooting. In China,
customers can report problems and get technical support by dialing the 24-hour
hotline 400-830-2118. In other regions, customers should contact the local
representative office of Huawei.

General Troubleshooting Procedure
Figure 3-1 General troubleshooting procedure
Table 3-1 General troubleshooting procedure

Comment Description
No.
1 Make a true and detailed record of the fault, including the time
when the fault occurred and any operations performed leading up
to and after the occurrence. Collect alarms, performance events,
and other important information.
You can perform one-click data collection using the NCE.

Comment Description
No.
2 For OptiX RTN 380, a common external cause is a power supply

fault. Handle the fault yourself by referring to Table 3-3, or
contact a power engineer.
3 Determine the fault type according to preliminary analysis on

alarms at the network operations center (NOC). Handle different
types of faults as follows:
● If a microwave link is faulty, follow instructions in
Troubleshooting Microwave Link Faults.
● If an Ethernet service is faulty, follow instructions in
Troubleshooting Ethernet Service Faults.
● For faults of other types, handle alarms in descending order of
severities according to A.2 Alarms and Handling Procedures.
● If services are running properly but the NE is unreachable to
the network management system (NMS), follow instructions in
Troubleshooting DCN Faults.
If the faulty NE cannot be managed at the NOC, follow
instructions in Figure 3-2 and Table 3-3 to handle the fault
onsite.
4 To report fault information or obtain technical support, contact

the local Huawei office.
5 After rectifying the fault, perform the following operations:

1. Check for alarms and ensure that the system is running
properly.
2. Arrange personnel to attend to the system during peak service
hours, and promptly address any problems.
3. Fill in the sheet for onsite operations. Send the sheet and fault
symptoms to Huawei. Table 3-2 shows the sheet for onsite
operations.
Table 3-2 Sheet for on-site operations

Maintained on Maintenance Personnel
Actual Step Step in the Handling Result Remarks

Whole Procedure

Onsite Fault Handling Process
Figure 3-2 Onsite fault handling process

Table 3-3 Onsite fault handling process

Comment Description
No.
1 The process is as follows:

1. Check whether the power sourcing equipment indicator status
is correct.
If the power sourcing equipment indicator status is normal, go
to the next step in the onsite fault handling process.
2. Check whether the circuit breaker controlling the power supply
to OptiX RTN 380 on the power sourcing equipment is
disconnected.
If the circuit breaker is automatically disconnected, identify the
cause (such as short circuits or insufficient fuse capacity) and
handle the fault.
3. Check whether the power sourcing equipment is functioning
properly.
2 Check whether the OptiX RTN 380 is damaged, tilt, or wet, and
whether cables are disconnected or broken.
3 It is recommended that you prioritize equipment alarms over link

alarms and prioritize link alarms over other types of alarms.
Equipment alarms mainly include:
● HARD_BAD, POWER_ALM, and TEMP_ALARM
● RADIO_TSL_HIGH and RADIO_TSL_LOW
● ETH_LOS
Microwave link alarms mainly include:
● MW_LOF, MW_LIM, MW_BER_EXC, MW_BER_SD, and
MW_FEC_UNCOR
● RADIO_RSL_HIGH and RADIO_RSL_LOW
● MW_CFG_MISMATCH
Other types of alarms do not cause service interruption and NE
unreachability at the same time. Handle the alarms according to
the alarm reference document.
3.2 Troubleshooting Microwave Link Faults

Microwave link faults refer to interruptions or performance deterioration of
microwave links. After microwave link faults occur, an NE reports alarms such as
MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR, or MW_LOF.
Types of Microwave Link Faults

Microwave link faults are classified into:

● Equipment faults, including OptiX RTN 380 faults, power supply faults,
antenna damage, and cable damage
● Propagation faults, including fading, interference, and poor line of sight (LOS)
● Poor construction quality, including poor component installation, poor
grounding, and poor waterproofing
Figure 3-3 Types of microwave link faults
Fading Symptoms and Causes

Link fading is the main cause for microwave link faults. Locating and handling link
fading is more difficult than locating and handling hardware faults.
Table 3-4 Fading symptoms and causes

Fading Type Symptom Cause
Classified Down The RSL is lower than the RSL in ● Multipath fading
by fading the free space. The difference can ● Duct-type fading
received be tens of decibels.
signal level ● Rain fading
(RSL) Up The RSL is higher than the RSL in ● Interference
fading the free space. The difference can ● Long delay caused by terrain
be 10 decibels to 19 decibels. reflection

Fading Type Symptom Cause
Classified Fast Fast fading lasts from several ● Multipath fading

by fading fading milliseconds to tens of seconds. ● Duct-type fading
duration Generally, fast fading is caused by ● Long delay caused by terrain
multipath fading. It occurs reflection
periodically. For example, fast
fading occurs in the period from
18:00 to 20:00 of a day or in a
certain season of a year.
Slow Slow fading lasts from tens of ● Slow up fading is usually caused
fading seconds to several hours. by interference.
● Slow down fading is usually
caused by rain, and therefore is
also called rain fading. Rain
fading occurs on links that work
at a frequency higher than 10
GHz or in areas where there is
heavy rain.

Troubleshooting Procedure

Figure 3-4 Procedure for troubleshooting a microwave link fault

Table 3-5 Procedure for troubleshooting a microwave link fault

Comm Operation Description
ent
No.
1 Check for Check whether any of the following misoperations has been
misoperations. performed:
● The power supply has been shut down, which prevented the
network management system (NMS) from reaching the local or
remote NE.
● The radio transmitter has been muted, which triggered a
RADIO_MUTE alarm.
● A loopback has been performed on an IF port, which triggered a
LOOP_ALM alarm.
● Microwave link data has been configured incorrectly, which
triggered an MW_CFG_MISMATCH or NB_CFG_MISMATCH alarm.
● An adaptive modulation (AM) self-check has been enabled, which
triggered an MW_AM_TEST alarm.
● A pseudo random binary sequence (PRBS) test has been enabled.
● IF consecutive wave output has been enabled, which triggered an
MW_CONT_WAVE alarm.
If any of the preceding misoperations has been performed, undo it.
2 Check for Check for the following hardware fault alarms:

hardware ● HARD_BAD
alarms.
● RADIO_TSL_HIGH and RADIO_TSL_LOW
When a hardware fault occurs, replace the OptiX RTN 380.
3 Check for IF Check for the following IF and RF alarms:

and RF alarms. ● MW_LIM, MW_LOF, and MW_RDI
● MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR
● RADIO_RSL_HIGH, RADIO_RSL_LOW
● RADIO_RSL_BEYONDTH
● AM_DOWNSHIFT
4 Check the RSL is the major reference for locating and handling propagation
receive power. faults. Follow instruction in Browsing Historical Transmit Power and
Receive Power to browse and analyze the historical RSL values and
the current RSL value.


ent
No.
5 Check whether If the RSL value is greater than the current receiver sensitivity but the
the fault is an microwave link is still interrupted or signals degrade, up fading has
up fading fault. occurred. Generally, co-channel/adjacent-channel interference results
in up fading. To locate frequencies possibly used by interfering sources,
see Scanning Interfering Signals.
● If a third-party RF device is the source of interfere, contact the local
frequency spectrum management department to clear the
interference source.
● If the interference is caused due to improper route planning, modify
the frequency plan to minimize the interference impact.
6 Check whether If the RSL value has been less than the designed value for a long time,
the fault is a the propagation trail is faulty. Perform the following operations:
down fading ● Check whether the tower/pole carrying the antenna meets the anti-
fault. wind requirement. Because OptiX RTN 380 has a small main lobe, a
small antenna adjustment may result in severe down fading. If the
tower/pole carrying an OptiX RTN 380 antenna does not meet the
anti-wind requirement, the microwave link will become faulty.
● Check whether the antenna is misaligned. If the antenna is
misaligned, re-align it.
● Check whether there are any blocks on the radio transmission trail
or in the near field of the antenna. If there are, adjust the
installation height of the antenna to bypass the blocks, or replan
the microwave link route.
● Check whether loss increases because 1the antenna or hybrid
coupler is damaged or wet. If any of these components is damaged
or wet, replace it.


ent
No.
7 Check whether If the fault occurs in poor weather conditions (such as rainy, snowy, or
the fault is a foggy) and is rectified after the conditions clear, the fault cause is rain
rain fading fading. For a fault caused by rain fading, check whether the link
fault. fading margin is insufficient.
1. Calculate the actual link availability using the following formula:
link availability = total fault time/statistical period. In this formula,
the statistical period is generally six months or one year.
● If the actual link availability is lower than the designed value by
an order of magnitude, the link fading margin is insufficient.
Replan the microwave link parameters.
● If the difference between the actual link availability and the
designed value is small, no action is required.
2. Before replanning microwave link parameters, ensure that the rain
zone parameters, the refractivity gradient, and the planning
algorithm are correct. To minimize rain fading impact, you can also:
● Increase the transmit power or replace the antenna with a
larger-diameter antenna, to increase the system gain and the
fading margin.
● Use a frequency band on which rain fading has a smaller
impact.
8 Check whether If the receive power fluctuates greatly and quickly (by more than 10
the fault is a dB or dozens of dB within several seconds or dozens of seconds), fast
fast fading fading has occurred.
fault. Fast fading may occur because of:
● Multipath fading: Faults occur periodically, for example, during the
transition between day and night.
● Duct-type fading: random fast fading
To handle fast fading, perform the following operations:
● Increase the path inclination. That is, adjust the installation heights
of antennas at both ends to increase the height differences.
● Reduce surface reflection. For apparent strong reflection surfaces,
for example, large areas of water, flat lands, and bald mountain
tops, adjust antennas to move reflection points out of the strong
reflection areas or use landforms to mask the reflection.
● Reduce the path clearance. With LOS conditions guaranteed, lower
installation heights of antennas as much as possible.
9 Troubleshoot If the preceding operations do not rectify the fault, replace the
the fault by equipmens at both ends. Then, check whether services recover. If the
replacing fault persists, replan the microwave link parameters, for example,
suspected change the operating frequency, replace antennas with larger-
faulty parts. diameter antennas, change the antenna installation heights, or change
the route.

3.3 Troubleshooting Ethernet Service Faults

Ethernet service faults refer to Ethernet service interruptions or deterioration.
Fault Symptoms
Ethernet services are interrupted, or Ethernet services are not running properly,
resulting in slow Internet surfing, long delay, packet loss, or incorrect received or
transmitted packets.
Table 3-6 Common Ethernet service faults

Symptom Alarm
Ethernet services Hardware alarms such as HARD_BAD, LASER_MOD_ERR,

are interrupted. and TEMP_ALARM
Link alarms such as ETH_EFM_LOOPBACK,

ETH_LINK_DOWN, ETH_LOS, and LOOP_ALM
Service alarms such as ETH_CFM_AIS, ETH_CFM_LOC, and

ETH_NO_FLOW
Ethernet services Hardware alarms such as HARD_BAD and TEMP_ALARM

deteriorate.
Service alarms such as DROPRATIO_OVER, FLOW_OVER,
MAC_EXT_EXC, MAC_FCS_EXC, and PORT_EXC_TRAFFIC
Upstream alarms such as AM_DOWNSHIFT,

MW_BER_EXC, and MW_BER_SD
Fault Causes
● An Ethernet board loopback or a transmission line loopback is performed.
● Parameters such as the port status (enabled or disabled), working mode, and
flow control are inconsistently configured for the local and peer Ethernet
ports.
● Service configurations are incorrect.
● The local equipment is faulty.
● A link fault or bit errors occur.
● The Ethernet service bandwidth decreases because of an adaptive modulation
(AM) downshift.
● The interconnected equipment is faulty.
● The network cable is faulty.
● External electromagnetic interference is severe.

Figure 3-5 Procedure for troubleshooting an Ethernet service fault

Table 3-7 Procedure for troubleshooting an Ethernet service fault

ent
No.
1 Check for Check whether any of the following misoperations has been
misoperations. performed:
● A loopback has been configured for the Ethernet port.
● A loopback has been configured for the transmission line.
● Parameters such as the port status (enabled or disabled), working
mode, and flow control have been set inconsistently for the local
and peer Ethernet ports.
● The Ethernet protocol or Ethernet services (especially Ethernet port
attributes) have been configured incorrectly.
If any of the preceding misoperations has been performed, undo the
operation.
2 Check for Check for the following equipment alarms:

equipment ● HARD_BAD, POWER_ALM, and TEMP_ALARM
alarms and
microwave link ● LASER_MOD_ERR
alarms. Check for the following microwave link alarms:
● MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR, MW_LIM,
MW_LOF, and MW_RDI
● RADIO_RSL_HIGH, RADIO_RSL_LOW, RADIO_TSL_HIGH,
RADIO_TSL_LOW
● AM_DOWNSHIFT
3 Check for Check for the following Ethernet alarms:

Ethernet alarms ● ETH_LINK_DOWN, ETH_LOS, LAG_DOWN, LAG_MEMBER_DOWN
● ETH_NO_FLOW, FLOW_OVER
● DROPRATIO_OVER, MAC_EXT_EXC, MAC_FCS_EXC,
PORT_EXC_TRAFFIC
4 Perform Take measures based on the diagnostic results by following

intelligent fault instructions provided in Troubleshooting Ethernet Services Using the
diagnosis. Smart Fault Diagnosis Function.
5 Check for Check whether E-LAN service loops are formed by referring to E-LAN
Ethernet local Service Loopback Detection.
area network ● If E-LAN service loops are formed, modify configurations to
(E-LAN) service eliminate the loops.
loops.
● If physical E-LAN service loops are necessary for service protection,
eliminate logical loops by configuring Ethernet ring protection
switching (ERPS) or split horizon groups.


ent
No.
6 Analyze service Query the Ethernet traffic, bandwidth, or bandwidth utilization of

traffic. the Ethernet port. Diagnose the fault by analyzing the traffic rate at
the Ethernet port.
● If the receive rate at the Ethernet port is out of the specified range,
the interconnected equipment is faulty.
● If the transmit rate at the Integrated IP radio port is close to or
equal to the service bandwidth supported by the current IF working
mode, the service bandwidth of the microwave link is insufficient.
Contact network planning personnel to replan the service
bandwidth for the microwave link. If the replanned service
bandwidth exceeds the limit specified by the license, apply to
Huawei for a license that allows higher service bandwidth.
● If the traffic at the ingress port is markedly different from that at
the egress port (for an OptiX RTN 380, the ingress port is usually
an Ethernet port and the egress port is usually an Integrated IP
radio port), check whether the service and quality of service (QoS)
configurations are proper.
● If the transmitted traffic is equal to the received traffic, query the
traffic of each VLAN service on the same port to check whether
bandwidth preemption occurs.
3.4 Troubleshooting DCN Faults

A data communication network (DCN) fault prevents the network management
system (NMS) from reaching an NE because of failed or unstable communication
between the NMS and the NE.
Fault Symptoms and Causes
Table 3-8 Fault symptoms and causes
Symptom Possible Cause
NEs that receive network ● Cause 1: Services are interrupted.

management messages ● Cause 2: DCN parameters are incorrectly set.
through service ports
(such as air interfaces ● Cause 3: System control units are faulty.
and Ethernet ports) are
unreachable to the NMS.
NEs that receive network ● Cause 1: Network cables are disconnected or

management messages damaged.
through NMS ports are ● Cause 2: DCN parameters are incorrectly set.
unreachable to the NMS.
● Cause 3: System control units are faulty.

Symptom Possible Cause
A few NEs are ● Cause 1: DCN parameters are incorrectly set.

unreachable to the NMS ● Cause 2: An NE ID or NE IP address conflict
or their connections to occurs on the DCN subnet.
the NMS are unstable.
● Cause 3: The DCN subnet is oversized.
● Cause 4: System control units are faulty.
Figure 3-6 Procedure for troubleshooting a DCN fault

Table 3-9 Procedure for troubleshooting a DCN fault

Com Operation
ment Symptom and
No. Analysis Measures
1 Locate the Locate the faulty NE ● If the faulty NE has a service fault, rectify
faulty NE. based on the DCN the service fault first.
networking diagram. ● If an unreachable NE is connected to the
● If all NEs within an NMS through an external DCN, verify that
area are the external DCN equipment or the cable
unreachable to the used for DCN connection is working
NMS, the correctly.
unreachable NE
closest to a
reachable NE is
probably the faulty
NE.
● If only one NE is
unreachable to the
NMS, that NE is the
faulty NE.
2 Handle ● The faulty NE ● Handle the hardware alarms by referring to

hardware reports hardware A Alarm Reference.
faults. alarms such as ● Reconnect or replace the network cable or
HARD_BAD. optical fiber.
● The NMS port on
the faulty NE is
incorrectly
connected, or the
network cable of
the faulty NE is
damaged.
3 Modify The faulty NE reports Handle the alarms by referring to

configurations an NEIP_CONFUSION NEIP_CONFUSION and
. or SUBNET_RT_CONFLICT.
SUBNET_RT_CONFLIC
T alarm or both.
4 Decrease the The faulty NE reports Handle the alarms by referring to

number of a DCNSIZE_OVER or DCNSIZE_OVER or DCNLINK_OVER.
NEs on the DCNLINK_OVER
DCN subnet. alarm.

Com Operation
ment Symptom and
No. Analysis Measures
5 Troubleshoot Some NEs may ● Verify that a minimum of 512 kbit/s

network occasionally become bandwidth is allocated to the inband DCN. If
management unreachable to the the allocated bandwidth is lower than 512
information NMS. kbit/s, packets from the NMS may be lost.
loss. ● Check whether the quality of service (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. If the QoS priority allocated
to the inband DCN is low, NEs may be
unreachable to the NMS because of packet
loss caused by congestion. The per-hop
behavior (PHB) priority of inband DCN
packets must not be lower than expedited
forwarding (EF).
6 Troubleshoot ● Logging in to the ● Search for the IP address of the faulty NE on

no-response NE from the NMS the NMS.
problems. on the site fails. ● If the IP address is not found, or if the IP
● The NE does not address is found but the NMS still cannot
respond to any reach the faulty NE, power off and then
commands. restart the OptiX RTN 380 in an authorized
maintenance window in which services can
be interrupted.

Maintenance Guide 4 Part Replacement
4 Part Replacement
Part replacement is a method frequently used to locate faults. The replacement

operation varies according to the specific part type.
4.1 Replacing an OptiX RTN 380

When an OptiX RTN 380 is being replaced, services on it are interrupted.
4.2 Replacing an SFP Module
When a small form pluggable (SFP) module at a port is being replaced,
unprotected services on the port are interrupted.
4.1 Replacing an OptiX RTN 380

When an OptiX RTN 380 is being replaced, services on it are interrupted.
Prerequisites
● You are aware of the impact of replacing an OptiX RTN 380.
● The spare OptiX RTN 380 is at hand, whose model is the same as that of the
OptiX RTN 380 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.
● You can back up and recover NE data by using a USB flash drive onsite if the
following conditions are met.
– The USB access control function of the NE has been enabled.
– The RTN.CER file of the new NE has been copied to the root directory of
the USB flash drive.
A 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.

Tools, Equipment, and Materials

● Wrench (Adjustable wrench, Hex key)
● Silicon
● Waterproof tape
● USB flash drive
The USB flash drive must be compatible with the OptiX RTN 380 and have a
capacity no less than 4 GB.
Folders related to the NE (\pkg, \patch, \sysdata, \db, \script, and \license)
must not exist.
● Web LCT
Precautions
● If OptiX RTN 380s are installed on a hybrid coupler, power off only the OptiX
RTN 380 to be replaced, but do not power off or mute the other OptiX RTN
380. This can prevent services from being affected. The port of the hybrid
coupler ejects little microwave radiation, meeting the safety standards for
microwave radiation.
● Do not damage the paint of the OptiX RTN 380 during the replacement. If the
paint is damaged, repaint the damaged areas.
● Power on the OptiX RTN 380 within 24 hours of unpacking. During
maintenance, the power-off time of the equipment cannot be longer than 24
hours.
Procedure
Step 1 Ensure that the model of the spare OptiX RTN 380 is the same as that of the
OptiX RTN 380 to be replaced.
Step 2 Optional: If the NE is running, back up the NE data to the USB flash drive.
1. Enable USB Access by Web LCT
a. Select the NE from the object tree in the NE Explorer, and choose
Communication > Access Control from the function tree.
b. Select the USB Access Control tab page.
c. Set the USB access status to Enabled.
2. Insert the blank USB flash drive into the USB port on the OptiX RTN 380.
The indicator beside the USB port is blinking green during the data backup.
The backup may last for about 12 minutes based on the content to be backed
up. The indicator will be steady green after the data backup is complete.
3. Remove the USB flash disk after the data backup is complete.
After the data backup is complete, new RTN.CER and RTNEXTRA.CER files are
generated in the USB flash drive. Both default users names and their corresponding
passwords (u: szhw/p: nesoft) and (u: szhw/p: Changeme_123) are saved in the files
RTN.CER and RTNEXTRA.CER respectively. After being connected to a spare part (the
NE data and password for a spare part are not modified), the USB flash disk can pass
authentication so the spare part can restore NE data from the USB flash disk.

Step 3 Power off the OptiX RTN 380.

● If power is supplied to the OptiX RTN 380 by the power injector (PI), switch
off the circuit breaker, on the power cabinet, connected to the PI.
Step 4 Remove the faulty OptiX RTN 380.

1. Remove all the cables connected to the OptiX RTN 380.
2. Loosen the four captive screws in a diagonal sequence, and remove the OptiX
RTN 380 from the antenna or coupler.
Step 5 Install the spare OptiX RTN 380 by following instructions in the OptiX RTN 380
Quick Installation Guide. The main steps are as follows:
1. Mount the OptiX RTN 380 on the antenna or coupler.
2. Tighten the four captive screws in a diagonal sequence.
3. Connect cables to the OptiX RTN 380 and waterproof them.
Step 6 Switch on the circuit breaker on the power cabinet of the OptiX RTN 380.
The system indicator on OptiX RTN 380 is blinking green when the OptiX RTN 380
is being powered on and started, and is blinking red after the OptiX RTN 380 is
started.
Step 7 Restore the NE data according to the onsite situations.

● If you have performed Step 2 to back up the NE data on the USB flash disk,
restore the NE data using the backup data.
a. Insert the USB flash disk with the NE data backup into the USB port on
the OptiX RTN 380.
The indicator beside the USB port is blinking green during the data
restoration The restoration may last for 2 to 12 minutes based on the
content to be restored. The indicator will be steady green after the data is
restored.
b. After the data is restored, remove the USB flash drive.
If a patch has been installed on the OptiX RTN 380 to be replaced and a USB flash drive
will be used to restore NE data, software version of the spare device should be the same as
that of the device to be replaced. If the spare device and the device to be replaced have
different software versions, restore software package data before restoring patch package
data.
● If you have no NE data backup on the USB flash disk.
a. See Changing an NE ID and Setting NE Communication Parameters to
modify the NE ID and IP.
b. If there is a backup file in the NMS, restore the NE database using the
backup file.
● If there is no backup file, re-configure the NE data by referring to the
Commissioning Guide and network plan document.
Step 8 Query the current alarms on the NE. Ensure that the faults disappear and no
alarm is generated after the replacement.
----End

4.2 Replacing an SFP Module

When a small form pluggable (SFP) module at a port is being replaced,
unprotected services on the port are interrupted.
Prerequisites
● You are aware of the impact of replacing an SFP module.
● You are aware of the position of the SFP module to be replaced.
● You are aware of whether protection has been configured for services on the
SFP module to be replaced. If no protection is configured, the services will be
interrupted during the replacement.
● A spare SFP module with the same version and model as the SFP module to
be replaced is available. To obtain information about the SFP module to be
replaced, query the board manufacturing information.

● ESD wrist strap
● NCE
Precautions
When handling optical fibers, do not stand close to, or look into the optical fiber
outlet directly without eye protection.
Procedure
Step 1 Remove the cables connected to the SFP module.
Step 2 Remove the SFP module.
Step 3 Ensure that the model of the spare SFP module is the same as that of the SFP
module to be replaced.
Step 4 Insert the spare SFP module.
Step 5 Connect cables to the SFP module.
Step 6 Take anti-corrosion measures for the port by following instructions provided in the
installation reference of the Quick Installation Guide.

Step 7 Query the current alarms.

Alarms on the SFP module have been cleared.
----End

Maintenance Guide 5 Database Backup and Restoration
5 Database Backup and Restoration
The OptiX RTN 380 supports database backup and restoration through the NMS.
5.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.
5.2 Backing Up the Database Manually
NE configuration data is stored in the database of an NE. To prevent the database
from being damaged due to hardware faults or potentially service-affecting
operations such as upgrading software, you need to manually back up the
database periodically and before these operations.
5.3 Backing Up the Database Periodically
This section describes how to enable periodical backup of the database by
configuring the database backup policy.
5.4 Restoring the Database by NMS
If the database is damaged, you can restore the NE database by using the
database file that is saved previously.
5.5 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.
5.6 Restoring Databases from a USB Flash Drive
If NE data is lost or becomes abnormal and NE DCN communication fails, you can
restore NE databases from a USB flash drive.
5.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.

NE Database Type
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
After NE configuration data is delivered to the system control unit, the data is
initially stored in the MDB. If the data is successfully verified, the system control
unit copies the data from the MDB to DRDB and delivers the data to other units.
Two modes are available to back up DRDB data to the FDB:
When DRDB data is being backed up to the FDB, do not recover or backup NE data by USB flash
drive.
● An NE backs up DRDB data to the FDB within five minutes after NE
configuration data is modified.
● An NE backs up DRDB data to the FDB every 24 hours.
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.
● If a USB flash drive is connected to the USB port and all folders related to the
NE do not exist, the NE backs up FDB data from flash memory to \db in the
USB flash drive.
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 corrupted, data can be restored
from the dedicated partition of the flash memory.
● If a USB flash drive is connected to the USB port and the database folder
(\db) contains data, the NE backs up NE database from the USB flash drive to
a dedicated directory in the flash memory.
● When the databases of an NE are damaged, you can restore the databases
manually for the NE on the NMS or its opposite NE.
During the database recovering by the NMS, do not recover or back up data using a USB flash
drive.
When you restore databases for an NE from its opposite NE, not only the NE's databases but
also the NE's system parameter settings including the NE ID and NE IP are restored.
5.2 Backing Up the Database Manually

NE configuration data is stored in the database of an NE. To prevent the database
from being damaged due to hardware faults or potentially service-affecting
operations such as upgrading software, you need to manually back up the
database periodically and before these operations.
Prerequisites
● You must be an NM user with NE administrator authority or higher.
● You have logged in to the NE.

NCE
The Web LCT does not support this operation.
Precautions
During the database backup by the NMS, do not recover or backup data by USB flash drive.
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 Select the NE whose database needs to be backed up, and click Backup.
By holding down Ctrl, you can select multiple NEs to back up their data at one time.
Step 5 Set the data backup path to OSS Server or OSS Client according to the
requirements.
If NMS Client is selected, you can click to set the path in which the client data is
stored.
----End
5.3 Backing Up the Database Periodically

This section describes how to enable periodical backup of the database by
configuring the database backup policy.
5.3.1 Setting the User-Defined Backup Policy

Through this task, you can set the backup policy for a specific NE.
Prerequisites
● You must log in to the NE.

NCE
Background Information
Each NE has a default data backup policy.
● Database packages are backed up once at 22:00.

● The default backup policy is enabled by default.
● A maximum of five database packages can be backed up at a time.
● 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
5.3.2 Executing 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
5.3.3 Suspending 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

Step 3 Right-click the selected NE. Click Disable Backup Policy.
----End
5.4 Restoring the Database by NMS

If the database is damaged, you can restore the NE database by using the
database file that is saved previously.

Prerequisites
● NE data has been backed up.
● You have logged in to the NE.

NCE
Precautions
NOTICE
Exercise caution when activating the database because this operation may
interrupt services.
Activate the database within 5 minutes after the NE data is restored. Otherwise,
the database automatically rolls back.
Ensure that the database file used for backing up the database is correct.
Otherwise, services will be interrupted.
During the database recovering by the NMS, do not recover or backup data by USB flash drive.
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 Changme_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 Select Apply in Deliver To Board Activate.

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.
If the NE transmits data services, select Deliver to Board.

Services are interrupted during the activation of databases.
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
5.5 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
You must be an NM user with NE operator authority or higher.
A microwave link between the NE and its peer NE has been configured, and the
DCN channel has been set up.

NCE
Web LCT also supports this operation and the steps are the same as those on the NCE.
Precautions
If the NE is configured with 1+1 protection, you cannot restore the database of the
NE from its peer NE.
Procedure
Step 1 Restore databases for the NE from its peer NE.

Step 2 Check the execution results.
The execution results are displayed on the Database Restoration from Peer page. You can
click Events Logs to view them.
----End
5.6 Restoring Databases from a USB Flash Drive

If NE data is lost or becomes abnormal and NE DCN communication fails, you can
restore NE databases from a USB flash drive.
Prerequisites
● The data has been backed up to the NCE side.

● NCE
● USB flash drive
Procedure
Step 1 On your PC, create a folder usbfile and a subfolder db under it.

Step 2 Copy db_pck.gz and dbf.pkg from the NCE to the directory db under usbfile.
Step 3 Generate an authentication file and copy it to the usbfile directory.

1. Use the NMS-specific tool to generate an authentication file. For details, see
Running the USB File Generation Tool and Generating the USB Authentication
File RTN.CER.
2. Copy the generated RTN.CER file to the usbfile directory.
Step 4 Optional: Use the NMS-specific tool to harden safety of the database and
authentication files. For details, see Safety Hardening.
This step is mandatory when the NE is in incompatible mode.

By default, the NE is in incompatible mode.
Step 5 Copy files to a USB flash drive.
If the NE Is in... Then...
Incompatible mode Copy the hardening files generated in

Step 4 to the root directory of the USB
flash drive.
Compatible mode Copy the files in usbfile to the root

directory of the USB flash drive.
Step 6 Insert the USB flash drive to the USB port on the OptiX RTN 380.
During the database restoration process, do not perform operations such as data
configuration, NE resets, and software loading.
Step 7 Check the data-loading status based on the USB indicator.

Status of the USB Data-Loading Status Operation

Indicator
The indicator blinks NE databases are Remove the USB flash

green, goes off, blinks successfully restored. drive.
green, and turns steady
green.
The indicator turns off The USB flash drive fails 1. Reseat the USB flash
after the USB flash drive to go online due to a drive and check
is inserted. fault or poor contact. whether the indicator
is normal.
The indicator blinks red. The USB flash drive
model is incorrect, a 2. If the exception
read/write error occurs in persists, copy the NE
the USB flash drive, or databases to another
database restoration USB flash drive, and
fails. perform Step 6 to
restore NE databases.
NOTE
For the USB flash drive
models supported by an
OptiX RTN 380, see the
Product Description.
----End

Maintenance Guide 6 Monitoring a Network
6 Monitoring a Network
This section provides hyperlinks to operations of monitoring a network.
Context
The following operations are performed on the NCE.
6.1 Browsing Alarms and Performance Data

This section provides hyperlinks to operations of browsing alarms and
performance data.
6.2 Browsing Performance Data of a Microwave link
This section provides hyperlinks to operations of browsing performance data of a
microwave link.
6.3 Browsing Ethernet Performance Data
This section provides hyperlinks to operations of browsing Ethernet performance
data.
6.4 Monitoring Ethernet Traffic Volumes at Ports
This section provides hyperlinks to operations of monitoring Ethernet traffic
volumes at Ethernet ports and microwave ports.
6.5 Monitoring Entire-Network Performance in a Long Term
The NCE uses the performance management system (PMS) to manage all types of
performance monitoring tasks performed on Huawei equipment in a long term.
6.6 Querying a Report
You can obtain the version, manufacture, and microwave link information of all
the boards by querying the corresponding report.
6.7 Setting Alarm and Performance Management Functions
The OptiX RTN 380 supports various alarm and performance management
functions.
6.1 Browsing Alarms and Performance Data

This section provides hyperlinks to operations of browsing alarms and
performance data.

6.1.1 Browsing Current Alarms

You can find the faults that occur on the equipment by browsing current alarms.
Prerequisites
You must be an NM user with NE monitor 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 current alarm window.
Step 2 Specify filter conditions.

Step 3 View alarm information.
Step 4 Notify the troubleshooting personnel to clear the alarms in time.

For the details, see A.2 Alarms and Handling Procedures.
Complete the following steps to browse current alarms from the Web LCT:
1. Select the NE from the NE Explorer and click in the tool bar.
2. The Browse Current Alarms tab page is displayed by default.
----End
Related Information
A current alarm refers to an alarm that is not cleared.
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
● Light blue: warning
● Blue: event
6.1.2 Browsing History 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

NCE
Procedure
Step 1 Open the historical alarm window.


Step 3 View alarm information.
Complete the following steps to browse historical alarms from the Web LCT:
Select the NE from the NE Explorer and click in the tool bar.
Click the Browse Historical alarms tab.
----End
6.1.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 6.7.1 Configuring the
Performance Monitoring Status of NEs.

● You must be an NM user with NE monitor authority or higher.

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

Complete the following steps to query current performance events from the Web LCT:
Select the board in the NE Explorer and choose Performance > Current Performance from the
Function Tree.
----End
6.1.4 Browsing History 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 6.7.1 Configuring the
Performance Monitoring Status of NEs.
● You must be an NM user with NE monitor authority or higher.

NCE
Procedure
Step 1 Open the performance data window.

Step 2 View historical performance data.
Complete the following steps to query historical performance events from the Web LCT:
Select the board in the NE Explorer and choose Performance > Historical Performance from
the Function Tree.
----End
6.1.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 Web
LCT:
Select the board in the NE explorer and choose Performance > Threshold-Crossing Record
from the Function Tree.
----End
6.2 Browsing Performance Data of a Microwave link

This section provides hyperlinks to operations of browsing performance data of a
microwave link.

6.2.1 Browsing Historical Transmit Power and Receive Power

This section describes how to query the change trend of historical transmit power
and receive power, which serves as a reference for microwave link troubleshooting.
Prerequisites

NCE
Procedure
Step 1 Browse historical transmits power or receive power.
----End
6.2.2 Querying the SNR of a Microwave Link

This section describes how to query the change trend of the signal-to-noise ratio
(SNR) value of a microwave link, which serves as a reference for troubleshooting
microwave link faults.
Prerequisites

NCE

Procedure
Step 1 Query the SNR of a microwave link.
----End
6.2.3 Browsing Current Performance Events of a Microwave

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.
You can view current performance of a microwave link on the Web LCT by performing the
following:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave
Link Performance from the Function Tree. Then select the Current Performance tab.
----End
6.2.4 Browsing Historical Performance Data of a Microwave

link
You can learn about the operating status of a microwave 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.
You can view historical performance of a microwave link on the Web LCT by performing the
following:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave
Link Performance from the Function Tree. Then select the History Performance tab.
----End
6.3 Browsing Ethernet Performance Data

This section provides hyperlinks to operations of browsing Ethernet performance
data.
6.3.1 Browsing Current Performance Events of Ethernet

After you configure a remote network monitoring (RMON) statistics group for a
port, you can browse the real-time statistical performance data of the port.
Prerequisites

NCE

Procedure
Step 1 Query current Ethernet performance.
----End
6.3.2 Setting the Ethernet Performance Threshold-Crossing

Parameter
After you configure a remote network monitoring (RMON) alarm group for a port,
you can monitor whether the performance value of the port crosses the
configured thresholds in the long term.
Prerequisites

NCE
Procedure
Step 1 Set the Ethernet performance threshold-crossing parameter.

----End
6.3.3 Configuring the Parameters for Ethernet Historical

Performance Monitoring
When configuring a historical control group for an Ethernet port, you can
configure how the historical performance data of the port is monitored. The
Ethernet board monitors the historical performance data of each port at the
default sampling interval of 30 minutes. A maximum of 50 historical performance
entries can be saved.
Prerequisites

NCE
Procedure
Step 1 Configure the parameters for Ethernet historical performance monitoring.
----End

6.3.4 Browsing Ethernet Historical Performance Data

After you configure a remote network monitoring (RMON) historical group for a
port, you can browse the historical performance data of the port.
Prerequisites
● You must be an NM user with NE operator authority or higher.
● Parameters for Ethernet historical performance monitoring have been
configured.

NCE
Procedure
Step 1 Query historical Ethernet performance.
----End
6.4 Monitoring Ethernet Traffic Volumes at Ports

This section provides hyperlinks to operations of monitoring Ethernet traffic
volumes at Ethernet ports and microwave ports.
6.4.1 Enabling Flow Monitoring, Physical Bandwidth

Monitoring, and Bandwidth Usage Monitoring for Ports
To check how the traffic volume, physical bandwidth, or bandwidth usage at an
Ethernet port or a microwave port changes within a certain period, you need to
enable the monitoring for the object before that period starts.
Prerequisites
You must be an NM user with NE maintainer authority or higher.

Tools, Instruments, and Materials

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.
Procedure
Step 1 Enable flow monitoring, physical bandwidth monitoring, and bandwidth usage
monitoring for ports.
----End
6.4.2 Querying the Traffic Volume, Physical Bandwidth, and

Bandwidth Usage of a Port
This section describes how to query the change of the traffic volume, physical
bandwidth, or bandwidth usage at an Ethernet port or a Microwave Port within a
certain period.
Prerequisites
The flow monitoring function is enabled on the port. To enable the flow
monitoring function on a port, see 6.4.1 Enabling Flow Monitoring, Physical
Bandwidth Monitoring, and Bandwidth Usage Monitoring for 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.
Procedure
Step 1 Query the traffic volume, physical bandwidth, and bandwidth usage of a port.
----End
6.5 Monitoring Entire-Network Performance in a Long

Term
The NCE uses the performance management system (PMS) to manage all types of
performance monitoring tasks performed on Huawei equipment in a long term.
6.5.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

NCE
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
● Create a data monitoring template.

● Create an RMON TCA monitoring template.
----End
6.5.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 380, 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
6.5.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
6.5.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
6.6 Querying a Report

You can obtain the version, manufacture, and microwave link information of all
the boards by querying the corresponding report.
6.6.1 Querying the Board Information Report

You can obtain the 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 Web LCT:
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
6.6.2 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
Web LCT:
Select the NE from in the NE Explorer and choose Report > Board Details Information Report
from the Function Tree.
Manufacturing information of all boards is displayed in Board Details Information Report.
----End
6.6.3 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

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

6.7 Setting Alarm and Performance Management

Functions
The OptiX RTN 380 supports various alarm and performance management
functions.
6.7.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
Procedure
Step 1 Set the performance monitoring status for the NE.
----End
6.7.2 Suppressing Alarms

This section describes how to suppress specific alarms.
Prerequisites


NCE
Procedure
Step 1 Set alarm suppression.
----End
6.7.3 Reversing Alarms for Ports

This section describes how to reverse alarms for ports.
Prerequisites

NCE
Context
For OptiX RTN 380, only MW_LOF and ETH_LOS alarms support alarm reversion.
● Auto restore mode
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 mode
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.
Procedure
Step 1 Set the alarm reversion mode.
Step 2 Enable alarm reversion for a port.
----End
6.7.4 Setting Bit Error Thresholds for Microwave Ports

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

NCE

Procedure
Step 1 Set bit error thresholds for a microwave port.
The value of Microwave Link Excessive Errors is the threshold for reporting the MW_BER_EXC
alarm.
The value of Microwave Link Signal Degraded is the threshold for reporting the MW_BER_SD
alarm.
----End
6.7.5 Setting Monitoring and Auto-Report Status of

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

NCE
Procedure
Step 1 Set performance monitoring and the auto-report status.

----End
6.7.6 Setting Performance Thresholds

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

NCE
Procedure
Step 1 Set the performance event threshold.
----End

6.7.7 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 1 Reset the performance register.
----End

Maintenance Guide 7 Common Maintenance Operations
7 Common Maintenance Operations
This chapter describes the common maintenance operations.
7.1 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.
7.2 Resetting an NE
Reset, including cold reset and warm reset, is an important measure to rectify
software faults.
7.3 Common Operations for Handling Microwave Link Faults
This section provides links to the common operations for handling microwave link
faults.
7.4 Common Operations for Handling Ethernet Service Faults
faults.
7.5 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 RF 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.
7.6 Querying Power Consumption of NE
This section describes how to query power consumption of NE.
7.7 Enabling the Power-Saving Mode for an NE
This section describes how to enable the power-saving mode for an NE. NEs adopt
the power-saving mode by default.
7.8 Enabling Automatic Fault Recovery
With automatic fault recovery enabled for an NE, the NE automatically restarts
after the fault recovery time expires if both microwave links and DCN links
connected to the NE are interrupted.
7.9 Querying Site Information
You can query microwave site information.

7.10 Querying the Microwave Link Information Report

7.11 Querying Optical Power and Alarm Thresholds of Optical Ports
This section describes how to query the RX/TX optical power and alarm thresholds
of optical ports.
7.1 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.
7.1.1 Setting Port Loopbacks for NEs

This section describes how to set the loopback for each service port on an NE.
Prerequisites

NCE
Context
● The IF port inloop is a process wherein the IF signals are looped back at the
modem unit towards the MUX unit.
● The composite port inloop is a process wherein the microwave baseband
signal is looped back at the MUX/DEMUX unit towards the Ethernet switching
unit.
● The composite outloop is a process wherein the microwave baseband signal is
looped back at the MUX/DEMUX unit towards the modem unit.
● A MAC-layer inloop is an inloop where the Ethernet switching unit loops back
the Ethernet physical signals towards the baseband processing unit at the
MAC layer.
● A PHY-layer inloop is an inloop where the Ethernet access unit loops back the
Ethernet frame signals towards the baseband processing unit at the PHY layer.
● A CPRI port inloop is an inloop where the CPRI port loops back the CPRI
service signals towards the air interface.
● A CPRI port outloop is an outloop where the CPRI port loops back the CPRI
service signals towards the external device.

Precautions
NOTICE
● A loopback operation results in service interruption.

● A software loopback may be released automatically after a certain period (five
minutes, by defaults). For details, see 7.5 Setting the Automatic Release
Function.
Procedure
● Set the port loopback for the NE.
● Set the CPRI port loopback.
----End

7.1.2 Setting the Loopback on a Microwave Link

OptiX RTN 380 supports the setting of loopback on each loopback point of a hop
of microwave link.
Prerequisites

NCE
Precautions
NOTICE
● A loopback operation interrupts the services on the port or in the path where
the loopback is conducted.
● A software loopback may be automatically released within a period (five
minutes by default). For details, see 7.5 Setting the Automatic Release
Function.
Procedure
Step 1 Set the loopback on a microwave link.
----End

7.2 Resetting an NE
Reset, including cold reset and warm reset, is an important measure to rectify
software faults.
Prerequisites

NCE
Precautions
● During a cold reset, services are interrupted. The NE configuration data
modified within five minutes after a cold reset may be lost.
● During a warm reset, services are not interrupted.
Procedure
● Set a cold reset of an NE.
● Set a warm reset of an NE.

----End
7.3 Common Operations for Handling Microwave Link

Faults
faults.
7.3.1 Monitoring Microwave link Indicators

This section describes how to collect high-density samples about the RSL and MSE
indicators of microwave 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 microwave
links.
Step 2 Configure parameters for monitoring the RSL and MSE indicators of microwave
links.
Step 3 Query the monitoring result.

----End
7.3.2 Scanning Interfering Signals

This section describes how to check whether interference exists by scanning
frequency spectrums in microwave channels.
Prerequisites
● You must be an NM user with NE maintainer authority or higher.

● If the OptiX RTN 380 is configured with 1+1 protection switching, lock 1+1
protection switching before scanning interfering signals. After the scanning is
completed, unlock 1+1 protection switching.

NCE
Precautions
Services are interrupted during the scanning.
Procedure
Step 1 Optional: If the OptiX RTN 380 is configured with 1+1 protection switching, lock
1+1 protection switching.

Step 2 Scan interfering signals.
The difference between the specified scanning range and the frequency range in the scanning
result is equal to TR spacing. If the receive power on the working channel is greater than
-81dBm, interfering signals exist on the channel.
Step 3 Check information about available frequency bands and interference.
Step 4 Optional: Unlock 1+1 protection switching.

----End

7.3.3 Muting/Unmuting an NE
The transmit status of an OptiX RTN 380 includes: mute and unmute. In umute
status, the OptiX RTN 380 transmits and receives microwave signals. In mute
status, the OptiX RTN 380 only receives signals, and the transmitter does not
work.
Prerequisites

NCE
Procedure
Step 1 Mute or unmute an NE.
----End
7.3.4 Performing a PRBS Test at an Air Interface

OptiX RTN 380 supports PRBS tests at air interfaces. Therefore, you can send a
pseudo random binary sequence (PRBS) to a microwave port.
Prerequisites
● An outloop at a composite port has been configured on the peer NE.


NCE
Precautions
Figure 7-1 PRBS test on the OptiX RTN 380
NOTICE
During the PRBS test, the services in the tested path are interrupted.
Procedure
Step 1 Configure a PRBS test to be carried out on an air interface.
----End

7.3.5 Enabling the Consecutive Wave Detection Function

The consecutive wave detection function is used to check whether the transmit
frequency deviates.
Prerequisites

NCE
Procedure
Step 1 Set detection of consecutive waves.
----End
7.3.6 Microwave 1+1 Protection Switching

You can perform external switching on the microwave 1+1 protection by
performing microwave 1+1 protection switching.
Prerequisites
● Microwave 1+1 protection has been configured.
Tools, Instruments and Materials

NCE

Procedure
Step 1 Perform microwave 1+1 protection switching.
----End
7.3.7 Querying the AM Status

This section describes how to query the adaptive modulation (AM) scheme
changes and the Ethernet bandwidth in the current modulation scheme.
Prerequisites

NCE
Context
The following procedure queries the AM scheme and the Ethernet bandwidth in
the current modulation scheme.
Procedure
Step 1 Query the AM status.

----End
7.3.8 Querying ATPC Adjustment Records

This section describes how to query automatic transmit power control (ATPC)
adjustment records.
Prerequisites

NCE
Procedure
Step 1 Query ATPC adjustment records.
----End

7.4 Common Operations for Handling Ethernet Service

Faults
faults.
7.4.1 Querying the Attributes of an Ethernet Port

This section describes how to learn about Ethernet service flow rates and physical
parameters of Ethernet ports.
Prerequisites

NCE
Procedure
Step 1 Query the attributes of an Ethernet port.
----End
7.4.2 Using IP Ping Commands to Locate Ethernet Service

Faults
The OptiX RTN 380 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 OptiX RTN 380 is faulty.
Near-end IP ping can be initiated from the CE device to a UNI on the near-
end OptiX RTN 380, or from a UNI on the OptiX RTN 380 to the near-end CE
device. For example, the RNC initiates IP ping packets to the UNI port on NE1,
as shown in Figure 7-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 OptiX RTN 380 is faulty. Far-end IP ping
can be initiated from the CE device to a UNI on the far-end OptiX RTN 380, or
from a UNI on the OptiX RTN 380 to the far-end CE device. For example, the
RNC initiates IP ping packets to the UNI port on NE2, as shown in Figure 7-2.
Figure 7-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.

● 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 7-3 shows the test procedure, using the Ethernet service between PORT1
on NE1 and PORT1 on NE2 as an example.
Figure 7-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
OptiX RTN 380 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 NodeB
(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.

If... Then...
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
7.4.3 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) or physical link aggregation (PLA) group,
the packet header capturing function can be enabled only for the master port.
● 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.
Procedure
● Capture headers of Layer 2 packets.

● Capture headers of Layer 3 packets.
----End
7.4.4 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 7-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.
Precautions
A port on an OptiX RTN 380 supports port mirroring in only one direction (egress
or ingress).
Procedure
Step 1 Configure port mirroring on the board.

----End
7.4.5 Configuring IP Packet Coloring and Statistics Collection

IP packet coloring and statistics collection is an IP network performance
measurement technology. It marks IP service packets and counts the marked
packets, thereby achieving accurate packet loss measurement from end to end or
by segment.
Prerequisites
● You are an NMS user with administrator rights or higher rights.
● Native Ethernet services or Ethernet services carried by PWs have been
created.

NCE
Procedure
Step 1 Click a desired NE in the NE Explorer and choose Diagnose&Maintenance > IP
Packet Marking from the main menu.
Step 2 (Optional) Set the coloring bit. The default value is IP FLAG BIT0.
Step 3 Click New. The Create IP Packet Marking tab is displayed.

1. Set the following parameters: ID, Name, Role, Action, and Auto Stop
After(minutes).
2. Set the packet matching rules and the logical relationship between the
matching rules.

Step 4 Set the measurement point.
● Uplink/Downlink nodes can be set as VUNI or QinQ measurement points.

● Intermediate nodes can be bound to the VUNI, QinQ, and Tunnel measurement nodes.
● For a VUNI measurement point, set the following parameters: Direction,
Service, Port, VLAN, and Priority.
● For a QinQ measurement point, set Direction, Service, and QinQ Link.
● For a Tunnel function node, set the following parameters: Direction, Port, and
PW Label.
Step 5 Click Start to start a test.
Step 6 Click Stop to stop a test or wait for the test to automatically stop.

Step 7 After the test is over, query the test result.
----End
7.4.6 Checking Ethernet Service Performance Using TWAMP

Light
Two-Way Active Measurement Protocol (TWAMP) is a technology that measures
the two-way performance of IP links. TWAMP Light is a light version of TWAMP.
Microwave devices serve as reflectors and respond to a TWAMP Light test initiated
by other devices. In this way, the quality of network links (delay, jitter, and packet
loss rate) is monitored.
Prerequisites
● The Ethernet services have been correctly deployed, and the service
connectivity is correct.

NCE
Context
TWAMP Light performance measurement consists of on-demand measurement
and continuous measurement.
● On-demand measurement: A performance test is manually initiated to check
the Ethernet service performance only once within a specified period.
● Continuous measurement: A performance test is conducted in a continuous
and uninterrupted way.

Figure 7-5 TWAMP Light performance measurement process
As shown in Figure 7-5, the Controller is the TWAMP Light initiator and the
Responder is the TWAMP Light reflector.
The Controller sends TWAMP-Test packets. After the Responder receives them, it
returns a response to the Controller. After the Controller receives TWAMP-Test
packets from the Responder, it collects statistics about the two-way delay, jitter,
and packet loss rate based on the sequence numbers and timestamps in the
TWAMP-Test packets.
The OptiX RTN 380 can only serve as the TWAMP Light reflector.
Precautions
None.
Procedure
Step 1 Set the TWAMP Light reflector. For details, see the reflector configuration manual.
Step 2 Set the OptiX RTN 380 as the TWAMP Light reflector.
1. In the NE Explorer, select the desired NE and choose Configuration >
TWAMP Server from the Function Tree.
2. Click New.
3. In the New Light Test Session window, set parameters according to the
network plan.

4. Click OK.
Step 3 Perform a TWAMP Light test on the reflector and check the quality of network
links (delay, jitter, and packet loss rate). For details, see the reflector configuration
manual.
The reflector automatically responds to the TWAMP Light test from the initiator.
----End
7.5 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 RF 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 Navigate to the interface of the automatic release function.
Step 2 Enable the automatic release function.

----End
7.6 Querying Power Consumption of NE

This section describes how to query power consumption of NE.
Prerequisites

NCE
Procedure
Step 1 Query the power consumption of the NE.

----End
7.7 Enabling the Power-Saving Mode for an NE

This section describes how to enable the power-saving mode for an NE. NEs adopt
the power-saving mode by default.
Prerequisites

NCE
Context
For an NE operating at a channel space of 250 MHz, the frequencies of some
clocks in the scenario in which the NE works in power-saving mode are lower than
the frequencies in the scenario in which the NE works in normal mode. As such,
the power consumption is reduced.
An NE working in normal mode supports only channel space switchovers between

500 MHz and 250 MHz, whereas an NE working in power-saving mode supports
both channel space switchovers between 500 MHz and 250 MHz and those
between 250 MHz and 125 MHz.
Changing the power-saving mode for an NE interrupts the services carried by the
NE.

Procedure
Step 1 Enter the power-saving configuration window.
Step 2 Enable the power-saving mode for an NE.
----End
7.8 Enabling Automatic Fault Recovery

With automatic fault recovery enabled for an NE, the NE automatically restarts
after the fault recovery time expires if both microwave links and DCN links
connected to the NE are interrupted.
Prerequisites
NOTICE
Automatic fault recovery is supported only in the 1+0 scenario.


NCE
Procedure
Step 1 Enable automatic fault recovery.
----End
7.9 Querying Site Information

You can query microwave site information.
Prerequisites

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

----End
7.10 Querying the Microwave Link Information Report

Prerequisites

NCE
Procedure
Step 1 Query the microwave link information report.

----End
7.11 Querying Optical Power and Alarm Thresholds of

Optical Ports
This section describes how to query the RX/TX optical power and alarm thresholds
of optical ports.
Prerequisites

NCE
Procedure
Step 1 Query the optical power and alarm thresholds of optical ports.

----End

Maintenance Guide A Alarm Reference
A Alarm Reference
Alarms are important indicators for exceptions. This section describes all the
possible alarms on OptiX RTN 380 and how to handle them.
A.1 Alarm List

The following table lists all the possible alarms on the OptiX RTN 380 in
alphabetical order.
Table A-1 Alarm list
Alarm Name Description Alarm Severity
AM_DOWNSHIFT AM/AMAC downshifts Major
ARP_FAIL An Ethernet port fails to learn the Major

peer-end MAC address through
ARP.
ARP_MAC_MISMATCH Inconsistency between the MAC Major

address in a configured static ARP
entry and the MAC address of the
peer port
ARP_SPOOF An ARP spoofing attack. Major
BDTEMP_SENSOR_FAIL Board temperature sensor failure Major
BOOTROM_BAD BOOTROM data check fails. Major
BRDCASTRATIO_OVER The broadcast traffic ratio exceeds Major

the allowed upper threshold.
BUS_ERR Bus error Critical
CLK_LOCK_FAIL Clock locking fails. Major
CLK_NO_TRACE_MODE The clock works in a non-tracing Minor

mode.

COM_EXTECC_FULL An excessive number of TCP Major

connections between
automatically extended ECC NEs.
DBMS_DELETE All databases are being deleted. Critical
DBMS_ERROR Database error Critical
DBMS_PROTECT_MODE Database in protected mode Critical
DB_UNSAVE Configurations cannot be saved Critical

permanently.
DCNCFG_NOT_COMMIT The configured DCN subnet ID has Minor

not been committed.
DCN_CHANNEL_BITERR The DCN_CHANNEL_BITERROR Major

OR alarm indicates bit errors on the
DCN channel.
DCNLINK_OVER Excessive number of DCN links. Major
DCNSIZE_OVER The DCN network is over-sized. Major
DEVICE_AUTH_FAIL Device anti-theft function failure Major
DROPRATIO_OVER The number of lost packets due to Minor

congestion exceeds the threshold.
ELAN_SMAC_FLAPPING The source MAC address learned Major

by an E-LAN service flaps.
ERPS_IN_PROTECTION ERPS in protected mode Minor
ERPS_BLOCK ERPS_BLOCK Minor
ERPS_NOT_COMPLETE The ERPS configuration is Minor

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

TCH channels in an APS group are
inconsistent at the two ends.
ETH_APS_SWITCH_FAIL APS switching failure Minor
ETH_APS_TYPE_MISMA Inconsistent APS protection types Major

TCH
ETH_AUTO_LINK_DOW An Ethernet port is automatically Minor

N switched to the link down state.
ETH_CFM_AIS A local MEP_AIS occurs Major
ETH_CFM_LOC Loss of connectivity Critical

ETH_CFM_MISMERGE Mis-connection Critical
ETH_CFM_RDI An opposite MEP_RDI occurs. Minor
ETH_CFM_UNEXPERI Errored frames Minor
ETH_EFM_DF Discovery failure Major
ETH_EFM_EVENT Performance events at the Major

opposite end
ETH_EFM_LOOPBACK A loopback occurs. Major
ETH_EFM_REMFAULT Faults occur at the opposite end. Critical
ETH_LINK_DOWN Connection fault on an Ethernet Critical

port
ETH_LOS The Ethernet port connection is Critical

lost.
ETH_NO_FLOW No flow on the Ethernet port Major
ETHOAM_SELF_LOOP Point-to-point OAM detects a port Major

loopback.
FDBSIZEALM_ELAN E-LAN forwarding table entries are Minor

exhausted.
FLOW_OVER Received flow at a port exceeds Minor

the threshold.
GNE_CONNECT_FULL The number of gateway Minor

connections exceeds the threshold.
HARD_BAD The hardware is faulty. Critical
HARD_ERR Minor hardware faults Minor
IN_PWR_ABN Abnormal input power Major
INSUFFCNT_MEM_SPAC Insufficient file system space in a Critical

E memory
INSUFFCNT_FLSH_SPAC Insufficient file system space in a Critical

E flash memory
KMC_KEY_SYNC_FAIL Indicates a KMC key Critical

synchronization failure.
LAG_DOWN A LAG is unavailable. Major
LAG_MEMBER_DOWN A member port of the LAG is Minor

unavailable.

LASER_MOD_ERR The pluggable optical module on Major

the board does not match the
optical port.
LASER_SHUT A laser is shut down. Major
LCS_DAYS_OF_GRACE The license file is invalid but Major

remains in the 60-day grace
period.
LCS_EXPIRED The license file is invalid and its Critical

grace period has elapsed.
LCS_FILE_NOT_EXIST No license is installed on the NE. Critical
LCS_LIMITED An NE is configured with a service Major

capacity or function beyond the
permission of the installed license.
LCS_TRIAL_PERIOD The NE is in trial run. Major
LICENSE_LOST The NE fails to detect any license Major

file.
LOOP_ALM A loopback occurs. Minor
LSR_BCM_ALM Setover Current of the Laser over Major

Threshold
LSR_NO_FITED Laser not installed Critical
LSR_WILL_DIE A laser is to reach its life end. Critical
LTI Loss of the synchronous source Major
MAC_EXT_EXC The number of bit errors at the Major

MAC 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 The number of SD errors exceeds Minor

the upper threshold at the MAC
layer.
MPLS_PW_AIS Indicating a defect in the forward Major

direction of a PW
MPLS_PW_BDI PW backward defect indication Minor
MPLS_PW_CSF Client signal failure Major
MPLS_PW_EXCESS The number of TTSIs received by a Suggestion

PW exceeds the upper threshold.

MPLS_PW_LCK LCK is enabled on the tunnel Major

carrying a PW.
MPLS_PW_LOCK A PW delivers a lock command. Major
MPLS_PW_LOCV Loss of PW connectivity Major
MPLS_PW_MISMATCH Only CV/FFD packets with Major

incorrect TTSIs are received within
three consecutive CV/FFD periods.
MPLS_PW_MISMERGE Both CV/FFD packets with correct Major

TTSIs and CV/FFD packets with
MPLS_PW_OAMFAIL OAM protocol negotiation fails on Minor

the NEs at the two ends of a PW.
MPLS_PW_RDI Indicating a defect in the Minor

backward direction of a PW
MPLS_PW_SD SD occurs on a PW. Major
MPLS_PW_SF SF occurs on a PW. Major
MPLS_PW_UNEXPMEG An MEP receives a CCM with a Critical

correct MEG level but an incorrect
MEG ID.
MPLS_PW_UNEXPMEP The MEP ID in a CCM packet Major

received by the sink end is not the
expected one.
MPLS_PW_UNEXPPER The MEG level, MEG ID, and MEP Major

ID in a CCM packet received by
the sink end are correct, but the
interval for receiving CCM packets
is not the expected one.
MPLS_PW_UNKNOWN An unknown defect occurs on a Major

PW.
MPLS_TUNNEL_AIS Indicating a defect in the forward Major

direction of a tunnel
MPLS_TUNNEL_BDI Tunnel backward defect indication Minor
MPLS_TUNNEL_EXCESS The number of TTSIs received by a Suggestion

tunnel exceeds the upper
threshold.
MPLS_TUNNEL_FDI Tunnel FDI Minor
MPLS_TUNNEL_LOCK A tunnel delivers a lock command. Minor

MPLS_TUNNEL_LOCV Loss of tunnel connectivity Major
MPLS_TUNNEL_MISMA No CV/FFD packet with a correct Major

TCH TTSI is received within three
consecutive CV/FFD periods.
MPLS_TUNNEL_MISME Both CV/FFD packets with correct Major

RGE TTSIs and CV/FFD packets with
MPLS_TUNNEL_OAMFAI OAM protocol negotiation fails on Minor

L the NEs at the two ends of a
tunnel.
MPLS_TUNNEL_RDI Indicating a defect in the Minor

backward direction of a tunnel
MPLS_TUNNEL_SD SD occurs on a tunnel. Major
MPLS_TUNNEL_SF SF occurs on a tunnel. Major
MPLS_TUNNEL_UNEXP The MEG ID in a CCM packet Critical

MEG received by the sink end is not the
expected one.
MPLS_TUNNEL_UNEXP The MEP ID in a CCM packet Major

MEP received by the sink end is not the
expected one.
MPLS_TUNNEL_UNEXPP The MEG level, MEG ID, and MEP Major

ER ID in a CCM packet received by
the sink end are correct, but the
interval for receiving CCM packets
is not the expected one.
MPLS_TUNNEL_UNKNO An unknown defect occurs on a Major

WN tunnel.
MOD_COM_FAIL Inter-module communication fails. Critical
MULTI_RPL_OWNER The ring network contains Minor

multiple RPL owner nodes.
MW_AM_TEST An IF port is in the AM testing Minor

state.
MW_BER_EXC Excessive errors on microwave Minor

links
MW_BER_SD Signal degrade due to excessive Minor

errors on microwave links
MW_CFG_MISMATCH Configuration mismatch on the Critical

microwave link

MW_CONT_WAVE Continuous wave Minor
MW_FEC_EXC The FEC bit error rate exceeds the Minor

upper threshold.
MW_FEC_UNCOR Microwave frames contain the Minor

errors that cannot be corrected by
using the forward error correction
(FEC) technology.
MW_LIM Mismatched microwave link ID Major
MW_LOF Loss of microwave frames Critical
MW_RDI Remote defect indication on Minor

microwave links
NB_CFG_MISMATCH Inconsistent configurations on NEs Major

in a PLA or 1+1 protection group
NB_UNREACHABLE A neighboring NE is unreachable Major

to the local NE.
NE_DCN_MODE The NE works in DCN mode. Major
NEIP_CONFUSION Multiple NEs use the same IP Major

address.
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.
NTP_SYNC_FAIL NTP time synchronization fails. Minor
OUT_PWR_ABN Output optical power is abnormal. Critical
PASSWORD_NEED_CHA The default password used by a Major

NGE default user to log in to the NE or
default password of a WLAN
connection has never been
changed.
PATCH_BD_EXCLUDE An NE is automatically isolated Major

from patch installation.
PATCH_BD_MATCH_FAI A patch package fails to be Major

L matched with an NE.
PATCH_PKGERR Patch package errors Minor
PATCH_OP_TIMEOUT Patch package operation timeout Minor
PATCH_INIT_FAIL patch initialize failed Major

PING_ARP_MISMATCH The MAC addresses in the static Minor

and dynamic ARP entries conflict
with each other.
PING_LOS Ping failure Minor
PLA_CFG_MISMATCH PLA configurations are Critical

inconsistent at the two ends of a
microwave link.
PLA_DOWN PLA group failure Major
PLA_MEMBER_DOWN_E PLA group member failure Minor

XT
PLA_PKT_ERR Service packet reassembly fails in Major

the receive direction.
PORT_EXC_TRAFFIC The traffic is higher than the port Warning

bandwidth threshold.
PORTMODE_MISMATC The working mode of the remote Minor

H Ethernet port does not match that
of the local Ethernet port.
PRO_PKT_FLOODING Protocol packet flood attack Major

detected by an NE
PORT_BER_SD Signal degrade due to excessive Minor

bit errors
POWER_ALM Power module alarm Major
PTP_SOURCE_SWITCH PTP time source switching Minor
PTP_TIME_ADJUST_OFF PTP time adjustment function is Minor

disabled
PTP_TIMESTAMP_ABN Abnormal PTP timestamp Major
PW_APS_DEGRADED A PW in an APS protection group Major

fails.
PW_APS_OUTAGE All PWs in an APS protection Major

group fail.
PW_DROPPKT_EXC The number of lost packets on a Suggestion

PW exceeds the upper threshold.
PW_NO_TRAFFIC No traffic on a PW Critical
PWAPS_LOST Loss of APS frames Minor
PWAPS_PATH_MISMAT The working and protection Major

CH channels in an APS group are
inconsistent at the two ends.

PWAPS_SWITCH_FAIL PW APS switching failure Minor
PWAPS_TYPE_MISMATC Inconsistent PW APS protection Major

H types
PWD_ENCRYPT_RISK The user password encryption Major

mode of an NE has security risks.
R_LOF Loss of multiframe on the receive Critical

side
R_LOS Loss of signals on the receive line Critical

side
RADIO_FADING_MARGI Insufficient radio fading margin Minor

N_INSUFF
RADIO_MUTE The radio transmitter is muted. Warning
RADIO_RSL_BEYONDTH The received signal level exceeds Minor

the threshold.
RADIO_RSL_HIGH Over high radio received signal Critical

level
RADIO_RSL_LOW Over low radio received signal Critical

level
RADIO_TSL_HIGH The difference between the actual Critical

transmit power and configured
transmit power crosses the upper
threshold (3 dBm).
RADIO_TSL_LOW The difference between the actual Critical

transmit power and configured
transmit power crosses the lower
threshold (- 3 dBm).
REFLECTOR_IP_CNFLCT The IP address simulated by the Major

reflector is the same as another IP
address on the network.
RPS_INDI Radio protection switching Major

indication
S1_SYN_CHANGE Clock source switching in S1 mode Major
SEC_RADIUS_FAIL Excessive RADIUS authentication Major

failures
SECU_ALM Login attempts of unauthorized Major

users
SRV_LOOP_LD Ethernet service loop alarm Major
SRV_SHUTDOWN_LD Ethernet services disabled Major

SSL_CERT_DAMAGED A user-customized SSL certificate Critical

file is damaged.
SSL_CERT_TO_EXPIRE A customized SSL certificate file is Critical

about to expire.
SSL_CERT_NOENC The certificate file of SSL is not Major

encrypted
STORAGE_FAIL Memory fault Critical
STORM_CUR_QUENUM_ Alarm storms Minor

OVER
SUBNET_RT_CONFLICT Subnetwork route conflict Major
SWDL_ACTIVATED_TIM The activation operation times Critical

EOUT out.
SWDL_COMMIT_FAIL The submit operation fails. Minor
SWDL_INPROCESS The NE is in the process of Warning

package loading.
SWDL_NEPKGCHECK Loss of package files Critical
SWDL_PKGVER_MM Inconsistent package versions Minor
SWDL_ROLLBACK_FAIL The version rollback on an NE Minor

fails.
SYNC_C_LOS Loss of synchronization clock Warning

source in the priority table
SYSLOG_COMM_FAIL Communication between the NE Major

and the syslog server fails
TEM_HA Too high laser temperature Major
TEM_LA Too low laser temperature Major
TEMP_ALARM The current temperature exceeds Minor

the lower/higher threshold.
TIME_LOCK_FAIL Time locking fails. Major
TIME_LOS The time source level is lost. Major
TIME_NO_TRACE_MOD The NE time enters the non- Minor

E tracing state.
TF Laser transmission fails. Critical
TUNNEL_APS_DEGRADE A tunnel in an APS protection Major

D group is interrupted.

TUNNEL_APS_OUTAGE All tunnels in an APS protection Major

group are interrupted.
USB_FILE_UNSEC The USB flash drive used by the Major

NE is insecure.
USB_PROCESS_FAIL Data fails to be restored from or Minor

backed up to a USB flash drive.
VERSION_NOTSUPPORT The current version does not Critical

support the function or data
configured for an NE.
A.2 Alarms and Handling Procedures

This section describes the alarms that possibly occur on the OptiX RTN 380 in
alphabetic order and how to handle these alarms.
A.2.1 AM_DOWNSHIFT
Description
The AM_DOWNSHIFT alarm indicates that the AM/AMAC downshifts the
modulation scheme. This alarm occurs when a lower order modulation scheme is
used or when a lower channel spacing is used in QPSK Strong modulation scheme.
This alarm clears when the highest order modulation scheme is used.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Impact on the System

Service transmission capacity over the microwave link decreases.
Possible Causes
● Cause 1: Adverse weather conditions cause the performance of the working
channel to deteriorate.
● Cause 2: Interference around the working channel causes its performance to
deteriorate.

● Cause 3: Abnormal transmit power of the OptiX RTN 380 at the transmit end
causes the performance of the working channel to deteriorate.
● Cause 4: Abnormal receive power of the OptiX RTN 380 at the receive end
Procedure
Step 1 Cause 1: Adverse weather conditions cause the performance of the working
channel to deteriorate.
1. The AM/AMAC scheme downshift is normal when adverse weather conditions
cause the performance of the working channel to deteriorate. Therefore, no
operations are required.
Step 2 Cause 2: Interference around the working channel causes its performance to
deteriorate.
1. Eliminate the interference around the working channel.
Step 3 Cause 3: Abnormal transmit power of the OptiX RTN 380 at the transmit end
1. Use the network management system (NMS) to check whether the transmit
power of the OptiX RTN 380 at the transmit end is abnormal. If the transmit
power is abnormal, troubleshoot the fault by referring to Troubleshooting
Radio Links.
Step 4 Cause 4: Abnormal receive power of the OptiX RTN 380 at the receive end causes
the performance of the working channel to deteriorate.
1. Use the NMS to check whether the receive power of the OptiX RTN 380 at the
receive end is abnormal. If the receive power is abnormal, troubleshoot the
fault by referring to Troubleshooting Radio Links.
----End
Related Information
None
A.2.2 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
A.2.3 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
A.2.4 ARP_SPOOF
Description
The ARP_SPOOF alarm indicates 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
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, Parameter 2 Indicate the slot number.
Parameter 3 Indicates the subboard number.
Parameter 4, Parameter 5 Indicate 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 engineers.
----End
Related Information
None
A.2.5 BDTEMP_SENSOR_FAIL
Description
The BDTEMP_SENSOR_FAIL alarm indicates that the temperature sensor of the NE
fails.

Attribute
Major Equipment alarm
Parameters
None

The NE temperature data cannot be collected. As a result, the TEMP_ALARM
alarm is not reported when the NE temperature exceeds the upper threshold.
Possible Causes
Cause 1: The temperature sensor is faulty.
Procedure
Step 1 Replace the NE.
----End
Related Information
None
A.2.6 BOOTROM_BAD
Description
The BOOTROM_BAD alarm indicates that boot ROM data verification fails. This
alarm is reported when boot ROM data is found damaged in a periodical system
check.
Attribute
Parameters
table.

Name Meaning
Parameter 1 This parameter has a fixed value of 0x01.
Parameters 2 and 3 Indicate the type of the boot ROM damage.
● 0x00, 0x01: damage to basic BIOS
● 0x00, 0x02: damage to extended BIOS
Parameters 4 and 5 These parameters have a fixed value of 0xff, 0xff.

If the NE is cold reset when the BOOTROM_BAD alarm occurred, BIOS loading
fails and the NE fails to be started.
Possible Causes
Cause 1: The OptiX RTN 380 is faulty.
Procedure
Step 1 Replace the OptiX RTN 380.
----End
Related Information
None
A.2.7 BRDCASTRATIO_OVER
Description
The BRDCASTRATIO_OVER alarm indicates that the ratio of broadcast and
multicast packets to the total packets exceeds the preset upper threshold.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the service direction.

● 0x00: receive direction
● 0x01: transmit direction

A broadcast storm might have occurred.
Possible Causes
● Cause 1: A service loop is formed.
● Cause 2: In an IPTV scenario, the broadcast packet suppression threshold is
not properly set.
● Cause 3: In a PLA group, PLA configurations have been deleted from the
alarmed NE but not from the other NE.
Procedure
Step 1 Cause 1: A service loop is formed.
1. Check for and release any port self-loop or service loop on the service path.
Step 2 Cause 2: In an IPTV scenario, the broadcast packet suppression threshold is not
properly set.
1. Change the broadcast packet suppression threshold to a proper value. For
details, see Setting the Advanced Attributes for an Ethernet Port.
Step 3 Cause 3: In a PLA group, PLA configurations have been deleted from the alarmed
NE but not from the other NE.
1. Delete PLA configurations from the other NE.
----End
Related Information
None
A.2.8 BUS_ERR
Description
The BUS_ERR alarm indicates a bus error.
Attribute
Critical Equipment alarm

Parameters
table.
Name Meaning
Parameter 1 Indicates that communication between hardware modules on

equipment is abnormal.
● 0x01: Bus signals from the analog to digital converter (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.
● 0x08: Services on a PLA member are abnormal.
● 0x0A: Bus signals from the IF modem to the FPGA module are
abnormal.
● 0x0B: Bus signals on channel 0 from the FPGA module to the
data switching chip are abnormal.
● 0x0C: Bus signals on channel 1 from the FPGA module to the
data switching chip are abnormal.
● 0x0D: Bus signals between the FPGA module and the data
switching chip are abnormal.
● 0x0E: Encapsulation & decapsulation asynchronization is
abnormal.

Name Meaning
Parameter When Parameter 1 is 0x08, Parameter 2 indicates the ID of the PLA

2, member port on which services are abnormal.
Parameter 3
When Parameter 1 is 0x0B:
● When Parameter 2 is 0x01, bus signals on channel 0 from the
FPGA module to the data switching chip are abnormal.
data switching chip to the FPGA module are abnormal.
When Parameter 1 is 0x0A and Parameter 2 is 0x01, bus signals
from the IF modem to the FPGA module are abnormal.
When Parameter 1 is 0x0C:
When Parameter 1 is 0x0D and Parameter 2 is 0x02, bus signals
from the data switching chip to the FPGA module are abnormal.
When Parameter 1 is 0x0E and Parameter 2 is 0x02, downstream
decapsulation asynchronization occurs.

Name Meaning
Parameter When Parameter 1 is 0x08, Parameter 2 indicates the ID of the PLA

2, member port on which services are abnormal.
Parameter 3
When Parameter 1 is 0x0B:
When Parameter 1 is 0x0A and Parameter 2 is 0x01, bus signals
from the IF modem to the FPGA module are abnormal.
When Parameter 1 is 0x0C:
When Parameter 1 is 0x0D and Parameter 2 is 0x02, bus signals
from the data switching chip to the FPGA module are abnormal.
When Parameter 1 is 0x0E and Parameter 2 is 0x02, downstream
decapsulation asynchronization occurs.
When Parameter 1 is 0x08, Parameter 2 indicates the ID of the
port where the PLA member service is abnormal.
● when Parameter 1 is 0x08 and Parameter 2 is 0x01, the PLA
member service on port 1 are abnormal.
● when Parameter 1 is 0x08 and Parameter 2 is 0x02, the PLA
member service on port 2 are abnormal.

Services that travel along the faulty bus have bit errors or are interrupted.
Possible Causes
Cause 1: The NE that reports the BUS_ERR alarm is faulty.
Procedure
1. Replace the OptiX RTN 380 that reports the BUS_ERR alarm.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None

A.2.9 CLK_LOCK_FAIL
Description
The CLK_LOCK_FAIL alarm indicates that clock locking fails.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicate the type of the out-of-lock for which this alarm is
reported.
● 0x05: The system clock is unlocked.
● 0x06: The analog PLL is unlocked.

The service may have bit errors.
Possible Causes
● Cause 1: Physical-layer synchronization is used, but the physical clock link is
faulty.
● Cause 2: Physical-layer synchronization is used, but the frequency deviation of
the clock source is too large.
● Cause 3: In CCDP networking scenarios, the cascade cable is faulty.
Procedure
Step 1 Cause 1: Physical-layer synchronization is used, but the physical clock link is faulty.
1. Check for and clear any ETH_LOS alarms.
2. If the CLK_LOCK_FAIL alarm persists, query the transmit optical power at the
opposite end on the NMS. If the transmit optical power is abnormal, replace
the optical module used at the opposite end.
3. If the CLK_LOCK_FAIL alarm persists, check whether the local receive port is
faulty. If it is faulty, Replace the OptiX RTN 380.

Step 2 Cause 2: Physical-layer synchronization is used, but the frequency deviation of the
clock source is too large.
1. Change the clock source that the NE traces by following instructions in
Configuring the System Clock Source.
– If the alarm persists, the clock unit of the local NE may be faulty. Replace
the OptiX RTN 380.
– If the alarm clears, handle the clock fault on upstream NEs.
Step 3 Cause 3: In CCDP networking scenarios, the cascade cable is faulty.

1. Check whether the other alarms occur on the cascade port. If yes, clear these
alarms before you proceed.
Step 4 If the CLK_LOCK_FAIL alarm persists, contact Huawei technical support engineers.
----End
Related Information
None
A.2.10 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE alarm indicates that the system clock is in a non-
tracing mode. This alarm occurs when the current system clock does not trace any
clock source.
Attribute
Minor Equipment alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the clock mode.
● 0x01: holdover mode
● 0x02: free-run mode


The system clock works in non-tracing mode and is of poor quality. The bit error
rate increases when NEs become asynchronous.
In CPRI mode, if CPRI services are normal, there is no impact on the system and the alarm
does not need to be handled.
Possible Causes
● Cause 1: No clock priority table is configured for the system clock.
● Cause 2: All the clock sources in the configured clock priority table fail.
Procedure
Step 1 Cause 1: No clock priority table is configured for the system clock.
1. Configure the clock priority table. For details, see Configuring Clock Sources.
Step 2 Cause 2: All the clock sources in the configured clock priority table fail.
1. If any clock source is lost, check for and clear any SYNC_C_LOS alarms.
----End
Related Information
None
A.2.11 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.
----End
Related Information
None
A.2.12 DBMS_DELETE
Description
The DBMS_DELETE alarm indicates that databases are being deleted. This alarm is
reported when a user runs a command to delete databases and the NE is in the
Deleting Database state.
Attribute
Parameters
None

If the NE is not reset after the deletion of databases, the NE cannot receive
configurations delivered by the NMS or store configurations within 48 hours. After
48 hours elapses, the NE automatically restores the deleted databases. If the NE is
reset within 48 hours after the deletion of databases, the NE enters the initial
state and the deleted databases can only be restored manually.

Possible Causes
Cause 1: Databases are being deleted.
Procedure
Step 1 Follow instructions in Restoring the Database by NMS to restore the databases.
----End
Related Information
None
A.2.13 DBMS_ERROR
Description
The DBMS_ERROR alarm indicates that an error occurred in system database
processing.
Attribute
Critical Processing error alarm
Parameters
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.
● 0x10: Incremental data fails to be backed up.
● 0x20: Incremental data fails to be backed up to the NVRAM.
● 0x40: Incremental data fails to be backed up to the flash
memory.

Name Meaning
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
● 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 cause of the alarm.
If the value of parameter 1 is 0x01, this parameter indicates a

storage area check error. Valid values are as follows:
● 0x01: An error occurs when a list file is generated in the storage
area.
● 0x02: An error occurs when the database file is being verified.
● 0x04: The database record header is incorrect.
periodical backup error.
● 0x01: The flash space is insufficient, causing the database
backup failure.
● 0x02: Database information fails to be checked.
system running fault.
● 0x08: Data of the active and standby boards fails to be
compared.
If the value of parameter 1 is 0x10, this parameter indicates that
the recycled incremental data fails to be backed up.
● 0x02: Database information fails to be checked.
incremental data fails to be written into the NVRAM. Valid values
are as follows:
● 0x01: The NVRAM is full.
● 0x02: The NVRAM header data is abnormal.
incremental data fails to be backed up to small files.
● 0x01: The flash file system fails to generate small files.
Parameter 5 Reserved fields

The system configuration may be lost. As a result, a failure indication is returned
for some query and setting commands, and some system functions are
unavailable.
Possible Causes
● Cause 1: The database processing fails or the database is damaged.
● Cause 2: The NE is faulty.

Procedure
Step 1 When the DBMS_ERR alarm occurs, contact the engineers of Huawei.
----End
Related Information
The DBMS_ERR alarm is used for the R&D personnel to locate the system
abnormality. When the DBMS_ERR alarm occurs, contact the engineers of Huawei.
A.2.14 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE alarm indicates that the system database of an NE is
in protection mode.
Attribute
Parameters
None

The system configuration may be lost. As a result, a failure indication is returned
for some query and setting commands, and some system functions are
unavailable.
Possible Causes
Cause 1: The NE software is frequently reset.
Procedure
Step 1 Contact Huawei's local technical support so they can analyze the cause for the
frequent NE software resets and rectify the fault.
----End
Related Information
None.

A.2.15 DB_UNSAVE
Description
The DB_UNSAVE alarm indicates that new configurations are not allowed to be
saved to the database on the active board. This alarm is reported when a
configuration is added to the database in scenarios where configurations are not
allowed.
Attribute
Critical Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates that new configurations are not allowed to be saved to
the database.
● 0x01: New configurations cannot be saved when the database is
in package loading state.

New configurations cannot be saved to the database.
Possible Causes
set-forbidswitch is run to forbid new configurations. When a configuration is
added, this alarm is reported.
Procedure
Step 1 Perform the commit operation.
Step 2 If the alarm persists, contact Huawei technical support engineers.
----End
Related Information
Perform the commit operation.

A.2.16 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
A.2.17 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 and 2 Indicate the slot ID of a board associated with the outband
DCN channel.
Parameters 3 and 4 Indicate the subboard ID of a board associated with the

outband DCN channel.
Parameters 5 and 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 the protocol layer.

● 0x02: indicates the physical layer.
● 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.
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 7.11 Querying Optical Power and Alarm Thresholds
of Optical 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 4.2 Replacing an SFP
Module.
2. Check whether the outband DCN link at the peer end is faulty.
The steps are the same as those in Step 1.
Step 2 Cause 2: The NE is faulty.
1. Replace the NE. For details, see 4.1 Replacing an OptiX RTN 380.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----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.
A.2.18 DCNLINK_OVER
Description
The DCNLINK_OVER alarm indicates that there is an excessive number of DCN
links. This alarm is reported if the number of OSPF neighbors on the DCN exceeds
the recommended value 10.
Attribute
Parameters
table.

Name Meaning
Parameter 1 0x01: The number of OSPF neighbors on the DCN exceeds the
recommended value.
0x02: The 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, and the NE
generating this alarm or its neighboring NEs may fail to be managed.
Possible Causes
Cause 1: The number of OSPF neighbors on the DCN exceeds the recommended
value 10.
Procedure
Step 1 Disable unused DCN channels.
----End
Related Information
None
A.2.19 DCNSIZE_OVER
Description
The DCNSIZE_OVER alarm indicates that a data communication network (DCN) is
over-sized.
Attribute
Parameters
table.

Name Meaning
Parameters 1 and 4 Indicate the size of the DCN network.
The value 0xFFFFFFFF indicates that the NEs work in L2DCN

mode. The other values indicate the size of the DCN
network.
Parameters 5 Reserved for future use.

● CPU resources are insufficient. As a result, DCN packets cannot be forwarded
immediately and some NEs are unreachable from the NMS.
● Route flapping or network storms may occur.
Possible Causes
Cause 1: The number of nodes on the DCN network crosses the preset threshold.
Procedure
Step 1 Cause 1: The number of nodes on the DCN network crosses the preset threshold.
1. Replan DCN subnets as required.
----End
Related Information
This alarm is reported if a Layer 2 DCN subnet consists of over 1024 nodes
(including NEs, NMS servers, and NMS clients on the same network segment), an
IP DCN subnet consists of over 200 nodes. The solution is to divide the subnet.
A.2.20 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


table.
Name Meaning
Parameter 1 Indicates the port number.

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 verification
code is correct. If the verification code is incorrect, change it.
2. If the anti-theft function is not enabled, go to the next step.
Step 2 Check whether the DEVICE_AUTH_FAIL alarm is cleared. If the alarm persists,
contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None
A.2.21 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 QoS alarm

Parameters
Name Meaning
Parameter 1 Indicates the direction in which traffic crosses the threshold.
● 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).
Procedure
Step 1 Cause 1: Service configuration is incorrect.
1. Check and reconfigure services according to the network plan.
Step 2 Cause 2: Actual traffic exceeds the configured port bandwidth or CIR.
1. Querying Traffic, Physical Bandwidth, or Bandwidth Utilization of
Ethernet Ports. 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 Configuring Port
Shaping to increase port bandwidth or expand the network.
----End
Related Information
If packet loss is indicated in the receive direction, check the method of handling
red packets in the traffic classification configuration. If the method of handling red
packets is non-discard, packets may not be actually lost in the receive direction.
A.2.22 ERPS_BLOCK
Description
The ERPS_BLOCK alarm indicates that a port on the ERPS ring is blocked when
protection switching is triggered (not in the idle state).

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 the ERPS_BLOCK 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
A.2.23 ELAN_SMAC_FLAPPING
Description
The ELAN_SMAC_FLAPPING alarm indicates that a learned MAC address for E-LAN
services flaps. This alarm is reported when two ports learn the same source MAC
address.

Attribute
Major QoS 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
Parameter 10 Indicates the slot ID of the board that learns the source
MAC address before the flapping occurs.
Parameter 11 Indicates the slot ID of the subboard that learns the

source MAC address before the flapping occurs.
Parameters 12 to 13 Indicates the ID of the port that learns the source MAC
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 Indicate the type of the port that learns the source MAC
address after the flapping occurs.
● 0x02: UNI
● 0x03: NNI
source MAC address after the flapping occurs.

Name Meaning
source MAC address after the flapping occurs.
Parameters 21 to 22 Indicates the ID of the port that learns the source MAC
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 Performing E-LAN
Service Loopback Detection.
----End
Related Information
None
A.2.24 ERPS_IN_PROTECTION
Description
The ERPS_IN_PROTECTION alarm indicates that a fault on an Ethernet ring
protection switching (ERPS) ring causes an ERPS switchover.
Attribute

Parameters
table.
Name Meaning
Parameter 1, Parameter 2 Indicate the ERPS ID.
Parameter 3 Indicates the direction where the fault locates on the
ERPS ring against the ring protection link (RPL)
owner.
● 0x00: west
● 0x01: east
Parameters 4 to 9 Indicate the MAC address of the faulty node.

Configured services may be interrupted because at least one node on the ERPS
ring has lost connectivity.
Possible Causes
Cause 1: A node on the EPRS ring is faulty.
Procedure
Step 1 Identify the faulty node based on the alarm parameters.
Step 2 Identify the blocked port on the faulty node.
Step 3 Rectify the fault related to the blocked port.
----End
Related Information
None
A.2.25 ERPS_NOT_COMPLETE
Description
The ERPS_NOT_COMPLETE alarm indicates that the ERPS configuration is
incomplete.

Attribute
Minor Equipment Alarm
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.

A.2.26 ETH_APS_LOST
Description
The ETH_APS_LOST alarm indicates 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
Minor Communication alarm
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
A.2.27 ETH_APS_PATH_MISMATCH
Description
The ETH_APS_PATH_MISMATCH alarm indicates that the working and protection
paths in an APS group are inconsistent at the two ends.
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
A.2.28 ETH_APS_SWITCH_FAIL
Description
The ETH_APS_SWITCH_FAIL alarm indicates a protection switching failure.
Attribute
Minor Processing error alarm
Parameters
None

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 Querying MPLS APS Status.
Then, deactivate and activate the APS protection group at the two ends.
Step 2 Cause 2: APS fails due to other reasons.

1. Reactivate APS protection at both ends.
----End
Related Information
None
A.2.29 ETH_APS_TYPE_MISMATCH
Description
The ETH_APS_TYPE_MISMATCH alarm indicates 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
A.2.30 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 port that reports the ETH_AUTO_LINK_DOWN alarm cannot carry any services
and a switchover may occur on the equipment connected to the port.
Possible Causes
● Cause 1: The microwave link connected to the port is faulty.
● Cause 2: The opposite service access port is faulty.
Procedure
Step 1 Cause 1: The microwave link connected to the port is faulty.

1. Check for and clear any MW_LIM and MW_LOF alarms on the local and
opposite microwave ports
Step 2 Cause 2: The opposite service access port is faulty.
1. Check for and clear any ETH_LOS or ETH_LINK_DOWN alarm, and optical-
module-related alarm on the opposite port.
----End
Related Information
None
A.2.31 ETH_CFM_AIS
Description
The ETH_CFM_AIS alarm indicates that the local maintenance end point (MEP)
receives alarm indication signal (AIS) messages, indicating that a fault occurred at
the server layer.
Attribute
Parameters
table.
Name Meaning
Parameters 1 to 4 Indicate the ID of the port that reports the ETH_CFM_AIS
alarm.
Parameters 5 and Indicate the VLAN ID of the MEP.
6
Parameter 7 Indicates the direction of the port on the local MEP.
● 0x00: direction insensitive
● 0x01: The port is in the ingress direction.
● 0x02: The port is in the egress direction.

Name Meaning
Parameter 8 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)

● The loopback (LB) and linktrace (LT) detection functions of Ethernet service
OAM are unavailable.
● The services between the local MEP and the remote MEP may be interrupted.
Possible Causes
Cause 1: The upstream AIS-activated NE detected a fault in the Ethernet server
layer.
Procedure
Step 1 Rectify the detected fault in the Ethernet server layer.
----End
Related Information
None
A.2.32 ETH_CFM_LOC
Description
The ETH_CFM_LOC alarm indicates the loss of continuity. This alarm is reported
when the system fails to receive continuity check messages (CCMs) from the
remote maintenance end point (MEP) in 3.5 consecutive continuity check (CC)
intervals.
Attribute

Parameters
table.
Name Meaning
Parameters 1 to 4 Indicate the ID of the port that reports the ETH_CFM_LOC
alarm.
Parameters 5 and 6 Indicate the VLAN ID of the MEP.
MEP.
Parameter 9 and Indicates the ID of the remote MEP.
Parameter 10
(RMEPID)

● The loopback (LB) and linktrace (LT) functions of Ethernet service OAM are
unavailable.
Possible Causes
● Cause 1: The line between the local MEP and the remote 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
Step 1 Cause 1: The line between the local MEP and the remote MEP is interrupted.
1. Check whether the physical link between the two MEPs is normal.
If... Then...
The physical link is faulty Rectify the link fault.
The physical link is normal Go to Cause 2.
Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the
local MEP belongs is faulty.
1. Check whether the Ethernet service in the MA to which the local MEP belongs
is configured correctly.
If... Then...
The service is configured Re-configure the Ethernet service to
incorrectly ensure consistency at both ends.
The service is configured Go to Cause 3.
correctly
Step 3 Cause 3: Serious congestion occurs on the network.

1. Check the bandwidth utilization. If the bandwidth is exhausted, increase the
bandwidth or eliminate the source that abnormally sends a large amount of
data.
----End
Related Information
None
A.2.33 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE alarm indicates an incorrect connection. This alarm is
reported when the local maintenance end point (MEP) receives continuity check
messages (CCMs) carrying a maintenance domain (MD) or a maintenance
association (MA) name that is different from its configured MA name.
Attribute
Parameters


table.
Name Meaning
Parameters 1 to Indicate the ID of the port that reports the
4 ETH_CFM_MISMERGE alarm.
Parameters 5 Indicate the VLAN ID of the MEP.
and 6
MEP.

The services between the local MEP and the remote MEP may be interrupted or
the dataflow may be incorrectly routed.
Possible Causes
● Cause 1: The MD/MA names of the local and remote MEPs are configured
inconsistently.
● Cause 2: The physical connection is incorrect.
Procedure
Step 1 Cause 1: The MD/MA names of the local and remote MEPs are configured
inconsistently.
1. Check whether the MD/MA names of the local and remote MEPs are the
same.
If... Then...
They are different Re-configure them consistently.
They are the same Go to Cause 2.

Step 2 Cause 2: The physical connection is incorrect.

1. Check the physical connection of the Ethernet service route and rectify any
connection faults.
----End
Related Information
None
A.2.34 ETH_CFM_RDI
Description
The ETH_CFM_RDI alarm indicates that the system receives continuity check
messages (CCMs) with remote defect indication (RDI) from a remote maintenance
end point (MEP).
Attribute
Parameters
table.
Name Meaning
Parameters 1 to 4 Indicate the ID of the port that reports the ETH_CFM_RDI
alarm.
Parameters 5 and 6 Indicate the VLAN ID of the MEP.

Name Meaning
MEP.
Parameter 9 and Indicates the ID of the remote MEP.
Parameter 10
(RMEPID)

● The loopback (LB) and linktrace (LT) detection functions of Ethernet service
OAM are unavailable.
Possible Causes
Cause: The remote MEP receives incorrect CCMs.
Procedure
Step 1 Determine the alarmed port according to the alarm parameters.
Step 2 Check whether the remote MEP connected to the port reported the ETH_CFM_AIS,
ETH_CFM_LOC, ETH_CFM_MISMERGE, ETH_CFM_UNEXPERI alarm.
----End
Related Information
None
A.2.35 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI alarm indicates that the local maintenance end point
(MEP) receives incorrect continuity check messages (CCMs).

Attribute
Parameters
table.
Name Meaning
Parameters 1 to Indicate the ID of the port that reports the
4 ETH_CFM_UNEXPERI alarm.
Parameters 5 Indicate the VLAN ID of the MEP.
and 6
MEP.

● The loopback (LB) and linktrace (LT) functions of Ethernet service OAM are
unavailable.
● Services may become abnormal owing to the loop.
Possible Causes
● Cause 1: MEPs are inconsistently configured at the two ends.
● Cause 2: The service is looped back.

Procedure
Step 1 Cause 1: MEPs are inconsistently configured at the two ends.
1. Check whether MEPs are consistently configured at the two ends. if they are
inconsistently configured, reconfigure them consistently.
Step 2 Cause 2: The service is looped back.

1. Check whether any IP ports on the service path are looped back. Release any
loop.
----End
Related Information
None
A.2.36 ETH_EFM_DF
Description
The ETH_EFM_DF alarm indicates a port discovery failure. This alarm is reported
when the point-to-point OAM protocol negotiation fails at an Ethernet port.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the cause of the negotiation failure.
● 0x01: A connection fault occurs at the local end.

● 0x02: The local end fails to receive any OAM packets in the
specified period.
● 0x03: The OAM settings of the remote 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 remote end.
● 0x05-0xff: Reserved.


The services at the port may be interrupted.
Possible Causes
● Cause 1: The physical port at the local end is faulty.
● Cause 2: OAM auto-discovery is disabled at the remote end.
● Cause 3: OAM is inconsistently configured at both ends.
Procedure
Step 1 Determine the alarm cause according to the alarm parameters.
If... Then...
The value of Parameter 1 is 0x01 Go to Cause 1.
The value of Parameter 1 is 0x03 or 0x04 Go to Cause 3.
Step 2 Cause 1: The physical port at the local end is faulty.

1. Check whether the link connected to the port is faulty. If the link is faulty,
rectify the fault.
2. If the link is normal, check whether the port is faulty. If the port is faulty,
replace the OptiX RTN 380.
Step 3 Cause 2: OAM auto-discovery is disabled at the remote end.

1. Enable OAM auto-discovery.
Step 4 Cause 3: OAM is inconsistently configured at both ends.

1. Re-configure OAM parameters by referring to instructions in enabling OAM
auto-discovery.
----End
Related Information
None
A.2.37 ETH_EFM_EVENT
Description
The ETH_EFM_EVENT alarm indicates that an event occurred on the opposite NE.
This alarm is reported when the local end receives a link error indication packet
(OAMPDU) 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

The services at the port may be degraded or interrupted.
Possible Causes
Cause: The link is faulty.
Procedure
Step 1 Check whether cables and fiber connectors are intact and whether fiber
connectors are clean.
----End
Related Information
None
A.2.38 ETH_EFM_LOOPBACK
Description
The ETH_EFM_LOOPBACK alarm indicates a loopback. This alarm is reported 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 status of the loopback.
● 0x01: The local end initiates a loopback.

● 0x02: The local end responds to a loop request from the
opposite end.

The services at the port may be looped back.
Possible Causes
● Cause 1: The local end initiates a loopback.
● Cause 2: The opposite end initiates a loopback.
Procedure
Step 1 Determine the loopback initiation end according to the alarm parameters.
Step 2 Cause 1: The local end initiates a loopback.

1. Determine the cause of the loopback at the local end and release the
loopback.
Step 3 Cause 2: The opposite end initiates a loopback.

1. Determine the cause of the loopback at the opposite end and release the
loopback.
----End
Related Information
None

A.2.39 ETH_EFM_REMFAULT
Description
The ETH_EFM_REMFAULT alarm indicates that the opposite NE is faulty. This
alarm is reported when the local end receives a fault indication packet
(OAMPDUM) from the opposite end.
Attribute
Critical Communication alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the fault type at the opposite end.
● 0x01: link fault
● 0x02: dying gasp
● 0x03: critical event

The services at the port that reports the ETH_EFM_REMFAULT alarm may be
interrupted.
Possible Causes
● Cause 1: The opposite NE is reset.
● Cause 2: The opposite NE is faulty.
Procedure
Step 1 Cause 1: The opposite NE is reset.
1. Check whether the opposite NE is reset.
If... Then...
The opposite NE is reset Wait until the reset completes.
The opposite NE is not reset Rectify the fault on the opposite NE.

Step 2 Cause 2: The opposite NE is faulty.

1. Rectify the fault on the opposite NE.
----End
Related Information
None
A.2.40 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.
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 OptiX RTN 380.
The port is functional Go to Cause 4.

1. Check whether the opposite NE is faulty.
----End
Related Information
None
A.2.41 ETH_LOS
Description
The ETH_LOS alarm indicates the loss of connection on an optical Ethernet port.
Attribute
Parameters
None

Services at the port that reports the ETH_LOS alarm may be interrupted.
Possible Causes
● Cause 1: The optical fiber connected to the alarmed port is faulty.

● Cause 2: The local NE is faulty.

Procedure
Step 1 Cause 1: The optical fiber connected to the alarmed port is faulty.
1. Check the optical fiber connected to the alarmed port.
If... Then...
The optical fiber is loose Reconnect the optical fiber.
The SFP module is faulty Replace the SFP module.
The connection is correct Go to Cause 2.
Step 2 Cause 2: The local NE is faulty.

1. Check whether the alarmed port is faulty.
If... Then...
The port is faulty Replace the local OptiX RTN 380.
The port is not faulty Go to Cause 3.

1. Check whether the opposite NE connected to the alarmed port is faulty.
----End
Related Information
None
A.2.42 ETH_NO_FLOW
Description
The ETH_NO_FLOW alarm indicates that an Ethernet port in the link up state
bears no traffic.
Attribute
Major QoS alarm
Parameters


table.
Name Meaning
Parameter 1 Indicates the direction in which there is no traffic.

● 0x01: transmission direction

The port does not transmit services.
Possible Causes
● Cause 1: The port is not configured with any services.
● Cause 2: The services configured on the port do not have traffic.
Procedure
Step 1 Cause 1: The port is not configured with any services.
1. Configure Ethernet services on the port.
Step 2 Cause 2: The services configured on the port do not have traffic.
1. Determine which direction bears no traffic according to the alarm parameter.
If... Then...
There is no traffic in the transmit Verify that the service is running properly
direction at the local end.
There is no traffic in the receive Verify that the opposite NE is running
direction properly.
----End
Related Information
None
A.2.43 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP alarm indicates a MAC port that runs the point-to-point
OAM protocol is looped back. This alarm is reported if a MAC port receives OAM
protocol packets sent by itself or the local NE after the loop detection function is
enabled.

Attribute
Major Environment alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the loopback type.

● 0x01: port self-loop
● 0x02: inter-port loopback on an NE
● 0x03-0xff: reserved

A network storm may occur due to loopback.
Possible Causes
● Cause 1: The cable connected to the port is self-looped, the port joins a LAN
that has a loop, or a PHY/MAC loopback is manually configured at the port.
● Cause 2: Two ports on the NE are connected through a cable or join the same
LAN.
Procedure
Step 1 Determine the loopback type according to Parameter 1, and then handle the
loopback accordingly.
If... Then...
Step 2 Cause 1: The cable connected to the port is self-looped, the port joins a LAN that
has a loop, or a PHY/MAC loopback is manually configured at the port.

If... Then...
The PHY/MAC loopback is Manually release the PHY/MAC loopback
manually configured at the port at the port. If the loopback automatically
release function is enabled, wait five minutes
for the automatic release.
The cable connected to the port Reconnect the cables.
is self-looped
The port joins a LAN that has a Eliminate the loop on the LAN, or disconnect
loop the port from the LAN.
Step 3 Cause 2: Two ports on the NE are connected through a cable or join the same
LAN.
1. Check whether two ports on the NE are connected through a cable or join the
same LAN.
If... Then...
The two ports on the NE are connected Disconnect the cable.
through a cable
The two ports on the NE join the same LAN Disconnect a port from the
LAN.
----End
Related Information
None
A.2.44 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 QoS 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
A.2.45 FLOW_OVER
Description
The FLOW_OVER alarm indicates that data traffic at an Ethernet port crosses the
threshold.
Attribute
Minor QoS alarm
Parameters


table.
Name Meaning
Parameter 1 Indicates the direction in which traffic crosses the threshold.

● 0x01: transmit direction

Some data at the port may be discarded.
Possible Causes
● Cause 1: The traffic threshold at the local port is too low.
● Cause 2: The opposite port transmits heavy data traffic.
Procedure
Step 1 Cause 1: The traffic threshold at the local port is too low.
1. Follow instructions in Setting the Advanced Attributes for an Ethernet Port to
raise the traffic threshold at the local port. Note that the traffic threshold
cannot exceed the rate of the local port.
Step 2 Cause 2: The opposite port transmits heavy data traffic.

1. Configure QoS policies at the opposite port to reduce the data traffic from the
opposite port.
----End
Related Information
None
A.2.46 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 Indicate the type of the connection for which this alarm is
to 2 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.
0x38, the number of SSL connections for port 5432 exceeds
the threshold.
0x00, the 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
Step 1 Check all the connections and delete unused connections so that new connections
can be established.
----End
Related Information
None
A.2.47 HARD_BAD
Description
The HARD_BAD alarm indicates that hardware is faulty.

Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the cause of the fault.
Parameter 2 Indicates the location of the fault.

The NE may fail to work properly.
Possible Causes
Cause 1: The NE hardware is faulty.
Procedure
Step 1 Replace the NE.
----End
Related Information
None
A.2.48 HARD_ERR
Description
The HARD_ERR alarm indicates an hardware error. This alarm is reported when
there are minor hardware errors.

Attribute
Parameters
Name Meaning
● 0x14: The storage component is faulty.

Parameter 2 Indicates the location of the fault.
● When Parameter 1 is set to 0x01 and Parameter 2 is set to 0x01,

chip 7953 is faulty.
● When Parameter 1 is set to 0x01 and Parameter 2 is set to 0x02,
chip 7812 is faulty.
● When Parameter 1 is set to 0x14, Parameter 2 indicates the ID
of the faulty storage component.
Parameter 3 Reserved.

Generally, services are not affected.
Possible Causes
Cause: The board hardware is faulty.
Procedure
Step 1 Warm or cold reset the NE that reports the alarm on the NMS.
Step 2 If the alarm persists, replace the NE.
----End
Related Information
None.
A.2.49 IN_PWR_ABN
Description
The IN_PWR_ABN alarm indicates that the input optical power is abnormal.

Attribute
Parameters
Name Meaning
Parameter 1 For a CPRI port, indicates the type of the input optical power
abnormality.
● 0x00: Indicates that the input optical power is too low.
● 0x01: Indicates that the input optical power is too high.
For a non-CPRI port, no parameter is available.

Bit errors occur in the services at the port, which may lead to service interruption.
Possible Causes
● Cause 1: The transmit optical power of the opposite NE is beyond the allowed
range.
● Cause 2: Different optical modules are used at the local and remote ends.
● Cause 3: The receive optical module of the local NE is faulty.
Procedure
Step 1 Cause 1: The transmit optical power of the opposite NE is beyond the allowed
range.
1. Check whether the transmit optical power of the opposite NE is within the
allowed range. If it is beyond the allowed range, replace the optical module.
Step 2 Cause 2: Different optical modules are used at the local and remote ends.
1. Query the board manufacturing information report, and check whether the
same optical modules are used at the local and remote ends.
If... Then...
They are different Replace the optical module.
The modules are the same Go to Cause 3.
Step 3 Cause 3: The receive optical module of the local NE is faulty.

1. Use an optical power meter to measure the receive optical power, and check
whether the receive optical power meets the requirement. If it meets the
requirements, replace the SFP module.
----End
Related Information
None
A.2.50 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
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 engineers to
handle the alarm.
----End
Related Information
None
A.2.51 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 engineers to
handle the alarm.
----End
Related Information
None
A.2.52 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 engineers to handle the alarm.
----End
Related Information
None
A.2.53 LAG_DOWN
Description
The LAG_DOWN alarm indicates that a link aggregation group (LAG) is
unavailable. This alarm is reported when no member port in a LAG is activated.
Attribute
Parameters
None

Services at all ports in the LAG are interrupted.
Possible Causes
Cause 1: All member ports in the LAG fail.
Procedure
Step 1 Follow instructions in LAG_MEMBER_DOWN to troubleshoot each member port
in the LAG.
----End
Related Information
None

A.2.54 LAG_MEMBER_DOWN
Description
The LAG_MEMBER_DOWN alarm indicates that a member port in a link
aggregation group (LAG) is unavailable. This alarm is reported when a member
port in a LAG cannot be activated or cannot function as a standby port.
Attribute
Parameters
table.
Name Meaning
Parameters 1 and Indicate the slot ID of the board that reports the
2 LAG_MEMBER_DOWN alarm.
Parameter 3 This parameter has a fixed value of 0xff.
Parameters 4 and Indicate the ID of the port that reports the
5 LAG_MEMBER_DOWN alarm.
● 0x01: The port is in the link-down or disabled state.
● 0x02: The port receives no LACP packet.
● 0x03: The port works in half-duplex mode.
● 0x04: The port is self-looped.

The port in the LAG cannot share any service load. The port does not receive or
transmit any services.
Possible Causes
● Cause 1: The link connected to the port is faulty or blocked.
● Cause 2: The port does not receive any LACP packets.
● Cause 3: The port works in half-duplex mode.
● Cause 4: The port is self-looped.

Procedure
Step 1 Determine the alarmed port and the cause according to the alarm parameters.
If... Then...
The value of Parameter 6 is 0x01 Go to Step 2.
Step 2 Cause 1: The link connected to the alarmed port is faulty or blocked.
1. Check whether the port is enabled.
If... Then...
The port is disabled Enable the port in the LAG.
The port is enabled Go to the next step.
2. Check for ETH_LOS or MW_LOF alarms on all member ports.
If... Then...
The ETH_LOS or MW_LOF alarm Handle the ETH_LOS or MW_LOF
exists alarm.
The ETH_LOS or MW_LOF alarm does Go to Cause 2.
not exist
Step 3 Cause 2: The port does not receive any LACP packets.
1. Check whether the local and remote ports transmit any LACP packets. If they
do not transmit any LACP packets, reconfigure the ports at both ends so LACP
packets can be normally transmitted.
Step 4 Cause 3: The port works in half-duplex mode.
1. Check whether the local and remote ports work in half-duplex mode. If either
of them works in half-duplex mode, reconfigure it to work in full-duplex
mode.
Step 5 Cause 4: The port is self-looped.
1. Follow instructions in 7.4.1 Querying the Attributes of an Ethernet Port to
check whether the port is self-looped. If it is self-looped, release the loopback
at the port by referring to 7.1.1 Setting Port Loopbacks for NEs.
----End
Related Information
None

A.2.55 LASER_MOD_ERR
Description
The LASER_MOD_ERR alarm indicates that the small form-factor pluggable (SFP)
module mismatches the optical port.
Attribute
Parameters
None

The performance of the optical port deteriorates, which even causes service
interruption.
Possible Causes
● Cause 1: The NE does not support the type of the installed SFP module.
● Cause 2: The optical module is faulty.
Procedure
Step 1 Cause 1: The NE does not support the type of the installed SFP module.
1. Follow instructions in 6.6.2 Querying the Board Manufacturing Information
Report to check whether the optical module of the optical port matches the
rate of the optical port.
If... Then...
The optical module of the optical port does Contact Huawei engineers
not match the rate of the optical port to replace the optical
module.
The optical module of the optical port Go to Cause 2.
matches the rate of the optical port
Step 2 Cause 2: The optical module is faulty.

1. Replace the optical module.
If... Then...
The alarm clears No further action is required.

If... Then...
The alarm persists Go to Cause 3.
Step 3 Cause 3: The NE is faulty.

1. Replace the OptiX RTN 380.
----End
Related Information
None
A.2.56 LASER_SHUT
Description
The LASER_SHUT alarm indicates that a laser is shut down.
Attribute
Parameters
None

Shutting down a laser interrupts services on the corresponding port.
Possible Causes
● Cause 1. When the link-state pass through (LPT) function turns off the laser
of a port, an ETH_AUTO_LINK_DOWN alarm and a LASER_SHUT alarm are
generated. Suppressed by the ETH_AUTO_LINK_DOWN alarm, the
LASER_SHUT alarm is not reported. When the LPT function turns on the laser,
the ETH_AUTO_LINK_DOWN alarm is cleared and the LASER_SHUT alarm is
therefore reported. After the laser is on and a 10s alarm off-delay period
elapses, the LASER_SHUT alarm is automatically cleared.
● Cause 2: A microwave link that transmits CPRI services has a BER exceeding
10-4 or is interrupted, resulting in the shutdown of optical modules on the
CPRI ports.
Cause 1. When the link-state pass through (LPT) function turns off the laser of a
port, an ETH_AUTO_LINK_DOWN alarm and a LASER_SHUT alarm are generated.
Suppressed by the ETH_AUTO_LINK_DOWN alarm, the LASER_SHUT alarm is not
reported. When the LPT function turns on the laser, the ETH_AUTO_LINK_DOWN
alarm is cleared and the LASER_SHUT alarm is therefore reported. After the laser

is on and a 10s alarm off-delay period elapses, the LASER_SHUT alarm is

automatically cleared.
Procedure
Step 1 Cause 1. When the link-state pass through (LPT) function turns off the laser of a
port.
1. No handling is required, because the LASER_SHUT alarm is automatically
cleared after 10s.
Step 2 Cause 2: A microwave link that transmits CPRI services has a BER exceeding 10-4
or is interrupted, resulting in the shutdown of optical modules on the CPRI ports.
1. Query whether a MW_BER_EXC, MW_BER_SD, MW_LOF and R_LOF alarm is
reported from the microwave link. If such an alarm exists, clear the alarm.
----End
Related Information
None
A.2.57 LCS_DAYS_OF_GRACE
Description
The LCS_DAYS_OF_GRACE alarm indicates that the license file is invalid but
remains in the 60-day grace period.
Attribute
Parameters
table.
Name Meaning
Parameters 1 and Indicate the ID of the control item.
2
Parameters 3 and Indicate the number of remaining grace days.
4

Name Meaning
Parameter 5 Indicates the license file failure type.
● 0x00: The license file becomes invalid due to natural
expiration.
● 0x01: The license file is forcibly invalidated.
● 0x02: There is an ESN mismatch between the license file
and NE.
● 0x03: There is a V/R version mismatch between the license
file and NE.
● 0x04: The ESN and V/R version of the license file do not
match those of the NE.

NE functions are available, but this alarm is reported daily to remind the user to
update the license.
Possible Causes
● Cause 1: The license file is invalid but remains in the grace period.
● Cause 2: The ESN or V/R version of the license file does not match that of the
NE, but the NE remains in the grace period.
● Cause 3: A control item has expired but remains in the grace period.
Procedure
Step 1 Contact Huawei technical support engineers to reload the license file.
----End
Related Information
None
A.2.58 LCS_EXPIRED
Description
The LCS_EXPIRED alarm indicates that the license file is invalid and its 60-day
grace period has elapsed.
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 license file failure type.
● 0x00: The license file becomes invalid due to natural
expiration.
● 0x01: The license file is forcibly invalidated.
● 0x02: There is an ESN mismatch between the license file and
NE.
● 0x03: There is a V/R version mismatch between the license
file and NE.
● 0x04: The ESN and V/R version of the license file do not
match those of the NE.
● 0xff: Parameters 1 and 2 indicate the ID of the expired
license.

The NE enters the default state.
Possible Causes
● Cause 1: The license file has expired and its grace period has elapsed.
● Cause 2: The grace period of the license file whose ESN or V/R version does
not match that of the NE has elapsed.
Procedure
Step 1 Contact Huawei technical support engineers to reload the license file.
----End
Related Information
None
A.2.59 LCS_FILE_NOT_EXIST
Description
The LCS_FILE_NOT_EXIST alarm indicates that no license file is installed on the NE.

Attribute
Parameters
None

The NE enters the default state.
Possible Causes
The NE fails to find the required license file when being started.
Procedure
Step 1 Purchase and load the license file.
----End
Related Information
None
A.2.60 LCS_LIMITED
Description
The LCS_LIMITED alarm indicates that an NE is configured with a service capacity
or function beyond the license permission. This alarm is also reported on the
active NE in a 1+1 protection group when the standby NE has a licensed service
capacity less than the active NE.
Attribute
Parameters
table.

Name Meaning
Parameter 1 Indicates the license alarm type.

● 0x01: The service capacity is beyond the license permission.
● 0x02: The AM license is not loaded.
● 0x04: The 1588 V2 license is not loaded.
● 0x09: The license for air-interface frame header compression is
not loaded.
● 0x0a: The MPLS license is not loaded.
● 0x0b: The PLA license is not loaded.
● 0x0c: The total bandwidth for TDM services and data services on
the main and standby links is higher than the total bandwidth
for Ethernet services authorized by the license on the main and
standby links.
● 0x0d: The number of used GE ports exceeds the licensed
maximum.
● 0x0e: The XPIC license is not loaded.
● 0x0f: The ERPS license is not loaded.
● 0x11: The 1024QAM license is not loaded.
● 0x12: The license for 1+1 protection is not loaded.
● 0x13: The license for enhanced QoS is not loaded.
● 0x16: The MPLS-TP OAM is not loaded.
● 0x18: The AMAC license is not loaded.
● 0x1a: The HQoS license is not loaded.
● 0x22: The 62.5 MHz/125 MHz license is not loaded.
● 0x23: The license for 1.25 Gbit/s CPRI is not loaded.
● 0x24: The license for 2.5 Gbit/s CPRI is not loaded.
● 0x25: The license file for an extended 250 Mbit/s bandwidth is
not loaded.
● 0x26: The number of ports using the 2048QAM modulation
scheme exceeds the licensed number.
● 0x2a: The 2048QAM license is not loaded.
● 0x2b: The AES license is not loaded.
● 0x31: The CPRI license is not loaded.
● 0x34: The Y.1731-compliant bandwidth notification license is not
loaded.
● 0x36: The licensed maximum capacity for anti-theft function is
exceeded.

The alarmed NE is configured with a service capacity or function beyond the
license permission.

Possible Causes
● Cause 1: The corresponding license is not loaded.
● Cause 2: The service capacity or function is beyond the license permission.
Procedure
Step 1 Determine the license type according to the alarm parameters.
Step 2 If the value of the alarm parameter is 0x01 or 0x0c, decrease the service capacity
or purchase another license to expand the service capacity.
Step 3 If the value of the alarm parameter is not 0x01 and 0x0c, purchase and load the
corresponding license.
----End
Related Information
None
A.2.61 LCS_TRIAL_PERIOD
Description
The LCS_TRIAL_PERIOD alarm indicates that an NE is in the trial period. This alarm
is reported when an NE that is powered on and does not have a license is in the
trial period of 90 days.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the remaining trial period (days).

During a trial run period, an LCS_TRIAL_PERIOD alarm does not affect NE
functions.

After the trial run period expires, the NE reports an LCS_FILE_NOT_EXIST alarm
and enters the minimum-configuration state. Existing services are not affected;
however, configurations cannot be modified and no service can be added.
Possible Causes
Cause: An NE that is not loaded with a license is in the trial period of 90 days.
Procedure
Step 1 Purchase and load the license file.
----End
Related Information
None
A.2.62 LICENSE_LOST
Description
The LICENSE_LOST alarm indicates that the NE fails to detect the license file.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the license file.
● 0x06: NE license
● 0x07: ETH license

When the LICENSE_LOST alarm occurs, the functions authorized by the license file
cannot take effect.
Possible Causes
The license file is lost or is not loaded.

Procedure
Step 1 Contact Huawei engineers to reload the license file to the NE.
----End
Related Information
None
A.2.63 LOOP_ALM
Description
The LOOP_ALM alarm indicates that a loopback occurred.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the type of loopback.
● 0x00: composite inloops at microwave ports, or inloops at CPRI/

OBSAI optical ports
● 0x01: composite outloops at microwave ports, or outloops at
CPRI/OBSAI optical ports
● 0x14: outloops at IF ports
● 0x15: inloops at IF ports
● 0x16: inloops at RF ports

Services at the port that reports the LOOP_ALM alarm are interrupted.
Possible Causes
Cause 1: Loopback is performed on the NE.

Procedure
Step 1 Determine the type of loopback according to the alarm parameter.
Step 2 Find out why loopback was performed, and set the loopback status of the alarmed
port to Non-Loopback.
For details of loopback operations, see Software Loopback.
----End
Related Information
None
A.2.64 LSR_BCM_ALM
Description
The LSR_BCM_ALM is an alarm indicating a threshold-crossing of the bias current
of a laser of the SFP optical module. This alarm is reported when the bias current
of a laser exceeds the threshold.
Attribute
Parameters
None

When the alarm occurs during the data transmission, the optical module is aged
or faulty, which may cause packet loss or service interruption.
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 SFP Optical
Modules.
----End

Related Information
None
A.2.65 LSR_NO_FITED
Description
The LSR_NO_FITED alarm indicates that the small form-factor pluggable (SFP)
optical module is not installed in a port.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the MIMO port number. The value is 0x01 or 0x02.
NOTE
Parameters are displayed only when this alarm is reported by the MIMO
port.

The port cannot bear services.
Possible Causes
● Cause 1: No SFP optical module is installed for the alarmed port.
● Cause 2: The SFP optical module is faulty.
Procedure
Step 1 Cause 1: No SFP optical module is installed for the alarmed port.
1. Find out why no SFP optical module is installed, and install an SFP optical
module.
Step 2 Cause 2: The SFP optical module is faulty.
1. Replace the SFP optical module.
----End

Related Information
None
A.2.66 LSR_WILL_DIE
Description
The LSR_WILL_DIE alarm indicates that the laser is to stop working.
Attribute
Parameters
None

Bit errors occur after this alarm occurs. If the laser is not replaced immediately,
services will be interrupted after the laser stops working.
Possible Causes
● Cause 2: The detection circuit of the NE is faulty.
Procedure
Step 1 Cause 1: The laser is aged.
1. Perform the operations in Replacing an SFP Module.
Step 2 Cause 2: The detection circuit of the NE is faulty.

1. Perform the operations in Replacing an OptiX RTN 380.
----End
Related Information
None
A.2.67 LTI
Description
The LTI alarm indicates that an NE loses all synchronization sources.

Attribute
Parameters
table.
Name Meaning
Parameter 1 0x01: All synchronization sources in the clock source priority table
are lost.

The system clock quality does not meet requirements. The bit error rate will
increase when the NE is not synchronized with other NEs.
Possible Causes
● Cause 1: The clock configuration is incorrect.
● Cause 2: All the clock sources in the clock source priority table fail.
● Cause 3: The synchronization source is set to the manual reversion mode.
Procedure
Step 1 Cause 1: The clock configuration is incorrect.
1. Follow instructions in Configuring Clock Sources to check the clock source
priority table according to the network plan.
If... Then...
The clock source priority table is Re-configure the clock source
configured incorrectly priority table.
The clock source priority table is Go to Cause 2.
configured correctly
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
1. Check for and clear any SYNC_C_LOS alarms.
Step 3 Cause 3: The synchronization source is set to the manual reversion mode.

1. Follow instructions in Modifying Clock Source Reversion Parameters to set the

clock source to the automatic reversion mode.
----End
Related Information
None
A.2.68 MAC_EXT_EXC
Description
The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer
crosses the threshold.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the threshold crossing type.

● 0x01: ETHDROP threshold crossing
● 0x03: RXBBAD threshold crossing

Service performance deteriorates.
Possible Causes
● Cause 1: ETHDROP threshold crossing. The number of packet loss events
crosses the upper threshold.
● Cause 2: RXBBAD threshold crossing. The number of received bad packets
crosses the upper threshold.

Procedure
Step 1 Check whether the working modes of the ports at the transmit and receive ends
are the same.
1. On the NMS, query the working modes of the ports at both ends.
If... Then...
The ports at both ends work in Set the working modes of the two
different modes or in half-duplex ports to both full-duplex or auto-
mode negotiation by referring to Setting
the Basic Attributes for an Ethernet
Port.
The ports at both ends work in the Go to the next step.

same mode and are not working in
half-duplex mode
Step 2 Handle the packet transmission errors at the opposite end.
Step 3 Check whether PLA configurations are correct.
Check for and clear any MW_CFG_MISMATCH alarm and PLA_CFG_MISMATCH

alarm.
Step 4 Handle the line quality problem.
Check for and clear any alarms (ETH_LOS, ETH_LINK_DOWN, for example) at the
local end due to the damage to or large attenuation over the external line.
----End
Related Information
None
A.2.69 MAC_FCS_EXC
Description
The MAC_FCS_EXC alarm indicates that a bit error threshold-crossing event (based
on ETHFCS measurement results) is detected at the MAC layer. The software
periodically computes whether the number of bit errors crosses the threshold by
comparing the number of service bytes and the number of bit errors received on
the MAC chip.
Attribute

Parameters
Name Meaning
Parameter 1 ● 0x00: indicates that a performance threshold is crossed.
● 0x01: indicates bit-error-triggered switching.

Possible Causes
● Cause 1: Line signals deteriorate.
● Cause 2: Input optical power is abnormal.
● Cause 3: Fiber surface is dirty.
● Cause 4: PLA configurations are incorrect.
Procedure
Step 1 Cause 1: Line signals deteriorate.
1. On the NMS, check for and clear any LOOP_ALM alarm. Check whether the
MAC_FCS_EXC alarm clears. For details, see Setting Loopbacks for Ethernet
Ports.
2. If the alarm persists, check for and eliminate any unauthorized data sources
such as DOS attacks. Check whether the MAC_FCS_EXC alarm clears.
3. If the alarm persists, check for and replace any faulty cable or fiber. Check
whether the MAC_FCS_EXC alarm clears.
Step 2 Cause 2: Input optical power is abnormal.

1. Check whether the alarmed port also reports the IN_PWR_ABN alarm.
2. If the IN_PWR_ABN alarm is reported, clear the IN_PWR_ABN alarm and
check whether the MAC_FCS_EXC alarm clears.
Step 3 Cause 3: Fiber surface is dirty.

1. Clean the fiber surface.
Step 4 Cause 4: PLA configurations are incorrect.
Check for and clear any MW_CFG_MISMATCH and PLA_CFG_MISMATCH alarms.
----End
Related Information
None

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

Possible Causes
● Cause 1: Line signals degrade.
● Cause 2: Input optical power is abnormal.
● Cause 3: Fiber surface is 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 Setting Loopbacks for Ethernet
Ports.
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 alarmed port also reports the IN_PWR_ABN alarm.
2. If the IN_PWR_ABN alarm is reported, clear the IN_PWR_ABN alarm and
check whether the MAC_FCS_EXC alarm clears.
Step 3 Cause 3: Fiber surface is dirty.

1. Clean the fiber surface.
----End
Related Information
None
A.2.71 MOD_COM_FAIL
Description
The MOD_COM_FAIL alarm indicates that Module communicates abnormally.
Attribute
Parameters
table.
Name Meaning
Parameter 1 0x11 indicates that the communication between the system control
unit and packet switching unit is failed.

The related operations cannot be performed by using the NMS and the
performance information of each module cannot be queried.
Possible Causes
● Cause 1: The software processing of the related modules of the NE is faulty.
● Cause 2: The NE hardware is faulty.
Procedure
Step 1 4.1 Replacing an OptiX RTN 380.
----End

Related Information
None
A.2.72 MPLS_PW_AIS
Description
The MPLS_PW_AIS alarm indicates 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.
Step 2 Cause 2: An upstream NE detects a fault on the tunnel at the PW server layer.
1. Check whether a tunnel fault occurs on the S-PE. If an alarm such as
MPLS_TUNNEL_LOCV exists, clear the alarm immediately.
----End
Related Information
None

A.2.73 MPLS_PW_BDI
Description
The MPLS_PW_BDI alarm indicates 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...
The remote NE is reset or faulty Rectify the fault on the remote
NE.
The physical link between the local NE Rectify the fault on the physical
and the remote NE is faulty link.
The bandwidth allocated to the PW is Increase the bandwidth of the PW.
fully occupied.
----End
Related Information
None

A.2.74 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, ETH_LINK_DOWN
– Hardware-related alarm: HARD_BAD
– Alarm related to the IEEE 802.3ah protocol: ETH_EFM_DF,
ETH_EFM_LOOPBACK
----End
Related Information
None

A.2.75 MPLS_PW_Excess
Description
The MPLS_PW_Excess alarm indicates that excessive trail termination source
identifiers (TTSIs) are received on the PW. This alarm occurs when five or more
correct CV/FFD packets are received within three consecutive CV/FFD periods.
Attribute
Warning Communication alarm
Parameters
None

Services may be interrupted if excessive redundant packets are received.
Possible Causes
● 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.
3. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
Step 2 Cause 2: Physical links are misconnected.

1. Check whether any fiber or cable is misconnected.
2. If yes, rectify the fault.
----End
Related Information
None

A.2.76 MPLS_PW_LCK
Description
The MPLS_PW_LCK alarm indicates that a server layer tunnel is administratively
locked. This alarm is reported when the MEP receives a LCK message.
Attribute
Parameters
None

The server-layer tunnel is locked for diagnostic testing or other administrative
purposes.
Possible Causes
Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
Procedure
Step 1 Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
1. Check whether tunnel locking is enabled on the nodes along the PW path. If
yes, disable the CLK after administrative locking (for diagnostic testing or
other administrative purpose) is no longer needed.
----End
Related Information
None
A.2.77 MPLS_PW_LOCK
Description
The MPLS_PW_LOCK alarm indicates that the locked signal function (LCK) is
enabled for the PW layer.

Attribute
Parameters
None

The PW is locked for diagnostic testing or other administrative purposes.
Possible Causes
Cause 1: Administrative locking is enabled for the PW layer.
Procedure
Step 1 Cause 1: Administrative locking is enabled for the PW layer.
1. Check whether the LCK is enabled for the PW layer. If yes, disable the CLK
after administrative locking (for diagnostic testing or other administrative
purpose) is no longer needed.
----End
Related Information
None
A.2.78 MPLS_PW_LOCV
Description
The MPLS_PW_LOCV alarm indicates PW connectivity loss. This alarm occurs when
no expected CV/FFD packets are received within three consecutive CV/FFD periods.
Attribute
Parameters
None


When this alarm occurs, services are interrupted.
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
Step 1 Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
1. Check whether the remote NE of the PW stops transmitting CV/FFD packets.
If... Then...
The remote NE of the PW stops Enable the CV/FFD detection
transmitting CV/FFD packets and then check whether the
alarm clears.
The remote NE of the PW keeps Go to Cause 2.
transmitting CV/FFD packets
Step 2 Cause 2: The OAM is different between the ends of the PW.
1. Check whether the OAM is different between the ends of the PW. If no,
setting PW OAM (Y.1711) parameters according to the plan. If yes, go to
cause 3.
Step 3 Cause 3: The PW that carries services is faulty.

1. Check whether the local NE and remote NE of the PW report any alarm. If
yes, clear the alarm. Then, check whether the MPLS_PW_LOCV alarm is
cleared.
2. Check whether any link-related alarm is reported. If yes, clear the alarm.
Then, check whether the MPLS_PW_LOCV alarm is cleared.
If... Then...
The alarm is cleared End the alarm handling.
Step 4 Cause 4: The remote NE of the PW is faulty.

1. If the remote NE reports other alarms, clear these alarms. Then, check
whether the MPLS_PW_LOCV alarm is cleared.
If... Then...

If... Then...
Step 5 Cause 5: The service interface is configured incorrectly.

1. Check whether the service interface is configured correctly according to
service planning.
2. If not, reconfigure the service interface. Then, check whether the
MPLS_PW_LOCV alarm is cleared.
If... Then...
Step 6 Cause 6: Serious congestion occurs on the network.

1. Check whether the bandwidth allocated to the faulty tunnel is fully occupied.
2. If yes, increase the bandwidth of the PW or eliminate the sources that
transmit a large amount of invalid data.
----End
Related Information
None
A.2.79 MPLS_PW_MISMATCH
Description
The MPLS_PW_MISMATCH alarm indicates 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
Attribute
Parameters
None

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
A.2.80 MPLS_PW_MISMERGE
Description
The MPLS_PW_MISMERGE alarm indicates 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
None

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 is configured correctly according to NE planning.
2. If the PW is configured incorrectly, correct the configuration and then check

----End
Related Information
None
A.2.81 MPLS_PW_OAMFAIL
Description
The MPLS_PW_OAMFAIL alarm indicates 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 A.2.97
MPLS_TUNNEL_OAMFAIL occur on NEs at both ends of the PW. If yes, clear
them immediately.
2. Check whether service-related alarms such as A.2.78 MPLS_PW_LOCV occur
on NEs at both ends of the PW. If yes, clear them immediately.
----End
Related Information
None
A.2.82 MPLS_PW_RDI
Description
The MPLS_PW_RDI alarm indicates a defect in the backward direction of a PW.
The remote MEP sends an RDI packet to the local MEP when detecting a PW fault.
The MPLS_PW_RDI alarm is reported when the local MEP receives the RDI packet.
Attribute
Parameters
None


When this alarm occurs, services in the transmit direction on the remote MEP are
affected.
Possible Causes
The local MEP NE detects a PW fault.
Procedure
Step 1 Handle the PW fault according to the MPLS-TP OAM-related alarm reported by
the remote MEP.
Step 2 If the alarm persists, check whether the physical link between faulty NEs is faulty.
For example, the optical fiber or cable is damaged or pressed. If yes, replace the
faulty optical fiber or cable.
Step 3 Check whether the bandwidth allocated to the PW is used up. If yes, increase the
bandwidth allocated to the PW.
----End
Related Information
None
A.2.83 MPLS_PW_SD
Description
The MPLS_PW_SD alarm indicates 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.
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.
----End
Related Information
None
A.2.84 MPLS_PW_SF
Description
The MPLS_PW_SF alarm indicates 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.
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.
----End
Related Information
None
A.2.85 MPLS_PW_UNEXPMEG
Description
The MPLS_PW_UNEXPMEG alarm indicates that the MEP receives a packet with
correct MEG level but incorrect MEG ID.
Attribute
Parameters
None

When this alarm occurs, the MEP receives CCM packets of other PWs.
Possible Causes
● 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
A.2.86 MPLS_PW_UNEXPMEP
Description
The MPLS_PW_UNEXPMEP alarm indicates an error in the PW OAM CCM
information. This alarm is reported when the sink NE of the PW receives a CCM
packet with an unexpected MEP ID.
Attribute
Parameters
None

When this alarm occurs, services are interrupted or the sink NE receives CCM
packets of other PWs.
Possible Causes
MEP IDs are inconsistent between NEs at both ends of a PW.
Procedure
Step 1 MEP IDs are inconsistent between NEs at both ends of a PW.

1. Check whether the remote MEP ID on the source NE is correctly configured

with the MEP ID of the sink NE. If not, reconfigure the remote MEP ID on the
source NE.
----End
Related Information
None
A.2.87 MPLS_PW_UNEXPPER
Description
The MPLS_PW_UNEXPPER alarm indicates 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.
----End

Related Information
None
A.2.88 MPLS_PW_UNKNOWN
Description
The MPLS_PW_UNKNOWN alarm indicates unknown defects on the PW. This
alarm occurs when the connectivity check (CC) packets of unexpected types,
periods, and values are received within three consecutive periods.
Attribute
Parameters
None

PW OAM fails.
Possible Causes
Cause 1: The PW OAM configuration at the two ends is different.
Procedure
Step 1 Cause 1: The PW OAM configuration at the two ends is different.
1. Change the PW OAM configuration to the same at the two ends.
----End
Related Information
None
A.2.89 MPLS_TUNNEL_AIS
Description
The MPLS_TUNNEL_AIS alarm indicates 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

When this alarm occurs, services are interrupted.
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 NE. If yes, rectify the faults.
----End
Related Information
None
A.2.90 MPLS_TUNNEL_BDI
Description
The MPLS_TUNNEL_BDI alarm indicates tunnel backward defect indication. This
alarm occurs when the port of the local NE receives the backward defect
indication (BDI) packet, notifying that the opposite NE detects that the tunnel is
faulty.
Attribute

Parameters
None

When this alarm occurs, the services on the local NE is normal.
Possible Causes
Cause 1: The opposite NE detects MPLS alarms.
Procedure
Step 1 Cause 1: The opposite NE detects MPLS alarms.
1. Clear the MPLS alarms reported on the opposite NE.
----End
Related Information
None
A.2.91 MPLS_TUNNEL_Excess
Description
The MPLS_TUNNEL_Excess alarm indicates 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
Attribute
Warning Communication alarm
Parameters
None

Services may be interrupted if excessive redundant packets are received.
Possible Causes

Procedure
1. Check whether any fiber or cable is misconnected between the two ends. If
yes, reconnect the fiber or cable.
----End
Related Information
None
A.2.92 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
Step 1 Cause 1: The upstream NE detects that the physical link that carries the tunnel is
faulty.
If... Then...
The link-related alarms, such as MW_BER_EXC, Clear these alarms
MW_BER_SD, MW_FEC_UNCOR and MW_LOF, are first.
reported
The local NE reports hardware-related alarms, such as Clear these alarms
HARD_BAD and LSR_NO_FITED first.
----End
Related Information
None
A.2.93 MPLS_TUNNEL_LOCK
Description
The MPLS_TUNNEL_LOCK alarm the locked signal function (LCK) is enabled for a
tunnel.
Attribute
Parameters
None

The tunnel is locked for diagnostic testing or other administrative purposes.
Possible Causes
Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.

Procedure
Step 1 Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.
1. Check whether the LCK is enabled for the tunnel layer. If yes, disable the CLK
after administrative locking (for diagnostic testing or other administrative
purpose) is no longer needed.
----End
Related Information
None
A.2.94 MPLS_TUNNEL_LOCV
Description
The MPLS_TUNNEL_LOCV alarm indicates 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 3: A certain board is faulty.
● Cause 4: The physical link between the two ends is faulty.
Procedure
Step 1 Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection
packet type and detection packet period, differ at the two ends.
1. Check whether the MPLS OAM settings are the same at the two ends.

2. If the MPLS OAM settings are different at the two ends, change them to the
same.
If... Then...
Step 2 Cause 2: Severe congestion occurs on the network.

1. If the alarm persists, check whether the bandwidth allocated to the faulty
tunnel is fully used. If the bandwidth of the faulty tunnel is exhausted,
increase the bandwidth or eliminate the sources that transmit a large amount
of invalid data.
If... Then...
Step 3 Cause 3: A certain board is faulty.

1. Check for and clear any hardware alarms on the local and remote NEs, such
as HARD_BAD.
2. Then, check whether the MPLS_TUNNEL_LOCV alarm clears.
If... Then...
Step 4 Cause 4: The physical link between the two ends is faulty.
1. Check whether any fiber or cable is damaged. If yes, replace the damaged
fiber or cable.
----End
Related Information
None
A.2.95 MPLS_TUNNEL_MISMATCH
Description
The MPLS_TUNNEL_MISMATCH alarm indicates that the trail termination source
identifiers (TTSIs) on the tunnel do not match with the specified one. This alarm is
reported if no CV/FFD packets with correct TTSIs are received in three consecutive
CV/FFD periods.

Attribute
Parameters
None

When this alarm occurs, services are interrupted or packets from other tunnels are
received.
Possible Causes
● 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
A.2.96 MPLS_TUNNEL_MISMERGE
Description
The MPLS_TUNNEL_MISMERGE alarm indicates 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
Attribute
Parameters
None

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.
A.2.97 MPLS_TUNNEL_OAMFAIL
Description
The MPLS_TUNNEL_OAMFAIL alarm indicates 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, R_LOS alarm.
2. If yes, clear the alarm. After the OAM protocol negotiation succeeds, the
MPLS_TUNNEL_OAMFAIL alarm clears.
----End
Related Information
None
A.2.98 MPLS_TUNNEL_RDI
Description
The MPLS_TUNNEL_RDI alarm indicates a defect in the backward direction of a
tunnel. The local MEP sends an RDI packet to the remote MEP when detecting a
tunnel fault. The MPLS_TUNNEL_RDI alarm is reported when the remote MEP
receives the RDI packet.

Attribute
Parameters
None

When this alarm occurs, services are affected in the transmit direction on the
remote MEP.
Possible Causes
The local MEP NE detects a tunnel fault.
Procedure
Step 1 Handle the tunnel fault according to the MPLS-TP OAM-related alarm reported by
the remote MEP. Then, check whether the MPLS_TUNNEL_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the physical link is faulty between faulty NEs.
For example, the optical fiber or cable is damaged or pressed. If yes, replace the
faulty optical fiber or cable.
----End
Related Information
None
A.2.99 MPLS_TUNNEL_SD
Description
The MPLS_TUNNEL_SD alarm indicates 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
A.2.100 MPLS_TUNNEL_SF
Description
The MPLS_TUNNEL_SF alarm indicates 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
A.2.101 MPLS_TUNNEL_UNEXPMEG
Description
The MPLS_TUNNEL_UNEXPMEG alarm indicates an error in the tunnel OAM CCM
information. This alarm is reported when the sink NE receives a CCM packet with
an unexpected MEG ID.
Attribute
Parameters
None

When this alarm occurs, the sink NE receives CCM packets of other tunnels.

Possible Causes
● 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.
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.
----End
Related Information
None
A.2.102 MPLS_TUNNEL_UNEXPMEP
Description
The MPLS_TUNNEL_UNEXPMEP alarm indicates an error in the tunnel OAM CCM
information. This alarm is reported when the sink NE receives a CCM packet with
an unexpected MEP ID.
Attribute
Parameters
None

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
A.2.103 MPLS_TUNNEL_UNEXPPER
Description
The MPLS_TUNNEL_UNEXPPER alarm indicates 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.
----End
Related Information
None
A.2.104 MPLS_TUNNEL_UNKNOWN
Description
The MPLS_TUNNEL_UNKNOWN alarm indicates 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
A.2.105 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER alarm indicates that an Ethernet ring network contains
more than one ring protection link (RPL) owner node.
Attribute
Parameters
table.
Name Meaning
Parameters 1 and 2 Indicate the ID of the Ethernet ring protection (ERP)
instance.

Ethernet ring protection switching (ERPS) protection fails and the services on the
Ethernet ring are interrupted.
Possible Causes
Cause: ERPS protection configurations are incorrect.
Procedure
Step 1 Follow instructions in Querying the ERPS Status to check ERPS protection
configurations at each node. Ensure that there is only one RPL owner node on the
Ethernet ring network.
----End

Related Information
None
A.2.106 MW_AM_TEST
Description
The MW_AM_TEST alarm indicates that an IF port is in the AM testing state.
Attribute
Minor Other alarms
Parameters
None

Service transmission capacity decreases during the AM test.
Possible Causes
Cause 1: An AM test is being performed.
Procedure
Step 1 This alarm is automatically cleared after the AM test is complete.
----End
Related Information
None
A.2.107 MW_BER_EXC
Description
The MW_BER_EXC alarm indicates that the number of bit errors on a microwave
link crosses the specified alarming threshold (10-3 by default).
Attribute
Minor QoS alarm

Parameters
None

Bit errors occur in the services at the port that reports the MW_BER_EXC alarm.
Possible Causes
● Cause 1: Signal attenuation on the microwave link is too heavy.
● Cause 2: The transmit unit of the opposite end is faulty.
● Cause 3: The receive unit of the local end is faulty.
● Cause 4: An interference source exists around the microwave link.
Procedure
Step 1 Cause 1: Signal attenuation on the microwave link is too heavy.
1. Follow instructions in 6.2.1 Browsing Historical Transmit Power and
Receive Power to check whether the receive power of the OptiX RTN 380 at
the local end is normal. Diagnose any faults.
If... Then...
The received signal level Perform the following steps:

(RSL) is lower than the
receiver sensitivity 1. Check the installation of the antenna to ensure
that the azimuth angle of the antenna meets the
requirement.
2. Check the antenna direction. Especially, 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 the polarization direction of antennas and
adjust the incorrect polarization direction.
4. Check the antenna gain at the two ends and
replace the antennas that do not provide required
antenna gain.
5. Check whether transmission is blocked by any
mountains or buildings.
Contact the network planning department for
avoiding the block if any.

If... Then...
The RSL is higher than Slow up fading occurs. Perform the following steps:
the specified RSL of the
network. The offset 1. Check for interference. For details, see 7.3.2
value is tens of decibels. Scanning Interfering Signals.
The duration is from tens 2. Use a spectrum analyzer to analyze interference
of seconds to several sources.
hours 3. Contact the spectrum management department
to clear the interference spectrum, or change
plans to minimize the interference.
The RSL is lower than Slow down fading occurs. Generally, the microwave
the specified RSL of the link may be faulty in both directions, because slow
network. The offset down fading is imposed by the transmission path.
value is tens of decibels. Contact the network planning department to make
The duration is from tens the following changes:
of seconds to several
hours ● Increase the installation heights of antennas.
● Reduce the transmission distance.
● Increase the antenna gain.
● Increase the transmit power.
The RSL is lower than or Fast fading occurs. Contact the network planning
higher than the specified department to make the following changes:
RSL of the network and
the duration is from ● Adjust the position of the antenna to block the
several milliseconds to reflected wave or make the reflection point fall
tens of seconds on the ground that has a small reflection
coefficient, reducing multipath fading.
● Increase the fading margin.
Step 2 Cause 2: The transmit unit of the opposite end is faulty.
Replace the NE.
Step 3 Cause 3: The receive unit of the local end is faulty.
Replace the NE.
Step 4 Cause 4: An interference source exists around the microwave link.

1. Follow instructions in 7.3.2 Scanning Interfering Signals to scan the
frequency spectrum around the microwave link and check for co-channel
interference and adjacent-channel interference.
2. Use a spectrum analyzer to analyze interference sources.
3. Contact the spectrum management department to clear the interference
spectrum, or change plans to minimize the interference.
----End
Related Information
None.

A.2.108 MW_BER_SD
Description
The MW_BER_SD alarm indicates signal degrade on a microwave link. This alarm
is reported when the number of bit errors on a microwave link crosses the
MW_BER_SD alarming threshold (10-6 by default) but does not reach the
MW_BER_EXC alarming threshold (10-3 by default).
Attribute
Minor QoS alarm
Parameters
None

Service performance on the port that reports the MW_BER_SD alarm deteriorates.
Possible Causes
Procedure

If... Then...

requirement.
lobe.
antenna gain.

If... Then...
Replace the NE.
Replace the NE.

----End
Related Information
None.
A.2.109 MW_CFG_MISMATCH
Description
The MW_CFG_MISMATCH alarm indicates that two ends of a microwave link are
inconsistently configured.
Attribute
Parameters


table.
Name Meaning
Parameter 1 Indicates the cause of the alarm.

● 0x02: The AM or adaptive modulation and adaptive channel
space (AMAC) is enabled at only one end of the microwave link.
● 0x03: The 1588 IEEE 1588 timeslot is enabled at only one end of
the microwave link.
● 0x04: The modulation scheme is inconsistently configured at the
two ends of the microwave link.
● 0x05: The channel spacing is inconsistently configured at the
two ends of the microwave link.
● 0x09: IP frame header compression is enabled at only one end
of the microwave link.
● 0x0a: AES is inconsistently configured at the two ends of the
microwave link.
● 0x0b: CPRI is enabled at one end but disabled at the other end
of a microwave link.
● 0x0c: The CPRI rate settings are different at the two ends of a
microwave link.
Parameter 2 When the value of Parameter 1 is 0x09, the values of Parameter 2

and their meanings are as follows:
● 0x01: L2 frame header compression is configured inconsistently.
● 0x02: L3 frame header compression is configured inconsistently.
When Parameter 1 is 0x0a, the values of Parameter 2 and their
meanings are as follows:
● 0x01: AES is enabled at only one end of the link.
● 0x02: AES authentication code is configured inconsistently.
When parameter 1 is 0x0b or 0x0c, Parameter 2 indicates the port
number 0x03.

Service configurations do not take effect or services are interrupted. After the NE
is power cycled or reset, the services may still be affected.
Possible Causes
● Cause 1: The AM or AMAC status is configured inconsistently at the two ends.
● Cause 2: The modulation scheme is configured inconsistently at the two ends.
● Cause 3: The channel spacing is configured inconsistently.
● Cause 4: The IEEE 1588 timeslot is enabled at only one end.

● Cause 5: IP frame header compression is enabled at only one end of the

microwave link.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters.
Step 2 Configure related parameters consistently at the two ends.

● For causes 1, 2, 3, handle the alarm by following instructions in Managing a
Hop of Microwave Link.
● For cause 4, configure ports at the two ends as PTP or non-PTP ports by
following instructions in Creating a PTP Clock Port.
● For cause 5, handle the alarm by following instructions in Configuring
Ethernet Frame Header Compression and Error Frame Discarding at an Air
Interface.
----End
Related Information
If both the MW_CFG_MISMATCH and MW_LOF alarms are generated,
preferentially handle the MW_LOF alarm.
A.2.110 MW_CONT_WAVE
Description
The MW_CONT_WAVE alarm indicates that an IF unit outputs continuous waves.
Attribute
Parameters
None

The involved microwave link cannot transmit services.
Possible Causes
● Cause 1: The continuous wave function is enabled.
● Cause 2: The IF unit is faulty.

Procedure
Step 1 Cause 1: The continuous wave function is enabled.
1. Disable the continuous wave function by following instructions in 7.3.5
Enabling the Consecutive Wave Detection Function.
Step 2 Cause 2: The IF unit is faulty.
1. Replace the NE.
----End
Related Information
The continuous wave function tests the frequency stability and frequency
consistency and should be disabled after a test is complete.
A.2.111 MW_FEC_EXC
Description
The MW_FEC_EXC alarm indicates that the bit error rate of microwave forward
error correction (FEC) exceeds the threshold.
Attribute
Minor QoS alarm
Parameters
None

If EPLA is configured and FEC switching is enabled on the links, this alarm will
trigger an EPLA protection switching.
Possible Causes
● Cause 1: Signal attenuation on the radio link is very heavy.
● Cause 2: The transmit unit of the opposite station is faulty.
● Cause 3: The receive unit of the local site is faulty.
● Cause 4: An interference event occurs.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is very heavy.
1. At the local end, check whether the receive power is normal. If yes, determine
the abnormality and take proper measures.

If... Then...
The RSL is lower than Follow the steps:

the receiver sensitivity
1. Check the installation of the antenna to ensure that
the azimuth angle of the antenna meets the
requirement.
2. Check the antenna direction. Check whether the
received signal is from the main lobe.
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 Slow up fading occurs. Follow the steps:
the specified RSL of
the network. The 1. Check whether intra-frequency or inter-frequency
offset value is tens of interference exists by scanning frequency spectra in
decibels. The duration microwave channels. For details, see 7.3.2 Scanning
is from tens of seconds Interfering Signals.
to several hours. 2. Use a spectrum analyzer to analyze interference
sources.
3. Contact the spectrum management department to
clear the interference spectrum or change plans to
minimize the interference.
The RSL is lower than Slow down fading occurs. Generally, the radio link may
the specified RSL of be faulty in both directions, because slow fading is
the network. The imposed by the transmission path. Contact the
offset value is tens of network planning department to make the following
decibels. The duration changes:
is from tens of seconds
to several hours. ● Increase the installation height of the antenna.

If... Then...
If the RSL is lower than Fast fading occurs. Contact the network planning
or higher than the department to make the following changes:
specified RSL of the
network and if the ● Adjust the position of the antenna to block the
duration is from reflected wave or make the reflection point fall on
several milliseconds to the ground that has a small reflection coefficient,
tens of seconds. reducing 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.
Step 2 Cause 2: The transmit unit of the opposite station is faulty.
Locate the fault by looping back the opposite station and excluding the position
one by one. Follow the steps:
1. Perform an inloop on the IF port at the opposite end. For details, see 7.1.1
Setting Port Loopbacks for NEs. Check whether the fault at the opposite end
is rectified after the loopback.
If... Then...
The fault at the opposite end is not Replace the NE at the opposite
rectified end.
The fault at the opposite end is Go to the next step.
rectified
Step 3 Cause 3: The receive unit of the local site is faulty.
Locate the fault by looping back the opposite station and excluding the position
one by one. Follow the steps:
1. Perform an inloop on the IF port at the local end. For details, see 7.1.1
Setting Port Loopbacks for NEs. Check whether the fault at the local end is
rectified after the loopback.
If... Then...
The fault at the opposite end is not Replace the NE at the local
rectified end.
The fault at the opposite end is Go to the next step.
rectified
Step 4 Cause 4: An interference event occurs.

1. Check for co-channel interference. For details, see 7.3.2 Scanning Interfering
Signals.


spectrum or change plans to minimize the interference.
----End
Related Information
None
A.2.112 MW_FEC_UNCOR
Description
The MW_FEC_UNCOR alarm indicates that errors in microwave frames cannot be
corrected by using forward error correction (FEC).
Attribute
Parameters
None.

This alarm indicates that services contain bit errors.
Possible Causes
Procedure

If... Then...

requirement.
lobe.
antenna gain.

If... Then...
Replace the NE.
Replace the NE.

----End
Related Information
None
A.2.113 MW_LIM
Description
The MW_LIM alarm indicates a microwave link ID mismatch. This alarm is
reported if the link ID in the overheads of received microwave frames is
inconsistent with the specified value at the local end.
Attribute
Parameters
None


The services on the microwave link are interrupted.
Possible Causes
● Cause 1: The link ID of the local end is different from the link ID of the peer
end.
● Cause 2: Microwave signals on other microwave links are received because
microwave link receive frequencies at the local or peer end are incorrectly
configured.
● Cause 3: The antenna receives microwave signals from another site because
the direction of the antenna is set incorrectly.
Procedure
Step 1 Cause 1 or 2: The link ID of the local end is different from the link ID of the
opposite end or microwave signals on other microwave links are received because
microwave link receive frequencies at the local or peer end are incorrectly
configured.
1. Follow instructions in Configuring a Single Hop of Microwave Link to check
the settings of link ID, receive/transmit frequency at the two ends. If any
setting is incorrect, modify it according to the network plan.
Step 2 Cause 3: The antenna receives microwave signals from another site 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.
----End
A.2.114 MW_LOF
Description
The MW_LOF alarm indicates loss of microwave frames.
Attribute
Parameters
None

Services are interrupted. If the system is configured with protection, protection
switching may be triggered.

Possible Causes
● Cause 1: Other alarms are reported.
● Cause 2: Channel spacing, modulation scheme, and operating frequency are
inconsistently configured at the two ends of the microwave link.
● Cause 3: The transmit unit of the NE at the opposite end is faulty.
● Cause 4: The receive power of the NE at the local end is abnormal.
Procedure
Step 1 Cause 1: Other alarms are reported.
1. Check for and clear any equipment-related alarms at the local end.
The possible alarms are as follows:
– HARD_BAD
– RADIO_RSL_LOW
– TEMP_ALARM
Step 2 Cause 2: Channel spacing, modulation scheme, and operating frequency are
inconsistently configured at the two ends of the microwave link.
1. Check whether the channel spacing, modulation scheme, and OptiX RTN 380
operating frequency are consistently configured at two ends of the microwave
link by following instructions in Configuring a Single Hop of Microwave Link.
Re-configure the inconsistent data if any.
Step 3 Cause 3: The transmit unit of the NE at the opposite end is faulty.
1. Check for and clear any equipment-related alarms at the opposite end.
The possible alarms are as follows:
– HARD_BAD
– RADIO_TSL_HIGH or RADIO_TSL_LOW
– TEMP_ALARM
2. Locate the fault by performing loopbacks at the opposite end.
Perform the following steps:
a. Perform an inloop on the IF port at the opposite end by referring to

Setting Loopback for the IF Board. Check whether the fault at the
opposite end is rectified.
If... Then...
The alarm persists Replace the NE at the opposite end.
The alarm is cleared Go to the next step.
Step 4 Cause 4: The receive power of the NE at the local end is abnormal.

If... Then...
The received signal Perform the following steps:

level (RSL) is lower
than the receiver 1. Check the installation of the antenna to
sensitivity ensure that the azimuth angle of the antenna
meets the requirement.
lobe.
requirement, adjust the antenna in a wide
range.
3. Check the polarization direction of antennas
and adjust the incorrect polarization direction.
replace the antennas that do not provide
required antenna gain.
The RSL is higher than Slow up fading occurs. Perform the following
the specified RSL of the steps:
network. The offset
value is tens of 1. Check for co-channel interference. For details,
decibels. The duration is see 7.3.2 Scanning Interfering Signals.
from tens of seconds to 2. Use a spectrum analyzer to analyze
several hours interference sources.
3. Contact the spectrum management
department to clear the interference spectrum,
or change plans to minimize the interference.
The RSL is lower than Slow down fading occurs. Generally, the
the specified RSL of the microwave link may be faulty in both directions,
network. The offset because slow down fading is imposed by the
value is tens of transmission path. Contact the network planning
decibels. The duration is department to make the following changes:
from tens of seconds to
several hours – Increase the installation heights of antennas.
– Reduce the transmission distance.
– Increase the antenna gain.
– Increase the transmit power.

If... Then...
The RSL is lower than Fast fading occurs. Contact the network planning
or higher than the department to make the following changes:
specified RSL of the
network and the – Adjust the position of the antenna to block
duration is from several the reflected wave or make the reflection
milliseconds to tens of point fall on the ground that has a small
seconds reflection coefficient, reducing multipath
fading.
– Increase the fading margin.
Step 5 Cause 5: Interference exists.

----End
Related Information
None
A.2.115 MW_RDI
Description
The MW_RDI alarm indicates that defects exist at the remote end of a microwave
link. This alarm is reported when an NE detects an RDI in the radio frame
overheads.
Attribute
Parameters
None

● If the NEs are enabled with reverse switching, a 1+1 HSB switchover is
triggered when main and standby NEs receive MW_RDI alarms at the same
time.
● Services are interrupted in the receive direction of the opposite end.

Possible Causes
Cause 1: The opposite site detects service alarms in the receive direction.
Procedure
Step 1 Handle the microwave alarms at the opposite site. The possible alarms are as
follows:
● MW_LOF
● R_LOF
----End
Related Information
None
A.2.116 NB_CFG_MISMATCH
Description
The NB_CFG_MISMATCH alarm indicates that two NEs in a PLA or 1+1 protection
group are inconsistently configured.
Attribute
Parameters
table.
Name Meaning
Parameter 1 ● 0x01: The two NEs in a PLA group are inconsistently configured.
● 0x02: The two NEs in a 1+1 protection group are inconsistently
configured.
● 0x04: The two adjacent NEs have different physical clock
configurations.
● 0x05: The two NEs in a 1+1 protection group have different
service configurations.

Name Meaning
Parameter 2 When Parameter 1 is 0x01, Parameter 2 has the following

meanings:
● 0x01: The two NEs are configured as the main or standby NE.
● 0x02: The two NEs have different cascading port IDs.
● 0x03: The two NEs have different microwave port IDs.
● 0x04: The two NEs have different service port IDs.
● 0x05: The two NEs have different types of service ports.
● 0x06: The two NEs use different protection schemes.
● 0x07: The two NEs have different minimum active links.
● 0x08: The two NEs work in different modes.
● 0x09: The two NEs are configured with different service modes
on IF boards.
● 0x0A: The two NEs have different IF bandwidths.
● 0x0B: L2 header compression is enabled for only one NE.
● 0x0C: L3 header compression is enabled for only one NE.
● 0x0D: 1588 overhead is enabled for only one NE.
● 0x0E: Neighboring NEs have different numbers of service ports.
● 0x0F: The configured aggregation group types are inconsistent.
● 0x10: The two NEs have different cascading attributes.
● 0x11: The total air-interface ETH bandwidth of cascade
members exceeds the cascade port rate. (The cascade port rates
of 1G, 2.5G, and 10G are treated as 647M, 1.638G, and 6.593G
respectively.)
● 0x12: The extended running modes are inconsistent.
When Parameter 1 is 0x02, Parameter 2 has the following
meanings:
● 0x01: The two NEs use different protection schemes.
● 0x02: The two NEs have different main/standby attributes.
● 0x03: The two NEs work in different revertive modes.
● 0x04: The two NEs have different wait to restore (WTR) time.
● 0x05: The two NEs have different numbers of service ports.
● 0x06: The two NEs have different service port IDs.
● 0x07: Reverse switching is enabled for only one NE.
● 0x08: The two NEs have different application scenarios.
● 0x09: L2 header compression is enabled for only one NE.
● 0x0A: L3 header compression is enabled for only one NE.
● 0x0B: 1588 overhead is enabled for only one NE.
● 0x0C: The cascade port numbers on the adjacent NEs are
different.
● 0x0D: AES is enabled for only one NE.

Name Meaning
● 0x0E: The two NEs have different key negotiate intervals.
● 0x0F: The two NEs have different AES authentication codes.
● 0x10: The two NEs have different IF port IDs.
When Parameter 1 is 0x04, Parameter 2 has the following
meanings:
● 0x01: The two NEs assign different default quality levels to
clocks with unknown quality levels.
● 0x02: The two NEs work in different revertive modes.
● 0x03: The two NEs work in different S1 byte modes.
● 0x04: The two NEs have different WTR time.
● 0x05: The two NEs have different manually specified clock
qualities.
● 0x06: The two NEs have different clock lock settings.
● 0x07: The two NEs have different manually specified clock IDs.
● 0x08: The two NEs have different S1 byte output disabling
settings.
● 0x09: The two NEs have different S1 byte ID output disabling
settings.
● 0x0A: The two NEs have different clock priority tables.
● 0x0B: The two NEs work in different clock control modes.

● This alarm may cause a 1+1 protection or PLA protection failure.
● When an NB_CFG_MISMATCH alarm is reported, a 1+1 protection or PLA
switchover may interrupt services. Therefore, it is advisable to clear this alarm
before triggering a 1+1 protection or PLA switchover.
Possible Causes
● Cause 1: The two NEs in a 1+1 protection group are inconsistently configured.
● Cause 2: The two NEs have different physical clock settings.
● Cause 3: The two NEs in a 1+1 protection group have different service
configurations.
● Cause 4: The two NEs in a PLA group are inconsistently configured.
Procedure
Step 1 Determine the possible cause of the alarm according to the alarm parameters.
Step 2 Configure related parameters consistently for the two NEs in a PLA or 1+1
protection group.
● If the alarm is reported due to Cause 1, configure the two NEs consistently by
following instructions in Synchronizing Data Between the Main and Standby
NEs in a 1+1 Protection Group.

following instructions in Configuring Clocks.
● If the alarm is reported due to Cause 3, verify that the two NEs in the 1+1
protection group are consistently configured by following instructions in
Synchronize data between the main and standby NEs in the 1+1 protection
group.
If you perform this step, the NB_CFG_MISMATCH alarm is cleared immediately. If you
do not perform this step, the NB_CFG_MISMATCH alarm is cleared ten minutes later.
following instructions in Creating a PLA group.
----End
Related Information
None
A.2.117 NB_UNREACHABLE
Description
The NB_UNREACHABLE alarm indicates that a neighboring NE in a protection
group is unreachable to the local NE.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the faulty board on the cascading channel.
Parameter 2 Indicates the ID of the faulty subboard on the cascading channel.
Parameter 3 Indicates the number of the faulty port on the cascading channel.

None

Possible Causes
● Cause 1: The other NE in the protection group is faulty.
● Cause 2: The cascade port has no optical module.
● Cause 3: The cascading cable is loose or damaged.
Procedure
Step 1 Cause 1: The other NE in the protection group is faulty.
1. Troubleshoot the fault on the other NE.
Step 2 Cause 2: The cascade port has no optical module.

1. Find out why the port has no optical module and install an optical module for
the port.
Step 3 Cause 3: The cascading cable is loose or damaged.

1. Check the cascading cable. If the cable is loose or damaged, re-connect or
replace it.
----End
Related Information
None
A.2.118 NE_DCN_MODE
Description
The NE_DCN_MODE alarm indicates that an NE works in minimum DCN mode.
Attribute
Parameters
None

The NE's DCN communication is normal, but its services may be interrupted.
Possible Causes
The NE is unexpectedly reset frequently.

Procedure
Step 1 Use the fault data collection tool integrated on the NMS to collect NE data and
upload the NE data to the NMS. The NE data is used for analyzing and locating
NE faults.
Step 2 If NE databases have been backed up when the NE is normal, restore the backup
NE databases. Configure services if the restored databases do not include service
data.
Step 3 If no backup NE databases are available, delete the NE databases, reset the NE,
and configure the NE.
----End
Related Information
None
A.2.119 NEIP_CONFUSION
Description
The NEIP_CONFUSION alarm indicates an 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.

None.
Possible Causes
Cause: The NEIP on the network conflicts with the local NEIP/access control port's
IP/local access control port's IP address.

Procedure
Step 1 Change the IP address/access control port's IP/local access control port's IP address
of the local or peer end according to the network plan. For details, see Modifying
NE IP Addresses.
----End
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.
A.2.120 NESF_LOST
Description
The NESF_LOST alarm indicates that the NE software is lost.
Attribute
Parameters
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2 and 3 Indicate the file code.
Parameter 4 Indicates the alarm cause.

● 0x01: The file does not exist.
● 0x02: The file verification fails.

If neither the active nor standby area has NE software, the system cannot reboot
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
Step 1 Check whether the alarm is caused by the loading operation.
If... Then...
The alarm is caused by the loading Contact Huawei technical support
operation engineers for loading the NE
software.
The alarm is not caused by the loading Replace the NE.
operation
----End
Related Information
None
A.2.121 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 software versions in the OFS1 and OFS2 areas of
the system control unit are inconsistent.
● This alarms occurs when the time for which the system waits after the
software package is loaded exceeds 24 hours.
Attribute
Major Processing error alarm
Parameters
table.

Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2 and 3 Indicate the file number.

● 0x04: The software versions in the OFS1 and OFS2 areas
of the system control unit are inconsistent.

After the system is powered off or reset, the system may fail to reboot or work
correctly.
Possible Causes
Cause 1: Software versions in the OFS1 and OFS2 areas of the system control unit
are inconsistent.
Cause 2: The time for which the system waits after the software package is loaded
exceeds 24 hours.
Procedure
Step 1 Cause 1: Software versions in the OFS1 and OFS2 areas of the system control unit
are inconsistent.
1. Upgrade the software in the OFS1 and OFS2 areas of the system control unit
to the same latest version.
Step 2 Cause 2: 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 3 Check whether the NESOFT_MM alarm is cleared. If the alarm persists, contact
Huawei technical support engineers.
----End
Related Information
None

A.2.122 NTP_SYNC_FAIL
Description
The NTP_SYNC_FAIL alarm indicates 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, or communication
between the NTP server and the NE is interrupted.
● 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. Configure the NTP parameters for the NE.
Step 2 Cause 2: The NTP server cannot communicate with the NE, or communication
between the NTP server and the NE is interrupted.
1. Check whether the cable connecting the gateway NE to the NTP server is
normal. If no, rectify the connection fault.
2. Check whether the DCN communication between the NTP server and the NE
is normal. If no, configure the DCN communication correctly.
Step 3 Cause 3: The NTP server fails.
1. Rectify the NTP server.
----End
Related Information
None

A.2.123 OUT_PWR_ABN
Description
The OUT_PWR_ABN alarm indicates that the output optical power is abnormal.
Attribute
Parameters
None

This alarm affects service transmission, and may cause service interruption.
Possible Causes
● Cause 1: The output optical power is excessively high or low.
● Cause 2: The alarmed NE is faulty.
Procedure
Step 1 Cause 1: The output optical power is excessively high or low.
1. Check the performance events related to optical power.
If... Then...
The optical power is excessively Perform the operations in Replacing an
low SFP Module.
The optical power is excessively Add a proper attenuator to reduce the
high transmit optical power.
Step 2 Cause 2: The alarmed NE is faulty.

1. Perform the operations in Replacing an OptiX RTN 380.
----End
Related Information
None

A.2.124 PASSWORD_NEED_CHANGE
Description
The PASSWORD_NEED_CHANGE alarm indicates that the default password used
by a default user to log in to the NE or default password of a WLAN connection
has never been changed. Security risks exist and the password should be changed.
Attribute
Major QoS alarm
Parameters
None

Security risks exist.
Possible Causes
● Cause 1: The default password of a default user has never been changed.
● Cause 2: The default password of a WLAN connection has never been
changed.
Procedure
Step 1 Cause 1: The default password of a default user has never been changed.
1. Change the password of the default user.
Step 2 Cause 2: The default password of a WLAN connection has never been changed.
1. Change the password of the WLAN connection.
----End
Related Information
None
A.2.125 PATCH_BD_EXCLUDE
Description
The PATCH_BD_EXCLUDE alarm indicates that an NE is automatically isolated
from being installed with a patch.

Attribute
Parameters
None

After an NE is isolated, the patch package is not matched with or loaded to the
NE.
Possible Causes
Cause: During the loading of a patch package, an error occurs on an NE.
Procedure
Step 1 Re-load the patch package.
----End
Related Information
None
A.2.126 PATCH_BD_MATCH_FAIL
Description
The PATCH_BD_MATCH_FAIL alarm indicates that a patch fails to be matched with
an NE.
Attribute
Parameters
None

The patch fails to be loaded.

Possible Causes
Cause: The loaded patch does not match with the NE.
Procedure
Step 1 Load a patch that matches the NE.
----End
Related Information
None
A.2.127 PATCH_PKGERR
Description
The PATCH_PKGERR alarm indicates that a patch package is abnormal.
Attribute
Parameters
None

The patch package cannot be loaded, activated, or ran correctly. This alarm does
not affect services.
Possible Causes
● Cause 1: The patch package is incorrect.
● Cause 2: The patch package is corrupted.
● Cause 3: The patch package is deleted.
Procedure
Step 1 Load the correct patch package.
----End
Related Information
None

A.2.128 PATCH_INIT_FAIL
Description
The PATCH_INIT_FAIL alarm indicates that the patch initialization fails.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the cause of the patch initialization failure:
● 0x01: The version mismatches.
● 0x02: The hardware 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 hardware 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 hardware 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 hardware 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,
contact Huawei technical support engineers.
----End
Related Information
None
A.2.129 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
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,
contact Huawei technical support engineers.
----End

Related Information
None
A.2.130 PING_ARP_MISMATCH
Description
The PING_ARP_MISMATCH alarm indicates that the dynamic ARP and static ARP
conflict in the ping operation.
Attribute
Parameters
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.
----End
Related Information
None
A.2.131 PING_LOS
Description
The PING_LOS alarm indicates that IP Ping fails.

Attribute
Parameters
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 3.3 Troubleshooting Ethernet Service Faults.

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
A.2.132 PLA_CFG_MISMATCH
Description
The PLA_CFG_MISMATCH alarm indicates that physical link aggregation (Super
EPLA) configurations are inconsistent at the two ends of a microwave link.
Attribute
Critical QoS alarm
Parameters
table.
Name Meaning
Parameter 1, Indicates the ID of the Super EPLA group.

Parameter 2

Name Meaning
Parameter 3, Indicates the error type.

Parameter 4
● 0x00: The Super EPLA is configured for the local NE of the
microwave link but is not configured for the opposite NE.
● 0x12: The member ports of the local-end and remote-end
Super EPLAs have different rates.
● 0x13: The member channel configurations of the local-end
and remote-end Super EPLAs are inconsistent.
● 0x15: The Super EPLA channel configurations on both sides
of a relay NE are inconsistent.
● 0x16: The Super EPLA member port sequences on both sides
of a relay NE are inconsistent.

Services on the microwave link are interrupted.
Possible Causes
● Cause 1: A Super EPLA group is configured at only one end of the microwave
link.
● Cause 2: The local-end Super EPLA member channel configuration and the
remote-end Super EPLA member channel configuration are inconsistent.
● Cause 3: The local-end Super EPLA member port and the remote-end Super
EPLA member port have different port rates.
● Cause 4: The member channel configurations of the local-end and remote-
end Super EPLAs are inconsistent.
● Cause 5: The member port sequences of the local-end and remote-end Super
EPLAs are inconsistent.
Procedure
Step 1 Cause 1: A Super EPLA group is configured at only one end of the microwave link.
1. Check whether the Super EPLA group is configured at both ends of the
microwave link.
2. If the Super EPLA group is configured only at one end of the microwave link,
cancel the Super EPLA configuration at the end or configure the Super EPLA
group at the other end of the microwave link.
Step 2 Cause 2: The local-end Super EPLA member channel configuration and the
remote-end Super EPLA member channel configuration are inconsistent.
1. Check whether the Super EPLA member channel ID at the local end is
consistent with that at the opposite end.
2. If the channel IDs are inconsistent, delete the Super EPLA group configuration
at one end and reconfigure the Super EPLA group to ensure the Super EPLA
channel IDs at both ends of the microwave link are consistent.

Step 3 Cause 3: The local-end Super EPLA member port and the remote-end Super EPLA
member port have different port rates.
1. Check whether the Super EPLA member port rate at the local end is
consistent with that at the opposite end.
2. If the port rates are inconsistent, change them to the same.
Step 4 Cause 4: The member channel configurations of the local-end and remote-end
Super EPLAs are inconsistent.
1. Check whether the channel configurations of the Super EPLA member at the
local end are consistent with those at the opposite end of the relay NE.
2. If the channel configurations are inconsistent, change them to the same.
Step 5 Cause 5: The member port sequences of the local-end and remote-end Super
EPLAs are inconsistent.
1. Check whether the port sequences of the Super EPLA member at the local
end are consistent with those at the opposite end of the relay NE.
2. If the port sequences are inconsistent, change them to the same.
----End
Related Information
None
A.2.133 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 less than the
preset minimum number.
Attribute
Major QoS alarm

Parameters
Name Meaning
Parameters 1 to 2 Indicate the ID of the PLA group.

Services carried by the PLA group are interrupted.
Possible Causes
Cause: The number of active member links in the PLA group is 0 or less than the
preset minimum number.
Procedure
Step 1 Check whether the preset minimum number of active member links is the same as
that specified by the network plan. If they are different, re-configure the minimum
number of active member links. If they are the same, go to the next step.
Step 2 Clear the PLA_MEMBER_DOWN_EXT alarm.
----End
Related Information
None
A.2.134 PLA_MEMBER_DOWN_EXT
Description
The PLA_MEMBER_DOWN_EXT alarm indicates that a member link of a PLA group
is faulty.
Attribute
Minor QoS alarm
Parameters
table.

Name Meaning
Parameters 1 and 2 Indicate the ID of the PLA group.
Parameters 3 to 6 Indicate the NE ID.
Parameters 7 to 8 Indicate the slot ID.
Parameter 9 Indicates the slot ID of the sub-board.
Parameters 10 and 11 Indicate the port ID.
Parameters 12 and 13 Indicate the channel ID.

● 0x00: LOCV
● 0x01: RDI
● 0x02: CC loopback
● 0x03: forced switching
● 0x04: hardware fault
● 0x05: link fault
● 0x06: configuration mismatch
● 0x07: WTR
● 0x08: symmetry

If a PLA_DOWN alarm is also reported simultaneously, services are interrupted. If
no PLA_DOWN alarm is reported, only services carried by the faulty member link
are interrupted and the available bandwidth of the PLA group is decreased.
Possible Causes
Cause 1: A microwave link in the PLA group is faulty.
Cause 2: The cascading cable or its connector is faulty.
Cause 3: The local or cascaded NE has a hardware fault.
Procedure
Step 1 Check the status of the PLA group and identify the faulty microwave link.
Step 2 Check for and clear any alarms, such as MW_LOF, MW_LIM, R_LOF, and
MW_RDI, on the microwave link. If none of the alarms are reported, go to the
next step.
Step 3 Check whether the cascading cable is intact and properly connected and whether
its connector is intact. If the cascading cable is loose, secure it. If the cascading

cable or connector is damaged, replace the cable or connector. If the cascading

cable is intact and properly connected and the connector is intact, go to the next
step.
Step 4 Check for the HARD_BAD alarms on the local or cascaded NE. If the local or
cascaded NE reports a HARD_BAD alarm, replace the local or cascaded NE by
following instructions in Replacing an NE.
----End
Related Information
None
A.2.135 PLA_PKT_ERR
Description
The PLA_PKT_ERR alarm indicates that packet reassembly fails in the receive
direction.
Attribute
Major QoS alarm
Parameters
table.
Name Meaning
Parameters 1 and 2 Indicate the ID of the PLA group.

Packet loss occurs in services.
Possible Causes
Cause 1: A member link in the PLA group is faulty.
Cause 2: The local or cascaded NE has a hardware fault.

Procedure
Step 1 Check for MW_LOF, MW_LIM, R_LOF, and MW_RDI alarms on links in the PLA
group and clear them if any. If no such alarm is reported, go to the next step.
Step 2 Check for the HARD_BAD alarms on the local and cascaded NEs. If the local or
cascaded NE reports the HARD_BAD alarm, replace the local or cascaded NE by
following instructions in Replacing an NE.
----End
Related Information
None
A.2.136 PORT_BER_SD
Description
The PORT_BER_SD alarm indicates that the bit error rate (BER) on a CPRI port
exceeds the alarm threshold (10-6 by default).
Attribute
Minor QoS alarm
Parameters
None

The quality of services deteriorates.
Possible Causes
● Cause 1: The signal attenuation over optical fibers is large.
● Cause 2: The optical module of the CPRI port on the NE that reports the
PORT_BER_SD alarm is faulty.
● Cause 3: The optical module of the peer BBU or RRU is faulty.
Procedure
Step 1 Cause 1: The signal attenuation over optical fibers is large.
1. Check for IN_PWR_ABN and OUT_PWR_ABN alarms, which indicate abnormal
optical power, on the NE that reports the PORT_BER_SD alarm. If any, clear
them by following instructions in A.2.49 IN_PWR_ABN or A.2.123
OUT_PWR_ABN.

2. Check whether the PORT_BER_SD alarm is cleared. If the alarm persists, go to

Step 2.
Step 2 Cause 2: The optical module of the CPRI port on the NE that reports the
PORT_BER_SD alarm is faulty.
1. Replace the faulty optical module on the NE that reports the PORT_BER_SD
alarm.
2. Check whether the PORT_BER_SD alarm is cleared. If the alarm persists, go to
Step 3.
Step 3 Cause 3: The optical module of the peer BBU or RRU is faulty.
1. Check whether the optical module of the peer BBU or RRU is functional. If the
optical module is faulty, replace it.
2. Check whether the PORT_BER_SD alarm is cleared. If the alarm persists,
----End
Related Information
None
A.2.137 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC alarm indicates that the bandwidth utilization ratio of a
port exceeds the threshold. This alarm is reported when the bandwidth utilization
ratio of a port exceeds the preset threshold.
Attribute
Major QoS alarm
Parameters
table.
Name Meaning
Parameter 1 Indicates the transmit or receive direction.
● 0x00: receive
● 0x01: transmit


Excessive service traffic may cause service congestion.
Possible Causes
● Cause 1: The configured bandwidth limit is too low.
● Cause 2: The port handles excessive traffic.
Procedure
Step 1 Cause 1: The configured bandwidth limit is too low.
1. With reference to Setting Traffic Shaping for Egress Queues, check the
configured bandwidth limit.
2. If the bandwidth limit of the Ethernet port is too low, increase the bandwidth
limit according to Configuring Port Shaping or expand the network.
3. If the bandwidth of the IF port is too low, use a higher order modulation
scheme and increase the channel spacing according to Configuring a Single
Hop of Microwave Link.
Step 2 Cause 2: The port handles excessive traffic.

1. With reference to Querying Traffic, Physical Bandwidth, or Bandwidth
Utilization of Ethernet Ports, query the bandwidth utilization ratio of the
alarmed port.
2. If the port bandwidth utilization is higher than the threshold, check whether a
network storm occurs. If a network storm occurs, eliminate the source that
transmits a large amount of invalid data.
----End
Related Information
None
A.2.138 PORTMODE_MISMATCH
Description
The PORTMODE_MISMATCH alarm indicates that the working mode of the
opposite Ethernet port mismatches that of the local Ethernet port. This alarm is
reported when the configured working mode of the local Ethernet port is auto-
negotiation but the negotiated working mode is half-duplex.
Attribute
Minor QoS alarm

Parameters
table.
Name Meaning
Parameters 1 and 2 Indicate the current working mode.

● 0x01: 10M half-duplex
● 0x02: 10M full-duplex

This alarm does not affect services.
Possible Causes
Cause: The local Ethernet port and opposite Ethernet port work in different
modes.
Procedure
Step 1 Set the port working mode consistently at both ends by referring to instructions in
Setting the Basic Attributes for an Ethernet Port.
----End
Related Information
None
A.2.139 POWER_ALM
Description
The POWER_ALM alarm indicates that the voltage of the power module is out of
the normal range.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the power channel with abnormal voltage.
Parameter 2 Indicates the voltage exception type.

● 0x01: undervoltage
● 0x02: overvoltage

This alarm may cause the NE to work incorrectly.
Possible Causes
Cause 1: The NE's power module is abnormal.
Procedure
Step 1 Cause 1: The NE's power module is abnormal.
1. Perform the operations in Replacing an NE.
----End
Related Information
None.
A.2.140 PRO_PKT_FLOODING
Description
The PRO_PKT_FLOODING alarm indicates that an NE has detected a protocol
packet flood attack. This alarm is reported when the rate of a type of protocol
packets is greater than the upper threshold for consecutive 30s.
Attribute

Parameters
Name Meaning
Parameters 1 to 2 Indicate the slot ID.
Parameters 3 to 4 Indicate the packet type.

● 0x00: LAG
● 0x01: IP Ping
● 0x02: ERPS
● 0x03: MSTP
● 0x06: ARP
● 0x07: DCN
● 0x16: LLDP
● 0x1a: OAM3AH
Parameters 5 to 6 Indicate the upper threshold of the packet rate.

The system becomes unstable due to high CPU resource utilization. Normal
protocol packets may be lost.
Possible Causes
Cause: The rate of a type of protocol packets is greater than the upper threshold
for 30 consecutive seconds.
Procedure
Step 1 Check for and handle packet attacks on the network.
----End
Related Information
None
A.2.141 PTP_SOURCE_SWITCH
Description
The PTP_SOURCE_SWITCH is an alarm indicating a switchover between PTP time
sources.

Attribute
Parameters
table.
Name Meaning
Parameter 1, Parameter 2 Indicates the slot ID of the board before the
switching.
Parameter 3 Indicates the ID of the subboard before the switching.
0xFF indicates that there is no subboard.
Parameter 4, Parameter 5 Indicates the ID of the port before the switching.
Parameters 6 to 9 Indicates the ID 1 of the grandmaster clock before the
switching.
Parameters 10 to 13 Indicates the ID 2 of the grandmaster clock before the
switching.
Parameter 14, Parameter Indicates the slot ID of the board after the switching.
15
Parameter 16 Indicates the ID of the subboard after the switching.
0xFF indicates that there is no subboard.
Parameter 17, Parameter Indicates the ID of the port after the switching.
18
Parameters 19 to 22 Indicates the ID 1 of the grandmaster clock after the
switching.
Parameters 23 to 26 Indicates the ID 2 of the grandmaster clock after the
switching.

When this alarm occurs, a switchover occurs on the IEEE 1588v2 clock source
traced by the NE, which will cause clock switchover in the entire clock domain.
Possible Causes
● 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.

● Cause 4: There are ports on the link for which the IEEE 1588 function is not
enabled.
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.
Step 4 Cause 4: There are ports on the link for which the IEEE 1588 function is not
enabled.
1. Check whether the IEEE 1588 function needs to be enabled at both ends. If
yes, ensure that this function is enabled at both ends.
----End
Related Information
None
A.2.142 PTP_TIME_ADJUST_OFF
Description
The PTP_TIME_ADJUST_OFF alarm indicates that the PTP time adjustment
function is disabled.
Attribute
Parameters
None

When this alarm is generated, time synchronization may fail between the current
NE and the downstream NE. Consequently, services may encounter bit errors.

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.
The operation steps in the NCE network management are as follows:
----End
Related Information
None
A.2.143 PTP_TIMESTAMP_ABN
Description
The PTP_TIMESTAMP_ABN alarm indicates that PTP timestamps are abnormal.
Attribute

Parameters
Name Meaning
Parameter 1 ● 0x01: The interval for transmitting a SYNC packet is greater than
2s.
● 0x02: The t1 timestamps are the same for three consecutive
seconds.
● 0x03: The t2 timestamps are the same for three consecutive
seconds.
● 0x04: Both t1 and t2 timestamps are the same for three
consecutive seconds.
Parameter 2 ● 0x01: The interval for transmitting a delay packet is greater than
16s.
● 0x02: The t3 timestamps are the same for 17 consecutive
seconds.
● 0x03: The t4 timestamps are the same for 17 consecutive
seconds.
● 0x04: Both t3 and t4 timestamps are the same for 17
consecutive seconds.

The slave node cannot trace the time of the master node and services contain bit
errors.
Possible Causes
● Cause 1: The opposite end is faulty.
● Cause 2: The local end is faulty.
● Cause 3: The physical-layer synchronization and 1588v2 time synchronization
are configured, and the upstream node transmits less than one SYNC packet
per second.
Procedure
Step 1 Cause 1: The opposite end is faulty.
1. Rectify the fault at the transmit end or replace the clock source.
Step 2 Cause 2: The local end is faulty.

1. Check whether the NE at the local end has the HARD_BAD alarm. If the NE
has the HARD_BAD alarm, replace it by following instructions in Replacing
the NE.
Step 3 Cause 3: The physical-layer synchronization and 1588v2 time synchronization are
configured, and the upstream node transmits less than one SYNC packet per
second.

1. Set the upstream node to transmit more than one SYNC packet per second
according to Configuring 1588v2 Clock Packet Parameters.
----End
Related Information
None
A.2.144 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 QoS alarm
Parameters
None

Availability of the protection group declines.
Possible Causes
Cause: A PW in the protection group is faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the
PWs are incorrectly configured, rectify the configurations.
Step 2 Check whether a PWAPS_PATH_MISMATCH alarm is reported. If the alarm is

reported, handle the alarm.
----End
Related Information
None

A.2.145 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 QoS alarm
Parameters
None

The protection group is unavailable and the services carried by the protection
group are interrupted.
Possible Causes
Cause: The working and protection PWs in the protection group are faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the
PWs are incorrectly configured, rectify the configurations.
Step 2 Check whether a PWAPS_PATH_MISMATCH alarm is reported. If the alarm is

reported, handle the alarm.
----End
Related Information
None
A.2.146 PW_DROPPKT_EXC
Description
The PW_DROPPKT_EXC alarm indicates that the packet loss ratio on a PW exceeds
its threshold.

Attribute
Warning Processing error alarm
Parameters
Name Meaning
Parameter 1 Has a fixed value of 0x00, indicating that the traffic in the ingress
or egress direction crosses its threshold.

A small number of packets are lost, affecting service real-time performance.
Possible Causes
Cause: A small number of packets are lost on the alarmed PW.
Procedure
Step 1 Cause: A small number of packets are lost on the alarmed PW.
1. Check the bandwidth utilization of the alarmed PW. If the PW bandwidth is
exhausted, increase the bandwidth or eliminate any source that transmits a
large amount of invalid data.
----End
Related Information
None
A.2.147 PW_NO_TRAFFIC
Description
The PW_NO_TRAFFIC alarm indicates 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 port, and direction in which traffic is unavailable according
to the alarm information on the NMS.
If... Then...
The PW_NO_TRAFFIC alarm is reported in both the receive and Go to Step 2.

transmit directions
0x00 Go to Step 4.
0x01 Go to Step 3.
Step 2 Cause 1: No service is configured.

1. Check whether the port is configured with any services. If not, configure
services correctly.
Step 3 Cause 2: The local services are abnormal and therefore no packet is transmitted to
the peer end.
1. Check whether the local PW services are correctly configured.
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 NE.
2. Check whether the alarm is cleared. If the alarm persists, troubleshoot the
interconnected port.
----End
Related Information
None
A.2.148 PWAPS_LOST
Description
The PWAPS_LOST alarm indicates that the APS frame is lost. This alarm occurs
when no APS frame is received from the protection channel.
Attribute
Parameters
None

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
A.2.149 PWAPS_PATH_MISMATCH
Description
The PWAPS_PATH_MISMATCH alarm indicates 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

A.2.150 PWAPS_SWITCH_FAIL
Description
The PWAPS_SWITCH_FAIL alarm indicates 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
A.2.151 PWAPS_TYPE_MISMATCH
Description
The PWAPS_TYPE_MISMATCH alarm indicates 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
A.2.152 PWD_ENCRYPT_RISK
Description
The PWD_ENCRYPT_RISK alarm indicates that the user password encryption mode
of an NE has security risks.

Attribute
Parameters
None

The user password may be cracked, and the system has security risks.
Possible Causes
Cause: The user password encryption mode of the NE is MD5 or SHA256.
Procedure
Step 1 In the NE Explorer, click the NE and choose Security > NE User Password
Encryption Management. Change Encryption Type to PBKDF2.
----End
Related Information
None
A.2.153 R_LOF
Description
The R_LOF alarm indicates that frames are lost on the receive side. This alarm is
reported by a CPRI when the CPRI fails to detect CPRI frame headers in two or
more consecutive frames; it is also reported by an IF port when the port is in OFF
state for 3 ms or more.
Attribute
Parameters
None


If no protection switching scheme is configured, this alarm causes service
interruption. If a protection switching scheme is configured, this alarm triggers a
switchover.
Possible Causes
Possible causes for a CPRI to fail to receive frames include:
● Cause 1: Rate switching of wireless equipment
● Cause 2: The microwave link is faulty or contains bit errors.
● Cause 3: The optical interface is abnormal or the optical module does not
match.
Possible causes for an IF port to fail to receive frames include:

● Cause 1: The transmit unit of the remote NE is faulty.
● Cause 2: The receive power at the local end is abnormal.
● Cause 3: The receive unit of the local NE is faulty.
Procedure
● Procedure of handling frame lost on the receive side of a CPRI:
a. Cause 1: Rate switching of wireless equipment
i. Rate is switched during CPRI negotiation between wireless
equipment and OptiX RTN 380, so the R_LOF alarm is reported. The
R_LOF alarm clears after the negotiation is successful.
b. Cause 2: The microwave link is faulty.
i. Check whether the microwave link reports the RADIO_RSL_LOW
alarm. If yes, clear the alarm first.
ii. Check whether the microwave link is interfered. Follow instructions in
7.3.2 Scanning Interfering Signals or use a frequency spectrum
analyzer to locate the possible interfering frequencies.
○ If a third-party RF device is the interfering source, contact the
local frequency spectrum management department to handle
the interference.
○ If interference is caused due to improper route planning, modify
the frequency plan to minimize the interference impacts.
c. Cause 3: The optical module is faulty or does not match.
i. Replace the SFP optical module. Type of the optical module on the
CPRI must match rate of the CPRI.
● Procedure of handling frame lost on the receive side of an IF port:
a. Cause 1: The transmit unit of the remote NE is faulty.
i. Rectify the fault at the transmit unit of the remote NE by, for
example, enabling the transmit port.
b. Cause 2: The receive power at the local end is abnormal.

i. Follow instructions in 6.2.1 Browsing Historical Transmit Power

and Receive Power to check whether the receive power of the OptiX
RTN 380 at the local end is normal. Diagnose any faults.
If... Then...
The received signal Perform the following steps:

level (RSL) is lower
than the receiver 1. Check the installation of the antenna to
sensitivity ensure that the azimuth angle of the
antenna meets the requirement.
2. Check the antenna direction. Especially,
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 the polarization direction of
antennas and adjust the incorrect
polarization direction.
4. Check the antenna gain at the two ends
and replace the antennas that do not
provide required antenna gain.
5. Check whether transmission is blocked
by any mountains or buildings.
Contact the network planning
department for avoiding the block if
any.
The RSL is higher Slow up fading occurs. Perform the

than the specified following steps:
RSL of the network.
The offset value is 1. Check for co-channel interference. For
tens of decibels. The details, see 7.3.2 Scanning Interfering
duration is from tens Signals.
of seconds to several 2. Use a spectrum analyzer to analyze
hours interference sources.
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 Slow down fading occurs. Generally, the
the specified RSL of microwave link may be faulty in both
the network. The directions, because slow down fading is
offset value is tens of imposed by the transmission path. Contact
decibels. The the network planning department to make
duration is from tens the following changes:
hours ● Increase the installation heights of
antennas.
The RSL is lower than Fast fading occurs. Contact the network
or higher than the planning department to make the
specified RSL of the following changes:
network and the
duration is from ● Adjust the position of the antenna to
several milliseconds block the reflected wave or make the
to tens of seconds reflection point fall on the ground that
has a small reflection coefficient,
reducing multipath fading.
c. Cause 3: The receive unit of the local NE is faulty.
i. Replace the local NE.
----End
Related Information
None
A.2.154 R_LOS
Description
The R_LOS alarm indicates loss of signals on the receive side of a CPRI port.
Attribute
Critical alarm Communication alarm
Parameters


table.
Name Meaning
Parameter 1 Indicates that the optical module does not receive any signals.
Parameter 2 Indicates that data flows at the CPRI port are abnormal.

Services on the receive port are interrupted.
Possible Causes
● Cause 1: The fiber connection is faulty.
● Cause 2: The laser at the local end is shut down.
● Cause 3: The laser at the opposite end is shut down.
● Cause 4: The transmit unit of the remote NE is faulty.
● Cause 5: The receive unit of the local NE is faulty.
Procedure
Step 1 Cause 1: The fiber connection is faulty.
1. Check the optical fiber connected to the alarm port.
If... Then...
The fiber is not properly connected Connect the fiber properly.
The fiber is damaged Replace the fiber.
The SFP modules at both ends do not match Replace the SFP module.
or one SFP module is damaged
Step 2 Cause 2: The laser at the local end is shut down.

1. Check whether a LASER_SHUT alarm is reported from the microwave link. If
such an alarm exists, clear the alarm.
Step 3 Cause 3: The laser at the opposite end is shut down.

1. Turn on the laser at the opposite end.
Step 4 Cause 4: The transmit unit of the remote NE is faulty.

1. Rectify the fault at the transmit unit of the remote NE by, for example,
enabling the transmit port.
Step 5 Cause 5: The receive unit of the local NE is faulty.

1. 4.1 Replacing an OptiX RTN 380.
----End

Related Information
None
A.2.155 RADIO_FADING_MARGIN_INSUFF
Description
The RADIO_FADING_MARGIN_INSUFF alarm indicates that the mean receive
power of the OptiX RTN 380 is lower than the threshold (receiver sensitivity +14
dB). The threshold is configurable.
When the mean receive power of the OptiX RTN 380 in six consecutive hours is
lower than the threshold, the system reports the alarm. After the alarm is
reported, if the mean receive power of the OptiX RTN 380 is higher than the
threshold and maintains the state for three minutes, the alarm clears.
Attribute
Parameters
None

This alarm does not affect services if it is not accompanied by MW_BER_EXC,
MW_BER_SD, MW_LOF, or MW_FEC_UNCOR.
Possible Causes
● Cause 1: The transmit power is abnormal due to the faulty OptiX RTN 380 at
the opposite site.
● Cause 2: The direction of the antenna is deflected.
● Cause 3: Transmission environment changes.
● Cause 4: The fading margin planned for rain and fog is insufficient.
Procedure
Step 1 Cause 1: The transmit power is abnormal due to the faulty OptiX RTN 380 at the
opposite site.
1. Check whether the OptiX RTN 380 at the opposite site reports the
RADIO_TSL_LOW alarm.
If... Then...
The RADIO_TSL_LOW alarm is reported Handle the RADIO_TSL_LOW alarm.

If... Then...
The RADIO_TSL_LOW alarm is not Go to Cause 2.
reported
Step 2 Cause 2: The direction of the antenna is deflected.

1. Check whether the direction of the antenna is deflected.
If... Then...
The direction of the antenna is deflected Adjust the direction of the
antenna.
The direction of the antenna is not Go to Cause 3.
deflected
Step 3 Cause 3: 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 replanning the transmission trail.
The transmission environment Go to Cause 4.
does not change
Step 4 Cause 4: The fading margin planned for rain and fog is insufficient.
1. If the alarm is frequently reported in rainy or foggy weather, contact the
network planning department for increasing the fading margin.
----End
Related Information
None
A.2.156 RADIO_MUTE
Description
The RADIO_MUTE alarm indicates that the radio transmitter is muted.
Attribute
Warning Equipment alarm

Parameters
None

This alarm indicates that the radio transmitter does not transmit signals.
Possible Causes
● Cause 1: The transmitter of the local site is muted manually.
● Cause 2: The OptiX RTN 380 at the local site is faulty.
Procedure
Step 1 Cause 1: The transmitter of the local site is muted manually.
1. With reference to Configuring a Single Hop of Microwave Link, check whether
the OptiX RTN 380 at the local site is muted. If yes, unmute the OptiX RTN
380.
Step 2 Cause 2: The OptiX RTN 380 at the local site is faulty.
1. Replace an OptiX RTN 380.
----End
Related Information
None.
A.2.157 RADIO_RSL_BEYONDTH
Description
The RADIO_RSL_BEYONDTH alarm indicates 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 OptiX RTN 380 is lower than
the threshold (power to be received minus 3 dB), the RADIO_RSL_BEYONDTH
alarm is reported. The RADIO_RSL_BEYONDTH alarm is cleared after the actual
receive power of the OptiX RTN 380 is greater than or equal to the threshold.
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

This alarm does not affect services if it is not accompanied by MW_BER_EXC,
MW_BER_SD, MW_LOF, or MW_FEC_UNCOR.
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 receivable 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. After the
RADIO_FADING_MARGIN_INSUFF alarm clears, the RADIO_RSL_BEYONDTH
alarm clears.
----End
Related Information
None
A.2.158 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH alarm indicates that the radio received signal level (RSL) is
very high. This alarm is reported if the detected RSL is higher than or equal to the
upper threshold of the OptiX RTN 380 (-23 dBm).
Attribute
Parameters
None


This alarm affects service transmission.
This alarm triggers a switchover if a 1+1 protection group is configured.
Possible Causes
● Cause 1: There is a strong interference source nearby.
● Cause 2: The transmit power of the OptiX RTN 380 at the opposite site is very
high.
Procedure
Step 1 Cause 1: There is a strong interference source nearby.
1. With reference to 7.3.2 Scanning Interfering Signals, scan interference
signals, or Use a spectrum analyzer to scan interference signals nearby.
2. If any interference signal is detected, shut down or remove the signal source.
If the signal source cannot be shut down or removed, contact the network
planning department for changing the frequency plan.
Step 2 Cause 2: The transmit power of the OptiX RTN 380 at the opposite site is very
high.
the transmit power settings on the local and opposite NEs are consistent with
the network planning documents. If no, set the transmit power according to
the network planning documents.
1. Replace the NE.
----End
Related Information
None.
A.2.159 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW alarm indicates that the radio received signal level (RSL) is
very low. This alarm is reported when the detected RSL is lower than or equal to
the lower threshold of the OptiX RTN 380 (-72 dBm).
Attribute

Parameters
None

This alarm does not affect services if it is not accompanied by the MW_BER_EXC,
MW_BER_SD, MW_LOF, or MW_FEC_UNCOR alarm.
Possible Causes
● Cause 1: Certain other alarms occur at the opposite site.
● Cause 2: The transmitted signal level (TSL) at the opposite site is over low.
● Cause 4: Signal attenuation on the microwave link is heavy.
Procedure
Step 1 Cause 1: Certain other alarms occur at the opposite site.
Check whether any of the following alarms is reported at the opposite site. If yes,
clear the alarm immediately.
● RADIO_MUTE
● RADIO_TSL_LOW
Step 2 Cause 2: The transmitted signal level (TSL) at the opposite site is over low.
the preset transmit power and actual transmit power at the opposite site are
normal.
If... Then...
The preset transmit power is Change the transmit power according to the
abnormal network planning information.
The actual transmit power is Replace the OptiX RTN 380 at the opposite
abnormal site.
1. Replace the OptiX RTN 380 at the local site.
Step 4 Cause 4: Signal attenuation on the microwave link is heavy.

1. With reference to Troubleshooting Microwave Link Faults, handle the signal
attenuation.
----End
Related Information
None.

A.2.160 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH alarm indicates that the radio transmitted signal level (TSL)
is very high. This alarm is reported by the OptiX RTN 380 if the difference between
the actual transmit power and configured transmit power crosses the upper
threshold (3 dBm).
Attribute
Parameters
None

Possible Causes
Procedure
----End
Related Information
None.
A.2.161 RADIO_TSL_LOW
Description
The RADIO_TSL_LOW alarm indicates that the radio transmitted signal level (TSL)
is very low. This alarm is reported by the OptiX RTN 380 if the difference between
the actual transmit power and configured transmit power crosses the lower
threshold (- 3 dBm).

Attribute
Parameters
None

Possible Causes
Procedure
----End
Related Information
None.
A.2.162 REFLECTOR_IP_CNFLCT
Description
This alarm indicates that the simulated IP address of the reflection end conflicts
with the IP address of another node on the network.
Attribute
Major Processing error alarm
Parameters
table.

Name Meaning
Parameters 1 to 4 Indicate the ID of the reflection end.
Parameters 5 to 8 Indicate the simulated IP address of the reflection end.
Parameters 9 to 14 Indicate the MAC address of the node whose IP address
conflicts with the simulated IP address.

When this alarm is reported, the reflection end stops simulating service traffic.
Possible Causes
Cause: The simulated IP address of the reflection end conflicts with the IP address
of another node on the network.
Procedure
Step 1 Modify the simulated IP address of the reflection end.
----End
Related Information
None
A.2.163 RPS_INDI
Description
The RPS_INDI alarm indicates that radio protection switching occurred.
Attribute
Parameters
table.
Name Meaning
Parameter 1 Indicates the protection group ID.

Name Meaning
Parameter 2 Indicates the switching type.
0x01: HSB protection switching

Services are interrupted during the switching and recovered after the switching
completes.
Possible Causes
● Cause 1: An external switching event occurs.
● Cause 2: An automatic switching event occurs.
● Cause 3: An reverse switching event occurs.
Procedure
Step 1 Cause 1: An external switching event occurs. To be specific, a command is issued
from the NMS to trigger the switching.
1. Query whether the IF 1+1 switching status is forced switching or manual
switching.
If... Then...
The IF 1+1 switching status is forced Find the cause and clear the
switching or manual switching switching immediately.
The IF 1+1 switching status is not forced Go to Cause 2.
switching or manual switching
Step 2 Cause 2: An automatic switching event occurs. To be specific, the equipment is

faulty, or the service is defective.
1. Check whether the following faults or alarms occur. Rectify the faults or clear
the alarms if any.
– The hardware is faulty.
– The NE has been cold reset.
– RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH alarms
– MW_LOF, ETH_LOS, or ETH_LINK_DOWN alarms
– The NE has been powered off.
– Automatic switching is triggered by service-related hardware faults.

– In non-revertive mode, services will not be automatically switched back to the
main path after the main path recovers, and the RPS_INDI alarm persists. You need
to manually switch the services from the standby path to the main path. The
RPS_INDI alarm clears only after the services are switched back to the main path.
– In revertive mode, services are automatically switched back to the main path when
the specified wait to restore (WTR) time expires after the main path recovers. The
RPS_INDI alarm clears only after the services are switched back to the main path.

Step 3 Cause 3: An reverse switching event occurs.

1. Check for the MW_RDI alarm on both the main and standby NEs, and clear it
if any.
----End
Related Information
None
A.2.164 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE alarm indicates that the clock source is switched in S1 byte
mode.
Attribute
Parameters
table.
Name Meaning
Parameter 1 0x01: the system clock source is switched

If the new clock source degrades, service quality will degrade due to pointer
justifications and bit errors.
Possible Causes
The precondition is that the SSM or extended SSM is enabled.
● Cause 1: The original clock source is lost.

● Cause 2: The upstream NE reports the S1_SYN_CHANGE alarm.

Procedure
Step 1 Cause 1: The original clock source is lost.
1. Handle the SYNC_C_LOS alarm reported by the original clock source.
Step 2 Cause 2: The upstream NE reports the S1_SYN_CHANGE alarm.
1. Handle the S1_SYN_CHANGE alarm on the upstream NE.
----End
Related Information
S1 byte mode refers to the SSM or extended SSM clock protection mode.
A.2.165 SEC_RADIUS_FAIL
Description
The SEC_RADIUS_FAIL alarm indicates that consecutive RADIUS authentication
failures are too many. This alarm is reported when the number of consecutive
RADIUS authentication failures reaches five.
Attribute
Parameters
table.
Name Meaning
Parameters 1 to 5 Indicate the first five user accounts.

A user cannot log in to an NE.
Possible Causes
● Cause 1: The active period of the user account expires.
● Cause 2: Configurations on the RADIUS server such as passwords and access
policies are incorrect.
● 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 user account expires.
1. Use an active account.
Step 2 Cause 2: Configurations on the RADIUS server such as passwords and access
policies are incorrect.
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 unauthenticated login attempts.
Step 4 Cause 4: The shared key for the NE and the RADIUS server is configured
incorrectly.
1. Set the shared key correctly.
----End
Related Information
None
A.2.166 SECU_ALM
Description
The SECU_ALM alarm indicates that login attempts of unauthorized users fail.
Attribute
Parameters
None

This alarm is reported transiently and does not affect services.
Possible Causes
Cause: Unauthorized users attempt to log in to the NE.

Procedure
Step 1 Query the NE logs and check the users who have attempted to log in.
----End
Related Information
If a user fails in more than five consecutive login attempts (two login attempts
within three minutes are considered consecutive), the SECU_ALM alarm will be
reported at every failed attempt since the sixth one. In addition, the user account
will be locked for 900 seconds. The locked user account cannot be used for logins.
A.2.167 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
Name Meaning
Parameters 1–2 Indicate the VLAN ID of the service that encounters a loop. The
value range is 0x001-0xffe.
Parameter 3 Indicates the type of the receive port when a loop is detected.
● 0x00: UNIPHY
● 0x01: QinQ
● 0x02: PW

Name Meaning
Parameters 4–8 When Parameter 3 is 0x00:
● Parameters 4 and 5 indicate the slot ID.

● Parameter 6 indicates the subboard ID.
● Parameters 7 and 8 indicate the port ID.
When Parameter 3 is 0x01:
● Parameters 4-7 indicate the QinQ ID.
● Parameters 4-7 indicate the receive label 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
A.2.168 SRV_SHUTDOWN_LD
Description
The SRV_SHUTDOWN_LD alarm indicates that a looped Ethernet service is
disabled. This alarm is cleared after the loop is released and the Ethernet service is
enabled.
Attribute
Major QoS alarm

Parameters
Name Meaning
Parameters 1–2 Indicate the VLAN ID of the service that encounters a loop. The
value range is 0x001-0xffe.
Parameter 3 Indicates the type of the receive port when a loop is detected.
● 0x00: UNIPHY
● 0x01: QinQ
● 0x02: PW
Parameters 4–8 When Parameter 3 is 0x00:
● Parameters 4 and 5 indicate the slot ID.

● Parameter 6 indicates the subboard ID.
● Parameters 7 and 8 indicate the port ID.
● Parameters 4-7 indicate the QinQ ID.
● Parameters 4-7 indicate the receive label of the PW.

The looped service is interrupted.
Possible Causes
Cause 1: A looped service detected in a loop test is disabled.
Procedure
Step 1 Check service configurations on the path where the disabled service passes and
release the loop.
Step 2 Enable the service or reconfigure the service based on the service plan.
----End
Related Information
None

A.2.169 SSL_CERT_DAMAGED
Description
The SSL_CERT_DAMAGED alarm indicates 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.
----End
Related Information
None
A.2.170 SSL_CERT_NOENC
Description
SSL_CERT_NOEN indicates the certificate file of SSL is not encrypted.

Attribute
Major Equipment Alarm
Parameters
None

Unencrypted certificate file is stored on device, private key of the file may be
illegally obtained.
Possible Causes
Certificate file of SSL is not encrypted.
Procedure
Step 1 Re-load and activate the encrypted SSL certificate file on the NCE.
----End
Related Information
None
A.2.171 SSL_CERT_TO_EXPIRE
Description
The SSL_CERT_TO_EXPIRE alarm indicates that a customized SSL certificate file is
about to expire. This alarm is reported when a customized SSL certificate file will
expire after two months to prompt users to reload and activate the SSL certificate
file. This alarm is automatically cleared after the SSL certificate file is reloaded and
activated.
Attribute
Critical Security alarm
Parameters


table.
Name Meaning
Parameter 1 Indicates the type of the certificate that will expire.

If the customized SSL certificate file is not reloaded or activated in time, the NE
cannot communicate with the NMS through SSL after a reset.
Possible Causes
Cause: A customized SSL certificate file is about to expire.
Procedure
Step 1 Cause: A customized SSL certificate file is about to expire.
1. Log in to the NCE, and load and activate the customized SSL certificate file
again.
----End
Related Information
None
A.2.172 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
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
A.2.173 STORM_CUR_QUENUM_OVER
Description
The STORM_CUR_QUENUM_OVER alarm indicates alarm storms. This alarm is
reported when the current alarm queue length is one smaller than the maximum.
This alarm clears when the number of current alarms reduces to 950.
Attribute
Parameters
None

The earliest alarms in the current alarm queue will be overwritten and cannot be
queried.
Possible Causes
Cause: More than 1000 current alarms are stored in the current alarm queue.
Procedure
Step 1 Check the current alarms and clear the frequently reported ones.
----End
Related Information
The STORM_CUR_QUENUM_OVER alarm will not be overwritten.
Registers store alarm data in discard or overwrite mode. The default mode is
overwrite.
● In discard mode, registers discard the later alarm data if they are full.

● In overwrite mode, registers store the later alarm data in place of the earlier
alarm data if they are full. To be specific, later alarm data is stored in the
initial addresses of registers.
A.2.174 SUBNET_RT_CONFLICT
Description
The SUBNET_RT_CONFLICT alarm indicates 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/air
mask/gateway/ interface
protocol/interface) ● 129.9.0.1/255.255.255.255/127.0.0.1/direct/
loop
● 129.9.0.2/255.255.255.0/129.9.0.2/direct/air
interface
NE2 IP address 129.9.0.2
Subnet mask 255.255.255.0

NE Parameter
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.1/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.1/direct/air
interface
A.2.175 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT alarm indicates that the commit operation is not
performed within 30 minutes after activation of the NE software in a package
loading task.
Attribute
Parameters
None

Software files in the OFS1 and OFS2 areas of the system control unit are
inconsistent.
Possible Causes
● Cause 1: The commit operation is not performed within 30 minutes after
activation of the NE software.
● Cause 2: In a package diffusion task, NEs included in the package diffusion
task fail to receive the commit command due to microwave link failures.
Procedure
Step 1 Cause 1: The commit operation is not performed within 30 minutes after
activation of the NE software.
1. Proceed the task with the commit operation.

Step 2 Cause 2: In a package diffusion task, NEs included in the package diffusion task
fail to receive the commit command due to microwave link failures.
1. Check whether any microwave link is faulty.
If... Then...
The links are faulty Rectify the faults on the microwave links and
ensure that the links along which the package is
diffused are normal.
The links are Perform the commit operation for the alarmed NE.
normal
----End
Related Information
None
A.2.176 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL alarm indicates that the commit operation on an NE
fails in a package loading task.
Attribute
Parameters
None

This alarm indicates that the software versions in the OFS1 and OFS2 areas of the
system control unit are inconsistent. As a result, the package loading task fails and
the upgrade task fails.
Possible Causes
● Cause 1: The package file fails to be copied.
● Cause 2: Software fails to be loaded or activated.
Procedure
Step 1 Re-load the software package to the NE.
----End

Related Information
None
A.2.177 SWDL_INPROCESS
Description
The SWDL_INPROCESS alarm indicates that the NE is performing a package
loading task.
Attribute
Warning Processing error alarm
Parameters
None

Do not change NE configurations, download/upload files, back up databases, or
perform other similar operations before the task is completed.
Possible Causes
Cause: The NE is performing a package loading task.
Procedure
Step 1 Wait until the alarm clears. The alarm clears after the package loading task is
completed or after a rollback is completed in the case of a diffusion failure.
----End
Related Information
None
A.2.178 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK alarm indicates 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 in the process of package loading, the loading task fails.
● If this alarm occurs in other cases, automatic software matching fails.
Possible Causes
Cause: A file in the software package is lost and cannot be recovered.
Procedure
Step 1 Load the correct software package onto the alarmed NE.
----End
Related Information
None
A.2.179 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM alarm indicates 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 version of the software package is inconsistent with that described in the
software package. As a result, certain functions of the NE may be affected.
Possible Causes
Cause: The software version information in the description file of the software
package is inconsistent with the actual information about the software version.
Procedure
Step 1 Ensure that the loaded software package is correct. Perform package loading for
the NEs that report the SWDL_PKGVER_MM alarm.
----End
Related Information
None
A.2.180 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 fault cause. When Parameter 1 is set to 0x12, the
clock component is abnormal.
Parameter 2 Indicates the position of the fault.

● When Parameter 2 is 0x01, the SI5349 chip is abnormal.
● When parameter 2 is 0x02, the SI5349PLLA is unlocked.
● When parameter 2 is 0x03, the SI5349PLLB is unlocked.
● When Parameter 2 is 0x04, the SI5349 chip is lost.
● When Parameter 2 is 0x05, the SI5349 chip has frequency
deviation.
● When Parameter 2 is 0x06, the working clock is lost.


When the SYN_BAD alarm occurs, the quality of the clock source indicated by the
alarm parameter deteriorates. Tracing the clock source may cause bit errors to
services.
Possible Causes
● Cause 1: The quality of the synchronization clock source traced by the
equipment deteriorates.
● Cause 2: A hardware fault occurs on the clock board.
Procedure
1. Cause 1: The quality of the synchronization clock source traced by the
equipment.
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 upstream NE.

is a line clock
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 is faulty Rectify the fault.
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.

2. Cause 2: A hardware fault occurs on the clock board.

a. Replace the trouble unit.
Related InformationNone
None.
A.2.181 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL alarm indicates that an NE rollback fails.
Attribute
Parameters
None

This alarm affects some functions of the system.
Possible Causes
Cause: Rolling back the NE version fails.
Procedure
Step 1 Re-load the software package on the NCE.
----End
Related Information
None
A.2.182 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the synchronization clock source is
lost in the priority table.

Attribute
Warning Equipment alarm
Parameters
None

The NE clock degrades or enters the free-run mode.
Possible Causes
● In S1 mode:
– Cause 1: The cable is faulty (in the case of tracing the Ethernet clock
source) or the microwave link is incorrect.
● In non-S1 mode:
– Cause 1: The clock quality of the local NE changes.
Procedure
Step 1 On the NMS, check whether alarms causing the loss of the clock source are
generated on the NE.
1. See Checking the Clock 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 any of the following

microwave link clock. alarms is generated: R_LOF,
MW_LIM, LOOP_ALM, and
MW_LOF. If yes, preferentially
handle this alarm.
The synchronization source is a Check whether any of the following

Ethernet clock. alarms is generated: ETH_LOS,
ETH_LINK_DOWN, and LOOP_ALM.
If yes, preferentially handle this
alarm.
Step 2 If the clock source priority table is incorrectly configured, correct this
configuration. For details, see Configuring the System Clock Source.
Step 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 Setting the Basic
Attributes for an Ethernet Port.

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.
Step 4 Check whether the SYNC_C_LOS alarm is cleared. If the alarm persists, contact
Huawei technical support engineers.
----End
Related Information
None
A.2.183 SYSLOG_COMM_FAIL
Description
The SYSLOG_COMM_FAIL alarm indicates that the communication between the
NE and the syslog server fails.
Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicate the IP address of the Syslog server.
Parameter 5 Indicates the failure type.

● 0x01: The connection is interrupted.
● 0x02: The session is abnormal.

The syslog information of the NE cannot be sent to the syslog server.
Possible Causes
Cause 1: In the TCP mode, the connection between the NE and syslog server is
interrupted, or the session between the NE and server is abnormal.

Procedure
Step 1 Rectify the fault of the link between the NE and syslog server, or rectify the fault
of the protocol.
----End
Related Information
None
A.2.184 TEM_HA
Description
The TEM_HA alarm indicates 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, and replace it. For details,
see Replacing an SFP Module.
----End
Related Information
None

A.2.185 TEM_LA
Description
The TEM_LA alarm indicates 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, and replace it. For details,
see Replacing an SFP Module.
----End
Related Information
None
A.2.186 TEMP_ALARM
Description
The TEMP_ALARM alarm indicates that the temperature crosses the lower/upper
threshold.

Attribute
Minor Environment alarm
Parameters
table.
Name Meaning
Parameter 1 ● 0x01: The temperature crosses the upper threshold.
● 0x02: The temperature crosses the lower threshold.
Parameter 2 Indicates the alarmed location.
● 0x01: overall system
● 0x02: power amplifier

Services or the equipment may be affected, and the NE cannot work normally.
Possible Causes
● Cause 1: The ambient temperature crosses the upper/lower threshold.
● Cause 2: The temperature detection circuit of the NE is faulty.
Procedure
Step 1 Query the value of Parameter 1 on the NMS.
Step 2 If Parameter 1 takes the value of 0x01, the ambient temperature is excessively
high.
1. Lower the ambient temperature by taking measures such as installing a sun
shield and improving ventilation.
2. If the alarm persists, replace the NE.
Step 3 If Parameter 1 takes the value of 0x02, the ambient temperature is excessively low.
1. Increase the ambient temperature by taking warm-keeping measures.
2. If the alarm persists, replace the NE.
----End

Related Information
None.
A.2.187 TF
Description
The TF alarm indicates a laser transmission failure. This alarm occurs when an NE
detects that the output optical power of the laser crosses the preset alarm
threshold.
Attribute
Parameters
None

The laser transmission fails, causing service interruptions.
Possible Causes
● Cause 1: The laser is damaged.
Procedure
Step 1 Perform the operations in 4.2 Replacing an SFP Module.
----End
Related Information
None
A.2.188 TIME_LOCK_FAIL
Description
The TIME_LOCK_FAIL alarm indicates that time locking fails.

Attribute
Parameters
table.
Name Meaning
Parameter 1 0x01: The clock synchronization function is not enabled.

0x02: The clock is unlocked.
0x03: The transmit time of the master NE is consistent with the
receive time of the slave NE.
0x04: The transmit time of the slave NE is consistent with the
receive time of the master NE.
0x05: Time adjustment exceeds the upper threshold.
0x07: Time synchronization starts.

The slave node cannot trace the time of the master node and services contain bit
errors.
Possible Causes
● Cause 1: Jump of the time stamp at the local node is dramatic.
● Cause 2: Time adjustment frequently occurs on the upstream node.
● Cause 3: The master node is not synchronous with the slave node.
Procedure
Step 1 On the NMS, check whether the CLK_LOCK_FAIL alarm occurs. If yes, clear these
alarms.
Step 2 If time adjustment frequently occurs on the upstream node, check for the cause
and rectify the issue.
Step 3 If the master node is not synchronous with the slave node, rectify clock
configurations to synchronize their clocks.
----End

Related Information
None
A.2.189 TIME_LOS
Description
The TIME_LOS alarm indicates loss of the time source level. When the PTP is
enabled, this alarm will be reported if a clock source status is lost.
Attribute
Major Clock alarm
Parameters
table.
Name Meaning
Parameters 1 and 2 Indicate ID of the time source.
Each time source number occupies two bytes. The first byte
indicates the slot ID and the second byte indicates the port
number. Port numbers start from 1.

The local NE cannot trace the time of its upstream NE.
Possible Causes
Cause 1: A physical fault, for example, a port or link fault, occurs.
Procedure
Step 1 Cause 1: A physical fault, for example, a port or link fault, occurs.
1. Locate the port that reports the TIME_LOS alarm, according to the alarm
parameters.
2. If an IF port reports the TIME_LOS alarm, check whether it also reports
MW_LOF and MW_RDI alarms. If it reports MW_LOF and MW_RDI alarms,
clear these two alarms first.

3. If an Ethernet port reports TIME_LOS alarm, check whether it also reports

ETH_LOS and ETH_LINK_DOWN alarms. If it reports ETH_LOS and
ETH_LINK_DOWN alarms, clear these two alarms first.
4. Check whether the TIME_LOS alarm is cleared. If the TIME_LOS alarm persists,
----End
Related Information
None
A.2.190 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE alarm indicates that the high precision time of an NE
is in the non-tracing state. This alarm is reported when the high precision time
function is enabled on an NE but the currently traced source is the internal source.
Attribute
Parameters
None

The local NE may not be time synchronized with its upstream NE.
Possible Causes
● Cause 1: The link between the local NE and its upstream NE is faulty.
● Cause 2: The announce attributes of the upstream NE cause the failure to
trace the time source.
Procedure
Step 1 Cause 1: The link between the traced time source and the local NE is faulty.
1. Rectify the link fault.
Step 2 Cause 2: The announce attributes of the upstream NE cause the failure to trace
the time source.
1. Check the clock tracing relationship on the entire network according to the
network plan.
----End

Related Information
None
A.2.191 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED alarm indicates that a tunnel protection group
degrades.
Attribute
Major QoS 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 for an Ethernet
Port, check whether the port is disabled.
Enable the port if it was disabled.
Step 4 Refer to 6.1.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, and 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 6.1.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
A.2.192 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 QoS 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 Querying MPLS tunnel information.
----End
Related Information
None
A.2.193 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
● 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
A.2.194 USB_PROCESS_FAIL
Description
The USB_PROCESS_FAIL alarm indicates that databases cannot be recovered from
or backed up to the USB flash drive.
Attribute

Parameters
table.
Name Meaning
Parameter 1 Indicates the operation type.
● 0x01: data recovery
● 0x02: data backup
Parameter 2 Indicates the file type.
● 0x01: software package
● 0x02: patch package
● 0x03: system parameter area
● 0x04: script file
● 0x05: database file
● 0x06: license file
● 0x08: device locked

Database backup/recovery fails, and the system remains in the original state.
Possible Causes
● Cause 1: Databases cannot be recovered from the USB flash drive.
● Cause 2: Databases cannot be backed up to the USB flash drive.
Procedure
Step 1 Determine the type of the file that cannot be recovered from or backed up to the
USB flash drive according to the alarm parameters.
Step 2 In the case of a recovery failure, verify that the data in the USB flash drive is
correct, and perform another recovery attempt.
Step 3 In the case of a backup failure, verify that the NE can identify the USB flash drive
type and no unnecessary files exist on the USB disk drive. Then insert the USB
flash drive for another backup.
----End
Related Information
For the loading principles and types of USB flash drives, see USB Flash Drive.

A.2.195 VERSION_NOTSUPPORT
Description
The VERSION_NOTSUPPORT alarm indicates that the system control board of the
current version does not support the function or data configured for an NE.
Attribute
Parameters
Name Meaning
Parameter 1 This parameter has a fixed value of 0x01, indicating that the
function is not supported in the current version.
Parameter 2 This parameter has a fixed value of 0x01, indicating that the
number of VLANs exceeds 1024.

The configured function is not available or the configured data does not take
effect.
Possible Causes
Cause: More than 1024 VLANs are configured on the NE.
Procedure
Step 1 Re-configure services or delete functions that are not supported in the current
version to ensure that 1024 or less VLANs are configured on the NE.
----End
Related Information
None

Maintenance Guide B Performance Event Reference
B Performance Event Reference
Performance events are important indicators when the equipment performance

changes. This section describes all the possible performance events on the OptiX
RTN 380 and how to handle these performance events.
B.1 Performance Event List

The performance event list includes all the performance events of the OptiX RTN
380 and classifies them into different types.
B.1.1 Microwave Performance Events

Microwave performance events include the performance events regarding the
microwave power, ATPC, AM, microwave bit errors, and SNR.
Table B-1 Microwave power performance events

Performance Event Name Description
TSL_MAX Maximum radio transmitted signal

level
TSL_MIN Minimum radio transmitted signal

level
TSL_CUR Current radio transmitted signal level
TSL_AVG Average radio transmitted signal level
RSL_MAX Maximum radio received signal level
RSL_MIN Minimum radio received signal level
RSL_CUR Current radio received signal level
RSL_AVG Average radio received signal level

TLHTT Duration when the transmit power is

higher than the upper threshold
TLLTT Duration when the transmit power is

higher than the lower threshold
RLHTT Duration when the receive power is

lower than the upper threshold
RLLTT Duration when the receive power is

lower than the lower threshold
Table B-2 FEC performance events

FEC_UNCOR_BLOCK_CNT Number of frames that cannot be

corrected through FEC
Table B-3 Microwave link bit error performance events

IF_BBE Microwave link background block error
IF_BER Radio link bit error rate
IF_ES Microwave link errored second
IF_SES Microwave link severely errored second
IF_UAS Microwave link unavailable second
IF_CSES Microwave link consecutive severely

errored second
Table B-4 ATPC performance events

ATPC_P_ADJUST Positive ATPC adjustment event
ATPC_N_ADJUST Negative ATPC adjustment event

Table B-5 AM performance events

AMDOWNCNT Count of AM/AMAC downshifts
AMUPCNT Count of AM/AMAC upshifts
QAM_S_WS16 Working duration in 16QAMSTRONG

mode
QAMWS16 Working duration of the 16QAM mode
QAMWS2048 Working duration of the 2048QAM

mode
QPSKWS Working duration of the QPSK mode
QPSK_S_62P5M_WS Working duration of the QPSK Strong

mode with a 62.5 MHz spacing
QPSK_S_125M_WS Working duration of the QPSK Strong

mode with a 125 MHz spacing



Table B-6 SNR&MSE performance events

IF_SNR_MAX Maximum SNR
IF_SNR_MIN Minimum SNR
IF_SNR_AVG Average SNR
IF_MSE_MAX Maximum MSE
IF_MSE_MIN Minimum MSE
IF_MSE_AVG Average MSE
IF_MSE_CUR Current MSE

Table B-7 Port bit error performance events

PORT_BER_CNT Number of bit errors on ports
B.1.2 MPLS Tunnel/PW Performance Events

This section lists MPLS tunnel/PW performance events.
Table B-8 MPLS tunnel/PW performance events

Event Name Description
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
MPLS_TUNNEL_LS Tunnel packet loss seconds
MPLS_TUNNEL_SLS Tunnel severe packet loss seconds
MPLS_TUNNEL_CSLS Tunnel consecutive severe packet loss

seconds
MPLS_TUNNEL_UAS Tunnel unavailable seconds
MPLS_TUNNEL_LS_N Tunnel packet loss seconds at the near

end
MPLS_TUNNEL_SLS_N Tunnel severe packet loss seconds at

the near end
MPLS_TUNNEL_CSLS_N Tunnel consecutive severe packet loss

seconds at the near end
MPLS_TUNNEL_UAS_N Tunnel unavailable seconds at the near

end

B.1.3 Other Performance Events

Other performance events include performance events regarding optical power,
temperature, clock, and CPU/memory usage.
Table B-9 Optical power performance events
TPLMAX Maximum transmit power of a laser
TPLMIN Minimum transmit power of a laser
TPLCUR Current transmit power of a laser
RPLMAX Maximum receive power of a laser
RPLMIN Minimum receive power of a laser
RPLCUR Current receive power of a laser
Table B-10 Transmitted bias current performance events
TLBMAX Maximum transmitted bias current of

the laser
TLBMIN Minimum transmitted bias current of

the laser
TLBCUR Current transmitted bias current of the

laser
Table B-11 Board temperature performance events
BDTEMPMAX Maximum temperature of a board
BDTEMPMIN Minimum temperature of a board
BDTEMPCUR Current temperature of a board
Table B-12 Laser temperature performance events
OSPITMPMAX Maximum laser temperature
OSPITMPMIN Minimum laser temperature

OSPITMPCUR Current laser temperature
Table B-13 RF power amplifier temperature performance events
PATEMPMAX Maximum temperature of an RF power

amplifier
PATEMPMIN Minimum temperature of an RF power

amplifier
PATEMPCUR Current temperature of an RF power

amplifier
Table B-14 CPU usage performance events
CPUUSAGEMAX Maximum CPU usage
CPUUSAGEMAX Minimum CPU usage
CPUUSAGECUR Current CPU usage
CPUUSAGEAVG Average CPU usage
Table B-15 Memory usage performance events
MEMUSAGEMAX Maximum memory usage
MEMUSAGEMIN Minimum memory usage
MEMUSAGECUR Current memory usage
MEMUSAGEAVG Average memory usage
Table B-16 Clock performance events
MAXPHASEOFFSET Maximum phase offset
MINPHASEOFFSET Minimum phase offset

AVGPHASEOFFSET Average phase offset
MAXMEANPATHDELAY Maximum path delay
MINMEANPATHDELAY Minimum path delay
AVGMEANPATHDELAY Average path delay
Table B-17 Bandwidth usage threshold-crossing time events

Event Name Description
TX_BWUTIL_EXCS Time for which the bandwidth usage

at the transmit direction exceeds the
specified threshold
RX_BWUTIL_EXCS Time for which the bandwidth usage

at the receive direction exceeds the
specified threshold
TX_BWUTIL_EXCS_MIN Time for which the bandwidth usage

low specified threshold
RX_BWUTIL_EXCS_MIN Time for which the bandwidth usage

low specified threshold
TX_BWUTIL_EXCS_MID Time for which the bandwidth usage

middle specified threshold
RX_BWUTIL_EXCS_MID Time for which the bandwidth usage

middle specified threshold
TX_BWUTIL_EXCS_MAX Time for which the bandwidth usage

high specified threshold
RX_BWUTIL_EXCS_MAX Time for which the bandwidth usage

high specified threshold
B.2 Performance Events and Handling Procedures

This section describes all the possible performance events on the OptiX RTN 380
and how to handle these events.

B.2.1 AMDOWNCNT and AMUPCNT
Description
● AMDOWNCNT indicates the count of AM/AMAC downshifts in the current
performance monitoring period.
● AMUPCNT indicates the count of AM/AMAC upshifts in the current
performance monitoring period.
Attribute
Attribute Description
Performance event cell ACMDCNT (AMDOWNCNT),

ACMUCNT (AMUPCNT)
Unit None

● A large value of this event indicates frequent AM/AMAC shifts.
● If there is no factor that can affect a communication link such as sudden
weather changes but the AM shift count is very large, the communication link
may be faulty. You must check the communication link to prevent link
failures.
Relevant Alarms
AM_DOWNSHIFT
This alarm is not reported by default. If you need the reporting of this alarm,
change the setting according to 6.7.5 Setting Monitoring and Auto-Report
Status of Performance Events.
Possible Causes
When the AM/AMAC function is enabled, the modulation scheme varies
depending on the link quality. One change from a lower order modulation scheme
to a higher order modulation scheme is recorded as one upshift, causing the
AMUPCNT to increase by one. Similarly, one change from a higher order
modulation scheme to a lower order modulation scheme is recorded as one
downshift, causing the AMDOWNCNT to increase by one.
When the AM/AMAC function is enabled and the modulation scheme is

downshifted to QPSK Strong, the channel spacing also varies depending on the
link quality. One change from a lower spacing to a higher spacing is recorded as
one upshift, causing the AMUPCNT to increase by one. Similarly, one change from
a higher spacing to a lower spacing is recorded as one downshift, causing the
AMDOWNCNT to increase by one.

B.2.2 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
degrades. If this event occurs, you need to increase the transmit power of the
OptiX RTN 380 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
improves or the transmit power of the OptiX RTN 380 is very high. If this
event occurs, you need to decrease the transmit power of the OptiX RTN 380.
Attribute
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
does not affect services. A large value of this event indicates frequent ATPC
adjustments.
If there is no factor that can affect a communication link such as sudden weather
changes but the ATPC adjustment count is very large, the communication link may
be faulty. You must check the communication link to prevent link failures.
Relevant Alarms
None
B.2.3 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
B.2.4 MEMUSAGEMAX, MEMUSAGEMIN, MEMUSAGECUR, and

MEMUSAGEAVG
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

None
Relevant Alarms
None
B.2.5 MAXMEANPATHDELAY, MINMEANPATHDELAY, and

AVGMEANPATHDELAY
Description
● MAXMEANPATHDELAY indicates the maximum path delay between the
master clock and the slave clock.

● MINMEANPATHDELAY indicates the minimum path delay between the master

clock and the slave clock.
● AVGMEANPATHDELAY indicates the average path delay between the master
Attribute
Performance event cell MAXMEANPATHDELAY

(MAXMEANPATHDELAY)
MINMEANPATHDELAY
(MINMEANPATHDELAY)
AVGMEANPATHDELAY
(AVGMEANPATHDELAY)
Unit ns

The difference between MAXMEANPATHDELAY and MINMEANPATHDELAY
reflects the variation of path delay. If the difference is too large, the clock
performance will be affected.
Relevant Alarms
None
B.2.6 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR

Description
● BDTEMPMAX indicates the maximum temperature of an NE.
● BDTEMPMIN indicates the minimum temperature of an NE.
● BDTEMPCUR indicates the current temperature of an NE.
Attribute
Performance event cell XCS_TEMP
Unit 0.1°C

If the temperature of an NE is very high or very low, the performance of the NE
degrades and bit errors or other faults occur.

Relevant Alarms
The TEMP_ALARM alarm is reported if the temperature of a board exceeds the
specified threshold.
B.2.7 FEC_UNCOR_BLOCK_CNT
Description
FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be corrected
through FEC.
This event presents the number of errored blocks after FEC is performed.
Attribute
Performance event cell FECUNCORBLOCKCNT
Unit Block

If the value of FEC_UNCOR_BLOCK_CNT is not zero, services will contain bit errors.
Relevant Alarms
The MW_FEC_UNCOR alarm is reported if any bytes cannot be corrected. This
alarm is not reported by default. If you need the reporting of this alarm, change
the setting according to Setting Monitoring and Auto-Report Status of
Performance Events.
B.2.8 IF_BBE, IF_ES, IF_SES, IF_CSES, IF_UAS, and IF_BER

Description
● IF_BBE indicates the microwave link background block error.
BBE refers to the errored blocks excluding those in the unavailable seconds
and severely errored seconds.
● IF_ES indicates the microwave link errored second.
An ES refers to a second in which one or more errored blocks are detected.
● IF_SES indicates the microwave link severely errored second.
An SES refers to a 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 higher than or equal to 10-2 or
the signal is lost.
● IF_CSES indicates the microwave link consecutive severely errored second.

A CSES refers to a second in a period (shorter than 10 seconds) when severely

errored seconds occur continuously.
● IF_UAS indicates the microwave link unavailable second.
A UAS period starts from the first second of 10 consecutive SESs. These ten
seconds are a part of the unavailable time. A new available second period
starts from the first second of ten consecutive non-SESs. These ten seconds
are a part of the available time.
● IF_BER indicates the radio link bit error ratio (BER).
The BER is the number of bit errors divided by the total number of bits
transferred on a microwave link within a specified interval.
Attribute
Performance event cell IF_BIP8 (IF_BBE, IF_ES, IF_SES, IF_CSES,

IF_UAS)
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)

A small number of bit errors do not affect services. Excessive bit errors, however,
cause service interruptions. Generally, the BER requirement is less than 10-3 for
voice services, and less than 10-6 for data services.
Relevant Alarms
The MW_BER_SD or MW_BER_EXC alarm is reported if the BER exceeds the
specified threshold.
Possible Causes
The system detects bit errors on the microwave link by using the bit error
detection overheads in microwave frames.
Procedure
Step 1 See the MW_BER_SD or MW_BER_EXC alarm.
----End

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

A higher signal-to-noise ratio indicates better link performance and a lower
signal-to-noise ratio indicates worse link performance such as bit errors or service
interruptions.
Relevant Alarms
None
B.2.10 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
B.2.11 MAXPHASEOFFSET, MINPHASEOFFSET, and

AVGPHASEOFFSET
Description
● MAXPHASEOFFSET indicates the maximum phase offset between the master
● MINPHASEOFFSET indicates the minimum phase offset between the master
● AVGPHASEOFFSET indicates the average phase offset between the master
Attribute
Performance event cell MAXPHASEOFFSET

(MAXPHASEOFFSET),
MINPHASEOFFSET
(MINPHASEOFFSET),
AVGPHASEOFFSET
(AVGPHASEOFFSET)
Unit ns

This performance event reflects the phase offset between the local NE and the
upstream NE. If the phase offset is larger than 100 ns for a while, the local NE
cannot lock the time of the upstream NE. That is, time synchronization fails
between the local NE and the upstream NE.
Relevant Alarms
The TIME_LOCK_FAIL is reported if this performance event takes a value greater
than 100 ns.

B.2.12 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.
B.2.13 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

Attribute Meaning
Unit Second

The larger the number of packet loss seconds in one measurement period (for
example, 15 minutes or 24 hours), the more packets are lost, which seriously
affects the quality of service.
Procedure
Check the bandwidth utilization. If the set bandwidth has been reached or
exceeded, capacity expansion is required.
B.2.14 MPLS_TUNNEL_LS, MPLS_TUNNEL_SLS,

MPLS_TUNNEL_CSLS, and MPLS_TUNNEL_UAS
Description
● MPLS_TUNNEL_LS indicates packet loss seconds of MPLS services.
● MPLS_TUNNEL_SLS indicates severe packet loss seconds of MPLS services.
● MPLS_TUNNEL_CSLS indicates consecutive severe packet loss seconds of
MPLS services.
● MPLS_TUNNEL_UAS indicates unavailable seconds of MPLS services.
Attribute
Attribute Meaning
Performance event cell MPLS_TUNNEL_FLR
Unit Second

Procedure

B.2.15 MPLS_TUNNEL_LS_N, MPLS_TUNNEL_SLS_N,

MPLS_TUNNEL_CSLS_N, and MPLS_TUNNEL_UAS_N
Description
● MPLS_TUNNEL_LS_N indicates packet loss seconds of MPLS services at the
local end.
● MPLS_TUNNEL_SLS_N indicates severe packet loss seconds of MPLS services
at the local end.
● MPLS_TUNNEL_CSLS_N indicates consecutive severe packet loss seconds of
MPLS services at the local end.
● MPLS_TUNNEL_UAS_N indicates unavailable seconds of MPLS services at the
local end.
Attribute
Attribute Meaning
Performance event cell MPLS_TUNNEL_FLR_N
Unit Second

Procedure
B.2.16 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

Description
● OSPITMPMAX indicates the maximum temperature of a laser.
● OSPITMPMIN indicates the minimum temperature of a laser.
● OSPITMPCUR indicates the current temperature of a laser.
Attribute
Performance event cell TEMMN
Unit 0.1°C


If the temperature of a laser is excessively high or low, the performance of the
laser degrades and bit errors or other faults occur.
Relevant Alarms
None
B.2.17 PATEMPMAX, PATEMPMIN, and PATEMPCUR

Description
● PATEMPMAX indicates the maximum temperature of the radio frequency
signal power amplifier.
● PATEMPMIN indicates the minimum temperature of the radio frequency
signal power amplifier.
● PATEMPCUR indicates the current temperature of the radio frequency signal
power amplifier.
Attribute
Performance event cell XCS_TEMP
Unit 0.1°C

If the temperature of the radio frequency signal power amplifier is over low/high,
the output of radio frequency signal will become unstable, causing bit errors in
services or other faults.
Relevant Alarms
The TEMP_ALARM alarm is reported if the temperature of the radio frequency
signal power amplifier exceeds the lower/upper threshold.
B.2.18 PORT_BER_CNT
Description
The PORT_BER_CNT performance event indicates the number of bit errors on
ports.

Attribute
Performance event cell PORTBERCNT
Unit -

A few bit errors do not affect services. Excessive bit errors may degrade the service
quality.
Relevant Alarms
PORT_BER_SD
B.2.19 QAM_S_WS16, QAMWS16, QAMWS32, QAMWS64,

QPSKWS, QPSK_S_62P5M_WS, QPSK_S_125M_WS,
QPSK_S_250M_WS, QPSK_S_500M_WS, QPSK_S_750M_WS
Description
● QAM_S_WS16 indicates the working duration in 16QAMSTRONG mode.
● QAMWS16 indicates the working duration of the 16QAM modulation scheme.
● QPSKWS indicates the working duration of the QPSK modulation scheme.
● QPSK_S_62P5M_WS indicates the working duration of the QPSK Strong
modulation scheme with a 62.5 MHz spacing.
● QPSK_S_125M_WS indicates the working duration of the QPSK Strong
modulation scheme with a 125 MHz spacing.

Attribute
Performance event cell QAM_S_WS16SECOND(QAM_S_WS16)

QAMWS16SECOND(QAMWS16)
QPSKWSSECOND(QPSKWS)
QPSK_S_62P5M_WSSECON(QPSK_S_62
P5M_WS)
QPSK_S_125M_WSSECOND
(QPSK_S_125M_WS)
QPSK_S_250M_WSSECOND(QPSK_S_2
50M_WS)
00M_WS)
50M_WS)
Unit Second

When the adaptive modulation and adaptive channel space (AM/AMAC)function
is disabled, the performance event does not affect the system.
When the AM/AMACfunction is enabled and weather conditions are favorable, the
working duration (unit: s) of the AM full capacity mode should be the longest. If
the working duration of a lower-order modulation scheme is the longest, the
microwave link may be abnormal.
Relevant Alarms
None
B.2.20 RLHTT, RLLTT, TLHTT, and TLLTT

Description
● RLHTT indicates the duration when the receive power is lower than the upper
threshold.
● RLLTT indicates the duration when the receive power is lower than the lower
threshold.
● TLHTT indicates the duration when the transmit power is higher than the
upper threshold.
● TLLTT indicates the duration when the transmit power is higher than the
lower threshold.

TLHTT and TLLTT are valid only when automatic transmit power control (ATPC) is enabled.
Attribute
Performance event cell RLHTS (RLHTT), RLLTS (RLLTT), TLHTS

(TLHTT), and TLLTS (TLLTT)
Unit Second

None
Relevant Alarms
None
B.2.21 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.1 dBm

When the radio received signal level is very low or very high, bit errors occur and
even services are interrupted.
Relevant Alarms
If the radio received signal level exceeds the specified threshold, the
RADIO_RSL_HIGH or RADIO_RSL_LOW alarm is reported.

B.2.22 TLBMAX, TLBMIN, and TLBCUR

Description
● TLBMAX indicates the maximum transmitted bias current of a laser.
● TLBMIN indicates the minimum transmitted bias current of a laser.
● TLBCUR indicates the current transmitted bias current of a laser.
Attribute
Performance event cell LSBCM
Unit 0.1 mA

Excessively high/low current may cause damage to lasers.
Relevant Alarms
The IN_PWR_ABN alarm will be reported if the receive optical power of the
opposite site is abnormal.
B.2.23 TPLMAX, TPLMIN, and TPLCUR

Description
● TPLMAX indicates the maximum transmit optical power at an optical port.
● TPLMIN indicates the minimum transmit optical power at an optical port.
● TPLCUR indicates the current transmit optical power at an optical port.
Attribute
Performance event cell OPM
Unit 0.1 dBm

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

Relevant Alarms
The IN_PWR_ABN alarm will be reported if the receive optical power of the
opposite site is abnormal.
B.
2.24 TX_BWUTIL_EXCS,RX_BWUTIL_EXCS,TX_BWUTIL_EXCS_MI
N,RX_BWUTIL_EXCS_MIN,TX_BWUTIL_EXCS_MID,RX_BWUTIL_E
XCS_MID,TX_BWUTIL_EXCS_MAX,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 low specified threshold in a
period.
● RX_BWUTIL_EXCS_MIN indicates the total time for which the bandwidth
usage at the receive direction exceeds the low specified threshold in a period.
● TX_BWUTIL_EXCS_MID indicates the total time for which the bandwidth
usage at the transmit direction exceeds the middle specified threshold in a
period.
● RX_BWUTIL_EXCS_MID indicates the total time for which the bandwidth
usage at the receive direction exceeds the middle specified threshold in a
period.
● TX_BWUTIL_EXCS_MAX indicates the total time for which the bandwidth
usage at the transmit direction exceeds the high specified threshold in a
period.
● RX_BWUTIL_EXCS_MAX indicates the total time for which the bandwidth
usage at the receive direction exceeds the high specified threshold in a period.

Attribute
Performance event cell TX_BWUTIL_EXC_SEC(TX_BWUTIL_EXC

S)
RX_BWUTIL_EXC_SEC(RX_BWUTIL_EXC
S)
TX_BWUTIL_EXCS_MIN(TX_BWUTIL_EX
C_SEC_MIN)
RX_BWUTIL_EXCS_MIN(RX_BWUTIL_EX
C_SEC_MIN)
TX_BWUTIL_EXCS_MID(TX_BWUTIL_EX
C_SEC_MID)
RX_BWUTIL_EXCS_MID(RX_BWUTIL_EX
C_SEC_MID)
TX_BWUTIL_EXCS_MAX(TX_BWUTIL_EX
C_SEC_MAX)
RX_BWUTIL_EXCS_MAX(RX_BWUTIL_E
XC_SEC_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 remains high for a long time, upgrade the bandwidth for
the NE.
Step 4 If the bandwidth usage exceeds the maximum threshold for a long time, upgrade
the bandwidth for the NE.
----End

B.2.25 RPLMAX, RPLMIN, and RPLCUR

Description
● RPLMAX indicates the maximum receive optical power at an optical port.
● RPLMIN indicates the minimum receive optical power at an optical port.
● RPLCUR indicates the current receive optical power at an optical port.
Attribute
Performance event cell IPM
Unit 0.1 dBm

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 very low or very high, bit errors occur and even
services are interrupted.
Relevant Alarms
The IN_PWR_ABN alarm is reported if the receive optical power is abnormal.
B.2.26 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.1 dBm


When the radio transmitted signal level is very low or very high, the radio received
signal level at the opposite site is accordingly very low or very high. As a result, bit
errors occur and even services are interrupted.
Relevant Alarms
If the radio transmitted signal level is out of the range supported by the OptiX
RTN 380, the RADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.

Maintenance Guide C RMON Event Reference
C RMON Event Reference
RMON events reflect the running status of Ethernet services. This section describes
all the possible RMON events on the RTN 380 and how to handle these events.
C.1 RMON Performance Entry List

RMON performance entries refer to the table entries in the RMON statistics group
or RMON history group.
Table C-1 Basic performance entry list

Performance Entry Name Description Remarks
RXPKTS Received packets (packets) Bad packets, broadcast

packets, and multicast packets
are included.
ETHDROP Packet loss events (times) ETHDROP indicates the

number of packet loss events
caused by insufficient
resources.
RXOCTETS Received bytes (bytes) RXOCTETS indicates the total

number of bytes in received
packets (including bad
packets), including framing
bits but not FCS bytes.
RXMULCAST Received multicast packets RXMULCAST indicates the total

(packets) number of received good
packets with multicast
destination addresses,
excluding broadcast packets.

RXBRDCAST Received broadcast packets RXBRDCAST indicates the total

(packets) number of received good
packets with broadcast
excluding multicast packets.
ETHOVER Received oversized packets Indicates the number of

(packets) received packets that are
longer than MTU bytes
(including FCS bytes but not
framing bits) and do not
contain any other errors.
ETHJAB Received oversized error ETHJAB indicates the number

packets (packets) of received packets that are
larger than MTU (including
FCS bytes but not framing bits)
and contain FCS errors or
alignment errors.
ETHUNDER Received undersized packets Undersized packets are the

(packets) packets shorter than 64 bytes
framing bits) and contain no
errors.
ETHFRG Received fragments (packets) ETHFRG indicates the number

of received packets that are
shorter than 64 bytes
framing bits) and contain FCS
errors or alignment errors.
PORT_RX_BW_UTILIZATION Bandwidth utilization at a Bandwidth utilization =

receive port (Number of received bytes x 8/
Monitoring period)/Configured
or actual bandwidth
PORT_TX_BW_UTILIZATION Bandwidth utilization at a Bandwidth utilization =

transmit port (Number of transmitted bytes
x 8/Monitoring period)/
Configured or actual
bandwidth
PORT_RX_BW_UTILIZATION_M Minimum bandwidth Minimum bandwidth

IN utilization ratio at a receive utilization ratio at a receive
port port = (Number of received
bytes x 8/Monitoring period)/
bandwidth

PORT_RX_BW_UTILIZATION_A Average bandwidth utilization Average bandwidth utilization

VG ratio at a receive port ratio at a receive port =
(Number of received bytes x 8/
or actual bandwidth
PORT_RX_BW_UTILIZATION_M Maximum bandwidth Maximum bandwidth

AX utilization ratio at a receive utilization ratio at a receive
bandwidth
PORT_TX_BW_UTILIZATION_M Minimum bandwidth Minimum bandwidth

IN utilization ratio at a transmit utilization on a transmit port =
port (Number of transmitted bytes
bandwidth
PORT_TX_BW_UTILIZATION_A Average bandwidth utilization Average bandwidth utilization

VG ratio at a transmit port on a transmit port = (Number
of transmitted bytes x 8/
or actual bandwidth
PORT_TX_BW_UTILIZATION_M Maximum bandwidth Maximum bandwidth

AX utilization ratio at a transmit utilization on a transmit port =
bandwidth
RXPKT64 Packets received (64 bytes in FCS bytes are included, but
length) (packets) framing bits are excluded.
RXPKT65 Packets received (65-127 bytes FCS bytes are included, but
in length) (packets) framing bits are excluded.
RXPKT128 Packets received (128-255 FCS bytes are included, but

bytes in length) (packets) framing bits are excluded.


RXPKT1024 Total of received packets of FCS bytes are included, but

1024 to 1518 bytes (including framing bits are excluded.
bad packets)

Table C-2 Extended performance entry list

RXBGOOD Bytes in received good packets FCS bytes are included, but
(bytes) framing bits are excluded.
TXBGOOD Bytes in transmitted good FCS bytes are included, but

packets (bytes) framing bits are excluded.
RXBBAD Bytes in received bad packets FCS bytes are included, but
(bytes) framing bits are excluded.
TXUNICAST Transmitted unicast packets The unicast packets that are

(packets) discarded or fail to be
transmitted are included.
RXUNICAST Received unicast packets RXUNICAST indicates the

(packets) number of good unicast
packets.
TXMULCAST Transmitted multicast packets The multicast packets that are

TXBRDCAST Transmitted broadcast packets The broadcast packets that are

RXGOODFULLFRAMESPEED Bit rate of received good full Framing bits (20 bytes) and
frames (kbit/s) FCS bytes are included.
TXGOODFULLFRAMESPEED Bit rate of transmitted good Framing bits (20 bytes) and
full frames (kbit/s) FCS bytes are included.
RXFULLBGOOD Number of bytes in received Framing bits (20 bytes) and

good full frames (bytes) FCS bytes are included.
TXFULLBGOOD Number of bytes in Framing bits (20 bytes) and

transmitted good full frames FCS bytes are included.
(bytes)
RXPAUSE Received PAUSE frames RXPAUSE indicates the number

(frames) of MAC flow control frames
with the PAUSE opcode.
TXPAUSE Transmitted PAUSE frames TXPAUSE indicates the number

RXPKT1519 Total of received packets of FCS bytes are included, but

1519 to MTU bytes (including framing bits are excluded.
bad packets)
TXPKT64 Total of transmitted 64-byte FCS bytes are included, but

packets (including bad framing bits are excluded.
packets)

TXPKT65 Total of transmitted packets of FCS bytes are included, but

65 to 127 bytes (including bad framing bits are excluded.
packets)

bad packets)

bad packets)

bad packets)

bad packets)

1519 to MTU bytes (including framing bits are excluded.
bad packets)
TXPKTS Number of transmitted Bad packets, broadcast

packets (unit: packet) packets, and multicast packets
are included.
RX_DROP_RATIO Packet loss rate in the receive Discarded packets in the

direction (unit: 0.01%) receive direction/Total of
received packets.
TX_DROP_RATIO Packet loss rate in the transmit Discarded packets in the

direction (unit: 0.01%) transmit direction/Total of
transmitted packets.
TXOCTETS Number of transmitted bytes Total number of transmitted

(unit: byte) bytes (including those in bad
packets), including FCS bytes
but not framing bits.
RXBPS Bit rate (bit/s) in the receive Bit rate = Number of received
direction bytes x 8/Monitoring period
TXBPS Bit rate (bit/s) in the transmit Bit rate = Number of

direction transmitted bytes x 8/
Monitoring period
RXPPS Packet rate (packets/second) Packet rate = Number of

in the receive direction received packets/Monitoring
period

TXPPS Packet rate (packets/second) Packet rate = Number of

in the transmit direction transmitted packets/
Monitoring period
ETHFCS FCS error frames Number of received frames

that contain an integral
number of bytes but have FCS
errors. Oversized and
undersized frames are
excluded.
ETH_RX_THROUGHPUT_MAX Maximum port throughput Throughput = Number of

(kbit/s) in the receive direction received bytes (including
preambles and interframe
gaps)/Monitoring period
ETH_RX_THROUGHPUT_MIN Minimum port throughput Throughput = Number of

ETH_RX_THROUGHPUT_AVG Average port throughput Throughput = Number of

TX_DROP_PKTS Number of lost packets in the -

transmit direction
RX_DROP_PKTS Number of lost packets in the -

receive direction
ETH_TX_THROUGHPUT_MAX Throughput at the transmit

direction = Total number of
received bytes (including the
Indicates the maximum preamble and frame gap)/
transmit throughput of a port. Measurement period
ETH_TX_THROUGHPUT_MIN Throughput at the transmit

Indicates the minimum preamble and frame gap)/
transmit throughput of a port. Measurement period
ETH_TX_THROUGHPUT_AVG Throughput at the transmit

Indicates the average transmit preamble and frame gap)/
throughput of a port. Measurement period
RXBRDCAST_RATIO Broadcast traffic ratio in the Ratio of broadcast and

receive direction multicast packets to all packets
in the receive direction

TXBRDCAST_RATIO Broadcast traffic ratio in the Ratio of broadcast and

transmit direction multicast packets to all packets
in the transmit direction

bandwidth

or actual bandwidth

bandwidth

bandwidth

or actual bandwidth

bandwidth
RX_MAX_BW_UTILIZATION_CA Air interface bandwidth with Air interface bandwidth when

PACITY maximum RX bandwidth usage the bandwidth usage reaches
over a port the maximum value in the
receive direction
TX_MAX_BW_UTILIZATION_CA Air interface bandwidth with Air interface bandwidth when

PACITY maximum TX bandwidth usage the bandwidth usage reaches
over a port the maximum value in the
transmit direction

Table C-3 L2VPNa performance entry list

VUNI_RCVPKTS Packets received on the V-UNI -
VUNI_RCVBYTES Number of bytes received on -

the V-UNI
VUNI_SNDPKTS Number of packets -

transmitted on the V-UNI
VUNI_SNDBYTES Number of bytes transmitted -

on the V-UNI
VLAN_RCVPKTS Number of packets received by -

a VLAN to which a V-UNI
belongs
VLAN_RCVBYTES Number of bytes received by a -

VLAN to which a V-UNI
belongs
VLAN_SNDPKTS Number of packets -

transmitted by a VLAN to
which a V-UNI belongs
VLAN_SNDBYTES Number of bytes transmitted -

by a VLAN to which a V-UNI
belongs
VLAN_RX_BPS Bit rate (bit/s) in the receive Bit rate = Number of received
direction of a VLAN to which a bytes x 8/Monitoring period
V-UNI belongs
VLAN_RX_PPS Packet rate (packets/second) Packet rate = Number of

in the receive direction of a received packets x 8/
VLAN to which a V-UNI Monitoring period
belongs
VLAN_TX_BPS Bit rate (bit/s) in the transmit Bit rate = Number of

direction of a VLAN to which a transmitted bytes x 8/
V-UNI belongs Monitoring period
VLAN_TX_PPS Packet rate (packets/second) Packet rate = Number of

in the transmit direction of a transmitted packets x 8/
VLAN to which a V-UNI Monitoring period
belongs

Table C-4 ETH OAM 802.1ag performance entry list

ETH_CFM_FLR Packet loss rate of an E-Line Packet loss rate = (Number of

service packets transmitted by the
source MEP - Number of
packets received by the sink
MEP)/Number of packets
transmitted by the source MEP
ETH_CFM_FL Lost packets of an E-Line Number of lost packets =

service Number of packets transmitted
by the source - Number of
(Both numbers are detected by
the performance monitoring
scheme of OAM.)
ETH_CFM_FD Frame delay of an E-Line Frame delay = Time when the

service source MEP sends a request
packet - Time when the source
MEP receives the response
packet
ETH_CFM_FDV Frame delay variation of an E- Frame delay variation is the

Line service difference between two frame
delay test results.
Table C-5 Port traffic classification performance entry list

QOS_PORTCAR_MarkedRedPK Indicates the number of red -

TS packets after traffic
monitoring is enabled.
QOS_PORTCAR_MarkedYellow Indicates the number of yellow -

PKTS packets after traffic
QOS_PORTCAR_MarkedGreenP Indicates the number of green -

KTS packets after traffic
QOS_PORTSTRM_RCVMATCHP Indicates the number of -

KTS packets received in the
matched flow.
QOS_PORTSTRM_SNDMATCHP Indicates the number of -

KTS packets transmitted in the
matched flow.

QOS_PORTCAR_MarkedRedRA Indicates the proportion of Proportion of packets marked

TIO packets marked in red when in red in the ingress direction =
the traffic policing function is Number of packets marked in
enabled. red in the ingress direction/
Number of packets matching
the traffic classification rule in
the ingress direction
QOS_PORTSTRM_RX_PPS Indicates the packet rate Packet rate in the receive

(packets/s) in the receive direction = Number of received
direction of a matched flow. packets/Monitoring period
QOS_PORTSTRM_TX_PPS Indicates the packet rate Packet rate in the transmit

(packets/s) in the transmit direction = Number of
direction of a matched flow. transmitted packets/
Monitoring period
QOS_PORTSTRM_RCVMATCHB Indicates the number of bytes -

YTES (excluding inter-frame gaps
and preambles) in the received
packets of a matched flow.
QOS_PORTSTRM_SNDMATCH Indicates the number of bytes -

BYTES (excluding inter-frame gaps
and preambles) in the
transmitted packets of a
matched flow.
QOS_PORTSTRM_RX_BPS Indicates the bit rate in the Bit rate in the receive direction
receive direction of a matched = Number of received bytes
flow. (including inter-frame gaps
and preambles) x 8/Monitoring
period
QOS_PORTSTRM_TX_BPS Indicates the bit rate in the Bit rate in the transmit
transmit direction of a direction = Number of received
matched flow. bytes (including inter-frame
gaps and preambles) x 8/
Monitoring period
Table C-6 Port priority performance entry list

QOS_PORTQUEUE_DROPRATI Indicates the ratio of packet Packet loss rate in an egress

O loss due to congestion in queue = Number of discarded
egress queues with different packets with a priority in the
priorities. egress queue/Number of
packets with the priority in the
egress queue

QOS_PRI_DROPPKTS Indicates the number of -

packets discarded in the
services with different
priorities.
QOS_PRI_DROPBYTES Indicates the number of bytes -

discarded in the services with
different priorities.
PORT_PRI_SNDPKTS Indicates the number of -

packets transmitted in egress
queues with different
priorities.
PORT_PRI_SNDBYTES Indicates the number of bytes -

in the packets transmitted in
egress queues with different
priorities.
PORT_PRI_TX_BPS Indicates the bit rates of egress Bit rate = Number of

queues with different priorities transmitted bytes x 8/
in the transmit direction. Monitoring period
PORT_PRI_TX_PPS Indicates the packet rate Packet rate = Number of

(packets/second) of egress transmitted packets/
queues with different priorities Monitoring period
in the transmit direction.
Table C-7 1+1 performance entry list

RXPKTS Bad packets, broadcast

Indicates the packets received packets, and multicast packets
(packets). are included.
ETHDROP Indicates the packet loss ETHDROP indicates the

events (times). number of packet loss events
caused by insufficient Ethernet
chip resources. The count is
not the number of discarded
packets but the number of
times packet loss is detected.
Indicates the bytes received RXOCTETS indicates the total

(bytes). number of bytes in received
RXOCTETS bits but not FCS bytes.

RXMULCAST Indicates the multicast packets RXMULCAST indicates the total

received (packets). number of received good
RXBRDCAST Indicates the broadcast RXBRDCAST indicates the total

packets received (packets). number of received good
PORT_RX_BW_UTILIZATION Indicates the bandwidth Bandwidth utilization =

utilization on a port in the (Number of received bytes x 8/
receive direction. Monitoring period)/Configured
or actual bandwidth
PORT_TX_BW_UTILIZATION Indicates the bandwidth Bandwidth utilization =

utilization on a port in the (Number of transmitted bytes
transmit direction. x 8/Monitoring period)/
bandwidth

bandwidth

or actual bandwidth

bandwidth

bandwidth


or actual bandwidth

bandwidth

TXPKTS Indicates the packets Bad packets, broadcast

transmitted (packets). packets, and multicast packets
are included.
TXOCTETS Indicates the bytes transmitted Indicates the total number of

bytes in transmitted packets
(including bad packets),
including framing bits but not
FCS bytes.
ETHFCS Indicates the FCS errored Indicates the number of

frames (frames). received frames that are an
integral number of octets in
length but do not pass the FCS
check.
TXBGOOD Indicates the bytes in received FCS bytes are included, but
good packets (bytes). framing bits are excluded.
RXBGOOD Indicates the bytes in FCS bytes are included, but

transmitted good packets framing bits are excluded.
(bytes).
RXBBAD Indicates the bytes in received FCS bytes are included, but
bad packets (bytes). framing bits are excluded.
TXUNICAST Indicates the unicast packets The unicast packets that are
transmitted (packets). discarded or fail to be
RXUNICAST Indicates the unicast packets RXUNICAST indicates the

received (packets). number of good unicast
packets.
TXMULCAST Indicates the multicast packets The multicast packets that are

TXBRDCAST Indicates the broadcast The broadcast packets that are

packets transmitted (packets). discarded or fail to be
RXGOODFULLFRAMESPEED Indicates the rate of good full- Framing bits (20 bytes) and
frame bytes received (kbit/s). FCS bytes are included.
TXGOODFULLFRAMESPEED Indicates the rate of good full- Framing bits (20 bytes) and
frame bytes transmitted FCS bytes are included.
(kbit/s).
RXFULLBGOOD Indicates the good full-frame Framing bits (20 bytes) and
bytes received (bytes). FCS bytes are included.
TXFULLBGOOD Indicates the good full-frame Framing bits (20 bytes) and
bytes transmitted (bytes). FCS bytes are included.
TXPKT64 Indicates the count of FCS bytes are included, but

transmitted 64-byte packets framing bits are excluded.
(errored packets included)

transmitted packets with a framing bits are excluded.
length of 65 to 127 bytes





length of over 1518 bytes

RXPKT1519 Indicates the count of received FCS bytes are included, but
packets with a length of over framing bits are excluded.
1518 bytes (errored packets
included)
Table C-8 PLA performance entry list







or actual bandwidth

bandwidth


bandwidth

or actual bandwidth

bandwidth

bandwidth

or actual bandwidth

bandwidth
RXPKT64 Packets received (64 bytes in FCS bytes are included, but
length) (packets) framing bits are excluded.
RXPKT65 Packets received (65-127 bytes FCS bytes are included, but
in length) (packets) framing bits are excluded.






are included.

FCS bytes.

check.

(bytes).

packets.

(kbit/s).








included)
TX_DROP_RATIO Packet loss rate in the transmit -

direction (unit: 0.01%)
TX_DROP_PKTS Number of lost packets in the

transmit direction -
RXBPS Bit rate (bit/s) in the receive Bit rate = Number of received
direction bytes x 8/Monitoring period

TXBPS Bit rate (bit/s) in the transmit Bit rate = Number of

direction transmitted bytes x 8/
Monitoring period
RXPPS Packet rate = Number of

Packet rate (packets/second) received packets/Monitoring
in the receive direction period
TXPPS Packet rate = Number of

Packet rate (packets/second) transmitted packets/
in the transmit direction Monitoring period
RXBRDCAST_RATIO Broadcast traffic ratio in the Ratio of broadcast and

receive direction multicast packets to all packets
in the receive direction
TXBRDCAST_RATIO Broadcast traffic ratio in the Ratio of broadcast and

transmit direction multicast packets to all packets
in the transmit direction
Table C-9 LAG performance entry list








or actual bandwidth

bandwidth

bandwidth

or actual bandwidth

bandwidth

bandwidth

or actual bandwidth


bandwidth


are included.

FCS bytes.

check.

(bytes).

packets.


(kbit/s).







included)
RXPAUSE Received PAUSE frames RXPAUSE indicates the number


TXPAUSE Transmitted PAUSE frames TXPAUSE indicates the number

ETHOVER Received oversized packets Indicates the number of

(packets) received packets that are
longer than MTU bytes
framing bits) and do not
contain any other errors.
ETHJAB Received oversized error ETHJAB indicates the number

packets (packets) of received packets that are
larger than MTU (including
FCS bytes but not framing bits)
and contain FCS errors or
alignment errors.
ETHUNDER Received undersized packets Undersized packets are the

(packets) packets shorter than 64 bytes
framing bits) and contain no
errors.
ETHFRG Received fragments (packets) ETHFRG indicates the number

of received packets that are
framing bits) and contain FCS
errors or alignment errors.
Table C-10 MPLS-TP OAM performance entry list

MPLS_PW_FLR Indicates the packet loss rate Packet loss rate = (Number of
on the PW. packets transmitted by the
source - Number of packets
received by the sink)/Number
of packets transmitted by the
source
MPLS_PW_FLR_N Indicates the packet loss rate Packet loss rate = (Number of
on the PW at the near end. packets transmitted by the
source - Number of packets
received by the sink)/Number
of packets transmitted by the
source

MPLS_PW_FL Indicates the packet loss Number of lost packets =

number on the PW. Number of packets transmitted
scheme of OAM.)
MPLS_PW_FL_N Indicates the number of lost Number of lost packets =

packets on the PW at the near Number of packets transmitted
end. by the source - Number of
scheme of OAM.)
MPLS_PW_FD Indicates the frame delay on Frame delay = Time when the
the PW. source sends a request packet -
Time when the source receives
the response packet
MPLS_PW_FDV Indicates the frame delay Frame delay variation is the

variation on the PW. difference between two frame
delay test results.
MPLS_TUNNEL_FLR Indicates the packet loss rate Packet loss rate = (Number of
on the tunnel. packets transmitted by the
source tunnel - Number of
tunnel)/Number of packets
transmitted by the source
tunnel
MPLS_TUNNEL_FLR_N Indicates the packet loss rate Packet loss rate = (Number of
on the tunnel at the near end. packets transmitted by the
source tunnel - Number of
tunnel)/Number of packets
transmitted by the source
tunnel
MPLS_TUNNEL_FL Indicates the packet loss Number of lost packets =

number in the tunnel. Number of packets transmitted
scheme of OAM.)

MPLS_TUNNEL_FL_N Indicates the number of lost Number of lost packets =

packets on the tunnel at the Number of packets transmitted
near end. by the source - Number of
scheme of OAM.)
MPLS_TUNNEL_FD Indicates the frame delay in Frame delay = Time when the
the tunnel. source tunnel sends a request
packet - Time when the source
tunnel receives the response
packet
MPLS_TUNNEL_FDV Indicates the frame delay Frame delay variation is the

variation in the tunnel. difference between two frame
delay test results.
Table C-11 PW performance entry list

PW_RCVPKTS Indicates the number of -

packets received on the PW.
PW_SNDPKTS Indicates the number of Indicates the number of

packets transmitted on the PW. packets transmitted on a PW.
PW_RCVBYTES Indicates the number of bytes -

received on the PW.
PW_SNDBYTES indicates the number of bytes Indicates the number of bytes

transmitted on a PW. transmitted on a PW.
PW_DROPPKTS Indicates the number of -

packets discarded on the PW.
PW_RX_BPS Indicates the bit rate in the Bit rate = Number of received
receive direction of a bytes x 8/Monitoring period
monitored object.
PW_TX_BPS Indicates the bit rate in the Bit rate = Number of

transmit direction of a PW. transmitted bytes x 8/
Monitoring period
PW_RX_PPS Indicates the packet rate in the Packet rate = Number of

receive direction of a received packets/Monitoring
monitored object. period
PW_TX_PPS Indicates the packet rate in the Packet rate = Number of

transmit direction of a PW. transmitted packets/
Monitoring period

Table C-12 Tunnel performance entry list

TUNNEL_REVERSE_RCVPKTS Indicates the number of Indicates the number of

packets received in the reverse packets received in the reverse
tunnel. tunnel of a bidirectional transit
tunnel.
TUNNEL_REVERSE_SNDPKTS Indicates the number of Indicates the number of

packets transmitted in the packets transmitted in the
reverse tunnel. reverse tunnel of a
bidirectional transit tunnel.
TUNNEL_REVERSE_RCVBYTES Indicates the number of bytes Indicates the number of bytes

received in the reverse tunnel. received in the reverse tunnel
of a bidirectional transit
tunnel.
TUNNEL_REVERSE_SNDBYTES Indicates the number of bytes Indicates the number of bytes

transmitted in the reverse transmitted in the reverse
tunnel. tunnel of a bidirectional transit
tunnel.
TUNNEL_RCVPKTS Indicates the number of Indicates the number of

packets received in the tunnel. packets received in a tunnel.
TUNNEL_SNDPKTS Indicates the number of Indicates the number of

packets transmitted in the packets transmitted in a
tunnel. tunnel.
TUNNEL_RCVBYTES Indicates the number of bytes Indicates the number of bytes

received in the tunnel. received in a tunnel.
TUNNEL_SNDBYTES Indicates the number of bytes Indicates the number of bytes

transmitted in the tunnel. transmitted in a tunnel.
TUNNEL_REVERSE_RX_BPS Indicates the bit rate in the Bit rate = Number of received
receive direction of a reverse bytes x 8/Monitoring period
tunnel.
TUNNEL_REVERSE_TX_BPS Indicates the bit rate in the Bit rate = Number of received
transmit direction of a reverse bytes x 8/Monitoring period
tunnel.
TUNNEL_REVERSE_RX_PPS Indicates the packet rate in the Packet rate = Number of

receive direction of a reverse received packets/Monitoring
tunnel. period
TUNNEL_REVERSE_TX_PPS Indicates the packet rate in the Packet rate = Number of

transmit direction of a reverse transmitted packets/
tunnel. Monitoring period
TUNNEL_RX_BPS Indicates the bit rate in the Bit rate = Number of received
receive direction of a bytes x 8/Monitoring period
monitored object.

TUNNEL_TX_BPS Indicates the bit rate in the Bit rate = Number of

transmit direction of a tunnel. transmitted bytes x 8/
Monitoring period
TUNNEL_RX_PPS Indicates the packet rate in the Packet rate = Number of

receive direction of a received packets/Monitoring
monitored object. period
TUNNEL_TX_PPS Indicates the packet rate in the Packet rate = Number of

transmit direction of a tunnel. transmitted packets/
Monitoring period
a:
● supported by E-Line services only.
● VUNI refers to the virtual UNI corresponding to the service source or sink on the UNI side.
C.2 RMON Events and Handling Procedures

This section describes the RMON events that indicate Ethernet service exceptions
and how to handle these events.
C.2.1 ETHDROP
Description
ETHDROP indicates the number of events that packet loss occurs due to
insufficient resources. If the number exceeds the threshold, an RMON threshold-
crossing event will be reported.
ETHDROP does not count the packet loss events caused by link congestion or any other
factor.

Frequent packet loss events affect services and the system, and therefore require
immediate troubleshooting.
Relevant Alarms
MAC_EXT_EXC

Possible Causes
This performance event indicates packet loss due to the full MAC buffer, FIFO
overflow, or reverse pressure.
● The lower threshold is set to 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 from the
upper threshold opposite end. If the problem persists, go to
the next step.
----End
C.2.2 ETHFCS
Description
ETHFCS indicates the number of received Ethernet data frames with FCS errors or
alignment errors at the local end (excluding oversized and undersized frames). If
the number exceeds the threshold, an RMON threshold-crossing event will be
reported.

Most ports discard the packets with FCS errors or alignment errors. System
services are interrupted in the worst case.
Relevant Alarms
MAC_FCS_EXC
Possible Causes
1. The working modes of the local port and opposite port mismatch. For
example, one port works in full-duplex mode, and the other port works in
half-duplex mode.
2. Bit errors exist on the transmission line.
3. The local end is faulty.

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 local and opposite ports.
If... Then...
The working modes mismatch Change the working modes to the same.
The working modes match Go to the next step.
Step 3 Replace the fiber or optical module of the local or opposite port.
----End
C.2.3 ETHFRG
Description
ETHFRG indicates the number of received packets that are smaller than 64 packets
and contain FCS errors or alignment errors. If the number exceeds the threshold,
an RMON threshold-crossing event will be reported.

Data transmission is delayed or packet loss occurs.
Possible Causes
● The local port and opposite port work in different modes.
● The local end is faulty.
● The local port and opposite port work in half-duplex mode and communicate
a very high volume of data.
Procedure
Step 1 Check whether the local port and opposite port work in the same mode.
If... Then...
The ports work in the same Go to the next step.
mode
The ports work in different Change the working mode of the local port
modes to the same as the opposite port.

Step 2 Check whether the local port and opposite port work in half-duplex mode.
If... Then...
The ports do not work in half- Go to the next step.
duplex mode
The ports work in half-duplex mode Change the working modes to full-
duplex or auto-negotiation.
----End
C.2.4 ETHJAB
Description
ETHJAB indicates that the received packets are larger than the MTU value and
contain FCS errors or alignment errors. If the number of packets exceeds the
threshold, an RMON threshold-crossing event will be reported.

Data transmission is delayed or packet loss occurs.
Possible Causes
● The local port and opposite port work in different modes.
● The local end is faulty.
Procedure
Step 1 Check whether the local port and opposite port work in the same mode.
If... Then...
The ports work in the same Go to the next step.
mode
The ports work in different Change the working mode of the local port
modes to the same as the opposite port.
----End
C.2.5 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.


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 end that
that is longer than the maximum frame length the length of transmitted
set for the local equipment packets should be reduced.
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
C.2.6 ETHUNDER
Description
ETHUNDER indicates the number of received packets that are error-free and
shorter than 64 bytes. If the number exceeds the threshold, an RMON threshold-
crossing event will be reported.

The data frames of a length beyond the specific range are discarded. As a result,
the system services are affected.
Possible Causes
1. Excessive packets shorter than 64 bytes are received.
Procedure
Step 1 Check whether the opposite end transmits packets shorter than 64 bytes.

If... Then...
The opposite end transmits packets shorter Rectify the fault at the opposite
than 64 bytes end.
The opposite end does not transmit packets Go to the next step.
----End
C.2.7 RXBBAD
Description
RXBBAD indicates the total number of bytes in received bad packets, excluding
framing bits but including FCS bytes. If the number exceeds the threshold, an
RMON threshold-crossing event will be reported.

Bad packets are discarded at ports, and excessive bad packets may even interrupt
system services.
Relevant Alarms
MAC_EXT_EXC
Possible Causes
1. Errors occur when the opposite end transmits packets.
2. Bit errors exist on the transmission line.
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 Browsing Current Performance Events of Ethernet, and handle the errors at the
opposite end depending on the type of bad types.
Step 3 Handle the bit errors on the transmission line.

Check whether the local end reports ETH_LINK_DOWN or similar alarms because
the external line is damaged or over attenuated. If yes, clear these alarms.

----End

Maintenance Guide D Alarm Suppression Relationship
D 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 root alarm is reported but the reporting of
correlated alarms is suppressed depending on the alarm suppression relationship.
Table D-1 alarm suppression relationship for Ethernet services

Alarm Identifier of the Suppressed Alarm
Identifier
LSR_NO_FIT LASER_SHUT, ETH_LOS, TF, LSR_WILL_DIE, OUT_PWR_ABN

ED
LASER_MOD LASER_SHUT, LSR_WILL_DIE, IN_PWR_ABN, TEM_HA, TEM_LA,

_ERR R_LOS, ETH_LOS, ETH_LINK_DOWN, TFLSR_WILL_DIE,
OUT_PWR_ABN, TEM_HA, TEM_LA
LASER_SHUT LSR_WILL_DIE, TF, LSR_BCM_ALM, OUT_PWR_ABN
TF LSR_WILL_DIE, OUT_PWR_ABN
ETH_CFM_M ETH_CFM_UNEXPERI, ETH_CFM_LOC, ETH_CFM_RDI

ISMERGE
ETH_CFM_U ETH_CFM_LOC, ETH_CFM_RDI

NEXPERI
ETH_CFM_L ETH_CFM_RDI
OC
ETH_CFM_AI ETH_CFM_LOC
S

Table D-2 Alarm suppression relationship for Ethernet ports

Identifier
ETH_LOS ETH_LINK_DOWN, ETH_NO_FLOW
ETH_LINK_D MAC_FCS_EXC, ETH_EFM_DF

OWN
ETH_EFM_D ETH_EFM_REMFAULT
F
ETH_EFM_RE ETH_EFM_EVENT
MFAULT
ETH_AUTO_ LASER_SHUT
LINK_DOWN
Table D-3 Alarm suppression relationship for microwave ports

Identifier
MW_LOF AM_DOWNSHIFT, MW_FEC_UNCOR, MW_RDI, MW_LIM,

MW_BER_EXC, MW_BER_SD, R_LOF
MW_BER_EX MW_BER_SD
C
R_LOF MW_LIM, MW_BER_EXC, MW_BER_SD, MW_RDI
LCS_EXPIRE LCS_LIMITED
D
Table D-4 Alarm suppression relationship for CPRI ports

Identifier
LSR_NO_FIT LSR_WILL_DIE, LSR_BCM_ALM, TEM_LA, TEM_HA,

ED LASER_SHUT, LASER_MOD_ERR, R_LOF, R_LOS
LASER_MOD LSR_WILL_DIE, LSR_BCM_ALM, TEM_LA, TEM_HA,

_ERR LASER_SHUT, IN_PWR_ABN, R_LOS
R_LOS R_LOF, IN_PWR_ABN, PORT_BER_SD
R_LOF PORT_BER_SD
LASER_SHUT LSR_BCM_ALM

Table D-5 Alarm suppression relationship for MPLS Tunnel

Root Alarm Suppressed Alarm
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,
MPLS_TUNNEL_UNEXPMEP,
MPLS_TUNNEL_UNEXPPERMPLS_TUNNEL_LOCV,
MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,

EL_UNEXPM MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
EP MPLS_TUNNEL_UNEXPPERMPLS_TUNNEL_LOCV,
MPLS_TUNNEL_UNEXPPER

EL_AIS MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF, MPLS_TUNNEL_SD,
MPLS_TUNNEL_UNEXPMEP,
MPLS_TUNNEL_UNEXPPERMPLS_TUNNEL_LOCV,
MPLS_TUNN MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess,

EL_LOCV MPLS_TUNNEL_SFMPLS_TUNNEL_SF
MPLS_TUNN MPLS_TUNNEL_SD
EL_SF
Table D-6 Alarm suppression relationship for 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_UNEXPPERMPLS_PW_LOCV, MPLS_PW_SF,
MPLS_PW_U MPLS_PW_LOCV, MPLS_PW_UNKNOWN, MPLS_PW_Excess,

NEXPMEP MPLS_PW_SF, MPLS_PW_SD,
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_L MPLS_PW_UNKNOWN, MPLS_PW_Excess,

OCV MPLS_PW_SFMPLS_PW_SF
MPLS_PW_S MPLS_PW_SD
F
MPLS_PW_L MPLS_PW_LOCV, MPLS_PW_SF, MPLS_PW_SD

CK
Table D-7 Alarm suppression relationship for Tunnel APS

ETH_APS_PA ETH_APS_LOST
TH_MISMAT
CH
ETH_APS_LO ETH_APS_TYPE_MISMATCH, ETH_APS_SWITCH_FAIL

ST
Table D-8 Alarm suppression relationship for PW APS

PWAPS_SWI PWAPS_LOST, PWAPS_PATH_MISMATCH,

TCH_FAIL PWAPS_TYPE_MISMATCH
PWAPS_LOS PWAPS_PATH_MISMATCH, PWAPS_TYPE_MISMATCH

T

Table D-9 Alarm suppression relationship (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

RTN 380 V100R019C00 Maintenance Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RTN 380 V100R019C00 Maintenance Guide

Uploaded by

Copyright:

Available Formats

OptiX RTN 380 Radio Transmission System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Product Name Version

OptiX RTN 380 V100R019C00

This document is intended for:

● Network planning engineer

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. ii

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices

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.

Courier New Examples of information displayed on the screen

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are

{ x | y | ... } Optional items are grouped in braces and separated

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iii

[ x | y | ... ] Optional items are grouped in brackets and

{ x | y | ... }* Optional items are grouped in braces and separated

[ x | y | ... ]* Optional items are grouped in brackets and

Boldface Buttons, menus, parameters, tabs, window, and

> Multi-level menus are in boldface and separated by

Issue 02 (2020-06-30) Based on Product Version V100R019C00

Entire document All the screenshots of the U2000 are

- Fixed the known bugs.

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. iv

Issue 01 (2019-5-30) Based on Product Version V100R019C00

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. v

About This Document................................................................................................................ ii

2 Routine Maintenance Items............................................................................................... 16

5 Database Backup and Restoration.................................................................................... 43

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vi

5.3.1 Setting the User-Defined Backup Policy....................................................................................................................46

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. vii

6.7.5 Setting Monitoring and Auto-Report Status of Performance Events.............................................................. 92

7 Common Maintenance Operations................................................................................... 95

A Alarm Reference................................................................................................................. 132

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. viii

A.2.9 CLK_LOCK_FAIL................................................................................................................................................................ 153

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. ix

A.2.51 INSUFFCNT_FLSH_SPACE.......................................................................................................................................... 205

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. x

A.2.93 MPLS_TUNNEL_LOCK................................................................................................................................................. 249

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xi

A.2.135 PLA_PKT_ERR............................................................................................................................................................... 303

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xii

A.2.177 SWDL_INPROCESS..................................................................................................................................................... 352

B Performance Event Reference.......................................................................................... 372

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xiii

B.2.17 PATEMPMAX, PATEMPMIN, and PATEMPCUR...................................................................................................390

C RMON Event Reference..................................................................................................... 399

D Alarm Suppression Relationship..................................................................................... 432

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. xiv

1.1 General Safety Precautions

Issue 02 (2020-06-30) Copyright © Huawei Technologies Co., Ltd. 1